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

Hi,

I've updated to 9.401 but am still not having any luck; it may be an issue with how I have my network and ESXi set up; I'd appreciate a look at my other post at
https://community.sophos.com/products/unified-threat-management/f/52/p/75990/292124

Thanks,

Barry
Cancel
Vote Up 0 Vote Down

Cancel
alda over 8 years ago in reply to BarryG

Hello Barry,

I have instaled the update from 9.400 to 9.401 and WiFi works well!

Our APs connected to VLAN trunk work absolutely reliably. We have connected APs to ESXi ( ESXi 6.0 U2 ) by distributed virtual switch trunk.

alda
Cancel
Vote Up 0 Vote Down

Cancel
BarryG over 8 years ago in reply to alda

Hi, I'm passing separate vNICs to the UTM instead of trunking...

Please see my diagrams at https://community.sophos.com/products/unified-threat-management/f/52/p/75990/292124

Thanks,

Barry
Cancel
Vote Up 0 Vote Down

Cancel
alda over 8 years ago in reply to BarryG

Hello Barry,

I think you have a mistake in the definition of the interface eth1 in your UTM. This inteface is defined as " classical" Ethernet interface but the LAN interface at the ESXi is defined as VLAN 13. At the ESXi interface is a traffic tagged with tag number 13 but in UTM this traffic does not have a relevant tag - VLAN 13.

I think if you change the definition of interface the eth1 to VLAN interface with VLAN 13 network it will work.

And, of course, you have to similarly configure appropriate port of a LAN switch to which you are possibly connected AP30, if you do not have it connected directly to ESXi ....

alda
Cancel
Vote Up 0 Vote Down

Cancel

Reply

alda over 8 years ago in reply to BarryG

Hello Barry,

I think you have a mistake in the definition of the interface eth1 in your UTM. This inteface is defined as " classical" Ethernet interface but the LAN interface at the ESXi is defined as VLAN 13. At the ESXi interface is a traffic tagged with tag number 13 but in UTM this traffic does not have a relevant tag - VLAN 13.

I think if you change the definition of interface the eth1 to VLAN interface with VLAN 13 network it will work.

And, of course, you have to similarly configure appropriate port of a LAN switch to which you are possibly connected AP30, if you do not have it connected directly to ESXi ....

alda
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data