Intermittent disconnects: Rogers (Extreme)

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
I Plan to Stick Around
Posts: 19

Re: Intermittent disconnects: Rogers (Extreme)

hi @Datalink

Can you shed some light, am I having these issues?

 

No.TimeTypePriorityEvent
111/24/2017 17:38:4668010300errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
211/24/2017 18:55:0382000200criticalNo Ranging Response received - T3 time-out;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
311/25/2017 17:38:4668010300errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
411/25/2017 20:05:2582000200criticalNo Ranging Response received - T3 time-out;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
511/27/2017 17:38:4668010300errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
611/28/2017 13:47:0682000200criticalNo Ranging Response received - T3 time-out;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
711/29/2017 17:38:4668010300errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
811/29/2017 18:15:3984020200warningLost MDD Timeout;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
911/29/2017 18:25:0582000200criticalNo Ranging Response received - T3 time-out;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
1011/29/2017 18:50:0684020200warningLost MDD Timeout;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=yy:yy:yy:yy:yy:yy:12;CM-QOS=1.1;CM-VER=3.1;
1111/30/2017 11:54:5782000200criticalNo Ranging Response received - T3 time-out;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
1211/30/2017 17:38:4668010300errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
1311/30/2017 20:46:3890000000warningMIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
1411/30/2017 21:07:1484000500criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
1511/30/2017 21:07:1984020200warningLost MDD Timeout;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
1611/30/2017 21:07:4082000400criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
1711/30/2017 23:56:1890000000warningMIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
1812/03/2017 16:21:1282000200criticalNo Ranging Response received - T3 time-out;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
1912/03/2017 20:57:1690000000warningMIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;
2012/05/2017 02:56:2382000200criticalNo Ranging Response received - T3 time-out;CM-MAC=yy:yy:yy:yy:yy:yy;CMTS-MAC=00:17:10:91:68:12;CM-QOS=1.1;CM-VER=3.1;