HP Cisco MDS 9120 Cisco MDS 9000 Family Fabric Manager Configuration Guide - R - Page 602

Configuring SDV Chapter 27 SAN Device Virtualization Send documentation comments to [email protected] • 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. To link a virtual target with a physical target using Fabric Manager, follow these steps: Step 1 Step 2 Step 3 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 are linking with a physical target(see Figure 27-9). Select the Real Device ID of the physical target that you are linking with the virtual target. Figure 27-9 Create Real Devices Dialog Box SAN Device Virtualization vtpwwn vt1 SAN Device Virtualization Zone i1pwwn i2pwwn i3pwwn i1 i2 i3 Virtual Device t1pwwn t1 t2pwwn t2 159901 Primary Secondary Step 4 Step 5 Step 6 Choose either the pWWN or deviceAlias radio button, and select the appropriate pWWN or device alias 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. Click the CFS icon to save and distribute these changes, or click Close to discard any unsaved changes. 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: • 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. 27-8 Cisco MDS 9000 Family Fabric Manager Configuration Guide OL-17256-03, Cisco MDS NX-OS Release 4.x