Atlanta Router Node

This page provides views of data related to the Atlanta 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-02 16:38:02 UTC
Last Booted: 2006-05-24 20:41:54 UTC
Uptime: 259 days, 15:36
Load Averages: 0.42, 0.17, 0.11
Temperatures: 31, 34 (C)
Last Configured: 2007-02-02 16:38:02 UTC

Links to Data

Connection Technologies

Network Speed Type Shared AS IP Address MTU Multicast
Connectors
Jackson State University OC-3 ATM NO 32229 IPv4 192.208.151.13 4470 YES
IPv6  
Mississippi State University OC-3 ATM NO 10546 IPv4 192.208.151.9 4470 YES
IPv6  
SoX 10 gbps Ethernet NO 10490 IPv4 199.77.193.9 9000 YES
IPv6 2001:468:ff:e43::2 9174 NO
South Florida GigaPoP 10 gbps Ethernet YES 20080 IPv4  
IPv6 2001:468:ff:e47::2 9000 NO
University of Mississippi OC-3 ATM NO 25656 IPv4 130.74.3.50 4470 YES
IPv6  
University of South Florida OC-3 SONET NO 5661 IPv4 131.247.47.238 4470 YES
IPv6 2001:468:ff:e56::2 4470 NO
University of Southern Mississippi OC-3 ATM NO 16430 IPv4 131.95.1.25 4470 YES
IPv6  
Peers
ANSP (via AmPath) OC-12 SONET YES 1251 IPv4 198.32.252.230 9180 YES
IPv6  
ESnet OC-48 SONET NO 293 IPv4 198.124.216.141 9000 YES
IPv6  
Florida LambdaRail YES 11096 IPv4  
IPv6 2001:468:ff:e5e::2 NO
REACCIUN-2 (via AmPath) OC-12 SONET YES 20312 IPv4 198.32.252.226 9180 NO
IPv6  
RNP2 (via AmPath) OC-12 SONET YES 1916 IPv4 198.32.252.222 9180 YES
IPv6  
RedCLARA (via AmPath) OC-12 SONET YES 27750 IPv4 198.32.252.206 9180 YES
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.