Menu
Reply
Highlighted
  • 24
  • 0
  • 3
On our wavelength
259 Views
Message 1 of 5
Flag for a moderator

NN1 packet loss not fixed after 2 fix dates

https://www.thinkbroadband.com/broadband/monitoring/quality/share/b95a1d95b44cf2457cecf411d8401a9b1f...

 

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

1699000000-1.238256 qam37
2523000000038256 qam15
35310000000.438256 qam16
4539000000-0.538256 qam17
55470000000.540256 qam18
6555000000-0.238256 qam19
75630000000.238256 qam20
8571000000-0.438256 qam21
9579000000-1.438256 qam22
10587000000038256 qam23
11595000000-138256 qam24
12603000000-0.238256 qam25
13611000000-0.538256 qam26
14619000000-138256 qam27
15627000000-0.238256 qam28
16635000000-1.738256 qam29
17643000000-0.438256 qam30
18651000000-0.738256 qam31
19659000000-0.738256 qam32
20667000000-0.538256 qam33
21675000000-1.938256 qam34
22683000000-0.538256 qam35
23691000000-1.238256 qam36
24707000000-138256 qam38



Downstream bonded channels

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

1Locked38.660
2Locked38.940
3Locked38.600
4Locked38.900
5Locked40.300
6Locked38.900
7Locked38.960
8Locked38.650
9Locked38.920
10Locked38.900
11Locked38.900
12Locked38.660
13Locked38.940
14Locked38.900
15Locked38.900
16Locked38.9150
17Locked38.900
18Locked38.600
19Locked38.900
20Locked38.650
21Locked38.600
22Locked38.940
23Locked38.900
24Locked38.600

 

 

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

1462000044.45512064 qam1
2257999544.25512064 qam4
3325999524.3512064 qam3
4393999984.45512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

 

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
fg87dsfd;kfoA,.iyewrkldJKDHSUBs

 

when is there going to be a fix this has been happening for 5 months now and its ridiculous 

0 Kudos
Reply
Highlighted
  • 24
  • 0
  • 3
On our wavelength
258 Views
Message 2 of 5
Flag for a moderator

Re: NN1 packet loss not fixed after 2 fix dates

Time Priority Description

22/07/2020 10:42:9noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/07/2020 05:04:10noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/07/2020 05:04:10ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/07/2020 03:11:30ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/07/2020 02:31:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/07/2020 02:31:59Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/07/2020 01:18:55ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/07/2020 23:37:36Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/07/2020 21:33:45ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/07/2020 19:08:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/07/2020 14:03:23ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/07/2020 04:14:11Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2020 23:02:41ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2020 21:57:23Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2020 21:22:43criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2020 19:20:0Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2020 19:20:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2020 18:49:41Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2020 18:46:2criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2020 01:27:14Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
fg87dsfd;kfoA,.iyewrkldJKDHSUBs



Primary Downstream Service Flow

SFID10928
Max Traffic Rate402500089
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID10927
Max Traffic Rate38500089
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort
0 Kudos
Reply
Highlighted
  • 2.54K
  • 149
  • 324
Forum Team
Forum Team
201 Views
Message 3 of 5
Flag for a moderator

Re: NN1 packet loss not fixed after 2 fix dates

Hi Poyzii, thanks for your post - sorry for the delayed reply here.

 

I'm also sorry for any connection issues you've experienced. I wasn't able to run checks on the services using just your forum details, so I'll send a PM to confirm a few details with you so we can try to help further.

 

Tom 

 

 

0 Kudos
Reply
Highlighted
  • 3.5K
  • 567
  • 1.38K
Very Insightful Person
Very Insightful Person
195 Views
Message 4 of 5
Flag for a moderator

Re: NN1 packet loss not fixed after 2 fix dates

when is there going to be a fix this has been happening for 5 months now

I doubt anytime soon.  The BQM looks like classic over-utilisation, and your hub stats indicate no power or noise problems with the connection, although the Network log does show evidence of problems  If this has been going on since February-ish, then VM will be VERY unlikely to fix anytime soon, because (when the world returns to some normality) there's a chance that the over-utilisation issues could melt away. 

There's also a regrettable track record of VM not actually doing anything to improve local capacity  - they set a "fix" date, but the reality is that for some/many areas there are no quick, easy or low cost options, so what happens is that as the "fix" date approaches, they review the situation, and create a new review date a month or two down the line.  Partly this gives the pretence to customers that there's something being done, partly it is in the hope that sufficient customers leave and traffic levels come down to somewhere around the available capacity.  

You could complain, that won't make VM more or less likely to actually do anything.  You could then escalate to the arbitration scheme CISAS.  They could award you some modest compensation, and release you from any time-limited contract you may be in, but they still can't force VM to invest if the company don't wish to.

So your options are regrettably simple - to keep paying, sit it out and hope that one day the local network can cope with the traffic, or to find yourself a different ISP.

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

Highlighted
  • 2.54K
  • 149
  • 324
Forum Team
Forum Team
155 Views
Message 5 of 5
Flag for a moderator

Re: NN1 packet loss not fixed after 2 fix dates

Thanks for getting back to me @Poyzii.

 

I've taken a look this morning and am sorry to confirm a known fault was recently raised for the area and work is currently estimated to be completed later on today. 

 

If you continue to have problems by tomorrow please pop us another message so we can check again and take further action as necessary.

 

Tom 

0 Kudos
Reply