Unitymedia Häufiger Absturz von Cisco epc3212

[schranzer]

Hallo Ihr lieben,

bin neu auf Eurem Forum.

Kurze Vorstellung; bin 35 schon lange unitymediakunde und eigentlich begeistert, bis auf dauerhafte abstürze von meiner Internetleitung.

Bei ganz normalem surfen kommt es häufig vor dass ich zwar im Wlan bin, aber kein Internet vorhanden ist.

Das geht soweit, dass ich den Cisco und meine Fritzbox 7240 mittels stecker raus und rein wieder neustarten muss.

Durch euer Forum ist es mir gelungen mal in den cisco zu sehen und haben folgende LOGS siehe unten.

kann mir jemand verraten was ich tun kann? An meiner Fritzbox hängt es nicht. Die hat aktuellste Firmware und läuft gut.

falls ihr noch was braucht bitte bescheid geben.

Vielen Dank schonmal vorab.

Liebe Grüsse Thoms


Hier der LOG:



Time ID Level Description
Sun Jan 06 14:26:26 2013 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sun Jan 06 14:25:41 2013 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=60:2a:d0:3a...
Wed Jan 02 18:46:33 2013 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=60:2a:d0:3a...
Tue Jan 01 06:20:22 2013 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=60:2a:d0:3a...
Wed Oct 31 14:22:07 2012 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=60:2a:d0:3a...
Wed Oct 31 14:09:48 2012 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=60:2a:d0:3a...
Wed Oct 31 12:17:29 2012 2436694064 Critical (3) Booting up the cable modem
Mon Oct 29 00:05:35 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Oct 26 22:55:21 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Fri Oct 26 22:54:37 2012 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=60:2a:d0:3a...
Wed Sep 26 13:36:31 2012 84000400 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC S...
Wed Sep 26 13:14:18 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Wed Sep 26 13:14:16 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:52:49 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Wed Sep 26 12:52:04 2012 2436694064 Critical (3) Booting up the cable modem
Wed Sep 26 12:51:06 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Wed Sep 26 12:51:02 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:50:52 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Wed Sep 26 12:50:35 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:49:46 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Wed Sep 26 12:49:45 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:48:45 2012 2436694069 Critical (3) CISCO: RF disconnect,QAM lost.
Wed Sep 26 12:48:40 2012 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=60:2a:d0:3a...
Wed Sep 26 12:48:14 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Wed Sep 26 12:47:45 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:47:39 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:47:35 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Wed Sep 26 12:47:35 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:47:32 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:47:25 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:47:18 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:47:15 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Wed Sep 26 12:47:14 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Wed Sep 26 12:47:12 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...

 

[1AKA]

Wie sehen denn die Werte von deinem CM aus?

Vor allem die SNR im Upstream? ^^

 

[schranzer]

Hi,
danke dir für deine Antwort.

Leider versteh ich nicht ganz was du meinst....

ich geb dir mal die hauptseite...



Model: Cisco EPC3212
Vendor: Cisco
Hardware Revision: 1.0
MAC Address: 60:2a:d0:3a:e8:b2
Bootloader Revision: 2.3.0_R1
Current Software Revision: e3200-P10-5-v302r125533-110811c
Firmware Name: e3200-P10-5-v302r125533-110811c.bin
Firmware Build Time: Aug 11 20:17:30 2011
Cable Modem Status: Operational
Wireless Network:


Cable Modem State
DOCSIS Downstream Scanning: Completed
DOCSIS Ranging: Completed
DOCSIS DHCP: Completed
DOCSIS TFTP: Completed
DOCSIS Data Reg Complete: Completed
DOCSIS Privacy: Enabled

Downstream Channels
Power Level: Signal to Noise Ratio:
Channel 1: 5.8 dBmV 39.4 dB
Channel 2: 5.5 dBmV 39.4 dB
Channel 3: 6.6 dBmV 39.9 dB
Channel 4: 7.7 dBmV 40.0 dB
Channel 5: 0.0 dBmV 0.0 dB
Channel 6: 0.0 dBmV 0.0 dB
Channel 7: 0.0 dBmV 0.0 dB
Channel 8: 0.0 dBmV 0.0 dB

 

[Dinniz]

Wie sehen denn die Werte von deinem CM aus?

Vor allem die SNR im Upstream? ^^

Den Upstream SNR kann der Kunde nicht auslesn ..

 

[1AKA]

Wie sehen denn die Werte von deinem CM aus?

Vor allem die SNR im Upstream? ^^

Den Upstream SNR kann der Kunde nicht auslesn ..

Wat? Wassn das für'n rotz? xD

Verliert dein CM komplett die Verbindung? Oder ist es weiterhin "Online"? ^^

 

[schranzer]

und noch was wo upstream steht...



Cable Modem Status: Operational
Cable Modem IP Address: 10.144.38.54
Cable Modem Mask: 255.255.192.0
Cable Modem Gateway: 10.144.0.1
Cable Modem TFTP Server: 80.69.97.134
Current Time: Sun. Jan 13 17:04:01 2013
Time Server: 80.69.97.134
Time Offset: 7200 Seconds
Time Since Last Reset: 7 days 02h:38m:55s
Configuration File: be_l_1_epc3212_nv.bin
Cable Modem Certificate: Installed
IP Time Lease: 13.0 Days (1172069 Seconds / 1786371 Seconds)
IP Time Rebind: 10.0 Days ( 948772 Seconds / 1563074 Seconds)
IP Time Renew: 3.0 Days ( 278883 Seconds / 893185 Seconds)


Ethernet
Interface Name LINK Status LINK Speed LINK Duplex
LAN: Ethernet Interface 5 Link Up 100 MBits Yes



QoS
The data shown in the table below containing information about Call Processing for your cable modem.
PHS OFF
The data shown in the table below containing information about QoS for your cable modem.
SFID Direction Primary Packets Service Class Name
493 Upstream Yes 1835268 null
494 Downstream Yes 0 null