Los Angeles Router Node

This page provides views of data related to the Los Angeles 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-01-25 19:23:01 UTC
Last Booted:	2006-05-30 16:05:49 UTC
Uptime:	253 days, 20:16
Load Averages:	0.63, 0.36, 0.23
Temperatures:	26, 29 (C)
Last Configured:	2007-01-25 19:23:01 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
CalREN-2 South	10 gbps	Ethernet	NO	2153	IPv4	137.164.25.2	9000	YES
					IPv6	2001:468:ff:144e::2	9000	NO
Peers
AARNet	10 gbps	Ethernet	YES	7575	IPv4	207.231.241.4	9000	NO
					IPv6	2001:504:b:80::4	9000	NO
APAN/TransPAC2			YES	22388	IPv4	207.231.240.136		YES
					IPv6	2001:504:b:20::136		NO
CLARA			YES	27750	IPv4	207.231.240.138		YES
					IPv6	2001:504:b:20::138		NO
CUDI			YES	18592	IPv4	207.231.240.142		YES
					IPv6	2001:504:b:20::142		NO
NREN	10 gbps	Ethernet	YES	24	IPv4	207.231.246.3	9000	YES
					IPv6	2001:504:b:90::3	9000	NO
Qatar			YES	29384	IPv4	207.231.242.137		YES
					IPv6
SINET	10 gbps	Ethernet	YES	2907	IPv4	150.99.199.93	9000	NO
					IPv6
SingAREN			YES	23855	IPv4	207.231.242.140		NO
					IPv6
TWAREN			YES	7539	IPv4	207.231.240.133		YES
					IPv6	2001:504:b:20::133		NO
UltraLight	10 gbps	Ethernet	NO	32361	IPv4	198.32.11.42	9000	NO
					IPv6	2001:468:e9c:42::1	9000	NO
UniNet	OC-3	SONET	NO	4621	IPv4	63.216.18.54	4470	YES
					IPv6	2001:3c8:e100:1004::5	4470	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.