Send comments to mdsfeedback-doc@cisco.com.
3-20
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 Fx Port Connectivity
zone name zone-cc vsan 2
pwwn 50:06:0e:80:03:50:5c:01
pwwn 20:00:00:e0:69:41:a0:12
pwwn 20:00:00:e0:69:41:98:93
If the output of this command doesn’t show any information, this means that no zoneset has been
activated in the fabric. If this is the case, you can use the two commands show zone or show zoneset to
determine whether a zone configuration has been issued on the switch. (Zone configuration, and
configuration changes do not get propagated to the other switches in the fabric, but only the changes to
the active zones or active zoneset get propagated. For this reason if zone information is configured on
one switch, it won’t appear in the configuration of other switches).
Assuming that the zone configuration has been issued on the switch, but no active zoneset is shown, the
next step is to enable the active zoneset in the specific VSAN to which the zoneset is supposed to belong.
To activate a zoneset in a defined VSAN, run the following command:
switch(config)# zoneset activate name ZonesetName vsan 1
The command must be issued on same switch the zone configuration took place. By copying the active
zone database on the local zone database, it is possible to modify and apply those changes to the active
zoneset on a different switch from the one initially used to issue the active zone configuration.
If no port shows as isolated, it means that all the switches in the fabric (or in the specific VSAN) share
the same active zone database. This is ensured by the merge and change protocols used whenever any of
the following occurs:
• two fabrics are connected
• a new ISL is configured in the fabric
• a new switch is connected to a pre-configured fabric
• changes are applied to the active zone database on any switch in the fabric
Verify active zoneset membership
In case no port shows as isolated, check that the HBA’s FCID or pwwn and the storage subsystem FCID
or pwwn are correctly configured to belong to the same zone. Or, if they have been added to an fcalias,
check the correctness of the fcalias definition. Verify this information using the show zone active and
show zone commands, or by using the Fabric Manager VSAN/Zoning View.
In the following example, only the server HBA’s PWWN appears to be configured in the active zoneset
belonging to zone-cc on VSAN 2.
switch# show zoneset active
zoneset name ZoneSet1 vsan 1
zone name Zone1 vsan 1
pwwn 50:06:0e:80:03:50:5c:03
pwwn 20:00:00:e0:69:a1:b9:fc
zone name Zone2 vsan 1
pwwn 10:00:00:e0:02:21:df:ef
pwwn 20:00:00:e0:69:a1:b9:fc
zone name Zone3 vsan 1
fwwn 20:42:00:05:30:00:63:9e
fwwn 20:43:00:05:30:00:63:9e
zone name zone-cc vsan 2
pwwn 50:06:0e:80:03:50:5c:01
pwwn 20:00:00:e0:69:41:a0:12
To Next Page
Loading...
Need help?
General
