Zone Merge Failure
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Too many attribute groups
•
Too many zones
•
Too many LUN members
•
Too many zone members
•
Use the show zone internal merge event-history CLI command to determine the cause of the zone
merge failure.
You may see one or more of the following system messages after a zone merge failure:
Error Message ZONE-2-ZS_MERGE_ADJ_NO_RESPONSE: Adjacent switch not responding,
Isolating Interface [chars] (VSAN [dec]).
Explanation
zone server requests.
Recommended Action
Introduced
Error Message
[chars].
Explanation
Recommended Action
interface CLI command or similar Fabric Manager/Device Manager command.
Introduced
Error Message
mismatch on interface [chars].
Explanation
Databases are not merged.
Recommended Action
and flap the link.
Introduced
Error Message
mismatch on interface [chars].
Explanation
interface. Databases are not merged.
Recommended Action
and flap the link.
Introduced
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
14-14
Interface on the VSAN was isolated because the adjacent switch is not responding to
Flap the interface.
Cisco MDS SAN-OS Release 1.2(2a).
ZONE-2-ZS_MERGE_FAILED: Zone merge failure, Isolating interface
Interface isolated because of a zone merge failure.
Compare active zoneset with the adjacent switch or enter the zone merge
Cisco MDS SAN-OS Release 1.2(2a).
ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: Zone merge full database
Full zoning databases are inconsistent between two switches connected by interface .
Compare full zoning database with the adjacent switch. Correct the difference
Cisco MDS SAN-OS Release 1.3(1).
ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: Zone merge full database
Full zoning databases are inconsistent between two switches connected by the
Compare full zoning database with the adjacent switch, correct the difference
Cisco MDS SAN-OS Release 1.2(2a).
Chapter 14
Troubleshooting Zones and Zone Sets
OL-9285-05