I'm doing with one AP 121 with wpa2 authentication. But some devices such as mobile or laptop can not see the ssid. While almost them can see the ssid and can connect with it.
Can you trouble it for me? thanks
Until someone more knowledgeable replies, you can check the following:
Are your APs using both the 2.4 and 5 GHz bands? If only 5 GHz is enabled devices without dual-band radios won't see an SSID broadcast on those APs.
You can go into Configuration > Configure and Update Devices, click an AP and see if the Admin State of the 2.4 GHz interface is up or down. If it's down then it won'e be available and devices without dual-band radios won't be able to see SSIDs broadcast on that AP.
You also might want to create a brand new SSID object to make sure none of the defaults have been changed (disabling WMM or altering data rates) which could cause client issues as well.
While you have shown us that your Access Point has 2.4 and 5.0 Ghz Radios enabled it could be that the SSID is only applied (through the SSID configuration) to one radio, Can you provide a screenshot of your Network Policy and one of the SSID in question with the Data Rates expanded?
That problem was solved when I create new brand WLAN Interface 2.4GHz/ 5GHz are Wifi_01/Wifi_02. It's shown in the picture below. That client is connected to the SSID.
However, when I deploy new AP 121 in another project, that problem is still met. I try to create new brand WLAN Interface like as what I do before. But Its not working. I dont know how to fix it. Can you help me with it. This is my configuration for SSID and Data Rates
I would still be interested in a client monitor output of one of the clients with the default radio profiles (radio_ng0 and radio_an0). Hope this helps.
I tried everything. reset config in CLI, reboot, new Network Policy, new SSID, remove everything, start over, different radio modes, pull power cord on AP, etc etc...
The thing that DID help was to set 2,4ghz radio to NOT auto in sending power. Eg 15dBm. Then it suddenly started broadcasting the SSID. I could also safely switch back auto mode after this. I have no idea what was causing this, it seems to be so random, but I'm glad I finally got it working.