Is there anyone from Level 3 network that can explain why this particular router is responding to such high ping times. I cant seem to get any response from the Level 3 noc. The router seems to be in Chicago and a lot of east coast customers are complaining. [zaid@mrtg ~]$ ping 209.247.10.162 PING 209.247.10.162 (209.247.10.162): 56 data bytes 64 bytes from 209.247.10.162: icmp_seq=0 ttl=250 time=295.8 ms 64 bytes from 209.247.10.162: icmp_seq=1 ttl=250 time=498.7 ms 64 bytes from 209.247.10.162: icmp_seq=2 ttl=250 time=348.0 ms 64 bytes from 209.247.10.162: icmp_seq=3 ttl=250 time=498.7 ms 64 bytes from 209.247.10.162: icmp_seq=4 ttl=250 time=337.5 ms Webex-BR-HQ>tr 209.247.10.162 Type escape sequence to abort. Tracing the route to 209.247.10.162 1 WEBEX-HQ-L3.webex.com (64.68.96.150) 0 msec 4 msec 0 msec 2 209.247.202.113 4 msec 0 msec 4 msec 3 gigaethernet5-0.core2.SanJose1.Level3.net (209.244.13.45) [AS 3356] 4 msec 4 msec 0 msec 4 lo0.mp2.SanJose1.level3.net (209.247.8.240) [AS 3356] 4 msec 8 msec 4 msec 5 209.247.10.162 [AS 3356] 488 msec 388 msec * ------------------------------------------ Zaid Ali Network Architect WebEx 110 Rose Orchard Way San Jose, CA 95134 Tel: 408-435-7251 fax: 408-435-7004 www.webex.com ----------------------------------------
I'm experiencing a double whammy, from Abov->L3, since I seem to go through NYC. Usually I take their private peer back, maybe there are more cuts? bash-2.03$ traceroute 63.209.16.70 traceroute to 63.209.16.70 (63.209.16.70), 30 hops max, 40 byte packets 1 208.184.219.227 (208.184.219.227) 0.649 ms 0.451 ms 0.423 ms 2 208.184.169.main2.above.net (208.184.169.67) 0.337 ms 0.270 ms 9.343 ms 3 core3-main2.colo8-oc12.sjc2.above.net (208.184.102.233) 0.329 ms 0.343 ms 0.303 ms 4 core5.sjc2-core3.sjc2.above.net (208.185.156.66) 0.442 ms 0.365 ms 0.339 ms 5 nyc-sjc-oc12.nyc.above.net (208.185.156.162) 218.541 ms 219.857 ms 222.87 2 ms 6 posip2-1.core1.newyork1.level3.net (209.244.160.181) 226.828 ms 228.338 ms 229.893 ms 7 so-5-0-0.mp1.NewYork1.level3.net (209.247.10.33) 231.256 ms 241.142 ms 24 3.215 ms 8 209.247.11.14 (209.247.11.14) 235.393 ms 240.561 ms 242.571 ms 9 gigaethernet6-0.ipcolo2.SanJose1.Level3.net (209.244.13.46) 236.717 ms 235 .297 ms 240.763 ms 10 * * * bash-2.03$ ping 63.209.16.70 PING 63.209.16.70 (63.209.16.70): 56 data bytes 64 bytes from 63.209.16.70: icmp_seq=0 ttl=246 time=177.913 ms 64 bytes from 63.209.16.70: icmp_seq=1 ttl=246 time=173.035 ms 64 bytes from 63.209.16.70: icmp_seq=2 ttl=246 time=171.987 ms 64 bytes from 63.209.16.70: icmp_seq=3 ttl=246 time=189.229 ms -j -- /--------------------------/ Jason Legate \------------------------\ | jlegate@sitesmith.com | SiteSmith, Inc. | | 24x7 Call Center | http://www.sitesmith.com | | 888.898.7667 | PGP Key ID - 0xA855AAC3 | +---------------------------------+--------------------------------+ | Fingerprint - 2D5F 87A0 26E6 A65B 6837 D100 FB54 A972 A855 AAC3 | \------------------------------------------------------------------/
I'm experiencing a double whammy, from Abov->L3, since I seem to go through NYC. Usually I take their private peer back, maybe there are more cuts?
Abovenet told me they've been having core router problems. Haven't heard much squabble about it on the lists, so maybe it's just confined to our neck of the woods. It cleared up for us about 30 minutes ago.
On Tue, Jun 27, 2000 at 05:02:43PM -0700, Brian Kifiak wrote:
I'm experiencing a double whammy, from Abov->L3, since I seem to go through NYC. Usually I take their private peer back, maybe there are more cuts?
Abovenet told me they've been having core router problems. Haven't heard much squabble about it on the lists, so maybe it's just confined to our neck of the woods. It cleared up for us about 30 minutes ago.
I am a Level3 customer and I have noticed plenty of problems lately in the Bay Area, usual between San Francisco and San Jose. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073
[Level 3 hat on] I did respond privately but for other interested parties: The problem in the trace below is in SJO. Poor load sharing congested an uplink to a core router. Moved some traffic off congested link to gain some room. Times should have improved after that. After that there was a WAN link that was caught in that fiber cut yesterday that extended the issue for traffic heading out of SJO. thanks -cp
Is there anyone from Level 3 network that can explain why this particular router is responding to such high ping times. I cant seem to get any response from the Level 3 noc. The router seems to be in Chicago and a lot of east coast customers are complaining.
[zaid@mrtg ~]$ ping 209.247.10.162 PING 209.247.10.162 (209.247.10.162): 56 data bytes 64 bytes from 209.247.10.162: icmp_seq=0 ttl=250 time=295.8 ms 64 bytes from 209.247.10.162: icmp_seq=1 ttl=250 time=498.7 ms 64 bytes from 209.247.10.162: icmp_seq=2 ttl=250 time=348.0 ms 64 bytes from 209.247.10.162: icmp_seq=3 ttl=250 time=498.7 ms 64 bytes from 209.247.10.162: icmp_seq=4 ttl=250 time=337.5 ms
Webex-BR-HQ>tr 209.247.10.162
Type escape sequence to abort. Tracing the route to 209.247.10.162
1 WEBEX-HQ-L3.webex.com (64.68.96.150) 0 msec 4 msec 0 msec 2 209.247.202.113 4 msec 0 msec 4 msec 3 gigaethernet5-0.core2.SanJose1.Level3.net (209.244.13.45) [AS 3356] 4 msec 4 msec 0 msec 4 lo0.mp2.SanJose1.level3.net (209.247.8.240) [AS 3356] 4 msec 8 msec 4 msec 5 209.247.10.162 [AS 3356] 488 msec 388 msec *
------------------------------------------ Zaid Ali Network Architect WebEx 110 Rose Orchard Way San Jose, CA 95134 Tel: 408-435-7251 fax: 408-435-7004 www.webex.com ----------------------------------------
-- Craig Pierantozzi tozz@gweep.net
participants (5)
-
Brian Kifiak -
Jason Legate -
tozz＠sidehack.sat.gweep.net -
Ulf Zimmermann -
Zaid Ali