Professional Documents
Culture Documents
Version v1.0
Page 2
Table of Contents
Changes & Approval ............................................................................................................................. 2 Table of Contents ................................................................................................................................. 2 Purpose ................................................................................................................................................ 3 Applies to ............................................................................................................................................. 3 Frequency............................................................................................................................................. 3 Expected Outcome ............................................................................................................................... 3 Scope .................................................................................................................................................... 3 Responsibilities .................................................................................................................................... 3 Deviations from EDB standard ............................................................................................................. 4 Prerequisities ....................................................................................................................................... 4 References............................................................................................................................................ 4 Procedure ............................................................................................................................................. 4
Step 1 Log on to the mgmnt server .............................................................................................................. 4 Step 2 CISCO Fabric Manager ....................................................................................................................... 4 Step 3 Log on to FM ...................................................................................................................................... 5 Step 4 Zoning (Creating the alias and checking the prerequisites) .............................................................. 6 Step 5 Zoning (Creating the Zone) ..............................................................................................................11
Version v1.0
Page 3
Purpose
How to configure the zones in a CISCO SAN.
Applies to
Servers that are connected with FibreChannel from their own HBA adapters to a SAN switch.
Frequency
This SOP shall be used every time a new physical server is connected with FC and SAN.
Expected Outcome
Fully functional SAN disks attached to the requested server.
Scope
Describe the scope of this SOP.
Responsibilities
The server team (i.e Windows, Open, VMWare) order SAN disk to a specified server by filling out a form at the Backup & Storage web portal located at: http://orebro.os.edb.se/leveransgrupper/backup_and_storage/ An email with the order is sent to the EDB Helpdesk who is creating a request. This request is assigned to the Backup & Storage team. The IPC at Backup & Storage check and validate the request and assign it to a technician for handling. Configuration in the SAN (i.e zoning) is made before the SAN disks is assigned according to the order to the specific server by the Storage technician and notify the person responsible for the order (contact person). The contact need to verify the disk and give OK to close the request in Service Center.
Version v1.0
Page 4
Prerequisities
That the order is complete with all the necessary information requested. That there is a personal account created at the management server and Fabric Manager and the switches.
References
List any references to other documents, routines, etc. Reference Name Description
Procedure
Describe the steps required to perform this SOP.
Version v1.0
Page 5
Step 3 Log on to FM
Log on to Fabric Manager
Check both the core directors (TOM-CPU1 & TOM-CPU2) and click Open
Version v1.0
Page 6
Enter the servername in the Description field, change the VSAN to VSAN 2, change the status to Admin UP. Click Apply If everything is OK you will see a WWN logged in if you go to the FLOGI tab. This WWN shall match one of the WWNs included in the Excel sheet. Click Close and choose to save the configuration!
Version v1.0
Page 7
Wait until Discovery success is displayed down at the left corner in the new window. Scroll down to the FC-aliases and expand it.
Version v1.0
Page 8
In the Name: field, enter the server name (specified in the SC order) in lower case In the Port WWN: field, enter the first of the two WWNs (specified in the SC order) Click OK
Version v1.0
Page 9
Click Cancel Right click the created server alias and choose Insert
In the Port Name: field enter the second WWN and click Add
Version v1.0
Page 10
Click Close Now we check the alias with the 2 WWN entrys. The one with a blank Switch Interface is not logged in and belong to the second fabric and shall be removed!
Version v1.0
Page 11
Important! If none of the WWNs are logged in you need to contact the person listed as contact in the SC case and inform him/her that we cant see any logged in WWNs. Always use the matching pair of storage ports, ex: CL4-A belongs to CL3-A. You can verify that by looking at which blade and port in the director the storage ports are connected to, for instance fc6/29. That shall be equal for both storage ports!
Version v1.0
Page 12
In the Zone Name: field enter the servername same as the alias name (also here in lower case letters)
Version v1.0
Page 13
In the Port Name: field insert the WWN that did NOT log in (was blank and removed) during the step when the alias was created and then click Add
From the drop down menu, choose All Targets and click Filter
Next step is to choose a suitable storage port. Important! Choose a storage port that is least used. A good rule is that we never have more than 15 hosts per storage port. This can differ, for instance a VMWare ESX server with lots of virtual clients cant be counted as 1 server. Also choose a storage port belonging to storage in the SAME location (ie if the client is in CPU1, the storage shall also be located in CPU1)
Version v1.0
Page 14
Reference Table for storage ports mapped to which storage HDS18801-CL1N - USP-V in Tomteboda, CPU2 HDS20013-CL1A - VSP1 in Tomteboda, CPU2 HDS20621-CL1B VSP2 in Tomteboda, CPU1 HDS28735-CL1B - USP-V in Tomteboda, CPU1 HDS35903-CL1A - USP-VM in Stra Explanation: The first is telling you which storage the other tells you what storage port (like CL1-B) So, now again after this explanation, it is time to choose a suitable storage port. Since my server is located in Tomteboda CPU1 I look for a storage port in VSP2
Choose the port and click Add to Zone Check the occupancy of the port by right click in the column All Zone Membership, choose Chow Details, and choose All Rows
As you see, this storage port only contains this server as for now so this one we can use. A good rule is to not have more than 15 hosts per storage port! Be sure to NEVER use a storage port that is used by the storage itself!
Version v1.0
Page 15
Locate your zone and mark ONLY that one (if there are more zones to choose from), click Add
Version v1.0
Page 16
Click on Activate
Click on Ja
Check if this is the changes that you configured and click Close
Version v1.0
Page 17
If the suggested changes are what you configured, click Continue Activation
Version v1.0
Page 18
Version v1.0
Page 19
Important! You need to choose the exact matching sister storage port. You know this by checking the switch port, in this example its fc9/1 (meaning blade 9 port 1). In the other fabric you will look for the same blade switch port and that storage port will probably be called HDS20621-CL2C
When you done all the steps on this fabric as well the switch configuration is finished and you can go ahead add the host and attach the disk/disks to it from the Device Manager GUI.