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 #88 background imageLoading...
Page #88 background image
Send comments to mdsfeedback-doc@cisco.com.
4-14
Cisco MDS 9000 Family Troubleshooting Guide
OL-5183-02, Cisco MDS SAN-OS Release 1.3
Chapter 4 Troubleshooting Switch Fabric Level Issues
Troubleshooting Zoning Issues
Note For all FSPF configuration statements and diagnostic commands, if the vsan keyword is not specified,
VSAN 1 is used by default. When making configuration changes or issuing diagnostic commands in a
multi-VSAN environment, be sure to explicitly specify the target VSAN by including the vsan keyword
in the statement or command.
Troubleshooting Zoning Issues
This section describes how to identify and resolve zoning issues that may arise in a multiswitch fabric.
It includes the following topics:
• Mismatched Active Zonesets Within the Same VSAN, page 4-14
• Importing or Exporting a Zoneset Between Switches, page 4-16
• Deactivating a Zoneset and Restarting the Zone Merge Process, page 4-17
• Misconfigured Zones Within an Active Zoneset in the Same VSAN, page 4-19
If after you verify the proper operation of the fibre channel name server and FSPF problems remain
discovering remote switches and their attached resources, the fabric may have zone configuration
problems. Examples of zone configuration problems are mismatched active zonesets and misconfigured
zones within the active zoneset.
Mismatched Active Zonesets Within the Same VSAN
When merging switch fabrics, you must ensure that the zones in both active zonesets have unique names,
or that any zones with the same name have exactly the same members. If either of these conditions is
violated the E port connecting the two fabrics will appear in an isolated state.
Figure 4-2 Topology for Zone Merge Failure Example
In this example, two switches have the same zoneset name, and the same zone names, but different zone
members. As a result, the VSAN is isolated on the TE port that connects to two switches.
This issue can be resolved by doing one of the following:
1. Modify the zone members on both zonesets to match and elimiate conflict
2. Deactivate the zoneset on one of the switches and restart the zone merge process
3. Explicitly import or export a zoneset between the switches to synchronize them.
To identify this problem, follow these steps:
Step 1 Enter the following command to display the active zoneset configuration of the first switch:
Switch1# show zoneset active v 99
Domain_ID
1
Domain_ID
239
Port-channel 1
Switch2 Switch3
91409

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