• Configuring and unconfiguring border ports and border port channels
• Adding or removing VLANs from a cloud
• Configuring or unconfiguring SAN or NAS ports
• Associating or disassociating service profiles that contain configuration changes
• Configuring or unconfiguring VLANs under vNICs or vHBAs
• Upon receiving creation or deleting notifications from a VMWarevNIC, from an ESX hypervisor
Thisis outsidethe control of CiscoUCS ManagerNote
• Fabric interconnect reboot
• Cisco UCS Manager upgrade or downgrade
CiscoUCS Manager strictly enforces the VLAN port limit on service profile operations. If Cisco UCS Manager
detectsthat you have exceeded the VLAN port limit service profile configuration will fail during deployment.
Exceedingthe VLAN port count in a border domain is less disruptive. When the VLAN port count is exceeded
ina border domainCisco UCS Manager changes the allocation status to Exceeded. In order to change the
statusback toAvailable, you should complete one of the following actions:
• Unconfigure one or more border ports
• Remove VLANs from the LAN cloud
• Unconfigure one or more vNICs or vHBAs
Configuring Named VLANs

Creating a Named VLAN

Ina Cisco UCS domain that is configured for high availability, you can create a named VLAN that is accessible
toboth fabric interconnects or to only one fabric interconnect.
Youcannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved.
VLANsin the LAN cloud and FCoEVLANs in the SAN cloud must have differentIDs. Using the same
IDfor a VLAN and an FCoE VLANin a VSAN results in a critical fault and traffic disruption for all
vNICsand uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that
overlapswith an FCoEVLAN ID.
Important
Cisco UCS Manager GUI Configuration Guide, Release 2.0
280 OL-25712-04
Configuring Named VLANs