Forum Discussion

ESmith's avatar
ESmith
New Contributor

Unreliable internet

Hello,

Last sunday (11 dec 2016) there was a cable television outage in this area.  Once that was fixed, the internet became unreliable.  The modem/router resets seemingly spontaneously.

Since then, I have reset the computer(s) attached to the router.  I have reset the modem.  I have left the router/modem unplugged for >5 minutes and plugged them back in.  I have tried leaving the homelife wireless router off of the modem.  A technician was dispatched and luckily the problem occurred while he was here.

He checked the health of the modem/router, checked the power levels and we looked over the netlog.

The router resets every time a TLV-11 unrecognized OID message occurs.  Once things come back, older notice(6) entries disappear from the netlog, which seems strange.

Below is a sample of today's log.  The modem has reset itself three times while typing this message.

It is my understanding that TLV-11 messages generally are harmless, but since every time the modem reset this occurs it makes me wonder.

I have  looked up the CMTS mac address and it indicates that the sender is a Cisco device of some sort.  The technician didn't have anything else he could do once investigating the router/modem health and finding it good.  There was the suggestion that the TLV-11 message was being sent from the wirless (WNR2000v5) connected to the modem for the homelife.  The MAC address doesn't match, however, and it has been unplugged and disconnected while I have been writing this message. 

I feel I am out of options at this point since all indications are the equipment is good, but obviously constant and random resets are not ideal.

Perhaps the modem needs to be re-provisioned?  I really don't know.

A phone rep did reset the modem remotely on sunday.

Time Priority Description
2016-12-14, 16:48:18.0 Notice (6) TLV-11 - unrecognized OID;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 16:44:59.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 16:38:31.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 16:13:14.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 15:26:25.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 15:25:45.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 14:57:35.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 10:41:41.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 08:39:20.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 04:15:15.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-14, 03:31:17.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 23:37:49.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 22:34:05.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 22:33:25.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 20:05:03.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 19:12:20.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 18:11:52.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 18:06:39.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 18:01:59.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 17:26:48.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 17:22:05.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 15:36:27.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 09:48:08.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
2016-12-13, 07:46:02.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT
Time Not Established Notice (6) WiFi Interface [wl1] set to Channel 40 (Side-Band Channel:N/A) - Reason:INIT
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=50:6a:03:8b:67:78;CMTS-MAC=00:13:5f:00:41:dc;CM-QOS=1.0;CM-VER=3.0;

2 Replies

Replies have been turned off for this discussion
  • ChrisL's avatar
    ChrisL
    Former Moderator
    @ESmith

    The TLV-11 entries are basically non-events but the T4's suggest there is an intermittent signal or equipment issue somewhere. Are there any cable splitters you can try bypassing and seeing if that helps?

  • I guess I;m not alone on those problems..   Most awful service I ever experience!   Constant issues