on 30-11-2023 19:50
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?
Password | Show |
1 | 138750000 | 9.8 | 38 | 256 qam | 1 |
2 | 146750000 | 9.5 | 38 | 256 qam | 2 |
3 | 154750000 | 9.5 | 38 | 256 qam | 3 |
4 | 162750000 | 9.5 | 38 | 256 qam | 4 |
5 | 170750000 | 9.6 | 38 | 256 qam | 5 |
6 | 178750000 | 9.5 | 38 | 256 qam | 6 |
7 | 186750000 | 9.5 | 38 | 256 qam | 7 |
8 | 194750000 | 9.6 | 38 | 256 qam | 8 |
9 | 202750000 | 9.6 | 38 | 256 qam | 9 |
10 | 210750000 | 9.5 | 38 | 256 qam | 10 |
11 | 218750000 | 9.6 | 38 | 256 qam | 11 |
12 | 226750000 | 9.6 | 38 | 256 qam | 12 |
13 | 234750000 | 9.8 | 38 | 256 qam | 13 |
14 | 242750000 | 9.6 | 38 | 256 qam | 14 |
15 | 250750000 | 9.8 | 38 | 256 qam | 15 |
16 | 258750000 | 9.8 | 38 | 256 qam | 16 |
17 | 266750000 | 10 | 38 | 256 qam | 17 |
18 | 274750000 | 9.8 | 38 | 256 qam | 18 |
19 | 282750000 | 9.8 | 38 | 256 qam | 19 |
20 | 290750000 | 9.8 | 38 | 256 qam | 20 |
21 | 298750000 | 10 | 38 | 256 qam | 21 |
22 | 306750000 | 10 | 38 | 256 qam | 22 |
23 | 314750000 | 10 | 38 | 256 qam | 23 |
24 | 322750000 | 10.1 | 38 | 256 qam | 24 |
1 | Locked | 38.9 | 6 | 0 |
2 | Locked | 38.6 | 6 | 0 |
3 | Locked | 38.6 | 6 | 0 |
4 | Locked | 38.9 | 5 | 0 |
5 | Locked | 38.6 | 7 | 0 |
6 | Locked | 38.6 | 5 | 0 |
7 | Locked | 38.6 | 18 | 0 |
8 | Locked | 38.9 | 15 | 0 |
9 | Locked | 38.9 | 5 | 0 |
10 | Locked | 38.9 | 6 | 0 |
11 | Locked | 38.6 | 4 | 0 |
12 | Locked | 38.9 | 7 | 0 |
13 | Locked | 38.9 | 5 | 0 |
14 | Locked | 38.9 | 5 | 0 |
15 | Locked | 38.9 | 4 | 0 |
16 | Locked | 38.6 | 5 | 0 |
17 | Locked | 38.6 | 6 | 0 |
18 | Locked | 38.6 | 4 | 0 |
19 | Locked | 38.9 | 5 | 0 |
20 | Locked | 38.9 | 6 | 0 |
21 | Locked | 38.6 | 6 | 0 |
22 | Locked | 38.9 | 5 | 0 |
23 | Locked | 38.9 | 5 | 0 |
24 | Locked | 38.9 | 5 | 0 |
on 06-12-2023 13:05
hi
on 06-12-2023 13:07
Hi as u can see internet is still not right went down twice last night
on 06-12-2023 13:12
Sorry I pressed on solution by mistake can forum.team.change it as it hasn't been fixed.
on 08-12-2023 13:46
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?
on 22-03-2024 21:29
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?
on 22-03-2024 21:31
Password | Show |
1 | 23600000 | 34.3 | 5120 | 16 qam | 5 |
2 | 36600000 | 34.5 | 5120 | 64 qam | 3 |
3 | 43100000 | 34.5 | 5120 | 64 qam | 2 |
4 | 30100005 | 34.3 | 5120 | 64 qam | 4 |
5 | 49600000 | 35 | 5120 | 64 qam | 1 |
1 | ATDMA | 0 | 0 | 20 | 0 |
2 | ATDMA | 0 | 0 | 2 | 0 |
3 | ATDMA | 0 | 0 | 2 | 0 |
4 | ATDMA | 0 | 0 | 3 | 0 |
5 | ATDMA | 0 | 0 | 4 | 0 |
on 22-03-2024 21:32
Password | Show |
1 | 202750000 | 9.4 | 38 | 256 qam | 9 |
2 | 138750000 | 9.5 | 38 | 256 qam | 1 |
3 | 146750000 | 9.3 | 38 | 256 qam | 2 |
4 | 154750000 | 9.1 | 38 | 256 qam | 3 |
5 | 162750000 | 9.3 | 38 | 256 qam | 4 |
6 | 170750000 | 9.4 | 38 | 256 qam | 5 |
7 | 178750000 | 9.1 | 38 | 256 qam | 6 |
8 | 186750000 | 9.4 | 38 | 256 qam | 7 |
9 | 194750000 | 9.4 | 38 | 256 qam | 8 |
10 | 210750000 | 9.3 | 38 | 256 qam | 10 |
11 | 218750000 | 9.3 | 38 | 256 qam | 11 |
12 | 226750000 | 9.4 | 38 | 256 qam | 12 |
13 | 234750000 | 9.3 | 38 | 256 qam | 13 |
14 | 242750000 | 9 | 38 | 256 qam | 14 |
15 | 250750000 | 8.8 | 38 | 256 qam | 15 |
16 | 258750000 | 8.4 | 38 | 256 qam | 16 |
17 | 266750000 | 9 | 38 | 256 qam | 17 |
18 | 274750000 | 9.5 | 38 | 256 qam | 18 |
19 | 282750000 | 9.6 | 38 | 256 qam | 19 |
20 | 290750000 | 9.8 | 38 | 256 qam | 20 |
21 | 298750000 | 10.1 | 38 | 256 qam | 21 |
22 | 306750000 | 10 | 38 | 256 qam | 22 |
23 | 314750000 | 10 | 38 | 256 qam | 23 |
24 | 322750000 | 10.1 | 38 | 256 qam | 24 |
1 | Locked | 38.6 | 56 | 0 |
2 | Locked | 38.9 | 62 | 0 |
3 | Locked | 38.6 | 55 | 0 |
4 | Locked | 38.6 | 60 | 0 |
5 | Locked | 38.9 | 58 | 0 |
6 | Locked | 38.9 | 53 | 0 |
7 | Locked | 38.6 | 51 | 0 |
8 | Locked | 38.9 | 56 | 0 |
9 | Locked | 38.6 | 43 | 0 |
10 | Locked | 38.6 | 43 | 0 |
11 | Locked | 38.6 | 58 | 0 |
12 | Locked | 38.9 | 48 | 0 |
13 | Locked | 38.9 | 64 | 0 |
14 | Locked | 38.6 | 59 | 0 |
15 | Locked | 38.6 | 70 | 0 |
16 | Locked | 38.9 | 89 | 0 |
17 | Locked | 38.6 | 62 | 0 |
18 | Locked | 38.9 | 66 | 0 |
19 | Locked | 38.9 | 58 | 0 |
20 | Locked | 38.9 | 86 | 0 |
21 | Locked | 38.9 | 46 | 0 |
22 | Locked | 38.6 | 37 | 0 |
23 | Locked | 38.9 | 45 | 0 |
24 | Locked | 38.9 | 59 | 0 |
on 22-03-2024 21:34
on 22-03-2024 21:39
Password | Show |
21/03/2024 18:35:37 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/03/2024 11:51:28 | Error | DHCP 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:6 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/03/2024 23:51:27 | Error | DHCP 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:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/03/2024 11:51:27 | Error | DHCP 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:7 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/03/2024 12:44:44 | Error | DHCP 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:1 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/03/2024 21:58:10 | Error | DHCP 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:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/03/2024 18:20:42 | Error | DHCP 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:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/02/2024 12:35:39 | Error | DHCP 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:4 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2024 21:44:35 | Error | DHCP 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:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2024 01:58:52 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2024 01:58:50 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2024 01:58:48 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 22-03-2024 21:39
Loads of t3 timeouts too...