Real Initiator And Sdv Virtual Target With Lun; Sdv Virtual Initiator And Real Target With Lun; Sdv Virtual Initiator And Sdv Virtual Target With Lun; Resolving Fabric Merge Conflicts - Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual

Chapter 21 SAN Device Virtualization
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
•
•

Real Initiator and SDV Virtual Target with LUN

In Example 21-1
Example 21-1 Real Initiator and SDV Virtual Target with LUN
zoneset name zs1 vsan 2

SDV Virtual Initiator and Real Target with LUN

In Example 21-2
Example 21-2 SDV Virtual Initiator and Real Target with LUN
zoneset name zs2 vsan 1

SDV Virtual Initiator and SDV Virtual Target with LUN.

In Example 21-3
Example 21-3
zoneset name zs3 vsan 1

Resolving Fabric Merge Conflicts

Whenever two fabrics merge SDV merges its database. A merge conflict can occur when there is a
run-time information conflict or configuration mismatch. Run-time conflicts can occur due to:
•
•
•
OL-18084-01, Cisco MDS NX-OS Release 4.x
Virtual target (VT1) virtualizing the real target (T1)
Virtual initiator (VI1) virtualizing real initiator (I1)
a real initiator is zoned with an SDV virtual target (including the LUN).
zone name z1 vsan 2
member device-alias I1
member device-alias VT1 lun 0
member device-alias VT2 lun 1
an SDV virtual initiator is zoned with a real target (including the LUN).
zone name z2 vsan 1
member device-alias VI1
member device-alias T1 lun 0
member device-alias T2 lun 1
an SDV virtual initiator is zoned with an SDV virtual target (including the LUN).
zone name z3 vsan 1
member device-alias VI1
member device-alias VT1 lun 0
member device-alias VT2 lun 1
Identical pWWNs being assigned to different virtual devices
The same virtual devices are assigned different pWWNs.
The virtual device and virtual FC ID are mismatched.
Cisco MDS 9000 Family CLI Configuration Guide
Configuring SDV
21-11