Grrrrrr. Need some help or info plz

Originally Posted by BBKing

Being a confounded lunatic I'm VPN'd into work on the first day of my week off and can confirm my tools show no upstream congestion anywhere in Runcorn, (yes, we actually have perfectly good areas). I'd therefore suspect a local HFC issue.

Switching upstreams is something only high-level network techs (RF or IP) can do.

Hi, Bill, how's it going?

Not bad m8 and you

[jimbowen03]

Pinging www.ntlworld.com [62.253.162.30] with 32 bytes of data:

Reply from 62.253.162.30: bytes=32 time=14ms TTL=247
Reply from 62.253.162.30: bytes=32 time=25ms TTL=247
Reply from 62.253.162.30: bytes=32 time=14ms TTL=247
Reply from 62.253.162.30: bytes=32 time=16ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=14ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=14ms TTL=247
Request timed out.
Request timed out.
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=25ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Request timed out.
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=80ms TTL=247
Request timed out.
Request timed out.
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=14ms TTL=247
Reply from 62.253.162.30: bytes=32 time=14ms TTL=247
Reply from 62.253.162.30: bytes=32 time=14ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=16ms TTL=247
Request timed out.
Reply from 62.253.162.30: bytes=32 time=14ms TTL=247
Request timed out.
Reply from 62.253.162.30: bytes=32 time=24ms TTL=247
Reply from 62.253.162.30: bytes=32 time=14ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Request timed out.
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247
Reply from 62.253.162.30: bytes=32 time=15ms TTL=247



Hope this is what u meant :S I'm a bit of a noooooooooob :P

[rdhw]

Originally Posted by jimbowen03

System up time                       = 0 days 09h 39m 09.00s
Ethernet carrier sense xmit errs.1   = 36
Downstream channel ID                = 1
Downstream channel frequency         = 586750000 Hz
Downstream received signal power     = 1.4 dBmV
Upstream channel ID                  = 1
Upstream channel frequency           = 33584000 Hz
QoS max upstream bandwidth           = 128000 bps
QoS max downstream bandwidth         = 600000 bps
SigQu: Signal to Noise Ratio         = 34.6 dB
Cable modem status                   = Operational
Upstream transmit signal power       = 38.5 dBmV
Date and Time                        = 2003-11-23,20:18:00.0
Configuration filename               = ntlhm120-silver.cm

These figures for signal levels are fine in themselves, but I'd like to see some of the other diagnostic counters that can be obtained by using the -v option of DocsDiag. These might reveal whether there are any error-corrections or retransmissions going on.

[Ignition]

Originally Posted by rdhw

These figures for signal levels are fine in themselves, but I'd like to see some of the other diagnostic counters that can be obtained by using the -v option of DocsDiag. These might reveal whether there are any error-corrections or retransmissions going on.

RDHW - Could you PM me when you have some time, would like to 'pick your brain' about something. Thank you.

Have seen symptoms similar to the above, however in the previous case ping 'spikes' rather than outright timeouts were observed.

[jimbowen03]

Certainly seems a lot better.

What u reckon to these new tracert results ?

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.0.1
2 6 ms 7 ms 8 ms 10.51.80.1
3 9 ms 9 ms 8 ms bagu-t2cam1-b-ge-wan43-112.inet.ntl.com [80.5.16
2.177]
4 9 ms 8 ms 9 ms bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.13
7]
5 9 ms 9 ms 11 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
6 8 ms 9 ms 9 ms man-bb-a-so-700-0.inet.ntl.com [62.253.185.193]

7 9 ms 8 ms 14 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 15 ms 15 ms 15 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

9 16 ms 16 ms 15 ms win-dc-a-v902.inet.ntl.com [62.253.187.222]
10 15 ms 14 ms 17 ms www.ntlworld.com [62.253.162.30]

Trace complete.

Originally Posted by jimbowen03

Certainly seems a lot better.

What u reckon to these new tracert results ?

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.0.1
2 6 ms 7 ms 8 ms 10.51.80.1
3 9 ms 9 ms 8 ms bagu-t2cam1-b-ge-wan43-112.inet.ntl.com [80.5.16
2.177]
4 9 ms 8 ms 9 ms bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.13
7]
5 9 ms 9 ms 11 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
6 8 ms 9 ms 9 ms man-bb-a-so-700-0.inet.ntl.com [62.253.185.193]

7 9 ms 8 ms 14 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 15 ms 15 ms 15 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

9 16 ms 16 ms 15 ms win-dc-a-v902.inet.ntl.com [62.253.187.222]
10 15 ms 14 ms 17 ms www.ntlworld.com [62.253.162.30]

Trace complete.

Much better

[paulyoung666]

sweet baby , must be running a lot better is it

[jimbowen03]

Yep, it did go completely down lasnite for about 5 hours or so. Andi mean COMPLETELY down. LOL. But s'all good. Runnin sweet as a nut now.

[paulyoung666]

good to know , just shows if you ask then you get or was it a case of good timing , whatever your sorted

[zovat]

Originally Posted by jimbowen03

Yep, it did go completely down lasnite for about 5 hours or so. Andi mean COMPLETELY down. LOL. But s'all good. Runnin sweet as a nut now.

have a look at this thread (long !!) for info on what went on last night (looks like not just NTL had issues