Hello Oliver,   In the same download area as the firmware and release notes is another PDF, titled "iSCSI initiator and operating system considerations optimizing your SAN environment for High Availability"   That has some key settings that will allow your VMs and servers to ride out the failover time.  It's important to set that not only for Firmware Upgrades, but in the event of an unexpected fail over due to a CM failure.   Additionally if you are using VMware ESXi, there is a best practices PDF for that as well.  In addition to better handling the failover, these changes have been shown to improve performance as well.   The Tech Report TR1091 is available here:   [URL] The changes for Windows VMs and the ESXi nodes will require a restart to become effective.  What firmware version are you at, and what version are you upgrading to?  Other things I always suggest with upgrades is make sure both controllers are plugged into your switch and in the correct VLAN.  Since the active CM will failover to the passive, support gets many calls for can't access storage after firmware upgrade.  Or the standby ports weren't in the correct VLAN, or disabled, etc...      It's for these reasons, that personally I prefer to do upgrades via the serial port CLI.   The process is more verbose, and if something should go wrong, you need the serial port any way.   Having that setup and tested ahead of time is a huge time saver.   Here we use serial mux's so that all the array controllers can be accessed easily.  Regards,  Don  
Hi, I need to upgrade the firmware on my PS6100 EqualLogic controllers. I've found the instructions on how to do this and it all looks straight forward to do through the GUI. I notice there is a restart needed after the firmware has been applied. Does this mean I need to gracefully shutdown the VMs running on my SAN LUNs? Will my iSCSI connections be closed/broken during the post firmware upgrade restart? Thanks, Oliver.
Post firmware upgrade restart