How to do zoning on CISCO MDS SAN switches using Command Line Interface (CLI)

How to do zoning on CISCO MDS SAN switches using Command Line Interface (CLI)

In this step by step example to demonstrate How to do zoning on CISCO MDS SAN switches using Command Line Interface (CLI), port 1/24 will be used for server connection and port 2/24 for array port connection. VSAN 100 will be used as the production VSAN. Replace these values to reflect your environment and the follow the naming guidelines you may have for device alias, zone and zoneset at your site.

Connect to the switch using ssh/telnet

1.      Change into configuration mode

config t

2.      Check the vsan database and confirm if the interface is in part of the VSAN

show flogi database int fc1/24

show flogi database int fc2/24

3.      Add the ports into the VSAN if it is not in the database

vsan database

vsan 100 interface fc1/24

vsan 100 interface fc2/24

exit

4.      Create device alias for the interfaces

device-alias database

device-alias name TESTSERVER_hba0 pwwn xx:xx:xx:xx:xx:xx:xx:xx (WWN from interface 1/24)

device-alias name TESTARRAY_port0 pwwn xx:xx:xx:xx:xx:xx:xx:xx (WWN from interface 2/24)

5.      Check that the alias is in pending state to be added

do show device-alias pending-diff

 

6.      Commit device-alias changes

device-alias commit

exit

 

7.      Add a name/ description and enable the ports

int fc1/24

no shut

switchport description TESTSERVER_hba0

int fc2/24

no shut

switchport description TESTARRAY_p0

exit

8.      Create zone

zone name TESTSERVER_hba0_TESTARRAY_p0 vsan 100

member devicealias TESTSERVER_hba0

member devicealias TESTARRAY_p0

exit

9.      Check Active zoneset

show zoneset active

10.   Backup current zoneset (assuming current zoneset is TESTZONESET_Active)

zoneset clone TESTZONESET_Active TESTZONESET_Backup.<Date>  vsan 100

11.    Add new zone member to zoneset

zoneset name TESTZONESET_Active vsan 100

member TESTSERVER_hba0_TESTARRAY_p0

exit

12.    Verify that the zoneset is fully populated

do show zoneset brief vsan 100

13.   Activate zoneset

zoneset activate name TESTZONESET_Active vsan 100

exit

14.   Verify zone activation status

show zone status vsan 100

15.   Ensure that the new zone is part of the active zoneset

show zone name TESTSERVER_hba0_TESTARRAY_p0 active vsan 100

16.   Copy the running config to the startup config

copy run start                                                                               

17.   Repeat the above steps  Fabric B

This concludes the step by step procedure to do zoning on CISCO MDS SAN switches using Command Line Interface (CLI)

 

How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches

How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches

Large Mainframe environments may have requirements for installing multiple CISCO MDS SAN switches to accommodate the port capacity requirements. Alternatively, there may be requirements to extend the ISLs to a second site for disaster recovery purposes. In these cases, it may be required to create VSANs across multiple switches. Mainframe FICON VSANs have special configuration requirements to establish inter VSAN communication. Following the steps below you can create a FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches.

This post assumes that the protocol or communication is FC and the fiber patch leads are available for attachment to the switch ports. Any work required to complete the connectivity between the switches whether it is cabling or establishing a DWDM link to another site must be taken care prior to attempting the steps below.

The following example configuration will be using “switch_1” port 1/1 and “switch_2” 1/1 for establishing the ISLs and configuring FICON VSAN “101”.

1.      Login to switch_1 and disable switch port 1/1

config t

interface fc1/1

shut

exit

2.      Move port 1/1 to VSAN 1. The physical ISL port must be in VSAN 1. VSAN 101 is going to be created using the ISL links which are in the default VSAN – VSAN1.

 

3.      Set the switch port rate mode, trunk mode and name the port

config t

interface fc1/1

switchport rate mode dedicated

switchport trunk mode on

switchport description ISL_to_switch_2

 

4.      Connect the FC cable to switch port 1/1

5.      Repeat steps 1 to 4 on switch_2

6.      Enable port 1/1 on switch_1

config t

interface fc1/1

no shut

exit

 

7.      Repeat step 6 on switch_2

8.      Create VSAN 101 on switch_1

config t

vsan database

vsan 101

exit

9.      Set static FC domain ID for VSAN 101. Example below uses DID 101. Ensure that the DID is unique in the fabric and is not used elsewhere. Static domain IDs are required for FICON VSAN

 

config t

fcdomain domain 101 static vsan 101

fcdomain restart disruptive vsan 101

exit

10.   Set the load balancing for VSAN 101 to “src-dst-id”, mandatory for enabling FICON VSAN feature

config t

vsan database

vsan 101 loadbalancing src-dst-id

exit

11.   Set the “in-order-gurantee”  for VSAN 101 required for FICON VSANs

config t

In-order-gurantee vsan 101

exit

12.   Enable fabric binding for VSAN 101, mandatory for enabling FICON VSAN feature

config t

fabric-binding activate vsan 101

exit

13.   Now enable FICON protocol on VSAN 101

config t

ficon vsan 101

exit

14.   Repeat steps 8 to 13 on switch_2. Use the same VSAN ID as switch_1 (101) and different domain ID (102) (unique in the fabric) for switch_2

 

15.   Identify the switch wwn of switch_1

show wwn switch

16.   Repeat step 15 on switch_2

17.   Update fabric binding in switch_1 to include the remote switch WWN

config t

fabric-binding database vsan 101

swwn <wwn of remote switch> domain 102 (this is the domain ID of remote switch)

fabric-binding database activate vsan 101

18.   Repeat steps 17 on switch_2, use the swwn and domain id of switch_1

19.   Suspend and restart VSAN 101 on switch_1

config t

vsan database

suspend vsan 101

no suspend vsan 101

exit

 

20.   Repeat step 19 on switch_2

21.   Check and confirm VSAN 101 is spanning across sites

fcdomain vsan 101

22.   Copy running configuration to startup configuration on switch_1

copy run start

23.   Repeat step 22 on switch_2

This concludes the procedure How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches

How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches

How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches

How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches
How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches
How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches
How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches
How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches
How to Create FICON VSAN across Inter Switch Links (ISL) on CISCO MDS SAN switches

How to Virtualize EMC DMX-4 Storage Array with HP P9500 or HDS VSP

How to Virtualise EMC DMX-4 Storage Array behind HP P9500 or HDS VSP storage arrays.

This article explains the configuration requirements and steps involved in virtualising a DMX storage array behind HP P9500. As you may be aware the HP P9500 is a rebadged HDS VSP storage array. Therefore the steps are identical whether you are using HDS VSP or HP P9500. This article assumes that you are a storage administrator/designer who has worked with both EMC and HP/HDS storage arrays and are familiar with the terminology.

1.      Create a Cache Logical Partition (CLPR) of 4GB within the HP P9500/VSP.

The CLPR license is bundled with the base license. You can create up to 32 CLPRs without purchasing any additional license

It is recommended to use a dedicated CLPR for every external array that will be virtualized with P9500/VSP

2.      Identify the CHA ports on the P9500 that will be used as “external” ports. You will need a minimum of two front end ports, one from each cluster. In this example, I use 5E (fabric A) and 6E (fabric B)

3.      You may connect the P9500 ports directly to the DMX FA ports or using fabric switches. This example assumes that a fabric switch is being used. Set the external port properties as below.

Port Mode : External

Speed : 8Gbps (assuming your fabric switch supports this, if not set to match the switch port speed)

4.      Ensure that the P9500/VSP external ports are connected to the same fabric where the EMC FAs are connected. In this example I am using FA ports 7A0, 7A1 connected fabric A and 10A0, 10A1 connected fabric B

5.      Zone in P9500/VSP external ports to the EMC  FA ports identified

The zones will look like this

Fabric A

P9500_5E to DMX_7A0

P9500_5E to DMX_7A1

Fabric B

P9500_6E to DMX_10A0

P9500_6E to DMX_10A1

6.      Register the WWPNS of the P9500/VSP ports 5E and 6E on the corresponding DMX FA ports. Set the below port attributes for P9500 WWPNs on the DMX

Parameter                          Parameter setting

SC3 flag                              Enable

SPC2 flag                            Disable

7.      Create a 10GB (or any size) test LUN on the DMX-4

8.      Assign the test LUNs to P9500 WWPNs on FA ports 7A0,7A1 and 10A1 and 10B1

9.      On the P9500, In Remote Web Console, select Add External Volumes from the General Tasks menu and

display the Add External Volumes window.

10.    To create a new path group and add external volumes, select By “New External Path Group”

and click “Create External Path Group”, and then create a path group.

11.    To add external volumes to the existing external path group, select By Existing External Path

Group, and select the desired path group from the Available External Path Groups list. Click Next.

12.    Select external volumes from the Discovered External Volumes list and enter the external volume

group number and their sequential number in the Initial Parity Group ID box, and then click

Add. Select whether to create LDEVs in the external volume in Allow Simultaneous Creation of LDEVs.

If you want to take over the data of the external volume when you create LDEVs, select Yes in

Use External Storage System Configuration, and then enter an LDEV name in the LDEV Name

box. If you do not want to take over the data, select No in Use External Storage System

Configuration, and then enter an LDEV name in the LDEV Name box.You can

also set the attribute of the external volume by clicking Options.

Select the following options

CLPR : 1

Path mode : multi (This the multipathing policy for DMX arrays. IOS to the backend will be round robined)

Emulation :Open V

Cache mode : disable (IOs will be synchronously written to the DMX. In other words, the server will not be acknowledged until the IO hits the DMX cache and DMX acknowledges that data is safe)

Inflow control : disable (This setting controls the IO on the front end CHA port when there is an issue with the external storage system)

External Group Name: Exxxx (Select an External group name. This is similar to the Parity Group number in internal LUNs. If you have multiple external arrays, keep all the LUNs from one array under the same Ex group number or develop a standard suitable for your environment that will help you identify the LUNs in the future.)

Select the CU where the external LUN will be place and the LDEV number.

Click Finish to display the Confirm window.

13.   Procees with LUN mapping to the front end CHA port as required.

Any issues/questions/concerns please post here or email me. I may be able to help.

Have fun virtualizing EMC DMX-4 Storage Array behind HP P9500 or HDS VSP storage arrays!

How to create SRDF pairs between two EMC symmetrix VMAX storage arrays

How to create SRDF pairs between two EMC symmetrix VMAX storage arrays


This article provides step by step configuration procedure to create SRDF pairs between two EMC symmetrix storage arrays. 


1. Establish the replication link between the production site (source) and dr site (destination). The EMC symmetrix VMAX supports GigE RAs that can be used to configure FCIP between two sites. The other alterbatives are DWDM (FC) or use third party solutions such as Brocade 7800s to establish the connectivity between the sites. Click here to find the procedure for configuring FCIP using Brocade san switches.


2. Create an RDF group between two sites. To create RDF group 'testrdfg' with group id 3 and RDF directors 7G between symmetrix id 089 (prod site) and 099 (dr site), execute the command below


symrdf addgrp -label testrg -rdfg 03 -sid 089 -dir 7g -remote_rdfg 03 -remote_sid 099 -remote_dir 7g -gige 


3. Create a text file on the management server as below with a list of source devices against the destination devices. 


In the example, we will be creating an RDF pair from source device 045C on symmetrix id 089 to destination device 0285 on symmetrix id 099. So the text file will look like this


# cat pair.txt
045C         0285


045C and 0285 should have identical device characteristics. For example, if 045C is a striped meta device with 4 hypers of 60GB, then 0285 must be a striped meta of the same size. Click here for the procedure to create and expand striped meta devices. 


4. Create the pair between the source and target devices using the above text file. The command below will create pair between the devices mentioned in the text file from source array 089 using rdf group 3. rdf group 3 is already configured between Sym ID 089 and 099. So the command will pick the destination device 0285 from Sym ID 099 based on the relationship defined in rdfg 3. The commad will create the pairs in Adaptive copy mode. 



symrdf -file pair.txt -sid 089 -rdfg 3 createpair -type RDF1 -invalidate r2 -rdf_mode acp
_disk 


5. Check the status of the pair. You will see suspended status.


symrdf -file pair.txt  -rdfg 3 query -sid 089


6. Start the synchronization of the pairs. Once the below command is completed, execute command in step 5 to verify the status.


symrdf -file pair.txt  -rdfg 2 esta -sid 089


7. Switch the SRDF mode of operation from adaptive copy to Aysnc or sync, depending on the requirements. It is recommended to wait until the pairs are in sync in adaptive copy mode before switching the mode. There are also other caveats in configuring SRDF/A or SRDF/S which I will explain in another post.


symrdf -file pair.txt -rdfg 2 set mode async (or sync)


8. You could also create a disk group and add all source devices into it and then manage the pairs using the dg name. For example, the below commands create 'pair_dg' and add device 045C into it.


symdg create pair_dg -sid 089 -type RDF1
symld -g pair_dg add dev 045C -sid 089


9. Once the dg is created, use the dg name instead of the file name to query the pair status


symrdf -g pair_dg query -sid 089


Please note that you could have as many devices as you wish in the pair.txt file before issuing create device. You should also take precaution and necessary checks to make sure that the R2 devices on the destination array is not in use.


Enjoy!

How to migrate EMC Symmetrix LUNs non disruptively to another tier using symcli command symmigrate

How to migrate EMC Symmetrix LUNs non disruptively to another tier using symmigrate command

 

EMC Symmetrix Virtual LUN technology enables transparent, non disruptive data migration among storage tiers within the array and between RAID protection schemes without impacting local or remote replication. You can migrate data to unconfigured space or configured space.

Solutions Enabler 7.0 introduced a new symcli command symmigrate. Follwoing example use symmigrate command to non disruptively migrate an EMC LUN to another tier.

 

In this example, EMC symmetrix device 105e is a 30GB concatenated meta device in tier 1. This device needs to be migrated to tier 3. Given below are the step by step tasks to perform this migration

 

Create a concatenated meta device in the target tier (tier 3) of 30GB. Click here to find out the procedure for creating concatenated meta device. For this example we will use 27F7 which is a concatenated meta device in Tier 3 disk group.

 

Create a device file with source and destination devices. In this example I have created ‘migdevice.txt’. The content of the file is listed below. It is not necessary to create a text file, the symmigrate command can be used to migrate all devices in a device group or storage group.

# cat migdevice.txt

105e 27F7

 

Before performing the migration, run symmigrate command in validate mode to make sure that a migration can be completed with the source and target devices mentioned in the configuration file. You can name the migration session so that it is easy to identify and manage later.

#symmigrate -name testmig -sid 8899 -f migdevice.txt validate –v

 

Once the validate operation is completed successfully, the migration session can be established

#symmigrate -name testmig -sid 8899 -f migdevice.txt establish -v

 

Check the progress of the migration using the below command. Wait until the the status changes to “migrated”

#symmigrate -name testmig -sid 8899 query -detail -i 10

 

List the devices and make sure that the storage tier has changed

#symdev show 105E

 

This device will be showing the original disk group of 27F7

#symdev show 27F7

 

This device will be showing the disk group of the original 105E. Basically they would have swapped the disk groups.

 

Once the migration is completed, the session can be removed or terminated. The terminate operation removes the migration session named “testmig”

#symmigrate -name testmig -sid 8899 verify -migrated

#symmigrate -name testmig -sid 8899 terminate

 

All done!