We've recently moved from an old ZD setup to the cloud option. I'm pretty disappointed in the amount of access I have lost when it comes to the equipment we've purchased. Not only does the cloud give us absolute bare bones information and options but now it seems I don't even have the ability to log into my access points. Why is this?
Thanks for your feedback. We have a lot more troubleshooting capabilities planned in the near term releases. This will show some of the information and tools available to you today from ZD. So thats coming.
The crux of your question though, is why can't you login to AP UI/CLI. There are a couple of use cases after you login to the AP
- Troubleshooting or monitoring on a per AP level
- Making optimization of config on a per AP or even radio level
Moment you make config changes to the AP or radio from the AP UI/CLI, we end up in a state of two masters controlling that config. One might argue that AP changes should override cloud changes. However, when you consider scenarios at a wider scale this becomes increasingly problematic and runs counter to the philosophy of ease of management via Ruckus Cloud.
So the decision to not allow AP UI/CLI access was a design choice. Let us know what your use case is. We can try and accomodate that using APIs or direct features in the Ruckus Cloud.
Thank you for the concise reply Rajiv. I was mainly looking for information from the AP's and not looking to affect changes. ie, are their heaters enabled? "winter's coming", what is the signal strength between meshed AP's etc. All the information I'm used to finding in the ZD just seems to be locked away behind the cloud. I can certainly see why the decision to disable the CLI was made. I would hope that the informational aspects will soon be brought over to the cloud though.