I haven't been able to find anyone else posting about using the 4 priority data channels yet. We've upgraded to PMP450 firmware version 16.0.0.1 across our network on both our SMs and APs because we want to use multiple priority queues to prioritize data, voice, video and management traffic. I've enabled the 4 queues on the SM I'm working on but when checking the data channels on the AP, I only see low and high priority channels. We want all 4 channels so we have data through low priority, video through medium priority, voice through high priority and management through ultra high priority.
I will note that we provision our radios through a Radius server which reference selectable profiles for voice and data and sends the appropriate attributes to the SM with voice and management on the high priority channel and data on the low priority channel but I've been through the 16.0.1 guide and I don't see any attributes for the medium and ultra high priority channels yet. Could this be interfereing with the settings I'm configuring on the SM manually? I'm wondering what I might be doing wrong or what I can do differently to get this working.
What is the "Configuration Source" set to, on the AP? It can be found in "Configuration -> General" page, under "Bandwidth Configuration Source" section. If the "Configuration Source" is set to "Authentication Server" or "Authentication Server + SM", SM is getting it's data channel configuration from the Radius Server.
"Cambium-Canopy-DATACHANCOUNT" is the attribute, to set the number of Data Channels. Update the profile SM is using, to add the above attribute and set it to 4, and try again. Please ensure the Radius server has the latest dictionary.canopy file.
If you still have issues, please send me "engineering.cgi" from the AP to balaji.grandhi@cambiumnetworks.com.
In addtion to what Balaji said above, please ensure that your Radius profile is no longer using the "Cambium-Canopy-HPENABLE" VSA after 15.2. It may override the "Cambium-Canopy-DATACHANCOUNT" VSA if it's applied afterward. Similarly, the reverse can be true.
To ensure you can enable more than 2 Data Channels, set "Cambium-Canopy-DATACHANCOUNT" only, or after "Cambium-Canopy-HPENABLE".
Yes, it is set to Authentication server so this is most likely the issue. I will try setting the Cambium-Canopy-DATACHANCOUNT attribute next week and confirm this solves the issue.
Just curious - Is using the "Cambium-Canopy-HPENABLE" setting in RADIUUS still fine if we aren't using the new queueing system, even past 16.0?
Yes. You can use "Cambium-Canopy-HPENABLE" to configure 2 Data Channels, even on 16.0 or later releases.
Yes, but you have to make sure you're not also setting Cambium-Canopy-DATACHANCOUNT, or it will override that value used in Camium-Canopy-HPENABLE. Basically, they're mutually-exclusive, and whatever you write last is what will stick, so that's the main thing to keep in mind.
Thank you for the added clarity - we aren't expecting to utilize "Cambium-Canopy-DATACHANCOUNT" at this time, so that puts my mind at ease.
No problem. Just as another added piece of info, if you decide you might want to move to 3 or 4 Data Channels some time down the line, you could start phasing in using Cambium-Canopy-DATACHANCOUNT = 2 right now, and it would be equivalent to setting Cambium-Canopy-HPENABLE = true. Then you'd just have to change the 2 to a 3 or 4 later.