OIT Networking & Monitoring Services

Router Traffic Statistics

Contents

  1. Overview
  2. border-87
  3. border-87-vrf-esnet
  4. border-87-vrf-aws-vpcs
  5. core-87
  6. core-ns
  7. ppn-ha
  8. voipgate
  9. Useful Collections

Overview

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.

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 border-87

(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 border-87 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.

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 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 to 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 it 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 connections 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.

 

Core Router core-87

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.

This router is becoming the core of all CDN (Campus Data Network) networks.

You may also view a table showing traffic volume on all of this device's router interfaces ranked by Bit Rate or Packet Rate.

 

Core Router core-ns

This device acts as a switch (layer 2) within VLANs. In the future, it may also act as 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.

 

Core Router ppn-ha

(routing processor cpu) (routing processor memory)

This device acts both as a switch (layer 2) within PPN VLANs, and a router (layer 3) between some VLANs. Only the layer 3 components are listed here.

This device connects selected PPN networks (those routed to the campus) to the campus core.

You may also view a table showing traffic volume on all of this device's router interfaces ranked by Bit Rate or Packet Rate.

  • CAMPUS routing domain
  • ARTMUSEUMCAMERAS routing domain

  • DOORLOCKS routing domain

     

    Core Router voipgate

    (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), part of the campus routing domain.

    The device also 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.

     

    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