Resolving Fabric Merge Conflicts - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

Configuring SDV
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
•
To link a virtual target with a physical target using Fabric Manager, follow these steps:
Step 1 Click the Real Devices tab and then click the Create Row icon.
Select the Virtual Device ID from the pull-down list or enter an existing ID for the virtual target that you
Step 2
are linking with a physical target(see
Step 3 Select the Real Device ID of the physical target that you are linking with the virtual target.
Figure 27-9
Choose either the pWWN or deviceAlias radio button, and select the appropriate pWWN or device alias
Step 4
from the pull-down menu. Note that the Name field is automatically populated when you select the
pWWN or device alias.
Choose either the primary or secondary radio button for the Map Type.
Step 5
Click the CFS icon to save and distribute these changes, or click Close to discard any unsaved changes.
Step 6

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:
•
•
•
Cisco MDS 9000 Family Fabric Manager Configuration Guide
27-8
When the secondary device is active, if you link to a third device, and if the fallback attribute was
configured, then the third device becomes the primary device as well as the active device.
Create Real Devices Dialog Box
SAN Device Virtualization Zone
SAN Device
i1pwwn
Virtualization
vtpwwn
vt1
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.
Figure 27-9).
i2pwwn i3pwwn
i1 i2 i3
Virtual
Device
t1pwwn t2pwwn
t1 t2
Primary Secondary
Chapter 27 SAN Device Virtualization
OL-17256-03, Cisco MDS NX-OS Release 4.x