Scribd
Upload
119 views3 pages

Create Zone On The SAN Switch

This document provides instructions for connecting targets and initiators to SAN switches by creating device aliases, zones, and zone sets on the switches. It describes establishing physical connectivity between core/edge switches and storage/server ports, and outlines best practices for naming devices, zones, and zone sets. The step-by-step procedure explains how to check port links, log in to switches, create device aliases and zones, commit changes, and activate zone sets.

Uploaded by

संतोष शर्मा
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
119 views3 pages

Create Zone On The SAN Switch

This document provides instructions for connecting targets and initiators to SAN switches by creating device aliases, zones, and zone sets on the switches. It describes establishing physical connectivity between core/edge switches and storage/server ports, and outlines best practices for naming devices, zones, and zone sets. The step-by-step procedure explains how to check port links, log in to switches, create device aliases and zones, commit changes, and activate zone sets.

Uploaded by

संतोष शर्मा
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Create Zone on the SAN Switch

April 20

2012

This procedure will talk about how to connect the target(s)/initiator(s) to the SAN switches.

Author: Nilesh Nigam Contact: 8860079662

Description: 1. This procedure will talk about how to connect the target(s)/initiator(s) to the SAN switches. 2. This procedure can be used for creating device-alias for the initiator(s)/target(s) on the SAN switches. 3. This procedure can be used for creating the zones on the SAN Switches.

Consideration to be made before or while running this procedure: 1. Always establish connectivity between core switch ports and storage/Target ports and between Server/Initiator ports and Edge switch ports. 2. While establishing the physical link between the target(s)/initiator(s) and the SAN Switches, ensure that the links are routed to two fabrics, basis on the following standards, like: Initiator port(s) P1 will be routed to Edge switch-1 and Initiator port(s) P2 will be routed to Edge switch-2 and Target port(s) Odd numbered will be routed to Core switch-1 and Target port(s) Even numbered will be routed to Core switch-2. 3. Ensure the Target and Initiator port(s) optimal status, If not the case log a case with the respective OEM to replace it. 4. Test and ensure the FC cable(s) optimal status. 5. Always use the standard nomenclatures for the device-alias to be created, described as follows: For initiator port use Server name_HBAx_Px (substitute the number in the place of x) and for target port use Storage name_FAxyz (substitute the FA number eg. 8A0 in the place of xyz). 6. Name the zone as follows: Z_Server name_HBAx_Px_Storage name_FAxyz. 7. A note of caution while creating the device-alias, Be Careful and Do NOT alias a device wrongly. 8. Enable logging on the putty session before running any commands. 9. Create individual zone for every set of initiator and target. 10. Physical connectivity for both fabrics has to be similar eg. On fabric 1, host 1 is connected to port 5 & 6; on fabric 2 use the same ports for the host 1 connectivity. 11. Keep the switch(s) log-in credentials ready with you. 12. It is always recommended to keep a copy of the configuration backup before modifying the configuration on the switch. 13. Use the tab button key to auto complete the command and to search the available commands while logged-in to the switches. 14. Ensure the optimal health status of the switches before performing any configuration changes. Step-by-Step Procedure: 1. Check the link on the SAN switch port(s) which are connected to target/initiator port(s), it should be lid-up in green. 2. Log in to the core switches on at a time using the SSH. 3. Change the switch mode to configure, Use: # configure t 4. Create device-alias for the connected devices on each of the core switches, Use: # device-alias name <ALIAS NAME> pwwn <WWPN> # device-alias commit

5. To display the newly created alias, run: # show device-alias database 6. Create the zone between the initiator and target which needs to talk to each other, Use: # zone name <ZONE NAME> vsan <VSAN NUMBER> ; 7. Add the 1st member to the zone, Use: # zone name <ZONE NAME> vsan <VSAN NUMBER> ; member device-alias <DEVICE ALIAS> 8. Add the 2nd member to the zone, Use: # zone name <ZONE NAME> vsan <VSAN NUMBER> ; member device-alias <DEVICE ALIAS> 9. Commit the zone for it to be saved in the zone database, Run: # zone commit vsan <VSAN NUMBER> 10. Add the newly created zone(s) to the active zoneset and activate it, Use: # zoneset name <ZONESET NAME> vsan <VSAN NUMBER>; member <ZONE NAME> # zoneset activate name <ZONESET NAME> vsan <VSAN NUMBER> 11. To display the zoneset details, Run: # show zoneset active 12. Copy the running configuration to startup configuration, Use: # copy running-configuration startup-configuration

You might also like