NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nighthawk CM2000, RAXE300, pfSense CE, XS712Tv2 12-Port 10G Managed Switch Setup
A brief recap: Have used a pfSense virtual machine router/firewall for over a decade. A switch to Spectrum 1Gig Ethernet 2yrs ago forced a double NAT situation as could never succeed in coupling Spectrum modem to pfSense VM w/o Spectrum router betwixt them. Thought was to go all in on Netgear Nighthawk CM2000 and RAXE300 to resolve the double NAT w/ routing order ISP-CM2000-pfSenseVM-10G ManagedSwitch-RAXE300 Access Point. Connections to Internet proved intermittent at best.
CM2000 Event Log highlighted possible issues
Event Log
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
A splitter exposed to the elements dripped water when shaken. Spectrum arrived at 8AM July 3rd then forcibly urged up a ladder into the crawlspace above the garage to run coax cable to an open wall where additional electric outlets were being installed. Tech showed via an app that his home ethernet had the same Critical & Error values as above but allowed that the splitter was problematic.
And Voila! Internet worked on 1st power cycling. Spectrum tech left victorious and things rapidly went downhill. Cloned the pfSense VM instance, rebooted to add VLANs but no more Internet. Spectrum bumped (which I believe means reprovisioned) the modem several times then spotted a variation in the signal and sent another tech who worked a couple hours until all passed spec.
At this point however, the CM2000 seemed dead. Power cycled repeatedly yet the modem was no longer offering DHCP to the pfSense. The pfSense System Logs for DHCP, General and Gateways were devoid of activity. Spinning new pfSense VMs presented the same. It was decided the CM2000 was dead. Purchased a new one which arrived this morning.
After Spectrum provisioned the new modem nothing changed. Connecting the CM2000 directly to a laptop could establish Internet connectivity. pfSense v2.72 simply would not. Spent two hours with Netgear tech support who declared the new CM2000 fully functional. The only way that it will establish Internet connection through the pfSense is to re-introduce the RAXE300 as a buffer between the CM2000 and the pfSense router forcing a double NAT.
Surely there must be means by which Netgear pfSense can communicate with a Netgear Modem.
What parameters of the RAXE300 allow it to communicate with the CM2000?
Should one not accept leases from the CM2000 192.168.100.1 address?
Apparently many rely on Status/Interfaces/Release Wan to establish connectivity but does this not require System/Routing/Gateways to be entered? Else how do these show up?
|
O mio remorso! I apologize profusely to all. What ocean is deep enough to hide my tears of shame?
Every step has been a mistake: pfSense is Netgate, not Netgear!
The premise for every action taken over the past month was thus sorely flawed.
Your good graces have been abused. And oh! Netgear tech admonished for never having heard of pfSense; Spectrum tech urged into the crawlspace with a weed whacker, to each unjust.
Fare well! and if for ever, still for ever, fare thee well!
14 Replies
Replies have been turned off for this discussion
Please post a copy and paste of the modems connection status page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-routerAny Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
Had gone over the post length limit so had to delete. This is from the new CM2000 that arrived this morning. Connection Page:
Startup Procedure
Procedure
Status
Comment
Acquire Downstream Channel
471000000 Hz
Locked
Connectivity State
OK
Operational
Boot State
OK
Operational
Security
Enabled
BPI+
Downstream Bonded Channels
Channel
Lock Status
Modulation
Channel ID
Frequency
Power
SNR
Correctables
Uncorrectables
1
Locked
QAM256
33
471000000 Hz
3.2 dBmV
42.3 dB
0
0
2
Locked
QAM256
2
267000000 Hz
6.0 dBmV
42.5 dB
0
0
3
Locked
QAM256
3
273000000 Hz
5.8 dBmV
42.5 dB
0
0
4
Locked
QAM256
4
279000000 Hz
5.7 dBmV
42.5 dB
0
0
5
Locked
QAM256
5
285000000 Hz
5.6 dBmV
42.6 dB
0
0
6
Locked
QAM256
6
291000000 Hz
5.6 dBmV
42.5 dB
0
0
7
Locked
QAM256
7
297000000 Hz
5.4 dBmV
42.4 dB
0
0
8
Locked
QAM256
8
303000000 Hz
5.2 dBmV
42.4 dB
0
0
9
Locked
QAM256
9
309000000 Hz
5.2 dBmV
42.5 dB
0
0
10
Locked
QAM256
10
315000000 Hz
5.0 dBmV
42.6 dB
0
0
11
Locked
QAM256
11
321000000 Hz
4.8 dBmV
42.4 dB
0
0
12
Locked
QAM256
12
327000000 Hz
4.6 dBmV
42.4 dB
0
0
13
Locked
QAM256
13
333000000 Hz
4.4 dBmV
42.3 dB
0
0
14
Locked
QAM256
14
339000000 Hz
4.4 dBmV
42.3 dB
0
0
15
Locked
QAM256
15
345000000 Hz
4.4 dBmV
42.4 dB
0
0
16
Locked
QAM256
16
351000000 Hz
4.2 dBmV
42.3 dB
0
0
17
Locked
QAM256
17
357000000 Hz
4.2 dBmV
42.3 dB
0
0
18
Locked
QAM256
18
363000000 Hz
4.1 dBmV
42.3 dB
0
0
19
Locked
QAM256
19
369000000 Hz
4.1 dBmV
42.3 dB
0
0
20
Locked
QAM256
20
375000000 Hz
3.9 dBmV
42.2 dB
0
0
21
Locked
QAM256
21
381000000 Hz
3.7 dBmV
42.2 dB
0
0
22
Locked
QAM256
22
387000000 Hz
3.7 dBmV
42.3 dB
0
0
23
Locked
QAM256
23
393000000 Hz
3.6 dBmV
42.3 dB
0
0
24
Locked
QAM256
24
399000000 Hz
3.5 dBmV
42.3 dB
0
0
25
Locked
QAM256
26
405000000 Hz
3.3 dBmV
41.9 dB
0
0
26
Locked
QAM256
27
411000000 Hz
3.3 dBmV
42.2 dB
0
0
27
Locked
QAM256
28
417000000 Hz
3.1 dBmV
42.1 dB
0
0
28
Locked
QAM256
29
423000000 Hz
2.9 dBmV
42.0 dB
0
0
29
Locked
QAM256
30
453000000 Hz
3.1 dBmV
42.2 dB
0
0
30
Locked
QAM256
31
459000000 Hz
3.1 dBmV
41.9 dB
0
0
31
Locked
QAM256
32
465000000 Hz
3.1 dBmV
42.2 dB
0
0
32
Not Locked
Unknown
0
0 Hz
0.0 dBmV
0.0 dB
0
0
Upstream Bonded Channels
Channel
Lock Status
US Channel Type
Channel ID
Symbol Rate
Frequency
Power
1
Locked
ATDMA
81
5120
17800000 Hz
41.5 dBmV
2
Locked
ATDMA
82
5120
24200000 Hz
42.8 dBmV
3
Locked
ATDMA
83
5120
30600000 Hz
43.8 dBmV
4
Locked
ATDMA
84
5120
37000000 Hz
44.5 dBmV
5
Not Locked
Unknown
0
0
0 Hz
0.0 dBmV
6
Not Locked
Unknown
0
0
0 Hz
0.0 dBmV
7
Not Locked
Unknown
0
0
0 Hz
0.0 dBmV
8
Not Locked
Unknown
0
0
0 Hz
0.0 dBmV
Downstream OFDM Channels
Channel
Lock
StatusModulation /
Profile IDChannel
IDFrequency
Power
SNR /
MERActive Subcarrier
Number RangeUnerrored
CodewordsCorrectable
CodewordsUncorrectable
Codewords1
Locked
0 ,1 ,2
25
656000000 Hz
3.0 dBmV
41.3 dB
868 ~ 3227
392376174
386649668
0
2
Not Locked
0
0
0 Hz
0 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
0
0
0 Hz
0 dBmV
2
Not Locked
0
0
0 Hz
0 dBmV
Extended Upstream Transmit Power
Current System Time:Thu Jul 04 14:30:30 2024
System Up Time:02:27:04
New CM2000 Event Log:
Time
Priority
Description
Thu Jul 04 12:04:09 2024
(Notice (6))
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 12:04:04 2024
(Notice (6))
TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 12:04:03 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 12:04:03 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
(Notice (6))
Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not Established
(Critical (3))
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 11:42:06 2024
(Notice (6))
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 11:42:01 2024
(Notice (6))
TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 11:42:00 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 11:42:00 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
(Notice (6))
Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not Established
(Critical (3))
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 11:10:23 2024
(Notice (6))
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 11:10:18 2024
(Notice (6))
TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 11:10:18 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 11:10:18 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
(Notice (6))
Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not Established
(Critical (3))
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 10:06:01 2024
(Notice (6))
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 10:05:56 2024
(Notice (6))
TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 10:05:55 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 10:05:55 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
(Notice (6))
Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not Established
(Critical (3))
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 09:54:31 2024
(Notice (6))
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 09:54:26 2024
(Notice (6))
TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 09:54:25 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 09:54:25 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
(Notice (6))
Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not Established
(Critical (3))
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 08:58:15 2024
(Notice (6))
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 08:58:10 2024
(Notice (6))
TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 08:58:10 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 08:58:10 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
(Notice (6))
Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not Established
(Critical (3))
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 08:01:38 2024
(Notice (6))
DHCP Renew - lease parameters Time Protocol Servers modified;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 07:51:53 2024
(Notice (6))
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 07:51:48 2024
(Notice (6))
TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 04 07:51:47 2024
(Error (4))
Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:46:ee:8f:b8:6b;CMTS-MAC=00:01:5c:8f:98:68;CM-QOS=1.1;CM-VER=3.1;
Power levels are good and no correctables or uncorrectables.
Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box.
Be sure your using good quality RG6 coax cable up to the modem.
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/
