eceived paths for inbound soft reconfiguration BGP activity 191898/218 prefixes, 3666117/24554 paths, scan interval 60 secs Neighbor AS MsgRcvd MsgSent TblVer InO Outo Up/Down State/PfxRcd 10.0.0.2 0 never Idle (Admin) 12.0.1.63 45038 208637 0 03:04:16 12.123.1.236 39405 208637 0 03:05:02 191504 12.123.5.240 39735 208637 0 03:05:04 191504 12.123.9.241 39343 208637 0 03:05:03 191528 12.123.13.241 39617 208637 0 03:04:20 191529 12.123.17.244 39747 208637 0 03:04:58 191505 12.123.21.243 39441 208637 0 03:04:28 191528 12.123.25.245 39789 208637 0 03:05:07 191504 Chapter 10: Routing Protocols 12.123.29.249 39602 208637 0 03:04:16 191505 12.123.33.249 39541 208637 0 03:04:16 191528 12.123.37.250 39699 208637 0 03:04:26 191529 12.123.41.250 39463 208637 0 03:04:19 191529 12.123.45.252 39386 208637 0 03:04:20 191505 12.123.133.124 39720 208637 0 03:04:20 191528 12.123.134.124 39729 208637 0 03:04:22 191529 12.123.137.124 39480 208637 0 03:04:15 191528 12.123.139.124 39807 208637 0 03:04:24 191528 12.123.142.124 39748 208637 0 03:04:22 191505 12.123.145.124 39655 208637 0 03:04:23 191529 These route servers can get pretty busy and very slow. If you find your- self waiting too long for a response to a query, either wait a bit and try again, or try another route server. Choose your favorite public IP network (doesn't everyone have one?) and see how the paths look from the looking-glass router. If you don't have a favorite, choose one that you can easily figure out, like one in use by www.cisco.com or www.oreilly.com: [bossman@myserver bossman]$ nslookup www.oreilly.com Server: localhost Address: 127.0.0.1 Name: www.oreilly.com Addresses: 208.201.239.36, 208.201.239.37 Once you have the address, you can do a lookup for the network: route-server> sho ip bgp 208.201.239.0 BGP routing table entry for 208.201.224.0/19, version 157337 Paths: (19 available, best #15, table Default-IP-Routing-Table) Not advertised to any peer 7018 701 7065, (received & used) 12.123.137.124 from 12.123.137.124 (12.123.137.124) Origin IGP, localpref 