With two controllers installed, the primary controller handles all the data connections and the secondary is for redundancy in the event of hardware failure (controller), or during firmware updates which require restarting the primary controller. It is important to cable both controllers to non-aggregated ports on the switch and test failover to ensure that it is working properly
The propose of the multiple ports on the controller is for network load balancing. You can configure one to four ports for this model
When a iSCSI initiator requests access to a volume, it contacts the array group via the WKA (a.k.a. Group IP address), once the volume ACL access is verified (via chap, IP address or IQN name - or a combination of them), the array will redirect the initiator to one or more of the array(s) physical eth interfaces (one or more if using multipath on the host). The iSCSI spec doesn't allow for teaming of initiator interfaces on the host.
Joe S586
9 Technologist
•
729 Posts
530
1
Posted August 13th, 2014 13:00
Not sure what your exact question is?
With two controllers installed, the primary controller handles all the data connections and the secondary is for redundancy in the event of hardware failure (controller), or during firmware updates which require restarting the primary controller. It is important to cable both controllers to non-aggregated ports on the switch and test failover to ensure that it is working properly
The propose of the multiple ports on the controller is for network load balancing. You can configure one to four ports for this model
When a iSCSI initiator requests access to a volume, it contacts the array group via the WKA (a.k.a. Group IP address), once the volume ACL access is verified (via chap, IP address or IQN name - or a combination of them), the array will redirect the initiator to one or more of the array(s) physical eth interfaces (one or more if using multipath on the host). The iSCSI spec doesn't allow for teaming of initiator interfaces on the host.
-joe