Domain Id Guidelines; Transit Vsan Guidelines; Border Switch Guidelines - Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual

Configuring IVR
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
IVR-enabled VSANs can be configured when the interop mode is enabled (any interop mode) or disabled
Note
(no interop mode).

Domain ID Guidelines

Domain IDs must be unique across inter-connected VSANs when not using IVR NAT. To ensure unique
domain IDs across inter-connected VSANs, consider these guidelines:
•
•
You can configure domain IDs using one of two options:
•
•
In a configuration involving IVR without NAT, if one VSAN in the IVR topology is configured with
Note
static domain IDs, then the other VSANs (edge or transit) in the topology must be configured with static
domain IDs.

Transit VSAN Guidelines

Before configuring transit VSANs, consider the following guidelines:
•
•
•

Border Switch Guidelines

Before configuring border switches, consider the following guidelines:
•
•
•
•
Cisco MDS 9000 Family CLI Configuration Guide
23-18
Minimize the number of switches that require a domain ID assignment. This ensures minimum
traffic disruption.
Minimize the coordination between interconnected VSANs when configuring the SAN for the first
time as well as when you add each new switch.
Configure the allowed-domains list so that the domains in different VSANs are non-overlapping on
all participating switches and VSANs.
Configure static, non-overlapping domains for each participating switch and VSAN.
Besides defining the IVR zone membership, you can choose to specify a set of transit VSANs to
provide connectivity between two edge VSANs:
If two edge VSANs in an IVR zone overlap, then a transit VSAN is not required (though, not
–
prohibited) to provide connectivity.
– If two edge VSANs in an IVR zone do not overlap, you may need one or more transit VSANs
to provide connectivity. Two edge VSANs in an IVR zone will not overlap if IVR is not enabled
on a switch that is a member of both the source and destination edge VSANs.
Traffic between the edge VSANs only traverses through the shortest IVR path.
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.
Chapter 23 Configuring Inter-VSAN Routing
OL-18084-01, Cisco MDS NX-OS Release 4.x