Mobistar router met veel "critical" errors en soms een reboot
Geplaatst: 28 apr 2016, 16:45
Het internet van Mobistar valt soms weg, en als we naar de logs kijken, dan zien we heel wat errors. Ik weet niet als het een probleem is met de router zelf, als het een probleem is met de binnenkomende coax, of als het de verbinding met de Fritz!Box is die voor de problemen zorgt (we hebben een Fritz!Box via powerline ethernet moeten verbinden om een deftig WiFi signaal te krijgen).
Iemand een idee als de fout bij mij of bij Mobistar ligt?
Code: Selecteer alles
Status
DOCSIS Acquire Downstream Channel Done
Obtain Upstream Parameters Done
Cable Modem DHCP Done
Establish Time Of Day (TOD) Done
Cable Modem TFTP Done
Register Connection Done
Cable Modem Status operational
Initialize Baseline Privacy Done
Current Time and Date 2016-04-28 15:29:01
System Up Time 0day(s)0h:39m:38s
Code: Selecteer alles
Signals
Downstream Heading Channel Value
Channel ID 6 5 7 8 1 2 3 4
Frequency 442000000 434000000 450000000 458000000 402000000 410000000 418000000 426000000
Signal to Noise Ratio (SNR) 37 37 37 37 37 38 38 38
QAM - Downstream Modulation 256qam 256qam 256qam 256qam 256qam 256qam 256qam 256qam
Upstream Heading Channel Value
Channel ID 40 20 30 10
Frequency 38900000 52500000 45700000 59300000
Ranging Service ID 7426 7426 7426 7426
Symbol Rate 2.560 5.120 5.120 5.120
Power Level (dBmV) 36 33 33 33
Ranging Status success success success success
Upstream Modulation 64qam 64qam 64qam 16qam
Power Level (dBmV) 5 5 5 5 6 6 6 6
Signal Stats Heading Channel Value
Channel ID 6 5 7 8 1 2 3 4
Total Unerrored Codewords 100869048 101367426 101357773 101379672 83485420 100657944 82868088 100850673
Total Correctable Codewords 8937 9673 8864 8893 4776 7404 5370 7670
Total Uncorrectable Codewords 31533 33954 35441 34888 20942 32205 21217 31382
Code: Selecteer alles
Logs
Time Priority Code Message
2016-04-28 15:41:45 critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 15:33:21 critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 15:33:21 critical R03.0 Ranging Request Retries exhausted;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 15:33:20 critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 14:50:55 information B401.0 Authorized;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 14:48:50 critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 14:48:44 warning T202.0 Lost MDD Timeout;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 14:48:43 critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 14:48:43 warning T202.0 Lost MDD Timeout;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 14:48:20 critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 14:48:20 critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 14:36:40 warning T202.0 Lost MDD Timeout;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 14:36:19 critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 11:35:08 information B401.0 Authorized;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;
2016-04-28 11:32:56 critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:53:7c:71:de:4f;CMTS-MAC=00:17:10:87:a9:61;CM-QOS=1.1;CM-VER=3.0;