OIT Network Systems

Campus Core and Border Switches Traffic Statistics

Contents

  1. Overview
  2. vgate1
  3. vgate1-vrf-esnet
  4. vgate1-fwsm
  5. ips-primary
  6. gigagate1
  7. gigagate2
  8. gigagate4
  9. gigagate5
  10. gigagate6
  11. swch-ppn
  12. swch-ppn2
  13. swch-ppn3
  14. mini-swch-ppn
  15. voipgate
  16. voipgate2
  17. voipgate3
  18. Useful Collections

Overview

We monitor traffic volume on selected campus core and border switch interfaces.

The core switches are those that operate at the core of the campus network; the core of the network is in fact composed of these switches and the mesh of connections among them. The border switches are those that operate at the border connecting the campus network to the Internet and Internet2.

For each monitored interface, you may view graphs showing the 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 switches for CPU load and/or free memory.

The monitoring is performed with mrtg, rrdtool, and mrtg-rrd.

The display you see will be refreshed automatically by your Web browser every five minutes.

The switch interfaces we are monitoring are listed below, sorted by switch.

Border Switch vgate1

(switching processor cpu) (switching processor memory) (slot 5 inlet temperature):

This device acts both as a switch (layer 2), and a router (layer 3). Only the layer 2 components are listed here; the layer 3 components appear in Router Traffic Statistics.

This device connects Princeton University (and our off-campus outside customers) to the Internet and Internet2, acting both as the physical connection point and the router.

This device also acts as the router (but not physical connection point) for external customer networks.

You may view a port allocation map.

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.

 

Virtual 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 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.

 

Firewall vgate1-fwsm

(cpu) (connections)

This is a firewall interposed along the path between vgate1 and fastgate, interposed along the path between vgate1 and comcastgate, interposed along the path between vgate1 and magpigate, and interposed along the path between vgate1-vrf-esnet and esgate. These are the paths to our PAETEC, Comcast, MAGPI, and ESnet network service providers.

 

Intrusion Protection System ips-primary

This is an intrusion protection system interposed along the path between vgate1 and fastgate. and interposed along the path between vgate1 and comcastgate, and interposed along the path between vgate1 and magpigate. These are the paths to our PAETEC, Comcast, and MAGPI ISPs (but not our other ISPs).

Traffic statistics are unavailable for this device.  

Core Switch gigagate1

(switching processor cpu) (switching processor memory) (slot 7 inlet temperature):

This device acts both as a switch (layer 2) within each VLAN, and a router (layer 3) between VLANs. Only the layer 2 components are listed here; the layer 3 components appear as gigagate1 in Router Traffic Statistics.

This device primarily connects servers located in the 87 Prospect Avenue Machine Room to VLANs 6 (cs-oit-transport), 262 (cs-oit-tunnel), 52 (bulbnet), 128 (princeton-net), 3450 (bellnet), 4011 (doughnet), 4013 (expressnet), 4014 (ringnet), or 4017 (tbnnet). The device also provides the connection to VLAN 780 (linknet14) leading to csgate.

You may view a port allocation map.

You may also view a table showing traffic volume on all physical interfaces ranked by Bit Rate or Packet Rate.

 

Core Switch gigagate2

(switching processor cpu) (switching processor memory) (slot 7 inlet temperature):

This device acts both as a switch (layer 2) within each VLAN, and router (layer 3) between VLANs. Only the layer 2 components are listed here; the layer 3 components appear as gigagate2 in Router Traffic Statistics.

This device connects primarily academic buildings and offices to the campus core. The device also connects some non-princeton-net servers to the network.

You may view a port allocation map.

You may also view a table showing traffic volume on all interfaces ranked by Bit Rate or Packet Rate.

 

Core Switch gigagate4

(switching processor cpu) (switching processor memory) (slot 5 inlet temperature):

This device acts as both a switch (layer 2) within each VLAN, and a router (layer 3) between VLANs. Only the layer 2 components are listed here; the layer 3 components appear as gigagate4 in Router Traffic Statistics.

This device primarily connects dormitories, apartments, and eating clubs to the campus core.

You may view a port allocation map.

You may also view a table showing traffic volume on all interfaces ranked by Bit Rate or Packet Rate.

 

Host Aggregation Switch gigagate5

(switching processor cpu) (switching processor memory) (slot 5 inlet temperature):

This device acts as a switch (layer 2) within each VLAN.

This device primarily connects servers located in the New South Machine Room.

You may view a port allocation map.

You may view a table showing traffic volume on all physical interfaces ranked by Bit Rate or Packet Rate.)

 

Host Aggregation Switch gigagate6

(active supervisor cpu) (active supervisor memory) (slot 9 inlet temperature)

This device acts as a switch (layer 2) within each VLAN.

This device primarily connects servers located in the HPCRC Computer Room.

You may view a port allocation map.

You may view a table showing traffic volume on all physical interfaces ranked by Bit Rate or Packet Rate.)

 

Core Switch swch-ppn

(switching processor cpu) (switching processor memory) (slot 5 inlet temperature):

This device acts as both a switch (layer 2) with each PPN VLAN, and a router (layer 2) among some PPN VLANs. Only the layer 2 components are listed here; the layer 3 components appear as swch-ppn in in Router Traffic Statistics.

This switch is the core of the PPN VLANs.

This switch is the core of infranet4.

You may view a port allocation map.

You may also view a table showing traffic volume on all interfaces ranked by Bit Rate or Packet Rate.

 

Host Aggregation Switch swch-ppn2

(cpu) (memory)

This device acts as a switch (layer 2) within each VLAN.

This device primarily connects servers located in the New South Data Center to the PPN VLANs.

You may view a port allocation map.

You may view a table showing traffic volume on all physical interfaces ranked by Bit Rate or Packet Rate.

 

Host Aggregation Switch swch-ppn3

(cpu) (memory)

This device acts as a switch (layer 2) within each VLAN.

This device primarily connects servers located in the HPCRC Computer Room to the PPN VLANs.

You may view a port allocation map.

You may view a table showing traffic volume on all physical interfaces ranked by Bit Rate or Packet Rate.

 

Core Switch mini-swch-ppn

Under normal conditions, this switch provides no service. In the event of a disaster at 87 Prospect, this switch acts as the core of a minimal ppnnet (the Princeton Private Network) and stellanet.

You may view a port allocation map.

You may view a table showing traffic volume on all physical interfaces ranked by Bit Rate or Packet Rate.

 

Core Switch voipgate

(switching processor cpu) (switching processor memory) (slot 5 inlet temperature):

This device will act as both a switch (layer 2) with each VLAN, and a router (layer 2) between some VLANs. Only the layer 2 components are listed here; the layer 3 components appear as voipgate in in Router Traffic Statistics.

This switch is the core OIT VoIP Service, and supports the various VLANs supporting VoIP service. It does not switch those VLANs to the rest of the campus network.

This switch is the core of infranet5.

You may view a port allocation map.

You may also view a table showing traffic volume on all interfaces ranked by Bit Rate or Packet Rate.

 
 

Host Aggregation Switch voipgate2

(cpu) (memory)

This device acts as a switch (layer 2) within each VLAN.

This device primarily connects servers located in the New South Data Center to the VoIP VLANs.

You may view a port allocation map.

You may view a table showing traffic volume on all physical interfaces ranked by Bit Rate or Packet Rate.)

 

Host Aggregation Switch voipgate3

(cpu) (memory)

This device acts as a switch (layer 2) within each VLAN.

This device primarily connects servers located in the HPCRC Computer Room to the VoIP VLANs.

You may view a port allocation map.

You may view a table showing traffic volume on all physical interfaces ranked by Bit Rate or Packet Rate.

 

Useful Collections

The documents below collect some of the graphs above from several related devices or interfaces.

A service of OIT Network Systems
The Office of Information Technology,
Princeton University