peer routing issue between SBC and SPRINT in DFW??
seems there is an issue with SPRINT and SBC out of DFW SBC NS's are unreachable... Sprint says there is no problem with their gw-39 router. SBC NOC/NRC refused to assist because we aren't their customer. SBC's customer (BN Railroad) hasn't had any luck thru the normal customer support channels seems to be a return path issue from the router pasted sl-gw39, which according to SPRINT is the SBC router.... sbcbackbone.net is unreachable as well anyone around from SBC with enable to check routing?? mucho thanks traceroute to 151.164.1.1 (151.164.1.1), 64 hops max, 40 byte packets 1 rt01 (216.223.236.225) 1.049 ms 0.992 ms 0.899 ms 2 as10480.fa0-0-0-v-2.co.rt01.ixnm.net (63.170.28.137) 1.237 ms 1.024 ms 0.898 ms 3 sl-gw37-fw-0-0-TS7.sprintlink.net (160.81.60.57) 19.983 ms 16.596 ms 16.625 ms 4 sl-bb22-fw-4-0.sprintlink.net (144.232.11.169) 30.996 ms 16.957 ms 16.749 ms 5 sl-bb26-fw-11-0.sprintlink.net (144.232.11.30) 17.068 ms 17.299 ms 18.230 ms 6 sl-gw39-fw-0-0.sprintlink.net (144.232.11.61) 17.254 ms 16.786 ms 17.967 ms 7 * * * 8 * * * 9 * * * 10 * * * traceroute to 170.49.49.66 (170.49.49.66), 64 hops max, 40 byte packets 1 rt01 (216.223.236.225) 1.049 ms 0.992 ms 0.899 ms 2 as10480.fa0-0-0-v-2.co.rt01.ixnm.net (63.170.28.137) 1.237 ms 1.024 ms 0.898 ms 3 sl-gw37-fw-0-0-TS7.sprintlink.net (160.81.60.57) 19.983 ms 16.596 ms 16.625 ms 4 sl-bb22-fw-4-0.sprintlink.net (144.232.11.169) 30.996 ms 16.957 ms 16.749 ms 5 sl-bb26-fw-11-0.sprintlink.net (144.232.11.30) 17.068 ms 17.299 ms 18.230 ms 6 sl-gw39-fw-0-0.sprintlink.net (144.232.11.61) 17.254 ms 16.786 ms 17.967 ms 7 * * * 8 * * * 9 * * * 10 * * *
Thanks to Tom S at SBC for fixing the issue... john brown On Wed, Nov 26, 2003 at 03:50:17PM -0700, John Brown (CV) wrote:
seems there is an issue with SPRINT and SBC out of DFW
SBC NS's are unreachable...
Sprint says there is no problem with their gw-39 router.
SBC NOC/NRC refused to assist because we aren't their customer. SBC's customer (BN Railroad) hasn't had any luck thru the normal customer support channels
seems to be a return path issue from the router pasted sl-gw39, which according to SPRINT is the SBC router....
sbcbackbone.net is unreachable as well
anyone around from SBC with enable to check routing??
mucho thanks
traceroute to 151.164.1.1 (151.164.1.1), 64 hops max, 40 byte packets 1 rt01 (216.223.236.225) 1.049 ms 0.992 ms 0.899 ms 2 as10480.fa0-0-0-v-2.co.rt01.ixnm.net (63.170.28.137) 1.237 ms 1.024 ms 0.898 ms 3 sl-gw37-fw-0-0-TS7.sprintlink.net (160.81.60.57) 19.983 ms 16.596 ms 16.625 ms 4 sl-bb22-fw-4-0.sprintlink.net (144.232.11.169) 30.996 ms 16.957 ms 16.749 ms 5 sl-bb26-fw-11-0.sprintlink.net (144.232.11.30) 17.068 ms 17.299 ms 18.230 ms 6 sl-gw39-fw-0-0.sprintlink.net (144.232.11.61) 17.254 ms 16.786 ms 17.967 ms 7 * * * 8 * * * 9 * * * 10 * * *
traceroute to 170.49.49.66 (170.49.49.66), 64 hops max, 40 byte packets 1 rt01 (216.223.236.225) 1.049 ms 0.992 ms 0.899 ms 2 as10480.fa0-0-0-v-2.co.rt01.ixnm.net (63.170.28.137) 1.237 ms 1.024 ms 0.898 ms 3 sl-gw37-fw-0-0-TS7.sprintlink.net (160.81.60.57) 19.983 ms 16.596 ms 16.625 ms 4 sl-bb22-fw-4-0.sprintlink.net (144.232.11.169) 30.996 ms 16.957 ms 16.749 ms 5 sl-bb26-fw-11-0.sprintlink.net (144.232.11.30) 17.068 ms 17.299 ms 18.230 ms 6 sl-gw39-fw-0-0.sprintlink.net (144.232.11.61) 17.254 ms 16.786 ms 17.967 ms 7 * * * 8 * * * 9 * * * 10 * * *
Hi John, I just chatted with someone in the SBCIS NRC and discovered the situation has been resolved. There was a loop in Dallas and they did escalate properly & resolved it within an hour of notification. Not bad for 6 pm on the eve of a national holiday <G> BTW, http://www.sbcbackbone.net is working, confirmed from three other peer networks. Enjoy your turkey day tomorrow! Cheers, -ren At 03:50 PM 11/26/2003 -0700, John Brown (CV) wrote:
seems there is an issue with SPRINT and SBC out of DFW
SBC NS's are unreachable...
Sprint says there is no problem with their gw-39 router.
SBC NOC/NRC refused to assist because we aren't their customer. SBC's customer (BN Railroad) hasn't had any luck thru the normal customer support channels
seems to be a return path issue from the router pasted sl-gw39, which according to SPRINT is the SBC router....
sbcbackbone.net is unreachable as well
anyone around from SBC with enable to check routing??
mucho thanks
traceroute to 151.164.1.1 (151.164.1.1), 64 hops max, 40 byte packets 1 rt01 (216.223.236.225) 1.049 ms 0.992 ms 0.899 ms 2 as10480.fa0-0-0-v-2.co.rt01.ixnm.net (63.170.28.137) 1.237 ms 1.024 ms 0.898 ms 3 sl-gw37-fw-0-0-TS7.sprintlink.net (160.81.60.57) 19.983 ms 16.596 ms 16.625 ms 4 sl-bb22-fw-4-0.sprintlink.net (144.232.11.169) 30.996 ms 16.957 ms 16.749 ms 5 sl-bb26-fw-11-0.sprintlink.net (144.232.11.30) 17.068 ms 17.299 ms 18.230 ms 6 sl-gw39-fw-0-0.sprintlink.net (144.232.11.61) 17.254 ms 16.786 ms 17.967 ms 7 * * * 8 * * * 9 * * * 10 * * *
traceroute to 170.49.49.66 (170.49.49.66), 64 hops max, 40 byte packets 1 rt01 (216.223.236.225) 1.049 ms 0.992 ms 0.899 ms 2 as10480.fa0-0-0-v-2.co.rt01.ixnm.net (63.170.28.137) 1.237 ms 1.024 ms 0.898 ms 3 sl-gw37-fw-0-0-TS7.sprintlink.net (160.81.60.57) 19.983 ms 16.596 ms 16.625 ms 4 sl-bb22-fw-4-0.sprintlink.net (144.232.11.169) 30.996 ms 16.957 ms 16.749 ms 5 sl-bb26-fw-11-0.sprintlink.net (144.232.11.30) 17.068 ms 17.299 ms 18.230 ms 6 sl-gw39-fw-0-0.sprintlink.net (144.232.11.61) 17.254 ms 16.786 ms 17.967 ms 7 * * * 8 * * * 9 * * * 10 * * *
participants (2)
-
John Brown (CV) -
ren