Deploying SANTap - RecoverPoint Implementation Lab 3.3

Part 2: Deploying SANTap

Step Action

1 Log in to the switch as admin and copy the running configuration to an ftp site. Command Syntax:

copy run ftp://root@<IP Address>/<directory>/<filename>

Important: Configuration changes on the switch should only be performed by one user at a time. Each workgroup should coordinate switch configurations to ensure only one user is changing a configuration. Before changing the switch configuration, each group should backup the existing configuration on their first assigned switch. In a customer environment you would perform a backup of all switches in the environment.

2 Configure the SSM for SANTap. Log into the switch as admin and use the show module command to identify the slot number of the SSM module. You will need this number to perform several of the SANTap configuration commands. This number may be different on each switch in your environment.

Command Example: mds# show module

Step Action

3 Verify the license using the show license command. Command Example:

mds# show license

Show License – Output Example

4 At the switch prompt, enter the configuration terminal using the conf t command. Then, enable the SANTap service on the SSM module using the ssm enable feature command. Command Syntax:

mds(config)# ssm enable feature santap module <SSM#>

Note: This step is performed once per switch. You do not need to run this step if SANTap was previously enabled by another lab group (see example below).

Failed Message When SANTap is Currently Enabled – Command Example

Note: You will need a front end VSAN for your host initiator (HBA) and a backend VSAN for your storage target and RPA entities. A VSAN containing the host, RPAs, and storage target should already exist from your kdriver implementation. Keep this VSAN and use it as your back end VSAN. You will need to create a new VSAN for the front end VSAN. You will create a DVT for the front end VSAN and move the host port from the back end to the front end VSAN. Follow the steps below.

Step Action

5 At the switch prompt, enter the configuration terminal (if not already at the config prompt) using the conf t command. Then enter the VSAN database using the command vsan

database. Create the front end VSAN using the vsan command (see example below).

Assign the VSAN a number and a name. To prevent conflicts with other lab groups, assign a number to your front end VSAN which is ten higher than your back end VSAN. For example, if you back end VSAN is 5 make your front end VSAN 15.

Command Syntax: mds# conf t

mds(config)# vsan database

mds(config-vsan-db)# vsan <FrontEndVSAN#> name <VSAN Name> mds(config-vsan-db)# exit

Creating the Front End VSAN – Command Examples

Note: In later steps you will create the DVT and the host to storage zone in the front end

VSAN and move the host port into the front end VSAN.

6 From the config prompt, create the CVT in the back end VSAN. You will need to

designate the SSM module number, your back end VSAN number, and designate a name for the CVT.

Important: The CVT must be created in the back end VSAN. Do not create the CVT in the front end VSAN that you created in the previous step.

Command Syntax:

santap module <SSM#> appl-vsan <BackEndVSAN#> cvt-name <CVT Name>

Command Example:

Step Action

7 Verify the CVT was created correctly. You should see 10 Cisco PWWNs. Under the ―Type‖ column you should see 9 of the PWWNs listed as ―init‖ (initiator) and 1 listed as ―target‖. In a later step you will need to add the CVT to a zone. You must include all 10 of the PWWNs.

Command Syntax:

<do> show fcns database vsan <BackEndVSAN#>

Note: Add ‗do‘ to the front of a show command if you are at the ―config‖ prompt. Command Example

mds(config)# do show fcns database vsan 5

Finding the CVT in the Back End VSAN – Output Example

Set Persistent FCIDs (IBM AIX and HP-UX)

Setting persistent FCIDs must be done for IBM AIX and HP-UX. However, you can

perform these steps for any platform. If your lab environment does not contain IBM AIX or HP-UX you may skip this section and proceed with the next section Create the DVT.

Step Action

8 Determine the domain ID for the back end VSAN. Command Syntax:

show fcdomain domain-list vsan <BackEndVSAN#>

Command Example:

mds# show fcdomain domain-list vsan 5

show fcdomain Output Example

Note: Use the decimal Domain ID number.

9 From the config prompt, set the domain ID for the front end VSAN to be identical to that of the back end VSAN.

Command Syntax:

mds(config)# fcdomain domain <domainID> static vsan

<FrontEndVSAN#>

Command Example:

mds(config)# fcdomain domain 8 static vsan 15

10 From the config prompt, restart the front end VSAN. Command Syntax:

mds(config)# fcdomain restart disruptive vsan

<FrontEndVSAN#>

Command Example:

Step Action

11 From the config prompt, enable the persistent FCID. Command Syntax:

mds(config)# fcdomain fcid persistent vsan <FrontEndVSAN#> Command Example:

mds(config)# fcdomain fcid persistent vsan 15

Note: The switch should respond: FCID persistent feature is enabled

12 From the config-fcid-db prompt, make the FCID of the storage target port the same in the front end VSAN as in the back end VSAN. Use the show fcns database command to identify the Storage target port FCID.

Displaying the Storage Port FCID

Command Syntax:

mds(config)# fcdomain fcid database

mds(config-fcid-db)# vsan <FrontEndVSAN#> wwn <StoragePort

WWN> fcid <StoragePort FCID> dynamic

Command Example:

mds(config)# fcdomain fcid database

mds(config-fcid-db)# vsan 15 wwn 50:06:04:8a:ca:fe:64:13 fcid

0xa100c dynamic

13 Copy the running configuration to the startup configuration. Command Example:

From the switch prompt run: copy run start From the config prompt run: do copy run start

Step Action

14 Create the DVT. Each physical storage target port requires a corresponding DVT. The DVT and the storage target port will have the same PWWN (target-pwwn). The DVT resides in the front end VSAN (dvt-vsan) and the physical storage target port resides in the back end VSAN (target-vsan). In the lab configuration, the physical storage target port should already be in the back end VSAN. Creating the DVT is performed from the ―config‖ prompt. If you are not already at the config prompt enter the configuration terminal using the conf t command.

Command Syntax:

santap module <SSM#> dvt target-pwwn <StoragePort WWN> target-vsan <BackEndVSAN#> dvt-name <name> dvt-vsan <FrontEndVSAN#> lun-size-handling 1

Command Example:

mds(config)# santap module 2 dvt target-pwwn

50:06:01:60:10:60:1a:9c target-vsan 5 dvt-name Group_5_DVT dvt-vsan 15 lun-size-handling 1

15 Verify that the DVT was created properly. The command to display the DVT will show all DVTs configured. You may need to scroll through the output to find your DVT.

Command Syntax:

<do> show santap module <SSN#> dvt

Command Example

mds(config)# do show santap module 2 dvt

Step Action

16 Copy the running configuration to the startup configuration. Command Example:

From the switch prompt run: copy run start From the config prompt run: do copy run start

Creating the Front End Zoneset and Moving the Host Port

The VSAN you designated as the back-end VSAN should already contain a Host to Storage zone with the PWWNs of the host initiator port(s) and the storage target port(s). This zone must be recreated in the front end VSAN using the same PWWNs. The DVT and the physical storage target port have the same PWWN. The DVT is in the front end VSAN and the physical target is in the back end VSAN. The physical host initiator and the virtual host initiator (VI) also have the same PWWN. The physical host initiator will reside in the front end VSAN and the VI will be automatically created in the back end VSAN. Currently, the physical host initiator is logged into the back end VSAN. You will move it to the front end in a later step.

17 Display the active zone set in the back end VSAN. This will allow you to verify the PWWNs in the ―Host to Storage‖ zone. You will need these PWWNs for the next step.

Command Syntax:

<do> show zoneset active vsan <BackEndVSAN#>

Command Example

mds(config)# do show zoneset active vsan 5

Step Action

18 From the ―config‖ prompt, create a new front end zone set and a ―Host to Storage‖ zone that matches the back end ―Host to Storage‖ zone. Note: There are several ways to accomplish this task. The screen shot below provides an example of creating the zone set. The back end zone could also be copied to the front end using the command line or Fabric Manager GUI.

Command Syntax:

mds(config)# zoneset name <name> vsan <FrontEndVSAN#> mds(config-zoneset)# zone name <name>

mds(config-zoneset-zone)# member pwwn <Storage Target PWWN> mds(config-zoneset-zone)# member pwwn <Host Initiator PWWN> mds(config-zoneset-zone)# exit

mds(config-zoneset)#zoneset activate name <name> vsan

<FrontEndVSAN#>

Creating and Activating the New Front End Zone Set – Command Examples

19 Copy the running configuration to the startup configuration. Command Example:

From the switch prompt run: copy run start From the config prompt run: do copy run start

Step Action

20 Use the show flogi database command to identify the interface number for the host initiator port in the back end VSAN. You will need this number to move the host initiator to the front end VSAN.

Command Syntax:

<do> show flogi database vsan <BackEndVSAN#>

Command Example

mds# show flogi database vsan 5

Show Flogi Database – Output Example

21 From the ―config-vsan-db‖ prompt, move the host initiator port (referencing the interface ID) from the back end VSAN to the front end VSAN. You only need to reference the front end VSAN number in the command. You do not need to reference the back end VSAN because the interface ID is unique.

Command Syntax: mds# config t

mds(config)# vsan database

mds(config-vsan-db)# vsan <FrontEndVSAN#> interface

<interfaceID>

switch(config-vsan-db)# exit

Step Action

Once the host initiator port is moved to the front end VSAN, it should log into the DVT resulting in the virtual initiator being created in the back end VSAN. At this time, the host should be able to see its assigned devices. You can use inq or syminq on your host to verify the devices are visible. The following steps will run through a series of check to verify (from the switch perspective) that the configuration is correct to this point.

22 Verify that the host initiator port interface ID is listed in the flogi database for your front end VSAN.

Command Syntax:

show flogi database vsan <FrontEndVSAN#>

Show Flogi Database – Command Example

23 Display the active zoneset in your front end VSAN. You should see that the host initiator PWWN has a ―* fcid‖. This indicates that the port has logged in and is active.

Command Syntax:

show zoneset active vsan <FrontEndVSAN#>

Command Example:

mds# show zoneset active vsan 15

Step Action

24 Display the active zoneset in your back end VSAN. The VI PWWN should also have a ―* fcid‖. Note: The FCID numbers should match if you configured persistent FCIDs on the switch.

Command Syntax:

show zoneset active vsan <BackEndVSAN#>

Command Example:

mds# show zoneset active vsan 5

Display Active Zoneset in Back End VSAN – Output Example

25 If the host initiator has successfully logged into the DVT and the VI was created in the back end VSAN, the DVT LUNs should now be visible. Viewing the DVT LUNs is similar to viewing the DVTs. The command will show all the DVT LUNs on the SSM module. You will have to scroll through the output to find your LUNs.

Command Syntax:

<do> show santap module <SSM#> dvtlun

Command Example:

mds# show santap module 2 dvtlun

In document RecoverPoint Implementation Lab 3.3 (Page 130-143)