Orbi WiFi 7 RBE973

CM1000V2 terrible upload/download latencies, HUGE SPIKES HUGE HEADACHES.

jaydubzok
Aspirant

CM1000V2 terrible upload/download latencies, HUGE SPIKES HUGE HEADACHES.

PLEASE HELP, BEEN DEALING WITH THESE ISSUES FOR AWHILE, TOTAL HEADACHE.
Been having horrid spikes under load esp with upload when it's spiking well over 100ms and online gaming is **bleep**ing terrible experience too... here's my logs. Spectrum said nothing wrong with their end. 

 
 
Apply             Cancel    
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency

<tabindex=-1>Startup Procedure</tabindex=-1>

ProcedureStatusComment
Acquire Downstream Channel297000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnableBPI+
IP Provisioning ModeHonor MDDIPv4 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>

ChannelLock StatusModulationChannel IDFrequencyPowerSNR / MERUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1LockedQAM2561297000000 Hz7.7 dBmV43.5 dB68140823600
2LockedQAM2562303000000 Hz7.4 dBmV43.0 dB68139741900
3LockedQAM2563309000000 Hz7.5 dBmV43.4 dB68141449900
4LockedQAM2564315000000 Hz7.1 dBmV43.0 dB68141802900
5LockedQAM2565321000000 Hz6.9 dBmV43.2 dB68142217100
6LockedQAM2566327000000 Hz6.9 dBmV42.9 dB68142650000
7LockedQAM2567333000000 Hz6.9 dBmV43.0 dB68142996200
8LockedQAM2568339000000 Hz6.9 dBmV43.3 dB68143456900
9LockedQAM2569345000000 Hz6.9 dBmV43.1 dB68143814500
10LockedQAM25610351000000 Hz6.8 dBmV43.1 dB68144048000
11LockedQAM25611357000000 Hz6.7 dBmV42.9 dB68144520000
12LockedQAM25612363000000 Hz6.8 dBmV43.0 dB68144933200
13LockedQAM25613369000000 Hz6.6 dBmV42.8 dB68145189900
14LockedQAM25614375000000 Hz6.3 dBmV42.9 dB68145546600
15LockedQAM25615381000000 Hz6.2 dBmV42.6 dB68145928700
16LockedQAM25616387000000 Hz6.5 dBmV43.2 dB68146180400
17LockedQAM25617393000000 Hz6.7 dBmV42.9 dB68146656900
18LockedQAM25618399000000 Hz6.8 dBmV43.1 dB68146993300
19LockedQAM25619405000000 Hz7.4 dBmV43.2 dB68147573500
20LockedQAM25620411000000 Hz7.6 dBmV43.3 dB68147859000
21LockedQAM25621423000000 Hz7.5 dBmV43.1 dB68148324100
22LockedQAM25622429000000 Hz7.2 dBmV42.7 dB68148616100
23LockedQAM25623435000000 Hz6.8 dBmV43.0 dB68148934700
24LockedQAM25624447000000 Hz6.4 dBmV42.9 dB68149392700
25LockedQAM25625453000000 Hz6.5 dBmV43.1 dB68149684300
26LockedQAM25626459000000 Hz6.6 dBmV43.1 dB68150187200
27LockedQAM25627465000000 Hz6.9 dBmV43.3 dB68150480700
28LockedQAM25628471000000 Hz7.1 dBmV43.3 dB68150958400
29LockedQAM25629477000000 Hz7.1 dBmV43.3 dB68151263300
30LockedQAM25630483000000 Hz7.1 dBmV43.2 dB68151685000
31LockedQAM25631489000000 Hz7.1 dBmV43.3 dB68151954100
32LockedQAM25632495000000 Hz7.0 dBmV43.3 dB68151847100

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>

ChannelLock StatusModulationChannel IDFrequencyPower
1LockedATDMA224000000 Hz38.3 dBmV
2LockedATDMA330400000 Hz39.0 dBmV
3LockedATDMA436800000 Hz39.3 dBmV
4Not LockedUnknown00 Hz0.0 dBmV
5Not LockedUnknown00 Hz0.0 dBmV
6Not LockedUnknown00 Hz0.0 dBmV
7Not LockedUnknown00 Hz0.0 dBmV
8Not LockedUnknown00 Hz0.0 dBmV

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>

ChannelLock StatusModulation / Profile IDChannel IDFrequencyPowerSNR / MERActive Subcarrier Number RangeUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1Locked0, 1, 233617000000 Hz5.2 dBmV40.5 dB1108 ~ 29873399425492889349660
2Not Locked000 Hz6.6 dBmV0.0 dB0 ~ 4095000

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>

ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
1Locked3, 4, 11, 12, 1395850000 Hz35.5 dBmV
2Not Locked3, 4, 11, 12, 1300 Hz0.0 dBmV
Message 1 of 6
jaydubzok
Aspirant

Re: Need help with CM1000v2, packet loss + high latency with spectrum ISP

Thanks for your quick reply, here's the logs below. Is it the correctables on the downstream that should be 0? Been back and forth with my ISP with no resolution for awhile, new rg6 cables, etc. 

 

Using CAT 8, using a Netduma R2 for a router, I can test here in a bit doing a direct connection. 

 

 

 

 
 
 
 
Time Priority Description
2023-08-18, 21:41:07 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:41:07 Notice (6) US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:56 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:56 Notice (6) US profile assignment change. US Chan ID: 8; Previous Profile: 13; New Profile: 11 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:52 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:48 Notice (6) TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:48 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:48 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:48 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 19:07:56 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 19:07:45 Critical (3) REG RSP not received;CM-MAC=;CMTS-MAC=;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=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 09:33:11 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:57 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:57 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:47 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:45 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:45 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:39 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:37 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:37 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:31 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:31 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:31 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:23 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:22 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:22 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:15 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:13 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:13 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:05 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:03 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:03 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:53 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:53 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:53 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:41 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Message 2 of 6
FURRYe38
Guru

Re: Need help with CM1000v2, packet loss + high latency with spectrum ISP

Yes.

 

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. 
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-Mod...
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/

 

Message 3 of 6
FURRYe38
Guru

Re: CM1000V2 terrible upload/download latencies, HUGE SPIKES HUGE HEADACHES.

Any progress on this?


@jaydubzok wrote:

PLEASE HELP, BEEN DEALING WITH THESE ISSUES FOR AWHILE, TOTAL HEADACHE.
Been having horrid spikes under load esp with upload when it's spiking well over 100ms and online gaming is terrible experience too... here's my logs. Spectrum said nothing wrong with their end. 

Message 4 of 6
jaydubzok
Aspirant

Re: CM1000V2 terrible upload/download latencies, HUGE SPIKES HUGE HEADACHES.

Delete this post, please

Message 5 of 6
FURRYe38
Guru

Re: CM1000V2 terrible upload/download latencies, HUGE SPIKES HUGE HEADACHES.

Were you able to get this resolved? 

 

Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 736 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 7