The next step in configuring 3510s is to map logical disks to controller channels. The following tasks needs to be done
Each of logical partitions needs to map a channel in a both controllers in order systems to see them as disks.
Each logical partition is mapped to specific set of hosts as shown in Figure 2–5 below. We will use LUN masking on minnows to filter maps to specific hosts WWNs.
Each channel on minnows needs one logical disks mapped to LUN 0 and it should be free of LUN masking. This is the requirement for each of the hosts to see other volumes. We use leftover partition for this purpose to map to LUN 0 on each channel without any hosts filter.
Each logical partitions must be mapped to both channels on primary and secondary controllers. So depending on the logical drives (disks) the channel assignments vary. Drives assigned to the primary controller (ld0, ld2 and ld4) are mapped as follows:
0 channel tgt:40 is on controller 1
4 channel tgt:44 is on controller 2
Drives assigned to the primary controller (ld0, ld2 and ld4) are mapped as follows:
1 channel tgt:42 is on controller 2
5 channel tgt:46 is on controller 1
All LUN mappings are listed in the following table and color coded in Figure 2–5 below.
Table 2–5 LUN Mappings
3510 name |
Logical Drives |
Logical Volumes |
Hosts Mapped |
---|---|---|---|
amer-minnow-01 amer-minnow-02 |
ld0, ld2 |
ld0-00, ld2-00 |
phys-bedge5-1 phys-bedge5-2 |
ld4 |
ld4–00, ld4-01, ld-02, ld4-03 |
phys-bedge4-1 phys-bedge4-2 |
|
ld0, ld1, ld2, ld3, ld5 |
ld0-01, 02, 03 ld1-01, 02, 03, ld2-00, 01, 02, 03 ld3-00, 01, 02, 03 ld5-00, 01, 02, 03 |
phys-bedge1-1 phys-bedge1-2 |
|
ld1 |
ld1-00 |
phys-bedge1-2 (ldap) |
|
amer-minnow-03 amer-minnow-04 |
ld0, ld2 |
ld0-00, ld2-00 |
phys-bedge6-1 phys-bedge6-2 |
ld4 |
ld4–00, ld4-01, ld-02, ld4-03 |
phys-bedge4-1 phys-bedge4-2 |
|
ld0, ld1, ld2, ld3, ld5 |
ld0-01, 02, 03 ld1-01, 02, 03, ld2-00, 01, 02, 03 ld3-00, 01, 02, 03 ld5-00, 01, 02, 03 |
phys-bedge2-1 phys-bedge2-2 |
|
ld1 |
ld1-00 |
phys-bedge2-2 (ldap) |
|
amer-minnow-05 amer-minnow-06 |
ld0 |
ld0-00 (ldap) |
phys-bedge3-2 |
ld2 |
ld2-00 (IM) |
phys-bedge5-2 |
|
ld4, ld5 |
ld4-00, 01, 02, 03 ld5-00, 01, 02, 03 |
phys-bedge4-1 phys-bedge4-2 |
|
ld0, ld1, ld2, ld3 |
ld0-01, 02, 03 ld1-00, 01, 02, 03 ld2-00, 01, 02, 03 ld3-00, 01, 02, 03 |
phys-bedge3-1 phys-bedge3-2 |
Create an alias for each of the host WWNs on the minnows so that mappings of disks will much easier and for troubleshooting. We need to create 4 aliases for each of system as they have 4 paths (WWNs):
sccli>create host-wwn-name 210100E08B3B4CA5 phys-bedge1-1-c4 sccli>create host-wwn-name 210000E08B1B58A4 phys-bedge1-1-c5 sccli>create host-wwn-name 210100E08B3B58A4 phys-bedge1-1-c6 sccli>create host-wwn-name 210100E08B3B8BA4 phys-bedge1-1-c8 [...] |
Note: c4 ,c5, c6, c8 are controller names as seen by system for each HBA's port and gathered as part of the hbamap script in To Create the Zones or by running cfgadm -al.
Verify that you have created all the aliases required:
sccli> show host-wwn Host-ID/WWN Name -------------------------------------- 210100E08B3B4CA5 phys-bedge1-1-c4 210000E08B1B58A4 phys-bedge1-1-c5 210100E08B3B58A4 phys-bedge1-1-c6 210000E08B1B8BA4 phys-bedge1-1-c7 210100E08B3B8BA4 phys-bedge1-1-c8 210100E08B3B66A5 phys-bedge1-2-c4 210000E08B1B70A9 phys-bedge1-2-c5 210100E08B3B70A9 phys-bedge1-2-c6 210000E08B1BB4A2 phys-bedge1-2-c7 210100E08B3BB4A2 phys-bedge1-2-c8 210100E08B3B08A6 phys-bedge2-1-c4 [...] |
Map all of the LUNs using the sccli interface, according to Table 2–5. Leftover LUNs ld0-04 and ld1-04 are mapped to channels without hosts filters:
sccli> map ld0-04 0.40.0 sccli> map ld0-01 0.40.1 phys-bedge1-1-c6 sccli> map ld0-01 0.40.1 phys-bedge1-1-c8 sccli> map ld0-01 0.40.1 phys-bedge1-2-c6 sccli> map ld0-01 0.40.1 phys-bedge1-2-c8 sccli> map ld0-02 0.40.2 phys-bedge1-1-c6 [...] |
The complete list of mapping commands for each minnow is given in Appendix A, Logical Unit (LUN) Mapping.
Verify the mapping on each minnow by running show map command:
sccli> show map Ch Tgt LUN ld/lv ID-Partition Assigned Filter Map -------------------------------------------------------------------------- 0 40 0 ld0 08C6C8D4-04 Primary 0 40 1 ld0 08C6C8D4-01 Primary 210100E08B3B58A4 {phys-bedge1-1-c6} 0 40 1 ld0 08C6C8D4-01 Primary 210100E08B3B8BA4 {phys-bedge1-1-c8} 0 40 1 ld0 08C6C8D4-01 Primary 210100E08B3B70A9 {phys-bedge1-2-c6} 0 40 1 ld0 08C6C8D4-01 Primary 210100E08B3BB4A2 {phys-bedge1-2-c8} 0 40 2 ld0 08C6C8D4-02 Primary 210100E08B3B58A4 {phys-bedge1-1-c6} 0 40 2 ld0 08C6C8D4-02 Primary 210100E08B3B8BA4 {phys-bedge1-1-c8} 0 40 2 ld0 08C6C8D4-02 Primary 210100E08B3B70A9 {phys-bedge1-2-c6} 0 40 2 ld0 08C6C8D4-02 Primary 210100E08B3BB4A2 {phys-bedge1-2-c8} [...] |
Save the configuration of the Sun StorEdge 3510 FC array using the firmware application “Saving Configuration (NVRAM) to a Disk” and the Configuration Service Console's “Save Configuration” utility.