Komplettausfall Erding 12.05.2009 - 13.05.2009

[Ripperjack]

hallo

seit gestern war das Internet und Telefonie von Kabel Deutschland total tot im Landkreis Erding. Wollte mal nachfragen, ob es eine bekannte Störung gab, und ob diese auch wo anders als im LK Erding war.

danke

PS: in der letzten Zeit sind vermehrt Ausfälle von ca. 10 Minuten da. Gestern aber waren es 24 Stunden.


danke

PS: das war der Motorola LOG "Vor allem die Zeit 1970 ist echt heftig

1970-01-01 00:22:43 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:22:42 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:22:41 5-Warning SYNC: US Gain in cache is invalid: 0.00
1970-01-01 00:22:39 7-Information Starting Ranging On Channel 4
1970-01-01 00:22:21 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:22:20 7-Information Starting Ranging On Channel 2
1970-01-01 00:22:20 3-Critical R03.0 Ranging Request Retries exhausted
1970-01-01 00:22:19 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:22:16 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:22:14 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:22:12 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:22:10 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:22:06 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:22:03 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:59 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:57 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:55 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:55 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:51 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:51 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:49 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:48 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:47 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:45 7-Information Starting Ranging On Channel 1
1970-01-01 00:21:41 7-Information Downstream Locked - Collecting Upstream Information
1970-01-01 00:21:39 7-Information Channel Override Requested By Initial Ranging
1970-01-01 00:21:39 7-Information Tuning to frequency 562000000Hz, (us 1 mode 2)
1970-01-01 00:21:37 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:34 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:29 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:27 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:27 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:26 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:24 7-Information Starting Ranging On Channel 1
1970-01-01 00:21:20 7-Information Downstream Locked - Collecting Upstream Information
1970-01-01 00:21:17 7-Information Channel Override Requested By Initial Ranging
1970-01-01 00:21:17 7-Information Tuning to frequency 586000000Hz, (us 1 mode 2)
1970-01-01 00:21:14 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:14 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:11 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:10 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:09 5-Warning SYNC: US Gain in cache is invalid: 0.00
1970-01-01 00:21:09 7-Information Starting Ranging On Channel 4
1970-01-01 00:21:05 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:01 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:21:00 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:58 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:54 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:50 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:49 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:47 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:46 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:45 5-Warning SYNC: US Gain in cache is invalid: 0.00
1970-01-01 00:20:45 7-Information Starting Ranging On Channel 3
1970-01-01 00:20:40 7-Information Downstream Locked - Collecting Upstream Information
1970-01-01 00:20:38 7-Information Channel Override Requested By Initial Ranging
1970-01-01 00:20:38 7-Information Tuning to frequency 602000000Hz, (us 0 mode 1)
1970-01-01 00:20:35 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:30 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:29 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:28 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:20:28 5-Warning SYNC: US Gain in cache is invalid: 0.00
1970-01-01 00:20:28 7-Information Starting Ranging On Channel 4
1970-01-01 00:20:28 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
1970-01-01 00:20:26 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:20:25 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:20:21 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:20:20 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:20:19 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out

[Master2]

München-Ost lief in der Zeit.

[GMF]

Raum Wasserburg hatte zu diesem Zeitpunkt ebenfalls keine Probleme.

[Ripperjack]

hmm, haben wohl die Leute vom Erdinger Weißbier beim buddeln nach ner neuen Quelle n Kabel abgerissen
weiss ja ned obs nur bei mir im Kaff war. Aber bin für jede Erfahrung in den Umliegenden Landkreisen dankbar.


PS: ich weiss nicht was da kaputt ist, aber ab und zu laden Internetseiten schnell, dann wieder mit 5-6 Sekunden verzögerung. Laut Tracert gibt es ab und zu am 8. von 9 Knoten einen ms Anstieg von 40 auf 250 ms. Vor dem Ausfall war alles konstant.

[Ripperjack]

aargh, und schon wieder 2 mal Abbruch für 1 Minute innerhalb 10 Minuten


kann jemand da was anfangen, was das sein könnte? Probleme am Modem, Verteiler, oder selbst bei KD?


4-Error SYNC: Hardware didn't detect SYNC msg for 600ms - Disable Upstream and trying to lock on DS
2009-05-13 18:37:26 7-Information Synchronization LOST <562000000 Hz - ucd 1, Station Maintenance T4 Timeout or Ranging ABORT>
2009-05-13 18:37:26 3-Critical R03.0 Ranging Requests Retries exhausted
2009-05-13 18:37:25 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:24 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:23 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:22 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:21 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:19 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:18 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:17 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:16 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:16 4-Error DSX: CM Sends DSX-RSP with TA ID 46038, error code 6.
2009-05-13 18:37:16 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:37:16 4-Error DSX: CM Sends DSX-RSP with TA ID 46037, error code 6.
2009-05-13 18:37:16 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:37:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:15 4-Error DSX: CM Sends DSX-RSP with TA ID 46038, error code 6.
2009-05-13 18:37:15 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:37:15 4-Error DSX: CM Sends DSX-RSP with TA ID 46037, error code 6.
2009-05-13 18:37:15 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:37:14 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:14 4-Error DSX: CM Sends DSX-RSP with TA ID 46038, error code 6.
2009-05-13 18:37:14 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:37:14 4-Error DSX: CM Sends DSX-RSP with TA ID 46037, error code 6.
2009-05-13 18:37:14 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:37:13 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:13 4-Error DSX: CM Sends DSX-RSP with TA ID 46038, error code 6.
2009-05-13 18:37:13 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:37:13 4-Error DSX: CM Sends DSX-RSP with TA ID 46037, error code 6.
2009-05-13 18:37:13 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:37:12 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:37:10 3-Critical R02.0 No Ranging Response received - T3 time-out
2009-05-13 18:36:33 4-Error DSX: CM Sends DSX-RSP with TA ID 46034, error code 6.
2009-05-13 18:36:33 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:36:33 4-Error DSX: CM Sends DSX-RSP with TA ID 46033, error code 6.
2009-05-13 18:36:33 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:36:32 4-Error DSX: CM Sends DSX-RSP with TA ID 46034, error code 6.
2009-05-13 18:36:32 4-Error S03.2 Service Delete rejected - Service flow not found
2009-05-13 18:36:32 4-Error DSX: CM Sends DSX-RSP with TA ID 46033, error code 6.
2009-05-13 18:36:32 4-Error S03.2 Service Delete rejected - Service flow not found

[Master2]

München-Ost lief in der Zeit.

Ich habe jetzt noch in den Log meiner FritzBox reingeschaut. Da ist auch nichts von einem Netzausfall zu sehen.

Bei einem meiner VoIP-Anbieter meldet sich die FritzBox ca. alle 2-2,5 Minuten bei ihm, so dass ein Ausfall schnell auffallen würde.