Has anyone seen an issue with version 18.104.22.168-001R where the virtual controller will respond to a ping but the web interface stops working as well as the ability to ssh into the VC as well? The only way to get back into the web interface is to find which AP is acting as the VC and physically reboot it. I started noticing the problem with version 7.3 and have kept upgrading each time to see if a newer release would resolve it but it seems that it has only gotten worse.
Best answer by Daren Ellis
Most likely your issue is the AP configuration and not the firmware.
From your description of the problem you either attempted to configure dynamic virtual controller.
Or accidentally configured multiple APs via the AP profile to be a virtual controller.
Would suggest “if you have a device under contract” opening a ticket with GTAC to clean up the configuration.