OIT Networking & Monitoring Services

Campus Core and Border Switches Traffic Statistics

Contents

  1. Overview
  2. border-87
  3. border-87-vrf-esnet
  4. border-87-vrf-aws-vpcs
  5. gigagate6
  6. core-87
  7. core-ns
  8. core-lewis
  9. ppn-87
  10. ppn-ha
  11. swch-ppn2
  12. swch-ppn3
  13. mini-swch-ppn
  14. voipgate
  15. voipgate2
  16. voipgate3
  17. 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 border-87

(switching processor cpu) (switching processor memory) (SUP RP 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 border-87 to our ISPs.

 


Virtual Router border-87-vrf-esnet

This is a virtual router running on the same hardware as switch/router border-87.

border-87 forwards all traffic from selected campus source addresses (regardless of its destination) to virtual router border-87-vrf-esnet. If virtual router border-87-vrf-esnet determines that the traffic's destination is reachable via ESnet, it forwards the traffic toward ESnet; otherwise it forwards the traffic back to border-87, so border-87 may route the traffic based on the traffic's destination.
 
Virtual router border-87-vrf-esnet announces to ESnet routes to those selected campus source addresses. When border-87-vrf-esnet receives traffic from ESnet, it forwards that traffic to border-87, so border-87 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.

 


Virtual Router border-87-vrf-aws-vpcs

This is a virtual router running on the same hardware as switch/router border-87.

Virtual router border-87-vrf-aws-vpcs is a router supporting OIT's connection to Amazon Web Services (AWS) Virtual Private Cloud (VPC) instances. Each AWS VPC is connected via an AWS Private Virtual Interface (VIF) to border-87-vrf-aws-vpcs. border-87-vrf-aws-vpcs downlinks via plinknet40 to Campus Data Network (CDN) router core-87.

You may also view a table showing traffic volume on all 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 core-87

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

This device acts as both a switch (layer 2) for most Campus Data Network (CDN) VLANs, and a router (layer 3) among most CDN VLANs. Only the layer 2 components are listed here; the layer 3 components appear as core-87 in Router Traffic Statistics.

This switch is becoming the core switch and router for all CDN VLANs.

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

You may view a port allocation map.


Core Switch core-ns

(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 New South Data Center.

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

You may view a port allocation map.

 

Host Aggregation Switch switch core-lewis

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

This device primarily connects servers located in the Lewis Science Library Data Center to CDN 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 ppn-87

(switching processor cpu) (switching processor memory) (SUP RP inlet temperature):

This switch will be replaced with switch ppn-ha.

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

This device acts as the core of the infranet4 VLAN.

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 ppn-ha

(switching processor cpu) (switching processor memory) (SUP RP inlet temperature):

This switch will be replacing switch ppn-87.

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

This device will act as the core of the infranet4 VLAN.

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) (SUP RP 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

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

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 Networking & Monitoring Services
The Office of Information Technology,
Princeton University