Quote:
|
Originally Posted by Stu038
 your just a bitter and twisted man Ig, well twisted anyway 
|
I refer the honourable gentleman to exhibit a:
traceroute brhm-warw-ubr-1.inet.ntl.com
traceroute to brhm-warw-ubr-1.inet.ntl.com (62.253.190.97), 64 hops max, 44 byte packets
5 nth-bb-b-so-600-0.inet.ntl.com (62.253.184.1) 4.116 ms 3.868 ms 3.709 ms
6 lee-bb-a-so-600-0.inet.ntl.com (62.253.185.102) 7.023 ms 6.686 ms 16.301 ms
7 nth-bb-b-so-000-0.inet.ntl.com (62.253.185.101) 6.787 ms 6.561 ms 6.742 ms
8 nth-bb-a-ae0-0.inet.ntl.com (62.253.185.117) 7.384 ms 7.668 ms 7.232 ms
Now I'm sure that it'd be easier to just go nth-bb-b to nth-bb-a straight away rather than going to Leeds and back to bb-b and
then to bb-a....
Exhibit b)
5 nth-bb-b-so-600-0.inet.ntl.com (62.253.184.1) 3.989 ms 3.570 ms 4.019 ms
6 lee-bb-a-so-600-0.inet.ntl.com (62.253.185.102) 6.925 ms 9.725 ms 6.975 ms
7 lee-bb-b-ae0-0.inet.ntl.com (62.253.187.186) 7.252 ms 6.868 ms 7.333 ms
8 man-bb-a-so-700-0.inet.ntl.com (62.253.185.193) 8.838 ms 8.130 ms 18.499 ms
9 man-bb-b-ae0-0.inet.ntl.com (62.253.187.178) 12.715 ms 9.289 ms 10.600 ms
10 win-bb-a-so-300-0.inet.ntl.com (62.253.185.138) 12.159 ms 10.715 ms 13.484 ms
11 winn-t2core-a-pos31.inet.ntl.com (62.253.184.114) 11.983 ms 11.104 ms 10.573 ms
12 rdng-t2cam1-a-ge-wan32.inet.ntl.com (62.253.121.26) 13.275 ms 12.643 ms 11.385 ms
13 rdng-rdng-ubr-1-ge10.inet.ntl.com (62.253.122.2) 12.734 ms * 10.578 ms
Now call me stupid but I'm sure from Telehouse there are better ways on the ntl network to get to Reading than via Northampton, Leeds and Manchester, such as possibly Brentford / Poplar (can't remember which) and Guildford...
No dynamic routing protocol would give routes that insane so without going into too much detail these look manually provisioned. Take an IP network and use MPLS (badly) to turn it into an ATM-style static path network. Good call guys.