Configuring Inter-VSAN Routing
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
You can configure two types of database entries for persistent IVR FC IDs:
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.
IVR NAT must be enabled to use IVR persistent FC IDs.
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:
switch# config t
OL-16184-01, Cisco MDS SAN-OS Release 3.x
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.
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:
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:
Virtual FC ID to be used to represent a device for the given pWWN in the current AFID and
Enters configuration mode.
Cisco MDS 9000 Family CLI Configuration Guide