Cable Forum - View Single Post

jvn · 03-09-2005, 21:18

Hi again

Just tried the 192.168.100.1 cable modem diagnostic access and get the following info, copy & pasted from the browser window. Interestingly there are several entries all around 2pm yesterday in the event log which is the time everything went pear-shaped...

Does anyone out there know enough about these event logs to determine what might have happened?

thanks again in advance...

Cable Modem Status

Procedure Status Comment

Acquire Downstream Channel 482750000 Hz In Progress

Connectivity State In Progress Not Synchronized

Boot State In Progress Unknown

Security Disabled Disabled

Downstream Status

Downstream Lock : Not Locked

Downstream Frequency : 818000000 Hz

Downstream Modulation : unknown

Downstream Interleave Depth : ???

Downstream Receive Power Level : -1.8 dBmV

Downstream SNR : 0.0 dB

Upstream Status

Upstream Channel ID : 0

Upstream Transmit Power Level : 8.0 dBmV

Upstream Symbol Rate : 0 Ksym/sec

Upstream Frequency : 0 Hz

Upstream Mini-Slot Size : 0

Event Log

Index First Time Last Time Counts Level ID Text

1 Time Not Established THU NOV 25 13:32:52 2004 820Critical (3) 82000200 No Ranging Response received - T3 time-out

2 Time Not Established THU NOV 25 13:32:47 2004 40Critical (3) 82000300 Init RANGING Critical Ranging Request Retries exhausted

3 WED JUN 09 13:46:41 2004 FRI SEP 02 14:08:37 2005 48 Critical (3) 84000500 SYNC Timing Synchronization failure - Loss of Sync

4 WED JUN 09 13:46:51 2004 FRI SEP 02 14:08:57 2005 41 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

5 WED JUN 09 13:47:01 2004 FRI SEP 02 14:09:07 2005 31 Critical (3) 85000100 No UCD's Received - Timeout

6 WED JUN 09 14:52:51 2004 WED JUN 09 15:08:55 2004 83 Critical (3) 68000100 DHCP FAILED - Discover sent, no offer received

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

8 WED AUG 04 20:17:39 2004 WED AUG 31 05:23:38 2005 2313 Critical (3) 82000500 Started Unicast Maintenance Ranging - No Response received - T3 time-out

9 TUE MAY 10 01:14:30 2005 TUE MAY 10 01:14:30 2005 1 Critical (3) 73000200 REG RSP not received

10 Time Not Established Time Not Established 93035Notice (6) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

11 Time Not Established Time Not Established 2 Notice (6) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC framing

03-09-2005, 21:18	#6
jvn Inactive Join Date: Sep 2005 Posts: 5	Re: NTL cable modem died? Hi again Just tried the 192.168.100.1 cable modem diagnostic access and get the following info, copy & pasted from the browser window. Interestingly there are several entries all around 2pm yesterday in the event log which is the time everything went pear-shaped... Does anyone out there know enough about these event logs to determine what might have happened? thanks again in advance... Cable Modem Status Procedure Status Comment Acquire Downstream Channel 482750000 Hz In Progress Connectivity State In Progress Not Synchronized Boot State In Progress Unknown Security Disabled Disabled Downstream Status Downstream Lock : Not Locked Downstream Frequency : 818000000 Hz Downstream Modulation : unknown Downstream Interleave Depth : ??? Downstream Receive Power Level : -1.8 dBmV Downstream SNR : 0.0 dB Upstream Status Upstream Channel ID : 0 Upstream Transmit Power Level : 8.0 dBmV Upstream Symbol Rate : 0 Ksym/sec Upstream Frequency : 0 Hz Upstream Mini-Slot Size : 0 Event Log Index First Time Last Time Counts Level ID Text 1 Time Not Established THU NOV 25 13:32:52 2004 820Critical (3) 82000200 No Ranging Response received - T3 time-out 2 Time Not Established THU NOV 25 13:32:47 2004 40Critical (3) 82000300 Init RANGING Critical Ranging Request Retries exhausted 3 WED JUN 09 13:46:41 2004 FRI SEP 02 14:08:37 2005 48 Critical (3) 84000500 SYNC Timing Synchronization failure - Loss of Sync 4 WED JUN 09 13:46:51 2004 FRI SEP 02 14:08:57 2005 41 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout 5 WED JUN 09 13:47:01 2004 FRI SEP 02 14:09:07 2005 31 Critical (3) 85000100 No UCD's Received - Timeout 6 WED JUN 09 14:52:51 2004 WED JUN 09 15:08:55 2004 83 Critical (3) 68000100 DHCP FAILED - Discover sent, no offer received 7 Time Not Established Time Not Established 51 Critical (3) 68000300 DHCP WARNING - Non-critical field invalid in response. 8 WED AUG 04 20:17:39 2004 WED AUG 31 05:23:38 2005 2313 Critical (3) 82000500 Started Unicast Maintenance Ranging - No Response received - T3 time-out 9 TUE MAY 10 01:14:30 2005 TUE MAY 10 01:14:30 2005 1 Critical (3) 73000200 REG RSP not received 10 Time Not Established Time Not Established 93035Notice (6) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 11 Time Not Established Time Not Established 2 Notice (6) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC framing