Domain Id Guidelines; Transit Vsan Guidelines - HP Cisco MDS 9216 - Fabric Switch Configuration Manual

Manual IVR Configuration
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
•
•
•
Tip If you change any FSPF link cost, ensure that the FSPF path distance (that is, the sum of the link costs
on the path) of any IVR path is less than 30,000.
Note IVR-enabled VSANs can be configured when the interop mode is enabled (any interop mode) or disabled
(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:
•
•
Note In a configuration involving IVR without NAT, if one VSAN in the IVR topology is configured with
static domain IDs, then the other VSANs (edge or transit) in the topology should be configured with
static domain IDs.

Transit VSAN Guidelines

Before configuring transit VSANS, consider the following guidelines:
•
•
Cisco MDS 9000 Family CLI Configuration Guide
29-14
Configure unique domain IDs across all VSANs and switches participating in IVR operations if you
are not using IVR NAT. The following switches participate in IVR operations:
– All edge switches in the edge VSANs (source and destination)
All switches in transit VSANs
–
Configure IVR only in the relevant border switches.
Acquire a mandatory Enterprise License Package or SAN-EXTENSION license package and one
active IPS card for this feature.
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.
Chapter 29 Configuring Inter-VSAN Routing
OL-16184-01, Cisco MDS SAN-OS Release 3.x