A VSAN name must be unique.
Note
• Load balancing attributes—These attributes indicate the use of the source-destination ID (src-dst-id) or
the originator exchange OX ID (src-dst-ox-id, the default) for load balancing path selection.
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.
Note
This section describes how to create and configure VSANs and includes the following topics:
Reserved VSAN Range and Isolated VSAN Range Guidelines
On an NPV switch with a trunking configuration on any interface, or on a regular switch where the f
port-channel-trunk command is issued to enable the Trunking F Port Channels feature, follow these
configuration guidelines for reserved VSANs and the isolated VSAN:
• If trunk mode is on for any of the interfaces or NP Port Channel is up, the reserved VSANs are 3040 to
4078, and they are not available for user configuration.
• The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is 4079, and it is not available for user
configuration.
VSAN Creation
A VSAN is in the operational state if the VSAN is active and at least one port is up. This state indicates that
traffic can pass through this VSAN. This state cannot be configured.
Creating VSANs Statically
You cannot configure any application-specific parameters for a VSAN before creating the VSAN.
Creating VSANs
To create VSANs, follow these steps:
Step 1 switch# config terminal
Enters configuration mode.
Step 2 switch(config)# vsan database
switch(config-vsan-db)#
Configures the database for a VSAN. Application specific VSAN parameters cannot be configured from this prompt.
Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x
12
Configuring and Managing VSANs
Reserved VSAN Range and Isolated VSAN Range Guidelines
To Next Page
Loading...
Need help?
General
