on 11-11-2022 20:37
Just got a hub5, thought I would try router mode although I'm sure I'll come to my senses at some point.
I was just looking at network status and I cant find specific data about the 3.1 channels.
I just came from the hub4 where I could see the modulation and power levels of the downstream and upstream channels.
On the hub5 I cant.
Am i going nuts or what?
Here is the data......
Cable Modem StatusItem Status Comments
Acquired Downstream Channel(Hz) | 435000000 | Locked |
Ranged Upstream Channel(Hz) | 49600000 | Ranged |
Provisioning State | Online | Operational |
Downstream bonded channels
1 | 435000000 | 9.5 | 41 | QAM 256 | 4 |
2 | 411000000 | 9.4 | 40 | QAM 256 | 1 |
3 | 419000000 | 9.5 | 40 | QAM 256 | 2 |
4 | 427000000 | 9.7 | 41 | QAM 256 | 3 |
5 | 443000000 | 9.7 | 41 | QAM 256 | 5 |
6 | 451000000 | 9.6 | 41 | QAM 256 | 6 |
7 | 459000000 | 9.5 | 41 | QAM 256 | 7 |
8 | 467000000 | 9.3 | 41 | QAM 256 | 8 |
9 | 475000000 | 9.4 | 41 | QAM 256 | 9 |
10 | 483000000 | 9.5 | 41 | QAM 256 | 10 |
11 | 491000000 | 9.5 | 41 | QAM 256 | 11 |
12 | 499000000 | 9.5 | 41 | QAM 256 | 12 |
13 | 507000000 | 9.1 | 41 | QAM 256 | 13 |
14 | 515000000 | 9 | 41 | QAM 256 | 14 |
15 | 523000000 | 8.9 | 41 | QAM 256 | 15 |
16 | 531000000 | 9.1 | 41 | QAM 256 | 16 |
17 | 539000000 | 9.1 | 41 | QAM 256 | 17 |
18 | 547000000 | 9.1 | 41 | QAM 256 | 18 |
19 | 555000000 | 9.1 | 41 | QAM 256 | 19 |
20 | 563000000 | 8.9 | 41 | QAM 256 | 20 |
21 | 571000000 | 8.9 | 40 | QAM 256 | 21 |
22 | 579000000 | 8.9 | 41 | QAM 256 | 22 |
23 | 587000000 | 9 | 41 | QAM 256 | 23 |
24 | 595000000 | 9.1 | 41 | QAM 256 | 24 |
25 | 603000000 | 8.8 | 40 | QAM 256 | 25 |
26 | 611000000 | 8.2 | 40 | QAM 256 | 26 |
27 | 619000000 | 8.2 | 40 | QAM 256 | 27 |
28 | 627000000 | 8.2 | 40 | QAM 256 | 28 |
29 | 635000000 | 8.2 | 40 | QAM 256 | 29 |
30 | 643000000 | 8 | 40 | QAM 256 | 30 |
31 | 651000000 | 7.9 | 39 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 41 | 35 | 0 |
2 | Locked | 40 | 20 | 0 |
3 | Locked | 40 | 22 | 0 |
4 | Locked | 41 | 30 | 0 |
5 | Locked | 41 | 26 | 0 |
6 | Locked | 41 | 33 | 0 |
7 | Locked | 41 | 59 | 0 |
8 | Locked | 41 | 75 | 0 |
9 | Locked | 41 | 92 | 0 |
10 | Locked | 41 | 79 | 0 |
11 | Locked | 41 | 102 | 0 |
12 | Locked | 41 | 115 | 0 |
13 | Locked | 41 | 174 | 0 |
14 | Locked | 41 | 225 | 0 |
15 | Locked | 41 | 305 | 0 |
16 | Locked | 41 | 285 | 0 |
17 | Locked | 41 | 369 | 0 |
18 | Locked | 41 | 409 | 0 |
19 | Locked | 41 | 522 | 0 |
20 | Locked | 41 | 560 | 0 |
21 | Locked | 40 | 716 | 0 |
22 | Locked | 41 | 619 | 0 |
23 | Locked | 41 | 666 | 0 |
24 | Locked | 41 | 817 | 0 |
25 | Locked | 40 | 974 | 0 |
26 | Locked | 40 | 1370 | 0 |
27 | Locked | 40 | 1526 | 0 |
28 | Locked | 40 | 1687 | 0 |
29 | Locked | 40 | 1580 | 0 |
30 | Locked | 40 | 1517 | 0 |
31 | Locked | 39 | 1816 | 0 |
on 11-11-2022 20:38
Upstream bonded channels
0 | 49600000 | 41 | 5120 | QAM 64 | 1 |
1 | 43100000 | 40.5 | 5120 | QAM 64 | 2 |
2 | 36600000 | 40.5 | 5120 | QAM 64 | 3 |
3 | 30100000 | 40.3 | 5120 | QAM 64 | 4 |
4 | 23600000 | 40 | 5120 | QAM 64 | 5 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
General Configuration
Allowed |
1 |
Enabled |
3.1 |
254k;fg87dsfd;kfoA,.iyewr |
Primary Downstream Service Flow
8008 |
575000000 bps |
42600bytes |
0 bps |
Primary Upstream Service Flow
8007 |
38520000 bps |
42600bytes |
0 bps |
16320bytes |
Best Effort |
Network Log
11-11-2022 19:30:41 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:41 | warning | DBC-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; |
11-11-2022 19:30:37 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
11-11-2022 19:30:31 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:31 | warning | Dynamic Range Window violation |
11-11-2022 19:30:31 | warning | Dynamic Range Window violation |
11-11-2022 19:30:31 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:31 | warning | Dynamic Range Window violation |
11-11-2022 19:30:31 | warning | Dynamic Range Window violation |
11-11-2022 19:30:31 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:31 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:31 | warning | Dynamic Range Window violation |
11-11-2022 19:30:31 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:31 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:31 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:31 | warning | Dynamic Range Window violation |
11-11-2022 19:30:25 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:23 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:30:21 | notice | Honoring MDD; IP provisioning mode = IPv4 |
11-11-2022 19:30:11 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-11-2022 19:29:59 | critical | Cable Modem Reboot due to master console reset |
on 11-11-2022 22:01
on 11-11-2022 23:29
Yes it’s certainly a problem that is being ‘glossed over’. Personal view it’s just a problem in the firmware that’s not displaying the 3.1 channels, they are there and working. The Hub5 firmware seemed to use the Hub3 firmware as a base, this was obvious by some posts when it was first issued that showed the first page saying it was a "Hub3”! Of course the Hub3 firmware had no 3.1 channels. Looks like someone in the rush to get it out used the wrong base code.
on 12-11-2022 06:32
risc19's config file shows that he's on 500 Mbps and in that case the hub probably doesn't need the D3.1 channels. Seems from my Hub 5/250 connection that the 3.1 channels aren't enabled either, again because they aren't needed?
on 12-11-2022 07:24
Nah - RockerSBM is on 1 Gig with a hub 5 and the D3.1 channels are not shown.
on 12-11-2022 10:16
@Sephiroth wrote:Nah - RockerSBM is on 1 Gig with a hub 5 and the D3.1 channels are not shown.
Aren't you in the wrong thread, RockerSBM isn't involved?
And whilst I did think risc19 was on a Gig 1 contract, the Max Traffic Rate is clearly shown in post 2 in this thread at 575 Mbps, and the upstream is 38.5 Mbps, which I believe are the current values for an M500 package, certainly not Gig 1.
on 12-11-2022 10:44
Just to clear up any confusion.
I was in 1gig hub4 then down graded to 500.
I had 3.1 channels up and down on both packages.
Then I got a hub5 that’s when they stopped showing in network status.
My two penny’s worth…
I suspect they are there and active but are not showing due to the firmware.
on 12-11-2022 15:57
@Andrew-G wrote:
@Sephiroth wrote:Nah - RockerSBM is on 1 Gig with a hub 5 and the D3.1 channels are not shown.
Aren't you in the wrong thread, RockerSBM isn't involved?
And whilst I did think risc19 was on a Gig 1 contract, the Max Traffic Rate is clearly shown in post 2 in this thread at 575 Mbps, and the upstream is 38.5 Mbps, which I believe are the current values for an M500 package, certainly not Gig 1.
No - I was making the point that there is a Hub 5 on 1Gig, using D3.1, also not showing the power levels. There is a clue, though in Risc's stats. They show 31 D3.0 channels, none of which are marked as Primary. He's provisioned with 32 channels. So the 32nd channel is D3.1.
on 12-11-2022 17:37
"They show 31 D3.0 channels, none of which are marked as Primary. He's provisioned with 32 channels. So the 32nd channel is D3.1."
Exactly the same as my Hub5.