Indianapolis Router Node

This page provides views of data related to the Indianapolis 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-05 15:39:33 UTC
Last Booted: 2007-02-02 05:07:30 UTC
Uptime: 6 days, 7:13
Load Averages: 0.48, 0.21, 0.12
Temperatures: 29, 29 (C)
Last Configured: 2007-02-05 15:39:33 UTC

Links to Data

Connection Technologies

Network Speed Type Shared AS IP Address MTU Multicast
Connectors
Indiana GigaPoP NO 19782 IPv4 192.12.206.5 NO
IPv6  
Indiana GigaPoP 10 gbps Ethernet NO 19782 IPv4 192.12.206.250 9000 YES
IPv6 2001:468:ff:1244::2 9000 NO
Merit OC-12 SONET NO 237 IPv4 192.122.183.9 9000 YES
IPv6 2001:468:ff:1254::2 9000 NO
OARnet OC-48 SONET NO 3112 IPv4 192.88.192.133 9180 YES
IPv6  
University of Louisville OC-3 SONET NO 3714 IPv4 199.120.154.149 4470 YES
IPv6  
University of Minnesota (Northern Lights) OC-12 SONET NO 57 IPv4 192.42.152.170 9180 YES
IPv6 2001:468:ff:1259::2 9180 NO
Peers

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.