Chicago Router Node

This page provides views of data related to the Chicago 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-08 02:30:23 UTC
Last Booted: 2006-05-30 15:14:58 UTC
Uptime: 253 days, 21:04
Load Averages: 0.40, 0.26, 0.20
Temperatures: 27, 32 (C)
Last Configured: 2007-02-08 02:30:23 UTC

Links to Data

Connection Technologies

Network Speed Type Shared AS IP Address MTU Multicast
Connectors
NYSERNet OC-12 SONET NO 3754 IPv4 199.109.2.1 9180 YES
IPv6 2001:468:ff:f49::2 9180 NO
WiscREN OC-12 SONET NO 2381 IPv4 205.213.118.1 4470 YES
IPv6 2001:468:ff:f4f::2 4470 NO
Peers
Allstream YES 15290 IPv4 206.223.119.3 NO
IPv6  
Cox Communications YES 22773 IPv4 206.223.119.42 NO
IPv6  
DoubleClick YES 6432 IPv4 206.223.119.40 NO
IPv6  
ESnet OC-48 SONET NO 293 IPv4 198.125.140.53 9000 YES
IPv6  
Equinix Route Collector YES 65517 IPv4 206.223.119.125 NO
IPv6  
Global Crossing 10 gbps Ethernet YES 3549 IPv4 64.208.110.197 1500 NO
IPv6  
Globix Corporation YES 4513 IPv4 206.223.119.56 NO
IPv6  
Google YES 15169 IPv4 206.223.119.21 NO
IPv6  
HopOne Internet Corporation YES 14361 IPv4 206.223.119.91 NO
IPv6  
Host.net YES 13645 IPv4 206.223.119.69 NO
IPv6  
Limelight Networks YES 22822 IPv4 206.223.119.123 NO
IPv6  
Peer1 YES 13768 IPv4 206.223.119.30 NO
IPv6  
Server Central YES 23352 IPv4 206.223.119.57 NO
IPv6  
Shaw Cablesystems YES 6327 IPv4 206.223.119.20 NO
IPv6  
Swisscom IP-Plus YES 3303 IPv4 206.223.119.82 NO
IPv6  
TDS Telecom YES 4181 IPv4 206.223.119.64 NO
IPv6  
WV Fiber YES 19151 IPv4 206.223.119.18 NO
IPv6  
XEEX Communications YES 27524 IPv4 206.223.119.87 NO
IPv6  
YouTube YES 36561 IPv4 206.223.119.84 NO
IPv6  

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.