Is anyone aware of Verizon having any routing issues at this time? 13 20 ms 20 ms 20 ms A9-0-632.G-GSR1.MAD.verizon-gni.net [130.81.5.94] 14 20 ms 20 ms 20 ms P3-1-0.G-RTR1.MAD.verizon-gni.net [141.150.0.102] 15 24 ms 24 ms 24 ms 141.150.8.210 16 28 ms 23 ms 23 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 17 34 ms 27 ms 27 ms 141.150.8.210 18 26 ms 27 ms 26 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 19 30 ms 30 ms 30 ms 141.150.8.210 20 30 ms 30 ms 30 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 21 34 ms 33 ms 34 ms 141.150.8.210 22 33 ms 33 ms 33 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] -- Darrell Carley National Data Centers Network Engineer
Here is the trace in full... Tracing the route to IP node 141.150.60.158 from 1 to 30 hops 1 <1 ms <1 ms <1 ms 205.198.2.133 2 <1 ms <1 ms <1 ms ge6-1.atluna.ar.unaatlga.aleron.net [205.198.2.41] 3 13 ms 12 ms 12 ms atm0-0-0-13.asheqx.dcwdcrr02.eqxashva.aleron.net [205.198.0.74] 4 12 ms 12 ms 13 ms 205.198.1.54 5 14 ms 14 ms 14 ms wash02-core01.dc.inet.qwest.net [205.171.209.45] 6 14 ms 14 ms 14 ms wash02-core03.dc.inet.qwest.net [205.171.9.10] 7 14 ms 14 ms 14 ms wash02-edge03.dc.inet.qwest.net [205.171.9.94] 8 17 ms 17 ms 17 ms 65.118.218.46 9 17 ms 17 ms 17 ms so-0-1-0-0.BB-RTR2.PHIL.verizon-gni.net [130.81.7.237] 10 19 ms 19 ms 19 ms so-0-3-0-0.BB-RTR1.NWRK.verizon-gni.net [130.81.7.145] 11 19 ms 19 ms 19 ms so-0-0-0-0.BB-RTR2.NWRK.verizon-gni.net [130.81.7.142] 12 20 ms 20 ms 20 ms so-0-0-0-0.CORE-RTR2.MAD.verizon-gni.net [130.81.7.194] 13 20 ms 20 ms 20 ms A9-0-632.G-GSR1.MAD.verizon-gni.net [130.81.5.94] 14 20 ms 20 ms 20 ms P3-1-0.G-RTR1.MAD.verizon-gni.net [141.150.0.102] 15 24 ms 24 ms 24 ms 141.150.8.210 16 24 ms 23 ms 23 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 17 27 ms 28 ms 27 ms 141.150.8.210 18 27 ms 26 ms 27 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 19 30 ms 30 ms 30 ms 141.150.8.210 20 30 ms 30 ms 30 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 21 34 ms 34 ms 33 ms 141.150.8.210 22 33 ms 33 ms 33 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 23 37 ms 37 ms 37 ms 141.150.8.210 24 37 ms 36 ms 36 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 25 41 ms 40 ms 40 ms 141.150.8.210 26 40 ms 39 ms 39 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 27 43 ms 50 ms 43 ms 141.150.8.210 28 43 ms 43 ms 43 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 29 47 ms 47 ms 47 ms 141.150.8.210 30 46 ms 46 ms 46 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209 Trace Route Failed, no response from target node. thx, Darrell On Monday 05 August 2002 12:28, Mark Kent wrote:
Is anyone aware of Verizon having any routing issues at this time?
Yes, I just saw a traceroute on nanog that, even though it didn't include a source or destination IP address, firmly convinced me that Verizon was having problems.
-mark
Hi Darrell, What the others are trying to convey through sarcasm is that this behavior is a garden-variety issue which is very localized (ie. likely only affects the one destination prefix you're trying to reach or a small set). Moreover, it's not necessarily something that is amiss in Verizon's network; it may well be within a network which is downstream from them. The proper approach is to work with your directly upstream provider· (seemingly Aleron) to diagnose the problem and get in touch with the other ISPs in the path until the situation is definitively identified and hopefully resolved. Posting to NANOG is definitely not the right thing in this case; hence the sarcasm and chiding. Hope this info has been helpful. Tony On Mon, 5 Aug 2002, Darrell Carley wrote:
Here is the trace in full...
Tracing the route to IP node 141.150.60.158 from 1 to 30 hops
1 <1 ms <1 ms <1 ms 205.198.2.133 2 <1 ms <1 ms <1 ms ge6-1.atluna.ar.unaatlga.aleron.net [205.198.2.41] 3 13 ms 12 ms 12 ms atm0-0-0-13.asheqx.dcwdcrr02.eqxashva.aleron.net [205.198.0.74] 4 12 ms 12 ms 13 ms 205.198.1.54 5 14 ms 14 ms 14 ms wash02-core01.dc.inet.qwest.net [205.171.209.45]
6 14 ms 14 ms 14 ms wash02-core03.dc.inet.qwest.net [205.171.9.10] 7 14 ms 14 ms 14 ms wash02-edge03.dc.inet.qwest.net [205.171.9.94] 8 17 ms 17 ms 17 ms 65.118.218.46 9 17 ms 17 ms 17 ms so-0-1-0-0.BB-RTR2.PHIL.verizon-gni.net [130.81.7.237] 10 19 ms 19 ms 19 ms so-0-3-0-0.BB-RTR1.NWRK.verizon-gni.net [130.81.7.145] 11 19 ms 19 ms 19 ms so-0-0-0-0.BB-RTR2.NWRK.verizon-gni.net [130.81.7.142] 12 20 ms 20 ms 20 ms so-0-0-0-0.CORE-RTR2.MAD.verizon-gni.net [130.81.7.194] 13 20 ms 20 ms 20 ms A9-0-632.G-GSR1.MAD.verizon-gni.net [130.81.5.94] 14 20 ms 20 ms 20 ms P3-1-0.G-RTR1.MAD.verizon-gni.net [141.150.0.102] 15 24 ms 24 ms 24 ms 141.150.8.210 16 24 ms 23 ms 23 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 17 27 ms 28 ms 27 ms 141.150.8.210 18 27 ms 26 ms 27 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 19 30 ms 30 ms 30 ms 141.150.8.210 20 30 ms 30 ms 30 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 21 34 ms 34 ms 33 ms 141.150.8.210 22 33 ms 33 ms 33 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 23 37 ms 37 ms 37 ms 141.150.8.210 24 37 ms 36 ms 36 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 25 41 ms 40 ms 40 ms 141.150.8.210 26 40 ms 39 ms 39 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 27 43 ms 50 ms 43 ms 141.150.8.210 28 43 ms 43 ms 43 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209] 29 47 ms 47 ms 47 ms 141.150.8.210 30 46 ms 46 ms 46 ms S9-0-0-17.G-RTR1.MAD.verizon-gni.net [141.150.8.209
Trace Route Failed, no response from target node.
thx, Darrell
On Monday 05 August 2002 12:28, Mark Kent wrote:
Is anyone aware of Verizon having any routing issues at this time?
Yes, I just saw a traceroute on nanog that, even though it didn't include a source or destination IP address, firmly convinced me that Verizon was having problems.
-mark
On Mon, Aug 05, 2002 at 09:28:06AM -0700, Mark Kent wrote:
Is anyone aware of Verizon having any routing issues at this time?
Yes, I just saw a traceroute on nanog that, even though it didn't include a source or destination IP address, firmly convinced me that Verizon was having problems.
You don't consider the routing loop it contained to be a problem? :) There is a fine art to being bitchy on nanog, and the first rule is "make certain you are right" (for good examples, read Randy Bush posts). Now if you had simply pointed out that noone cares about verizon's routing loop for his T1, that would have been different. :) -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)
You mean beside them having a DS3 feeding Covad down for SIXTY (60) hours? First, they claimed to lack parts. Then the last 18 hours were because they left it in loopback & walked away. Other than that, all is cosy! -- A host is a host from coast to coast.................wb8foz@nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433
participants (5)
-
Darrell Carley -
David Lesher -
Mark Kent -
Richard A Steenbergen -
Tony Tauber