Rossaveling,   You can indeed change the individual IP's without a loss of the traffic. Now you will need to move all traffic from the controller first, over to the second controller, then you can make the change.   It runs along the line of a controller replacement, without replacing said controller.    One way of moving the traffic would be to shutdown the controller, as described on page 75 here.    You can also find the other steps on configuring the iSCSI as well.   Let me know how if this helps.    
Hi All, I've got an ME4024 that was originally deployed using a single /24 subnet for iSCSI networking.  I'm planning to introduce redundancy on that network and will be adding an additional iSCSI NIC to clustered Hyper-V hosts.  Therefore I'd like to re-IP both controllers to be on different /16 networks. Despite the hosts only having a single iSCSI NIC at this time, MPIO is in use with 8 paths configured to all ports on the ME4024.. I hope to do each controller one at a time so to keep everything up and avoid VM downtime.  Can anyone confirm that changing IPs on a single controller will not disrupt traffic on the other controller? Thanks in advance, Ross
PowerVault ME4024 - Changing controller IP addresses