EasyManuals Logo

Cisco MDS 9000 Series Troubleshooting Guide

Cisco MDS 9000 Series
161 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #56 background imageLoading...
Page #56 background image
Send comments to mdsfeedback-doc@cisco.com.
3-10
Cisco MDS 9000 Family Troubleshooting Guide
OL-5183-02, Cisco MDS SAN-OS Release 1.3
Chapter 3 Troubleshooting Switch Level Issues and Interswitch Connectivity
Troubleshooting TE Port Connectivity - VSAN Isolation
2547 frames input, 173332 bytes, 0 discards
0 CRC, 0 unknown class
0 too long, 0 too short
2545 frames output, 120300 bytes, 0 discards
14 input OLS, 12 LRR, 9 NOS, 33 loop inits
31 output OLS, 17 LRR, 13 NOS, 11 loop inits
switch2#
To fix the issue, the administrator can either change the static domain ID that is overlapping by manually
configuring a new static domain ID for the isolated switch, or disable the static domain assignment, and
allow the switch to request a new domain ID after a fabric reconfiguration.
For example, two switches may be merging and one of the switches is already powered up, but the second
switch has a domain ID preconfigured. In this case, the switch that is powered up will have the priority
in keeping the conflicting domain ID. The presently powered-on switch, being the principal switch, will
assign a new domain ID to the new switch.
The E port could still isolate if the new switch has the domain ID configured as static, thus it would not
take any other domain ID except for the one configured. If this were the case, it would be necessary to
configure a new domain ID on the switch before the two switches could merge.
Troubleshooting TE Port Connectivity - VSAN Isolation
Trunking E ports (TE ports) are similar to E ports except they carry traffic for multiple VSANs. E ports
carry traffic for a single VSAN. Because TE ports carry traffic for multiple VSANs, ISL isolation can
affect one or more VSANs. For this reason, on a TE port you must troubleshoot ISL isolation on each
VSAN.
Even in case of VSAN isolation, the starting point for troubleshooting the problem is to issue the show
interface command.
The following example shows what the result of the show interface command, issued on a TE port in
case of no VSAN is isolated (normal behavior).
switch# show interface fc7/9
fc7/9 is trunking
Hardware is Fibre Channel
Port WWN is 21:89:00:05:30:00:18:a2
Peer port WWN is 20:c1:00:05:30:00:13:9e
Admin port mode is auto, trunk mode is on
Port mode is TE
Speed is 2 Gbps
vsan is 1
Beacon is turned off
FCID is 0x000000
Receive B2B Credit is 12
Trunk vsans (allowed active) (1,333)
Trunk vsans (operational) (1,333)
Trunk vsans (up) (1,333)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
Counter Values (current):
262 frames input, 18808 bytes, 0 discards
0 runts, 0 jabber, 0 too long, 0 too short
0 input errors, 0 CRC, 2 invalid transmission words
0 address id, 0 delimiter
0 EOF abort, 0 fragmented, 0 unknown class
264 frames output, 16960 bytes, 0 discards
Received 5 OLS, 3 LRR, 2 NOS, 11 loop inits
Transmitted 8 OLS, 4 LRR, 2 NOS, 3 loop inits

Table of Contents

Other manuals for Cisco MDS 9000 Series

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Cisco MDS 9000 Series and is the answer not in the manual?

Cisco MDS 9000 Series Specifications

General IconGeneral
CategorySwitch
Operating SystemCisco NX-OS
PortsVaries by model
ProtocolsFibre Channel (FC), Fibre Channel over IP (FCIP), iSCSI
RedundancyRedundant supervisors, power supplies, and fans
ManagementCisco Data Center Network Manager (DCNM), CLI, SNMP
Virtualization SupportVSANs (Virtual SANs)
Security FeaturesFibre Channel Security Protocol (FC-SP)
Hot Swappable Componentspower supplies, fans
Power Supply OptionsAC and DC options available

Related product manuals