Bewertung Eventlog Thomsonmodem

[mikekd]

Hallo, seit etwa 3 Monaten meldet mein THG 540 im Eventlog fast täglich Störungen, meist T3 out.Diese dauern meist nur eine Minute, treten aber mehrmals am Tag auf.Ob das Telefon genau zum Auftreten der Störungen auch ausfällt, kann ich schwer feststellen.
Seit Auftreten der Störungen ist der Downloadpegel von 0dBmV auf -2dBmV gefallen, also noch im grünen Bereich. Das SNR fiel von konstant 36db auf 34-35dB, also auch kein Wert zum Grübeln. Der Uploadpegel liegt bei 50dBmV ziemlich stabil.
Meine Frage: Wie sollte man diese Störungen bewerten, ein Abbruch eines Downloads ist es allemal.Störungsticket ist aufgemacht, erwarte allerdings nicht viel.
Date/Time Event ID Event Level Description
08/31/2009 10.58 67020600 03 DCC aborted unable to communicate on new upstream channel
08/31/2009 10.58 82000300 03 Init RANGING Critical Ranging Request Retries exhausted
08/31/2009 10.58 82000200 03 No Ranging Response received - T3 time-out
08/30/2009 10.26 67020600 03 DCC aborted unable to communicate on new upstream channel
08/30/2009 10.26 82000300 03 Init RANGING Critical Ranging Request Retries exhausted
08/30/2009 10.26 82000200 03 No Ranging Response received - T3 time-out
08/28/2009 16.25 67020600 03 DCC aborted unable to communicate on new upstream channel
08/28/2009 16.25 82000300 03 Init RANGING Critical Ranging Request Retries exhausted
08/28/2009 16.25 82000200 03 No Ranging Response received - T3 time-out
08/26/2009 12.05 67040100 04 DCC-ACK not received
08/26/2009 12.04 82000200 03 No Ranging Response received - T3 time-out
08/24/2009 14.28 67021600 04 DCC rejected parameter invalid for context
08/24/2009 14.27 82000200 03 No Ranging Response received - T3 time-out
08/24/2009 14.25 84000100 03 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
08/24/2009 14.25 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
08/22/2009 18.48 82000200 03 No Ranging Response received - T3 time-out
08/22/2009 18.33 82000300 03 Init RANGING Critical Ranging Request Retries exhausted
08/22/2009 18.33 82000200 03 No Ranging Response received - T3 time-out
08/22/2009 18.33 67020600 03 DCC aborted unable to communicate on new upstream channel
08/20/2009 18.16 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
08/20/2009 07.54 82000200 03 No Ranging Response received - T3 time-out
08/13/2009 05.22 67020600 03 DCC aborted unable to communicate on new upstream channel
08/13/2009 05.22 82000300 03 Init RANGING Critical Ranging Request Retries exhausted
08/13/2009 05.22 82000200 03 No Ranging Response received - T3 time-out
08/11/2009 22.14 67020600 03 DCC aborted unable to communicate on new upstream channel
08/11/2009 22.14 82000300 03 Init RANGING Critical Ranging Request Retries exhausted
08/11/2009 22.14 82000200 03 No Ranging Response received - T3 time-out
08/11/2009 12.57 67040100 04 DCC-ACK not received
08/11/2009 12.57 82000200 03 No Ranging Response received - T3 time-out
08/11/2009 11.59 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
08/07/2009 11.53 82000200 03 No Ranging Response received - T3 time-out
07/31/2009 13.23 67020600 03 DCC aborted unable to communicate on new upstream channel
MfG Mike

[fLoo]

Ist nichts besonderes, so siehts hier auch aus

[mikekd]

Hallo, ein dreiviertel Jahr hatte ich aber solche Meldungen nicht, irgend etwas muß sich geändert haben.Bei einem T3 out läßt sich wohl schlecht downloaden.
MfG Mike