I couldn’t find any correct documentation about how to actually reset the configuration of a HP MSM720 Wireless Controller without using the web interface and I had to figure it out for myself – the issue that caused me needing to do this is in the second half of this post. Here’s how you do it:
Connect via serial to console port
Here’s a screenshot from PuTTY with everything you need to know:
Reset the configuration
Type in the following commands to clear the configuration and reboot the device:
What doesn’t work
The documentation talks about using the Reset and Clear buttons together to return the device to factory defaults. Here’s a picture of the device:
What you actually find when you try it is that there isn’t a clear button, only a hole. I’ve seen this on at least two different controllers so this definitely isn’t a manufacturing fault but I’ve no idea why. What this means, of course, is that you have to use the CLI method above to reset the device.
The original issue
I install a lot of HP MSM equipment and am used to the more than occasional idiosyncrasy (more on that another time) but by and large they do what you tell them to do. This one had me stumped. Consider the following:
Access Network VLAN IP: 10.100.1.10/24
Internet Network VLAN IP: 10.100.99.10/24
Default Gateway IP: 10.100.99.254
Static Route: Destination 10.0.0.0/8, next-hop 10.100.1.254
Here you have the basic information for the initial configuration of an MSM720 with an “inside” and “outside” network assuming that the internal LAN/WAN is based on 10.x.x.x addresses and the internet is available through the gateway on the Internet VLAN at 10.100.99.254. You need the static route as you can’t have two default gateways and need the controller to be able to talk to the APs across the internal networks. All completely textbook.
Unfortunately, when configuring these settings, in this order, on a controller that came out of the box running version 220.127.116.11 – the controller stopped responding when applying the static route. Power cycling the box would appear to work but I couldn’t ping the device on the LAN or Internet VLANs but the console was perfectly responsive once I’d figured out the very odd serial settings.
After resetting the box, I upgraded it to V18.104.22.168 and went through the above steps with no issues this time. It’s also my understanding that this issue is fixed in 22.214.171.124 but I’ve not fully tested this.