Wednesday, May 8, 2013

route-server.ip.att.net is now a juniper

I was working on a problem yesterday with a client that had ATT involvement, I found out one of the classic  route-server is now converted to  junos. This legacy  route-server has been around for years if not over a decade or more along with these;

route-server.he.net ( hurricane electric )
route-server.savvis.net
route-server.gblx.net
route-server.host.net ( I was one employed by them and they even purchase a competitor  that I also worked for )

To access ATT's route-server it's simple as telnet route-sever.ip.att.net

e.g

michel01:~ kfelix$ telnet route-server.ip.att.net
Trying 12.0.1.28...
Connected to route-server.cbbtier3.att.net.
Escape character is '^]'.
-------------- route-server.ip.att.net ---------------
---------  AT&T IP Services Route Monitor  -----------

The information available through route-server.ip.att.net is offered
by AT&T's Internet engineering organization to the Internet community.

This router maintains eBGP peerings with customer-facing routers
throughout the AT&T IP Services Backbone:

IPv4:
 12.123.21.243  Atlanta   12.123.133.124 Austin    12.123.41.250  Cambridge
 12.123.5.240   Chicago   12.123.17.244  Dallas    12.123.139.124 Detroit
 12.122.83.238  Denver    12.123.134.124 Houston   12.123.29.249  LA
 12.123.1.236   New York  12.123.33.249  Orlando   12.123.137.124 Philly
 12.123.142.124 Phoenix   12.123.145.124 SanDiego  12.123.13.241  SanFran
 12.123.25.245  St.Louis  12.122.125.224 Seattle   12.123.9.241   WashDC

IPv6:
 2001:1890:FF:FFFF:12:122:124:12   Atlanta
 2001:1890:FF:FFFF:12:122:127:66   Chicago
 2001:1890:FF:FFFF:12:122:124:138  Dallas
 2001:1890:FF:FFFF:12:122:120:7    Fort Lauderdale
 2001:1890:FF:FFFF:12:122:125:6    Los Angeles
 2001:1890:FF:FFFF:12:122:125:44   New York
 2001:1890:FF:FFFF:12:122:125:106  Philadelphia
 2001:1890:FF:FFFF:12:122:125:132  Phoenix
 2001:1890:FF:FFFF:12:122:126:232  San Francisco
 2001:1890:FF:FFFF:12:122:125:224  Seattle
 2001:1890:FF:FFFF:12:122:126:9    St. Louis
 2001:1890:FF:FFFF:12:122:126:64   Washington

*** Please Note:
Ping and traceroute delay figures measured here are unreliable, due to the
high CPU load experienced when complicated show commands are running.

For questions about this route-server, send email to: jayb@att.com

*** Log in with username 'rviews', password 'rviews' ***


route-server.ip.att.net (ttyp8)


The previous route-server, was god awfully slow and on a older cisco platform.

IIRC 7200/VXR


About route-servers:

We uses various  route-server (rs or rviews)  along with web looking-glasses ( lg ) to view our route and advertisements on the internet backbone from various  peers point or view or perspective.

To look a a bgp route (junos ) you can look  use a terse or full output;

show route protocol bgp 198.206.234.0/24 terse active-path

inet.0: 444837 destinations, 7117213 routes (444837 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

A V Destination        P Prf   Metric 1   Metric 2  Next hop        AS path
* ? 198.206.234.0/24   B 170        100                             7018 2914 25795 5706 I
  unverified                                       >12.0.1.1

rviews@route-server.ip.att.net>


We can also look at ipv6 advertisements on this same route-server,

e.g

rviews@route-server.ip.att.net> show route protocol bgp 2001:480:: terse

inet6.0: 12736 destinations, 165462 routes (12736 active, 0 holddown, 12 hidden)
+ = Active Route, - = Last Active, * = Both

A V Destination        P Prf   Metric 1   Metric 2  Next hop        AS path
* ? 2001:480::/32      B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31
  ?                    B 170        100                             7018 701 668 I
  unverified                                       >2001:1890:111d:111d:12:255:255:31



NOTE:  Junos unlike cisco-IOS/IOS-XR is smart enough to  understand ipv6 vrs v4 address and don't need any help on  the cmdline  or distinguisher. It's bi-lingual and understand either formated network address type.

Also a full detail output provide good information including the time that this "router" has installed the route into it's bgp table and via  a specific peer;

2001:480::/32 (13 entries, 1 announced)
        *BGP    Preference: 170/-101
                Next hop type: Indirect
                Address: 0x9eaa52c
                Next-hop reference count: 24916
                Source: 2001:1890:111d:111d:12:255:255:31
                Protocol next hop: 2001:1890:111d:111d:12:255:255:31
                Indirect next hop: 2 no-forward INH Session ID: 0x0
                State: <Active Ext>
                Local AS: 65000 Peer AS:  7018
                Age: 2w0d 19:26:15     Metric2: 0
                Validation State: unverified
                Task: BGP_7018.2001:1890:111d:111d:12:255:255:31+179
                Announcement bits (1): 3-Resolve tree 2
                AS path: 7018 701 668 I
                Communities: 7018:5000 7018:37232
                Accepted
                Localpref: 100
                Router ID: 12.0.1.63


and

rviews@route-server.ip.att.net> ping 2001:1890:111d:111d:12:255:255:31
PING6(56=40+8+8 bytes) 2001:1890:111d:111d:12:255:255:30 --> 2001:1890:111d:111d:12:255:255:31
16 bytes from 2001:1890:111d:111d:12:255:255:31, icmp_seq=0 hlim=64 time=1.348 ms
16 bytes from 2001:1890:111d:111d:12:255:255:31, icmp_seq=1 hlim=64 time=1.068 ms
16 bytes from 2001:1890:111d:111d:12:255:255:31, icmp_seq=2 hlim=64 time=1.131 ms
^C
--- 2001:1890:111d:111d:12:255:255:31 ping6 statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 1.068/1.182/1.348/0.120 ms

rviews@route-server.ip.att.net> traceroute 2001:1890:111d:111d:12:255:255:31
traceroute6 to 2001:1890:111d:111d:12:255:255:31 (2001:1890:111d:111d:12:255:255:31) from 2001:1890:111d:111d:12:255:255:30, 64 hops max, 12 byte packets
 1  2001:1890:111d:111d:12:255:255:31 (2001:1890:111d:111d:12:255:255:31)  1.528 ms  1.384 ms  1.134 ms

rviews@route-server.ip.att.net> 



keep in mind the following when using any looking-glass or route-server;


  • it 's best to get a view from various points on the geographical map
  • one  internet carrier might have you announcement and another does not
  • A problem could be local or geographical or carrier specfic
  • bgp communities could be over-ridden and drop
  • a carrier route-server typical peers only internal or as eBGP peer but to one router in that carrier ASN
  • their's no guarantee that a route-server is 100% available
  • they typically DO NOT carry traffic
  • they typically has a limit cmd and views ( role/view based access )
  • you may or may not be able to ping/traceroute from the  device ( not as restrictive on a lg btw )
  • route-server are typically built around cisco and juniper devices
  • a few are built around quagga(zebra)/bird/vyatta or other opensource routing platforms like the legacy GateD
  • almost all major tier 1 providers have a lg or rs available to the public


Here's some cool lg or rs links & information on these systems


https://labs.nic.cz/page/1304/ulg---universal-looking-glass/
http://routeserver.org/
http://www.merit.edu/research/
telnet://route-views.isc.routeviews.org
http://www.traceroute.org/


Ken Felix
Freelance Network/Security Engineer
kfelix  -at-    hyperfeed ---dot---- com

No comments:

Post a Comment