Original Message:
Sent: Jun 12, 2024 05:45 AM
From: jkmendess
Subject: MCR + Controller just assign 2 same channels to all APs on radio 6 ghz
Hello Chulcher,
I have opened a case more than 1 week ago, but till now nothing relevant.
Changing the maximum width to 80Mhz as you recommended, allowed the controller to assign 2 more channels to access points. This is great and the first step forward on this case; Now i am getting 5E,53E, 21E, 37E. So am i supposed to understand that the behaviour we are facing is normal depending on the minimum and maximum width ?
Will the controller still stay on PSC Channel according to the 6ghz radio ? In that case what about the interferences between access point which transmits on the same channels ? if we have 200 access points and we want to broadcast ssid with on 6ghz radio, what should we do to avoid interferences ?
Many thank for your help.
Original Message:
Sent: Jun 07, 2024 10:21 AM
From: chulcher
Subject: MCR + Controller just assign 2 same channels to all APs on radio 6 ghz
Change to 80 MHz channel widths, run the AirMatch solver and see if that results in any changes. If not, open a case with TAC to troubleshoot.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Jun 07, 2024 10:16 AM
From: jkmendess
Subject: MCR + Controller just assign 2 same channels to all APs on radio 6 ghz
In the regulatory domain
1,5,9,13,17,21,25,29,33,37,41,45,49,53,57,61,65,69,73,77,81,85,89,93
first of all the controller just pick 5 and 53. Once i removed it i changed to 21 and 37, still PSC. But always 2 channels.
Thanks for your reply
Original Message:
Sent: Jun 07, 2024 09:26 AM
From: chulcher
Subject: MCR + Controller just assign 2 same channels to all APs on radio 6 ghz
What regulatory domain? What channels do you have enabled?
For reasons that are historical and no longer apply in the real world but still impact the software, the AP will not normally operate on any channel that either isn't a PSC or that includes a PSC. Please make sure to enable ALL of the available 6 GHz channels for your regulatory domain. We are working on changes that will allow 20 MHz and 40 MHz operation on the non-PSC but that doesn't exist yet.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Jun 07, 2024 09:07 AM
From: jkmendess
Subject: MCR + Controller just assign 2 same channels to all APs on radio 6 ghz
Hello Chulcher,
Thank for your reply. Yes Airmatch is ok, and run, as i specified everything is ok on 5 Ghz for example.
And about 20Mhz, i dit it because in that case i avoid channel chaining, so i minimise interference, and after all i don t need high throughput. all my customers just do TSE,
Original Message:
Sent: Jun 06, 2024 10:01 AM
From: chulcher
Subject: MCR + Controller just assign 2 same channels to all APs on radio 6 ghz
Has AirMatch run a solution for those APs? Is there a reason you're restricting the 6 GHz channel to 20 MHz?
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Jun 05, 2024 12:25 PM
From: jkmendess
Subject: MCR + Controller just assign 2 same channels to all APs on radio 6 ghz
Hello everybody,
we have 9240 controllers link a mobility conductor, all in version 8.10.0.12 LSR. We have 19 APs in a group and we activate the 6 ghz on a SSID with security wpa3-personal.
I don t understand why out of all the channels available in the regulatory domain, all the APs are still on the same 2 channels. If i remove the 2 channels chosen from the regulatory domain, the APs just all take another two channels. On 5 ghz everything is ok with channel assignment. Airmatch is activated; it seems it does not act on 6 ghz.
i have 19 APs, for example i will have 10 on channel 5 and 9 on channel 53, if i remove 5 and 53 from the RD, the controller now assigns channel 21 to maybe 7 APs and channel 37 to the other 12 APs, but it always pick 2 channels in the set and assign them to all the APs; randomly or not, i don t know. You will see on the screen below, i force everything on 20 Mhz to be sure to not have couple channel.
Did someone already saw this issue ?