Send comments to mdsfeedback-doc@cisco.com.
3-6
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
The import option of the command of will overwrite the local switch’s active zoneset with that of the
remote switch. The export option will overwrite the remote switch’s active zoneset with the local
switch’s active zoneset.
• If the zoning databases between the two switches are overwritten, you will not be able to use the
import option. To work around this, you can manually change the content of the zone database on
either of the switches, and then issue a shut/no shut on the isolated port.
If the isolation is specific to one VSAN and not on a E port, the correct way to issue the cycle up/down,
is to remove the VSAN from the list of allowed VSANs on that trunk port, and re-insert it.
Do not simply issue a shut/no shut sequence of commands on the port, because this would affect all the
VSANs crossing the EISL instead of just the VSAN experiencing the isolation problem.
Using the Zone Merge Analysis tool in Fabric Manager, the compatibility of two active zonesets in two
switches can be checked before actually merging the two zonesets. Refer to the Cisco MDS 9000 Fabric
Manager User Guide for more information.
Troubleshooting a VSAN Configuration Conflict
In the following example, the E port has been isolated because the interfaces connecting the two switches
belong to different VSANs.
switch# show interface fc2/4
fc2/4 is down fc2/4 is down (isolation due to port vsan mismatch)
Hardware is Fibre Channel, WWN is 20:44:00:05:30:00:63:5e
vsan is 2
Beacon is turned off
30 frames input, 682 bytes, 0 discards
0 runts, 0 jabber, 0 too long, 0 too short
0 input errors, 0 CRC, 0 invalid transmission words
0 address id, 0 delimiter
0 EOF abort, 0 fragmented, 0 unknown class
30 frames output, 583 bytes, 0 discards
Received 2 OLS, 2 LRR, 2 NOS, 5 loop inits
Transmitted 5 OLS, 3 LRR, 2 NOS, 4 loop inits
In the above example, the E port isolated because the interface of the 2 switches belong to different
VSANS. To resolve this issue move the interfaces to the same VSAN.
You can check the VSAN membership with the switch interfaces with the following command.
switch# show vsan membership
vsan 1 interfaces:
fc2/1 fc2/2 fc2/3 fc2/4 fc2/6 fc2/7 fc2/8 fc2/9
fc2/10 fc2/11 fc2/12 fc2/14 fc2/15 fc2/16 fc7/1 fc7/2
fc7/3 fc7/4 fc7/5 fc7/6 fc7/7 fc7/8 fc7/9 fc7/10
fc7/11 fc7/12 fc7/13 fc7/14 fc7/15 fc7/16 fc7/17 fc7/18
fc7/19 fc7/20 fc7/21 fc7/22 fc7/23 fc7/24 fc7/25 fc7/26
fc7/27 fc7/28 fc7/29 fc7/30 fc7/31 fc7/32
vsan 2 interfaces:
fc2/5 fc2/13
vsan 4094(isolated_vsan) interfaces:
The command shows that all the interfaces on the switch belong to VSAN 1, with the exception of
interface 2/5 and 2/13 that are part of VSAN 2.
To Next Page
Loading...
Need help?
General
