Help with NTL CM Event log
 

Can anyone help decipher these errors?
I suspect connection problem with the NTL network rather than on my (ethernet) side.

Any comments and thoughts very welcome, I am suffering from frequent (70-80 each day) loss of connection. Anything from 2 seconds to 10 of minutes lost each time).

Time Not Established Time Not Established 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established 2 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 8 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 9 Critical(3) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 8 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 8 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 8 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out

Re: Help with NTL CM Event log
 

Have you contacted ntl TS ?

Re: Help with NTL CM Event log
 

BTW.
CM has been replaced, connections remade at house and distribution box, swap to another UBR, tap swapped in distribution box.
Concurrent with the CM problems (loss of SYNC and READY) I get a flashing light on the (SAmsung) set-top box. Does anyone know how to access the event log on the STB??

---------- Post added at 22:06 ---------- Previous post was at 22:05 ----------

I have contacted NTL, has three engineers so far, another one tomorrow. Each call is treated like a new one, getting sick of spending 30-40 minutes on the phone each time!

Re: Help with NTL CM Event log
 

Hi greyripper, :welcome:

Most of the above relate to the modem trying to scan and find a downstream to lock onto which it isnt.

No time stamp on any of them.

The 68000300 is from the DHCP server trying to send info which the modem is not understanding.

I think to access on the STB it is page up and page down.

However I think you may have to endure another engineer visit if your sync and ready lights are dropping then this would indicate by way of the sync light and the logs it is failing to lock onto the downstream.

Maybe your downstream power is fluctuating.

When the connection drops what are the power levels showing, take them from the first screen where you got the logs froms.

:D

Re: Help with NTL CM Event log
 

Downstream power is -2.8dBmV, I did a refresh and it showed -3.1, refreshed again -2.9, refreshed again -2.8. So it is fluctuating.
Upsteam is 44.0dBmV - but I assume this is irrelevant as it is just the transmit power of the CM?

Full text of the downstream page:-
Downstream Lock : Locked
Downstream Channel Id : 40
Downstream Frequency : 402750000 Hz
Downstream Modulation : QAM64
Downstream Symbol Rate : 5056.941 Ksym/sec
Downstream Interleave Depth : taps32Increment4
Downstream Receive Power Level : -3.1 dBmV
Downstream SNR : 37.2 dB

---------- Post added at 08:03 ---------- Previous post was at 07:55 ----------

Just polling the downstream page (refreshsing). Power is varying between
-2.5 and -3.1. Is bigger better (is -3.1 better than -2.5?)

Re: Help with NTL CM Event log
 

Some Information on levels can be found in here.

Re: Help with NTL CM Event log
 

Engineer has just called, and luckily the link was down when he arrived. He has confirmed an NTL network issue that he is escalating to network support. He couldn't even get a modem to lock-on in the distribution cabinet. It is up, for now (obviously as I am posting DUH!)