New Poster
•
5 Messages
Netgear Router - Started Unicast Maintenance Ranging
Hi all,
Did some googling and saw a lot of people have been seeing this issue as of late. I have a Netgear CM1150v router plugged in, up until a month ago signal was fine and no issues. Lately it has been dropping all the time. I remote into my work machine so this regularly impacts my job and has been quite frustrating to me throughout my day and I would like some help.
I have attached the event log from my routers page, I have seen others do that with this issue to help get eyes on what is going on.
Thu Jan 07 08:42:08 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 07 04:34:39 2021 | Warning (5) | TEK Invalid - Invalid Key Sequence Number;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 07 04:32:25 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 07 03:04:50 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 07 03:04:26 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 07 03:02:42 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 21:43:42 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 21:43:10 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 21:41:38 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 19:27:51 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 19:27:34 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 19:26:50 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 19:26:49 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 19:07:38 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 18:48:43 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 18:48:41 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 18:48:00 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 18:46:53 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 17:44:38 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 15:32:59 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 15:32:03 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 15:28:00 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 15:08:10 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 15:08:06 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 15:07:29 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 15:07:27 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 15:05:08 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 14:33:43 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 14:33:11 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 14:30:50 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 14:14:38 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 14:13:49 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 14:13:10 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 13:59:06 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 13:59:04 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 13:58:29 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 13:58:14 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 13:56:01 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 13:17:36 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan 06 13:17:12 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d4:f3:68;CMTS-MAC=00:01:5c:85:cc:66;CM-QOS=1.1;CM-VER=3.1; |
quartarolo_home
New Poster
•
5 Messages
4 years ago
Here is the Upstream/Downstream from the cable connections page,
Status
Profile ID
ID
MER
Number Range
Codewords
Codewords
Codewords
0
0
EG
Expert
•
111.5K Messages
4 years ago
The upstream power is way too high / out of spec. 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
quartarolo_home
New Poster
•
5 Messages
4 years ago
Yeah I checked everything going up to the attic and still the issue persists. This started about a month ago, before this everything was fine and there were no changes to any of the wiring in the house.
0
0
quartarolo_home
New Poster
•
5 Messages
4 years ago
I will have to investigate more to see if their is one I am missing, at this point I have not had any drops since eliminating the one splitter.
0
0
quartarolo_home
New Poster
•
5 Messages
4 years ago
I eliminated a splitter and this is the upstream now
0
0
EG
Expert
•
111.5K Messages
4 years ago
It's marginal. 40 to 45 dB would be ideal !
If there is nothing more that you can do to improve it then as stated, you'll need to get a tech out to investigate the problem.
Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home.
0
0
XfinityAmira
Official Employee
•
4.2K Messages
4 years ago
Hello @quartarolo_home, thanks for reaching out to our Digital Care Team on Forums. We appreciate you being a customer with us and I am sorry to hear about the connection issues you have been experiencing. We also apologize for the delay in getting back to you but I am happy to hear removing one splitter may have corrected this issue for you. I would like to confirm, has the Internet connection still been solid and steady with no drops on your end?
0
0