Kabel Helpdesk Forum :: Thema anzeigen

Count Time ID Level Description
63 Fri Feb 05 20:48:03 2016 73040100 Notice (6) TLV-11 - unrecognized OID;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Fri Feb 05 20:47:59 2016 2436694064 Notice (6) WiFi Interface [] on DFS Channel DFS State:
3 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
1 Fri Feb 05 07:30:01 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
5 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
1 Thu Feb 04 06:43:48 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
3 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
1 Mon Feb 01 07:52:14 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
4 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
1 Sun Jan 31 05:30:49 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
22 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
9 Fri Jan 15 21:53:09 2016 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Tue Jan 12 12:26:05 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
30 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
1 Mon Jan 04 17:17:13 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
9 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
1 Sun Jan 03 06:52:47 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Mon Dec 28 20:54:23 2015 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
8 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
1 Fri Dec 25 13:11:26 2015 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
9 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
1 Sat Dec 19 23:22:54 2015 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
35 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
1 Tue Dec 01 10:17:08 2015 82000300 Critical (3) Ranging Request Retries exhausted;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Tue Dec 01 10:17:08 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Tue Dec 01 10:17:02 2015 82000300 Critical (3) Ranging Request Retries exhausted;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
4 Tue Dec 01 10:17:02 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Tue Dec 01 10:16:59 2015 82000300 Critical (3) Ranging Request Retries exhausted;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
46 Tue Dec 01 10:16:59 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Tue Dec 01 10:16:02 2015 68000100 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
4 Tue Dec 01 10:15:44 2015 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Tue Dec 01 10:13:27 2015 82000800 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Tue Dec 01 10:13:27 2015 82000300 Critical (3) Ranging Request Retries exhausted;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
27 Tue Dec 01 10:13:27 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
4 Tue Dec 01 10:12:10 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
1 Tue Dec 01 10:12:01 2015 84000500 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0;
3 Tue Dec 01 10:11:54 2015 68000100 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
2 Tue Dec 01 10:11:19 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
7 Tue Dec 01 10:11:15 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;
7 Tue Dec 01 10:10:53 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;

Autor:	sascha_f [ Di 9. Feb 2016, 15:11 ]
Betreff des Beitrags:	Fehler des EPC3208 ?
Hallo zusammen, nachdem ich jetzt seit einem halben Jahr versuche mein Problem selbst zu lösen, hoffe ich auf ein hilfreiches Feedback hier im Forum. Die Hotline kann und will mir wohl nicht helfen - sind auch technisch überfordert - denke ich. Entsprechend (nach wiederholten und wenig hilfreichen bis unfreundlichen telefonischen Anfragen meinerseits bei der Kunden-Hotline) versuche ich es noch mal auf diesem Wege. Zu meinem Problem: In unregelmäßigen Abständen kann der Router (FB 7270) das Modem (CISCO EPC3208) nicht erreichen. Dabei ist das Modem nicht per http (http://192.168.100.1), ja nicht mal mehr per Ping (192.168.100.1) zu erreichen. Unabhängig ob es über das LAN - also über den Router - oder per direkter Verbindung zwischen PC und Modem probiert wird. Erst ein Neustart des Modems (aus- und wieder einschalten) ermöglicht ein Wiederherstellen der Internetverbindung. Die VoIP-Funktion steht allerdings auch zum Zeitpunkt einer Störung zur Verfügung. Ich habe inzwischen die Kabel und den Router (gegen eine anderen FB eines Freundes) getauscht. Leider ohne Erfolgt. Von der Hotline bekomme ich immer nur die Antwort "die Leitung zum Modem sieht gut aus - mehr können wir nicht tun". Selbst den Unterschied zwischen WLAN, LAN und WAN habe ich vergeblich versucht zu klären, da die Diskussion immer wieder darum ging, ob ich per WLAN oder LAN auf das Internet zugreife. Aus meiner Sicht ist das vollkommen egal, das der Router die Verbindung zum Modem nicht herstellen kann, egal ob ich mich per LAN oder per WLAN an meinen Router wende. Ein ping geht nicht durch - auch wenn ich das Kabel vom Modem direkt an den PC anschließe geht kein Ping durch. Als ob der TCP/IP-Stack des Modems einfach nicht mehr funktioniert. Derzeit ist es unter umständen so, dass ich mehrmals am Tag/in einer Stunde in den Keller muss um die Verbindung zum Internet wieder herzustellen. Ich vermute einen Defekt im Modem (kalte Lötstelle o.ä.) und sehe als letzte Möglichkeit den Tausch des Cisco Modems, da alle anderen Komponenten inzwischen schon getauscht wurden. Das ist lt. Hotline aber nicht möglich. Ich protokolliere zwar fleißig meine Ausfälle, aber das ist nett damit ich sehe wann ich mal wieder in den Keller musste - mehr aber auch nicht. Kurze Info noch zum Modem: Model: Cisco EPC3208 Vendor: Cisco Hardware Revision: 1.0 Bootloader Revision: 2.3.1_R3 Current Software Revision: e3200-E10-5-v302r125562-130611c_upc Firmware Name: e3200-E10-5-v302r125562-130611c_upc.bin Firmware Build Time: Jun 19 17:34:31 2013 Für Hinweise bin ich dankbar! Gruß Sascha

Autor:	Nutella [ Di 9. Feb 2016, 16:02 ]
Betreff des Beitrags:	Re: Fehler des EPC3208 ?
Kannst du dich mal auf das Modem versuchen einzuloggen und das Systemlog posten? Manuel

Autor:	sascha_f [ Di 9. Feb 2016, 17:17 ]
Betreff des Beitrags:	Re: Fehler des EPC3208 ?
Ich kann kurz das DOCSIS Log posten - oder gibt es da noch ein System-Log woanders? Code: Count Time ID Level Description 63 Fri Feb 05 20:48:03 2016 73040100 Notice (6) TLV-11 - unrecognized OID;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Fri Feb 05 20:47:59 2016 2436694064 Notice (6) WiFi Interface [] on DFS Channel DFS State: 3 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 1 Fri Feb 05 07:30:01 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 5 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 1 Thu Feb 04 06:43:48 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 3 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 1 Mon Feb 01 07:52:14 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 4 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 1 Sun Jan 31 05:30:49 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 22 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 9 Fri Jan 15 21:53:09 2016 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Tue Jan 12 12:26:05 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 30 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 1 Mon Jan 04 17:17:13 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 9 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 1 Sun Jan 03 06:52:47 2016 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Mon Dec 28 20:54:23 2015 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 8 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 1 Fri Dec 25 13:11:26 2015 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 9 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 1 Sat Dec 19 23:22:54 2015 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 35 Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 1 Tue Dec 01 10:17:08 2015 82000300 Critical (3) Ranging Request Retries exhausted;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Tue Dec 01 10:17:08 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Tue Dec 01 10:17:02 2015 82000300 Critical (3) Ranging Request Retries exhausted;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 4 Tue Dec 01 10:17:02 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Tue Dec 01 10:16:59 2015 82000300 Critical (3) Ranging Request Retries exhausted;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 46 Tue Dec 01 10:16:59 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Tue Dec 01 10:16:02 2015 68000100 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 4 Tue Dec 01 10:15:44 2015 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Tue Dec 01 10:13:27 2015 82000800 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Tue Dec 01 10:13:27 2015 82000300 Critical (3) Ranging Request Retries exhausted;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 27 Tue Dec 01 10:13:27 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 4 Tue Dec 01 10:12:10 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 1 Tue Dec 01 10:12:01 2015 84000500 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.1;CM-VER=3.0; 3 Tue Dec 01 10:11:54 2015 68000100 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 2 Tue Dec 01 10:11:19 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 7 Tue Dec 01 10:11:15 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0; 7 Tue Dec 01 10:10:53 2015 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:a2:4a:3f:48:79;CMTS-MAC=60:73:5c:72:64:b4;CM-QOS=1.0;CM-VER=3.0;

Kabel Helpdesk Forum https://forum.kabel-helpdesk.de/

Fehler des EPC3208 ? https://forum.kabel-helpdesk.de/viewtopic.php?f=20&t=7548	Seite 1 von 1

Seite 1 von 1	Alle Zeiten sind UTC + 1 Stunde [ Sommerzeit ]
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/