BellNexxia to C&W problems in NY ? (AS577 - AS3561)

Tue Mar 9 23:48:46 UTC 2004


Hi Mark,
         Thanks for responding / confirming. My transits that are C&W peers 
are Telus and 306/GT.  I contacted them to contact you as I am not a direct 
C&W customer.  I am just in the middle so to speak trying to understand and 
work around the problem.

         ---Mike

At 06:38 PM 09/03/2004, Mark Kasten wrote:
>Mike,
>    It does appear that this interconnect is running a bit hot.  If there 
> is anyone from Bell Nexxia/AS577 listening, feel free to ping me offline 
> and I'll see what I can do to help out.  But, to be honest, this is an 
> issue that could/should be handled your upstream and noc at cw.net.
>I don't see any emails from you sent to noc at cw.net.
>
>Regards,
>    Mark Kasten
>
>
>
>Mike Tancsa wrote:
>
>>
>>
>>I have a few users exchanging data with sites inside Bell Canada call in 
>>to complain today with various symptoms (eg. VPNs timing out, transfers 
>>taking a long time).  After a bit of narrowing down, it would seem that 
>>when the traffic comes at me via C&W from Bell (2 of my 3 transit 
>>providers 852 and 6539 talk to parts of Bell this way) the problems are acute.
>>
>>Looking at traceroutes between C&W and Bell IP space, there does indeed 
>>seem to be some issue between their exchange point in NY
>>
>>The 2 snippets being
>> From bell to cw
>>   6 bx2-newyork83-pos3-0.in.bellnexxia.net (206.108.103.194) 20 msec 20 
>> msec 16 msec
>>   7 iar4-so-2-3-0.NewYork.cw.net (208.173.135.185) [AS 3561] 172 msec 
>> 176 msec 176 msec
>> From cw to bell
>>   6 iar4-loopback.NewYork.cw.net (206.24.194.39) 68 msec 68 msec 72 msec
>>   7 teleglobe.NewYork.cw.net (208.173.135.186) 208 msec 208 msec 208 msec
>>
>>At one point in the day, it was adding about 400 to 500ms of latency
>>
>>Type escape sequence to abort.
>>Tracing the route to route-server.cw.net (209.1.220.234)
>>
>>   1 dis40-toronto63-fe5-0-0.in.bellnexxia.net (205.207.238.210) 32 msec 
>> 0 msec 232 msec
>>   2 core2-toronto63-pos11-5.in.bellnexxia.net (206.108.98.141) 0 msec 0 
>> msec 0 msec
>>   3 core3-toronto63-pos6-0.in.bellnexxia.net (64.230.242.101) 0 msec 0 
>> msec 0 msec
>>   4 core4-montreal02-pos13-1.in.bellnexxia.net (64.230.243.237) 28 msec 
>> 204 msec 208 msec
>>   5 core1-newyork83-pos0-0.in.bellnexxia.net (206.108.99.190) 20 msec 20 
>> msec 16 msec
>>   6 bx2-newyork83-pos3-0.in.bellnexxia.net (206.108.103.194) 20 msec 20 
>> msec 16 msec
>>   7 iar4-so-2-3-0.NewYork.cw.net (208.173.135.185) [AS 3561] 172 msec 
>> 176 msec 176 msec
>>   8 agr2-loopback.NewYork.cw.net (206.24.194.102) [AS 3561] 184 msec 176 
>> msec 180 msec
>>   9 dcr1-so-6-1-0.NewYork.cw.net (206.24.207.53) [AS 3561] 184 msec 180 
>> msec 184 msec
>>  10 dcr2-loopback.SantaClara.cw.net (208.172.146.100) [AS 3561] 248 msec 
>> 248 msec 248 msec
>>  11 bhr1-pos-0-0.SantaClarasc8.cw.net (208.172.156.198) [AS 3561] 256 
>> msec 244 msec 244 msec
>>  12 bhr2-ge-2-0.SantaClarasc8.cw.net (208.172.147.54) [AS 3561] 252 msec 
>> 248 msec 248 msec
>>  13 209.1.169.177 [AS 3561] 172 msec 184 msec *
>>
>>
>>
>>route-server.cw.net>traceroute looking-glass.in.bellnexxia.net
>>Translating "looking-glass.in.bellnexxia.net"...domain server 
>>(64.41.189.214) [OK]
>>
>>Type escape sequence to abort.
>>Tracing the route to looking-glass.in.bellnexxia.net (205.207.237.50)
>>
>>   1 209.1.169.178 0 msec 0 msec 0 msec
>>   2 bhr1-ge-2-0.SantaClarasc8.cw.net (208.172.147.53) 0 msec 0 msec 0 msec
>>   3 dcr2-so-3-0-0.SantaClara.cw.net (208.172.156.197) 0 msec 4 msec 0 msec
>>   4 dcr1-loopback.NewYork.cw.net (206.24.194.99) 76 msec
>>     dcr2-loopback.NewYork.cw.net (206.24.194.100) 72 msec
>>     dcr1-loopback.NewYork.cw.net (206.24.194.99) 68 msec
>>   5 agr1-so-0-0-0.NewYork.cw.net (206.24.207.50) 68 msec 72 msec 68 msec
>>   6 iar4-loopback.NewYork.cw.net (206.24.194.39) 68 msec 68 msec 72 msec
>>   7 teleglobe.NewYork.cw.net (208.173.135.186) 208 msec 208 msec 208 msec
>>   8 core1-newyork83-pos1-1.in.bellnexxia.net (206.108.103.193) 260 msec 
>> 332 msec 216 msec
>>   9 core4-montreal02-pos6-3.in.bellnexxia.net (206.108.99.189) 196 msec 
>> 204 msec 200 msec
>>  10 64.230.243.238 208 msec 296 msec 460 msec
>>  11 core2-torontodc-pos3-1.in.bellnexxia.net (206.108.104.2) [AS 577] 
>> 432 msec 404 msec 404 msec
>>  12 dis4-torontodc-Vlan82.in.bellnexxia.net (206.108.104.30) [AS 577] 
>> 400 msec 240 msec 440 msec
>>  13 looking-glass.in.bellnexxia.net (205.207.237.50) [AS 577] 452 msec 
>> 236 msec 244 msec
>>route-server.cw.net>
>>
>>Anyone know whats up ?
>>
>>     ---Mike
>>--------------------------------------------------------------------
>>Mike Tancsa,                                        tel +1 519 651 3400
>>Sentex Communications,                   mike at sentex.net
>>Providing Internet since 1994                    www.sentex.net
>>Cambridge, Ontario Canada              www.sentex.net/mike