Core Router Problem
 

One of the core routers I use appears to be a bit poorly tonight, these two traces were taken about 15 minutes apart;

C:\WINDOWS>tracert forums.digiguide.com
Tracing route to forums.digiguide.com [81.201.129.163]
over a maximum of 30 hops:
2 11 ms 7 ms 9 ms 10.145.xxx.254
3 54 ms 7 ms 35 ms nott-t2cam1-b-ge-wan42-122.inet.ntl.com [80.4.46
.201]
4 790 ms 2127 ms 759 ms not-t2core-b-ge-wan61.inet.ntl.com [80.1.79.185]
5 135 ms 121 ms 161 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 112 ms 108 ms 109 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
7 114 ms 111 ms * gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98]
8 119 ms 138 ms 120 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
9 42 ms 17 ms 19 ms linx1.lon1.as8553.net [195.66.224.126]
10 17 ms 17 ms 46 ms fa1-0.lon6.as8553.net [195.10.255.194]
11 19 ms 35 ms 20 ms s6-1.bris1.as8553.net [195.10.255.134]
12 183 ms 263 ms 227 ms fa0-0-2.bris2.as8553.net [195.10.254.82]
13 33 ms 25 ms 24 ms s6-0.man1.as8553.net [195.10.255.14]
14 25 ms 26 ms 39 ms 81.201.129.163
Trace complete.


C:\WINDOWS>tracert forums.digiguide.com
Tracing route to forums.digiguide.com [81.201.129.163]
over a maximum of 30 hops:
2 9 ms 27 ms 89 ms 10.145.xxx.254
3 8 ms 7 ms 7 ms nott-t2cam1-b-ge-wan42-122.inet.ntl.com [80.4.46
.201]
4 1926 ms 140 ms 719 ms not-t2core-b-ge-wan61.inet.ntl.com [80.1.79.185]
5 124 ms 150 ms 108 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 113 ms * 111 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
7 107 ms 108 ms 117 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98]
8 152 ms 152 ms 143 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
9 252 ms 310 ms 259 ms linx1.lon1.as8553.net [195.66.224.126]
10 19 ms 18 ms 17 ms fa1-0.lon6.as8553.net [195.10.255.194]
11 39 ms 23 ms 21 ms s6-1.bris1.as8553.net [195.10.255.134]
12 20 ms 19 ms 21 ms fa0-0-2.bris2.as8553.net [195.10.254.82]
13 25 ms 29 ms 25 ms s6-0.man1.as8553.net [195.10.255.14]
14 26 ms 26 ms 84 ms 81.201.129.163
Trace complete.
C:\WINDOWS>


Anyone else noticed they have this problem tonight ?

Re: Core Router Problem
 

you seem to have done better than me. I am slow browsing tonight but didn't expect this:-

Tracing route to 81.201.129.163 over a maximum of 30 hops

1 21 ms 10 ms 10 ms 10.11.32.1
2 * 10 ms 10 ms oldh-t2cam1-a-ge-wan51-120.inet.ntl.com [80.5.16
4.81]
3 10 ms 10 ms 10 ms mant-t2core-a-ge-wan64.inet.ntl.com [213.104.242
.53]
4 10 ms 10 ms 20 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
5 30 ms 10 ms 10 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]

6 10 ms 30 ms 10 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
7 20 ms 21 ms 20 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

8 50 ms * 50 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]

9 20 ms 30 ms 20 ms linx1.lon1.as8553.net [195.66.224.126]
10 10 ms 20 ms 20 ms fa1-0.lon6.as8553.net [195.10.255.194]
11 20 ms 20 ms 20 ms s6-1.bris1.as8553.net [195.10.255.134]
12 20 ms 20 ms 20 ms fa0-0-2.bris2.as8553.net [195.10.254.82]
13 30 ms 20 ms 30 ms s6-0.man1.as8553.net [195.10.255.14]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.


interesting have to do a few more to different ips.

Re: Core Router Problem
 

Fine from Leicester, but then again I use a different core router for hop 4. not-t2wan

Re: Core Router Problem
 

Ping has started ...

PING 80.1.79.185 (80.1.79.185): 56 data bytes
64 bytes from 80.1.79.185: icmp_seq=0 ttl=248 time=107.012 ms
64 bytes from 80.1.79.185: icmp_seq=1 ttl=248 time=111.234 ms
64 bytes from 80.1.79.185: icmp_seq=2 ttl=248 time=113.809 ms
64 bytes from 80.1.79.185: icmp_seq=3 ttl=248 time=131.378 ms
64 bytes from 80.1.79.185: icmp_seq=4 ttl=248 time=138.63 ms
64 bytes from 80.1.79.185: icmp_seq=5 ttl=248 time=144.185 ms
64 bytes from 80.1.79.185: icmp_seq=6 ttl=248 time=136.092 ms
64 bytes from 80.1.79.185: icmp_seq=7 ttl=248 time=250.411 ms
64 bytes from 80.1.79.185: icmp_seq=8 ttl=248 time=128.864 ms
64 bytes from 80.1.79.185: icmp_seq=9 ttl=248 time=131.684 ms
64 bytes from 80.1.79.185: icmp_seq=10 ttl=248 time=160.571 ms
64 bytes from 80.1.79.185: icmp_seq=11 ttl=248 time=99.425 ms
64 bytes from 80.1.79.185: icmp_seq=12 ttl=248 time=111.365 ms
64 bytes from 80.1.79.185: icmp_seq=13 ttl=248 time=112.239 ms
64 bytes from 80.1.79.185: icmp_seq=14 ttl=248 time=155.536 ms
64 bytes from 80.1.79.185: icmp_seq=15 ttl=248 time=142.72 ms

Re: Core Router Problem
 

LOL, hello Mole ;)

You are using Wan63, not Wan61 which is the problem one tonight. Kitty is using Wan64.

It also seems to be intermittent.

Re: Core Router Problem
 

er - ge-wan6x is the part of the dns name denoting the interface on that router - this will always be the one closest to you (where the icmp reply comes from). The important bit is the not-t2core-a or not-t2core-b bit, those are two separate machines.

No, I don't know what the problem is, before anyone asks, it's too far up the network for me, have to ask a big boss network guy. People on the nthellworld irc channel are complaining too though.

Re: Core Router Problem
 

it's 'deeper' than that for me too - & wan61 looked ok.

TraceRoute Report
on 06/01/04 at 22:28:52

Tracing route to forums.digiguide.com over a maximum of 25 hops:

#1 ***.**.***.*** [Unavailable]: TTL expired in transit, 17 ms
#2 80.4.47.225 [nott-t2cam1-b-ge-wan51-128.inet.ntl.com]: TTL expired in transit, 12 ms
#3 80.1.79.185 [not-t2core-b-ge-wan61.inet.ntl.com]: TTL expired in transit, 18 ms
#4 62.253.185.37 [nth-bb-b-so-200-0.inet.ntl.com]: TTL expired in transit, 34 ms
#5 62.253.185.117 [nth-bb-a-ae0-0.inet.ntl.com]: TTL expired in transit, 25 ms
#6 62.253.185.98 [gfd-bb-b-so-400-0.inet.ntl.com]: TTL expired in transit, 20 ms
#7 62.253.185.74 [tele-ic-2-so-100-0.inet.ntl.com]: TTL expired in transit, 24 ms
#8 195.66.224.126 [linx1.lon1.as8553.net]: TTL expired in transit, 24 ms
#9 195.10.255.194 [fa1-0.lon6.as8553.net]: TTL expired in transit, 24 ms
#10 195.10.255.134 [s6-1.bris1.as8553.net]: TTL expired in transit, 67 ms
#11 195.10.254.82 [fa0-0-2.bris2.as8553.net]: TTL expired in transit, 25 ms
#12 195.10.255.14 [s6-0.man1.as8553.net]: TTL expired in transit, 68 ms
#13 [Unavailable]: Request timed out
etc
#25 [Unavailable]: Request timed out

Statistics: Out: 25; In: 12; Loss: 52%; Times(min/avg/max): 12/29/68

Re: Core Router Problem
 

Yes, it's been poor most of the evening (Nottingham here, like you)

Re: Core Router Problem
 

Mr.Moony supertech got this escalated at 6pm. Should be resolved soon ;)

Re: Core Router Problem
 

Thank you Mr.Moony - it seems to be fixed now :D

Re: Core Router Problem
 

Good old My Moony......

Rep point on the way :)

Re: Core Router Problem
 

LOL, I thought of that - then i noticed he has his rep disabled .... :erm:

Re: Core Router Problem
 

:D Evening ;)

Thought that was why mine was fine. Glad it's all been sorted, mind.

Re: Core Router Problem
 

I'm still getting loads of timeouts, on pings and tracerts to just about anywhere. (though slow browsing seems to have been resolved)

Pardon me if I'm showing my ignorance, but that can't be good can it? ;)

Re: Core Router Problem
 

Doesn't sound good, this is one of my traces now - and I'm fine (the previously poor router shown in green).

Can you post one of your duff traces ?


Tracing route to forums.digiguide.com [81.201.129.163] over a maximum of 30 hops:
3 8 ms 7 ms 7 ms nott-t2cam1-b-ge-wan42-122.inet.ntl.com [80.4.46.201]
4 9 ms 9 ms 9 ms not-t2core-b-ge-wan61.inet.ntl.com [80.1.79.185]
5 9 ms 10 ms 13 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
6 10 ms 11 ms 9 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
7 14 ms 25 ms 13 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98]
8 20 ms 15 ms 14 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
9 36 ms 16 ms 15 ms linx1.lon1.as8553.net [195.66.224.126]
10 18 ms 17 ms 17 ms fa1-0.lon6.as8553.net [195.10.255.194]
11 19 ms 19 ms 20 ms s6-1.bris1.as8553.net [195.10.255.134]
12 26 ms 19 ms 24 ms fa0-0-2.bris2.as8553.net [195.10.254.82]
13 26 ms 26 ms 25 ms s6-0.man1.as8553.net [195.10.255.14]
14 25 ms 28 ms 25 ms 81.201.129.163

Trace complete.