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
23-3
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 23 Troubleshooting SANTap
Initial Troubleshooting Checklist
Interface Restrictions
When enabled on a per-port basis, SANTap must be enabled on a group of four ports on an SSM. The
following restrictions apply:
•
The fewest number of interfaces that can be SANTap enabled is four.
•
The first interfaces in a group must be 1, 5, 9, 13, 17, 21, 25, or 29. (You can specify fc5 through
fc8, but not fc7 through fc10.)
•
The groups of four interfaces do not need to be consecutive. For example, you can specify fc1
through fc8 and fc17 through fc20.
Initial Troubleshooting Checklist
Troubleshooting a SANTap problem involves gathering information about the configuration and
connectivity of the various SANTap components. Begin your troubleshooting activity as follows:
DVTs per SSM
32
Cisco SAN-OS 3.1(2) with SSI 3.1(2m) and later
16
Prior to Cisco SAN-OS 3.1(2) with SSI 3.1(2m)
Sessions per SSM
1024
Cisco SAN-OS 3.0(2) with SSI 3.0(2j)
2048
Cisco SAN-OS 3.1(2b) with SSI 3.1(2m) and later
LUN ID address
32-bits
Cisco SAN-OS 3.2
16-bits
Prior to Cisco SAN-OS 3.2
DVT LUNs per SSM
4080
All releases
ITLs per DPP
1500
Cisco SAN-OS 3.2
1024
Prior to Cisco SAN-OS 3.2
ITLs per SSM
1024
Cisco SAN-OS 3.0(2) with SSI 3.0(2j)
2048
Cisco SAN-OS 3.1(2b) with SSI 3.1(2m)
4080
Cisco SAN-OS 3.1(3) with SSI 3.1(3) and later
Table 23-2
SANTap Attribute Limitations (continued)
Attribute
Limitation
Cisco SAN-OS and SSI Release
Checklist
Check off
Verify licensing requirements. See
Cisco MDS 9000 Family Fabric Manager
Configuration Guide
.
Verify that SANTap is enabled on the SSM module of the selected switch.
Verify the VSAN configuration and zones for the appliance, using the configuration and
verification tools for the specific appliance.
Verify the physical connectivity for any problem ports or VSANs.
