From: (no name) (no email)
Date: Wed Jun 28 2000 - 12:04:23 EDT
[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 at 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
|
|
|