The following are some of the principles used in creating zones and zone sets:
Each Fabric will have one zone set named AMER_SAN_A or AMER_SAN_B.
All zones are created based on WWN's.
Each cluster will have a separate zone in each Fabric and will consist of WWN's of HBA's of both cluster nodes and corresponding Minnows.
All zones are named with following naming convention:
instance_zone_fabric
For example cluster 1 will have 2 zones one in each fabric named edge1_zone_A and edge1_zone_B. The following table lists all of the zone names and the zone members.
Zone Set |
Zone Name |
Members |
Storage Channels |
---|---|---|---|
SAN-A |
edge1_zone_A |
phys-bedge1–1phys-bedge1–2 |
amer-minnow-01 chl0, chl1amer-minnow-02 chl0, chl1 |
edge2_zone_A |
phys-bedge2–1phys-bedge2–2 |
amer-minnow-03 chl0, chl1amer-minnow-04 chl0, chl1 |
|
edge3_zone_A |
phys-bedge3–1phys-bedge3–2 |
amer-minnow-05 chl0, chl1amer-minnow-06 chl0, chl1 |
|
edge4_zone_A |
phys-bedge4–1phys-bedge4–2 |
amer-minnow-01, 02, 03, 04 chl0amer-minnow-05, 06 chl0, chl1 |
|
edge5_zone_A |
phys-bedge5–1phys-bedge5–2 |
amer-minnow-01 chl0, chl1amer-minnow-02 chl0, chl1 |
|
backup_zone_A |
bu-amer-01all cluster nodes |
amer-minnow-01, 02, 03, 04, 05, 06 |
|
SAN-B |
edge1_zone_B |
phys-bedge1–1phys-bedge1–2 |
amer-minnow-01 chl4, chl5amer-minnow-02 chl4, chl5 |
edge2_zone_B |
phys-bedge2–1phys-bedge2–2 |
amer-minnow-03 chl4, chl5amer-minnow-04 chl4, chl5 |
|
edge3_zone_B |
phys-bedge3–1phys-bedge3–2 |
amer-minnow-05 chl4, chl5amer-minnow-06 chl4, chl5 |
|
edge4_zone_B |
phys-bedge4–1phys-bedge4–2 |
amer-minnow-01, 02, 03, 04 chl4 amer-minnow-05, 06 chl4, chl5 |
|
edge5_zone_B |
phys-bedgephys-bedge |
amer-minnow- chl4, chl5amer-minnow- chl4, chl5 |
|
backup_zone_B |
bu-amer-01all cluster nodes |
amer-minnow-01, 02, 03, 04, 05, 06 |
Obtain the hbamap script and the Solaris Device Path Decoder from your Sun representative. The hbamap script will gather the output of the HBA's WWNs.
Copy hbmap to cluster node and run the script:
root@phys-bedge2-1:# /var/tmp/hbamap FOUND PATH TO 6 LEADVILLE HBA PORTS =================================== C# INST PORT WWN MODEL FCODE STATUS DEVICE PATH ------------------------------------------------ c3 qlc0 210000e08b1b08a6 ISP2312 1.14.09 NOT CONNECTED /pci@1c,600000/SUNW,qlc@1 c4 qlc1 210100e08b3b08a6 ISP2312 1.14.09 CONNECTED /pci@1c,600000/SUNW,qlc@1,1 c5 qlc2 210000e08b1b8ba3 ISP2312 1.14.09 CONNECTED /pci@1d,700000/SUNW,qlc@1 c6 qlc3 210100e08b3b8ba3 ISP2312 1.14.09 CONNECTED /pci@1d,700000/SUNW,qlc@1,1 c7 qlc4 210000e08b1bc5a4 ISP2312 1.14.09 NOT CONNECTED /pci@1d,700000/SUNW,qlc@2 c8 qlc5 210100e08b3bc5a4 ISP2312 1.14.09 CONNECTED /pci@1d,700000/SUNW,qlc@2,1 |
Map the controller with the slot number on the V440 system boards using the Solaris Device Path Decoder. For example:
/devices/pci@1c,600000/SUNW,qlc@1/fp@0,0:devctl : PCI Slot 5 Port 0 /devices/pci@1c,600000/SUNW,qlc@1,1/fp@0,0:devctl : PCI Slot 5 Port 1 /devices/pci@1d,700000/SUNW,qlc@1/fp@0,0:devctl : PCI Slot 4 Port 0 /devices/pci@1d,700000/SUNW,qlc@1,1/fp@0,0:devctl : PCI Slot 4 Port 1 /devices/pci@1d,700000/SUNW,qlc@2/fp@0,0:devctl : PCI Slot 2 Port 0 /devices/pci@1d,700000/SUNW,qlc@2,1/fp@0,0:devctl : PCI Slot 2 Port 1 |
Login to the management station and launch a web browser. You may need to download and install one first.
In the URL field, enter the switch name and log in using the following credentials:
Login: Administrator
Password: password (default is password)
Go to Configure->Zoneset and change the Zoneset name.
Go to Zones tab and create zones by entering a zone name and clicking on Add Zones.
Click on a zone name which will bring up another window where you can enter WWNs and add them to zones. The WWNs must be entered in mac address form, for example 210000e08b1b08a6 should be entered as 21:00:00:e0:8b:1b:08:a6.
After entering all of the WWNs, go back to the Zoneset tab and click on Save and Activate Zoneset information. This will force update on the zones to all switches in the fabric and should then be visible in the Solaris operating system.