Orbi WiFi 7 RBE973
Reply

CM2000 event log

Old_Soldier
Apprentice

CM2000 event log

Only showing these eight entries, in the event log and the top one gets overwritten 2-3x a day. Anyone have any ideas?

 
Time Priority Description
Sat Mar 16 05:20:47 2024(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 14:57:15 2024(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 14:57:09 2024(Notice (6))TLV-11 - unrecognized OID;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Time Not Established(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 14:56:01 2024(Critical (3))Resetting the cable modem due to docsDevResetNow
Fri Mar 08 02:31:44 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Message 1 of 11
plemans
Guru

Re: CM2000 event log

got a copy of the screensnip of the cable connections page? 

From the event log, your power level is going out of optimal range and then having signal issues back to the isp. 

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.
If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.

Message 2 of 11
Old_Soldier
Apprentice

Re: CM2000 event log

I'm on Xfinity and have been going around and around with them to solve an intermitant problem, for the past month. I've had four techs out and one was here, twice. He's the one that actually did anything, that helped. He removed an unneeded splitter, connected a new underground cable, from the pedestal to the distribution boxes, after checking connections there. No ampifiers in use, either. Working theory is in wall coax is sketchy and since I live in an apartment complex, there's nothing more that can be done, as yet.

Just rebooted the modem, because of websites weren't loading completely.

Current log:

Sat Mar 16 10:57:28 2024(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 16 10:42:15 2024(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 16 10:42:08 2024(Notice (6))TLV-11 - unrecognized OID;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Time Not Established(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 16 10:40:59 2024(Critical (3))Resetting the cable modem due to docsDevResetNow
Time Not Established(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 14:56:01 2024(Critical (3))Resetting the cable modem due to docsDevResetNow
Fri Mar 08 02:31:44 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Message 3 of 11
Old_Soldier
Apprentice

Re: CM2000 event log

I've cleared the logs, twice, since 1 March. Number of log entries doesn't change much, except for the RNG-RSP entry continually overwriting the previous one.

Message 4 of 11
Old_Soldier
Apprentice

Re: CM2000 event log

Procedure Status Comment
Acquire Downstream Channel507000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
IP Provisioning ModeHonor MDDIPv6 only
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1LockedQAM2565507000000 Hz-0.1 dBmV37.4 dB00
2LockedQAM2562489000000 Hz-0.3 dBmV37.3 dB00
3LockedQAM2563495000000 Hz-0.2 dBmV37.4 dB00
4LockedQAM2564501000000 Hz-0.1 dBmV37.4 dB00
5LockedQAM2566513000000 Hz0.0 dBmV37.4 dB00
6LockedQAM2567519000000 Hz0.0 dBmV37.4 dB00
7LockedQAM2568525000000 Hz-0.1 dBmV37.3 dB00
8LockedQAM2569531000000 Hz-0.1 dBmV37.3 dB00
9LockedQAM25610537000000 Hz0.0 dBmV37.3 dB00
10LockedQAM25611543000000 Hz-0.1 dBmV37.3 dB00
11LockedQAM25612549000000 Hz-0.1 dBmV37.3 dB00
12LockedQAM25613555000000 Hz0.0 dBmV37.4 dB00
13LockedQAM25614561000000 Hz0.1 dBmV37.5 dB00
14LockedQAM25615567000000 Hz0.2 dBmV37.4 dB00
15LockedQAM25616573000000 Hz0.2 dBmV37.5 dB00
16LockedQAM25617579000000 Hz0.1 dBmV37.4 dB00
17LockedQAM25618585000000 Hz0.1 dBmV37.1 dB00
18LockedQAM25619591000000 Hz0.2 dBmV37.4 dB00
19LockedQAM25620597000000 Hz0.1 dBmV37.5 dB00
20LockedQAM25621603000000 Hz0.1 dBmV37.5 dB00
21LockedQAM25622609000000 Hz0.2 dBmV37.6 dB00
22LockedQAM25623615000000 Hz0.0 dBmV37.6 dB00
23LockedQAM25624621000000 Hz-0.1 dBmV37.6 dB00
24LockedQAM25625627000000 Hz-0.2 dBmV37.6 dB00
25LockedQAM25626633000000 Hz-0.5 dBmV37.6 dB00
26LockedQAM25627639000000 Hz-0.6 dBmV37.7 dB00
27LockedQAM25628645000000 Hz-0.6 dBmV37.9 dB00
28LockedQAM25629651000000 Hz-1.2 dBmV37.8 dB00
29LockedQAM25630657000000 Hz-1.3 dBmV37.8 dB00
30LockedQAM25631663000000 Hz-1.6 dBmV37.8 dB00
31LockedQAM25632669000000 Hz-2.0 dBmV37.7 dB00
32Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1LockedATDMA15120 Ksym/sec35600000 Hz42.5 dBmV
2LockedATDMA45120 Ksym/sec16400000 Hz41.8 dBmV
3LockedATDMA25120 Ksym/sec29200000 Hz42.5 dBmV
4LockedATDMA35120 Ksym/sec22800000 Hz42.3 dBmV
5LockedATDMA91280 Ksym/sec39600000 Hz42.5 dBmV
6Not LockedUnknown0000.0 dBmV
7Not LockedUnknown0000.0 dBmV
8Not LockedUnknown0000.0 dBmV
 
Downstream OFDM Channels
Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1Locked0 ,1 ,2 ,337690000000 Hz-0.02 dBmV37.7 dB1108 ~ 298746148216461214770
2Not Locked000 Hz0 dBmV0 dB0 ~ 4095000
 
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1Not Locked000 Hz0 dBmV
2Not Locked000 Hz0 dBmV
 
Extended Upstream Transmit Power
 

 

 
Current System Time:Sat Mar 16 11:25:12 2024
System Up Time:00:43:46
 
 
 
Message 5 of 11
Old_Soldier
Apprentice

Re: CM2000 event log

Cable status shows as good. CM, downstream and upstream show green.

Message 6 of 11
Old_Soldier
Apprentice

Re: CM2000 event log

@plemansHave you had a chance to look at the data, yet? Still getting the RNG-RSP error and waiting on Xfinity to do something constructive, aside from what's been done. TIA

Message 7 of 11
plemans
Guru

Re: CM2000 event log

Your logs indicate line issues. 

So it can be any number of things. 

1. It could be the modem. Always a chance but usually not

2. the line/connectors. Even if they replaced them, it could've been a poor job/technician doing it. Not the first time

3. the hub. I've seen them loose at the hub. 

 

You're a little caught. Xfinity isn't going to try very hard because you're not using their device. I've had to actually rent one of there devices to come check my line again (because it still had issues)

Message 8 of 11
Old_Soldier
Apprentice

Re: CM2000 event log

I had one of their xb8 gateways and still had the same problems. I'm convinced it's back up the line at the CMTS, whereever it is. Nobody wants to actually go there and have a look, though, from what I'm getting.

Message 9 of 11
plemans
Guru

Re: CM2000 event log


@Old_Soldier wrote:

I had one of their xb8 gateways and still had the same problems. I'm convinced it's back up the line at the CMTS, whereever it is. Nobody wants to actually go there and have a look, though, from what I'm getting.


If their XB8 and the CM2000 have the same issue, it reduces the odds of it being the modem. You're a little caught as ISP's fight not to do more than they have to.

Live by anyone else that is having the same issue? 

Could be if a couple people are having the same issue, it might put additional pressure on them to recheck the line/hub

Message 10 of 11
Old_Soldier
Apprentice

Re: CM2000 event log

Sorry about not replying sooner, dealing with family problems, right now. To answer your question, no, I don't know of anyone else in the building that is on Xfinity that is having trouble. I strongly suspect that they don't know, don't use the internet as much as I do or just haven't bothered to complain to Xfinity. Support is looking into why the event log has so few entries, compared to the Motorola MB8611 I have and its been elevated to tier 2. As far as Xfinity goes, they've done nothing at all, beyond sending three techs out, one twice and promised to contact the complex manager, which hasn't happened either.

Message 11 of 11
Top Contributors
Discussion stats
  • 10 replies
  • 918 views
  • 3 kudos
  • 2 in conversation
Announcements

Orbi 770 Series