Hello,   Are the servers also on the "SCSI" switches?   I don't this being done without an outage.  You'll have to log out all the server connections, enter the new discovery address and re login.  If you have both at same time, you'd end up "double mounting" the volumes.  Which would likely lead to corruption when you logged out the old connections.   Otherwise your plan is mostly correct.   1.) Logout all servers  2.)  Change one port on each member to the new subnet.  3.)  Change the Group IP address  4.)  Change the remaining IP addressed one at a time.  Do one interface on one member, then another. 5.)  Assuming you are going isolate the switches, remove the inter connection between them.  6.)  Cable the Mgmt ports to the LAN switches, and enable Dedicated Mgmt on all members  7.)  Ping test every interface from the servers.   8.)  Remove old Discovery address and Favorite targets for windows. (Static Mappings for VMware)  9.)   Add new Discovery address and log volumes back in.   10.) Repeat on remaining servers    Regards, Don  
Hi, I wanted some advice on changing the ip addresses and subnet. I have a group with 3 equallogics, currently the group ip and the individual ip addresses are in the same subnet as the main network (though separated on different switches). The management ports are not enabled. (Don't ask, it's just the way it is!!!) What I want to do is change all the iscsi ports to another subnet, enable the management ports on the original subnet. How do I best do this without downtime (if possible)? Should I do the following 1. Change 1 nic on each server to the new subnet 2. Change eth1 on each equallogic to the new subnet 3. Change the Group IP to the new subnet 4. Connect targets in iscsi initiator on the servers to the new IP 5. Change the remainder of the nics on servers and equallogic to new subnet 6. Enable management nics on old subnet   
Changing IP and subnet