Send comments to mdsfeedback-doc@cisco.com.
3-2
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 E Port Connectivity - ISL Isolation
Overview
On an E port, only one VSAN can be passed and possibly be isolated. However, in a trunking E port
(TE), multiple VSANs can become isolated while others are passing traffic. The same troubleshooting
approach applies in both cases, except that on a trunking E port the troubleshooting may need to be done
on a per-VSAN basis and/or on multiple VSANs.
Step 1) Verify that each VSAN is able to see the other switches within the same VSAN.
To verify that each switch is able to see the other switches, issue the following command at the exec
prompt. This command is VSAN-specific. If a specific VSAN is omitted from the command, it will list
the output for all VSANs.
switch# show fcdomain domain-list vsan 1
The output of the command lists set of domain IDs and associated WWNs for each switch within a
VSAN. This list provides the WWN of the switches owning each domain ID and the information about
the principality of those switches in the fabric or VSAN they belong to.
Sample output #1 (obtained in a fabric with just 2 switches in VSAN 1)
switch# sh fcdomain domain-list vsan 1
Number of domains: 2
Domain ID WWN
--------- --------------------------------
0x4a(74) 20:01:00:05:30:00:13:9f [Local]
0x4b(75) 20:01:00:05:30:00:13:9e [Principal]
------- --------------------------------------
This is an output of VSAN 1 in which 2 switches are seen. This indicates that the switch where the
command has been issued has built its adjacency on VSAN 1 with the other switch in the same VSAN.
Sample output #2
switch# sh fcdomain domain-list vsan 1
Number of domains: 1
Domain ID WWN
--------- -----------------------
0x4a(74) 20:01:00:05:30:00:13:9f [Local] [Principal]
--------- -----------------------
In this output only one switch is seen. This indicates that the switch where the command has been issued
has not established adjacency with the neighboring switch in VSAN 1.
Possible Causes for the problem
In the previous output one domain ID is missing. The reason of this can be found in the erroneous
configuration of several parameters between adjacent switches.
In case of E port/VSAN isolation the following parameters and configurations should be checked in each
switch:
• Zoning configuration
• VSAN configuration
• Domain ID parameters
• Fabric Parameters & Timers
To Next Page
Loading...
Need help?
General
