iSCSI trying to be too clever
Just setting up an iSCSI LUN to dump WSUS updates onto with our Storevault S500, got a dedicated HP Gigabit switch for the traffic and separate NIC in the servers when I'm making iSCSI connections. Made separate 172.16 addresses for the SAN and server NICs, so far so good.
Make the iSCSI connection, logon to target, bind volume no trouble. Then as a test I pulled out the network cable... yet everything still works :confused:
Seems that because the Storevault has SAN and NAS (and thus has a connection to the main network) the iSCSI initiator finds the other route to the SAN and then sends the traffic through that if the primary connection goes. Thing is once it's failed over I can't see a way to change it back unless I logoff the target and logon again.
Checked this with network monitor and I can see the iSCSI data going over the main network IP if the 172.16 NIC goes - by default it goes over the correct connection.
Is there a way to exclude certain NICs from iSCSI traffic as really I don't want that extra overhead on the network if the iSCSI NIC did do bang...