I created a new test account, once inside a policy and a location and purchased a new AP121 which I added in HiveManager. I don't see the SSID I created hence I can't use the AP. Why could that be?

[akira]

I created a new test account, once inside a policy and a location and purchased a new AP121 which I added in HiveManager. I don't see the SSID I created hence I can't use the AP. Why could that be?

[AnonymousM]

There are a few types of communications. Some basic things are sent/received over the CAPWAP session. But some more secure things (configuration updates) are sent over SSH/HTTPS sessions. I suspect that CAPWAP is being allowed out/in fine - denoted by the white LED and your ability to manually reboot it from the GUI but the secure port(s) are not based on the fact that you cant push a config or get a config delta on the device.

I'd start my troubleshooting with content filter and/or firewall for proper ports being opened.

[akira]

Thank you BJ Stahlin. I'm totally lost here. The device does restart when I restart it from the cloud, so I guess the communication is working. Also it shows a white light. On the 2 error indicators (the "device Update Failed" and the red exclamation (!) mark next to the green hexagone, this is what I see. I do not understand which warnings are important or not. I'm a bit frustrated....

[bruce_stahlin]

It appears the config was never successfully pushed, as noted by the failed update notification. This is usually due to loss of capwap between the device and HiveManager, which is either a result of a misconfig in the layer two (vlan) or three (ip/routing) configuration. If you roll over the failure notification, it might lead you toward a resolution. After you've identified and corrected the misconfiguration and a successful push, your AP should be operational.

[akira]

This is what I see. Note it complains that "Device Update Failed"