Hi there,
I've run into a zone merge Failure, and going over the documentation it seem like the zoneset import command should be the most efficient way to work this out. I'ld like to know if the zoneset import command is disruptive for the vsan I'm working on and/or all vsan running on the equipment.
The actual status of the situation:
Log
%ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: %$VSAN 292%$ Zone merge full database mismatch on interface san-port-channel 2
%ZONE-2-ZS_MERGE_FAILED: %$VSAN 292%$ Zone merge failure, isolating interface san-port-channel 2 reason: Member mismatch:[reason:0]
%PORT-5-IF_TRUNK_DOWN: %$VSAN 292%$ Interface san-port-channel 2, vsan 292 is down (Isolation due to zone merge failure)
Interface status
….
Belongs to san-port-channel 2
Trunk vsans (admin allowed and active) (1,291-292,299)
Trunk vsans (up) (1,291,299)
Trunk vsans (isolated) (292)
Trunk vsans (initializing) ()
Zone status
….
VSAN: 292 default-zone: deny distribute: full Interop: default
mode: enhanced merge-control: allow
session: none
hard-zoning: enabled broadcast: disabled
Default zone:
qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
DB size: 111804 bytes
Zonesets:1 Zones:746 Aliases: 1 Attribute-groups: 1
Active Zoning Database :
DB size: 78720 bytes
Name: Fabric-B Zonesets:1 Zones:746s
Status: Commit completed at 15:44:26 EDT Apr 2 2020
If someone have information to share about this, it would be appreciate.
Thanks!
Alain
