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.
We also monitor some routers for CPU use and/or free memory.
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) to PAETEC router fastgate.
The connection between vgate1 and internet1-ips is 1000 Mbps full-duplex,
and bandwidth contracted with the ISP is 1000 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,
and bandwidth contracted with the ISP is 1000 Mbps full-duplex.
-
Comcast
bit rate
packet rate
Comcast is an Internet1 Service Provider.
The connection is not directly between vgate1 and Comcast 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) to to Comcast 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) to Internet2 MAGPI router magpigate.
The connection between vgate1 and i2-ips is 1000 Mbps full-duplex,
and the bandwidth contracted with the ISP is 1000 Mbps full-duplex.
- Connections to Virtual Routers
-
vgate1-vrf-esnet
bit rate
packet rate
Virtual router vgate1-vrf-esnet runs on the same hardware as switch/router vgate1.
vgate1 forwards all traffic from selected campus source addresses (regardless of its destination)
to vgate1-vrf-esnet.
If virtual router vgate1-vrf-esnet determines that the traffic's destination is reachable via ESnet,
it forwards the traffic
(sometimes via internal firewall vgate1-fwsm)
to ESnet; otherwise it forwards the traffic back to vgate1,
so vgate1 may route the traffic based on the traffic's destination.
- 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.)
-
virtual router router vgate1-vrf-esnet
This is a virtual router running on the same hardware as switch/router vgate1
vgate1 forwards all traffic from selected campus source addresses (regardless of its destination)
to vgate1-vrf-esnet.
If virtual router vgate1-vrf-esnet determines that the traffic's destination is reachable via ESnet,
it forwards the traffic
(sometimes via internal firewall vgate1-fwsm)
to ESnet; otherwise it forwards the traffic back to vgate1,
so vgate1 may route the traffic based on the traffic's destination.
Virtual router vgate1-vrf-esnet announces to ESnet routes to those selected
campus source addresses.
When it receives traffic from ESnet, it forwards that traffic to vgate1,
so vgate1 may route the traffic based on the traffic's destination.
You may also view a table showing traffic volume on all interfaces ranked by
Bit Rate
or
Packet Rate.
- vgate1
bit rate
packet rate
-
ESnet
bit rate
packet rate
ESnet is the Energy Sciences Network.
The connection is not directly from vgate1-vrf-esnet to ESnet router esgate.
Instead,
vgate1-vrf-esnet is attached
(sometimes via internal firewall vgate1-fwsm)
to (via tap 10) intrusion protection system i2-ips,
which in turn is attached (via tap 11) to CWDM cwdm-forrestal-87pr-g07,
which in turn is attached to CWDM cwdm-forrestal-sayre-bdf,
which in turn is attached to ESnet router esgate.
The connection between vgate1-vrf-esnet and i2-ips is 1000 Mbps full-duplex,
as is the connection between i2-ips and cwdm-forrestal-87pr-g07,
as is the channel between cwdm-forrestal-87pr-g07 and cwdm-forrestal-sayre-bdf,
as is the connection between cwdm-forrestal-87pr-g07 and esgate,
and the bandwidth contracted with the network service provider is 1000 Mbps full-duplex.
-
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 3450 (bellnet), 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.
-
core router swch-ppn
(routing processor cpu)
(routing processor memory):
This device acts both as a switch (layer 2) within VLANs,
and a router (layer 3) between some 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 routes VLAN 4030 (infranet5) to the campus routing domain.
The device routes among all networks within the VOIP routing domain
(voipnet*, voip-servernet, plinknet1, plinknet2), but does not route those networks
to any other routing domain.
-
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.
The documents below collect some of the graphs above
from several related devices or interfaces.
