Have been experiencing some consistenent (daily) intermittent connectivity. Searching based off the logs from the modem it would seem most issues are with some of the bonded channels running hot.
Logs repeadetly spam Event Type Code: 20 and 22 but I'm having a hard time finding documentation that coved the event type codes.
Posting here in hopes that someone can help me fill in the blanks for a resolution.
Startup Procedure |
Procedure | Status | Comment | Acquire Downstream Channel | 525000000 Hz | Locked | Connectivity State | OK | Operational | Boot State | OK | Operational | Security | Enable | BPI+ | IP Provisioning Mode | Honor MDD | IPv6 only |
|
|
Downstream Bonded Channels |
Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR / MER | Unerrored Codewords | Correctable Codewords | Uncorrectable Codewords | 1 | Locked | QAM256 | 20 | 525000000 Hz | 7.2 dBmV | 42.5 dB | 2199444205 | 3 | 0 | 2 | Locked | QAM256 | 8 | 447000000 Hz | 7.6 dBmV | 42.6 dB | 2198291868 | 19 | 0 | 3 | Locked | QAM256 | 9 | 453000000 Hz | 7.4 dBmV | 42.5 dB | 2198295788 | 2 | 0 | 4 | Locked | QAM256 | 10 | 459000000 Hz | 7.3 dBmV | 42.5 dB | 2198295838 | 2 | 0 | 5 | Locked | QAM256 | 11 | 465000000 Hz | 7.2 dBmV | 42.4 dB | 2198304405 | 2 | 0 | 6 | Locked | QAM256 | 12 | 471000000 Hz | 7.3 dBmV | 42.4 dB | 2198302480 | 4 | 0 | 7 | Locked | QAM256 | 13 | 477000000 Hz | 7.3 dBmV | 42.4 dB | 2198309056 | 0 | 0 | 8 | Locked | QAM256 | 14 | 483000000 Hz | 7.6 dBmV | 42.5 dB | 2198316039 | 0 | 0 | 9 | Locked | QAM256 | 15 | 489000000 Hz | 7.6 dBmV | 42.6 dB | 2198362964 | 2 | 0 | 10 | Locked | QAM256 | 16 | 495000000 Hz | 8.1 dBmV | 42.7 dB | 2198365220 | 3 | 0 | 11 | Locked | QAM256 | 17 | 507000000 Hz | 8.2 dBmV | 42.7 dB | 2198367458 | 0 | 0 | 12 | Locked | QAM256 | 18 | 513000000 Hz | 7.5 dBmV | 42.6 dB | 2198370287 | 5 | 0 | 13 | Locked | QAM256 | 19 | 519000000 Hz | 7.6 dBmV | 42.6 dB | 2198377890 | 6 | 0 | 14 | Locked | QAM256 | 21 | 531000000 Hz | 7.3 dBmV | 42.4 dB | 2198379135 | 3 | 0 | 15 | Locked | QAM256 | 22 | 537000000 Hz | 7.1 dBmV | 42.5 dB | 2198386874 | 7 | 0 | 16 | Locked | QAM256 | 23 | 543000000 Hz | 7.1 dBmV | 42.4 dB | 2198388289 | 11 | 0 | 17 | Locked | QAM256 | 24 | 549000000 Hz | 7.1 dBmV | 42.4 dB | 2198533904 | 7 | 0 | 18 | Locked | QAM256 | 25 | 555000000 Hz | 7.1 dBmV | 42.5 dB | 2198534260 | 5 | 0 | 19 | Locked | QAM256 | 26 | 561000000 Hz | 7.3 dBmV | 42.4 dB | 2198537254 | 3 | 0 | 20 | Locked | QAM256 | 27 | 567000000 Hz | 7.3 dBmV | 42.3 dB | 2198546417 | 4 | 0 | 21 | Locked | QAM256 | 28 | 573000000 Hz | 7.5 dBmV | 42.3 dB | 2198539883 | 9 | 0 | 22 | Locked | QAM256 | 29 | 579000000 Hz | 7.4 dBmV | 42.3 dB | 2198551937 | 6 | 0 | 23 | Locked | QAM256 | 30 | 585000000 Hz | 7.5 dBmV | 42.3 dB | 2198552115 | 3 | 0 | 24 | Locked | QAM256 | 31 | 591000000 Hz | 7.1 dBmV | 42.2 dB | 2198563305 | 11 | 0 | 25 | Locked | QAM256 | 32 | 597000000 Hz | 7.4 dBmV | 42.1 dB | 2198566919 | 12 | 0 | 26 | Locked | QAM256 | 33 | 603000000 Hz | 6.8 dBmV | 41.8 dB | 2198561341 | 22 | 0 | 27 | Locked | QAM256 | 34 | 609000000 Hz | 7.0 dBmV | 41.9 dB | 2198573421 | 16 | 0 | 28 | Locked | QAM256 | 35 | 615000000 Hz | 6.6 dBmV | 41.8 dB | 2198566191 | 13 | 0 | 29 | Locked | QAM256 | 36 | 621000000 Hz | 7.0 dBmV | 41.8 dB | 2198584267 | 5 | 0 | 30 | Locked | QAM256 | 37 | 627000000 Hz | 6.8 dBmV | 41.6 dB | 2198585365 | 8 | 0 | 31 | Locked | QAM256 | 38 | 633000000 Hz | 7.0 dBmV | 41.6 dB | 2198583413 | 8 | 0 | 32 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV | 0.0 dB | 0 | 0 | 0 |
|
|
Upstream Bonded Channels |
Channel | Lock Status | Modulation | Channel ID | Frequency | Power | 1 | Locked | ATDMA | 1 | 19300000 Hz | 48.0 dBmV | 2 | Locked | ATDMA | 2 | 25700000 Hz | 48.3 dBmV | 3 | Locked | ATDMA | 3 | 32300000 Hz | 48.8 dBmV | 4 | Locked | ATDMA | 4 | 38700000 Hz | 49.5 dBmV | 5 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV | 6 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV | 7 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV | 8 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV |
|
|
Downstream OFDM Channels |
Channel | Lock Status | Modulation / Profile ID | Channel ID | Frequency | Power | SNR / MER | Active Subcarrier Number Range | Unerrored Codewords | Correctable Codewords | Uncorrectable Codewords | 1 | Locked | 0, 1, 2, 3 | 48 | 850000000 Hz | 3.8 dBmV | 38.5 dB | 1108 ~ 2987 | 8457828872 | 8117812284 | 12 | 2 | Not Locked | 0 | 0 | 0 Hz | 8.3 dBmV | 0.0 dB | 0 ~ 4095 | 0 | 0 | 0 |
|
|
Upstream OFDMA Channels |
Channel | Lock Status | Modulation / Profile ID | Channel ID | Frequency | Power | 1 | Not Locked | Unknown | 0 | 0 Hz | 0 dBmV | 2 | Not Locked | Unknown | 0 | 0 Hz | 0 dBmV |
|
Time | Priority | Description |
2020-12-22, 14:47:03 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 14:46:17 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 14:46:06 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 14:45:17 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:55:57 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:54:47 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:25:46 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:21:04 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:19:40 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:19:15 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:17:29 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:17:00 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:16:38 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:15:54 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:13:49 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:13:25 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:12:09 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
2020-12-22, 10:11:43 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:b9:8a:b0:38:78;CMTS-MAC=00:01:5c:65:74:76;CM-QOS=1.1;CM-VER=3.1; |
EG
Expert
•
111.4K Messages
5 years ago
The downstream power is not too hot. It's borderline in spec. It's the upstream power that is on the high side and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
0
0