Ready to manage your wireless network? Think again.
After you configure the controller using CLI’s day-0 setup, you first have to fix the AP country code setting in order to get rid of the day-0 loop on the web GUI. Then you keep following Cisco’s documentation to get your wireless set and deployed. And the app will still not work: unless you provision the network using the app so it add God and Cisco knows what obscure setting, the app will keep asking you to provision this controller, over and over. Hints on how to fix this are inexistent. So if you ever plan on using this app to manage your controller, use it from the start, or forget it ever existed.
Show more
Limited
Wow. This is shockingly bad.
Extremely limited interface.
No ability to drill down into access points or clients to get any sort of troubleshooting information.
Useless for anything other than an initial system setup. Even then it’s barely enough to get you going.
Extremely limited interface.
No ability to drill down into access points or clients to get any sort of troubleshooting information.
Useless for anything other than an initial system setup. Even then it’s barely enough to get you going.
Annoying
Doesn’t support mobility express and Cisco have removed any apps that can support mobility express.
Screen Orientation not working
Appreciate if you could fix the screen orientation issues, we’re using apple iPad w/ magic keyboard and have to disconnect the iPad from Magic Keyboard to view/monitor our WLCs.
Has the features you need for initial setup. Not the features you want after that.
This app made it very quick and easy to get the EWC running on day 0. It took just a minute or two and internet and network were browsable. Then I could login to the WebUI to complete the setup.
Setup of the EWC required this app for me. EWC and AP version 17.6.4. Both the web based deployment and the serial console deployment failed and left things inoperable requiring factory reset. Notes on that below.
Once setup the app is very basic. As mentioned, it had the bare minimum of what you need to get running. After that any information or configuration you want needs to be done from the WebUI or CLI. The app tells you you which AP’s are online and let’s you rename them, and maybe setup administrators. That’s about it.
Finding this app was difficult. After my first two deployment attempts failed I recalled Cisco had a wireless deployment app for using AirProvision. I did a quick search in the App Store but didn’t see it. I did a quick Google search and found Cisco Community posts saying the AirProvision app no longer exists.
Finally I went to the documentation and found the name “Cisco Catalyst Wireless” referenced. Even searching the full name in the App Store it is the fourth result which already had me wondering initially if it no longer existed, since an exact name search didn’t have it show up in the first three I see.
From that point on it was very, very easy. I just had to check the documentation for the first time password.
Within 2 minutes my SSID was up, I could connect, log in to the controller through the WebUI, and see everything.
That wraps up the app review, the rest of this is just environment details that may help someone else or comments on other parts of the setup process.
2 x Catalyst 9130AXI running 17.6.4. I had first tried the EWC deployment through a browser. After the initial screen when I selected finish my SSID was findable by devices but everything else was pretty much in a soft lock. The AP was not passing traffic to the internet. Logging in to the controller showed many blank pages with no connected AP’s and no SSID’s even though I could see it and connect (though I had no internet access). I couldn’t do any configuration as the AP claimed to not be associated. This was after waiting 15-30 minutes.
Reset to factory defaults and tried again using a console cable. Almost the exact same results.
After another reset to factory defaults I tried the app, the process of which is reviewed above.
I have an outstanding issue of the Cisco AirProvision SSID’s still appearing to my devices even though they do not appear in the config. I’m guessing a quick cleanup using the CLI will resolve that.
Setup of the EWC required this app for me. EWC and AP version 17.6.4. Both the web based deployment and the serial console deployment failed and left things inoperable requiring factory reset. Notes on that below.
Once setup the app is very basic. As mentioned, it had the bare minimum of what you need to get running. After that any information or configuration you want needs to be done from the WebUI or CLI. The app tells you you which AP’s are online and let’s you rename them, and maybe setup administrators. That’s about it.
Finding this app was difficult. After my first two deployment attempts failed I recalled Cisco had a wireless deployment app for using AirProvision. I did a quick search in the App Store but didn’t see it. I did a quick Google search and found Cisco Community posts saying the AirProvision app no longer exists.
Finally I went to the documentation and found the name “Cisco Catalyst Wireless” referenced. Even searching the full name in the App Store it is the fourth result which already had me wondering initially if it no longer existed, since an exact name search didn’t have it show up in the first three I see.
From that point on it was very, very easy. I just had to check the documentation for the first time password.
Within 2 minutes my SSID was up, I could connect, log in to the controller through the WebUI, and see everything.
That wraps up the app review, the rest of this is just environment details that may help someone else or comments on other parts of the setup process.
2 x Catalyst 9130AXI running 17.6.4. I had first tried the EWC deployment through a browser. After the initial screen when I selected finish my SSID was findable by devices but everything else was pretty much in a soft lock. The AP was not passing traffic to the internet. Logging in to the controller showed many blank pages with no connected AP’s and no SSID’s even though I could see it and connect (though I had no internet access). I couldn’t do any configuration as the AP claimed to not be associated. This was after waiting 15-30 minutes.
Reset to factory defaults and tried again using a console cable. Almost the exact same results.
After another reset to factory defaults I tried the app, the process of which is reviewed above.
I have an outstanding issue of the Cisco AirProvision SSID’s still appearing to my devices even though they do not appear in the config. I’m guessing a quick cleanup using the CLI will resolve that.
Show more
