Forum Discussion
skohon25
New Contributor III
Here are the status notes
Startup Procedure | ||
---|---|---|
Procedure | Status | Comment |
Acquire Downstream Channel | 951000000 Hz | Locked |
Connectivity State | OK | Operational |
Boot State | OK | Operational |
Configuration File | OK | |
Security | Enabled | BPI+ |
DOCSIS Network Access Enabled | Allowed |
Downstream Bonded Channels | |||||||
---|---|---|---|---|---|---|---|
Channel ID | Lock Status | Modulation | Frequency | Power | SNR/MER | Corrected | Uncorrectables |
29 | Locked | QAM256 | 951000000 Hz | -2.1 dBmV | 41.6 dB | 0 | 0 |
1 | Locked | QAM256 | 783000000 Hz | 2.0 dBmV | 43.0 dB | 0 | 0 |
2 | Locked | QAM256 | 789000000 Hz | 2.0 dBmV | 43.0 dB | 0 | 0 |
3 | Locked | QAM256 | 795000000 Hz | 1.9 dBmV | 43.0 dB | 0 | 0 |
4 | Locked | QAM256 | 801000000 Hz | 1.9 dBmV | 43.0 dB | 0 | 0 |
5 | Locked | QAM256 | 807000000 Hz | 1.7 dBmV | 42.9 dB | 0 | 0 |
6 | Locked | QAM256 | 813000000 Hz | 1.7 dBmV | 42.8 dB | 0 | 0 |
7 | Locked | QAM256 | 819000000 Hz | 1.6 dBmV | 42.9 dB | 0 | 0 |
8 | Locked | QAM256 | 825000000 Hz | 1.3 dBmV | 42.8 dB | 0 | 0 |
9 | Locked | QAM256 | 831000000 Hz | 1.1 dBmV | 42.7 dB | 0 | 0 |
10 | Locked | QAM256 | 837000000 Hz | 1.1 dBmV | 42.7 dB | 0 | 0 |
11 | Locked | QAM256 | 843000000 Hz | 0.8 dBmV | 42.7 dB | 0 | 0 |
12 | Locked | QAM256 | 849000000 Hz | 0.8 dBmV | 42.7 dB | 0 | 0 |
13 | Locked | QAM256 | 855000000 Hz | 0.7 dBmV | 42.6 dB | 0 | 0 |
14 | Locked | QAM256 | 861000000 Hz | 0.3 dBmV | 42.5 dB | 0 | 0 |
15 | Locked | QAM256 | 867000000 Hz | 0.1 dBmV | 42.4 dB | 0 | 0 |
16 | Locked | QAM256 | 873000000 Hz | 0.0 dBmV | 42.4 dB | 0 | 0 |
17 | Locked | QAM256 | 879000000 Hz | -0.3 dBmV | 42.3 dB | 0 | 0 |
18 | Locked | QAM256 | 885000000 Hz | -0.6 dBmV | 42.3 dB | 0 | 0 |
19 | Locked | QAM256 | 891000000 Hz | -0.7 dBmV | 42.2 dB | 0 | 0 |
20 | Locked | QAM256 | 897000000 Hz | -1.0 dBmV | 41.9 dB | 0 | 0 |
21 | Locked | QAM256 | 903000000 Hz | -1.2 dBmV | 41.9 dB | 0 | 0 |
22 | Locked | QAM256 | 909000000 Hz | -1.4 dBmV | 41.9 dB | 0 | 0 |
23 | Locked | QAM256 | 915000000 Hz | -1.6 dBmV | 41.7 dB | 0 | 0 |
24 | Locked | QAM256 | 921000000 Hz | -1.8 dBmV | 41.6 dB | 0 | 0 |
25 | Locked | QAM256 | 927000000 Hz | -1.8 dBmV | 41.7 dB | 0 | 0 |
26 | Locked | QAM256 | 933000000 Hz | -2.0 dBmV | 41.7 dB | 0 | 0 |
27 | Locked | QAM256 | 939000000 Hz | -2.2 dBmV | 41.5 dB | 0 | 0 |
28 | Locked | QAM256 | 945000000 Hz | -2.0 dBmV | 41.6 dB | 0 | 0 |
30 | Locked | QAM256 | 957000000 Hz | -2.1 dBmV | 41.5 dB | 0 | 0 |
31 | Locked | QAM256 | 963000000 Hz | -2.1 dBmV | 41.5 dB | 0 | 0 |
32 | Locked | QAM256 | 969000000 Hz | -2.4 dBmV | 41.4 dB | 0 | 0 |
159 | Locked | Other | 300000000 Hz | 4.2 dBmV | 42.5 dB | 415147869 | 0 |
Upstream Bonded Channels | ||||||
---|---|---|---|---|---|---|
Channel | Channel ID | Lock Status | US Channel Type | Frequency | Width | Power |
1 | 4 | Locked | SC-QAM Upstream | 16900000 Hz | 6400000 Hz | 33.0 dBmV |
2 | 1 | Locked | SC-QAM Upstream | 36300000 Hz | 6400000 Hz | 34.0 dBmV |
3 | 2 | Locked | SC-QAM Upstream | 29900000 Hz | 6400000 Hz | 34.0 dBmV |
4 | 3 | Locked | SC-QAM Upstream | 23500000 Hz | 6400000 Hz | 34.0 dBmV |
5 | 5 | Locked | SC-QAM Upstream | 60000000 Hz | 6400000 Hz | 35.0 dBmV |
6 | 6 | Locked | SC-QAM Upstream | 67000000 Hz | 6400000 Hz | 36.0 dBmV |
7 | 7 | Locked | SC-QAM Upstream | 74000000 Hz | 6400000 Hz | 36.0 dBmV |
8 | 8 | Locked | SC-QAM Upstream | 81000000 Hz | 6400000 Hz | 36.0 dBmV |
Current System Time: Thu Dec 10 13:59:18 2020
skohon25
4 years agoNew Contributor III
Here is the error log
Date Time | Event ID | Event Level | Description |
---|---|---|---|
12/10/2020 13:58 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 13:55 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 13:55 | 82000800 | 3 | "16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 13:55 | 82000600 | 3 | "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 13:55 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 12:54 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 12:54 | 82000800 | 3 | "16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 12:54 | 82000600 | 3 | "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 12:54 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 12:47 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 12:46 | 82000800 | 3 | "16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 12:46 | 82000600 | 3 | "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/10/2020 12:46 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 22:43 | 74010100 | 6 | "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 22:43 | 74010100 | 6 | "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 21:59 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 19:42 | 74010100 | 6 | "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 19:41 | 74010100 | 6 | "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 18:01 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:47 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:46 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:42 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:32 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
12/09/2020 17:30 | 2436694061 | 5 | "Dynamic Range Window violation" |
12/09/2020 17:30 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=8c:61:a3:cb:93:f1;CMTS-MAC=00:29:c2:00:95:cb;CM-QOS=1.1;CM-VER=3.1;" |
- DustinP4 years agoModeratorSkohon25,
Thank you for your patience and providing this information. There's currently an outage investigation alert open in your area at this time, so we will hold off on troubleshooting at this time. You may track outage alerts through our Cox App and each time you see there is an outage, you may request to receive text alerts on the status. If issues should remain for you once the outage clears, then we can take a closer look and run some tests as well.
Dustin
Cox Forum Support Moderator- skohon254 years agoNew Contributor III
Thank you, Dustin. I have a tech scheduled for tomorrow am between 8-10. Is something still being investigated? Would you recommend Me keeping the appointment to ensure everything on my end is tip top?
- Allan4 years agoModerator@Skohon25, I recommend keeping the appointment just in case the outage is not the cause of the issue that you are experiencing. -Allan, Cox Support Forums Moderator.
Related Content
- 4 years ago
- 5 years ago
- 4 years ago