Chapter 29
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
•
Border Switch Guidelines
Before configuring border switches, consider the following guidelines:
•
•
•
•
•
Configuring IVR Without NAT
To enable IVR in NAT mode from Fabric Manager, follow these steps:
Step 1
Expand All VSANs and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Figure 29-6
Click the Action tab.
Step 2
Uncheck the Enable IVR NAT check box (see
Step 3
Click the Apply Changes icon to distribute this change to all switches in the fabric.
Step 4
Manually Creating the IVR Topology
You must create the IVR topology in every IVR-enabled switch in the fabric if you have not configured
IVR topology in auto mode. You can have up to 128 VSANs in an IVR topology. Specify the IVR
topology using the following information:
•
•
•
OL-16184-01, Cisco MDS SAN-OS Release 3.x
Transit VSAN information is common to all IVR zone sets. Sometimes, a transit VSAN can also act
as an edge VSAN in another IVR zone.
Border switches require Cisco MDS SAN-OS Release 1.3(1) or later.
A border switch must be a member of two or more VSANs.
A border switch that facilities IVR communications must be IVR enabled.
IVR can (optionally) be enabled on additional border switches to provide redundant paths between
active IVR zone members.
The VSAN topology configuration must be updated before a border switch is added or removed.
Action Tab
The switch WWNs of the IVR-enabled switches.
A minimum of two VSANs to which the IVR-enabled switch belongs.
The AFID, which distinguishes two VSANs that are logically and physically separate, but have the
same VSAN number. You can specify up to 64 AFIDs. See
Figure
29-6).
Figure
29-7.
Cisco MDS 9000 Family CLI Configuration Guide
Manual IVR Configuration
29-15