Basic Internet Connectivity And Modem Help

[Theother0]

I just read these threads and I decided to go and check my logs and this is what I found.

Do you think I should have a tech come out and take a look?

2011-09-15 01:41:46 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2011-09-15 01:41:35 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:41:28 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:41:28 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:40:43 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:40:43 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:40:08 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:40:08 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:39:30 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
timing 2011-09-15 01:39:26 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC
framing 2011-09-15 01:39:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
timing 2011-09-15 01:39:14 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC
framing 2011-09-15 01:39:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
timing 2011-09-15 01:39:12 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC
framing 2011-09-15 01:39:11 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
timing 2011-09-15 01:39:07 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:38:48 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:38:48 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:38:05 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:38:05 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:37:29 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:37:29 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:36:56 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:36:56 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:36:15 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:36:15 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:35:32 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:35:32 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:34:47 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:34:47 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:34:06 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:34:06 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:33:39 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:33:39 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:33:05 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:33:05 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:32:24 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:32:24 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:31:50 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
timing 2011-09-15 01:31:36 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC
framing 2011-09-15 01:31:36 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
timing 2011-09-15 01:31:36 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:31:36 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:30:55 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:30:55 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:30:20 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:30:20 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:29:46 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-15 01:29:46 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-15 01:29:10 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2011-09-15 01:29:05 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3
time-out 2011-09-14 22:47:53 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2011-09-14 22:47:50 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received 2011-09-14 22:47:34 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-14 22:47:15 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast
Maintenance opportunities received - T4 timeout 2011-09-14 22:47:15 3-Critical D002.0 DHCP FAILED - Request sent, No response 2011-09-14 22:44:36 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received 2011-09-14 22:43:56 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-14 22:43:42 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received 2011-09-14 22:40:25 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-14 22:40:08 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2011-09-14 22:39:31 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received 2011-09-14 22:38:22 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-14 22:38:01 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-14 22:38:01 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-14 22:37:23 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-14 22:37:23 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-14 22:36:50 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
timing 2011-09-14 22:36:48 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC
framing 2011-09-14 22:36:48 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
timing 2011-09-14 22:36:36 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC
framing 2011-09-14 22:36:36 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
timing 2011-09-14 22:36:36 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-14 22:36:36 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-14 22:35:48 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-14 22:35:48 3-Critical R002.0 No Ranging Response received - T3 time-out 2011-09-14 22:35:08 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 2011-09-14 22:35:08 3-Critical R002.0

No Ranging Response received - T3 time-out

[EG]

Are you actually having any problems ? What do your modem's signal stats look like ? Get them here; http://192.168.100.1

Please post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.

[tn38066]

found this site / to many reboots form timeouts

http://www.dslreports.com/faq/powerlink/3_Technical_Questions#8560

by swcox edited by MacLeech
last modified: 2005-11-16 09:43:23

FAQ: Modem log entries listing T-x timeouts and/or errors.

Basically a cable modem gets online this way:

The modem scans for a digital QAM channel (which can be digital TV or modem downstream channels) and "listens" for upstream channel descriptor (UCD) information on it (which is only found on modem downstream channels). If it doesn't get the UCD after a few seconds of receiving data on that channel, a T1 timeout occurs and the modem looks for another digital QAM channel.

Once the modem finds the correct downstream channel and receives the upstream channel descriptor, it then waits for its initial opportunity to "talk" to the CMTS. If it doesn't get that chance within 12 seconds, a T2 timeout occurs.

So during initial modem connections, T1 and T2 timeouts are perfectly normal to see in the modem logs.

After locating a downstream data carrier channel, the modem gets its chance to "talk" to the CMTS and sends data to negotiate the proper upstream signal levels and timing. This negotiation process takes several data exchanges between the cable modem and the CMTS. If at any point the modem doesn't receive a response from the CMTS within about 200 milliseconds, a T3 timeout occurs. Several T3s have to occur before a modem resets.

The modem then goes through the DHCP, TFTP, TOD processes and once all are completed the modem is online.

Once the modem is online, the CMTS sends "Periodic Ranging" or keep-alive requests to it every 30 seconds. If the modem doesn't receive one, a T4 timeout occurs. Once 16 of the T4 timeouts have to occurred, a modem resets.

If there is a downstream communication problem, the cable modem might not receive these "keep-alive requests". If the upstream utilization is too high, or too many modems are connected to the same upstream port, it is possible that some modems will not get the required bandwidth or transmit opportunities to respond to the keep-alive requests. Either of these issues can result in T3 or T4 timeouts occurring.

[EG]

Regardless of the technical reasons, the bottom line is that the stats need to be in spec which may indicate whether there is unimpeded communication between the system and the modem (which is imperative), that is why I asked to see them.