3ffe:2a00::/24 routing loop?
Trond Skjesol
Trond.Skjesol@uninett.no
Wed, 14 Jul 1999 09:46:56 +0200
During this period we had some routing problems with the routing into US, the
problem was somewhere at Teleglobe. I guess thats why the 6bone routing also
failed.
-Trond
staff@nordu.net said:
> Ticket Number : NORDUnet/19990713-00 Ticket Status : OPEN, UPDATED
> Ticket Type : Unscheduled Ticket Source : KTHNOC
> Site/Line : Most US sites unreachable
> Ticket Scope : Routing Ticket Priority : Normal
> Ticket Owner : KTHNOC Ticket Issuer : nnc@sunet.se
> Problem Fixer : N/A Time to Fix : N/A
> Ticket Opened : 19990713 19:13 UTC Problem Starts : 19990713 17:20 UTC ?
> Closed : Ended : 19990713 20:20 UTC ?
> Problem Description:
> Loss of routing to most US.
> Affected:
> All NORDUNet traffic to/from US
> Action:
> Contated Teleglobe (by fax!)
> Fix:
> Teleglobe (Mia) confirmed reception of fax at 19.20,
> handing the case to techn. staff.
> -----
> 990713 20:50 Update by nnc@sunet.se
> At 20:35 (UTC) Teleglobe called and told allocation
> of Ticken-# 81844. Problem escalated to 1:st level
> support for investignation.
> GÅ told them that the problem is currently not there.
> (since some 10-15 min.) They will continue to
> investignate, and inform by E-Mail.
> Now the loop is:
>
> tracert6 -d 3ffe:dfe:fffe::9
>
> Tracing route to 3ffe:dfe:fffe::9
> over a maximum of 30 hops:
>
> 1 1 ms <1 ms 1 ms 3ffe:2a00:100:7031::1
> 2 3 ms 3 ms 3 ms 3ffe:2a00:100:7ffd::1
> 3 20 ms 19 ms 23 ms 3ffe:200:1:b::1
> 4 82 ms 69 ms 69 ms 3ffe:1d00:2:4::1
> 5 75 ms 68 ms * 3ffe:200:1:2::2
> 6 105 ms 226 ms 163 ms 3ffe:1d00:2:4::1
> 7 199 ms 112 ms 122 ms 3ffe:200:1:2::2
> 8 167 ms 157 ms 188 ms 3ffe:1d00:2:4::1
> 9 171 ms 187 ms 196 ms 3ffe:200:1:2::2
> 10 ^C
>
> > -----Original Message-----
> > From: Richard Draves
> > Sent: Tuesday, July 13, 1999 8:33 AM
> > To: 'jane@ifi.uio.no'
> > Cc: '6bone'
> > Subject: 3ffe:2a00::/24 routing loop?
> >
> > It looks like there's a routing loop in the 3ffe:2a00::/24
> > pTLA... see below.
> > I'm running in the IETF terminal room.
> >
> > Thanks,
> > Rich
> >
> > tracert6 -d 3ffe:dfe:fffe::9
> >
> > Tracing route to 3ffe:dfe:fffe::9
> > over a maximum of 30 hops:
> >
> > 1 1 ms <1 ms <1 ms 3ffe:2a00:100:7031::1
> > 2 3 ms 3 ms 3 ms 3ffe:2a00:100:7ffd::1
> > 3 177 ms 177 ms 182 ms 3ffe:2a00:100:7ffc::2
> > 4 183 ms 182 ms 181 ms 3ffe:2a00:100:7ffd::1
> > 5 356 ms 355 ms 349 ms 3ffe:2a00:100:7ffc::2
> > 6 358 ms 349 ms 355 ms 3ffe:2a00:100:7ffd::1
> > 7 542 ms 544 ms ^C