Northampton Re segmentation Saga 7 months on
Hi All,
Hoping that someone can help/provide some guidance on a issue we have here in Northampton. I live in a new build area Pineham , have been here for 5 years and a customer of Virgin Media with no issues whatsoever. Always got full speeds 24/7. And my BQM was perfect. Around early Jan, VM have started/completed a reseg and refreshed the cmts hardware at the headend. Since this , the internet has been absolutely awful with high latency all day long which makes anything other than general web browsing painful. There seems to be no sign of them fixing this as they just keep moving the fix date along and along, but this is affecting around ~700 homes on just my estate. Speaking with VM we are just getting the scripted response that we can now leave if we want to as we have complained so many times, but currently there is no other providers that service my area. I have been patient and appreciate the current situation with covid, but as we are now also starting to see issues with intermittent pixelation whilst watching tv, it is becoming increasingly more frustrating. Any help/advise or insights if anyone here works for virgin media and could shed some light on what the issue is and when it will actually be fixed would be greatly appreciated. Thanks, Adam https://www.cableforum.uk/images/local/2020/07/1.png Cable Modem Status Item Status Comments Acquired Downstream Channel (Hz) 723000000 Locked Ranged Upstream Channel (Hz) 39399976 Locked Provisioning State Online Downstream bonded channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 723000000 2.5 38 256 qam 40 2 539000000 3.9 38 256 qam 17 3 547000000 3.7 38 256 qam 18 4 555000000 3.7 38 256 qam 19 5 563000000 3.7 38 256 qam 20 6 571000000 3.5 38 256 qam 21 7 579000000 3.2 38 256 qam 22 8 587000000 3.5 38 256 qam 23 9 595000000 3.2 38 256 qam 24 10 603000000 3.4 38 256 qam 25 11 611000000 3 38 256 qam 26 12 619000000 3 38 256 qam 27 13 627000000 2.9 38 256 qam 28 14 635000000 2.5 38 256 qam 29 15 643000000 2.5 38 256 qam 30 16 651000000 2 38 256 qam 31 17 659000000 2.2 38 256 qam 32 18 667000000 2.2 38 256 qam 33 19 675000000 2.2 38 256 qam 34 20 683000000 2.5 38 256 qam 35 21 691000000 2.5 38 256 qam 36 22 699000000 2.7 38 256 qam 37 23 707000000 2.5 38 256 qam 38 24 715000000 2.5 38 256 qam 39 Downstream bonded channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 38.9 17 0 2 Locked 38.9 16 0 3 Locked 38.6 18 0 4 Locked 38.9 13 0 5 Locked 38.9 12 0 6 Locked 38.9 10 0 7 Locked 38.9 11 0 8 Locked 38.9 10 0 9 Locked 38.9 8 0 10 Locked 38.9 11 0 11 Locked 38.9 16 0 12 Locked 38.9 10 0 13 Locked 38.9 9 0 14 Locked 38.9 20 0 15 Locked 38.6 13 0 16 Locked 38.9 24 0 17 Locked 38.6 27 0 18 Locked 38.6 22 0 19 Locked 38.6 19 0 20 Locked 38.9 26 0 21 Locked 38.9 24 0 22 Locked 38.9 21 0 23 Locked 38.6 15 0 24 Locked 38.6 8 0 Upstream bonded channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 1 39399976 4.3 5120 64 qam 2 2 25800012 4.3 5120 64 qam 4 3 32599957 4.3 5120 64 qam 3 4 46200014 4.3 5120 64 qam 1 Upstream bonded channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 1 ATDMA 0 0 0 0 2 ATDMA 0 0 0 0 3 ATDMA 0 0 0 0 4 ATDMA 0 0 0 0 General Configuration Network access Allowed Maximum Number of CPEs 1 Baseline Privacy Enabled DOCSIS Mode Docsis30 Config file A,.iyewrkldJKDHSUBsg Primary Downstream Service Flow SFID 5466 Max Traffic Rate 575000000 Max Traffic Burst 42600 Min Traffic Rate 0 Primary Upstream Service Flow SFID 5465 Max Traffic Rate 38520000 Max Traffic Burst 42600 Min Traffic Rate 0 Max Concatenated Burst 16320 Scheduling Type BestEffort Network Log Time Priority Description 06/07/2020 21:59:19 critical No Ranging Response received - T3 time-out;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 17:12:55 notice LAN login Success;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 09:51:11 critical No Ranging Response received - T3 time-out;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 09:51:10 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 09:49:43 critical No Ranging Response received - T3 time-out;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 09:49:1 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 09:47:10 critical No Ranging Response received - T3 time-out;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 09:47:9 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 09:47:9 critical Ranging Request Retries exhausted;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 09:46:13 critical No Ranging Response received - T3 time-out;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 06:06:50 Error DHCP RENEW sent - No response for IPv4;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 06/07/2020 00:01:29 critical No Ranging Response received - T3 time-out;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 05/07/2020 14:21:51 Error DHCP RENEW sent - No response for IPv4;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 01/07/2020 04:09:56 critical No Ranging Response received - T3 time-out;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 30/06/2020 18:48:24 notice LAN login Success;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 30/06/2020 06:48:28 notice DHCP Renew - lease parameters tftp file-Vcb573b2ee9a9587e.cm modified;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 30/06/2020 06:48:28 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 29/06/2020 15:47:44 Error DHCP RENEW sent - No response for IPv4;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 29/06/2020 09:01:24 critical No Ranging Response received - T3 time-out;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; 29/06/2020 00:47:2 Error DHCP RENEW sent - No response for IPv4;CM-MAC=c0:05:c2:04:b5:c3;CMTS-MAC=a0:f8:49:6a:f2:43;CM-QOS=1.1;CM-VER=3.0; |
Re: Northampton Re segmentation Saga 7 months on
Those stats are fine. You could try putting a complaint into the CEOs office but tbh at this point all I can see you being offered is a hefty discount. The good news is that they are away of the issue and have a plan in place to remedy it, it is just a question of when and a waiting game unfortunately. I have heard many a story like this plan where these sorts of problems get dragged out over a year and a half with delay after delay after delay.
|
Re: Northampton Re segmentation Saga 7 months on
Currently being told November this year after we are already 8 months down the road. It is just very disappointing
|
Re: Northampton Re segmentation Saga 7 months on
Still not fixed , went off on Tuesday night and we are now on a different SFID ? And my public ip has changed again .
performance is even worse now with my bqm a sea of blue during weekday wfh. https://www.thinkbroadband.com/broad...4a17ed3feab278 |
Re: Northampton Re segmentation Saga 7 months on
That definitely sucks ass
|
Re: Northampton Re segmentation Saga 7 months on
Surely a reseg should fix issues not make them worse, although I can say VM have seen a huge uptake in traffic due to COVID 19 and lockdowns meaning a lot more people using their connection.
Reseg themselves take a lot of prep work and with the current situation VM won't have as many team ready to go hence the delays I suppose. Best you can do now is make a complaint and keep records of dates as you may need this to get some sort of compensation, as I fear that coming in to the Christmas holidays VM upgrade work will stop as to avoid any major issues. |
Re: Northampton Re segmentation Saga 7 months on
adz's region needs both upstream and downstream resegs. The upstream one was done last week. The downstream one is scheduled to happen in early December.
|
Re: Northampton Re segmentation Saga 7 months on
Quote:
|
Re: Northampton Re segmentation Saga 7 months on
|
Re: Northampton Re segmentation Saga 7 months on
Quote:
|
Re: Northampton Re segmentation Saga 7 months on
Pleased to say that since the works my bqm and overall performance of my connection is a lot better !
Phase 2 of my development are still having issues but looks like VM have split the estate and still have some work to do in the new year. https://www.thinkbroadband.com/broad...4a17ed3feab278 |
Re: Northampton Re segmentation Saga 7 months on
It's as good as mine and I get 1Gig/50 meg nearly all the time.
So, it seems you're sorted - for now. |
All times are GMT +1. The time now is 18:36. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.