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
About IVR
IVR is not supported on the Cisco MDS 9124 Fabric Switch, the Cisco MDS 9134 Fabric Switch, the
Note
Cisco Fabric Switch for HP c-Class BladeSystem, and the Cisco Fabric Switch for IBM BladeCenter.
Data traffic is transported between specific initiators and targets on different VSANs without merging
VSANs into a single logical fabric. Fibre Channel control traffic does not flow between VSANs, nor can
initiators access any resource across VSANs other than the designated ones. Valuable resources such as
tape libraries are easily shared across VSANs without compromise.
IVR is in compliance with Fibre Channel standards and incorporates third-party switches, however,
IVR-enabled VSANs may have to be configured in one of the interop modes.
IVR is not limited to VSANs present on a common switch. Routes that traverse one or more VSANs
across multiple switches can be established, if necessary, to establish proper interconnections. IVR used
in conjunction with FCIP provides more efficient business continuity or disaster recovery solutions (see
Figure
Note
See the
scenario shown in
Figure 23-1
Traffic Continuity Using IVR and FCIP
IVR-Enabled
Switch
MDS1
FC
FC
FC
VSAN 1
Note
OX ID based load balancing of IVR traffic from IVR- enabled switches is not supported on Generation
1 switching modules. OX ID based load balancing of IVR traffic from a non-IVR MDS switch should
work. Generation 2 switching modules support OX ID based load balancing of IVR traffic from
IVR-enabled switches.
Cisco MDS 9000 Family CLI Configuration Guide
23-2
23-1).
"Example Configurations" section on page 23-39
Figure
23-1.
FC or FCIP links (multiple links for redundancy)
Transit VSAN (VSAN 4)
MDS2
FC
FC
T
for procedures to configure the sample
MDS3
FC
FC
FC
FC
S1
VSAN 2
Chapter 23
Configuring Inter-VSAN Routing
MDS4
FC
FC
FC
FC
S2
VSAN 3
OL-18084-01, Cisco MDS NX-OS Release 4.x