I think the problem is with APX that was connected to Central. The APX 320 which was connected to the Central does not appear in Pending access points but I have the APX740 which has never been connected to Central and this APX is already active at 2.4 and 5 GHz.
I will try to convince APX320 somehow, although I turned it on and off several times (always with at least 5 minutes delay) so in the end is permanently lit red LED, therefore, does not have connectivity to the Internet. I have the APX530 too which is connected to Central, so maybe I'll try that one too ...
We are waiting so long and now such problems ?! I guess without commenting that ...
I think the problem is with APX that was connected to Central. The APX 320 which was connected to the Central does not appear in Pending access points but I have the APX740 which has never been connected to Central and this APX is already active at 2.4 and 5 GHz.
I will try to convince APX320 somehow, although I turned it on and off several times (always with at least 5 minutes delay) so in the end is permanently lit red LED, therefore, does not have connectivity to the Internet. I have the APX530 too which is connected to Central, so maybe I'll try that one too ...
It was the same with the UTM, if AP was joined to central, you needed to remove, reboot, then add it to UTM, it failed, remove it from UTM and add it again, when it was pending.
I will try to block access from the APX to central IP ranges, as it tried on port 443, let's see if XG will be the fallback on 1.2.3.4 ;)
I think the problem is with APX that was connected to Central. The APX 320 which was connected to the Central does not appear in Pending access points but I have the APX740 which has never been connected to Central and this APX is already active at 2.4 and 5 GHz.
I will try to convince APX320 somehow, although I turned it on and off several times (always with at least 5 minutes delay) so in the end is permanently lit red LED, therefore, does not have connectivity to the Internet. I have the APX530 too which is connected to Central, so maybe I'll try that one too ...
It was the same with the UTM, if AP was joined to central, you needed to remove, reboot, then add it to UTM, it failed, remove it from UTM and add it again, when it was pending.
I will try to block access from the APX to central IP ranges, as it tried on port 443, let's see if XG will be the fallback on 1.2.3.4 ;)
Connected it to Central account, let it firmware upgrade in there (Think the new firmware installs xg as fallback?!) Deleted from central, and voila!:
[Unknown] new AP detected, adding to system. ID:P1200xxxxxx Model:APX530 Version:custom-build LAN_MAC:7c:5a:1c:34:59:c8 WIFI_MAC:7c:5a:1c:34:59:c0 Max SSIDS:8 TX Power Control:1 DFS:1
how did you connected an APX to the Central? Through XG or by another connectivity? Because the APX 320 does not want me to join to the Central Account ...
I joined it to another central account that had wireless sub. let it upgrade through there.
Found this just now:
community.sophos.com/.../133505
Problem is, APX does not install latest firmware by themselves.
[Update - RESOLVED] This issue has been resolved - all APX models should now be able to update to the latest firmware when connected to the internet and become compatible for management with XG Firewalls.
Apologies for any inconveniences caused.
Please don't hesitate to PM me directly for any further questions or concerns.
