Anyone seeing issues with XO routing? /root# traceroute www.cisco.com traceroute to www.cisco.com (198.133.219.25), 30 hops max, 38 byte packets 1 132.237.9.3 (132.237.9.3) 3.510 ms 0.448 ms 0.443 ms 2 132.237.245.1 (132.237.245.1) 0.739 ms 0.791 ms 0.790 ms 3 67.104.110.113 (67.104.110.113) 1.826 ms 2.091 ms 1.860 ms 4 p4-3-0.MAR1.Fremont-CA.us.xo.net (207.88.80.9) 2.044 ms 2.088 ms 2.112 ms 5 p5-1-0-0.RAR1.SanJose-CA.us.xo.net (65.106.5.141) 2.438 ms 2.371 ms 2.368 ms 6 p1-0-0.RAR1.Washington-DC.us.xo.net (65.106.0.37) 82.448 ms 87.242 ms 82. 110 ms 7 p6-0-0.RAR2.NYC-NY.us.xo.net (65.106.0.1) 86.110 ms 86.055 ms 86.090 ms 8 ge5-0.dist1.hud-ny.us.xo.net (64.220.3.65) 86.688 ms 86.560 ms 86.586 ms 9 ge6-0.edge1.hud-ny.us.xo.net (64.220.3.83) 86.734 ms 86.715 ms 86.835 ms 10 * * * 11 * * agr1-loopback.NewYork.cw.net (206.24.194.101) 3100.552 ms 12 * * *
Before there is wild speculation since cw.net shows up in the path.... We are not experiencing any issues in DC or NY that would cause the problem below. I have dropped in traceroutes from the ingress to our network from XO to Cisco.com, and back to the first hop in the traceroute in Joe's traceroute to demonstrate that CW is forwarding packets as we are supposed to do. :-) If there are questions regarding routing issues within AS3561, noc@cw.net would be happy to investigate and respond. Regards, Mark Kasten Cable & Wireless autojuco@iar1.nyr> traceroute www.cisco.com traceroute to www.cisco.com (198.133.219.25), 30 hops max, 40 byte packets 1 agr2-loopback.NewYork.cw.net (206.24.194.102) 1.131 ms agr1-loopback.NewYork.cw.net (206.24.194.101) 1.077 ms 1.001 ms 2 dcr2-so-7-1-0.NewYork.cw.net (206.24.207.197) 0.789 ms 0.650 ms dcr2-so-6-0-0.NewYork.cw.net (206.24.207.177) 0.610 ms 3 agr4-so-4-0-0.NewYork.cw.net (206.24.207.78) 0.758 ms agr3-so-2-0-0.NewYork.cw.net (206.24.207.186) 0.671 ms 0.704 ms 4 acr1-loopback.NewYork.cw.net (206.24.194.61) 1.026 ms 1.039 ms 0.912 ms 5 206.24.195.202 (206.24.195.202) 0.843 ms 0.799 ms 0.814 ms 6 gbr2-p70.n54ny.ip.att.net (12.123.1.134) 1.037 ms 0.863 ms 0.852 ms 7 tbr1-p013301.n54ny.ip.att.net (12.122.11.5) 1.261 ms 3.661 ms 1.650 ms 8 tbr1-cl1.cgcil.ip.att.net (12.122.10.5) 68.805 ms 68.180 ms 68.625 ms 9 tbr1-p013302.sffca.ip.att.net (12.122.11.217) 68.233 ms 68.018 ms 67.755 ms 10 gbr5-p100.sffca.ip.att.net (12.122.11.74) 66.266 ms 66.326 ms 66.368 ms 11 gar1-p360.sj2ca.ip.att.net (12.122.2.253) 67.636 ms 67.600 ms 67.711 ms 12 12.127.200.82 (12.127.200.82) 67.434 ms 67.357 ms 67.478 ms 13 sjck-dirty-gw1.cisco.com (128.107.239.9) 66.229 ms 66.220 ms 66.134 ms 14 sjck-sdf-ciod-gw1.cisco.com (128.107.239.106) 67.582 ms 67.750 ms 67.504 ms ^C autojuco@iar1.nyr> ping www.cisco.com PING www.cisco.com (198.133.219.25): 56 data bytes 64 bytes from 198.133.219.25: icmp_seq=0 ttl=244 time=66.618 ms 64 bytes from 198.133.219.25: icmp_seq=1 ttl=244 time=66.287 ms autojuco@iar1.nyr> traceroute 132.237.9.3 traceroute to 132.237.9.3 (132.237.9.3), 30 hops max, 40 byte packets 1 agr1-loopback.NewYork.cw.net (206.24.194.101) 1.152 ms agr2-loopback.NewYork.cw.net (206.24.194.102) 1.081 ms 0.823 ms 2 dcr2-so-6-0-0.NewYork.cw.net (206.24.207.177) 9.728 ms dcr1-so-7-0-0.NewYork.cw.net (206.24.207.65) 0.797 ms dcr2-so-7-1-0.NewYork.cw.net (206.24.207.197) 0.803 ms 3 dcr1-loopback.Washington.cw.net (206.24.226.99) 4.954 ms dcr2-loopback.Washington.cw.net (206.24.226.100) 5.144 ms dcr1-loopback.Washington.cw.net (206.24.226.99) 4.943 ms 4 agr2-so-0-0-0.Washington.cw.net (206.24.238.54) 4.851 ms agr2-so-2-0-0.Washington.cw.net (206.24.238.182) 4.770 ms 4.692 ms 5 iar2-loopback.Washington.cw.net (206.24.226.13) 5.180 ms 5.167 ms 5.065 ms 6 xo-communication-telc-audit.Washington.cw.net (208.173.10.70) 5.402 ms 4.883 ms 5.632 ms 7 ge5-3-1.RAR1.Washington-DC.us.xo.net (64.220.0.222) 6.359 ms 6.010 ms 6.067 ms 8 p1-0-0.RAR1.SanJose-CA.us.xo.net (65.106.0.38) 78.736 ms 78.773 ms 79.209 ms 9 p4-0-0.MAR1.Fremont-CA.us.xo.net (65.106.5.142) 78.519 ms 78.741 ms 78.407 ms 10 p0-0.CHR1.Fremont-CA.us.xo.net (207.88.80.10) 79.890 ms 79.791 ms 80.193 ms 11 67.104.110.114 (67.104.110.114) 81.329 ms 82.717 ms 81.717 ms 12 * * * 13 * * * 14 * * * -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Joe Blanchard Sent: Wednesday, April 17, 2002 4:03 PM To: 'nanog@merit.edu' Subject: XO problems? Anyone seeing issues with XO routing? /root# traceroute www.cisco.com traceroute to www.cisco.com (198.133.219.25), 30 hops max, 38 byte packets 1 132.237.9.3 (132.237.9.3) 3.510 ms 0.448 ms 0.443 ms 2 132.237.245.1 (132.237.245.1) 0.739 ms 0.791 ms 0.790 ms 3 67.104.110.113 (67.104.110.113) 1.826 ms 2.091 ms 1.860 ms 4 p4-3-0.MAR1.Fremont-CA.us.xo.net (207.88.80.9) 2.044 ms 2.088 ms 2.112 ms 5 p5-1-0-0.RAR1.SanJose-CA.us.xo.net (65.106.5.141) 2.438 ms 2.371 ms 2.368 ms 6 p1-0-0.RAR1.Washington-DC.us.xo.net (65.106.0.37) 82.448 ms 87.242 ms 82. 110 ms 7 p6-0-0.RAR2.NYC-NY.us.xo.net (65.106.0.1) 86.110 ms 86.055 ms 86.090 ms 8 ge5-0.dist1.hud-ny.us.xo.net (64.220.3.65) 86.688 ms 86.560 ms 86.586 ms 9 ge6-0.edge1.hud-ny.us.xo.net (64.220.3.83) 86.734 ms 86.715 ms 86.835 ms 10 * * * 11 * * agr1-loopback.NewYork.cw.net (206.24.194.101) 3100.552 ms 12 * * *
That's what happens when you loose your core router group. ;) -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Mark Kasten Sent: Wednesday, April 17, 2002 2:02 PM To: Joe Blanchard; nanog@merit.edu Subject: RE: XO problems? Before there is wild speculation since cw.net shows up in the path.... We are not experiencing any issues in DC or NY that would cause the problem below. I have dropped in traceroutes from the ingress to our network from XO to Cisco.com, and back to the first hop in the traceroute in Joe's traceroute to demonstrate that CW is forwarding packets as we are supposed to do. :-) If there are questions regarding routing issues within AS3561, noc@cw.net would be happy to investigate and respond. Regards, Mark Kasten Cable & Wireless autojuco@iar1.nyr> traceroute www.cisco.com traceroute to www.cisco.com (198.133.219.25), 30 hops max, 40 byte packets 1 agr2-loopback.NewYork.cw.net (206.24.194.102) 1.131 ms agr1-loopback.NewYork.cw.net (206.24.194.101) 1.077 ms 1.001 ms 2 dcr2-so-7-1-0.NewYork.cw.net (206.24.207.197) 0.789 ms 0.650 ms dcr2-so-6-0-0.NewYork.cw.net (206.24.207.177) 0.610 ms 3 agr4-so-4-0-0.NewYork.cw.net (206.24.207.78) 0.758 ms agr3-so-2-0-0.NewYork.cw.net (206.24.207.186) 0.671 ms 0.704 ms 4 acr1-loopback.NewYork.cw.net (206.24.194.61) 1.026 ms 1.039 ms 0.912 ms 5 206.24.195.202 (206.24.195.202) 0.843 ms 0.799 ms 0.814 ms 6 gbr2-p70.n54ny.ip.att.net (12.123.1.134) 1.037 ms 0.863 ms 0.852 ms 7 tbr1-p013301.n54ny.ip.att.net (12.122.11.5) 1.261 ms 3.661 ms 1.650 ms 8 tbr1-cl1.cgcil.ip.att.net (12.122.10.5) 68.805 ms 68.180 ms 68.625 ms 9 tbr1-p013302.sffca.ip.att.net (12.122.11.217) 68.233 ms 68.018 ms 67.755 ms 10 gbr5-p100.sffca.ip.att.net (12.122.11.74) 66.266 ms 66.326 ms 66.368 ms 11 gar1-p360.sj2ca.ip.att.net (12.122.2.253) 67.636 ms 67.600 ms 67.711 ms 12 12.127.200.82 (12.127.200.82) 67.434 ms 67.357 ms 67.478 ms 13 sjck-dirty-gw1.cisco.com (128.107.239.9) 66.229 ms 66.220 ms 66.134 ms 14 sjck-sdf-ciod-gw1.cisco.com (128.107.239.106) 67.582 ms 67.750 ms 67.504 ms ^C autojuco@iar1.nyr> ping www.cisco.com PING www.cisco.com (198.133.219.25): 56 data bytes 64 bytes from 198.133.219.25: icmp_seq=0 ttl=244 time=66.618 ms 64 bytes from 198.133.219.25: icmp_seq=1 ttl=244 time=66.287 ms autojuco@iar1.nyr> traceroute 132.237.9.3 traceroute to 132.237.9.3 (132.237.9.3), 30 hops max, 40 byte packets 1 agr1-loopback.NewYork.cw.net (206.24.194.101) 1.152 ms agr2-loopback.NewYork.cw.net (206.24.194.102) 1.081 ms 0.823 ms 2 dcr2-so-6-0-0.NewYork.cw.net (206.24.207.177) 9.728 ms dcr1-so-7-0-0.NewYork.cw.net (206.24.207.65) 0.797 ms dcr2-so-7-1-0.NewYork.cw.net (206.24.207.197) 0.803 ms 3 dcr1-loopback.Washington.cw.net (206.24.226.99) 4.954 ms dcr2-loopback.Washington.cw.net (206.24.226.100) 5.144 ms dcr1-loopback.Washington.cw.net (206.24.226.99) 4.943 ms 4 agr2-so-0-0-0.Washington.cw.net (206.24.238.54) 4.851 ms agr2-so-2-0-0.Washington.cw.net (206.24.238.182) 4.770 ms 4.692 ms 5 iar2-loopback.Washington.cw.net (206.24.226.13) 5.180 ms 5.167 ms 5.065 ms 6 xo-communication-telc-audit.Washington.cw.net (208.173.10.70) 5.402 ms 4.883 ms 5.632 ms 7 ge5-3-1.RAR1.Washington-DC.us.xo.net (64.220.0.222) 6.359 ms 6.010 ms 6.067 ms 8 p1-0-0.RAR1.SanJose-CA.us.xo.net (65.106.0.38) 78.736 ms 78.773 ms 79.209 ms 9 p4-0-0.MAR1.Fremont-CA.us.xo.net (65.106.5.142) 78.519 ms 78.741 ms 78.407 ms 10 p0-0.CHR1.Fremont-CA.us.xo.net (207.88.80.10) 79.890 ms 79.791 ms 80.193 ms 11 67.104.110.114 (67.104.110.114) 81.329 ms 82.717 ms 81.717 ms 12 * * * 13 * * * 14 * * * -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Joe Blanchard Sent: Wednesday, April 17, 2002 4:03 PM To: 'nanog@merit.edu' Subject: XO problems? Anyone seeing issues with XO routing? /root# traceroute www.cisco.com traceroute to www.cisco.com (198.133.219.25), 30 hops max, 38 byte packets 1 132.237.9.3 (132.237.9.3) 3.510 ms 0.448 ms 0.443 ms 2 132.237.245.1 (132.237.245.1) 0.739 ms 0.791 ms 0.790 ms 3 67.104.110.113 (67.104.110.113) 1.826 ms 2.091 ms 1.860 ms 4 p4-3-0.MAR1.Fremont-CA.us.xo.net (207.88.80.9) 2.044 ms 2.088 ms 2.112 ms 5 p5-1-0-0.RAR1.SanJose-CA.us.xo.net (65.106.5.141) 2.438 ms 2.371 ms 2.368 ms 6 p1-0-0.RAR1.Washington-DC.us.xo.net (65.106.0.37) 82.448 ms 87.242 ms 82. 110 ms 7 p6-0-0.RAR2.NYC-NY.us.xo.net (65.106.0.1) 86.110 ms 86.055 ms 86.090 ms 8 ge5-0.dist1.hud-ny.us.xo.net (64.220.3.65) 86.688 ms 86.560 ms 86.586 ms 9 ge6-0.edge1.hud-ny.us.xo.net (64.220.3.83) 86.734 ms 86.715 ms 86.835 ms 10 * * * 11 * * agr1-loopback.NewYork.cw.net (206.24.194.101) 3100.552 ms 12 * * *
On 04/17/02, Joe Blanchard <jblanchard@wyse.com> wrote:
Anyone seeing issues with XO routing?
Yep, I was seeing 3000+ ms from SBC into XO earlier this afternoon. Seems to have cleared up now. -- J.D. Falk "say your peace" -- Scott Nelson <jdfalk@cybernothing.org> (probably a typo, but I like it)
On Wed, 17 Apr 2002, J.D. Falk wrote:
Anyone seeing issues with XO routing?
Yep, I was seeing 3000+ ms from SBC into XO earlier this afternoon. Seems to have cleared up now.
You that that is bad, try ordering a few hundred DS1s.
<> Nathan Stratton CTO, Exario Networks, Inc. nathan at robotics.net nathan at exario.net http://www.robotics.net http://www.exario.net
participants (6)
-
J.D. Falk -
Joe Blanchard -
Karyn Ulriksen -
Mark Kasten -
Nathan Stratton -
Rich Fulton