New Poster
•
3 Messages
Multiple Daily Outages for ~5 Minutes Each - "No Ranging Response received"
I have Xfinity Gigabit Internet plan with a Netgear CM1200 modem. Every day, there is one or more network outage where there is no connectivity at all for about 5-10 minutes. It happens randomly with no specific pattern. I've verified that it isn't my home networking equipment as I've been connected wired directly to the modem and the issue still occurs.
The modem logs during the outage are copied below. There are multiple "Critical" type logs including "No Ranging Response received - T3 time-out" and "no Unicast Maintenance opportunities received - T4 time out". I've seen other posts similar to this where Comcast stepped into help. Hope that can happen here or others from the community can suggest what to do. Link aggregation (LACP) is disabled on the modem which is the only known related issue I could find related to CM1200.
Time | Priority | Description |
Tue Jun 09 13:13:44 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:13:42 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:12:33 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:12:02 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:11:59 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:11:38 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:11:38 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:11:25 2020 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Tue Jun 09 13:11:17 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:11:02 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:11:02 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:11:02 2020 | 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=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:11:01 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:11:00 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:10:59 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:10:58 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:10:54 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:10:53 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:10:51 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:10:44 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:09:44 2020 | 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=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:09:34 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:09:07 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:09:07 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:09:02 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:57 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:56 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:46 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:46 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:36 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:29 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:26 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:24 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:15 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:13 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:08:05 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:07:54 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:07:26 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:07:02 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 09 13:07:00 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Accepted Solution
EG
Expert
•
111.5K Messages
5 years ago
The upstream power 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, and latency problems.
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
EG
Expert
•
111.5K Messages
5 years ago
Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
0
0
ravishi
New Poster
•
3 Messages
5 years ago
Hi EG,
I copied the contents of the "Cable Connection" page below. Note that this capture is when the internet is working normally. Hope this helps.
Status
Profile ID
ID
MER
Number Range
Codewords
Codewords
Codewords
0
0
ravishi
New Poster
•
3 Messages
5 years ago
Thanks EG! I'm in an apartment so I can't control all splitters on the line but I'm not using any inside the apartment. However, I reseated the connection to the modem and rebooted it. I'm not an expert on what I should be looking for but the downstream power is higher and the upstream power is lower. I pasted the updated "Cable Connection" output below. I'll keep an eye on any outages over the next couple days. If none, I'll come back and mark your reply as "Best Answer". Thanks for your help so far!
Status
Profile ID
ID
MER
Number Range
Codewords
Codewords
Codewords
0
0
EG
Expert
•
111.5K Messages
5 years ago
These are the desired Comcast specs from the troubleshooting tips sticky topic at the top of the board;
0
Mac_guru
New Poster
•
1 Message
5 years ago
So when I check my cable settings, My download are all < 1
Is this cause for concern? I am losing packets, and have also seen the "No Ranging response received" message, although not as frequently.
Thanks!
0
0