HP Cisco MDS 9120 Cisco MDS 9000 Family CLI Configuration Guide, Release 3.x ( - Page 547

Chapter 22 Configuring Inter-VSAN Routing Configuring IVR Send documentation comments to [email protected] • Host devices always see the same FC ID for targets. • It helps you plan your SAN layout better by assigning virtual domains for IVR to use. • It can make SAN monitoring and management easier. When you see the same domain or FC ID consistently assigned, you can readily determine the native VSAN or device to which it refers. You can configure two types of database entries for persistent IVR FC IDs: • Virtual domain entries-Contain the virtual domain that should be used to represent a native VSAN in a specific VSAN (current VSAN). These entries contain the following information: - Native AFID - Native VSAN - Current AFID - Current VSAN - Virtual domain to be used for the native AFID and VSAN in current AFID and VSAN • Virtual FC ID entries-Contain the virtual FC ID that should be used to represent a device in a specific VSAN (current VSAN). These entries contain the following information: - Port WWN - Current AFID - Current VSAN - Virtual FC ID to be used to represent a device for the given pWWN in the current AFID and VSAN Note If you use persistent FC IDs for IVR, we recommend that you use them for all the devices in the IVR zoneset. We do not recommend using persistent FC IDs for some of the IVR devices while using automatic allocation for others. Note IVR NAT must be enabled to use IVR persistent FC IDs. Note In an IVR NAT configuration, if one VSAN in the IVR topology is configured with static domain IDs, then the IVR domains that can be exported to that VSAN must also be assigned static domains. Configuring Persistent FC IDs for IVR To configure persistent FC IDs for IVR, follow these steps: Step 1 Command switch# config t Purpose Enters configuration mode. OL-16184-01, Cisco MDS SAN-OS Release 3.x Cisco MDS 9000 Family CLI Configuration Guide 22-25