Modem techies: Need advice Please
I really just need to be pointed in the right direction because I am being sent in circles. I have Gigablast and normally I have no issues. A couple months ago, there was a worker in a bucket truck...
Forum Discussion
Well, the difference between Corrected and Uncorrected tells the story. It's now 0.
SNR (Signal to Noise Ratio)
This is how clear the downstream signal at your modem.
For 256 QAM
Minimum: 30 dB
Recommended: 33+ dB
Before/After
• Before, you had averaged almost Minimum at 36 dB
• After, you had averaged better than Recommended at 44 dB
• You gained an average of + 7.34 dB
Downstream Power
This is the amount of signal from Cox to your modem.
Recommended: - 7 to + 7 dBmV
Acceptable but out of spec: +/- 8 to +/-10 dBmV
Maximum but out of spec: +/- 11 to +/- 15 dBmV
Before/After
• Before, your Power appeared to be within spec
• After, your Power still appears to be within spec but gain an average of 3.60 dBmV
If anything, your signal got clearer.
Ingress is just a perceptive. If you're testing on the Cox network (outside your house), ingress would be noise coming from your house onto the Cox network. As a Cox tech, I'm sure the tech would call it ingress.
If you were testing inside your house, ingress would be noise coming from the Cox network onto your house. The tech said your house is creating noise. Just to be clear, the previous tech(s) did not detect or report ingress?
Was this ingress before or after your husband bypassed the splitters? Meaning, what was connected inside your house...just the modem and speed-testing laptop or everything? I think the tech tested before your husband tested.
This appears you have faulty splitters. Others are much smarter at this than I, so let's see what they conclude.
Lol, once again, I had a whole reply and I keep losing internet. Once, right as I hit send, so I am having to retype everything lol. This might take a while to get posted lol.
You were correct in that the previous tech said that everything looked good when he tested.
The modem logs that I posted were after hubby bypassed the splitter but before the tech got here and we only used 1 computer.
Now, hubby did bypass splitters BEFORE the tech came out today and we left them like that for the duration of the testing when the tech was here (which he reported ingress).
After the tech left, hubby had to get back to working so I hooked the router back up. I should have made a copy of the modem logs before I hooked up the router, but the uncorrectables were starting to show up prior to hooking up router, but in low digits and they weren't in every channel yet like they are now.
Now here we are a little over 4 hours since a modem reboot and the uncorrectables are climbing again. I don't know if that's normal.
For the record, we are still bypassing splitters at the moment.
Connection
Top of Form
Startup Sequence
Startup Step
Status
Comment
Acquire Downstream Channel
381000000 Hz
Locked
Upstream Connection
OK
Operational
Boot State
OK
Operational
Configuration File
OK
Security
Enabled
BPI+
Connection Status
System Up Time
0 days 04h:16m:06s
Network Access
Allowed
Downstream Bonded Channels
Channel
Lock Status
Modulation
Channel ID
Freq. (MHz)
Pwr (dBmV)
SNR (dB)
Corrected
Uncorrected
1
Locked
QAM256
37
381.0
8.2
45.1
22113
61582
2
Locked
QAM256
1
681.0
3.8
42.3
32923
84538
3
Locked
QAM256
2
687.0
4.0
42.2
32814
81781
4
Locked
QAM256
3
693.0
4.0
42.4
32998
78549
5
Locked
QAM256
4
699.0
4.1
42.5
29050
70096
6
Locked
QAM256
5
705.0
4.3
42.7
28504
66630
7
Locked
QAM256
6
711.0
4.4
42.6
26986
63722
8
Locked
QAM256
7
717.0
4.5
42.6
24285
56670
9
Locked
QAM256
8
723.0
4.4
42.3
22326
53606
10
Locked
QAM256
9
729.0
4.6
42.5
22038
53082
11
Locked
QAM256
10
735.0
4.6
42.3
22504
55605
12
Locked
QAM256
11
741.0
4.6
42.5
21889
54873
13
Locked
QAM256
12
747.0
4.5
41.8
25795
66973
14
Locked
QAM256
13
753.0
4.9
42.5
25418
64216
15
Locked
QAM256
14
759.0
4.8
42.5
26050
63289
16
Locked
QAM256
15
765.0
4.5
42.3
25158
59648
17
Locked
QAM256
16
771.0
4.3
42.2
25623
57677
18
Locked
QAM256
33
357.0
7.8
44.7
14396
45188
19
Locked
QAM256
34
363.0
7.8
44.7
52520
177925
20
Locked
QAM256
35
369.0
8.1
45.0
32937
108602
21
Locked
QAM256
36
375.0
8.3
45.3
22930
74822
22
Locked
QAM256
38
387.0
8.1
45.4
19901
47780
23
Locked
QAM256
39
393.0
8.4
45.4
30608
93284
24
Locked
QAM256
40
399.0
8.3
45.5
65058
214457
25
Locked
QAM256
41
405.0
8.1
45.8
38570
122556
26
Locked
QAM256
42
411.0
8.1
45.5
37540
109817
27
Locked
QAM256
43
417.0
8.2
45.5
61588
195018
28
Locked
QAM256
44
423.0
7.9
45.3
43187
136936
29
Locked
QAM256
45
429.0
7.7
45.2
38070
121799
30
Locked
QAM256
46
435.0
7.6
45.2
23827
68551
31
Locked
QAM256
47
441.0
7.4
45.0
26101
79029
32
Locked
QAM256
48
447.0
7.2
44.9
32013
104582
33
Locked
OFDM PLC
159
300.0
7.8
43.4
4992219
76932
Upstream Bonded Channels
Channel
Lock Status
Channel Type
Channel ID
Symb. Rate (Ksym/sec)
Freq. (MHz)
Pwr (dBmV)
1
Locked
SC-QAM
1
5120
36.8
38.0
2
Locked
SC-QAM
2
5120
30.4
38.0
3
Locked
SC-QAM
3
5120
24.0
37.5
4
Locked
SC-QAM
4
5120
17.6
37.5
5
Locked
SC-QAM
5
5120
60.0
39.3
6
Locked
SC-QAM
6
5120
67.0
39.8
7
Locked
SC-QAM
7
5120
74.0
40.3
8
Locked
SC-QAM
8
5120
81.0
40.3
Downstream Frequency Setting
Downstream Frequency Select
Bottom of Form
Event Log
Top of Form
Event Log
Time
Priority
Description
15:19:53
Thu Jan 6 2022Notice (6)
Honoring MDD; IP provisioning mode = IPv4
15:19:57
Thu Jan 6 2022Warning (5)
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:19:57
Thu Jan 6 2022Notice (6)
TLV-11 - unrecognized OID;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:20:02
Thu Jan 6 2022Warning (5)
REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:20:02
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:20:02
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
15:20:02
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:20:02
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
15:20:02
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:20:02
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
15:20:02
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:20:02
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
15:20:02
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:20:02
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
15:20:03
Thu Jan 6 2022Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:20:03
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:20:03
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
15:20:04
Thu Jan 6 2022Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:28:13
Thu Jan 6 2022Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:28:13
Thu Jan 6 2022Warning (5)
Dynamic Range Window violation
15:29:14
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:29:35
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:29:49
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:29:49
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:31:21
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:31:21
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:31:45
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:31:45
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:32:20
Thu Jan 6 2022Critical (3)
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:32:23
Thu Jan 6 2022Warning (5)
DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:32:27
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
15:32:27
Thu Jan 6 2022Notice (6)
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;
Bottom of Form
Ok...4 hours later your signal still looks in specs.
Correctable and Uncorrectable identify packet loss. You will always have some errors unless you live next door to Cox. Correctable is the number of packets corrected. Uncorrectable is the number of packets so corrupt your modem had to request a resend from Cox.
Uncorrectable are your most concerning. You'll typically see 1 or 2 channels with high Uncorrectables due to interference from specific frequencies.
You, however, have Uncorrectables on all frequencies, so something is causing interference.
Since a couple months ago, did you install new electronic devices in your home? Hammer any nails into a wall? Has anybody inspected the 4-foot segment of coax flapping in the breeze outside your house for wear, tear, chaffing?
When you or your husband were in the attic and aside from the 4 segments of coaxial cable and 2 splitters, did you notice any other electronic components, such as an amplifier, filter or tap?
Ok. Hubby says he did not see any electrical components in the attic. There's really no new devices in the home either. Only a smart plug that I only use during Christmas for the tree, but I did a whole device elimination test even prior to the plug since I was already having issues. I actually did some wifi device moving the other week because the tech that was out here said maybe I had too many devices on one channel. (I laughed because I had a total of 9 devices spread across 3 channels at the time, but I removed them and added 1 at a time anyway to be sure)
I believe the tech today took a quick look at the 4 ft section of cable outside but I know hubby did as well and he didn't see anything that stood out.
Hubby is going to try and make a run to home depot tonight or tomorrow to get the high performance splitter like Mouth suggested cuz it looks like from Amazon it wouldn't get here until next week. Hopefully that will fix one of my issues.
I am trying not to get too frustrated with all this. It's just crazy to think everything just blew up all at once, when everything was working all good a couple months ago.
I really appreciate all the time yall have taken trying to help me, so please let me know when I have worn out my welcome lol.
