1Rendersall VSANs with an ID in the range from 3840 to 4079 non-operational.
2Raisesa faultagainst the non-operationalVSANs.
3Transfersall non-operational VSANs to the default VSAN.
4Transfersall vHBAs associated with the non-operational VSANs to the default VSAN.
Ifyou disable Fibre Channel trunking and delete any existing SAN port channels, Cisco UCS Manager returns
allVSANs in the range from 3840 to 4078 to an operational state and restores any associated vHBAs back
tothose VSANs.
Range Restrictions for Named VSAN IDs in FC Switch Mode
Ifyou plan to use FC switch mode in a Cisco UCS domain, do not configure VSANs in the range from 3040
to4078.
Whena fabric interconnect operating in FC switch mode is connected to MDS as the upstream switch, VSANs
configuredin Cisco UCS Manager in the range from 3040 to 4078 and assigned as port VSANs cannot be
createdin MDS. This configuration results in a possible port VSAN mismatch.
Guidelines for FCoE VLAN IDs
FCoEVLANs in the SAN cloud and VLANs in the LAN cloud must have differentIDs. Using the same
IDfor an FCoE VLAN in a VSAN and a VLAN resultsin a critical fault and traffic disruption for all
vNICsand uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN which has an
IDthat overlapswith an FCoE VLAN ID.
Note
VLAN4048 is user-configurable. However, Cisco UCS Manager uses VLAN 4048 for the following default
values.If you want to assign 4048 to a VLAN, you must reconfigure these values:
Thedefault FCoE VLAN varies according to the type of VSAN and whether Cisco UCS is a fresh installation
oran upgrade, as follows:
• After an upgrade to Cisco UCS, release 2.0: The FCoE storage port native VLAN uses VLAN 4048 by
default.If the default FCoE VSAN wasset to use VLAN 1before the upgrade, you mustchange it to a
VLANID that is not used or reserved. For example, consider changing the default to 4049 if that VLAN
IDis not in use.
• After a fresh install of Cisco UCS, release 2.0: The FCoE VLAN for the default VSAN uses VLAN
4048by default. The FCoE storageport native VLAN uses VLAN 4049.
Creating a Named VSAN
FCoEVLANs in the SAN cloud and VLANs in the LAN cloud must have differentIDs. Using the same
IDfor an FCoE VLAN in a VSAN and a VLAN resultsin a critical fault and traffic disruption for all
vNICsand uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN which has an
IDthat overlapswith an FCoE VLAN ID.
Note
Cisco UCS Manager GUI Configuration Guide, Release 2.0
OL-25712-04 335
Creating a Named VSAN