CG3000 - "Critical" Log beskeder

Hej.

 

Jeg prøver at hjælpe en stakkels TDC kunde med at få deres internet til at fungere ordentligt og stabilt. Er der mon nogen af jer der ved hvad disse logbeskeder betyder inde i admin interfacet på deres CG3000 Netgear router?

 

Specifikt gad jeg godt at vide om det kan konkluderes at det er enheder på lokalnetværket der genererer disse beskeder(jeg kan ikke finde nogen af deres computere med passende MAC adresser) - eller om dette er logs der genereres af routeren og dens forsøg på at snakke med TDCs backend(skal jeg have fat i en TDC tekniker og bede dem om at fixe problemet)?

 

Sat Oct 20 14:47:24 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:47:24 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:46:25 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:46:20 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:45:44 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:45:32 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:45:03 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:44:58 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:44:42 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:44:32 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:44:01 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:43:52 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:43:01 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:42:28 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:42:01 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:41:20 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:41:01 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:40:46 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:39:02 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:38:40 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:38:00 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:37:46 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:36:38 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:36:26 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:35:59 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:35:04 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:34:38 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:34:32 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:33:58 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:33:44 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:33:39 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;  Sat Oct 20 14:33:22 2012   Warning (5)  MDD message timeout;CM-MAC=2c:b0:5d🇦🇨f7:f0;CMTS-MAC=00:11:92:20:f8:ac;CM-QOS=1.1;CM-VER=3.0;