Unable to get latest AP Firmware Pattern Update

Hi Bruce,

I think it is called 11.0.18-a or v11.0.8-1 and if you register your APX120 in CM the issue is supposed to be fixed going from memory of details in other posts on the subject.

I could connect one my APX120 to my EAP to see the version number if that would help, it is currently sitting idle.

Ian

I'm sorry there may be some confusion -- why would I need to register an AP in central to make sure the SFOS system (I think I did not make it clear -- I'm controlling the AP from the firewall, NOT central -- now that I re-read your post, pretty sure this is where the confusion lies) pulled a firmware pattern update.  I'm talking about this screen:

If I read the release notes correctly, installing .017 will probably brick my APX120.  Need to see how to get v19 to full the newest wifi firmware if possible.

I'm sorry there may be some confusion -- why would I need to register an AP in central to make sure the SFOS system (I think I did not make it clear -- I'm controlling the AP from the firewall, NOT central -- now that I re-read your post, pretty sure this is where the confusion lies) pulled a firmware pattern update.  I'm talking about this screen:

If I read the release notes correctly, installing .017 will probably brick my APX120.  Need to see how to get v19 to full the newest wifi firmware if possible.

As far as i understand, you have to first install 017 to get to 018. It is currently a upgrade path and not a migration. 

Other reported the same in the 018 release notes: https://community.sophos.com/sophoswireless/b/blog/posts/release-notes-news-the-ap-firmware-11-0-018-for-sophos-firewall-os-sfos

Sophos is currently looking into this. Could be, because the appliance "know" there is a 017 and did not replace it with 018, as the U2d already reported 017. 

So you'd have to brick your AP to attempt to update it?  That doesn't sound right; the firewall should just pull the latest available.  I'm pretty sure I've probably seen that behavior before in the past as well.  I suspect that maybe Sophos just hasn't have .018 available for the v19EAP systems, but I could be wrong.

Agreed. Forwarded some feedback about this situation. 

Hi Bruce,

there is no confusion. I am running v19 EAP with AP firmware 11.0.018 and I am managing my APX120 via CM which is also running AP firmware 11.0.018. The issue you are addressing only occurs on devices being managed by XG not on those managed by CM.

Ian

I think you missed my point entirely -- if one is using the XG/S for wifi management (not central like you), and you upgraded to wifi firmware on the XGS to 11.0.17, you can brick an attached APX120.  what needs to happen is to have the XGS make the latest available firmware update available, to avoid issues like this, not make an admin go through each update (including a potentially damaging one) in sequence to get to a good one.  It's a different situation than your central-managed AP.  That's the point I was making.

Just a headsup: 11.0.17 is not broken, as it got replaced. So you are not breaking your APX by installing 11.0.17. 

LuCar, thanks for the info -- is there a place this information is posted publicly?  I guess you can see how this would be confusing...

Well I did apply it just now and it didn't brick the APX120, so there's that :)