on 08-02-2021 20:45
Hi
Can anyone tell me why t3 pop up on they upstream bit but dont show up on the error logs? im getting more t3 on the upstream bit but they dont show on the error logs when another shows up!
on 07-03-2021 15:17
Hey
I am Like internet cops! i know when the line is not good!
on 09-03-2021 13:41
Thank you for coming back to us @RockerSBM
I have taken another look over your account, there seems to be some noise on the downstream.
There is a team looking into this issue.
Kind Regards,
Zak_M
on 09-03-2021 18:17
Hi Zak
wouldnt it be upstream too with the qam dropping to 32?
is this why i always get that error message RCS Partial Service then noise hits on the downstream? the one ive been going on about for 2 years now?
hit that message last night with noise on the downstream.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 195000000 | 1.9 | 38 | 256 qam | 8 |
2 | 139000000 | 2.5 | 38 | 256 qam | 1 |
3 | 147000000 | 2.5 | 38 | 256 qam | 2 |
4 | 155000000 | 2.7 | 38 | 256 qam | 3 |
5 | 163000000 | 2.7 | 38 | 256 qam | 4 |
6 | 171000000 | 2.5 | 38 | 256 qam | 5 |
7 | 179000000 | 2.2 | 38 | 256 qam | 6 |
8 | 187000000 | 1.7 | 38 | 256 qam | 7 |
9 | 203000000 | 2.2 | 38 | 256 qam | 9 |
10 | 211000000 | 2.2 | 38 | 256 qam | 10 |
11 | 219000000 | 1.9 | 38 | 256 qam | 11 |
12 | 227000000 | 2 | 38 | 256 qam | 12 |
13 | 235000000 | 1.9 | 38 | 256 qam | 13 |
14 | 243000000 | 1.5 | 38 | 256 qam | 14 |
15 | 251000000 | 1 | 38 | 256 qam | 15 |
16 | 259000000 | 1 | 38 | 256 qam | 16 |
17 | 267000000 | 1 | 38 | 256 qam | 17 |
18 | 275000000 | 1 | 38 | 256 qam | 18 |
19 | 283000000 | 1 | 38 | 256 qam | 19 |
20 | 291000000 | 1.2 | 38 | 256 qam | 20 |
21 | 299000000 | 1.5 | 38 | 256 qam | 21 |
22 | 307000000 | 1.5 | 38 | 256 qam | 22 |
23 | 315000000 | 1.5 | 38 | 256 qam | 23 |
24 | 323000000 | 1.4 | 38 | 256 qam | 24 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 94 | 138 |
2 | Locked | 38.6 | 83 | 76 |
3 | Locked | 38.6 | 127 | 55 |
4 | Locked | 38.6 | 128 | 53 |
5 | Locked | 38.6 | 171 | 71 |
6 | Locked | 38.6 | 130 | 50 |
7 | Locked | 38.9 | 107 | 58 |
8 | Locked | 38.9 | 117 | 56 |
9 | Locked | 38.9 | 91 | 150 |
10 | Locked | 38.6 | 84 | 54 |
11 | Locked | 38.9 | 108 | 66 |
12 | Locked | 38.6 | 151 | 52 |
13 | Locked | 38.9 | 92 | 61 |
14 | Locked | 38.6 | 51 | 41 |
15 | Locked | 38.6 | 40 | 50 |
16 | Locked | 38.6 | 53 | 42 |
17 | Locked | 38.6 | 54 | 53 |
18 | Locked | 38.6 | 43 | 144 |
19 | Locked | 38.9 | 42 | 49 |
20 | Locked | 38.6 | 52 | 65 |
21 | Locked | 38.6 | 61 | 66 |
22 | Locked | 38.9 | 55 | 48 |
23 | Locked | 38.6 | 40 | 62 |
24 | Locked | 38.6 | 60 | 73 |
Time Priority Description
09/03/2021 01:00:3 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/03/2021 21:49:59 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/03/2021 06:21:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 09-03-2021 20:56
Hey zak
get on the blower to them and tell them qam dropping on upstream too still!
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 45 | 5120 | 64 qam | 1 |
2 | 25800000 | 41.5 | 5120 | 32 qam | 4 |
3 | 32600000 | 43 | 5120 | 64 qam | 3 |
4 | 39400000 | 45 | 5120 | 64 qam | 2 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 15 | 0 |
3 | ATDMA | 0 | 0 | 2 | 0 |
4 | ATDMA | 0 | 0 | 3 | 0 |
on 12-03-2021 18:06
Hi @RockerSBM,
Very sorry to see you're having some ongoing issues,
I have checked your account again and still showing no signs of upstream issues.
There are no faults or outage but have noticed you haven't rebooted in over 2 weeks, might be worth rebooting the hub to see if this helps?
Is this on all devices you are having this issue and do you do these tests via wired and wirelessly?
Thanks,
Sasha
Sasha - Forum Team
New around here? To find out more about the Community check out our Getting Started guide
on 12-03-2021 19:02
Hi sasha
has the downstream problem been fixed?
on 16-03-2021 15:51
Hi @RockerSBM
So sorry to see you have been suffering with these issues but thanks for getting back to us.
I have checked your account and I cannot currently see any area outages that may be affecting you.
If you are still facing these issues can I ask you to confirm you have recently tried to reboot? Can I also ask you to confirm whether the above test were done on a wired or WiFi connection and if all your devices are affected?
on 17-03-2021 13:31
Hi
Well you're other forum team member said they was problem with downstream and yesterday and today there red all along the tbb graph! So clearly it's not fixed.
Cheers
Shaun
on 17-03-2021 14:04
Hi @RockerSBM
I'm so sorry to hear you are still facing these issues and it has not been resolved for you.
Sorry to repeat but we do just need to check, have you tried the reboot? Are these test from a wired or WiFi connection and are you noticing issues across all devices.
on 17-03-2021 18:04
Hi
Yes i rebooted it at weekend the red has come back at top of the graph and the upstream still droping qam to 32 different channel now.
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 45 | 5120 | 64 qam | 1 |
2 | 25800000 | 41 | 5120 | 64 qam | 4 |
3 | 32600000 | 43 | 5120 | 64 qam | 3 |
4 | 39400000 | 44 | 5120 | 32 qam | 2 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |