FortiAP 233G cannot use multiple SSIDs on 2.4Ghz radio

[cjackson_ncl]

We have recently migrated a number of sites away from older FortiWLC Controllers and Meru AP's to FortiGates and FortiAP's, and found we are having a number of issues with AP's not publishing SSID's on the 2.4Ghz radio when multiple SSIDs are configured. In our case there are 3 SSIDs.

For example, we have a FortiAP 233G with 3 SSID's configured on the 2.4Ghz and 5Ghz radios as follows;

SSID1

SSID2
SSID3

The SSID's are in bridged mode. 5Ghz clients can see and connect to all 3 SSID's with no issues. However 2.4Ghz clients can only see and connect to SSID1. It can happen randomly across any of the FortiAP's we have installed and is happening at multiple sites.

If we enable any one of the 3 SSID's on the 2.4Ghz radio on its own, devices can see and connect to the SSID with no issues, so it seems the FortiAP 233G has an issue when the 2.4Ghz radio is configured with multiple SSID's i.e. devices can only see and connect to one of the SSID's.

Has anyone else experienced this? If so were you able to resolve it and how did you do so?

Our FortiAP's are managed by FortiGate on FortiOS 7.4.7 and the AP's are on 7.4.5. An ticket has been raised with TAC also.

Thanks in advance for any help or suggestions.

[Jean-Philippe_P]

Hello cjackson_ncl, 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

Thanks, 

[Jean-Philippe_P]

Hello,

We are still looking for an answer to your question.

We will come back to you ASAP.

Thanks,

[ebilcari]

Are all the SSIDs in bridge mode or also in tunnel mode? You can check the 'Operation Profiles' for the AP under Radio settings. Use Manual if the setup has a mix with tunneled and bridge SSIDs and make sure that all the SSIDs are added in the list.

[cjackson_ncl]

They are in bridged mode. The issue boils down to failed beacons on each SSID when the issue occcurs. TAC have provided us with firmware to try and resolve the issue which appears to be working so far