US Cable Support > Mediacom > [Cable HSI] IF you are having Modem reboots please post HERE!

[Cable HSI] IF you are having Modem reboots please post HERE!

Re: [Cable HSI] IF you are having Modem reboots please post HERE

reply to mike1965
Just so you have some more to compare to, here is mine from my topic.

2013-01-07 11:33:02 6-Notice I401.0 TLV-11 - unrecognized OID
2013-01-07 11:33:01 3-Critical D003.0 DHCP FAILED - Requested Info not supported.
2013-01-07 11:32:50 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2013-01-07 11:32:46 4-Error C216.0 DCC rejected parameter invalid for context
2013-01-07 11:32:44 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:29 3-Critical D003.0 DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:07 6-Notice M571.1 Ethernet link up - ready to pass packets
2013-01-07 11:32:04 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2013-01-07 11:32:04 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2013-01-07 11:31:32 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 11:31:21 4-Error C401.0 DCC-ACK not received
2013-01-07 11:31:20 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 11:31:20 4-Error C401.0 DCC-ACK not received
2013-01-07 11:31:18 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out


reply to mike1965
Jan 08 2013 15:41:54 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to MDD Loss ;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:41:11 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:40:47 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:39:29 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:34:40 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:34:39 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:34:17 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:32:55 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to MDD Loss ;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:31:36 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:31:12 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:27:36 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to MDD Loss ;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:17:03 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:17:02 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 08 2013 15:16:40 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 07 2013 22:58:47 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:17:10:03:ae:d9;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=00:23:74:f6:92:56;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

reply to mike1965
Here's what I was seeing on a SB5101U DOCSIS 2 modem:

2013-01-04 18:27:44 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2013-01-04 18:27:44 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2013-01-04 18:27:12 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-04 18:27:01 4-Error C401.0 DCC-ACK not received
2013-01-04 18:27:01 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-04 18:27:00 4-Error C401.0 DCC-ACK not received
2013-01-04 18:26:58 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
 

Here is mine on a motorola SB5101 modem.

2013-01-08 04:38:56 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2013-01-03 01:14:39 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2013-01-03 01:13:29 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2013-01-02 17:06:09 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-02 17:06:06 4-Error C401.0 DCC-ACK not received
2013-01-02 17:06:06 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-02 17:06:06 4-Error C401.0 DCC-ACK not received
2013-01-02 17:06:04 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-01 08:02:41 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2012-12-26 14:46:01 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:17 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2012-12-26 12:32:44 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:17 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.

reply to mike1965
same here. it is losing connection every few minutes.

:uhh:

2013-01-08 19:07:11 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:19 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2013-01-08 19:06:41 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2013-01-08 19:06:09 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-08 19:05:59 4-Error C401.0 DCC-ACK not received
2013-01-08 19:05:59 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-08 19:05:58 4-Error C401.0 DCC-ACK not received
2013-01-08 19:05:58 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-08 19:05:57 4-Error C401.0 DCC-ACK not received
2013-01-08 19:05:55 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-08 18:46:29 6-Notice I401.0 TLV-11 - unrecognized OID


reply to mike1965
Thanks guys, common theme going on here, if you do not mind when your issues get fixed please post what fixed it......

Thanks again

reply to postmortem
Algerardi and Portmortem,

If you want to send me your telephone# or MAC address I can take a look at this for you and see what we can find out.

My modem doesn not appear to be rebooting. My only observed issue is at night time around 11:00PM or later....the download speed and response is slow....which I imagine is due to more load on the node. I don't know what the errors mean......just thought I would throw it out there to see if it would help anybody.

reply to MediacomChad
MediacomChad,

I haven't had experienced any problems in last two days. Thanks.

reply to mike1965
I've been having this issue since October/November. At one time I had 4 techs at my house at one time. They changed out some wiring outside and the problem never went away. I'm at the point now where I'm about fed up and about to go to DSL in my area because what's the point of having a fast connection if it's not stable?

Tonight has been especially bad and went googling to see if I couldn't find anything online regarding this issue and found this forum post.

reply to postmortem
Good to hear! Let me know if you have any other issues.

CookMN, send me an IM with your account or phone number and I will be happy to look into this.

Sent you a PM/IM Chad - hopefully something can get fixed because if it doesn't clear up I will be forced to go with DSL (really don't want to).

Thank You! I assure you, I will do everything I can to get this resolved in a timely manner.