Had a small outage earlier. Rang 150, automated message with "We are improving our network in your area". Oh good, perhaps being moved to a new CMTS. Anyway, connection has come back up but there's been no changes as far as I can tell. Oddly, there is two different CMTS MAC's in the network log. One a Cisco and the other a RiverDelta, which is the one that I think I'm still on. Not sure what's going on there.
Network Log
Date And Time Error Number Event Description
2017-04-20 10:17:50.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:a2:89:26:7d:61;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:18:45.00 82000900 B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=00:a2:89:26:7d:61;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:18:46.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:a2:89:26:7d:61;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:19:10.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=00:a2:89:26:7d:61;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:19:14.00 84020200 Lost MDD Timeout;CM-MAC=;CMTS-MAC=00:a2:89:26:7d:61;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:19:19.00 82000100 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=00:a2:89:26:7d:61;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:20:03.00 84020200 Lost MDD Timeout;CM-MAC=;CMTS-MAC=00:a2:89:26:7d:61;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:20:04.00 84020300 MDD message timeout;CM-MAC=;CMTS-MAC=00:a2:89:26:7d:61;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:20:17.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:21:21.00 68000100 DHCP FAILED - Discover sent, no offer received;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:21:52.00 84020200 Lost MDD Timeout;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:21:52.00 84020300 MDD message timeout;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:23:08.00 68000100 DHCP FAILED - Discover sent, no offer received;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:23:38.00 84020200 Lost MDD Timeout;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:23:38.00 84020300 MDD message timeout;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:23:51.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:24:10.00 84020200 Lost MDD Timeout;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:24:10.00 84020300 MDD message timeout;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:25:28.00 68000100 DHCP FAILED - Discover sent, no offer received;CM-MAC=;CMTS-MAC=00:0e:39:d2:28:01;CM-QOS=1.1;CM-VER=3.0;
2017-04-20 10:26:09.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:30:b8:d0:be:56;CM-QOS=1.1;CM-VER=3.0;
