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