This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Heads up that both of the latest firmware updates for WAX630E APs (10.3.1.7 & 10.3.1.8) appear to break my pretty simple set up:
Two WAX630E using POE++
Untagged VLAN unchecked
Management VLAN configured to alternative value
Couple of SSIDs with separate VLANs
When upgrading to either of the new Firmwares, the APs immediately show as disconnected from Insight and are unresponsive locally. Only solution I found was to disconnect from LAN, connect to power brick, factory reset and rollback the firmware to 10.2.0.19 using the local web interface. This creates a problem because Insight forces Firmware update when you add new devices (which brings them back to the broken 10.3.1.7 or .8 version now) and the only choice is to factory reset / run locally.
APs worked (well enough) on 10.2.0.19 so something certainly changed with 10.3.1.7 (like the bug introduced with WiFi passwords containing special characters) and 10.3.1.8 was rushed out to fix it (no download link even available yet, but Insight enrollment will pick it up and force install .8).
This is pretty frustrating as I've had nothing but issues with the WAX630Es since they arrived from preorder. After more than a year, I still had constant disconnects/crashes which I believe could be related to 2.4 GHZ and 5 GHZ being broadcasted on the same SSID and now this Firmware issue may be the final straw.
Nice. Are you running the 10.3.1.8 firmware on your WAX6xx devices? If so, have you noticed any issues with operating the management interface on an alternative VLAN ID? Do you have the untagged VLAN box checked?
If so, have you noticed any issues with operating the management interface on an alternative VLAN ID? Do you have the untagged VLAN box checked?
That makes a different topic I'm following for a longer time here. Unfortunately currently in the local university clinic a stroke center for almost four weeks now, so limited physical access to my test grounds.
