cancel
Showing results for 
Search instead for 
Did you mean: 

Packet Loss after VM outage

Kay4
On our wavelength

Two days ago we had one of those brief outages that took over an hour to recover from, having to factory reset modem and router. Ever since we've had packet losses, currently 16% using https://packetlosstest.com/

Is this due to whatever was going on at the time with VM, could it be an SNR, how do I get it fixed?

1 ACCEPTED SOLUTION

Accepted Solutions

Client62
Hero

The reported 16% packet loss may well be due to the choice of settings for : https://packetlosstest.com/ after all this test will record a packet as lost when it is delivered later that the chosen latency limit.

Looking at the 3.0 DOCSIS Downstream stats, Power levels are at the very high end of the spectrum, but so far errors do not appear to be a problem. If the power rises further ( dBmV > 10 )  that would be a concern.

Looking at the 3.0 DOCSIS Upstream stats, the QAM 32 on all channels indicates a local noise issue.

See where this Helpful Answer was posted

8 REPLIES 8

Kay4
On our wavelength
Refresh data
Item Status TypeChannel Overview Downstream Upstream
Cable Modem StatusOnlineDOCSIS 3.0
Primary downstream channelLockedSC-QAM
DOCSIS 3.0 channels315
DOCSIS 3.1 channels11

Kay4
On our wavelength
 

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13310000008.242QAM 25625
213900000010.342QAM 2561
31470000009.941QAM 2562
41550000009.841QAM 2563
51630000009.541QAM 2564
61710000009.641QAM 2565
71790000009.341QAM 2566
81870000009.341QAM 2567
91950000009.341QAM 2568
102030000009.341QAM 2569
112110000009.441QAM 25610
122190000009.541QAM 25611
132270000009.241QAM 25612
142350000009.141QAM 25613
152430000008.741QAM 25614
162510000008.542QAM 25615
172590000008.542QAM 25616
18267000000942QAM 25617
192750000009.542QAM 25618
202830000009.642QAM 25619
212910000009.242QAM 25620
222990000008.842QAM 25621
233070000008.542QAM 25622
243150000008.342QAM 25623
253230000008.242QAM 25624
263390000008.542QAM 25626
273470000008.642QAM 25627
283550000008.642QAM 25628
293630000008.641QAM 25629
303710000008.741QAM 25630
31379000000941QAM 25631

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked42613
2Locked42636
3Locked41931
4Locked41829
5Locked41628
6Locked41523
7Locked41618
8Locked41417
9Locked41314
10Locked41116
11Locked41215
12Locked41314
13Locked41116
14Locked41214
15Locked41215
16Locked42314
17Locked42115
18Locked42215
19Locked42115
20Locked42214
21Locked42414
22Locked42314
23Locked42413
24Locked42413
25Locked42314
26Locked42315
27Locked42613
28Locked42413
29Locked41414
30Locked41513
31Locked41513

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33944K1840QAM 40961108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
33Locked438.24534689300

Kay4
On our wavelength

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000038.55120QAM 321
14310000038.35120QAM 322
23660000038.55120QAM 323
33010000038.55120QAM 324
42360000038.85120QAM 325

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0010
3ATDMA0000
4ATDMA0000

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
61133.22KQAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA2207400000000

Kay4
On our wavelength

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file
Allowed
1
Enabled
3.1
cmreg-vmdg660-bbt057-b.cm

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic Rate
38052
143750047 bps
42600bytes
0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type
38051
22000047 bps
42600bytes
0 bps
42600bytes
Best Effort

Kay4
On our wavelength

Network Log

Time Priority Description
14-02-2024 18:24:00noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 18:23:50noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 18:18:47noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 18:18:34noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 18:13:31noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 18:13:22noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 18:08:19noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 18:08:12noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 18:03:09noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 18:03:00noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:57:57noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:57:44noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:52:41noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:52:38noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:47:35noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:47:28noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:45:02warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:45:02warningDynamic Range Window violation
14-02-2024 17:45:02warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:45:02warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:45:02warningDynamic Range Window violation
14-02-2024 17:45:02warningDynamic Range Window violation
14-02-2024 17:42:26warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 17:42:25noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-02-2024 08:42:37warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-02-2024 21:17:30noticeREGISTRATION COMPLETE - Waiting for Operational status
13-02-2024 21:17:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-02-2024 21:17:24noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-02-2024 21:17:19noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-02-2024 21:17:15noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-02-2024 21:17:13warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-02-2024 21:17:11noticeHonoring MDD; IP provisioning mode = IPv4

Client62
Hero

The reported 16% packet loss may well be due to the choice of settings for : https://packetlosstest.com/ after all this test will record a packet as lost when it is delivered later that the chosen latency limit.

Looking at the 3.0 DOCSIS Downstream stats, Power levels are at the very high end of the spectrum, but so far errors do not appear to be a problem. If the power rises further ( dBmV > 10 )  that would be a concern.

Looking at the 3.0 DOCSIS Upstream stats, the QAM 32 on all channels indicates a local noise issue.

Kay4
On our wavelength

If it is a local noise issue, can I do anything or is it just waiting to see if it improves

Hi Kay4,

Thank you for reaching out to us in our community and welcome back, it has been quite a while, hope you have kept well, sorry to see you have been facing packet loss after an area fault, I was unable to locate you on our system with the details we have for you, so I can have a closer ;look to see if it is an area SNR issue, I have sent you an invite into a private chat, please look out for the white envelope to accept.

Regards

Paul.