Seattle Router Node

This page provides views of data related to the Seattle 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-07 19:50:24 UTC
Last Booted:	2006-05-30 16:46:32 UTC
Uptime:	253 days, 19:37
Load Averages:	0.65, 0.28, 0.15
Temperatures:	32, 35 (C)
Last Configured:	2007-02-07 19:50:24 UTC

Links to Data

Usage Statistics
Netflow Statistics
- Summary Statistics
- IP Protocol Statistics
Throughput Statistics
One-way Latency Statistics
- IPv4
- IPv6
Throughput Statistics
- TCP
  - IPv4
  - IPv6
- UDP
  - IPv4
  - IPv6

Connection Technologies

Network	Speed	Type	Shared	AS	IP	Address	MTU	Multicast
Connectors
Pacific/Northwest GigaPoP	10 gbps	Ethernet	NO	101	IPv4	209.124.179.1	9000	YES
					IPv6	2001:468:ff:16c2::2	9000	NO
Peers
AARNet (via Pacific Wave)	10 gbps	Ethernet	YES	7575	IPv4	207.231.240.4	9000	NO
					IPv6	2001:504:b:10::4	9000	NO
AARNet (via Pacific Wave)	10 gbps	Ethernet	YES	7575	IPv4	207.231.242.2	1500	YES
					IPv6	2001:504:b:11::2	1500	NO
CA*net (via Pacific Wave)	10 gbps	Ethernet	YES	6509	IPv4	198.32.170.44	1500	YES
					IPv6	2001:468:ff:16c1::3	1500	NO
CA*net (via Pacific Wave)	10 gbps	Ethernet	YES	6509	IPv4	207.231.240.3	9000	YES
					IPv6
DREN (via Pacific Wave)	10 gbps	Ethernet	YES	668	IPv4	198.32.170.37	1500	NO
					IPv6
DREN (via Pacific Wave)	10 gbps	Ethernet	YES	668	IPv4
					IPv6	2001:504:b:10::9	9000	NO
Experimental Microsoft	10 gbps	Ethernet	NO	8075	IPv4	198.32.170.40	1500	NO
					IPv6
GEMNET (via Pacific Wave)	10 gbps	Ethernet	YES	23796	IPv4	207.231.240.10	9000	YES
					IPv6
KOREN/KREONET2 (via Pacific Wave)	10 gbps	Ethernet	YES	17579	IPv4	198.32.170.33	1500	YES
					IPv6	2001:468:ff:16c1::6	1500	NO
NREN (via Pacific Wave)	10 gbps	Ethernet	YES	24	IPv4	207.231.245.131	9000	YES
					IPv6	2001:504:b:88::131	9000	NO
National University of Singapore	10 gbps	Ethernet	YES	7610	IPv4	198.32.170.47	1500	YES
					IPv6
REANNZ	10 gbps	Ethernet	YES	38018	IPv4	207.231.240.18	9000	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.