[AusNOG] Telstra --> Pacific hand over problem? RESOLVED (again)
Don Gould
don at bowenvale.co.nz
Sat May 28 12:06:57 EST 2011
Brett,
Ok, seems to be bent back into shape again. :)
Is it looking better for you as well now?
D
1.
router
0.0% 6 0.2 0.2 0.2 0.2 0.0
2. ???
3.
lo0.internet.ivpn.pe22.telstraclear.net
0.0% 6 13.2 14.9 9.2 21.3 4.9
4. ???
5.
ie1-g-0-0-0.telstraclear.net
0.0% 6 24.8 24.5 23.5 25.5 0.8
6.
ge-0-2-0-1.xcore1.acld.telstraclear.net
0.0% 6 22.0 28.6 22.0 50.0 11.0
7.
203.167.233.10
0.0% 6 24.5 24.6 22.3 25.6 1.3
8.
i-3-1-0.syd-core03.bx.reach.com
0.0% 6 50.4 48.9 46.5 50.8 2.0
9.
i-0-5-4-0.sydp-core05.bx.reach.com
0.0% 6 50.6 48.9 48.0 50.6 1.0
10.
i-11-0-0.sydp-core01.bi.reach.com
0.0% 6 48.6 48.5 47.5 49.2 0.7
11.
telstra_domestic_peer-peer.sydp-core01.pr.reach.com
0.0% 6 64.2 54.7 51.6 64.2 4.7
12.
bundle-ether3.chw-core2.sydney.telstra.net
0.0% 6 51.4 50.9 48.2 52.6 1.7
13.
tengigabitethernet7-1.ult1.sydney.telstra.net
0.0% 5 49.2 50.3 49.2 51.2 0.8
14.
pacifi121.lnk.telstra.net
0.0% 5 51.2 50.4 48.5 53.4 2.0
15.
vl63.switch1.syd.pacific.net.au
0.0% 5 200.1 154.2 51.3 235.0 76.2
16.
bvi11-0.cr-rtr01.ult.bulletproof.net
0.0% 5 50.4 53.0 50.4 55.9 2.5
17.
171-171-53-117.rev.bulletproof.net
0.0% 5 48.7 50.0 48.7 52.2 1.4
--> 15.
vl63.switch1.syd.pacific.net.au
0.0% 5 200.1 154.2 51.3 235.0 76.2
That hop is often a bit bent out of shape. I have commented to Telstra
about it, but got no comment back.
Tracing the route to 121-73-114-1.cable.telstraclear.net (121.73.114.1)
1 vl96.switch2.syd.pacific.net.au (61.8.2.1) 0 msec
vl98.switch1.syd.pacific.net.au (210.23.140.1) 0 msec
vl96.switch2.syd.pacific.net.au (61.8.2.1) 0 msec
2 vl63.switch2.syd.pacific.net.au (125.255.94.122) 4 msec
GigabitEthernet3-1.ult1.Sydney.telstra.net (139.130.248.85) 0 msec
vl63.switch2.syd.pacific.net.au (125.255.94.122) 0 msec
3 TenGigE0-1-0-0.chw-core2.Sydney.telstra.net (203.50.20.129) 4 msec
GigabitEthernet3-1.ult1.Sydney.telstra.net (139.130.248.85) 0 msec
TenGigE0-1-0-0.chw-core2.Sydney.telstra.net (203.50.20.129) 0 msec
4 TenGigE0-1-0-0.chw-core2.Sydney.telstra.net (203.50.20.129) 0 msec
Bundle-ether1.pad-gw1.Sydney.telstra.net (203.50.6.25) 4 msec
TenGigE0-1-0-0.chw-core2.Sydney.telstra.net (203.50.20.129) 0 msec
5 i-0-0-0-peer.sydp-core01.pr.reach.com (134.159.126.33) 0 msec
Bundle-ether1.pad-gw1.Sydney.telstra.net (203.50.6.25) 8 msec
i-0-0-0-peer.sydp-core01.pr.reach.com (134.159.126.33) 0 msec
6 i-0-0-0-peer.sydp-core01.pr.reach.com (134.159.126.33) 0 msec
i-0-1-1-0.sydp-core05.bi.reach.com (202.84.220.209) 0 msec
i-0-0-0-peer.sydp-core01.pr.reach.com (134.159.126.33) 4 msec
7 i-0-0-1-0.sydo-core02.bi.reach.com (202.84.249.14) 4 msec
i-0-1-1-0.sydp-core05.bi.reach.com (202.84.220.209) 0 msec
i-0-0-1-0.sydo-core02.bi.reach.com (202.84.249.14) 0 msec
8 i-0-0-1-0.sydo-core02.bi.reach.com (202.84.249.14) 4 msec
i-7-1-1.hptw-core01.bx.reach.com (202.84.142.154) 24 msec
i-0-0-1-0.sydo-core02.bi.reach.com (202.84.249.14) 4 msec
9 203.167.233.14 [AS 4768] 24 msec
i-7-1-1.hptw-core01.bx.reach.com (202.84.142.154) 24 msec
203.167.233.14 [AS 4768] 28 msec
10 203.167.233.14 [AS 4768] 24 msec
ie1-g-0-0-0.telstraclear.net (203.98.50.1) [AS 4768] 24 msec
203.167.233.14 [AS 4768] 28 msec
11 *
ie1-g-0-0-0.telstraclear.net (203.98.50.1) [AS 4768] 60 msec *
12 *
121-73-114-1.cable.telstraclear.net (121.73.114.1) 40 msec *
On 28/05/2011 11:05 a.m., Don Gould wrote:
> Use http://mrtg.pacific.net.au/zip-lg.html to trace to my gw -
> 121.73.114.1
>
> I could be wrong, but I think this time it is a fault in Telstra
> Australia. The trace looks different from the last one I had.
>
> I'll throw this at t.au off list as well, though I'm sure they've seen it.
>
> D
>
>
> Type escape sequence to abort.
> Tracing the route to 121-73-114-1.cable.telstraclear.net (121.73.114.1)
>
> 1 vl96.switch2.syd.pacific.net.au (61.8.2.1) 0 msec
> vl98.switch1.syd.pacific.net.au (210.23.140.1) 4 msec
> vl96.switch2.syd.pacific.net.au (61.8.2.1) 0 msec
> 2 vl63.switch2.syd.pacific.net.au (125.255.94.122) 0 msec
> GigabitEthernet3-1.ult1.Sydney.telstra.net (139.130.248.85) 0 msec
> vl63.switch2.syd.pacific.net.au (125.255.94.122) 0 msec
> 3 TenGigE0-1-0-0.chw-core2.Sydney.telstra.net (203.50.20.129) 0 msec
> GigabitEthernet3-1.ult1.Sydney.telstra.net (139.130.248.85) 0 msec
> TenGigE0-1-0-0.chw-core2.Sydney.telstra.net (203.50.20.129) 0 msec
> 4 TenGigE0-1-0-0.chw-core2.Sydney.telstra.net (203.50.20.129) 4 msec
> Bundle-ether1.pad-gw1.Sydney.telstra.net (203.50.6.25) 4 msec
> TenGigE0-1-0-0.chw-core2.Sydney.telstra.net (203.50.20.129) 4 msec
> 5 i-0-0-0-peer.sydp-core01.pr.reach.com (134.159.126.33) 0 msec
> Bundle-ether1.pad-gw1.Sydney.telstra.net (203.50.6.25) 4 msec
> i-0-0-0-peer.sydp-core01.pr.reach.com (134.159.126.33) 0 msec
> 6 i-0-0-0-peer.sydp-core01.pr.reach.com (134.159.126.33) 0 msec
> i-0-1-1-0.sydp-core05.bi.reach.com (202.84.220.209) 4 msec
> i-0-0-0-peer.sydp-core01.pr.reach.com (134.159.126.33) 0 msec
> 7 i-0-0-1-0.sydo-core02.bi.reach.com (202.84.249.14) 4 msec
> i-0-1-1-0.sydp-core05.bi.reach.com (202.84.220.209) 0 msec
> i-0-0-1-0.sydo-core02.bi.reach.com (202.84.249.14) 4 msec
> 8 i-0-0-1-0.sydo-core02.bi.reach.com (202.84.249.14) 4 msec
> i-7-1-1.hptw-core01.bx.reach.com (202.84.142.154) 24 msec
> i-0-0-1-0.sydo-core02.bi.reach.com (202.84.249.14) 8 msec
> 9 203.167.233.14 [AS 4768] 168 msec
> i-7-1-1.hptw-core01.bx.reach.com (202.84.142.154) 24 msec
> 203.167.233.14 [AS 4768] 168 msec
> 10 203.167.233.14 [AS 4768] 168 msec
> ie1-g-0-0-0.telstraclear.net (203.98.50.1) [AS 4768] 168 msec
> 203.167.233.14 [AS 4768] 188 msec
> 11 *
> ie1-g-0-0-0.telstraclear.net (203.98.50.1) [AS 4768] 164 msec *
> 12 *
>
> 121-73-114-1.cable.telstraclear.net (121.73.114.1) 180 msec *
>
>
> On 28/05/2011 11:01 a.m., Don Gould wrote:
>> Yip, it's back for me as well.
>>
>> The PN guys do monitor this list, so it would be NICE if they'd just
>> drop a note on list to say "got it" so we don't have to chase
>> everyone again.
>>
>> I'll check it from their looking glass a bit later and confirm it's
>> the same issue and bump their guys an off list note. It will be
>> effecting the same pplz again by the looks.
>>
>> I understand the issue is that they lost some transit because of a
>> cable cut. I'm going to guess they got the transit back but it's
>> stuff up their routing in the process.... but that really is just a
>> guess (while trying to connect some dots that might or might not relate).
>>
>> D
>>
>> On 27/05/2011 11:56 p.m., Brett wrote:
>>> Would appear this issue has resurfaced recently or is still onging?
>>>
>>> 1 115.31.88.230 (115.31.88.230) 0.890 ms 0.960 ms 1.141 ms
>>> 2 10.1.1.1 (10.1.1.1) 0.846 ms 0.838 ms 0.829 ms
>>> 3 c-20784-2726-VAIES-303-464.pr2.melb.nxg.net.au
>>> <http://c-20784-2726-VAIES-303-464.pr2.melb.nxg.net.au>
>>> (203.176.97.53) 14.941 ms 15.438 ms 15.454 ms
>>> 4 s-pr2-melb-1.br1.melb.nxg.net.au
>>> <http://s-pr2-melb-1.br1.melb.nxg.net.au> (121.200.224.151) 14.932
>>> ms 15.382 ms 21.397 ms
>>> 5 GigabitEthernet7-19.lon55.Melbourne.telstra.net
>>> <http://GigabitEthernet7-19.lon55.Melbourne.telstra.net>
>>> (165.228.205.81) 2.433 ms 2.432 ms 2.456 ms
>>> 6 TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net
>>> <http://TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net>
>>> (203.50.80.1) 2.457 ms 4.003 ms 3.996 ms
>>> 7 Bundle-Pos3.chw-core2.Sydney.telstra.net
>>> <http://Bundle-Pos3.chw-core2.Sydney.telstra.net> (203.50.11.14)
>>> 19.134 ms 19.161 ms 18.209 ms
>>> 8 Bundle-ether1.pad-gw1.Sydney.telstra.net
>>> <http://Bundle-ether1.pad-gw1.Sydney.telstra.net> (203.50.6.25)
>>> 18.069 ms 18.067 ms 18.090 ms
>>> 9 i-0-0-0-peer.sydp-core01.pr.reach.com
>>> <http://i-0-0-0-peer.sydp-core01.pr.reach.com> (134.159.126.33)
>>> 171.731 ms 171.750 ms 172.672 ms
>>> 10 i-0-1-1-0.sydp-core05.bi.reach.com
>>> <http://i-0-1-1-0.sydp-core05.bi.reach.com> (202.84.220.209)
>>> 173.265 ms 172.752 ms 172.743 ms
>>> 11 i-0-0-1-0.sydo-core02.bi.reach.com
>>> <http://i-0-0-1-0.sydo-core02.bi.reach.com> (202.84.249.14) 172.457
>>> ms 172.486 ms 172.487 ms
>>> 12 i-7-1-1.hptw-core01.bx.reach.com
>>> <http://i-7-1-1.hptw-core01.bx.reach.com> (202.84.142.154) 171.819
>>> ms 171.923 ms 171.947 ms
>>> 13 203.167.233.14 (203.167.233.14) 171.992 ms 171.983 ms 171.969
>>> ms^C
>>>
>>> On Tue, May 3, 2011 at 10:53 AM, Kevin Karp <ausnog at pps.com.au
>>> <mailto:ausnog at pps.com.au>> wrote:
>>>
>>> Hi Don
>>>
>>> We have had a ticket open with Pacnet since early March
>>> highlighting the
>>> problem at
>>>
>>> pacifi121.lnk.telstra.net <http://pacifi121.lnk.telstra.net>
>>>
>>> I believe the ticket is still open. Pacnet have never
>>> acknowledged the problem.
>>> They have many times requested traces and we have responded an
>>> equal number of
>>> times with results such as the one you listed.
>>>
>>> Unfortunately, I have no idea what the cause or remedy may be.
>>>
>>> Regards
>>>
>>> KJK
>>>
>>> Kevin Karp
>>> PPS Internet
>>>
>>> [p] +61 2 9281 3905 <tel:%2B61%202%209281%203905>
>>> [e] kjk at pps.com.au <mailto:kjk at pps.com.au>
>>> [w] pps.com.au <http://pps.com.au>
>>>
>>> _______________________________________________
>>> AusNOG mailing list
>>> AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net>
>>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>>
>>>
>>>
>>> _______________________________________________
>>> AusNOG mailing list
>>> AusNOG at lists.ausnog.net
>>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>>
>> --
>> Don Gould
>> 31 Acheson Ave
>> Mairehau
>> Christchurch, New Zealand
>> Ph: + 64 3 348 7235
>> Mobile: + 64 21 114 0699
>>
>>
>>
>> _______________________________________________
>> AusNOG mailing list
>> AusNOG at lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
> --
> Don Gould
> 31 Acheson Ave
> Mairehau
> Christchurch, New Zealand
> Ph: + 64 3 348 7235
> Mobile: + 64 21 114 0699
>
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
--
Don Gould
31 Acheson Ave
Mairehau
Christchurch, New Zealand
Ph: + 64 3 348 7235
Mobile: + 64 21 114 0699
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20110528/1f009bad/attachment.html>
More information about the AusNOG
mailing list