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.

Re: Core Router Problem
 

I'm posting two, the first one to digiguide, the second to microsoft.


Tracing route to www.digiguide.com [146.101.2.56]
over a maximum of 30 hops:

1 12 ms 9 ms 12 ms 10.144.247.254
2 19 ms 14 ms 13 ms nott-t2cam1-b-ge-wan61-141.inet.ntl.com[80.4.46.153]
3 13 ms 17 ms 13 ms not-t2core-b-ge-wan74.inet.ntl.com [80.1.79.201]

4 11 ms 14 ms 13 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
5 14 ms 15 ms 19 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
6 17 ms 18 ms 15 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98]
7 27 ms 18 ms 19 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

8 19 ms 22 ms 18 ms linx-gw2.uk.psi.net [195.66.226.14]
9 27 ms 17 ms 33 ms 154.14.68.198
10 18 ms 22 ms 18 ms core1.lond1-ge1.dc.uk.psi.net [146.101.0.2]
11 22 ms 19 ms 30 ms neigh1.lond1-ge1-1.dc.uk.psi.net [146.101.0.18]

12 * * * Request timed out.
13 * * * Request timed out.

etc...




and to microsoft:




Tracing route to www2.microsoft.akadns.net [207.46.244.188]
over a maximum of 30 hops:

1 10 ms 9 ms 11 ms 10.144.247.254
2 13 ms 12 ms 13 ms nott-t2cam1-b-ge-wan61-141.inet.ntl.com [80.4.46
.153]
3 16 ms 14 ms 29 ms not-t2core-b-ge-wan74.inet.ntl.com [80.1.79.201]

4 22 ms 13 ms 12 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
5 23 ms 23 ms 19 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
6 15 ms 15 ms 18 ms So5-0-0.LONCR2.London.opentransit.net [193.251.2
54.141]
7 87 ms 17 ms 86 ms P1-0.NYKCR3.New-york.opentransit.net [193.251.24
3.89]
8 89 ms 87 ms 90 ms P12-0.OAKCR1.Oakhill.opentransit.net [193.251.24
2.254]
9 * 95 ms 93 ms P12-0.OAKCR1.Oakhill.opentransit.net [193.251.24
2.254]
10 96 ms * 95 ms 207.46.45.73
11 91 ms 92 ms 93 ms 207.46.34.113
12 98 ms 93 ms 182 ms 207.46.33.61
13 180 ms 181 ms 180 ms 207.46.36.214
14 181 ms 183 ms 184 ms 207.46.155.13
15 * 181 ms * 207.46.155.13
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.


Edit: problems are further down, but something is not right...

Re: Core Router Problem
 

he still get the points and the comments if you leave any which will be visable when he enables his rep. :D

Re: Core Router Problem
 

Actually both those traces are looking fine - the first one is missing the final step of the server itself - which is expected as ICMP is blocked by the servers firewall (I know, I configured it).

The second one is fine and identical to mine, the 207.46.x.x hops are all inside the Microsoft Network so I would guess they are blocking ICMP at the servers as well (hence you can't ping them either).

Re: Core Router Problem
 

Ah :confused: :), Apparently you need to know a little about the address you are querying, and timeouts may be normal. I'm considering starting a thread where this stuff might be explained to novices like me. (Your ping times out as expected) or something like that.

I'm glad browsing is ok again though ;)

Re: Core Router Problem
 

Bahhh im fed up of taking those routing calls, I stumbled across it in November first of all, noticed it by complete fluke. MTRG was showing allot of trouble, so got it escalated then. Then it happened again, and now again! Ahhh well gives me something to do....

Im to controversial to enable rep. Ohhh the negative-ness from .com

Edit : thats MRTG^ Typing never was my strong point

Re: Core Router Problem
 

yes this would confirm?

TraceRoute Report on 07/01/04 at 01:39:47

Tracing route to 207.46.244.188 over a maximum of 25 hops:

#1 ***.**.***.***[Unavailable]: TTL expired in transit, 42 ms
#2 80.4.47.225 [nott-t2cam1-b-ge-wan51-128.inet.ntl.com]: TTL expired in transit, 26 ms
#3 80.1.79.201 [not-t2core-b-ge-wan74.inet.ntl.com]: TTL expired in transit, 15 ms
#4 62.253.188.37 [nth-bb-b-so-300-0.inet.ntl.com]: TTL expired in transit, 13 ms
#5 62.253.185.117 [nth-bb-a-ae0-0.inet.ntl.com]: TTL expired in transit, 17 ms
#6 193.251.254.141 [So5-0-0.LONCR2.London.opentransit.net]: TTL expired in transit, 18 ms
#7 193.251.128.205 [So3-0-0.LONCR1.London.opentransit.net]: TTL expired in transit, 50 ms
#8 193.251.242.254 [P12-0.OAKCR1.Oakhill.opentransit.net]: TTL expired in transit, 211 ms
#9 193.251.248.109 [So4-0-0.ASHBB1.Ashburn.opentransit.net]: TTL expired in transit, 91 ms
#10 193.251.248.109 [So4-0-0.ASHBB1.Ashburn.opentransit.net]: TTL expired in transit, 97 ms
#11 207.46.34.113 [Unavailable]: TTL expired in transit, 93 ms
#12 207.46.34.113 [Unavailable]: TTL expired in transit, 98 ms
#13 207.46.33.61 [Unavailable]: TTL expired in transit, 186 ms
#14 207.46.155.13 [Unavailable]: TTL expired in transit, 190 ms
#15 207.46.155.13 [Unavailable]: TTL expired in transit, 184 ms
#16 [Unavailable]: Request timed out
#17 [Unavailable]: Request timed out
etc
#25 [Unavailable]: Request timed out

Statistics: Out: 25; In: 15; Loss: 40%; Times(min/avg/max): 13/88/211

Re: Core Router Problem
 

have they fix the core yet ?

Re: Core Router Problem
 

Intermittent probs for me too at the moment:

Code:

---

Tracing route to nthellworld.co.uk [216.40.241.59]
over a maximum of 30 hops:

  1    1 ms    1 ms    1 ms  192.168.123.254
  2    8 ms    9 ms    8 ms  10.15.80.1
  3    9 ms    9 ms    11 ms  bagu-t2cam1-b-ge-wan52-122.inet.ntl.com [80.5.162.217]
  4    8 ms    9 ms    9 ms  bagu-t2core-b-ge-wan62.inet.ntl.com [80.5.161.133]
  5    10 ms    12 ms    11 ms  lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
  6    10 ms    11 ms    10 ms  lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
  7    15 ms    15 ms    15 ms  pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
  8    57 ms    60 ms    *    tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
  9    18 ms    *        *    lndnuk1icx1.wcg.net [195.66.224.105]
 10  128 ms  128 ms    *    nycmny2wcx2-oc12.wcg.net [64.200.87.153]
 11    *      129 ms  128 ms  hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
 12  129 ms    *        *    hrndva1wcx3-oc48.wcg.net [64.200.95.74]
 13  129 ms    *      129 ms  drvlga1wcx2-pos.wcg.net [64.200.210.57]
 14  129 ms  129 ms  128 ms  drvlga1wcx1-oc48.wcg.net [64.200.127.29]
 15  128 ms    *      127 ms  dllstx1wcx3-oc48.wcg.net [64.200.240.21]
 16  127 ms  128 ms  128 ms  dllstx1wcx2-oc48.wcg.net [64.200.110.73]
 17  128 ms  128 ms  128 ms  hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
 18  128 ms    *      129 ms  hstntx1wce2-everyonesinternet-gige.wcg.net [65.77.93.54]
 19    *      119 ms  119 ms  ivhou-207-218-223-34.ev1.net [207.218.223.34]
 20    *        *        *    Request timed out.
 21    *        *        *    Request timed out.
 22    *        *        *    Request timed out.
 23    *        *        *    Request timed out.
 24    *        *        *    Request timed out.

---

Re: Core Router Problem
 

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Garry>tracert www.nthellworld.co.uk

Tracing route to nthellworld.co.uk [216.40.241.59]
over a maximum of 30 hops:

1 11 ms 9 ms 6 ms 10.138.23.254
2 8 ms 9 ms 9 ms nott-t2cam1-b-ge-wan51-130.inet.ntl.com [80.4.47
.233]
3 39 ms 9 ms 11 ms not-t2core-b-ge-wan61.inet.ntl.com [80.1.79.185]

4 11 ms 10 ms 9 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
5 13 ms 13 ms 22 ms lee-bb-a-so-600-0.inet.ntl.com [62.253.185.102]

6 22 ms 18 ms 18 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

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

8 26 ms 20 ms 23 ms lndnuk1icx1.wcg.net [195.66.224.105]
9 130 ms 132 ms 131 ms nycmny2wcx2-pos15-3.wcg.net [64.200.87.61]
10 131 ms 130 ms 146 ms hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
11 132 ms 132 ms 129 ms hrndva1wcx3-oc48.wcg.net [64.200.95.74]
12 136 ms 130 ms 135 ms drvlga1wcx2-pos.wcg.net [64.200.210.57]
13 134 ms 130 ms 133 ms drvlga1wcx1-oc48.wcg.net [64.200.127.49]
14 130 ms 134 ms 132 ms dllstx1wcx3-oc48.wcg.net [64.200.240.21]
15 132 ms 131 ms 129 ms dllstx1wcx2-oc48.wcg.net [64.200.110.73]
16 131 ms 131 ms 131 ms hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
17 131 ms 131 ms 132 ms hstntx1wce2-everyonesinternet-gige.wcg.net [65.7
7.93.54]
18 134 ms 131 ms 131 ms ivhou-207-218-223-34.ev1.net [207.218.223.34]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Documents and Settings\Garry>