Symptoms

ISL is not passing VSAN traffic because of zone mode mismatch in Cisco switch.Error message: Zone merge failure, isolating interface fc4/1 received reason: Zoning modes does not match Received rjt from adjacent switch:[reason:0]. The zone status for the VSAN is different on the two switches. This issue may also happen when the mode is changed and VSAN has not bounced. The following command confirms the same: show zone status vsan 1-4093 Sample Output: VSAN: 10 default-zone: deny distribute: active only Interop: default ( mode: enhanced merge-control: allow session: none hard-zoning: enabled broadcast: unsupported Default zone: qos: none broadcast: unsupported ronly: unsupported Full Zoning Database : DB size: 4 bytes Zonesets:0 Zones:0 Aliases: 0 Active Zoning Database : Database Not Available Status: The interface details show that VSAN 10 is isolated. You can verify if the VSAN is isolated or not using the command: show interface fc4/1 Sample Output: (fc4/1 is the interface in this example. fc4/1 is trunking (not all VSANs are UP on the trunk.) Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN) Port WWN is 20:01:00:05:73:cb:a9:80 Peer port WWN is 20:01:00:05:73:cf:f5:f0 Admin port mode is E, trunk mode is on snmp link state traps are enabled Port mode is TE Port vsan is 1 Speed is 8 Gbps Rate mode is dedicated Transmit B2B Credit is 32 Receive B2B Credit is 500 B2B State Change Number is 14 Receive data field Size is 2112 Beacon is turned off Trunk vsans (admin allowed and active) (1,10) Trunk vsans (up) (1) Trunk vsans (isolated) (10) Trunk vsans (initializing) () 5 minutes input rate 152 bits/sec, 19 bytes/sec, 0 frames/sec 5 minutes output rate 56 bits/sec, 7 bytes/sec, 0 frames/sec 4520 frames input, 318268 bytes 0 discards, 0 errors 0 CRC, 0 unknown class 0 too long, 0 too short 4896 frames output, 392484 bytes 0 discards, 0 errors 52 input OLS, 30 LRR, 12 NOS, 11 loop inits 52 output OLS, 38 LRR, 32 NOS, 15 loop inits 500 receive B2B credit remaining 32 transmit B2B credit remaining 28 low priority transmit B2B credit remaining Interface last changed at Mon May 10 11:51:54 2011

Cause

The issue happens when the zone mode (enhanced or basic) is different on the two ISL'ed switches. The VSAN does not merge and is isolated.

Resolution

Make the zone mode consistent (enhanced or basic) on both switches followed by suspending VSAN 10 and enabling it again.Note: The fix is disruptive and affects all traffic that is related to the affected VSAN in the issue. (Skip this step if they are consistent.) Make the zone mode consistent on both switches. Run the following commands for enhanced: switch# config t switch(config)# zone mode enhanced vsan 10 switch(config)# zone commit vsan 10 Make the zone mode consistent on both switches. Run the following commands for basic: switch# config t switch(config)# no zone mode enhanced vsan 10 Suspend and enable the VSAN using the following commands: switch# config t switch(config) # vsan database switch (config-vsan-db) #vsan 10 suspend switch (config-vsan-db) #no vsan 10 suspend For more information, see Configuring and Managing VSANs.

Support Cases