Cisco MDS-9124 Troubleshooting Guide - Page 202

Common Problems with Port Interfaces Chapter 8 Troubleshooting Ports Send documentation comments to [email protected] Troubleshooting E port Isolation Using the CLI To troubleshoot E port isolation due to zoning using the CLI, follow these steps: Step 1 Use the show interface command output to verify that the E port did not come up because of a zone merge failure. Note Zoning information exists on a per VSAN basis. Therefore, for a TE port, it may be necessary to verify that the zoning information does not conflict for any allowed VSAN. Step 2 Step 3 Step 4 switch# show interface fc2/14 fc2/14 is down (Isolation due to zone merge failure) Hardware is Fibre Channel, WWN is 20:4e:00:05:30:00:63:9e vsan is 1 Beacon is turned off 40 frames input, 1056 bytes, 0 discards 0 runts, 0 jabber, 0 too long, 0 too short 0 input errors, 0 CRC, 3 invalid transmission words 0 address id, 0 delimiter 0 EOF abort, 0 fragmented, 0 unknown class 79 frames output, 1234 bytes, 16777216 discards Received 23 OLS, 14 LRR, 13 NOS, 39 loop inits Transmitted 50 OLS, 16 LRR, 21 NOS, 25 loop inits Verify the zoning information using the following commands: • show zone vsan vsan-id • show zoneset vsan vsan-id Use one of the following two approaches to resolve a zone merge failure: • Overwrite the zoning configuration of one switch with the other switch's configuration. This can be done with the following commands: - zone copy interface fc slot/port import vsan vsan-id - zone copy interface fc slot/port export vsan vsan-id The import option of the command of overwrites the local switch's active zoneset with that of the remote switch. The export option overwrites the remote switch's active zoneset with the local switch's active zone set. • If the zoning databases between the two switches are overwritten, you cannot 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 shutdown/no shutdown command sequence on the isolated port. If the isolation is specific to one VSAN and not on an E port, the correct way to issue the cycle u p or down is to remove the VSAN from the list of allowed VSANs on that trunk port, and reinsert it. Note We recommend that you do not disable and then enable a T or TE port. This would affect all the VSANs crossing the EISL instead of just the VSAN experiencing the isolation problem. 8-30 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x OL-9285-05