Sdv Merge Fails When Isl Comes Up; Zone Activation Fails In A Sdv Zone - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

SDV Issues
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

SDV Merge Fails When ISL Comes Up

Table 12-5
Symptom
Table 12-5 SDV Merge Fails When ISL Comes Up
Symptom Possible Cause
SDV merge fails Configuration mismatch in the merging
when ISL comes up. fabrics.
Virtual device name and pWWN
mismatch in the merging fabrics.
Virtual device name and FC ID
mismatch in the merging fabrics.

Zone Activation Fails in a SDV Zone

Symptom
If a zone activation fails in a SDV zone, enter the show zone internal sdv-table command to view the
physical-virtual mapping maintained in the zone server. Devices should be zoned so that they cannot
communicate to both the real device and its virtual component.
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
12-6
describes the measures to take when an SDV merge fails and ISL comes up.
SDV merge fails when the ISL comes up.
Zone activation fails in a SDV zone.
Chapter 12 Troubleshooting SAN Device Virtualization
Solution
To forcefully recover from an SDV merge failure due to an
ISL not coming up, perform an empty commit from one of
the involved fabrics.
This should not only remedy name and pWWN
Note
mismatches, but also a device alias failure.
OL-9285-05