Table Of Contents

Configuring SANTap

Configuring SANTap on the SSM Using the CLI

Enabling SANTap on the SSM

Deploying SANTap

Configuring DVTs on the SSM

Displaying SANTap Information

Removing Appliance-Generated Entities

Removing AVTs and AVT LUNs

Removing SANTap Sessions

Removing Initiator-Target-LUNs

Creating a SANTap CVT SSM Using Fabric Manager

Deleting a SANTap CVT SSM Using Fabric Manager

Creating a SANTap DVT SSM Using Fabric Manager

Deleting a SANTap DVT SSM Using Fabric Manager

SANTap Support on Cisco MDS 9000 Family 18/4-Port Multiservice Module (MSM-18/4)

SANTap Support on Cisco MDS 9222i Multiservice Modular Switch

Configuring SANTap Multiservice Module Using the CLI

Enabling SANTap on the MDS 9222i Switch and the MSM-18/4

Enabling SANTap on the SSM

Deploying SANTap on the MSM-18/4

Configuring DVTs on the MDS 9222i Switch and MSM-18/4 Module

Displaying SANTap Information

Creating a SANTap DVT MSM Using Fabric Manager

Deleting a SANTap CVT MSM Using Fabric Manager

Deleting a SANTap DVT MSM

CISCO-SANTAP-MIB

SANTap DVT Interoperability Support Matrix

SANTap Compatibility with Storage Service Interface Images

SANTap Scalability Matrix

Default Settings

Configuring SANTap

---

This chapter describes how to configure SANTap and includes the following sections:

•Configuring SANTap on the SSM Using the CLI

•Displaying SANTap Information

•Removing Appliance-Generated Entities

•Default Settings

•Creating a SANTap CVT SSM Using Fabric Manager

•Deleting a SANTap CVT SSM Using Fabric Manager

•SANTap Support on Cisco MDS 9000 Family 18/4-Port Multiservice Module (MSM-18/4)

•Creating a SANTap DVT MSM Using Fabric Manager

•SANTap DVT Interoperability Support Matrix

•SANTap Scalability Matrix

Configuring SANTap on the SSM Using the CLI

The SANTap service can be configured to run in proxy operating mode. This mode offers unique design advantages that allow SANTap to fit customer requirements with minimal changes to current configurations.

The SANTap service provides a reliable copy of storage write operations to a third-party appliance, which enables applications to provide data protection, data migration, remote replication, and SLA monitoring, without the disadvantages of deploying devices in-band within the data path or out-of-band in conjunction with host-based software agents.

This section describes how to configure SANTap using the CLI and includes these topics:

•Enabling SANTap on the SSM

•Configuring DVTs on the SSM

Enabling SANTap on the SSM

To enable the SANTap feature, follow these steps:

	Command	Purpose
Step 1	switch# config t switch(config)#	Enters configuration mode.
Step 2	switch(config)# ssm enable feature santap module num	Enables the SANTap application on the entire SSM in the specified slot.
	switch(config)# no ssm enable feature santap module num	Disables the SANTap application on the entire SSM in the specified slot.

---

Note Only one intelligent service can be configured on a single SSM.

---

Deploying SANTap

To deploy SANTap, follow these steps:

---

Step 1 Identify the Storage Service Module (SSM) slot number.

switch# show module

Mod  Ports  Module-Type                      Model              Status

---  -----  -------------------------------- ------------------ ------------

1    16     1/2 Gbps FC/Supervisor           DS-X9216-K9-SUP    active *

2    32     Storage Services Module          DS-X9032-SMA       ok

Mod  Sw              Hw      World-Wide-Name(s) (WWN)

---  --------------  ------  --------------------------------------------------

1    4.1(1)          1.0     20:01:00:05:30:00:43:5e to 20:10:00:05:30:00:43:5e

2    4.1(1)          0.5     20:41:00:05:30:00:43:5e to 20:60:00:05:30:00:43:5e

Mod      Application Image Description       Application Image Version

-------- -----------------------------       -------------------------

2        SSI linecard image                  4.1(1)

Mod  MAC-Address(es)                         Serial-Num

---  --------------------------------------  ----------

1    00-0b-46-a1-a4-28 to 00-0b-46-a1-a4-2c  JAB065004G7

2    00-05-30-00-ad-12 to 00-05-30-00-ad-16  JAB070605MW

* this terminal session

Step 2 Verify that a SANTap license is installed.

switch# show license usage

Feature                      Ins  Lic   Status Expiry Date Comments

                                 		Count

--------------------------------------------------------------------------------

STORAGE_SERVICES_ENABLER_PKG  No    0   Unused             Grace 106D 18H

Step 3 Enable SANTap services on the SSM module.

switch(config)# ssm enable feature santap module number

Step 4 Check for SSM provisioning.

switch# show ssm provisioning

Module   Ports/Nodes       Application        Provisioning Status

-----------------------------------------------------------

   7      1-32          santap          success

Step 5 Create two VSANs.

SANTap uses two VSANs: a Back-End VSAN (BE-VSAN) and a Front-End VSAN (FE-VSAN). The BE-VSAN includes all storage targets, RPAs, and the control virtual target (CVT). A FE-VSAN includes host initiators and the data virtual target (DVT), which is a virtual representation of a storage target.

Step 6 Create a CVT in the BE-VSAN.

switch(config)# santap module number appl-vsan number cvt-name name

Step 7 Create a DVT in the FE-VSAN.

You must create a DVT for each storage port that you want to replicate. You can create several DVTs in one FE-VSAN or create DVTs in different VSANs.

switch(config)# santap module number dvt target-pwwn pwwn target-vsan number dvt-name name 
dvt-vsan number lun-size-handling 1

The BE-VSAN is zoned using the WWNs of the host initiator ports and the storage target ports. The same WWNs will be used in the FE-VSAN. Consequently, the back-end zoning scheme may be used for the FE-VSAN.

At this point, all I/O activity between the host and the target is relayed by SANTap. The I/Os are relayed from the actual host port in the FE-VSAN to the actual target port in the BE-VSAN via the DVT and the host port VI. This process has no impact to the hosts and is completely transparent.

---

Configuring DVTs on the SSM

To configure a DVT, follow these steps:

	Command	Purpose
Step 1	switch# config t switch(config)#	Enters configuration mode.
Step 2	switch(config)# santap module num dvt target-pwwn pwwn-id target-vsan vsan-id dvt-name name dvt-vsan vsan-id	Configures the pWWN, target VSAN (which contains the target and VI), DVT name, and DVT VSAN (which contains the host and the CVT).
	switch(config)# santap module num dvt target-pwwn pwwn-id target-vsan vsan-id dvt-name name dvt-vsan vsan-id dvt-port num	Configures the pWWN, target VSAN, DVT name, DVT VSAN, and DVT port. Note SANTap has to be provisioned for the entire module 2. When using the interface command, it should be provisioned on interface fc1/1-4. If not, you will not be able to provide the dvt-port option. The DVT port maps to one of the ports on the SSM. You can assign a port for explicit load balancing or not assign a port, which allows the SSM to select the port and handle the load balancing (default).
	switch(config)# santap module num dvt target-pwwn pwwn-id target-vsan vsan-id dvt-name name dvt-vsan vsan-id lun-size-handling num	Configures the pWWN, target VSAN, DVT name, DVT VSAN, and LUN size handling flag (enabled). Enabling the LUN size handling flag allows special LUN resize handling by the vendor. The default LUN size handling flag value is 1 (enabled).
	switch(config)# santap module num dvt target-pwwn pwwn-id target-vsan vsan-id dvt-name name dvt-vsan vsan-id io-timeout seconds	Configures the pWWN, target VSAN, DVT name, DVT VSAN, and timeout value in seconds. The timeout determines the interval after which to time out I/Os on the target side. The range is 10 to 200 seconds and the default value is 10 seconds.
	switch(config)# no santap module num dvt target-pwwn pwwn-id	Removes the DVT configuration.

In Cisco SAN-OS Release 3.2(1) or NX-OS Release 4.1(x), SANTap supports 32 host initiators per DVT.

Displaying SANTap Information

Use the show santap module command to display information about SANTap (see Example 2-1 to Example 2-6).

Example 2-1 Displays SANTap CVT Information

switch# show santap module 2 cvt

CVT Information :

        cvt pwwn     = 23:4f:00:0d:ec:09:3c:02

        cvt nwwn     = 23:9d:00:0d:ec:09:3c:02

        cvt id       = 135895180

        cvt xmap_id  = 135895212

        cvt vsan     = 8

        cvt name     = MYCVT

Example 2-2 Displays SANTap DVT Information

switch# show santap module 2 dvt

DVT Information :

       dvt pwwn     = 50:06:0e:80:03:81:32:36

       dvt nwwn     = 50:06:0e:80:03:81:32:36

       dvt id       = 136773180

       dvt mode     = 3

       dvt vsan     = 12

       dvt if_index = 0x1080000

       dvt fp_port  = 1

       dvt name     = MYDVT

       dvt tgt-vsan = 9

       dvt io timeout            = 10 secs

       dvt lun size handling     = 0

       dvt app iofail behaviour  = 1

       dvt quiesce behavior      = 1

       dvt tgt iofail behavior   = 0

       dvt appio failover time   = 50 secs

       dvt inq data behavior     = 0

Example 2-3 Displays SANTap DVT LUN Information

switch# show santap module 2 dvtlun

 DVT LUN Information :

        dvt pwwn     = 22:00:00:20:37:88:20:ef

        dvt lun      = 0x0

        xmap id      = 8

        dvt id       = 3

        dvt mode     = 0

        dvt vsan     = 3

        tgt pwwn     = 22:00:00:20:37:88:20:ef

        tgt lun      = 0x0

        tgt vsan     = 1

Example 2-4 Displays SANTap Session Information

switch# show santap module 2 session

Session Information :

        session id   = 1

        host pwwn     = 21:00:00:e0:8b:12:8b:7a

        dvt pwwn     = 50:06:0e:80:03:81:32:36

        dvt lun      = 0x0

        tgt pwwn     = 50:06:0e:80:03:81:32:36

        tgt lun      = 0x0

        adt pwwn     = 33:33:33:33:33:33:33:00

        adt lun      = 0x0

        aci pwwn     = 22:22:22:22:22:22:22:22

        cvt pwwn     = 23:4f:00:0d:ec:09:3c:02

        num ranges   = 0

        session state = 5

        redirect mode = 0

        mrl requested 1

        MRL : vsan 8 RegionSize 4806720, DiskPWWN 0x234f000dec093c02, DiskLun 0x 1, 
startLBA 1

        pwl requested 1

        PWL : type 2, UpdatePol 2, RetirePolicy 4, pwl_start 1

        iol requested 0

Example 2-5 Displays SANTap AVT Information

switch# show santap module 2 avt

 AVT Information :

        avt pwwn     = 2a:4b:00:05:30:00:22:25

        avt nwwn     = 2a:60:00:05:30:00:22:25

        avt id       = 12

        avt vsan     = 4

        avt if_index = 0x1080000

        hi pwwn      = 21:00:00:e0:8b:07:61:aa

        tgt pwwn     = 22:00:00:20:37:88:20:ef

        tgt vsan     = 1

Example 2-6 Displays SANTap AVT LUN Information

switch# show santap module 2 avtlun

 AVT LUN Information :

        avt pwwn     = 2a:4b:00:05:30:00:22:25

        avt lun      = 0x0

        xmap id      = 16

        avt id       = 12

        tgt lun      = 0x0

Removing Appliance-Generated Entities

An appliance might terminate its SANTap application without removing generated entities on the MDS switch. This section describes how to remove these entities using the CLI on the MDS switch.

This section includes the following topics:

•Removing AVTs and AVT LUNs

•Removing SANTap Sessions

•Removing Initiator-Target-LUNs

Removing AVTs and AVT LUNs

The AVT and AVT LUN configuration occasionally remains after a SANTap application terminates. To remove AVTs and AVT LUNs, follow these steps:

	Command	Purpose
Step 1	switch# show santap module num avt	Displays the AVT pWWNs.
	switch# show santap module num avtlun	Displays the AVT pWWNs and LUNs
Step 2	switch# clear santap module num avt 2a:4b:00:05:30:00:22:25 lun 234456	Removes a LUN from the AVT.
	switch# clear santap module num avt 2a:4b:00:05:30:00:22:25	Removes the AVT. Note You can remove the AVT only after all the LUNs are removed.

Removing SANTap Sessions

A SANTap session continues occasionally after a SANTap application terminates. To remove a SANTap session, follow these steps:

	Command	Purpose
Step 1	switch# show santap module 2 session	Displays SANTap session information on the SSM in slot 2.
Step 2	switch# clear santap module 2 session 1	Removes SANTap session 1 on the SSM in slot 2.

Removing Initiator-Target-LUNs

The initiator-target-LUN (ITL) triplet identifies a LUN loaded on a DVT. The ITL configuration occasionally remains after a SANTap application terminates. To remove all LUNs for an ITL triplet, follow these steps:

	Command	Purpose
Step 1	switch# show santap module 2 dvtlun	Displays the target and host pWWNs for the ITLs on the SSM in slot 2.
Step 2	switch# clear santap module 2 itl target-pwwn 22:00:00:20:37:88:20:ef host-pwwn 22:00:00:20:37:88:20:ef	Removes an ITL on the SSM in slot 2. Note The host port should be shut down before executing this command.

Creating a SANTap CVT SSM Using Fabric Manager

You have to configure a logical port on a switch to create the CVT for SANTap. CVTs create the control path, which processes the SANTap service requests sent by an appliance.

Before requesting the SANTap service, the appliance contacts the CVT, and specifies the initiator and the target for replicating the data flowing between them.

To create a SANTap CVT using Fabric Manager, follow these steps:

---

Step 1 Expand End Devices, and then select Intelligent Features from the Physical Attributes pane.

You see the FCWA tab in the Information pane.

Step 2 Click the SANTap CVT tab.

You see the SANTap configuration in the Information pane.

Step 3 Click Create Row.

You see the create SANTap CVT dialog box shown in Figure 2-1.

Figure 2-1 SANTap CVT Dialog Box

Step 4 Select the switch and the module on which you want to configure a SANTap CVT.

---

Note SANTap must be enabled and provisioned as a service on the SSM module of the selected switch.

---

Step 5 Select the VSAN ID in which you want to configure the SANTap CVT.

Step 6 Click Create to create this SANTap CVT.

---

Deleting a SANTap CVT SSM Using Fabric Manager

To delete a SANTap CVT using Fabric Manager, follow these steps:

---

Step 1 Expand End Devices, and then select Intelligent Features from the Physical Attributes pane.

You see the FCWA tab in the Information pane.

Step 2 Click the SANTap CVT tab.

You see the SANTap configuration in the Information pane.

Step 3 Select the SANTap CVT that you want to delete.

Step 4 Click Delete Row.

You see the Fabric Manager Confirmation dialog box.

Step 5 Click Yes to proceed with the deletion or click No to discard the changes.

---

Creating a SANTap DVT SSM Using Fabric Manager

To create a SANTap DVT using Fabric Manager, follow these steps:

---

Step 1 Expand End Devices, and then select Intelligent Features from the Physical Attributes pane.

You see the FCWA tab in the Information pane.

Step 2 Click the SANTap DVT SSM tab.

You see the SANTap configuration in the information pane (see Figure 2-2).

Figure 2-2 SANTap DVT SSM Dialog Box

Step 3 Click Create Row.

You see the create SANTap DVT SSM dialog box as shown in Figure 2-3.

Figure 2-3 SANTap DVT SSM Dialog Box

Step 4 Select the switch on which the SANTap DVT SSM will be configured.

Step 5 Select the interface. This is the port on the module where the DVT will be created.

Step 6 Select the VSAN ID in which you want to create the SANTap DVT SSM.

Step 7 Select the port WWN of the real target for which this corresponding DVT is being created. The DVT has the same port WWN as the target.

Step 8 Select the target VSAN ID for the VSAN of the real target for which this DVT is being created.

---

Note Uncheck the Automatically Choose Interface check box to select the interface.

---

Step 9 Assign a name to this SANTap DVT SSM.

Step 10 Check the LunSizeHandling check box if you want to use the real target LUN size for the virtual LUN or the maximum LUN size supported (2 TB).

Step 11 From the IOTimeout drop-down list, select the I/O timeout value for the DVT. The default value is 10 seconds.

Step 12 Click Create to create this SANTap DVT SSM.

---

Deleting a SANTap DVT SSM Using Fabric Manager

To delete a SANTap DVT using Fabric Manager, follow these steps:

---

Step 1 Expand End Devices, and then select Intelligent Features from the Physical Attributes pane.

You see the FCWA tab in the information pane.

Step 2 Click the SANTap DVT SSM tab.

You see the SANTap configuration in the Information pane.

Step 3 Select the SANTap DVT that you want to delete.

Step 4 Click Delete Row.

You see the Fabric Manager Confirmation dialog box.

Step 5 Click Yes to proceed with the deletion or click No to discard the changes.

---

SANTap Support on Cisco MDS 9000 Family 18/4-Port Multiservice Module (MSM-18/4)

The Cisco MDS 9000 Family 18/4-port multiservice module (MSM-18/4) provides 18 autosensing
1/ 2 / 4-Gbps Fibre Channel ports and four Gigabit Ethernet IP services ports. MSM-18/4 provides multiprotocol capabilities such as Fibre Channel, Fibre Channel over IP (FCIP), Small Computer System Interface over IP (iSCSI), IBM Fiber Connectivity (FICON), and FICON Control Unit Port (CUP) management.

MSM-18/4 provides intelligent diagnostics, protocol decoding, and network analysis tools with the integrated Call Home capability.

---

Note Cisco MDS 9500 Series switches running Cisco MDS SAN-OS Release 3.2 (1) or later support MSM-18/4, but SANTap provisioning is supported only from NX-OS Release 4.1(x).

---

SANTap Support on Cisco MDS 9222i Multiservice Modular Switch

The Cisco MDS 9222i Multiservice Modular switch includes an integrated supervisor module (in slot 1) that provides the control and management functions of the Cisco MDS 9222i Switch. The switch provides an 18-port Fibre Channel switching and 4-port Gigabit Ethernet IP services module. The Cisco MDS 9222i built-in supervisor module provides multiple communication and control paths to avoid a single point of failure.

The Cisco MDS 9222i switch includes a modular expansion slot to host Cisco MDS 9000 Family Switching and Services Modules.

For additional information, refer to the Cisco MDS 9200 Series Hardware Installation Guide.

---

Note The Cisco MDS 9222i switch requires a minimum of MDS SAN-OS Release 3.2(1).

---

Configuring SANTap Multiservice Module Using the CLI

This section describes how to configure SANTap on the Multiservice Module using the CLI:

•Enabling SANTap on the MDS 9222i Switch and the MSM-18/4

•Deploying SANTap on the MSM-18/4

•Configuring DVTs on the MDS 9222i Switch and MSM-18/4 Module

Enabling SANTap on the MDS 9222i Switch and the MSM-18/4

SANTap can be enabled on an MDS 9222i Switch and an MSM-18/4 platform.

---

Note You will need a license to provision SANTap. Set the boot ssi value for module 1 (MDS 9222i Switch) and then reload the switch before you provision SANTap on Module 1.

---

The following command enables SANTap on an Octeon-based platform:

switch(config)#

switch(config)#ssm enable feature santap module x 

module x is where the MSM module is present.

Enabling SANTap on the SSM

The following command enables SANTap on the SSM:

switch(config)#

switch(config)# ssm enable feature santap module 1

---

Note SANTap can be enabled on SSM Module 2.

---

Deploying SANTap on the MSM-18/4

To deploy SANTap, follow these steps:

---

Step 1 Identify the MSM slot number.

switch# show module

Mod  Ports  Module-Type                      Model              Status

---  -----  -------------------------------- ------------------ ------------

1    22     4x1GE IPS, 18x1/2/4Gbps FC/Sup2  DS-X9222I-K9       active *

Mod  Sw              Hw      World-Wide-Name(s) (WWN)

---  --------------  ------  --------------------------------------------------

1    3.2(1a)         0.610   20:01:00:0d:ec:4a:c8:40 to 20:12:00:0d:ec:4a:c8:40

Mod      Application Image Description       Application Image Version

-------- -----------------------------       -------------------------

1        SSI linecard image (Packaged in SAN-OS) 3.2(1a)

Mod  MAC-Address(es)                         Serial-Num

---  --------------------------------------  ----------

1    00-17-5a-b5-6d-1c to 00-17-5a-b5-6d-24  JAE1123KB03

* this terminal session

Step 2 Verify that SANTap license is installed.

switch# show license usage

Feature                      Ins  Lic   Status Expiry Date Comments

                                 Count

--------------------------------------------------------------------------------

FM_SERVER_PKG                 No    -   Unused             Grace expired

MAINFRAME_PKG                 No    -   Unused             -

ENTERPRISE_PKG                No    -   Unused             -

DMM_FOR_SSM_PKG               No    0   Unused             -

SAN_EXTN_OVER_IP              No    0   Unused             -

PORT_ACTIVATION_PKG           No    0   Unused             -

SAN_EXTN_OVER_IP_18_4         No    0   Unused             -

SAN_EXTN_OVER_IP_IPS2         No    0   Unused             -

SAN_EXTN_OVER_IP_IPS4         No    0   Unused             -

10G_PORT_ACTIVATION_PKG       No    0   Unused             -

STORAGE_SERVICES_ENABLER_PKG  No    0   Unused             Grace 117D 23H

switch# ------------------------------------------------------------------------

Step 3 Enable SANTap services on the SSM module.

switch(config)# ssm enable feature santap module number

Step 4 Check for SSM provisioning.

switch# show ssm provisioning

Module   Ports/Nodes       Application        Provisioning Status

-----------------------------------------------------------

  12      1-1           santap          success

Step 5 Create two VSANs.

SANTap uses two VSANs: a Back-End VSAN (BE-VSAN) and a Front-End VSAN (FE-VSAN). The BE-VSAN includes all storage targets, RPAs, and the control virtual target (CVT). A FE-VSAN includes host initiators and the data virtual target (DVT), which is a virtual representation of a storage target.

Step 6 Create CVT in the BE-VSAN.

switch(config)# santap module number appl-vsan number cvt-name name

Step 7 Create DVT in the FE-VSAN.

You must create a DVT for each storage port that you want to replicate. You may create several DVTs in one FE-VSAN or create DVTs in different VSANs.

switch(config)# santap module number dvt target-pwwn pwwn target-vsan number dvt-name name 
dvt-vsan number lun-size-handling 1

The BE-VSAN is zoned using the WWNs of the host initiator ports and the storage target ports. The same WWNs will be used in the FE-VSAN. Consequently, the back-end zoning scheme may be used for the FE-VSAN.

At this point, all I/O activity between the host and the target is relayed by SANTap. The I/Os are relayed from the actual host port in the FE-VSAN to the actual target port in the BE-VSAN via the DVT and the host port VI. This process has no impact to the hosts and is completely transparent.

---

Configuring DVTs on the MDS 9222i Switch and MSM-18/4 Module

A Data Virtual Target (DVT) is a logical target port that resides on the switch and is used to intercept traffic for a real target. Assigning a DVT to a different front-panel port is supported only on an SSM but not on an MDS 9222i Switch and MSM-18/4 Module. SANTap provisioning using the interface command is not supported on an SSM.

To configure a DVT, follow these steps:

	Command	Purpose
Step 1	switch# config t switch(config)#	Enters configuration mode.
Step 2	switch(config)# santap module num dvt target-pwwn pwwn-id target-vsan vsan-id dvt-name name dvt-vsan vsan-id	Configures the pWWN, target VSAN (which contains the target and VI), DVT name, and DVT VSAN (which contains the host and the CVT).
	switch(config)# santap module num dvt target-pwwn pwwn-id target-vsan vsan-id dvt-name name dvt-vsan vsan-id dvt-port num	Configures the pWWN, target VSAN, DVT name, DVT VSAN, and DVT port. Note SANTap has to be provisioned for the entire module 2. When using the interface command, it should be provisioned on interface fc1/1-4. If not, you will not be able to provide the dvt-port option. The DVT port maps to one of the ports on the SSM. You can assign a port for explicit load balancing or not assign a port, which allows the SSM to select the port and handle the load balancing (default).
	switch(config)# santap module num dvt target-pwwn pwwn-id target-vsan vsan-id dvt-name name dvt-vsan vsan-id lun-size-handling num	Configures the pWWN, target VSAN, DVT name, DVT VSAN, and LUN size handling flag (enabled). Enabling the LUN size handling flag allows special LUN resize handling by the vendor. The default LUN size handling flag value is 1(enabled).
	switch(config)# santap module num dvt target-pwwn pwwn-id target-vsan vsan-id dvt-name name dvt-vsan vsan-id io-timeout seconds	Configures the pWWN, target VSAN, DVT name, DVT VSAN, and timeout value in seconds. The timeout determines the interval after which to time out I/Os on the target side. The range is 10 to 200 seconds and the default value is 10 seconds.
	switch(config)# no santap module num dvt target-pwwn pwwn-id	Removes the DVT configuration.

---

Note In Cisco SAN-OS Release 3.2(1) or NX-OS Release 4.1(x), SANTap supports 32 host initiators per DVT.

---

---

Note Do not use the dvt-port option for the MDS 9222i Switch and MSM-18/4 Module from the dvt-port help CLI.

---

Displaying SANTap Information

Use the show santap module command to display information about SANTap (see Example 2-7 to Example 2-12).

Example 2-7 Displays SANTap CVT Information

switch# show santap module 2 cvt

CVT Information :

        cvt pwwn     = 23:4f:00:0d:ec:09:3c:02

        cvt nwwn     = 23:9d:00:0d:ec:09:3c:02

        cvt id       = 135895180

        cvt xmap_id  = 135895212

        cvt vsan     = 8

        cvt name     = MYCVT

Example 2-8 Displays SANTap DVT Information

switch# show santap module 2 dvt

DVT Information :

       dvt pwwn     = 50:06:0e:80:03:81:32:36

       dvt nwwn     = 50:06:0e:80:03:81:32:36

       dvt id       = 136773180

       dvt mode     = 3

       dvt vsan     = 12

       dvt if_index = 0x1080000

       dvt fp_port  = 1

       dvt name     = MYDVT

       dvt tgt-vsan = 9

       dvt io timeout            = 10 secs

       dvt lun size handling     = 0

       dvt app iofail behaviour  = 1

       dvt quiesce behavior      = 1

       dvt tgt iofail behavior   = 0

       dvt appio failover time   = 50 secs

       dvt inq data behavior     = 0

Example 2-9 Displays SANTap DVT LUN Information

switch# show santap module 2 dvtlun

 DVT LUN Information :

        dvt pwwn     = 22:00:00:20:37:88:20:ef

        dvt lun      = 0x0

        xmap id      = 8

        dvt id       = 3

        dvt mode     = 0

        dvt vsan     = 3

        tgt pwwn     = 22:00:00:20:37:88:20:ef

        tgt lun      = 0x0

        tgt vsan     = 1

Example 2-10 Displays SANTap Session Information

switch# show santap module 2 session

Session Information :

        session id   = 1

        host pwwn     = 21:00:00:e0:8b:12:8b:7a

        dvt pwwn     = 50:06:0e:80:03:81:32:36

        dvt lun      = 0x0

        tgt pwwn     = 50:06:0e:80:03:81:32:36

        tgt lun      = 0x0

        adt pwwn     = 33:33:33:33:33:33:33:00

        adt lun      = 0x0

        aci pwwn     = 22:22:22:22:22:22:22:22

        cvt pwwn     = 23:4f:00:0d:ec:09:3c:02

        num ranges   = 0

        session state = 5

        redirect mode = 0

        mrl requested 1

        MRL : vsan 8 RegionSize 4806720, DiskPWWN 0x234f000dec093c02, DiskLun 0x 1, 
startLBA 1

        pwl requested 1

        PWL : type 2, UpdatePol 2, RetirePolicy 4, pwl_start 1

        iol requested 0

Example 2-11 Displays SANTap AVT Information

switch# show santap module 2 avt

 AVT Information :

        avt pwwn     = 2a:4b:00:05:30:00:22:25

        avt nwwn     = 2a:60:00:05:30:00:22:25

        avt id       = 12

        avt vsan     = 4

        avt if_index = 0x1080000

        hi pwwn      = 21:00:00:e0:8b:07:61:aa

        tgt pwwn     = 22:00:00:20:37:88:20:ef

        tgt vsan     = 1

Example 2-12 Displays SANTap AVT LUN Information

switch# show santap module 2 avtlun

 AVT LUN Information :

        avt pwwn     = 2a:4b:00:05:30:00:22:25

        avt lun      = 0x0

        xmap id      = 16

        avt id       = 12

        tgt lun      = 0x0

Creating a SANTap DVT MSM Using Fabric Manager

To create a SANTap DVT MSM using Fabric Manager, follow these steps:

---

Step 1 Expand End Devices, and then select Intelligent Features from the Physical Attributes pane.

You see the FCWA tab in the information pane.

Step 2 Click the SANTap DVT MSM tab.

You see the SANTap configuration in the information pane (see Figure 2-4).

Figure 2-4 SANTap DVT MSM Dialog Box

Step 3 Click Create Row.

You see the create SANTap DVT MSM dialog box as shown in Figure 2-5.

Figure 2-5

SANTap DVT MSM Dialog Box

Step 4 Select the switch on which the SANTap DVT MSM will be configured.

Step 5 Select the interface. This is the port on the module where the DVT will be created.

Step 6 Select the VSAN ID in which you want to create the SANTap DVT MSM.

Step 7 Select the port WWN of the real target for which this corresponding DVT is being created. The DVT has the same port WWN as the target.

Step 8 Select the target VSAN ID for the VSAN of the real target for which this DVT is being created.

---

Note Uncheck the Automatically Choose Interface check box to select the interface.

---

Step 9 Assign a name to this SANTap DVT MSM.

Step 10 Check the LunSizeHandling check box if you want to use the real target LUN size for the virtual LUN or the maximum LUN size supported (2 TB).

Step 11 From the IOTimeout drop-down list, select the I/O timeout value for the DVT. The default value is 10 seconds.

Step 12 Click Create to create this SANTap DVT MSM.

---

Deleting a SANTap CVT MSM Using Fabric Manager

To delete a SANTap CVT using Fabric Manager, follow these steps:

---

Step 1 Expand End Devices, and then select Intelligent Features from the Physical Attributes pane.

You see the FCWA tab in the Information pane.

Step 2 Click the SANTap CVT tab.

You see the SANTap configuration in the Information pane.

Step 3 Select the SANTap CVT you want to delete.

Step 4 Click Delete Row.

You see the Fabric Manager Confirmation dialog box.

Step 5 Click Yes to proceed with the deletion or click No to discard the changes.

---

Deleting a SANTap DVT MSM

To delete a SANTap DVT MSM using Fabric Manager, follow these steps:

---

Step 1 Expand End Devices, and then select Intelligent Features from the Physical Attributes pane.

You see the FCWA tab in the information pane.

Step 2 Click the SANTap DVT MSM tab.

You see the SANTap configuration in the information pane.

Step 3 Select the SANTap DVT that you want to delete.

Step 4 Click Delete Row.

You see the Fabric Manager Confirmation dialog box.

Step 5 Click Yes to proceed with the deletion or click No to discard the changes.

---

CISCO-SANTAP-MIB

The Cisco SANTap MIB provides an SNMP interface to create and delete a SANTap Control Virtual Target (CVT) and a Data Virtual Target (DVT).

For more information on the SANTap MIB, refer to the Cisco MDS 9000 Family MIB Quick Reference.

SANTap DVT Interoperability Support Matrix

The SANTap DVT Interoperability Support Matrix is located in the SANTap section of the Cisco Data Center Interoperability Support Matrix.

SANTap Compatibility with Storage Service Interface Images

For compatibility information between SANTap, Cisco MDS SAN-OS software releases, and Storage Service Interface (SSI) releases, refer to the Cisco MDS SAN-OS Release Compatibility Matrix for Storage Service Interface Images.

SANTap Scalability Matrix

Table 2-1 lists the scalability limits for the SAN-OS and NX-OS releases that support SANTap.

Table 2-1 SANTap Scalability Matrix on SSM

Attribute	3.1(2m)	3.1(3)	3.2(3)	4.1(x)
Hosts per DVT	16	16	64	64
LUNs per Host per DVT	256	256	256	256
LUNs per DVT	1K	1K	3K	3K
DVTs per SSM	16	32	64	128
Sessions per SSM	2K	2K	2K	2K
LUN ID address size	16	16	32	32
DVT LUNs per SSM	2K	4K	16K	16K
ITLs per DPP	1K	1K	3K	3K
ITLs per SSM	2K	4K	24K	24K

Table 2-2 lists the scalability limits for NX-OS Release 4.1(1i) on the MSM-18/4 module and the MDS 9222i switch.

Table 2-2 SANTap Scalability on the MSM-18/4 Module and the MDS 9222i Switch

Attribute	4.1(1i)
Hosts per DVT	64
LUNs per Host per DVT	256
LUNs per DVT	3K
DVTs per SN	128
Sessions per SN	2K
LUN ID address size	32
DVT LUNs per SN	16K
ITLs per DPP	24K
ITLs per SN	24K

Default Settings

Table 2-3 lists the default settings for SANTap parameters.

Table 2-3 Default SANTap Parameters 

Parameters	Default
SANTap feature	Disabled.
DVT I/O timeout	10 seconds.
DVT LUN size handling flag	1 (enabled).

---

Note The LUN-size handling flag is enabled by default.

---