Speed Rochdale

th'engineer · 20-05-2005, 11:35

anyone having similar problems

Fri, 20 May 2005 11:33:24 UTC
1st 128K took 3688 ms = 35540 Bytes/sec = approx 296 kbits/sec
2nd 128K took 547 ms = 239620 Bytes/sec = approx 1994 kbits/sec
3rd 128K took 562 ms = 233224 Bytes/sec = approx 1940 kbits/sec
4th 128K took 3219 ms = 40718 Bytes/sec = approx 339 kbits/sec

Fri, 20 May 2005 11:40:33 UTC
1st 128K took 563 ms = 232810 Bytes/sec = approx 1937 kbits/sec
2nd 128K took 547 ms = 239620 Bytes/sec = approx 1994 kbits/sec
3rd 128K took 3109 ms = 42159 Bytes/sec = approx 351 kbits/sec
4th 128K took 3375 ms = 38836 Bytes/sec = approx 323 kbits/sec

1 1 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.0.1
3 86 ms 67 ms 176 ms 10.23.48.1
4 172 ms 11 ms 9 ms oldh-t2cam1-a-v115.inet.ntl.com [80.5.164.61]
5 74 ms 121 ms 57 ms mant-t2core-a-ge-wan62.inet.ntl.com [213.104.24
41]
6 226 ms 371 ms * man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
7 11 ms 18 ms 119 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 16 ms 16 ms 81 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
9 146 ms 15 ms 19 ms win-dc-a-v903.inet.ntl.com [213.105.174.34]
10 141 ms 176 ms 67 ms www.ntlworld.com [62.253.162.30]
race complete.

tracert www.ntlworld.com
racing route to www.ntlworld.com [62.253.162.30]
ver a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.0.1
3 415 ms * 95 ms 10.23.48.1
4 * 11 ms 11 ms oldh-t2cam1-a-v115.inet.ntl.com [80.5.164.61]
5 11 ms 10 ms 9 ms mant-t2core-a-ge-wan62.inet.ntl.com [213.104.24
41]
6 69 ms 187 ms 354 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
7 507 ms * 251 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 * * * Request timed out.
9 17 ms 16 ms 16 ms win-dc-a-v903.inet.ntl.com [213.105.174.34]
10 16 ms 16 ms 16 ms www.ntlworld.com [62.253.162.30]
race complete.
tracert www.ntlworld.com

tracing route to www.ntlworld.com [62.253.162.30]
ver a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.0.1
3 351 ms 296 ms * 10.23.48.1
4 * * 10 ms oldh-t2cam1-a-v115.inet.ntl.com [80.5.164.61]
5 125 ms 157 ms * mant-t2core-a-ge-wan62.inet.ntl.com [213.104.24
41]
6 233 ms * 39 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
7 11 ms 9 ms 17 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 364 ms 473 ms * win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
9 16 ms 16 ms 17 ms win-dc-a-v903.inet.ntl.com [213.105.174.34]
10 196 ms 201 ms 301 ms www.ntlworld.com [62.253.162.30]
race complete.

th'engineer · 21-05-2005, 05:48

well have reported it and they have agreed there is a network problem

1 2 ms 2 ms 1 ms 192.168.2.1
2 5 ms 3 ms 2 ms 192.168.0.1
3 264 ms 231 ms 203 ms 10.23.48.1
4 159 ms 67 ms 359 ms oldh-t2cam1-a-v115.inet.ntl.com [80.5.164.61]
5 * 95 ms 64 ms mant-t2core-a-ge-wan62.inet.ntl.com [213.104.242
.41]
6 256 ms 60 ms 61 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
7 14 ms 9 ms 10 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 71 ms 65 ms 16 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
9 15 ms 19 ms 16 ms win-dc-a-v903.inet.ntl.com [213.105.174.34]
10 259 ms 17 ms 15 ms www.ntlworld.com [62.253.162.30]

how do they know this because i can tracert to local ubr in under 10ms therefore its a network problem

1 1 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.0.1
3 9 ms 8 ms 13 ms spc1-roch1-6-0-gw.bagu.broadband.ntl.com [81.100
.143.1]

**Paul** · 21-05-2005, 06:15

Looks a bit like like a network problem between your UBR and oldh-t2cam1-a-v115.inet.ntl.com.

Ignition · 21-05-2005, 10:19

Not from where I'm sitting it doesn't looks more like an RF noise issue to me:

2 2 ms 2 ms 2 ms 192.168.0.1
3 86 ms 67 ms 176 ms 10.23.48.1

2 5 ms 3 ms 2 ms 192.168.0.1
3 264 ms 231 ms 203 ms 10.23.48.1

2 2 ms 2 ms 2 ms 192.168.0.1
3 351 ms 296 ms * 10.23.48.1

2 2 ms 2 ms 2 ms 192.168.0.1
3 415 ms * 95 ms 10.23.48.1

The symptoms seen between CMTS and CAM are symptomatic of the loss between CMTS and modem, the fact you managed 1 out of 5 where the CMTS responded ok doesn't prove an IP network issue.

th'engineer · 25-05-2005, 22:08

Quote:

Originally Posted by Ignition

Not from where I'm sitting it doesn't looks more like an RF noise issue to me:

2 2 ms 2 ms 2 ms 192.168.0.1
3 86 ms 67 ms 176 ms 10.23.48.1

2 5 ms 3 ms 2 ms 192.168.0.1
3 264 ms 231 ms 203 ms 10.23.48.1

2 2 ms 2 ms 2 ms 192.168.0.1
3 351 ms 296 ms * 10.23.48.1

2 2 ms 2 ms 2 ms 192.168.0.1
3 415 ms * 95 ms 10.23.48.1

The symptoms seen between CMTS and CAM are symptomatic of the loss between CMTS and modem, the fact you managed 1 out of 5 where the CMTS responded ok doesn't prove an IP network issue.

Seeing as i have not got any sense from anyone on this problem will be going up a few levels tommorow to get it sorted.

its still bobbins between the rochdale ubr and manc core so will be using all of my charm and personality tommorow

Warning Eng on warpath

__________________

Tracing route to spc1-roch1-6-0-gw.bagu.broadband.ntl.com [81.100.143.1]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.0.1
3 17 ms 10 ms 14 ms spc1-roch1-6-0-gw.bagu.broadband.ntl.com [81.100
.143.1]

Trace complete.

tracert www.ntlworld.com

Tracing route to www.ntlworld.com [62.253.162.30]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.0.1
3 9 ms 9 ms 70 ms 10.23.48.1
4 16 ms 13 ms 10 ms oldh-t2cam1-a-v115.inet.ntl.com [80.5.164.61]
5 123 ms 183 ms 122 ms mant-t2core-a-ge-wan62.inet.ntl.com [213.104.242
.41]
6 * 75 ms 80 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
7 11 ms 11 ms 25 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 36 ms 21 ms 107 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

9 * 158 ms 282 ms win-dc-a-v903.inet.ntl.com [213.105.174.34]
10 372 ms 183 ms 178 ms www.ntlworld.com [62.253.162.30]

Trace complete.

TOTAL BOBBINS OF A SERVICE

Raistlin · 25-05-2005, 22:14

Quote:

Originally Posted by th'engineer

Seeing as i have not got any sense from anyone on this problem will be going up a few levels tommorow to get it sorted.

Now that's a bit harsh.....

th'engineer · 25-05-2005, 22:20

Quote:

Originally Posted by Raistlin

Now that's a bit harsh.....

Unfortunateley its the only way given them a good few days to sort it since its been reported

this is ridiculous
7 305 ms 339 ms 164 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]

Raistlin · 25-05-2005, 23:32

Quote:

Originally Posted by th'engineer

Unfortunateley its the only way given them a good few days to sort it since its been reported

this is ridiculous
7 305 ms 339 ms 164 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]

Sorry, thought you were talking about the response you had received here didn't realise you meant the response from NTL. My bad.....

Florence · 26-05-2005, 07:21

Quote:

Originally Posted by th'engineer

Unfortunateley its the only way given them a good few days to sort it since its been reported

this is ridiculous
7 305 ms 339 ms 164 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]

I tried a few tracerts and didn't seem to get the same man core as you all seem to be working well here today.

Quote:

Tracing route to www.vispa.co.uk [62.24.228.26]
over a maximum of 30 hops:

1 8 ms 8 ms 8 ms 10.11.32.1
2 8 ms 8 ms 10 ms oldh-t2cam1-a-ge-wan51-120.inet.ntl.com [80.5.16
4.81]
3 10 ms 9 ms 13 ms mant-t2core-a-ge-wan64.inet.ntl.com [213.104.242
.53]
4 9 ms 9 ms 10 ms man-bb-a-so-210-0.inet.ntl.com [213.105.174.18]

5 10 ms 10 ms 10 ms 212.187.137.1
6 11 ms 25 ms 19 ms 194.168.63.129
7 9 ms 9 ms 8 ms 62.24.228.26

th'engineer · 26-05-2005, 08:17

thanks kits am trying to get it sorted at this moment in time. Taking into account what Ignition says looks like it could take ages.

I am trying a new approach trying to keep quiet on the edge of the forum but NTL are not helping.
All I am getting is why is the internet always breaking of the kids when i get in from work.

27-05-2005, 15:10

Quote:

Originally Posted by th'engineer

thanks kits am trying to get it sorted at this moment in time. Taking into account what Ignition says looks like it could take ages.

I am trying a new approach trying to keep quiet on the edge of the forum but NTL are not helping.
All I am getting is why is the internet always breaking of the kids when i get in from work.

So how did you get on when Andy called today ?

Florence · 27-05-2005, 15:37

would say its sorted what ever was wrong or you have something between you and this 305 ms 339 ms 164 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178] causing the problem.

Quote:

Tracing route to man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
over a maximum of 30 hops:

1 11 ms 10 ms 11 ms 10.11.32.1
2 15 ms 11 ms 10 ms oldh-t2cam1-b-ge-wan51-120.inet.ntl.com [80.5.16
4.209]
3 10 ms 12 ms 10 ms mant-t2core-b-ge-wan64.inet.ntl.com [213.104.242
.181]
4 9 ms 11 ms 8 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]

Trace complete.

Ignition · 27-05-2005, 18:26

Man-bb is not a router that's going to respond too well to pings, they are very low down on the list of priorities for it for security and other reasons.

Have tested the implicated link and it's performing fine, no work has been done on it as far as I'm aware.

27-05-2005, 18:30

Quote:

Originally Posted by Ignition

Man-bb is not a router that's going to respond too well to pings, they are very low down on the list of priorities for it for security and other reasons.

Have tested the implicated link and it's performing fine, no work has been done on it as far as I'm aware.

One of our Engineers visited th'engineer today.

Ignition · 27-05-2005, 18:31

*nod* local problem to him, thought as much.