Annex 1: Zoning with Brocade

In a Networked Storage environnement where all hosts and storage arrays are connected through a fabric, switch zoning becomes a critical task that ensures security by defining which ports may communicate together in the SAN. Every port connected to a SAN has a unique built-in address called WWN (World Wide Name) as similar to the MAC address for the NICs ports in some way, thus we can define for a specified port which other ports it can see by using their WWNs, this is called a soft zoning. A best practice deployment supposes that we have tow fabrics connected to storage and hosts, this will provide high availability in case of a switch failure, as a concequence the tow fabrics should have the same configuration including zoning. A multipathing software should also be installed on the hosts connected to the fabric, in the example we are dealing with, the windows host will see the same LUN two times, one from the storage controller A (SPA) through the switch A and the other from the controller B through the second switch. the multipathing product such as EMC Powerpath, dm-multipath for linux, RDAC & MPIO for AIX creates a logical device under /dev that will manage the available paths to reach the detected LUN usually from one path that you can read/write from. In case of a HBA or a switch failure, the multipathing software will fail back to an other available path in order to reach the same LUN again. In this article we will show, step by step, how to create a zone which includes Windows and Solaris hosts connected with a storage array. you will need to provide multipathing features and zone HBA ports with storage controllers accordingly.

1. Login to the Brocade switch

First of all, use a navigator and type the IP address of the SAN Brocade switch that you want to configure and enter the administrator credentials, you need java installed.

The first panel will guide you through the different administration/monitoring tasks that you may perform, actually we are interested with zoning the brocade, click on zone admin .

2. Locate your WWNs (You may need to retrieve WWNs form hosts to make correspondences, see Annex 2)
As a prerequisit, you have to know the WWN of each initiator and storage targets you want to zone together, please refer to this link to find out how to retreive them depending on the running operating system.

3. Create a zone
The zone we are creating will contain each ports wwn that should communicate together.

4. Add hosts ports and storage port to the zone

Select your previously created zone and add the portss wwns, we will focus on Windows and Solaris hostss ports (initiators) and the storage port (target).

5. Add the created zone to Zone Config

once you have created the zone, add it to a running zone configuration and enable it in order to make the switch aware of the changes.

6. Enable the configuration

7. Confirm

Best practices
Its not recommended to create such zone in a production environment,we want to make things easy but it will work for sure. the two hosts will never communicate together (they are initiators), they will initiate SCSI write/read commands to a storage port called target, thats why its better to create an (initiator-to-target) zoning this will ensure more flexibility during trablshooting.

Annex 2: find out the WWNN/WWNP of an HBA port 1. Using HBA software tools
You can use the following ways to view the WWN of each port:

HBAnyware (Emulex HBA only) SANsurfer utility (Qlogic HBA only)

Usually these tools are installed with the HBA driver the first time,tray to use command line interface this should work with all supported operating systems.

With HBAnyware

$ hbacmd listhbas
Manageable HBA List Port WWN : Node WWN : Fabric Name: Flags : Host Name : Mfg : Port WWN : Node WWN : Fabric Name: Flags : Host Name : Mfg : [ ..... ] For more details about speed, firmware version ... run: $ hbacmd HBAAttrib WWN $ hbacmd PortAttrib PWWN 10:00:00:00:c9:49:28:42 20:00:00:00:c9:49:28:42 10:00:00:60:69:80:2d:ee 8000f980 server01 Emulex Corporation 10:00:00:00:c9:49:28:47 20:00:00:00:c9:49:28:47 10:00:00:60:69:80:0e:fc 8000f980 fraudmgmt01 Emulex Corporation

With SANsurfer

# scli -i Host Name : sunserver HBA Model : QLE2462 HBA Alias : Port :1 Port Alias : Node Name : 20-00-00-1B-32-XX-XX-XX Port Name : 21-00-00-1B-32-XX-XX-XX Port ID : 11-22-33 Serial Number : AAAAAAA-bbbbbbbbbb Driver Version : qlc-20080514-2.28 FCode Version : 1.24 Firmware Version : 4.04.01 HBA Instance :2 OS Instance :2 HBA ID : 2-QLE2462

OptionROM BIOS Version : 1.24 OptionROM FCode Version : 1.24 OptionROM EFI Version : 1.08 OptionROM Firmware Version : 4.00.26 Actual Connection Mode : Point to Point Actual Data Rate : 2 Gbps PortType (Topology) : NPort Total Number of Devices : 2 HBA Status : Online

2. Linux
On a Linux or UNIX system WWNN and WWPN are recorded in the messages log file when HBA driver is loaded during boot process. To find WWNN/WWPN search messages file for HBA driver name or wwnn pattern: $ cat messages | grep -i wwnn May 17 15:24:19 sunserver1 qlc: [ID 657001 kern.info] Qlogic qlc(0) WWPN=210000e08b122275 : WWNN=200000e08b122275 May 17 15:24:21 sunserver1 qlc: [ID 657001 kern.info] Qlogic qlc(1) WWPN=210100e08b322275 : WWNN=200100e08b322275 May 17 15:24:32 sunserver1 qlc: [ID 657001 kern.info] Qlogic qlc(2) WWPN=210000e08b123372 : WWNN=200000e08b123372 May 17 15:24:33 sunserver1 qlc: [ID 657001 kern.info] Qlogic qlc(3) WWPN=210100e08b323372 : WWNN=200100e08b323372

3. AIX
Find the name of your fiber channel card: # lsdev -Ccadapter | grep fcs Then get the WWN (for fcs0 in this example): # lscfg -vp -l fcs0 | grep Network Address

4. Solaris 10
# prtconf -vp | grep wwn port-wwn: 2100001b.3202f94b node-wwn: 2000001b.3202f94b port-wwn: 210000e0.8b90e795 node-wwn: 200000e0.8b90e795

5. Windows
Install the Fiber Channel Information Tool from Microsoft Download Center and run the following on the command line: C:\>fcinfo There are 2 adapters: com.qlogic-QLA2300/2310-0: PortWWN: 21:00:00:e0:8b:08:95:df \\.\Scsi2: com.emulex-LP9002-1: PortWWN: 10:00:00:00:c9:30:d0:17 \\.\Scsi3: