Contributor
•
69 Messages
IPv6 down for my address?
Something happened around 1 AM on May 24 (see screenshot). I lost all IPv6. I rebooted all my network equipment and PCs, reset my Netgear CM600 to factory, retightened all connections, no effect. I have included the recent modem logs as well. Is this my problem or yours? Thanks for reading and please advise.
| Time | Priority | Description |
| 2024-05-26, 17:53:34 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
| 2024-05-25, 15:55:35 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2024-05-25, 15:55:10 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2024-05-25, 15:55:05 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2024-05-25, 15:55:03 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2024-05-25, 15:55:01 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
| 2024-05-25, 15:55:01 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
| 2024-05-25, 15:54:58 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
| 2024-05-25, 15:54:58 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
| 2024-05-25, 15:54:57 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
| 2024-05-25, 15:54:57 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
| 2024-05-25, 15:54:10 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
| 2024-05-24, 14:28:19 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
| 2024-05-23, 22:35:26 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:xx:xx:xx;CMTS-MAC=00:90:f0:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; |
Accepted Solution
prove
Contributor
•
69 Messages
11 months ago
Someone's working today! Thanks for the assist, whoever your are!
1
0