Cisco MDS-9124 Troubleshooting Guide - Page 465

Send documentation comments to [email protected] 23 C H A P T E R Troubleshooting SANTap This chapter describes how to identify and resolve problems that might occur when implementing SANTap. This chapter includes the following sections: • Overview, page 23-1 • Definitions, page 23-2 • Limitations, page 23-2 • Initial Troubleshooting Checklist, page 23-3 • SANTap Issues, page 23-6 Overview Note SANTap is not supported in Release 3.3.1. SANTap is an Intelligent Storage Services feature supported on the Storage Services Module (SSM). The SSM supports SANTap in Cisco MDS SAN-OS Release 2.0(2b) and later. The SANTap feature allows third-party data storage applications, such as long distance replication and continuous backup, to be integrated into the SAN. SANTap has a control path and a data path. The control path services requests that create and manipulate replication sessions that are sent by an appliance. The control path is implemented using a SCSI-based protocol. An appliance sends requests to a control virtual target (CVT) which the SANTap process creates and monitors. Responses are sent to the control LUN on the appliance. SANTap also allows LUN mapping to appliance virtual targets (AVTs). You can have a maximum of 512 target LUNs. When introducing SANTap-based applications, SANTap does not require reconfiguration of either the host or the target, and neither the host initiator nor the target is required to be directly connected to an SSM. This accomplished by assigning Cisco-specific WWNs to the virtual initiators (VIs) and data virtual targets (DVTs). A host initiator or a target can be connected directly to an SSM. However, you must partition the SAN using VSANs. You must configure the host initiator and the DVT in one VSAN and configure the virtual initiator (VI) and the target in another VSAN. OL-9285-05 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x 23-1