This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AP55 Bricked After Deleting from UTM 9.4

I received a second AP55 marked as compatible with Sophos Central Wireless.  Before gaining access to Central Wireless, I decided to test mesh on my UTM 9.4 and all worked as expected.

Today, I followed instructions to delete the device from the UTM and attempt registration through Sophos Central.  It eventually timed out, as did the re-attempt.  I then checked the AP to see if it was reachable via ping (I have a MAC address reservation) and it was not.  No amount of reboots, etc seemed to change this behavior nor the status light on the AP.  I then attached it to another router and there were no DHCP attempts there either, and thus no connectivity to cloud for registration.

I found a AP Check utility (sophos_apcheck-1.0.iso), which was not able to detect the AP after following the on screen instructions.

I have been told a firmware flash utility is being created.

Is there anything I can do before that releases?



This thread was automatically locked due to age.
Parents
  • Hello Michael,

    Yes, we have a utility to unbrick the APs. As of now, the tool is only distributed over support.

    After bringing back the AP to a functional state, and registering it to your Sophos Central account will trigger a firmware update. The AP will be more stable after this update and we implemented additional measures to avoid AP from getting into a bricked state.

    regards

    Alex. 

Reply
  • Hello Michael,

    Yes, we have a utility to unbrick the APs. As of now, the tool is only distributed over support.

    After bringing back the AP to a functional state, and registering it to your Sophos Central account will trigger a firmware update. The AP will be more stable after this update and we implemented additional measures to avoid AP from getting into a bricked state.

    regards

    Alex. 

Children