https://community.hpe.com/t5/bladesystem-general/firmware-upgrade/m-p/628#M33476 It takes approximately 45 minutes to flash a VC-Enet module -- about 10 minutes for a VC-FC module. If you have redundancy designed into your configuration, you should not experience any down time. Thanks, Dave Tue, 28 Oct 2008 16:08:00 GMT David Billot 2008-10-28T16:08:00Z https://community.hpe.com/t5/bladesystem-general/firmware-upgrade/m-p/627#M33475 Does anyone know what the true downtime is on the firmware upgrade for the virtual connects? I have two populated in slots 1 and 2 and just want to get an idea of what impact it will have on my env. My esx env is the most important and I have the virtual switches spread across both. Tue, 28 Oct 2008 14:57:00 GMT https://community.hpe.com/t5/bladesystem-general/firmware-upgrade/m-p/627#M33475 duhaas 2008-10-28T14:57:00Z https://community.hpe.com/t5/bladesystem-general/firmware-upgrade/m-p/628#M33476 It takes approximately 45 minutes to flash a VC-Enet module -- about 10 minutes for a VC-FC module. If you have redundancy designed into your configuration, you should not experience any down time. Thanks, Dave Tue, 28 Oct 2008 16:08:00 GMT https://community.hpe.com/t5/bladesystem-general/firmware-upgrade/m-p/628#M33476 David Billot 2008-10-28T16:08:00Z https://community.hpe.com/t5/bladesystem-general/firmware-upgrade/m-p/629#M33477 If portfast/portfast trunk is configured as appropriate for the number of uplinks you are using you should not experience any problems. My testing with ping reveals a maximum of 2 dropped packets when the active & passive modules swap roles. It appears that the active/active network configuration may be a little better than the active/passive network configuration also. This should not be a problem for any well designed application. Wed, 29 Oct 2008 19:06:00 GMT https://community.hpe.com/t5/bladesystem-general/firmware-upgrade/m-p/629#M33477 Calvin Staples 2008-10-29T19:06:00Z