Router Traffic Statistics
We monitor traffic volume on selected router interfaces.
For each monitored router interface, you may view
graphs showing traffic volume in and out of that
interface over several recent time periods
(the past 31 hours, 8 days, 31 days, and 365 days).
In most cases, volume is measured by bit rate and packet rate.
Traffic graphed as "incoming"
(in
GREEN | )
represents traffic entering the monitored network interface,
while the traffic graphed as "outgoing"
(in BLUE | )
represents traffic leaving the network interface.
We also monitor some routers for CPU use and/or free memory.
The monitoring is performed with
mrtg,
RRDtool,
and
mrtg-rrd.
Except where noted otherwise,
links listed below in bold operate at 1000 Mbps full-duplex;
and links not listed in bold operate at 100 Mbps full-duplex.
The display you see will be refreshed automatically by your Web browser every five minutes.
The router interfaces we are monitoring are listed below, sorted by router.
-
border router vgate1
(routing processor cpu)
(routing processor memory)
This device acts both as a switch (layer 2) within VLANs,
and a router (layer 3) between VLANs.
Only the layer 3 components are listed here.
You may also view a table showing traffic volume on all interfaces ranked by
Bit Rate
or
Packet Rate.
You may view a map of our
Internet Flow and Monitoring Layout
showing the paths that lead from vgate1 to our ISPs.
Note that because the device performs Layer 3 Switching, most traffic
that traditionally would be routed between VLANs is instead switched, so is not reflected
on these graphs; the layer 3 component (router) in this device never sees that traffic.
To view all traffic regardless of whether it is routed, see
Campus Core and Border Switches Traffic Statistics.
This device acts as
a border router and firewall connecting Princeton University (and our off-campus outside customers) to the Internet and Internet2.
This device also acts as the router (but not physical connection point) for external customer networks.
- Connections to Internet and Internet2 Service Providers
(Uplinks to ISPs.)
-
PAETEC
bit rate
packet rate
PAETEC is an Internet1 Service Provider.
The connection is not directly between vgate1 and PAETEC router fastgate.
Instead,
vgate1 is attached
(sometimes via internal firewall vgate1-fwsm)
to (via tap 1) intrusion protection system internet1-ips,
which in turn is attached (via tap 2 leading to tap 3) to PAETEC router fastgate.
The connection between vgate1 and internet1-ips is 1000 Mbps full-duplex,
however bandwidth contracted with the ISP is 500 Mbps full-duplex.
-
PAETEC Backup
bit rate
packet rate
PAETEC is an Internet1 Service Provider.
This is a backup for our primary connection to them.
The connection is not always directly between vgate1 and PAETEC router fastgate-backup.
Instead,
vgate1 is attached
(sometimes via internal firewall vgate1-fwsm)
to PAETEC router fastgate-backup.
The connection between vgate1 and PAETEC router fastgate-backup is 1000 Mbps full-duplex,
however bandwidth contracted with the ISP is 500 Mbps full-duplex.
-
Patriot Communications
bit rate
packet rate
Patriot Communications is an Internet1 Service Provider.
The connection is not directly between vgate1 and Patriot router patriotgate.
Instead,
vgate1 is attached
(sometimes via internal firewall vgate1-fwsm)
to (via tap 4) intrusion protection system internet1-ips,
which in turn is attached (via tap 5 leading to tap 6) to to Patriot router patriotgate.
The connection between vgate1 and internet1-ips 1000 Mbps full-duplex,
however the bandwidth arranged with the ISP is 500 Mbps full-duplex.
-
MAGPI
bit rate
packet rate
MAGPI is an Internet2 Service Provider.
The connection is not directly from vgate1 to Internet2 MAGPI router magpigate.
Instead,
vgate1 is attached
(sometimes via internal firewall vgate1-fwsm)
to (via tap 7) intrusion protection system i2-ips,
which in turn is attached (via tap 8 leading to tap 9) to Internet2 MAGPI router magpigate.
The connection between vgate1 and i2-ips is 1000 Mbps full-duplex,
however, the bandwidth contracted with the ISP is 500 Mbps full-duplex.
- Connections to Princeton University
(Downlinks to the campus network.)
- Connections to Off-Campus Outside Customers
(Downlinks to off-campus outside customers.)
- Connections to External Customer Networks
(Downlinks to external customers, many of whom may be physically on-campus.)
-
core router gigagate1
(routing processor cpu)
(routing processor memory):
This device acts both as a switch (layer 2) within VLANs,
and a router (layer 3) between VLANs.
Only the layer 3 components are listed here.
You may also view a table showing traffic volume on all of this device's
router interfaces ranked by
Bit Rate
or
Packet Rate.
This device primarily connects servers located in the 87 Prospect Avenue Machine Room
to VLAN 128 (princeton-net) or VLAN 4014 (ringnet), VLAN 4017 (tbnnet), or VLAN 102 (baronet).
The device also connects VLAN 232 (towernet),
and VLAN 780 (linknet14) (leading to csgate).
-
core router gigagate2
(routing processor cpu)
(routing processor memory):
This device acts both as a switch (layer 2) within VLANs,
and a router (layer 3) between VLANs.
Only the layer 3 components are listed here.
You may also view a table showing traffic volume on all of this
device's router interfaces ranked by
Bit Rate
or
Packet Rate.
This device primarily connects campus subnets to the campus core.
The device also connects some non-princeton-net servers to the network.
-
core router gigagate4
(routing processor cpu)
(routing processor memory):
This device acts both as a switch (layer 2) within VLANs,
and a router (layer 3) between VLANs.
Only the layer 3 components are listed here.
You may also view a table showing traffic volume on all of this device's
router interfaces ranked by
Bit Rate
or
Packet Rate.
The device connects VLAN 1400 (Dormnet) to the campus core.
-
router csgate
(cpu)
A router connecting Computer Science private networks to gigagate1.
-
router gfdl-gate
(cpu)
(memory)
This device acts as both a switch (layer 2) within VLANs, and a router (layer 3) between VLANs.
Only the layer 3 components are listed here.
Note that because the device performs Layer 3 Switching,
most traffic that traditionally would be routed between VLANs is instead switched,
so is not reflected on these graphs; the layer 3 component (router) in this device never sees that traffic.
To view all traffic regardless of whether it is routed, see
Campus Core and Border Switches Traffic Statistics.
Useful Collections
The documents below collect some of the graphs above
from several related devices or interfaces.
-
All vgate1 Router interfaces - Past
day
week
month
year
Traffic (measured by both bit rate and packet rate).
-
vgate1 router interfaces leading (eventually) to ISPs - Past Day
bit rate
packet rate
-
Princeton Routers and Core Switches - CPU Use - Past
day
week
month
year
CPU use over the past day on core switches, routers, and some ISP routers.
Also include the switch components of core routers.
-
Routers - Interfaces Sorted by Current
bit rate
packet rate
Tables showing activity levels on core router interfaces, border router interfaces, and some ISP router interfaces.
A service of
OIT Network Systems
The Office of Information Technology,
Princeton University
