CM700 Modem - Downgraded services

[TheTwinky]

Fireware Verison: V1.01.09 (as supported by my ISP) 

My home ISP is saying the reason why I'm recieving downgraded services is because my modem is at fault. The issues happen once a month for about a week. I bought the CM700 Modem in Feb of this year. I know a bit about computers, but networking is where I lack. I went into my event logs and i was wondering if someone that explain these events showing up. Any help would be useful thank you.

Time	Priority	Description
Jul 22 2017 12:58:51	Critical (3)	No Ranging Response received - T3 time-out
Jul 22 2017 12:58:51	Critical (3)	No Ranging Response received - T3 time-out
Jul 22 2017 12:58:51	Critical (3)	No Ranging Response received - T3 time-out
Jul 22 2017 13:00:34	Warning (5)	Lost MDD Timeout
Jul 23 2017 14:08:50	Critical (3)	No Ranging Response received - T3 time-out
Jul 23 2017 14:09:40	Warning (5)	Lost MDD Timeout
Jul 24 2017 14:45:26	Critical (3)	No Ranging Response received - T3 time-out
Jul 24 2017 14:47:35	Warning (5)	Lost MDD Timeout
Jul 25 2017 04:00:03	Critical (3)	No Ranging Response received - T3 time-out
Jul 25 2017 18:01:00	Warning (5)	Lost MDD Timeout
Jul 25 2017 23:09:44	Critical (3)	No Ranging Response received - T3 time-out
Jul 25 2017 23:10:14	Warning (5)	Lost MDD Timeout
Jul 27 2017 00:10:52	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync
Jul 27 2017 00:10:56	Warning (5)	Lost MDD Timeout
Jul 27 2017 00:11:45	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jul 27 2017 00:31:52	Critical (3)	No Ranging Response received - T3 time-out
Jul 27 2017 00:32:40	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 27 2017 00:32:40	Notice (6)	TLV-11 - unrecognized OID
Jul 27 2017 00:32:41	Warning (5)	RCS Partial Service
Jul 27 2017 00:38:35	Warning (5)	Lost MDD Timeout
Jul 27 2017 10:04:38	Critical (3)	No Ranging Response received - T3 time-out
Jul 27 2017 10:05:16	Warning (5)	Lost MDD Timeout
Jul 27 2017 19:08:05	Critical (3)	No Ranging Response received - T3 time-out
Jul 27 2017 19:08:43	Warning (5)	Lost MDD Timeout
Jul 28 2017 04:19:15	Critical (3)	No Ranging Response received - T3 time-out
Jul 28 2017 04:37:34	Warning (5)	Lost MDD Timeout
Jul 29 2017 02:55:30	Critical (3)	No Ranging Response received - T3 time-out
Jul 29 2017 02:56:08	Warning (5)	Lost MDD Timeout
Jul 29 2017 14:25:13	Critical (3)	No Ranging Response received - T3 time-out
Jul 29 2017 14:25:17	Warning (5)	Lost MDD Timeout
Jul 29 2017 19:40:40	Critical (3)	No Ranging Response received - T3 time-out
Jul 29 2017 19:40:41	Warning (5)	Lost MDD Timeout
Jul 30 2017 15:13:23	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 30 2017 15:13:23	Notice (6)	TLV-11 - unrecognized OID
Jul 30 2017 15:13:25	Warning (5)	RCS Partial Service
Jul 30 2017 15:19:49	Warning (5)	Lost MDD Timeout
Jul 30 2017 15:28:03	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 30 2017 15:28:03	Notice (6)	TLV-11 - unrecognized OID
Jul 30 2017 15:28:04	Warning (5)	RCS Partial Service
Jul 30 2017 15:28:40	Warning (5)	Lost MDD Timeout
Jul 30 2017 16:05:15	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 30 2017 16:05:15	Notice (6)	TLV-11 - unrecognized OID

[DarrenM]

Hello TheTwinky

You have alot of T3 timeouts which is typically a issue with the ISP cable lines.

Explanation: The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request.

DarrenM