Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor II
•
Continual freezes during day ...how to get actual resolution?
Getting continual freezes during day, some require a power cycle of the Modem
I get
CM-STATUS codes of different values through the day / occasional T3 T4
Frequent Dynamic Range Window violation
Can also generate what seems like a lot of uncorrectables
I dont see Power or SNR values that look off
I have swapped RG6 cables around / cable modems / ... ...all changed nothing
Phoned in for help
Sadly got a contractor that didnt know what a Modem error code was at all (not that I know all that much)
Contractor literally switched my drop with the neighbors at the pedestal and bailed (awesome service) ...that of course did nothing
DesertBlossom
New Contributor II
•
Paging tiffanyr
Had also asked for help at cox.help mail 30 hours ago ...zero response
0
0
LisaH
Moderator
•
0
DesertBlossom
New Contributor II
•
Still happening of course
Cox monkeys have an update coming overnight "planned outage starts today." ...shall see what happens
2023-03-15, 07:22:37
Warning (5)
Dynamic Range Window violation
2023-03-15, 07:22:37
Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:22:36
Warning (5)
Dynamic Range Window violation
2023-03-15, 07:22:36
Warning (5)
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:22:31
Notice (6)
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:22:26
Notice (6)
TLV-11 - unrecognized OID;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:22:25
Warning (5)
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
Notice (6)
Honoring MDD; IP provisioning mode = IPv4
Time Not Established
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:14:34
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=c8:9e:43: ;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:14:30
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:14:11
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:14:10
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:13:51
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:13:50
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:13:32
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:13:31
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:13:11
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:13:10
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:12:16
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
2023-03-15, 07:12:11
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=c8:9e:43: ;CMTS-MAC=28:af:fd:9a: ;CM-QOS=1.1;CM-VER=3.1;
1
0
DesertBlossom
New Contributor II
•
So much for keeping to their word
Did it at 8am and then immediately down in 30 minutes
We’re happy to say that our network is back up and running, so you can continue to enjoy a great streaming, gaming and sharing experience. Your equipment should restart automatically, but click below if you need a hand.
Don’t worry, we’ll keep you posted on any future updates that may impact your service as we continue to meet your needs. Hopefully this was a little inconvenience to bring you a stronger network.
1
0