S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
SANTap has a control path and a data path. The control path handles requests that create and manipulate
replication sessions 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.
SANTap does not require reconfiguration of either the host or target when introducing SANTap-based
applications. Also, neither the host initiator nor the target is required to be directly connected to an SSM.
This is 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 VI and the target in
another VSAN. See
Cisco MDS 9000 Family CLI Configuration Guide
Integrating Third-Party Storage Applications in a SAN
= Data trap
OL-16184-01, Cisco MDS SAN-OS Release 3.x