Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Service outages for the last month

svcWhatSvc
Tuning in

on ‎19-10-2022 23:37

Posting the details here because I'm getting fed up, and despite thinking numerous times that someone would escalate the issue, I'm still getting numerous dropouts every day.

Package is gig1. No issues with the speed. I get/exceed the 1130/52 (the cabinet is ~10 metres from the house). Everything is as advertised... while connected.

It's a Volt bundle too, so I signed up for internet, phone, TV, mobile (O2) as part of the deal. Mobile signal is 1 to 2 bars of Edge/3G at home (same for any carrier). If you lean out of the window, you might see a bar of 4G. Calls are terrible, so Wi-Fi calling is the only way.

I've tried all sorts of different network settings/options (including modem-only mode, separate router/APs). I've reverted to the default VM router/Wi-Fi at the moment to stop the 'we can't support that's. I've also checked during a disconnect to make sure the hub doesn't make any weird noises or overheat.

Common with every dropout: all wired and wireless devices lose internet simultaneously. During dropout, I can access the router web page and other devices on the local network via ethernet and Wi-Fi (local pings don't miss a beat).

  • Issue reported 20th September 2022 via webchat. Engineer booked.
  • Engineer attended 22nd September, said there was a known issue with Hub4s in the area getting bad software updates, causing them to boot-loop. Went back to the office, and came back, installed a Hub5.
  • In the meantime had notice about a fault in the area
  • 3rd October, called phone support, explained I was still having dropouts. Spoke to 4 different people. Total call time was just over 2 hours. Asked each rep to call back if the line dropped because that day it was about a drop every 30-90 minutes.
    • First person: Checked the details, checked the router, could see 10 disconnects for the day so far (this was late morning). Went through the basic troubleshooting, explained that the hub had been replaced. Call disconnected. Waited for a bit, but no call back, so I rang again.
    • Second person: Explained where we'd got to, and asked them to check the notes from the previous call. I asked for an engineer, but they couldn't book it unless I wanted to pay £25 for it. Alternatively, I was offered Wi-Fi boosting pods. I declined both options and asked to escalate the issue because I didn't believe I should pay to fix a service fault. They couldn't escalate the call so I asked how we can proceed short of cancelling the service.
    • Third person: waited on hold again, went through security again, very friendly rep agreed that I shouldn't have to pay for an engineer, asked for another chance to rectify the situation, but they were the cancellations dept. so couldn't assist.
    • Fourth person: transferred, waited on hold again, seemed to be making progress in getting an engineer arranged. call dropped, waited but no call back. We're were just about at the end of the call (short of confirming an engineer) so I had to assume a visit had been booked.
  • Web chat 5th (possibly 6th) October. Very helpful person, applied some credit to the account for the inconvenience because the outages so far hadn't been detected by whatever applies the auto-ofcom compensation. Upon further chatting, it seems the service has to be hard down, not just completely unusable, for this to be applied. Engineer was also booked for Sat 8th.
  • Engineer attended 8th October and tested the external cable. Saw noise/interference on it and said it needed replacing. He said that even though the old ntlworld cable should work, the fact it was above ground in the green conduit meant it was more susceptible to damage/foxes over time. Also said that even though it pre-dated the contract, it should've been replaced/re-installed, buried or at least pinned to something rather than running loose along the driveway.
  • WhatsApp support chat 11th October, asking for an update/installation date for the new cable. There didn't seem to be details of a new cable installation being booked, but I was told the Wi-Fi super pods had been ordered and were on the way.
  • Friday 14th. VM contractor arrived to run a coil of cable from the cabinet to the end of the driveway
  • Tuesday 18th October. VM contractor team arrived to install the new cable. These guys were great actually, really helpful, fast work and tidy, and bearing in mind they had to channel through concrete, they were finished really quickly. They said they couldn't run any other tests because they're not allowed to enter properties to test further. They were the first people however, to point out I can see disconnect logs in the VM hub (which given they're not even VM employees, made me chuckle).
  • We've made it to today. 19th October. A month since reporting the fault. After all of this, I'm still getting outages. If I had to put a positive spin on it, I'd say that it seems like there were only 2 today, (although the first one took ages to come back and means a rearranged work zoom call - it's getting pretty embarrassing). Knowing where to look now on the hub, I can see errors.

Based on other threads, and requested information, Downstream, Upstream and Network Log info below...

0 Kudos
26 REPLIES 26

svcWhatSvc
Tuning in

on ‎19-10-2022 23:38

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13060000000.838QAM 25622
21380000001.440QAM 2561
31460000001.439QAM 2562
41540000001.439QAM 2563
51620000001.339QAM 2564
61700000001.339QAM 2565
71780000001.339QAM 2566
81860000001.439QAM 2567
91940000001.539QAM 2568
102020000001.439QAM 2569
112100000001.639QAM 25610
122180000001.739QAM 25611
132260000001.739QAM 25612
142340000001.839QAM 25613
152420000001.839QAM 25614
162500000001.839QAM 25615
172580000001.839QAM 25616
182660000001.839QAM 25617
192740000001.739QAM 25618
202820000001.638QAM 25619
212900000001.438QAM 25620
222980000001.138QAM 25621
233140000000.838QAM 25623
243220000000.838QAM 25624
253300000000.737QAM 25625
263380000000.838QAM 25626
273460000000.838QAM 25627
283540000000.838QAM 25628
293620000000.837QAM 25629
303700000000.737QAM 25630
313780000000.637QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked3820
2Locked4000
3Locked3900
4Locked3900
5Locked3900
6Locked3900
7Locked3900
8Locked3900
9Locked3900
10Locked3900
11Locked3900
12Locked3900
13Locked3900
14Locked3900
15Locked3900
16Locked3900
17Locked3900
18Locked3900
19Locked3900
20Locked3800
21Locked3810
22Locked3800
23Locked3810
24Locked3800
25Locked3710
26Locked3810
27Locked3810
28Locked3830
29Locked3720
30Locked3710
31Locked3750

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000048.55120QAM 647
14310000048.55120QAM 648
23660000048.55120QAM 649
33010000048.55120QAM 6410
42360000048.85120QAM 6411

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0100
1ATDMA01210
2ATDMA01590
3ATDMA01560
4ATDMA01610

 

Network Log

Time Priority Description
19-10-2022 23:00:34noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 21:04:11noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 20:55:51warningRNG-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;
19-10-2022 20:54:08warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 20:54:08noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 20:52:57criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 19:49:08noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 17:41:31noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 16:37:43noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 14:30:06noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 14:20:31noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 14:15:28noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 11:19:48noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 11:14:45noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 11:05:41noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 11:00:38noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:27:30noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:19:20critical16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:19:20criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:18:32criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:18:31warningRNG-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;
19-10-2022 10:18:31warningDynamic Range Window violation
19-10-2022 10:18:08criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:17:44warningRNG-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;
19-10-2022 10:12:31criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:12:14warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:12:14noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:11:58criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:11:57criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:11:57criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:11:57critical16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-10-2022 10:11:56warningDynamic Range Window violation
0 Kudos

svcWhatSvc
Tuning in
In response to svcWhatSvc

on ‎20-10-2022 13:16

I setup a think broadband monitor last night too, already a few red spikes

tb.png

 Any advice on what to try next would be greatly appreciated.

0 Kudos

jbrennand
Very Insightful Person
Very Insightful Person
In response to svcWhatSvc

on ‎20-10-2022 15:01

You need someone more knowledgeable than me to comment on the logs - which do look odd.

Lets look at the BQM after 24h

However, all power levels appear fine - spot on - there are a couple of issues though. Too many T timeouts. Can you start from a clean sheet as below. Also you have no DOCSIS 3.1 Down or Up channels - is it really not there?. This is usual to have for 1GB connections.

So either that is causing the issues and so its a fault that needs checking - or - the flaky firmware is just not reporting it in the settings
___________________________________________________________

Switch the Hub off and unplug it from the mains supply for five minutes. Whilst it's off, do a quick check that all of your coax and ethernet cable connections are in nice and "finger" tight - at the Hub and wall box and also at any connectors etc. Ensure there are no “unterminated cable loose ends. Disconnect all the connections and reconnect to be sure. Also check that the internal wiring is ok with no kinking or chaffing, check that all looks good with the outside cabling and wall box (no “staples, etc.,) piercing the cables. Then switch the Hub back on and leave ~5 minutes
When all done, check back in the settings and ensure that the T errors have all reset to 0. Then check every hour or so to see if they start reappearing - they shouldn't. If they do (particularly any postRS in downstream and T3 ones in Up ) you have a problem (noise) that only a Tech visit will sort.

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

svcWhatSvc
Tuning in
In response to jbrennand

on ‎20-10-2022 17:30

Hi John. Thanks for the reply (and suggestions).

I'm not sure what I should be seeing on the Downstream/Upstream pages in terms of DOCSIS 3.1 channels. On the Configuration tab, it does say DOCSIS mode is 3.1.

After the powerdown, the counters have reset. All of the connections are tight (ethernet, hub to splitter, tv boxes to splitter, splitter to external). The cable looks fine internally and externally.

I'll report back tomorrow.
0 Kudos

svcWhatSvc
Tuning in
In response to svcWhatSvc

on ‎24-10-2022 12:35

I'm still seeing errors that coincide with full service drops:

22-10-2022 09:26:33noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-10-2022 09:26:24criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-10-2022 09:26:24critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-10-2022 09:25:16criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

Is there anything else I can try, or does this need a (fourth) visit to try to resolve?

0 Kudos

svcWhatSvc
Tuning in
In response to svcWhatSvc

on ‎25-10-2022 13:27

25-10-2022 13:18:31noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-10-2022 13:18:21criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-10-2022 13:18:21critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-10-2022 13:17:13criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Same issues.

Any advice on how to get VM staff to look at this?

 

0 Kudos

svcWhatSvc
Tuning in
In response to jbrennand

on ‎27-10-2022 00:44

Hi John - given that you're the only one to have replied: "You need someone more knowledgeable than me to comment on the logs - which do look odd." - any way I can go about requesting assistance? I've started messaging staff mods, but nothing yet. I'm more than happy to do more troubleshooting, I just don't know if there is anything else I can try.

0 Kudos

svcWhatSvc
Tuning in
In response to svcWhatSvc

on ‎27-10-2022 11:57

Apologies to the couple of staff I annoyed with a DM 😬

Screenshot 2022-10-27 at 11-48-47 Good folk to know - Virgin Media Community.png

 

Screenshot 2022-10-27 at 11-49-17 Private Messages - Virgin Media Community.png

Not trying to be a pain, I just have no idea how to further troubleshoot the ongoing issues. Even my boss is now asking when I'm going to change broadband because of how often I drop off of work calls. I really just want to get this working, because the product is really good, but I just can't trust it to work when I need it.

0 Kudos

svcWhatSvc
Tuning in
In response to svcWhatSvc

on ‎29-10-2022 13:16

Logs from a 5 minute outage just now:

29-10-2022 13:08:15noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:07:57noticeREGISTRATION COMPLETE - Waiting for Operational status
29-10-2022 13:07:53noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:07:47noticeDS 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;
29-10-2022 13:07:27warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:07:25noticeHonoring MDD; IP provisioning mode = IPv4
29-10-2022 13:07:11criticalReceived 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.1;
29-10-2022 13:03:27criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:03:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:03:09critical16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:03:09criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:03:09criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:03:09critical16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:03:09criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:02:45criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 13:02:27warningRNG-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;
29-10-2022 13:02:01criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 12:53:45noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 12:40:26errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 11:49:51criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 11:49:51critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-10-2022 11:48:43criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

Thursday outages:

My Broadband Ping - VM downtime

Yesterday:

My Broadband Ping - VM downtime

Today so far:

My Broadband Ping - VM downtime

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13060000001.138QAM 25622
21380000001.740QAM 2561
31460000001.740QAM 2562
41540000001.740QAM 2563
51620000001.740QAM 2564
61700000001.640QAM 2565
71780000001.740QAM 2566
81860000001.739QAM 2567
91940000001.839QAM 2568
102020000001.839QAM 2569
11210000000239QAM 25610
12218000000239QAM 25611
132260000002.139QAM 25612
142340000002.139QAM 25613
152420000002.239QAM 25614
162500000002.139QAM 25615
172580000002.139QAM 25616
182660000002.139QAM 25617
19274000000239QAM 25618
202820000001.939QAM 25619
212900000001.738QAM 25620
222980000001.338QAM 25621
23314000000138QAM 25623
24322000000138QAM 25624
253300000000.938QAM 25625
263380000001.138QAM 25626
273460000001.138QAM 25627
283540000001.138QAM 25628
293620000001.138QAM 25629
30370000000138QAM 25630
313780000000.837QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked3820
2Locked4000
3Locked4000
4Locked4010
5Locked4000
6Locked4000
7Locked4000
8Locked3900
9Locked3900
10Locked3900
11Locked3900
12Locked3900
13Locked3900
14Locked3900
15Locked3900
16Locked3900
17Locked3900
18Locked3900
19Locked3920
20Locked3910
21Locked3800
22Locked3820
23Locked3820
24Locked3860
25Locked3840
26Locked3840
27Locked3850
28Locked3850
29Locked3820
30Locked3870
31Locked37130

 

0 Kudos
Top