on 11-10-2021 10:38
Hi,
So I have recently upgraded to the Gig1 Service, and I only just realised that I'm not getting any DOCSIS 3.1 channels.
It doesn't have anything to do with upstream or downstream as I have recently had this sorted.
Here is the status page stats for the downstream/upstreams channels.
Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream
Cable Modem Status | Online | DOCSIS 3.1 |
Primary downstream channel | Locked | SC-QAM |
DOCSIS 3.0 channels | 32 | 4 |
DOCSIS 3.1 channels | 0 | 0 |
Thanks in advance.
on 11-10-2021 15:07
Can you please run a speed test and post the results along with a full set of stats from the hub.
on 11-10-2021 20:34
Hi,
I get around 600-700mbps, and here are the stats for the hub.
3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
9 | 203000000 | 5.099998 | 40.366287 | QAM256 | 9 |
2 | 147000000 | 6.900002 | 40.366287 | QAM256 | 2 |
3 | 155000000 | 6.699997 | 40.366287 | QAM256 | 3 |
10 | 211000000 | 5.099998 | 40.946209 | QAM256 | 10 |
11 | 219000000 | 5.000000 | 40.366287 | QAM256 | 11 |
12 | 227000000 | 5.000000 | 40.366287 | QAM256 | 12 |
13 | 235000000 | 5.400002 | 40.366287 | QAM256 | 13 |
14 | 243000000 | 5.599998 | 40.946209 | QAM256 | 14 |
15 | 251000000 | 5.500000 | 40.366287 | QAM256 | 15 |
16 | 259000000 | 5.800003 | 40.366287 | QAM256 | 16 |
17 | 267000000 | 6.000000 | 40.946209 | QAM256 | 17 |
18 | 275000000 | 6.099998 | 40.366287 | QAM256 | 18 |
19 | 283000000 | 5.699997 | 40.366287 | QAM256 | 19 |
20 | 291000000 | 5.599998 | 40.366287 | QAM256 | 20 |
21 | 299000000 | 5.800003 | 40.366287 | QAM256 | 21 |
22 | 307000000 | 5.900002 | 40.366287 | QAM256 | 22 |
23 | 315000000 | 5.599998 | 40.366287 | QAM256 | 23 |
24 | 323000000 | 5.400002 | 40.946209 | QAM256 | 24 |
25 | 331000000 | 4.900002 | 40.366287 | QAM256 | 25 |
26 | 339000000 | 5.099998 | 40.366287 | QAM256 | 26 |
27 | 347000000 | 5.099998 | 40.946209 | QAM256 | 27 |
28 | 355000000 | 4.900002 | 40.366287 | QAM256 | 28 |
29 | 363000000 | 4.900002 | 40.366287 | QAM256 | 29 |
30 | 371000000 | 4.900002 | 40.366287 | QAM256 | 30 |
31 | 379000000 | 4.800003 | 40.946209 | QAM256 | 31 |
32 | 387000000 | 4.900002 | 40.366287 | QAM256 | 32 |
33 | 395000000 | 5.000000 | 40.366287 | QAM256 | 33 |
34 | 403000000 | 5.099998 | 40.366287 | QAM256 | 34 |
35 | 411000000 | 5.000000 | 40.366287 | QAM256 | 35 |
36 | 419000000 | 4.800003 | 40.366287 | QAM256 | 36 |
37 | 427000000 | 4.699997 | 40.946209 | QAM256 | 37 |
38 | 435000000 | 4.800003 | 40.366287 | QAM256 | 38 |
3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 32600000 | 47.520599 | 5120 KSym/sec | 64QAM | 5 |
2 | 46200000 | 47.270599 | 5120 KSym/sec | 64QAM | 3 |
3 | 53700000 | 47.520599 | 5120 KSym/sec | 64QAM | 2 |
4 | 39400000 | 47.770599 | 5120 KSym/sec | 64QAM | 4 |
General Configuration
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | cmreg-vmdg640-bbt076-b.cm |
Primary Downstream Service Flow
SFID | 109350 |
Max Traffic Rate | 1230000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Primary Upstream Service Flow
SFID | 109349 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | bestEffort |
Thanks again.
on 11-10-2021 23:01
All those look fine and you are on 1G plan ok. There are two tables missing and they may be important. One is the downstream Pre & Post errors count and the other is the upstream t1/t2/r3/T4 counts.
on 11-10-2021 23:44
Hi,
I didn't include them as I have it in modem mode. Also I knew my levels were fine, I was just wondering why I don't have any DOCSIS 3.1 channels. Am I suppose to?
Thanks
on 12-10-2021 01:13
on 12-10-2021 12:47
Okay. Thanks
on 14-10-2021 12:54
Hi NikkiD69,
Thank you for reaching out to us here on the Community.
I am very sorry to hear you are experiencing some issues the service.
I have taken a look from our side and can see there have been some prolonged issues identified. With this being the case, I am going to pop you over a private message to grab a few more detail and we can go from there.
Speak soon,
on 24-11-2021 12:50
Hi NikkiD69,
Thanks for your message to Nat, she won't be back on shift for a while so I'll be looking into this on her behalf 🙂
I'm sorry to hear that you weren't able to get this resolved during your visit. I'll pop over an email to the Area Field Manager and ask for them to take a look into this for you. Once I do have any updates, I will let you know.
If you need anything else in the meantime please just let us know.
Beth
on 24-11-2021 13:25