cancel
Showing results for 
Search instead for 
Did you mean: 

Virgin upgrade works has messed up power levels

madmanx
On our wavelength

Hi had some work on my local network done today as it says it was doing upgrade work to improve the services, 

But after being down for half the day when the hub came back online I saw the power levels are way out if sync now. The downstream before was between 0 and 3dbmv and the upstream dbmv was about 38 dmbv, now the downstream is +10 dbmv and the upstream is now around 34dbmv, do I need an engineer to fix it? I have a 6db forward path attenuater fitted at back of hub which i could change to a 10db forward path attenuator to bring down the downstream power levels but its the upstream I'm concerned about as its only 34dbmv?

Have I a problem now?

 

Welcome back!
Sign in to view or modify your Hub 3.0 settings.
PasswordShow
 


 
 
 
Router status

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
11387500009.838256 qam1
21467500009.538256 qam2
31547500009.538256 qam3
41627500009.538256 qam4
51707500009.638256 qam5
61787500009.538256 qam6
71867500009.538256 qam7
81947500009.638256 qam8
92027500009.638256 qam9
102107500009.538256 qam10
112187500009.638256 qam11
122267500009.638256 qam12
132347500009.838256 qam13
142427500009.638256 qam14
152507500009.838256 qam15
162587500009.838256 qam16
172667500001038256 qam17
182747500009.838256 qam18
192827500009.838256 qam19
202907500009.838256 qam20
212987500001038256 qam21
223067500001038256 qam22
233147500001038256 qam23
2432275000010.138256 qam24


Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.960
2Locked38.660
3Locked38.660
4Locked38.950
5Locked38.670
6Locked38.650
7Locked38.6180
8Locked38.9150
9Locked38.950
10Locked38.960
11Locked38.640
12Locked38.970
13Locked38.950
14Locked38.950
15Locked38.940
16Locked38.650
17Locked38.660
18Locked38.640
19Locked38.950
20Locked38.960
21Locked38.660
22Locked38.950
23Locked38.950
24Locked38.950
73 REPLIES 73

madmanx
On our wavelength

Screenshot_20231206-130223.png

 hi 

Screenshot_20231206-130223.png

madmanx
On our wavelength

Hi as u can see internet is still not right went down twice last night

madmanx
On our wavelength

Sorry I pressed on solution by mistake can forum.team.change it as it hasn't been fixed.

Hey madmanx, thank you for reaching out and I am so sorry to hear about this.

I have just taken a look at our side and everything is look great on our side, your levels are showing great.

How has it been over the last few days, still the same? Cheers 

Matt - Forum Team


New around here?

Hi upstream qam keeps changing, can go from qam64 to qam16 then up to qam32 then back up to 64qam then, can keep changing qam like every few minutes but generally only seems to affect one upstream channel the lowest frequency one. When it drops to 16qam I get packet loss on my thinkbroadband quality monitor, is this due to noise on upstream? And would I be right in thinking its a network problem, rather then being a problem that's only affecting me? Any help be nice, also my downstream power levels are going over 10db but forum staff saying that my power levels are great?

madmanx
On our wavelength
Welcome back!
Sign in to view or modify your Hub 3.0 settings.
PasswordShow
 


 
 
 
Router status

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
12360000034.3512016 qam5
23660000034.5512064 qam3
34310000034.5512064 qam2
43010000534.3512064 qam4
54960000035512064 qam1


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA00200
2ATDMA0020
3ATDMA0020
4ATDMA0030
5ATDMA0040

madmanx
On our wavelength
Welcome back!
Sign in to view or modify your Hub 3.0 settings.
PasswordShow
 


 
 
 
Router status

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
12027500009.438256 qam9
21387500009.538256 qam1
31467500009.338256 qam2
41547500009.138256 qam3
51627500009.338256 qam4
61707500009.438256 qam5
71787500009.138256 qam6
81867500009.438256 qam7
91947500009.438256 qam8
102107500009.338256 qam10
112187500009.338256 qam11
122267500009.438256 qam12
132347500009.338256 qam13
14242750000938256 qam14
152507500008.838256 qam15
162587500008.438256 qam16
17266750000938256 qam17
182747500009.538256 qam18
192827500009.638256 qam19
202907500009.838256 qam20
2129875000010.138256 qam21
223067500001038256 qam22
233147500001038256 qam23
2432275000010.138256 qam24


Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.6560
2Locked38.9620
3Locked38.6550
4Locked38.6600
5Locked38.9580
6Locked38.9530
7Locked38.6510
8Locked38.9560
9Locked38.6430
10Locked38.6430
11Locked38.6580
12Locked38.9480
13Locked38.9640
14Locked38.6590
15Locked38.6700
16Locked38.9890
17Locked38.6620
18Locked38.9660
19Locked38.9580
20Locked38.9860
21Locked38.9460
22Locked38.6370
23Locked38.9450
24Locked38.9590

madmanx
On our wavelength

madmanx_0-1711143279326.png

 

madmanx
On our wavelength
Welcome back!
Sign in to view or modify your Hub 3.0 settings.
PasswordShow
 


 
 
 
Router status

Network Log

Time Priority Description
21/03/2024 18:35:37criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/03/2024 11:51:28ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/03/2024 17:18:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2024 23:51:27ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/03/2024 13:12:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/03/2024 11:51:27ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/03/2024 20:38:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/03/2024 12:44:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/03/2024 21:47:1criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/03/2024 21:58:10ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/03/2024 00:00:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/03/2024 18:20:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/02/2024 13:15:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/02/2024 12:35:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2024 23:29:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2024 21:44:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2024 08:09:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2024 01:58:52Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2024 01:58:50Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2024 01:58:48criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

madmanx
On our wavelength

Loads of t3 timeouts too...