Nog steeds internet problemen

[josje22]

Hallo forumleden en ziggo moderatoren

>>> Kan iemand uit mijn log iets zinnigs vinden ? vast bedankt.

Alweer uitval internet. Vorige week verbinding nog door ziggo getest nadat ik ze gezegd heb dat ik vaak toch wel 1 x per week uitval heb:

>> Dit hebben we voor je nagekeken: verbinding naar je huis, hoofdaansluiting en modemkabels

situatie: smartwifi modem / fritzbox 4040

24 september 2024 iets voor 14:00
- geen internet
- wel router connect & gui
- wel modem connect & gui
---
-> router gerestart
- geen internet
- geen modem connect
-> modem gerestart
- wit lampje fade in / fade out

14:14
- internet werkt weer

>>> Hierna volgt de log op het moment dat er geen internet is. Hel4emaal op het einde de netwerklog na re hard boot/restart van het modem

LOG FILES MODEM ZIGGO

Cable Modem Status Online DOCSIS 3.0
Primary downstream channel Locked SC-QAM
Channel Overview Downstream Upstream
DOCSIS 3.0 channels 31 4
DOCSIS 3.1 channels 1 2
*****************************************************************
1 594000000 5 39 QAM 256 3
2 578000000 5.1 39 QAM 256 1
3 586000000 5 39 QAM 256 2
4 602000000 5.1 39 QAM 256 4
5 610000000 4.9 38 QAM 256 5
6 618000000 5 38 QAM 256 6
7 626000000 5.1 38 QAM 256 7
8 642000000 5.1 38 QAM 256 9
9 650000000 5.2 38 QAM 256 10
10 658000000 5.1 38 QAM 256 11
11 666000000 5.2 38 QAM 256 12
12 674000000 5.3 38 QAM 256 13
13 682000000 5.2 38 QAM 256 14
14 690000000 5.3 38 QAM 256 15
15 698000000 5.4 38 QAM 256 16
16 706000000 5.5 38 QAM 256 17
17 714000000 5.6 38 QAM 256 18
18 722000000 5.8 38 QAM 256 19
19 730000000 5.8 38 QAM 256 20
20 738000000 5.8 38 QAM 256 21
21 746000000 5.9 38 QAM 256 22
22 754000000 5.9 38 QAM 256 23
23 762000000 5.9 38 QAM 256 24
24 770000000 5.7 38 QAM 256 25
25 778000000 5.6 38 QAM 256 26
26 786000000 5.9 38 QAM 256 27
27 794000000 6.1 38 QAM 256 28
28 802000000 6.4 38 QAM 256 29
29 810000000 6.6 39 QAM 256 30
30 818000000 6.6 38 QAM 256 31
31 826000000 6.7 38 QAM 256 32
3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 39 546 60
2 Locked 39 428 75
3 Locked 39 494 71
4 Locked 39 506 77
5 Locked 38 588 71
6 Locked 38 590 68
7 Locked 38 578 65
8 Locked 38 623 66
9 Locked 38 537 56
10 Locked 38 477 67
11 Locked 38 422 53
12 Locked 38 599 55
13 Locked 38 617 53
14 Locked 38 548 47
15 Locked 38 571 30
16 Locked 38 344 42
17 Locked 38 310 54
18 Locked 38 326 22
19 Locked 38 350 41
20 Locked 38 367 52
21 Locked 38 373 21
22 Locked 38 383 42
23 Locked 38 450 4
24 Locked 38 721 7
25 Locked 38 790 18
26 Locked 38 664 9
27 Locked 38 587 3
28 Locked 38 535 0
29 Locked 39 439 0
30 Locked 38 481 0
31 Locked 38 463 0
3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33 168 4K 3301 QAM 4096 368
3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33 Locked 39 6.5 3514762612 1
******************************************************************************
3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 58800000 44.5 5120 QAM 64 1
1 52000000 44.5 5120 QAM 64 2
2 45200000 44.8 5120 QAM 64 3
3 38400000 44.5 5120 QAM 64 4
3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0 ATDMA 0 0 2 0
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
25 15 39.0 2K QAM 64
26 17.25 38.5 2K QAM 64
3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
25 OFDMA 300 74000000 0 0
26 OFDMA 345 74000000 36 0
*********************************************************************************
General Configuration

Network access Allowed
Maximum Number of CPEs 3
Baseline Privacy Enabled
DOCSIS Mode 3.1
Config file bac102000106cc00f1d95b8b
Primary Downstream Service Flow

SFID 759381
Max Traffic Rate 428000000 bps
Max Traffic Burst 42600bytes
Min Traffic Rate 0 bps
Primary Upstream Service Flow

SFID 759380
Max Traffic Rate 42800000 bps
Max Traffic Burst 42600bytes
Min Traffic Rate 0 bps
Max Concatenated Burst 42600bytes
Scheduling Type Best Effort
SFID 759382
Max Traffic Rate 42800000 bps
Max Traffic Burst 42600bytes
Min Traffic Rate 0 bps
Max Concatenated Burst 42600bytes
Scheduling Type Best Effort
*********************************************************************************

Network Log

Time Priority Description
24-09-2024 13:51:29 notice GUI Login Status - Login Success from LAN interface
24-09-2024 13:50:25 notice CM-STATUS message sent. Event Type Code: 8; Chan ID: 26; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 13:49:48 critical 16 consecutive T3 timeouts while trying to range on upstream channel 9;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 13:49:48 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 13:48:40 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 13:15:21 notice US profile assignment change. US Chan ID: 25; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 12:09:51 notice US profile assignment change. US Chan ID: 25; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 11:45:11 notice US profile assignment change. US Chan ID: 25; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 01:46:34 notice US profile assignment change. US Chan ID: 25; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
23-09-2024 23:46:31 notice US profile assignment change. US Chan ID: 25; Previous Profile: 11 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
23-09-2024 22:27:57 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
23-09-2024 20:27:53 notice US profile assignment change. US Chan ID: 26; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
23-09-2024 19:46:27 notice US profile assignment change. US Chan ID: 25; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
23-09-2024 18:58:08 notice US profile assignment change. US Chan ID: 25; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
22-09-2024 22:20:34 notice US profile assignment change. US Chan ID: 25; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
22-09-2024 20:20:31 notice US profile assignment change. US Chan ID: 25; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
22-09-2024 09:15:44 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
20-09-2024 18:23:09 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
19-09-2024 19:16:14 notice US profile assignment change. US Chan ID: 25; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
19-09-2024 18:14:04 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
19-09-2024 17:16:11 notice US profile assignment change. US Chan ID: 25; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
19-09-2024 16:14:01 notice US profile assignment change. US Chan ID: 26; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
19-09-2024 12:50:08 notice GUI Login Status - Login Success from LAN interface
18-09-2024 21:15:42 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
18-09-2024 19:15:24 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
18-09-2024 17:15:21 notice US profile assignment change. US Chan ID: 26; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
18-09-2024 10:40:18 notice GUI Login Status - Login Success from LAN interface
18-09-2024 10:27:32 notice GUI Login Status - Login Success from LAN interface
18-09-2024 10:27:10 notice GUI Login Status - Login Fail from LAN interface
17-09-2024 11:21:47 notice CM-STATUS message sent. Event Type Code: 8; Chan ID: 26; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 11:21:35 critical 16 consecutive T3 timeouts while trying to range on upstream channel 9;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 11:21:35 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 11:20:27 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
15-09-2024 20:32:44 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
15-09-2024 20:20:23 notice US profile assignment change. US Chan ID: 25; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
15-09-2024 18:32:41 notice US profile assignment change. US Chan ID: 26; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
15-09-2024 18:20:20 notice US profile assignment change. US Chan ID: 25; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;

----------------------------------------------------------------------------------------------------------------------------------------------
Network Log na hard reboot

Time Priority Description
24-09-2024 14:15:21 notice GUI Login Status - Login Success from LAN interface
24-09-2024 14:12:41 notice REGISTRATION COMPLETE - Waiting for Operational status
24-09-2024 14:12:35 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:12:27 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:12:24 notice TLV-11 - unrecognized OID;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:12:20 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:12:18 notice Honoring MDD; IP provisioning mode = IPv4
24-09-2024 14:12:15 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:11:33 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:11:27 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:11:22 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:11:20 critical Cable Modem Reboot because of - HW or Power-On Reset
09-09-2024 09:52:32 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 09:51:48 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 09:51:42 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 09:51:36 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 09:51:36 critical Cable Modem Reboot because of - HW or Power-On Reset
06-09-2024 17:48:58 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
06-09-2024 17:48:18 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
06-09-2024 17:48:13 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
06-09-2024 17:48:06 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
06-09-2024 17:48:03 critical Cable Modem Reboot because of - HW or Power-On Reset
05-09-2024 02:23:25 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
21-08-2024 17:45:19 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
21-08-2024 17:45:17 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
21-08-2024 17:44:26 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
21-08-2024 17:44:20 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
21-08-2024 17:44:20 critical Cable Modem Reboot because of - HW or Power-On Reset
18-08-2024 20:47:14 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
18-08-2024 20:47:09 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
18-08-2024 20:47:02 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
18-08-2024 20:47:00 critical Cable Modem Reboot because of - HW or Power-On Reset
14-08-2024 23:55:09 critical 16 consecutive T3 timeouts while trying to range on upstream channel 9;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;

[josje22]

p.s.

oude mail/topics van mij over hetzelfde probleem:
https://community.ziggo.nl/t5/Archief/Meermaals-per-maand-verbroken-internetverbinding-wat-nu/m-p/13...
https://community.ziggo.nl/t5/Archief/frequent-uitval-internet-verbinding-oplossing-of-opzeggen-abbo...

gr, josje22

[tobiastheebe]

De historie laat uitval van OFDMA 2 (CID 26) in de upstream zien, vandaag om 13:48, op 17-9 om 11:20 en op 14-8 om 23:55, dit veroorzaakt inderdaad een merkbaar onderbroken internetverbinding. Op nagenoeg alle SC-QAM-kanalen in de downstream zijn uncorrectable codeword errors ('Fouten na RS') voorgekomen. De actuele downstream/upstream-waarden zijn goed tot zeer goed.

Kun je een of meerdere foto’s plaatsen van de hoofdaansluiting (het AOP) in de meterkast of woonkamer, inclusief (een) eventuele splitter(s) en/of signaalversterker?

[josje22]

Deze aop is vorig jaar geinstalleerd ter vervanging van de oude, die er al zat van de A2000 periode (pre UPC). Daar kan het dus niet aan liggen.

Tobias, heb jij enig idee wat de mogelijke oorzaak van de uitval van OFDMA 2 (CID 26) is? Is ziggo hiervoor verantwoordelijk? 

Dank je wel voor het meedenken, lezen en intepreteren van mijn modem log.

Josje22

 

[tobiastheebe]

Het AOP (btv 01-SET) en de IEC/F-kabel groen/rood zijn inderdaad prima en up-to-date. Gezien het modem direct op het AOP is aangesloten moet de oorzaak van de uitval buitenshuis gezocht worden, mogelijk veroorzaakt een medeklant sporadisch storing.

Een moderator (Ziggo-medewerker) kan de juiste vervolgstap bepalen en komt binnenkort langs in dit topic.

[josje22]

ik ben zeer benieuwd...

[Carlien]

Goedemorgen! @josje22 

Nooit fijn als je uitval ervaart! Goed dat je aan de bel hebt getrokken!

Ik heb internet gekeken en zie geen rare dingen in het signaal. Ik heb daarom een modem sessie gestart voor de komende 7 dagen om even alles goed te controleren. Kun jij de komende week de datum en tijdstippen controleren van de momenten dat je uitval ervaart? Dan kunnen we dit daarna naast elkaar houden en vanuit daar verdere beslissingen maken wat we kunnen doen! Ik kom volgende week even in de lucht! 

[Carlien]

Goedemorgen! @josje22 

Hoe is het gegaan afgelopen week? Heb je tijdstippen en data genoteerd wanneer je uitval hebt ervaren? Zo ja, wil je mij die doorsturen? Dan gaan we eens kijken of we overeenkomsten kunnen terugvinden! 

[josje22]

uitval:

25 sep 20:34 internet uitval
01 oct 23:59 internet uitval

----------------
Network Log

Time Priority Description
26-09-2024 08:15:59 notice GUI Login Status - Login Success from LAN interface
25-09-2024 21:15:41 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 20:35:41 notice CM-STATUS message sent. Event Type Code: 8; Chan ID: 26; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 20:35:17 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 20:35:17 critical 16 consecutive T3 timeouts while trying to range on upstream channel 9;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 20:34:09 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 15:29:41 notice US profile assignment change. US Chan ID: 25; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 13:29:41 notice US profile assignment change. US Chan ID: 25; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 12:41:55 notice GUI Login Status - Login Success from LAN interface
25-09-2024 10:57:21 notice GUI Login Status - Login Success from LAN interface
25-09-2024 10:56:47 notice GUI Login Status - Login Fail from LAN interface
25-09-2024 10:49:06 notice GUI Login Status - Login Success from LAN interface
25-09-2024 08:00:29 notice GUI Login Status - Login Success from LAN interface
24-09-2024 14:15:21 notice GUI Login Status - Login Success from LAN interface
24-09-2024 14:12:41 notice REGISTRATION COMPLETE - Waiting for Operational status
24-09-2024 14:12:35 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:12:27 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:12:24 notice TLV-11 - unrecognized OID;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:12:20 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:12:18 notice Honoring MDD; IP provisioning mode = IPv4
24-09-2024 14:12:15 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:11:33 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:11:27 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:11:22 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
24-09-2024 14:11:20 critical Cable Modem Reboot because of - HW or Power-On Reset
09-09-2024 09:52:32 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 09:51:48 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 09:51:42 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 09:51:36 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 09:51:36 critical Cable Modem Reboot because of - HW or Power-On Reset
06-09-2024 17:48:58 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
06-09-2024 17:48:18 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
06-09-2024 17:48:13 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
06-09-2024 17:48:06 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
06-09-2024 17:48:03 critical Cable Modem Reboot because of - HW or Power-On Reset
05-09-2024 02:23:25 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
21-08-2024 17:45:19 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
21-08-2024 17:45:17 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
------------------------------------------------------------------------------------------------

21-08-2024 17:44:26 critical No Ranging Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;

-----------------------------------------------------------------------------------------------
Network Log

Time Priority Description
02-10-2024 11:29:09 notice GUI Login Status - Login Success from LAN interface
01-10-2024 23:59:51 notice CM-STATUS message sent. Event Type Code: 8; Chan ID: 26; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
01-10-2024 23:59:37 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
01-10-2024 23:59:37 critical 16 consecutive T3 timeouts while trying to range on upstream channel 9;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
01-10-2024 23:58:29 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
01-10-2024 00:59:35 notice US profile assignment change. US Chan ID: 25; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 22:59:33 notice US profile assignment change. US Chan ID: 25; Previous Profile: 11 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 22:36:32 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 20:59:30 notice US profile assignment change. US Chan ID: 25; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 20:36:28 notice US profile assignment change. US Chan ID: 26; Previous Profile: 11 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 18:59:25 notice US profile assignment change. US Chan ID: 25; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 18:42:05 notice US profile assignment change. US Chan ID: 25; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 18:37:32 notice US profile assignment change. US Chan ID: 25; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 18:36:24 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 18:26:35 notice US profile assignment change. US Chan ID: 26; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 17:08:05 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 15:08:05 notice US profile assignment change. US Chan ID: 26; Previous Profile: 11 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 13:07:58 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 12:18:55 notice US profile assignment change. US Chan ID: 26; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 10:53:46 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 08:53:45 notice US profile assignment change. US Chan ID: 26; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 05:44:30 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 03:44:27 notice US profile assignment change. US Chan ID: 26; Previous Profile: 11 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
30-09-2024 01:44:24 notice US profile assignment change. US Chan ID: 26; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
29-09-2024 23:44:19 notice US profile assignment change. US Chan ID: 26; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
29-09-2024 22:30:52 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
29-09-2024 21:32:50 notice US profile assignment change. US Chan ID: 26; Previous Profile: 11 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
29-09-2024 19:32:47 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
29-09-2024 18:09:01 notice US profile assignment change. US Chan ID: 26; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
29-09-2024 14:13:24 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
29-09-2024 12:13:19 notice US profile assignment change. US Chan ID: 26; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
29-09-2024 10:12:27 notice US profile assignment change. US Chan ID: 26; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
29-09-2024 09:15:44 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
28-09-2024 11:54:58 notice GUI Login Status - Login Success from LAN interface
26-09-2024 08:27:09 notice GUI Login Status - Login Success from LAN interface
26-09-2024 08:15:59 notice GUI Login Status - Login Success from LAN interface
25-09-2024 12:41:55 notice GUI Login Status - Login Success from LAN interface
25-09-2024 10:57:21 notice GUI Login Status - Login Success from LAN interface
25-09-2024 10:56:47 notice GUI Login Status - Login Fail from LAN interface
25-09-2024 10:49:06 notice GUI Login Status - Login Success from LAN interface
25-09-2024 08:00:29 notice GUI Login Status - Login Success from LAN interface
24-09-2024 14:15:21 notice GUI Login Status - Login Success from LAN interface

[tobiastheebe]

Op beide momenten die je noemt was sprake van uitval van OFDMA 2 (CID 26), zoals aan het begin van het topic ook het geval was.

[Carlien]

Dankjewel! @josje22 

Ik heb samen met mijn collega's gekeken naar het signaal en we zien wel iets terug waar we graag een monteur naar willen laten kijken. De aansluiting binnen zit er namelijk netjes uit dus ik plan gelijk iemand voor je in die mee gaat kijken en het signaal vanuit huis gaat checken. 

Volgende week maandag 7 oktober komt er iemand langs tussen 12.00-18.00 uur. Als het niet uitkomt, dan kan je de afspraak wijzigen via MijnZiggo. 

Horen we van je hoe het gegaan is? 👌

[josje22]

update:

Monteur net de deur uit.

- Hij heeft de API gecontroleerd,

- het signaal op alle frequenties getest. Niets raars te zijn. Boven gemiddeld goed signaal

- reactie monteur over uitval door "modems in de buurt": Als dat het geval is kunnen wij dat zijn, en dat is niet het geval

- reactie monteur over mogelijke oorzaken uitval:

1. chipfout in het modem (modem wordt binnenkort vervangen)

2. omdat met modem in bridgemode staat, kan mijn router mogelijk de problemen met uitval veroorzaken

Verder kan hij niks doen. Hij suggereerde de router er tijdelijk tussenuit te halen, maar dat kan praktisch niet omdat er hier nog meer mensen afhankelijk zijn van de internet aansluiting en interne netwerken dan niet meer werken. 

Opmerking van mij over mogelijkheid 2. : hier snap ik niks van. Hoe kan mijn router nu het ziggo modem "laten vastlopen" De fritz!box router valt nooit uit.

Ik hoop dat het op te sturen nieuwe modem de problemen EINDELIJK oplost. we wachten weer af.

mvrgr,

josje22

[tobiastheebe]

De uitval van OFDMA heeft niets met de eigen router of andere apparatuur in het interne netwerk te maken en gaat vrijwel zeker ook niet opgelost wordt met een nieuw modem.

[josje22]

hey Tobias, dat dacht ik ook. Maar WAT veroorzaakt de uitval van OFDMA dan wel? En nog belangrijker, hoe kan het mogelijk opgelost worden? De monteur zei niks te kunnen doen.

Desalniettemin waardeer ik jou antwoorden/meedenken zeer. Dank maar weer...

[tobiastheebe]

Als medeklant kan ik ook niet veel meer doen op dit moment. Uiteraard kan ik wel nogmaals de historie analyseren als je onverhoopt opnieuw uitval ervaart.

[josje22]

Dat snap ik, maar heb je enig idee over 1. wat veroorzaakt de problemen, en 2. hoe zou je dit op kunnen lossen? Ik kan me voorstellen dat ziggo vind dat  een paar paar per maand uitval binnen de tollerantie (consumer account) valt en ik dit dus maar moet accepteren. De monteur weet het blijkbaar niet... 

[josje22]

En weer een uitval!

Dit keer T4

What the hell is hier gaande?

Wie verteld mij zinnige begrijpelijke informatie?

mvrgr,

josje22

log:

Network Log

Time Priority Description

08-10-2024 19:04:18	notice	GUI Login Status - Login Success from LAN interface
08-10-2024 08:43:20	notice	CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 25 26 27 28 29 30 31 32 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.
08-10-2024 08:43:20	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;C
08-10-2024 08:43:10	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:43:10	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:43:10	notice	CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:42:49	warning	RCS Partial Service;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:42:19	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:42:18	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:42:03	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:42:02	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:40:51	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:40:51	warning	MDD message timeout;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:40:45	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:40:45	warning	MDD message timeout;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
08-10-2024 08:40:41	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:00:f1:d9:5b:8b;CMTS-MAC=00:01:5c:af:28:78;CM-QOS=1.1;CM-VER=3.1;
07-10-2024 11:38:02	notice	GUI Login Status - Login Success from LAN interface

[tobiastheebe]

Ik zie alleen uitval tussen 8:40 en 8:43, dit was waarschijnlijk een signaalonderbreking. Voor uitval na 8:43 ligt de oorzaak mogelijk bij de eigen apparatuur.

[josje22]

ah ik begrijp de uitval tussen 8:40 en 8:43, dat was de monteur die hier de kabel er uit trok. Vals alarm dus, hahah...