Multiple SSIDs on 6GHz

[roo54]

I have a network built of CW9164 APs (MR 31.1.6). I would like to run a Corporate and a Guest SSID on both 5 and 6GHz. I thought I'd configured it to do so, but when I survey with Ekahau/Sidekick2, I can see only the Guest SSID on 6GHz. 5GHz is carrying them and other SSIDs. What am I doing wrong

[aleabrahao]

Ensure WPA3 is enabled for the Corporate SSID

6 GHz requires WPA3 (or OWE for open SSIDs). WPA2 is not supported on 6 GHz.

[roo54]

I should have said in the first place, both Guest and Corporate are running WPA3. and for what its worth, I have 4 SSIDs:

Guest runs on 2.4/5/6 and is WPA3, .11r disabled, .11w required/reject

Corporate runs on 5/6 and is WPA3, .11r disabled, .11w required/reject

IoT runs on 2.4 and 5, WPA2, .11r adaptive, .11w enabled allow

Legacy Corporate runs on 5, and is wpa2 .11r adaptive, .11w enabled/allow

[aleabrahao]

Meraki limits the number of SSIDs that can be broadcast on 6 GHz (usually 4). If you have more than 4 SSIDs enabled on the network, some will be automatically excluded from 6 GHz.

[roo54]

I edited my earlier response to document the SSIDs, and yes, I have held it down to 4 SSIDs, only two of which are on 6GHz

[aleabrahao]

To confirm which SSIDs are actually broadcasting on 6 GHz:

Go to Wireless > Monitor > Access Points

Click on an AP (CW9164)

Click the “RF” tab

Scroll to the 6 GHz band section

Look under “SSID(s)”, it will list exactly which SSIDs are broadcasting on that band

If Corporate isn’t listed there, it’s not being broadcast on 6 GHz, even if configured correctly elsewhere.

Temporarily disable the Guest SSID

Reboot an AP

Re-survey with Sidekick2

See if Corporate now appears on 6 GHz

[roo54]

I went to Wireless > Monitor > Access Points and selected an access point, but there is no "RF Tab", but what I did see was "BSSID Details" and that showed all four SSIDs on their correct bands

[aleabrahao]

So, I believe that it's not a Meraki issue.

[roo54]

Well, thats what I was beginning to think, that the Ekahau/Sidekick was lying to me, so I had the operator take it to a different site where we knew 6GHz was operating correctly and do a survey there. The Ekahau showed the 6GHz broadcast of both Guest and Corporate there, no problem. The we went back to the affected site: Just Guest, no Corporate on 6GHz, so the issue has to be originating in the Meraki: there's nowhere else to look....

[aleabrahao]

Compare RF Profiles,even if the same SSIDs are configured network-wide, Meraki RF profiles and AP tags are site-specific.

If everything is ok, I suggest you open a support case.

[roo54]

You are on the money with the support case, I started that early on, this one looked weird. I also posted here because I knew there were guys like you with broader experience than me who may have just said "Oh yeah, seen that, just to this , this and this". When the going gets weird, I share as widely as I can 😀

[Karsten Iwen]

On which channels are you running? I am not sure if it is still the case, but some time ago, the Sidekick2 only found SSIDs on PSCs.

[roo54]

We have 200-odd APs, so there should be enough APs running on the PSCs to show up. Also, we are running 80MHz channels, so we will be seeing 4 channesl as one, similar pitch to PSC

[CMR]

The BSSID details are simply the potential BSSIDs, I have 6GHz external APs (CW9163E) and they show the BSSID for 6GHz only SSIDs even though they correctly do not broadcast it as it is illegal to do so in the UK. When I had an exception for testing before launch they did work, but the BSSID details are misleading, at least for the 6GHz band.

[roo54]

Worth knowing, thanks. However, I downloaded the CSV file "BSSID Details" and that showed all SSIDs on their correct bands and documented whether they were broadcast or not. The 2.4 and 5GHz BSSIDs were listed as broadcast and the listing was right, but the right 6GHz BSSIDs were listed as broadcast, even though they weren't, so I take this whole piece of info with a pinch of salt. Meanwhile, if you go into Wireless > Assurance , then look at Infrastructure connectivity, it looks universally bad, but I'm not sure what to do about this