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

9.400 bricks connected APs!

Hello,

just a heads up warning regarding the soft released 9.400.

Just installed it on the gateway and all connected APs that were using VLAN tagging and bridging communication to VLANs got bricked by the AP firmware update.

If the AP is not using VLAN tagging and wireless networks just use bridging to AP LAN then it works. If VLAN tagging is used then after the firmware update the AP never finishes booting and gets stuck while trying to get IP address from DHCP in an never ending loo (AP50). Got a confirmation from a customer where it bricked their AP30s. For AP50 and 30 it is possible to use the flash tool to get them back to working state. Unfortunately AP55c gets bricked totally as there is no flash tool for it and after it gets the 9.400 firmware update and is deployed with VLAN tagging enabled it basically dies and never finishes booting or does not even get to a point of requesting the IP address from DHCP and gets stuck rebooting over and over again.

After rolling back to 9.355 (restore from tape) and reflashing the APs using the recovery tool (when possible) wireless works fine.

Looks like some nasty bug that slipped through QA... again :(

This thread was automatically locked due to age.

Parents

BarryG over 8 years ago

I'm trying to get my AP30 working with 9.400 in ESXi...

I'm trying with Tagging or Untagging VLAN 1 on the switch port to the AP, and Tagging it to the UTM.

The UTM saw the AP at least briefly, but it won't go 'Active'.

The AP ultimately is supposed to get its management IP on VLAN 13, but that isn't happening.

Thanks,

Barry
Cancel
Vote Up 0 Vote Down

Cancel
etaube over 8 years ago in reply to BarryG

Hi Barry,

what does the switch port config says about VLAN 13 (on the switch port to the AP)? tagged, untagged or both? The AP was configured (the last time it worked) with vlantagging enabled and as vlantag 1 or 13?

Regards,
Emanuel
Cancel
Vote Up 0 Vote Down

Cancel
BarryG over 8 years ago in reply to etaube

Hi,

All VLANs are Tagged to both the AP30, and to the ESXi host the UTM is running in. The ESXi host provides multiple NICs (one per VLAN) without tagging to the UTM.

Previously, I had port 1 Untagged going to the AP30; I've tried that as well but can't get it working.

I'm not sure if this is a 9.4 problem or not, so I've also posted a new thread at https://community.sophos.com/products/unified-threat-management/f/52/p/75990/292124#292124

Thanks,
Barry
Cancel
Vote Up 0 Vote Down

Cancel

Reply

BarryG over 8 years ago in reply to etaube

Hi,

All VLANs are Tagged to both the AP30, and to the ESXi host the UTM is running in. The ESXi host provides multiple NICs (one per VLAN) without tagging to the UTM.

Previously, I had port 1 Untagged going to the AP30; I've tried that as well but can't get it working.

I'm not sure if this is a 9.4 problem or not, so I've also posted a new thread at https://community.sophos.com/products/unified-threat-management/f/52/p/75990/292124#292124

Thanks,
Barry
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data