The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco UCS Central enables you to define global VLANs in a LAN cloud at the domain group root, or at the domain group level. You can create a single VLAN or multiple VLANs in one operation.
Global VLAN resolution takes place in Cisco UCS Central prior to global service profiles deployment. If a global service profile references a global VLAN, and that VLAN does not exist, the global service profile deployment fails in the Cisco UCS domain due to insufficient resources. All global VLANs created in Cisco UCS Central must be resolved before deploying that global service profile.
Global VLANs are pushed to Cisco UCS domain along with the global service profiles that reference them. Global VLAN information is visible to Cisco UCS Manager only if a global service profile with reference to a global VLAN is deployed in that Cisco UCS domain. When a global VLAN is deployed and becomes available in the Cisco UCS domain, locally-defined service profiles and policies can reference the global VLAN. A global VLAN is not deleted when a global service profile that references it is deleted.
![]() Note |
You must have created the VLAN in Cisco UCS Central prior to publishing it to push it down to Cisco UCS Manager. |
![]() Note |
If a VLAN group is used to allow VLANs on a Fabric Interconnect’s uplink, the global VLAN must be manually published to Cisco UCS Manager and added to the VLAN group, prior to adding to the service profile assigned to the Cisco UCS domain. If the global VLAN is not published and added to the VLAN group, the vNIC will shut down as the uplink will not allow the global VLAN to pass through. |
![]() Note |
A global VLAN is not deleted when a global service profile that references it is deleted. |
You cannot delete a global VLAN from Cisco UCS Manager. If you want to delete a global VLAN from Cisco UCS Manager, you have to localize the VLAN and then delete it.
All VLANs configured in Cisco UCS Central are common to the orgs in which they are created. You must assign organization permissions before the Cisco UCS Manager instances that are part of the organizations can consume the resources. When you assign org permission to a VLAN, the VLAN is visible to those organizations, and available to be referenced in service profiles maintained by the Cisco UCS Manager instances that are part of the organization.
VLAN name resolution takes place within the hierarchy of each domain group. If a VLAN with the same name exists in multiple domain groups, the organization permissions are applied to all VLANs with the same name across the domain groups.
You can create, modify or delete VLAN org permission.
![]() Note |
Make sure to delete the VLAN org permission from the same org you created it in. On Cisco UCS Central GUI you can view the org structure where this VLAN is associated. But at the sub org level on the Cisco UCS Central CLI, you cannot view the VLAN org permission association hierarchy, so if you try to delete the VLAN at the sub org level on the Cisco UCS Central CLI the delete operation will fail. |
You can create a VLAN at the domain group root or at a specific domain group level, and specify the orgs that can access the VLAN.
You can edit theVLAN ID, Multicast Policy and access for control for any selected VLANs. After creating a VLAN in a domain group, you can not change the Domain Group Location or the VLAN Name.
To watch a video on creating a VLAN, see Video: Creating a VLAN and Assigning Org Permission.
From the Manage VLAN Access dialog box, you can add or remove permissions to one or more VLANs at the same time.
![]() Note |
You can only add or remove access each time you open the dialog box. If you want to do both actions, you will need to relaunch the dialog box. |
A VLAN Group is a logical entity created to configure VLANs on uplink ports and port channels, and vNICs in a Global Service Profile. Starting Cisco UCS Central 2.0, you can create a VLAN Group to logically group VLANs on Ethernet uplink ports by function, or by VLANs that belong to a specific network. You can apply these VLAN Groups to Ethernet uplink ports or service profile vNICs. VLAN Groups for Ports and Service Profiles are supported for Cisco UCS Manager 3.1(3) and later releases. However, Global VLAN Groups are not supported on Cisco UCS Manager releases prior to 3.1(3) even though they are supported locally in Cisco UCS Central.
You can create a VLAN Group under LAN Cloud per Domain-Group.
For a Global Service profile, all associated VLAN Groups are resolved when the service profile is associated to a server. Depending on the server location in Cisco UCS Central, the VLANs get dynamically resolved and get deployed to the domain.
For VLAN Groups on a Port, all associated VLANs are resolved when you save the port configuration depending on the domain group membership of the domain in Cisco UCS Central.
VLAN Groups have Org permission configured, and are accessible only from those Global Service Profiles that are created under the Orgs with the corresponding org permission. After you assign a VLAN to a VLAN group, all changes you make are applied to all Ethernet uplink ports and vNICs that are configured in the VLAN Group. You can configure multiple VLAN Groups for a vNIC (in the case of the Global Service Profile), and for uplink ports or port-channels. More than one VLAN Group can co-exist with other ungrouped VLANs that are configured on a vNIC or a port or port-channel.
When you configure an uplink port with a VLAN Group, that uplink port supports only the VLANs that are part of the associated VLAN Group, and the individual VLANs if any, that are associated with the uplink. An uplink port on a particular Cisco UCS Domain that is not associated with the VLAN Group does not support the VLANs that are part of the configured VLAN Group.
You can configure VLAN Groups on the vNICs in the following ways:
Directly modifying the vNIC
Modifying through the LAN Connectivity Policy
Modifying through the vNIC template
A VLAN Group Container view displays a list of all VLAN groups in a domain. You can view the following details in the VLAN Group Container view:
Name—Lists the VLAN group names present in a domain group
Native VLAN—Lists the Native VLANs associated with the VLAN groups
You can filter the VLAN group Containers by Domain Group, Export, Delete, Tag, and Search for a specific VLAN group on this page.