Chapter 18
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 .
Transit VSAN Guidelines
Consider the following guidelines for transit VSANs:
•
•
•
Border Switch Guidelines
Before configuring border switches, consider the following guidelines:
•
•
•
•
•
IVR Configuration
To configure IVR in a SAN fabric, follow these steps:
Determine whether to use IVR NAT (Network Address Translation).
Step 1
If you do not plan to use IVR NAT (supported as of Cisco MDS SAN-OS Release 2.1(1a)), verify that
Step 2
unique domain IDs are configured in all switches and VSANs participating in IVR.
Enable IVR in the border switches.
Step 3
Configure the service group as required.
Step 4
Step 5
Configure fabric distribution as required.
Step 6
Configure the IVR topology, either manually or automatically.
Create and activate IVZSs in all of the IVR-enabled border switches, either manually or using fabric
Step 7
distribution.
Verify the IVR configuration.
Step 8
OL-6973-03, Cisco MDS SAN-OS Release 2.x
Besides defining the IVZ membership, you can choose to specify a set of transit VSANs to provide
connectivity between two edge VSANs:
If two edge VSANs in an IVZ overlap, then a transit VSAN is not required (though, not
–
prohibited) to provide connectivity.
If two edge VSANs in an IVZ do not overlap, you may need one or more transit VSANs to
–
provide connectivity. Two edge VSANs in an IVZ will not overlap if IVR is not enabled on a
switch that is a member of both the source and destinations edge VSANs.
Traffic between the edge VSANs only traverses through the shortest IVR path.
Transit VSAN information is common to all IVZs. Sometimes, a transit VSAN can also double-up
as an edge VSAN in another IVZ.
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 IVZ members.
The VSAN topology configuration must be updated before a border switch is added or removed if
the switch is running Cisco MDS SAN-OS Release 2.0(3) or earlier, or if IVR topology automatic
mode is not enabled (available as of Cisco MDS SAN-OS Release 2.1(1a) or later).
Cisco MDS 9000 Family Configuration Guide
IVR Configuration
18-5