Cisco MDS-9124 Troubleshooting Guide - Page 292

Zone Merge Failure Chapter 14 Troubleshooting Zones and Zone Sets Send documentation comments to [email protected] • 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 Interface on the VSAN was isolated because the adjacent switch is not responding to zone server requests. Recommended Action Flap the interface. Introduced Cisco MDS SAN-OS Release 1.2(2a). Error Message ZONE-2-ZS_MERGE_FAILED: Zone merge failure, Isolating interface [chars]. Explanation Interface isolated because of a zone merge failure. Recommended Action Compare active zoneset with the adjacent switch or enter the zone merge interface CLI command or similar Fabric Manager/Device Manager command. Introduced Cisco MDS SAN-OS Release 1.2(2a). Error Message ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: Zone merge full database mismatch on interface [chars]. Explanation Full zoning databases are inconsistent between two switches connected by interface . Databases are not merged. Recommended Action Compare full zoning database with the adjacent switch. Correct the difference and flap the link. Introduced Cisco MDS SAN-OS Release 1.3(1). Error Message ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: Zone merge full database mismatch on interface [chars]. Explanation Full zoning databases are inconsistent between two switches connected by the interface. Databases are not merged. Recommended Action Compare full zoning database with the adjacent switch, correct the difference and flap the link. Introduced Cisco MDS SAN-OS Release 1.2(2a). 14-14 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x OL-9285-05