Anyone know what is up between them in Ontario, Canada ? I am seeing pretty high latency and packet loss in both directions. Dont know if its a chronic capacity problem or just a dead/down circuit ?
Bell's looking glass showed (prior to my prepending)
BGP routing table entry for 199.212.134.0/24, version 89013385
Paths: (2 available, best #1)
Not advertised to any peer
852 11647, (received & used)
206.108.96.231 (metric 2060) from 206.108.96.17 (206.108.96.17)
Origin IGP, metric 1000, localpref 110, valid, internal, best
Community: 577:55 577:4520 577:5602 577:10100
Originator: 206.108.96.231, Cluster list: 206.108.96.17, 206.108.96.1
852 11647, (received & used)
206.108.96.231 (metric 2060) from 206.108.96.18 (206.108.96.18)
Origin IGP, metric 1000, localpref 110, valid, internal
Community: 577:55 577:4520 577:5602 577:10100
Originator: 206.108.96.231, Cluster list: 206.108.96.18, 206.108.96.1
Type escape sequence to abort.
Tracing the route to ns.sentex.ca (199.212.134.1)
1 bxsmc-fe5-0-0.in.bellnexxia.net (205.207.238.210) 20 msec 204 msec 200 msec
2 core2-toronto63-pos11-5.in.bellnexxia.net (206.108.98.141) 0 msec 0 msec 4 msec
3 core4-toronto63-pos6-0.in.bellnexxia.net (64.230.242.105) 0 msec 4 msec 0 msec
4 core4-toronto12-pos13-0.in.bellnexxia.net (64.230.242.181) 0 msec 0 msec 0 msec
5 core1-toronto12-pos0-1.in.bellnexxia.net (64.230.242.198) 0 msec 0 msec 0 msec
6 bx5-toronto12-so-0-1-0-0.in.bellnexxia.net (64.230.242.150) 0 msec 0 msec 0 msec
7 toroonnlgr00.bb.telus.com (154.11.3.25) [AS 852] 176 msec 180 msec 176 msec
8 toroonzddr00.bb.telus.com (154.11.6.3) [AS 852] 172 msec 176 msec 176 msec
9 *
hespler155ATM-waterloo.sentex.ca (199.212.135.77) [AS 11647] 164 msec 172 msec
10 *
ns.sentex.ca (199.212.134.1) [AS 11647] 160 msec *
and a traceroute from telus' route server to Bell
route-views.on>traceroute 206.108.111.125
Type escape sequence to abort.
Tracing the route to bx5-toronto12-so-0-0-1-0.in.bellnexxia.net (206.108.111.125)
1 toroonxngr00.bb.telus.com (154.11.63.85) 0 msec 0 msec 0 msec
2 toroonnlbr00.bb.telus.com (154.11.11.37) 4 msec 0 msec 0 msec
3 toroonnlgr00.bb.telus.com (154.11.11.58) 0 msec 0 msec 0 msec
4 bx5-toronto12-so-0-0-1-0.in.bellnexxia.net (206.108.111.125) [AS 577] 164 msec 164 msec 164 msec
route-views.on>
route-views.on>show ip bgp 206.108.111.125
BGP routing table entry for 206.108.111.0/24, version 117710304
Paths: (2 available, best #1)
Advertised to non peer-group peers:
198.32.162.100 198.32.162.102
577, (aggregated by 577 206.108.96.25)
154.11.0.147 from 154.11.0.150 (154.11.0.150)
Origin IGP, metric 0, localpref 90, valid, internal, atomic-aggregate, best
Originator: 154.11.0.147, Cluster list: 154.11.0.150
577, (aggregated by 577 206.108.96.25)
154.11.0.147 from 154.11.0.151 (154.11.0.151)
Origin IGP, metric 0, localpref 90, valid, internal, atomic-aggregate
Originator: 154.11.0.147, Cluster list: 154.11.0.151
route-views.on>
i.e. as soon as it hits Bell's network, there is quite a jump in latency and packet loss.
Some of the paths to 577 out of Telus actually go down via Sprint in Chicago which seems rather odd
e.g.
route-views.on>show ip bgp 198.235.69.11
BGP routing table entry for 198.235.69.0/24, version 239594939
Paths: (2 available, best #1)
Advertised to non peer-group peers:
198.32.162.100 198.32.162.102
1239 577
154.11.0.155 from 154.11.0.150 (154.11.0.150)
Origin IGP, metric 100, localpref 100, valid, internal, best
Originator: 209.115.137.204, Cluster list: 154.11.0.150
1239 577
154.11.0.155 from 154.11.0.151 (154.11.0.151)
Origin IGP, metric 100, localpref 100, valid, internal
Originator: 209.115.137.204, Cluster list: 154.11.0.151
route-views.on>
Anyone know whats up ?
---Mike
Anyways, just wanted to publicly thank the nice Telus NOC people for making my life easier.