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: 

Regular connection dropout Hub4

reidm99
Up to speed

on ‎24-08-2022 00:26

Currently on Volt Gig1 (with 52 Mbps upstream).

Since early on Monday morning (2022-08-21), I have been experiencing regular internet disconnects at appx. half-hourly intervals.
These last from a couple of seconds to appx 30 seconds.
I didn’t notice this until late Monday night when attempting to play online gaming.

I only have PC, printer and one V6 box connected via ethernet and another V6 box and mobile connected via wi-fi, so nothing too strenuous.

I have rebooted my PC, Hub4 (3x) and  performed a hard reset on the Hub4 (3x). 
Aside from that I  I have also checked the head-end, all coax connections etc.

The first time I performed a hard reset, it actually triggered a software update which I thought might solve the problem, but no.

When I check the online service status it doesn’t find a fault in my area, but further checking the broadband, it states:

“Looks like there's still an issue with your connection
We're looking into it. Check back here after * hours and if there's still an issue we'll help you book a technician.”   
* Currently at 3 hours.

The Hub4 diagnostic tool reports:
1        Your broadband connection is working.
2        Gateway IPv4 address is valid.
3        Your broadband connection is ready.
4        The temperature of your Hub 4 is normal.
5        There is no telephone service.

Network Log

Time Priority Description

Tue Aug 23 15:21:34 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 15:21:40 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 15:21:56 20226US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 17:13:12 20226CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 17:42:58 20226US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 18:13:49 20226CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 18:13:57 20226US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 18:47:40 20226CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 19:17:00 20226US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 20:38:53 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 20:38:58 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 20:39:08 20225DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 20:39:08 20226US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 20:48:32 20226CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 21:11:00 20226US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 22:16:12 20226CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 23 22:46:05 20226US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

 

 

 

0 Kudos
90 REPLIES 90

reidm99
Up to speed
In response to reidm99

on ‎15-04-2023 21:01

Had text message from VM about outage on BB, TV & Voice fault F010597427.
Latest fix estimate is 19th April @ 18:00.

We'll see.

Current BQM isn't too bad:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/501a243cb089ea47099aa98f000f038e99... 

0 Kudos

ccutler
Joining in
In response to reidm99

‎17-04-2023 18:53 - edited ‎17-04-2023 19:16

Hi,

I've have what appears to be a very similar scenario to the one you describe going on since the end of 2022 / early 2023.

Since the end of 2022 year I've had short disconnects (normally under 10-15 seconds) every 30 / 60 mins. I'm on a 1GB connection and a Hub 4 since last July. I've been with Virgin about 10 years and had a fantastic connection until this year. 

I ignored it for a while but it is really disruptive of online games and video calls so early March I installed software to track the connection.

The connection always drops at the same time e.g. yesterday and today it is dropping at 36 mins past the hour.

It doesn't always drop every hour - but if it is going to drop it will drop in those time windows.

Today (17th April) the connection dropped at 36 mins past the hour most hours:

01:36
02:36
04:36
05:36
10:36
11:36
12:36
13:36
14:36
15:36
17:36

Yesterday the time drifted a little throughout the day:

23:36
22:36
16:33
13:32
10:30
05:28
00:25

The above disconnects come from my internal monitoring software that are less sensitive that the BQM monitors - here is today from BQM and you can see the red disconnects every 30 mins:

17th April:

My Broadband Ping - virgin: march 22 on

another chart from 14th March:

My Broadband Ping - virgin: march 12 - march 22

I've had two engineer visits who have replaced the splitter and removed an attenuator. They also changed my port in the local cabinet. It's now been escalated to the networks team - but hasn't led anywhere yet. They have confirmed they are seeing 400 - 500 disconnections a week.

I had a brief window from 11-13 April where I had no disconnections - but after that 2 day break am back to regular disconnections.

Virgin are apparently going to try a Hub 5 to see if it makes any difference. After putting up with this for several months I'm going to give up on Virgin if the Hub 5 doesn't work.

 

0 Kudos

ccutler
Joining in
In response to ccutler

on ‎17-04-2023 19:11

Posting Hub4 configuration / log in case that helps someone:

Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream

 
Online
DOCSIS 3.1
Primary downstream channel
Locked
SC-QAM
DOCSIS 3.0 channels
31
5
DOCSIS 3.1 channels
1
1
0 Kudos

ccutler
Joining in
In response to ccutler

on ‎17-04-2023 19:12

Downstream

3.0 Downstream channels

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

41630000007.539QAM2564
11390000008.239QAM2561
2147000000839QAM2562
31550000007.939QAM2563
51710000007.338.6QAM2565
6179000000739QAM2566
71870000006.740.4QAM2567
81950000006.339QAM2568
92030000005.839QAM2569
102110000005.439QAM25610
112190000004.839QAM25611
122270000004.839QAM25612
13235000000539QAM25613
142430000004.839QAM25614
152510000004.239QAM25615
162590000004.438.6QAM25616
172670000004.838.6QAM25617
182750000005.339QAM25618
192830000005.239QAM25619
20291000000539QAM25620
212990000004.938.6QAM25621
223070000005.339QAM25622
233150000005.740.4QAM25623
24323000000540.4QAM25624
253310000004.640.4QAM25625
263390000004.440.4QAM25626
273470000004.339QAM25627
283550000004.240.4QAM25628
293630000003.939QAM25629
30371000000438.6QAM25630
31379000000339QAM25631



3.0 Downstream channels

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

4Locked38.98326100
1Locked38.98326100
2Locked38.98326100
3Locked38.98326100
5Locked38.60537700
6Locked38.98326100
7Locked40.36628700
8Locked38.98326100
9Locked38.98326100
10Locked38.98326100
11Locked38.98326100
12Locked38.98326100
13Locked38.98326100
14Locked38.98326100
15Locked38.98326100
16Locked38.60537700
17Locked38.60537700
18Locked38.98326100
19Locked38.98326100
20Locked38.98326100
21Locked38.60537700
22Locked38.98326100
23Locked40.36628700
24Locked40.36628700
25Locked40.36628700
26Locked40.36628700
27Locked38.98326100
28Locked40.36628700
29Locked38.98326100
30Locked38.60537700
31Locked38.98326100



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159964K1840QAM4096759


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked40-2.317492983590
0 Kudos

ccutler
Joining in
In response to ccutler

on ‎17-04-2023 19:12

Upstream

3.0 Upstream channels

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

13660000036.55120 KSym/secQAM643
22360000035.55120 KSym/secQAM645
33010000036.55120 KSym/secQAM644
443100000375120 KSym/secQAM642
54960000037.85120 KSym/secQAM641



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
5ATDMA0000



3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
610.030.52KQAM128


3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA20053.920
0 Kudos

ccutler
Joining in
In response to ccutler

on ‎17-04-2023 19:14

Network log

Network Log

Time Priority Description

Mon 17/04/2023
13:06:45		6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/04/2023
12:52:37		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/04/2023
12:00:31		6DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/04/2023
12:00:31		4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/04/2023
10:06:35		6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/04/2023
08:37:35		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/04/2023
08:36:23		6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/04/2023
07:11:12		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/04/2023
20:35:48		6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/04/2023
20:08:26		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/04/2023
14:32:56		6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/04/2023
13:55:02		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/04/2023
08:29:55		6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/04/2023
06:37:24		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/04/2023
03:28:10		6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/04/2023
03:27:44		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/04/2023
19:25:01		6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/04/2023
18:42:12		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/04/2023
10:48:30		6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/04/2023
10:45:35		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/04/2023
06:57:12		6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/04/2023
05:04:44		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 14/04/2023
18:16:26		6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 14/04/2023
18:16:26		5DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 14/04/2023
18:16:10		5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 13/04/2023
19:40:25		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 13/04/2023
14:46:01		6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 13/04/2023
14:41:50		6DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 13/04/2023
14:41:49		4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 13/04/2023
02:58:14		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 12/04/2023
20:17:17		6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 12/04/2023
14:51:25		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 12/04/2023
13:03:33		6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 11/04/2023
00:51:46		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/04/2023
12:39:05		6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/04/2023
12:39:05		5DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/04/2023
12:38:47		5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/04/2023
10:58:08		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/04/2023
10:37:28		6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/04/2023
10:20:13		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/04/2023
09:32:35		6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/04/2023
03:15:03		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos

Steven_L
Forum Team
Forum Team

on ‎19-04-2023 20:05

Thanks for coming back to us reidm99, how has your connection been running since you last posted on Monday? I have looked into your connection on our systems and cannot see anything that would be causing your issues. 

Kind Regards,

Steven_L

0 Kudos

reidm99
Up to speed
In response to Steven_L

on ‎20-04-2023 02:43

Hi Steven, connexion has been stable, although there was a Fault registered: Service update. Broadband, Voice and TV fault  F010597427 which was due to be fixed by 18:00 Tuesday 2023-04-19. 

I haven't seen any major issues regarding this- see BQM & network log - but the status line [0800 561 0061] is still reporting a 'complex issue' in my postcode @ 2023-04-20 02:38.
I therefore will continue to monitor as long as that is the case.

reidm99_0-1681954775810.png

Network Log

Time Priority Description
18-04-2023 13:34:46warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-04-2023 13:34:46noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-04-2023 12:28:36warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-04-2023 12:28:36noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-04-2023 04:29:41warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-04-2023 04:29:41noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-04-2023 03:27:27warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-04-2023 03:27:27noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 20:25:39errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 19:35:44noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 19:35:44warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 18:55:21noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 18:55:21warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 16:34:09noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 16:34:09warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 15:27:54warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 15:27:54noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 12:31:57warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 12:31:57noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 11:26:45warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 11:26:45noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 03:57:44warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 03:57:44noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 03:47:39noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 03:47:39warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-04-2023 19:53:54noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-04-2023 19:53:54warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-04-2023 18:53:19warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-04-2023 18:53:19noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-04-2023 18:02:53warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-04-2023 18:02:53noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-04-2023 16:57:52warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos

Zach_R
Forum Team
Forum Team
In response to reidm99

on ‎22-04-2023 09:41

Hi @reidm99,

Thank you for expanding on this and providing that fault reference number too. I've checked over it, and it appears that fault has now been resolved. Can you confirm if your issues are ongoing today?

Thanks,
 


Zach - Forum Team
New around here? To find out more about the Community Forums, take a look at our FAQs!


0 Kudos

reidm99
Up to speed
In response to Zach_R

on ‎22-04-2023 11:12

Hi Zach,
The status line is no longer reporting a fault in my area and I haven't seen any disconnects or packet loss for sometime.

I will consider this closed now, but will still keep an active BQM in case any issues crop up.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/501a243cb089ea47099aa98f000f038e99d64ed9


Thanks,

0 Kudos
Top