Menu
Reply
Highlighted
  • 4
  • 0
  • 0
Joining in
89 Views
Message 1 of 6
Flag for a moderator

High packet loss

Hi,

I managed to get through on the phone this morning after being on hold for an hour, the operator then said I was being transferred to the tech team as I have done all the required tasks.

I have setup a BQM this morning and can see that the packet loss is very high.

This is a replacement super hub 3 which has been fine for the past few weeks. But today has really bad packet loss and interrupting remote connections.

My Broadband Ping - Virgin

0 Kudos
Reply
Highlighted
  • 11.49K
  • 891
  • 1.46K
Alessandro Volta
82 Views
Message 2 of 6
Flag for a moderator

Re: High packet loss

Can you please

Type 192.168.0.1 (192.168.100.1 in Modem mode) into your browser URL bar and press enter. 

Hub 2 & 3 When the page appears DO NOT LOG IN but click ‘Check Router Status’.

Hub 4 When the page appears LOG IN then click ‘Check Router Status’.

Copy and paste the contents of the Downstream, Upstream and Network Log tabs onto here, if you get a yellow / straw box warning click the Post button again. Use one post for each tab if you wish. Please do not use screen grabs.

A Guru will be along soon to decipher the info.

***********************************************************************************************************************************

Mike Robinson
Retired Aircraft Engineer & Computer Based Training and Learning Designer for many of the world's Military Arms.


My Broadband Ping - 26_Aug_2020

0 Kudos
Reply
Highlighted
  • 4
  • 0
  • 0
Joining in
78 Views
Message 3 of 6
Flag for a moderator

Re: High packet loss

 

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
331000000
Locked
Ranged Upstream Channel (Hz)
46199983
Locked
Provisioning State
Online

 

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

133100000010.138256 qam25
22030000001037256 qam9
32110000009.937256 qam10
42190000009.537256 qam11
52270000009.337256 qam12
62350000008.637256 qam13
72430000008.337256 qam14
82510000007.637256 qam15
92590000007.337256 qam16
10267000000737256 qam17
112750000008.137256 qam18
12283000000937256 qam19
132910000009.538256 qam20
142990000009.837256 qam21
153070000009.838256 qam22
163150000009.938256 qam23
173230000009.838256 qam24
18371000000938256 qam26
193790000008.537256 qam27
203870000007.538256 qam28
213950000007.138256 qam29
224030000006.837256 qam30
23411000000737256 qam31
244190000006.538256 qam32


Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.9400
2Locked37.3430
3Locked37.3470
4Locked37.6500
5Locked37.6410
6Locked37.3350
7Locked37.3620
8Locked37.6330
9Locked37.3330
10Locked37.3490
11Locked37.6410
12Locked37.6460
13Locked38.6240
14Locked37.6390
15Locked38.6360
16Locked38.6310
17Locked38.6320
18Locked38.9270
19Locked37.6410
20Locked38.6400
21Locked38.9460
22Locked37.6490
23Locked37.6450
24Locked38.6500

 

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

14619998335512064 qam3
23940000035512064 qam4
35369998335512064 qam2
46029999636.5512064 qam1


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

0 Kudos
Reply
Highlighted
  • 4
  • 0
  • 0
Joining in
77 Views
Message 4 of 6
Flag for a moderator

Re: High packet loss

Time Priority Description

02/11/2020 09:49:38noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 23:49:53criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 12:03:3noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 12:03:3ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 04:04:18ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 20:32:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 20:05:36ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:50criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:50Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:49criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:41Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:36Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:36criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:36Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:36criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:36Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:36:14criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:32:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 14:32:15criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Highlighted
  • 11.49K
  • 891
  • 1.46K
Alessandro Volta
64 Views
Message 5 of 6
Flag for a moderator
Helpful Answer

Re: High packet loss

One over your Downstream Power Levels is too high and one is maxed out and several are very close to max.

This will need an engineer to put right.

You can either phone in (08:00 is the best time) or wait on here for a few days (6 to 7 days average) until one of the VM Forum Staff comes along.

If you wait on here Do Not bump the thread it will put it further down the VM 'to do list'.

***********************************************************************************************************************************

Mike Robinson
Retired Aircraft Engineer & Computer Based Training and Learning Designer for many of the world's Military Arms.


My Broadband Ping - 26_Aug_2020

Highlighted
  • 4
  • 0
  • 0
Joining in
60 Views
Message 6 of 6
Flag for a moderator

Re: High packet loss

Thanks @MikeRobbo.

After trying to call the helpline, it just says can we text you a link for resolving the issue, but forces it and says if you do not have the link, the call will end.

Will try tomorrow at 8am.

Thank you for you help.

0 Kudos
Reply