Virtual Connect Failover Documents

[chuckk281]

Andrew was working with a customer on the firmware update process:

************

I have a customer woring with Virtual Connect and that they see that the modules goes offline when the firmware is upgraded.   

We’ve positioned the fact that properly bonding NIC’s in the blades will mitigate most of this disruption. Does anyone know of or have a whitepaper or document that we can use to as a reference to properly upgrade VC modules without disruption.

************

Reply from Aleksandar:

**************

I have done dozens of firmware upgrades on OA and VC via VCSU and haven’t encountered issues with modules going offline or other issues if the environment is healthy and properly prepared (VC module redundancy, proper stacking and proper blade configuration with active-active links, etc. ).

From top of my mind I am attaching few good documents that provide good insight on the FW upgrade process and several approaches for Virtual Connect modules.

**************

Suggestions or comments on your experiences?