Menu
Reply
Highlighted
  • 174
  • 0
  • 32
Up to speed
1,182 Views
Message 11 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

Can't even use the forum's own image posting...and on hold for 43 minutes.....

0 Kudos
Reply
Highlighted
  • 12.44K
  • 859
  • 3.72K
Very Insightful Person
Very Insightful Person
1,176 Views
Message 12 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

Images will not appear until someone has okayed em. Ive done that with yours.

Metrics we need to see are specifically- upstream, downstream and network logs from your HUB

Up to date BQM trace.

It wouldn't hurt to have a continuous ping to the server you are using when the issue occurs.

As for having danced that dance-  I thought we had too, but the only thread I can find of yours other than this is from 2013?

 

 

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
Highlighted
  • 174
  • 0
  • 32
Up to speed
1,134 Views
Message 13 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

So we finally have the upload speed sorted again. That only took 2 hours to Phone Support. At least we are back where we started though. So here we go:

 
 
Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
14830000006.138256 qam32
22030000005.438256 qam9
32110000005.338256 qam10
42190000005.338256 qam11
52270000005.138256 qam12
6235000000538256 qam13
72430000004.938256 qam14
8251000000538256 qam15
92590000004.938256 qam16
10267000000538256 qam17
11275000000538256 qam18
12283000000540256 qam19
13291000000538256 qam20
142990000005.538256 qam21
15307000000640256 qam22
16315000000640256 qam23
17323000000638256 qam24
184270000005.840256 qam25
194350000005.640256 qam26
204430000005.940256 qam27
214510000006.340256 qam28
224590000006.140256 qam29
234670000006.440256 qam30
244750000006.340256 qam31


Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.9110
2Locked38.9320
3Locked38.990
4Locked38.980
5Locked38.9150
6Locked38.9160
7Locked38.960
8Locked38.9250
9Locked38.6120
10Locked38.9290
11Locked38.9100
12Locked40.3100
13Locked38.9130
14Locked38.9290
15Locked40.3300
16Locked40.380
17Locked38.980
18Locked40.3210
19Locked40.3210
20Locked40.3150
21Locked40.3170
22Locked40.3180
23Locked40.3220
24Locked40.3160
0 Kudos
Reply
Highlighted
  • 174
  • 0
  • 32
Up to speed
1,133 Views
Message 14 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

 
 
Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1394000004.625512064 qam2
2462000004.575512064 qam1
3325999664.675512064 qam3
4257999034.729512064 qam4


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
Highlighted
  • 174
  • 0
  • 32
Up to speed
1,131 Views
Message 15 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

 
 
Network LogTime Priority Description
10/11/2019 12:34:16ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/11/2019 14:13:56criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/11/2019 14:51:29ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/11/2019 17:39:53ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:36criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:6Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:12criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:12Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:12criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:17Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:11Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:27criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:27criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:33Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:59:45criticalReceived 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.0;
18/11/2019 13:00:5criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 13:00:5Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 13:04:8criticalReceived 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.0;
19/11/2019 17:48:18criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Highlighted
  • 174
  • 0
  • 32
Up to speed
1,129 Views
Message 16 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

20.11.2019
20.11.2019.png

0 Kudos
Reply
Highlighted
  • 174
  • 0
  • 32
Up to speed
1,128 Views
Message 17 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

21.11.2019

21.11.2019.png

0 Kudos
Reply
Highlighted
  • 174
  • 0
  • 32
Up to speed
1,125 Views
Message 18 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

22.11.2019

22.11.2019.png

0 Kudos
Reply
Highlighted
  • 12.44K
  • 859
  • 3.72K
Very Insightful Person
Very Insightful Person
1,088 Views
Message 19 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

Though the BQM is improved you are still getting packet loss as of today.

Can you post the latest network logs?

 

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
Highlighted
  • 174
  • 0
  • 32
Up to speed
1,080 Views
Message 20 of 237
Flag for a moderator

Re: A very SERIOUS issue with VM - spread the word

I already have, just above the BQM charts.

 
 
 
Network LogTime Priority Description
10/11/2019 12:34:16ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/11/2019 14:13:56criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/11/2019 14:51:29ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/11/2019 17:39:53ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:36criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:6Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:12criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:12Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:12criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:52:17Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:11Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:27criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:27criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:57:33Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 12:59:45criticalReceived 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.0;
18/11/2019 13:00:5criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 13:00:5Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2019 13:04:8criticalReceived 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.0;
19/11/2019 17:48:18criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply