Denver Router Node

This page provides views of data related to the Denver Router Node. Included below are views of basic system data for the router node, usage statistics for connectors and peers, netflow summaries, throughput statistics, and one-way latency measurements. The tables below summarize the technologies used by connectors and peers. This later data is collected as part of the Visual Backbone project.

System Data

Data Collected: 2007-02-06 20:35:05 UTC
Last Booted: 2006-05-30 15:21:29 UTC
Uptime: 253 days, 20:58
Load Averages: 0.51, 0.24, 0.18
Temperatures: 32, 36 (C)
Last Configured: 2007-02-06 20:35:05 UTC

Links to Data

Connection Technologies

Network Speed Type Shared AS IP Address MTU Multicast
Connectors
Front Range GigaPoP OC-12 SONET NO 14041 IPv4 192.43.217.165 9000 YES
IPv6 2001:468:ff:1045::2 9000 NO
Intermountain GigaPoP OC-12 SONET NO 210 IPv4 205.124.237.9 9000 YES
IPv6 2001:468:ff:1048::2 9000 NO
Peers
CHECS-NET OC-48 SONET NO 3912 IPv4 206.206.145.6 9000 YES
IPv6  
Qwest Labs OC-3 SONET NO 209 IPv4  
IPv6 2001:468:ff:10c1::2 9000 NO

The table above describes the technogies associated with the connections to Abilene. It is constructed by creating a table of BGP peers associated with the router node. The peering data is obtained by doing the equivalent "show bgp neighor" on the router. That data contains a local interface except in cases where the peer is a multi-hop peer. The properties of the interfaces are collected by doing the equivalent of a "show interfaces". The data includes the speed and type of the interface on the abilene router. If two different peers come in through a common physical interface, then the connection is listed as shared. If two peering sessions for the same connection come in through a common logical interface and one is IPv4 and the other IPv6, they are combined into a common row of the table. If the BGP peer is also a pim neighbor, then the multicast column is set to "YES". Note that for IPv6, all multicast columns are therefore set to "NO". Note also that it is entirely possible for a BGP peer to have an IPv4 session on one logical-interface and an IPv6 session on a different logical-interface. Such sessions are listed on separate rows in the table above.