This section assists you in configuring your DS400 so that the host can detect the storage. Refer to the ServeRAID Manager User’s Guide for complete details.
If you are here as the result of a problem, make sure that
the ServeRAID Access Control List (ACL) contains the Port Node Names of your
HBAs and that logical drives have been mapped to the host.
Host assignment
ServeRaid Manager can automatically discover the initiators connected to each of the enclosure ports. To automatically discover the initiators, do the following:
1.
From a ServeRAID Manager Session,
right-click the enclosure and select Configure Enclosure from the pop-up
menu. Create an array and logical drives (if not already done).
2.
From the ServeRAID Manager Access
Control – Add an Initiator dialog, click on the Discover new
initiators. Select the desired initiator and edit the Initiator alias
name to one of your choice. See figures 1
and 2.
3.
You can now assign the logical
drives to the initiator using its alias. See Figure 5 . If the ServeRaid Manager automatic
discovery is not successful, you can cut and paste the Port Node Name from the
Information tab of FAStT MSJ to the ServeRaid Manager Access
Control – “Add an Initiator” dialog box. Refer to Viewing the
configuration with FAStT MSJ
Note: When two or
more initiators on the same host (that is the host has two HBAs) are assigned
to the same logical drive(s), make sure that the LUN ID for the logical drives is
the same for each initiator. Example:
Host A initiator 1 and Host A initiator 2 assigned to
Device-1 should have the same LUN ID (LUN 0 for ex.)
See Host assignment in a multi path environment.
Figure 1 – ServeRaid Manager Initiator Dialog
Figure 2 – ServeRaid Manager Select a discovered initiator dialog
Viewing the
configuration with FAStT MSJ
Figure 3 – FAStT MSJ HBA Port information tab
Note: Remove the dashes if name was pasted from FAStT MSJ.
Figure 4 – ServeRAID Add Port Name
Figure 5 – ServeRAID Assign Devices to initiator
-
Note: Each tab represents a different HBA alias.
Host assignment in a multi path environment
In order for a host with two HBAs to have access to the LUNs in a multi path environment (redundant configuration), both initiators need to be assigned to the LUNs in the Access Control List. In this instance, the LUN ID for a particular LUN needs to be the same for both initiators.
Figures 6a and 6b show an example of a host to LUN assignment. ServeRAID Manager highlights LUNs with multiple assignments in red. SCTRLA1 and SCTRLB1 have the same LUN ID respectively for both initiators. This is a valid configuration.
Figure 6a – HBA0 assignment to LUNs
Figure 6b – HBA1 assignment to LUNs
By contrast, Figures 7a and 7b show an example of a host to LUN assignment whereas the same LUN has a different ID for each initiator. This is an invalid configuration. ServeRAID Manager will flag this configuration as a Warning. See Figure 8.
Figure 7a – HBA0 assignment to LUNs with different ID
Figure 7b – HBA1 assignment to LUNs with different ID
Figure 9 shows the HBA tree from FAStT MSJ. The HBAs are assigned to each LUN. The MPIO driver will manage the path from each HBA to the controller ports in the event that a path failure occurs on either HBA.