Network Management

Hi all,

We have a vsf stack consisting of a couple of Aruba 5400's which forms the distribution layer of our network.

With everything connected via LACP trunks, the stack is capable of a firmware upgrade with no impact to connected devices using the 

 vsf sequenced-reboot command.

We're wanting to upgrade this using Airwave going forward, but want some certainty around how Airwave will manage this upgrade.  Unfortunately we don't have enough sparing to test this ourselves.

Does anyone have any experience with upgrading the firmware of 5400 vsf stacks? Or know how Airwave will handle this?

Thanks,

Ben.

https://support.arubanetworks.com/Documentation/tabid/77/DMXModule/512/Command/Core_Download/Default.aspx?EntryId=37244

Please check supported device list, Airwave supports firmware upgrade, it support multiple protocols to push firmware to switches.

Below screen shot provide protocol it supports and location where we need to upload firmware files.

We can initiate firmware upgrade from Groups> <click any Group>  >Firmware tab or from Devices> List page > click on pencil icon (modify devices) and select devices from the list and from drop down list choose option upgrade firmware for selected devices.

Also check below setting in AMP Setup > General page, if switches are in monitor mode then you need to enable this option.

Hi Pavan - thanks for the response.  I've been upgrading firmware fine - very familiar with the process thanks.

This is a specific question about how Airwave will handle the vsf stack - we need to ensure it will do the upgrade without impacting downstream switches.

Upgrading stack switch from Airwave will not impact downstream devices, Airwave will push firmware to commander in stack and commander will push firmware to members and reboot complete stack.

Right. Thanks for confirming that, that’s disappointing. 

The 5400 stack supports non-stop switching (or ISSU) and can upgrade without downtime to switching - it doesn’t need to do a stack reboot

If the whole stack reboots as you say, then all downstream switches/clients are impacted.