Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 883 views
  • Users 0 members are here
Options
Suggested
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

AP55C deactivated after contact with XG-firewall

Dennis Groppe

Hi,

At the moment we are running an UTM/SG310 firewall I am currently preparing a XG310 firewall for our company network. On the SG310 we had 8 AP55C connected. Yesterday I disconnected the SG and instead temporarily connected the XG to our network to see, what is already working and what not.

Since I reconnected the SG, everything works as expected again, except for all of the AP55s. They are all listed, but as "deactivated" in wireless protection section.

Is there a feasible way to get them working again? I already read that there is no "reset button"... Restarting an AP does not help either.

Thank you for any advice! Here is a part of the ever-recurring live-log entries for wireless protection:

2021:08:15-10:48:42 utm-1 awed[32520]: [A4002xxxxxxxxxx] AP55C from 192.xxx.xx.xx:38905 identified as A4002xxxxxxxxxx
2021:08:15-10:48:42 utm-1 awed[32520]: [A4002xxxxxxxxxx] (Re-)loaded identity and/or configuration
2021:08:15-10:48:42 utm-1 awed[32520]: [A4002xxxxxxxxxx] Corrupt payload. Device may have wrong key. MD5 of the key is 140394223959a8d1620c50a09c773a84. Delete device to re-register it.
2022:03:19-12:18:45 A4002xxxxxxxxxx aweclient[1002]: facility_awed.c (258) Error while reading data from awed.
2022:03:19-12:18:45 A4002xxxxxxxxxx aweclient[1002]: json_messages.c (546) Error while reading data from awed.
2022:03:19-12:18:45 A4002xxxxxxxxxx aweclient[1002]: Cloudclient not found on ubus.
2022:03:19-12:18:45 A4002xxxxxxxxxx aweclient[1002]: aweclient.c (822) Magic IP not found.
2022:03:19-12:18:45 A4002xxxxxxxxxx aweclient[1002]: aweclient.c (2514) Cannot find a magic IP in configuration, retry later.
2022:03:19-12:18:45 A4002xxxxxxxxxx aweclient[1002]: aweclient.c (2567) Error in getting new configuration. Reconnecting (20)
2022:03:19-12:18:45 A4002xxxxxxxxxx aweclient[1002]: aweclient.c (2688) Failed to configure device.
2022:03:19-12:18:45 A4002xxxxxxxxxx aweclient[1002]: Closing log...


This thread was automatically locked due to age.
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to Sophos Community.

    I'm moving this thread to correct Sophos(XG) Firewall forum.

    Ensure that latest 'AP Firmware' pattern is installed(SYSTEM > Backup & firmware > Pattern updates).

    If the latest pattern is installed then try deleting inactive AP from the access points list and add it again from the Pending list.

  • 0

    Hi 

    Hope you are doing well!

    Thanks for sharing all the information and logs.

    2021:08:15-10:48:42 utm-1 awed[32520]: [A4002xxxxxxxxxx] Corrupt payload. Device may have wrong key. MD5 of the key is 140394223959a8d1620c50a09c773a84.

    Solution: Delete Wireless AP from the firewall appliance and re-register it. You can switch to ISP also.

    Please note that Sophos AP55C has already been declared as EOS and EOL soon.

    EOS - Sophos AP55c - Please read this link for more information. 

  • 0 in reply to NM_1987

    Thank you for your reply! I wasn't sure if I can delete them without losing the wireless configuration. Meanwhile we decided that my collegues can wait for the WLANs till the XG becomes the firewall "on duty", so there is no urgency. What does "switch to ISP" refer to in this case? What is ISP?