Having problem with Wowway Internet?

Background

Recently we have been having to reboot our modem at least twice a day. I provided the modem logs in this superuser post and the answer said that it either noise in the cable or the street level repeater is going bad. I sent the modem log to Wowway along with the superuser post and asked if they have check their street level equipment.

Thank you for sharing your story. Your Ticket No. is 2767191.

Your story will not be served on a provider but will be shared internally to inform policy and potential enforcement. You will not receive any further communication from the FCC.

If you want to file an informal complaint that will be served on your provider, please go to www.consumercomplaints.fcc.gov and select a complaint category.
Your story provides the FCC with important information we can use to develop policies to protect consumers, remedy violations of the Communications Act, and encourage future compliance with the law.

Thank you for your help in furthering the FCC’s mission on behalf of consumers.

Below are my modem log results from a recent check:
Sep 10 2018 15:14:26 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:35 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:35 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:34 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:26 4-Error B603.0 Map Request Retry Timeout;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:25 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:25 4-Error B603.0 Map Request Retry Timeout;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:24 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:24 4-Error B603.0 Map Request Retry Timeout;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:23 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:22 4-Error B603.0 Map Request Retry Timeout;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:21 4-Error B603.0 Map Request Retry Timeout;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:20 4-Error B603.0 Map Request Retry Timeout;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0; Sep 10 2018 15:10:19 4-Error B603.0 Map Request Retry Timeout;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;

Timing of Service Interruptions

The service is usually fine until about 3 o’clock when kids come home from school and start using the web. For example today it was working without a hitch until 3 p.m. exactly and then I started seeing these types of entries in the modem logs:

September 13Sep 13 2018 17:37:02 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 13 2018 17:34:54 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 17:23:52 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 17:23:07 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 15:20:49 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 15:20:48 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;

Sep 13 2018 15:20:49 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 15:20:48 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 15:13:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 15:13:35 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;


Sep 13 2018 15:06:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 15:06:30 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 15:05:50 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 14:56:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 14:50:11 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 13 2018 14:49:29 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:62:69:f0:93:33;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;

Changed Modem

We also tried changing the modem, which Wow can see because they have to reassign the MAC Address. Shortly after changing it we see this in the logs:

Sep 15 2018 19:28:513-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 15 2018 19:24:493-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 15 2018 19:24:493-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 15 2018 19:24:483-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;

Continuous Log Updates

I’ll keep a journal of some of the log entries that occur everyday here in living document format (Curious as to how long it will actually take Wowway to provide helpful feedback). All of these log entries are coming from a new modem and the router was also replaced:

Oct 09 2018 22:40:433-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 09 2018 22:37:094-ErrorD101.0DHCP RENEW sent - No response for IPv4;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 09 2018 15:52:333-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 09 2018 14:42:564-ErrorD101.0DHCP RENEW sent - No response for IPv4;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 08 2018 09:16:274-ErrorD104.0DHCP REBIND WARNING - Field invalid in response;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 08 2018 09:16:094-ErrorD101.0DHCP RENEW sent - No response for IPv4;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;TimePriorityCodeMessageOct 06 2018 16:29:554-ErrorD104.0DHCP REBIND WARNING - Field invalid in response;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 06 2018 16:29:294-ErrorD101.0DHCP RENEW sent - No response for IPv4;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 04 2018 17:03:423-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 04 2018 05:13:585-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 04 2018 04:47:593-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 04 2018 04:29:013-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 04 2018 04:29:005-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 03 2018 15:22:013-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 03 2018 05:18:344-ErrorD104.0DHCP REBIND WARNING - Field invalid in response;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 03 2018 05:18:164-ErrorD101.0DHCP RENEW sent - No response for IPv4;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 01 2018 12:50:014-ErrorD104.0DHCP REBIND WARNING - Field invalid in response;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Oct 01 2018 12:49:434-ErrorD101.0DHCP RENEW sent - No response for IPv4;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 29 2018 20:43:514-ErrorD104.0DHCP REBIND WARNING - Field invalid in response;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 29 2018 20:43:294-ErrorD101.0DHCP RENEW sent - No response for IPv4;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 26 2018 04:45:403-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 26 2018 02:04:245-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 26 2018 01:59:293-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 26 2018 01:59:293-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 26 2018 01:59:283-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 25 2018 15:21:163-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 25 2018 15:17:253-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 25 2018 15:17:253-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 25 2018 15:17:233-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 25 2018 15:16:395-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 25 2018 15:22:003-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 25 2018 15:21:595-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 22 2018 01:17:363-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 22 2018 01:17:355-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CMSep 22 2018 01:16:483-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 22 2018 00:52:115-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;-VER=3.0;
Sep 22 2018 00:51:273-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 22 2018 00:46:353-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 21 2018 23:05:025-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 21 2018 23:04:193-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 21 2018 23:00:183-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 21 2018 22:59:293-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 21 2018 22:59:293-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 21 2018 22:59:283-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 21 2018 19:48:105-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 20 2018 14:27:333-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 20 2018 14:27:325-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2018 14:15:323-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 20 2018 14:11:293-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 20 2018 14:11:293-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 20 2018 14:11:273-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2018 12:29:443-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 19 2018 12:29:435-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 17 2018 11:41:563-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;Sep 17 2018 11:37:423-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d4:c3:4b;CMTS-MAC=00:01:5c:6b:be:4a;CM-QOS=1.1;CM-VER=3.0;

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ole Ersoy

Ole Ersoy

Founder of Firefly Semantics Corporation