[27886] in North American Network Operators' Group
Re: Sprint routing issues
daemon@ATHENA.MIT.EDU (Phil Howard)
Thu Mar 23 04:29:50 2000
Message-ID: <20000323092729.14232.qmail@networklight.net>
From: "Phil Howard" <phil-nanog@ipal.net>
To: jlewis@lewis.org
Date: Thu, 23 Mar 2000 03:27:29 -0600 (CST)
Cc: nanog@nanog.org
In-Reply-To: <Pine.LNX.4.10.10003230034100.25904-100000@redhat1.mmaero.com> from "jlewis@lewis.org" at Mar 23, 2000 12:40:45 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
jlewis@lewis.org wrote:
> On Thu, 23 Mar 2000, Nick Bastin wrote:
>
> > >I can ping all of them, but none answer DNS queries. Makes it tough to
> > >access their customers.
> >
> > Sprint has a master ticket #3461302 open for at least something related to
> > this problem, or at least that's what the engineer thought. Apparently
> > they're having an 'issue' with a router on the east coast. He muttered
> > something about gateway 13, but I didn't catch it all.
>
> I just got another call back to tell me that they'd isolated the problem
> to the Orlando, FL site where we connect to them. I said "I don't think
> so." All their NS servers are unreachable or unresponsive (to the whole
> net, not just me), and they think it's a bad circuit in Orlando? It seems
> almost like the two callbacks I've gotten so far are from different parts
> of Sprint. Neither seems to know what the other is doing. Neither seems
> to know what's going on in general. At least the first one knew there was
> some general "big problem" on their network. Both are acting on the same
> ticket opened by a single phone call from me.
>
> ----------------------------------------------------------------------
> Jon Lewis *jlewis@lewis.org*| Spammers will be winnuked or
> System Administrator | nestea'd...whatever it takes
> Atlantic Net | to get the job done.
> _________http://www.lewis.org/~jlewis/pgp for PGP public key__________
I'm on CW.NET and I am seeing routing that doesn't make much sense to
me. Things vary by host within a class C and by source address. I can
reach some addresses within a class C but not others, and that varies
by the source address I am using.
tracing FROM 208.152.116.17 TO 209.207.224.196:
traceroute to 209.207.224.196 (209.207.224.196), 30 hops max, 40 byte packets
1 208-128-66-16.ipv4.intur.net (208.128.66.16) 169.363 ms 157.531 ms 174.376 ms
2 208-128-66-2.ipv4.intur.net (208.128.66.2) 177.345 ms 149.884 ms 139.444 ms
3 208-152-121-1.ipv4.intur.net (208.152.121.1) 170.996 ms 149.054 ms 159.872 ms
4 bar2-serial4-0-0-15-0.Chicagochd.cw.net (208.172.8.145) 189.807 ms 189.665 ms 179.858 ms
5 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 179.738 ms 209.73 ms 189.853 ms
6 corerouter2.WillowSprings.cw.net (204.70.9.146) 179.814 ms 191.996 ms 207.478 ms
7 core4.WillowSprings.cw.net (204.70.4.73) 189.864 ms 189.573 ms 189.914 ms
8 cw-ip-eng-interconnects.WillowSprings.cw.net (206.157.77.94) 189.819 ms 179.604 ms 182.714 ms
9 sl-bb11-chi-2-1.sprintlink.net (144.232.10.157) 176.883 ms 199.484 ms 169.924 ms
10 sl-bb11-atl-4-0.sprintlink.net (144.232.18.34) 209.803 ms 219.697 ms 209.885 ms
11 sl-bb10-atl-9-0.sprintlink.net (144.232.12.17) 209.813 ms 220.153 ms 209.832 ms
12 sl-bb11-rly-5-0.sprintlink.net (144.232.9.197) 209.502 ms 226.099 ms 229.827 ms
13 sl-bb5-dc-4-0-0.sprintlink.net (144.232.7.166) 219.826 ms 199.655 ms 210.105 ms
14 208.28.7.19 (208.28.7.19) 209.79 ms 199.643 ms 209.726 ms
15 sl-csg-1-0-0-T3.sprintlink.net (144.228.108.94) 229.768 ms 209.828 ms 209.876 ms
16 ns1.andover.net (209.207.224.196) 219.811 ms 229.701 ms 209.731 ms
tracing FROM 206.97.151.201 TO 209.207.224.196:
traceroute to 209.207.224.196 (209.207.224.196), 30 hops max, 40 byte packets
1 eth-1.cisco-1.intur.net (206.97.149.1) 2.084 ms 2.077 ms 2.167 ms
2 unassigned-private-host.in.30.172.in-addr.arpa (172.30.1.2) 3.575 ms 3.480 ms 3.458 ms
3 bar2-serial4-0-0-15-0.Chicagochd.cw.net (208.172.8.145) 27.515 ms 27.499 ms 27.570 ms
4 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 28.523 ms 28.057 ms 27.915 ms
5 corerouter2.WillowSprings.cw.net (204.70.9.146) 29.202 ms 28.836 ms 32.201 ms
6 core4.WillowSprings.cw.net (204.70.4.73) 30.887 ms 52.848 ms 29.607 ms
7 sl-chi-15-H1-0-T3.sprintlink.net (206.157.77.90) 30.392 ms 30.746 ms 30.570 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
Things are good up to core4.WillowSprings.cw.net, then there is a diversion.
Both of these netblocks are assignments from CW.NET.
It gets better:
Coming from the same IP that failed above, I now go to a different IP on the
same class C and I get:
tracing FROM 206.97.151.201 TO 209.207.224.41:
traceroute to 209.207.224.41 (209.207.224.41), 30 hops max, 40 byte packets
1 eth-1.cisco-1.intur.net (206.97.149.1) 2.152 ms 2.028 ms 2.233 ms
2 unassigned-private-host.in.30.172.in-addr.arpa (172.30.1.2) 3.576 ms 3.520 ms 3.494 ms
3 bar2-serial4-0-0-15-0.Chicagochd.cw.net (208.172.8.145) 27.679 ms 27.531 ms 27.587 ms
4 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 28.065 ms 27.903 ms 27.850 ms
5 corerouter2.WillowSprings.cw.net (204.70.9.146) 30.053 ms 29.332 ms 28.926 ms
6 core4.WillowSprings.cw.net (204.70.4.73) 29.677 ms 29.752 ms 29.616 ms
7 cw-ip-eng-interconnects.WillowSprings.cw.net (206.157.77.94) 42.546 ms 30.327 ms 30.951 ms
8 sl-bb11-chi-2-1.sprintlink.net (144.232.10.157) 30.390 ms 30.738 ms 30.397 ms
9 sl-bb11-atl-4-0.sprintlink.net (144.232.18.34) 55.761 ms 56.279 ms 55.871 ms
10 sl-bb10-atl-9-0.sprintlink.net (144.232.12.17) 55.918 ms 55.478 ms 56.495 ms
11 sl-bb11-rly-5-0.sprintlink.net (144.232.9.197) 66.480 ms 55.877 ms 58.161 ms
12 sl-bb5-dc-4-0-0.sprintlink.net (144.232.7.166) 56.151 ms 56.744 ms 56.812 ms
13 208.28.7.19 (208.28.7.19) 57.426 ms 56.306 ms 56.442 ms
14 sl-csg-1-0-0-T3.sprintlink.net (144.228.108.94) 56.827 ms 56.669 ms 58.161 ms
15 209.207.224.41 (209.207.224.41) 57.308 ms 57.681 ms 56.898 ms
And going there from the first source gets there, but by a slightly
different path right after core4.WillowSprings.cw.net.
tracing FROM 208.152.116.17 TO 209.207.224.41:
traceroute to 209.207.224.41 (209.207.224.41), 30 hops max, 40 byte packets
1 208-128-66-16.ipv4.intur.net (208.128.66.16) 155.435 ms 172.896 ms 139.777 ms
2 208-128-66-2.ipv4.intur.net (208.128.66.2) 159.756 ms 139.701 ms 150.207 ms
3 208-152-121-1.ipv4.intur.net (208.152.121.1) 159.643 ms 169.688 ms 169.905 ms
4 bar2-serial4-0-0-15-0.Chicagochd.cw.net (208.172.8.145) 179.529 ms 189.557 ms 179.911 ms
5 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 179.747 ms 189.858 ms 179.737 ms
6 corerouter2.WillowSprings.cw.net (204.70.9.146) 179.79 ms 189.628 ms 180.291 ms
7 core4.WillowSprings.cw.net (204.70.4.73) 189.295 ms 199.571 ms 199.833 ms
8 sl-chi-15-H1-0-T3.sprintlink.net (206.157.77.90) 189.768 ms 189.707 ms 179.852 ms
9 sl-bb11-chi-2-1.sprintlink.net (144.232.10.157) 180.013 ms 189.535 ms 179.877 ms
10 sl-bb11-atl-4-0.sprintlink.net (144.232.18.34) 209.77 ms 223.68 ms 206.015 ms
11 sl-bb10-atl-9-0.sprintlink.net (144.232.12.17) 209.726 ms 229.484 ms 209.799 ms
12 sl-bb11-rly-5-0.sprintlink.net (144.232.9.197) 209.806 ms 208.054 ms 199.559 ms
13 sl-bb5-dc-4-0-0.sprintlink.net (144.232.7.166) 250.126 ms 209.53 ms 219.904 ms
14 208.28.7.19 (208.28.7.19) 229.756 ms 229.641 ms 209.916 ms
15 sl-csg-1-0-0-T3.sprintlink.net (144.228.108.94) 269.96 ms 219.565 ms 229.851 ms
16 209.207.224.41 (209.207.224.41) 219.807 ms 237.806 ms 231.999 ms
Is Sprint advertising routes smaller than /24?
Has Sprint caused the route table in core4.WillowSprings.cw.net to be goofed?
--
| Phil Howard - KA9WGN | My current boycotts: Amazon.Com, any DVD, Mattel
| phil-nospam@ipal.net +--------------------------------------------------
| Dallas - Texas - USA | My current websites: linuxhomepage.com, ham.org
