modem errors

ace_vz · 12-04-2006, 00:54

anyone shed any light on these?

Code:

 First Time  Last Time  Counts  Level  ID  Text 
Sun Apr 09 14:29:23 2006   Sun Apr 09 14:29:23 2006    1  Critical(3)  82000500 Started Unicast Maintenance Ranging - No Response received - ...
Sun Apr 09 06:57:08 2006   Sun Apr 09 06:57:08 2006    1  Warning(5)  68010300 DHCP RENEW WARNING - Field invalid in response
Thu Apr 06 02:45:57 2006   Thu Apr 06 02:45:57 2006    1  Critical(3)  68000300 DHCP WARNING - Non-critical field invalid in response.
Thu Apr 06 02:45:48 2006   Thu Apr 06 02:45:48 2006    1  Critical(3)  82000200 No Ranging Response received - T3 time-out
Thu Apr 06 02:37:44 2006   Thu Apr 06 02:37:44 2006    1  Critical(3)  82000400 Received Response to Broadcast Maintenance Request, But no Un...
Wed Apr 05 11:07:30 2006   Wed Apr 05 11:07:30 2006    1  Warning(5)  68010300 DHCP RENEW WARNING - Field invalid in response
Mon Apr 03 15:16:18 2006   Mon Apr 03 15:16:18 2006    1  Critical(3)  68000300 DHCP WARNING - Non-critical field invalid in response.
Mon Apr 03 15:16:11 2006   Mon Apr 03 15:16:11 2006    1  Critical(3)  82000200 No Ranging Response received - T3 time-out
Mon Apr 03 15:15:05 2006   Mon Apr 03 15:15:05 2006    1  Critical(3)  82000400 Received Response to Broadcast Maintenance Request, But no Un...
Sat Apr 01 22:13:28 2006   Sat Apr 01 22:13:28 2006    2  Critical(3)  82000500 Started Unicast Maintenance Ranging - No Response received - ...
Fri Mar 31 06:55:30 2006   Fri Mar 31 06:55:30 2006    1  Warning(5)  68010300 DHCP RENEW WARNING - Field invalid in response
Wed Mar 29 21:51:05 2006   Wed Mar 29 21:51:05 2006    4  Critical(3)  82000500 Started Unicast Maintenance Ranging - No Response received - ...
Mon Mar 27 18:55:30 2006   Mon Mar 27 18:55:30 2006    1  Warning(5)  68010300 DHCP RENEW WARNING - Field invalid in response
Sun Mar 26 15:51:01 2006   Sun Mar 26 15:51:01 2006    5  Critical(3)  82000500 Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established  Time Not Established   1  Critical(3)  68000300 DHCP WARNING - Non-critical field invalid in response.
Thu Apr 06 02:45:43 2006   Thu Apr 06 02:45:43 2006    11987  Critical(3)  84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Fri Mar 24 12:33:05 2006   Fri Mar 24 12:33:05 2006    1  Critical(3)  82000400 Received Response to Broadcast Maintenance Request, But no Un...
Time Not Established  Time Not Established   1  Critical(3)  68000300 DHCP WARNING - Non-critical field invalid in response.
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)  82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established  Time Not Established   17  Critical(3)  82000200 No Ranging Response received - T3 time-out
Time Not Established  Time Not Established   1  Critical(3)  82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established  Time Not Established   17  Critical(3)  82000200 No Ranging Response received - T3 time-out
Time Not Established  Time Not Established   510  Critical(3)  84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established  Time Not Established   1  Critical(3)  82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established  Time Not Established   17  Critical(3)  82000200 No Ranging Response received - T3 time-out
Time Not Established  Time Not Established   1  Critical(3)  82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established  Time Not Established   17  Critical(3)  82000200 No Ranging Response received - T3 time-out
Time Not Established  Time Not Established   1  Critical(3)  82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established  Time Not Established   17  Critical(3)  82000200 No Ranging Response received - T3 time-out
Time Not Established  Time Not Established   1  Critical(3)  82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established  Time Not Established   17  Critical(3)  82000200 No Ranging Response received - T3 time-out

James Henry · 12-04-2006, 02:27

Yep certainly.

Quote:

Time Not Established Time Not Established 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
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) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 510 Critical(3) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out

Modem is scanning downstream frequencies starting looking for a signal to lock on to, which it isn't finding. Looks as though these all happened at the same time as there is no time stamp there.

Quote:

Fri Mar 24 12:33:05 2006 Fri Mar 24 12:33:05 2006 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un.

It received an initial response from a device it was trying to synch up with, but was never offered the opportunity to talk back (it had locked a downstream signal and 'shouted' back and been acknowledged, but then it all broke down as it never saw an offer to talk back on its' own).

Quote:

Time Not Established Time Not Established 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.

Nothing to worry about a response from ntl's DHCP servers carried information that the modem didn't understand.

The rest of it is already covered, it's the modem losing its' synchronisation with ntl's equipment and then trying to recover it.

Your modem isn't the most stable beast, I have seen a lot better, though I've also seen a lot worse.