New Contributor
•
1 Message
T3 time-out errors
I've noticed my connection being a little spotty lately, so I decided to dig around in my router/modem and check out the logs. I noticed I was getting multiple T3 time-out errors a day. The router/modem combo I use is a Netgear C3700-100NAS. Here's the logs from yesterday:
| Time | Priority | Description |
| 2017-11-4, 10:00:52 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:00:53 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:02:25 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:02:27 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:02:33 | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
| 2017-11-4, 10:02:35 | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:02:36 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:02:39 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:03:35 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:03:40 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:03:45 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:05:08 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:05:09 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:06:39 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:06:40 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:07:54 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:07:55 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:09:11 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:09:12 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:09:18 | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
| 2017-11-4, 10:09:22 | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:09:23 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:09:25 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:09:56 | Critical (3) | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:10:14 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:10:26 | Notice (6) | Received REG-RSP while in REG-HOLD1 state;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:10:27 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:10:32 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:12:27 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:12:29 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:14:02 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:14:04 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-4, 10:15:05 | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
| 2017-11-4, 10:15:07 | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:15:08 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 10:15:10 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-4, 22:53:19 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:7d:d3:f0;CMTS-MAC=50:57:a8:88:fc:78;CM-QOS=1.1;CM-VER=3.0; |
Here's the connection info from the router:
| Frequency start Value | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Startup Procedure | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Upstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I have the router plugged directly into the wall. The only splitter is the one that splits the incoming connection from outside. Would this be causing any problems? I've seen some people say that this is completely normal, and others think it is a problem. Thanks for any info!
No Responses!