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.
If a global VLAN is part of a global service profile, or a global port configuration, automatic VLAN resolution takes place when the service profile is pushed down, and the VLANs are available for local consumption in the Cisco UCS domain. If the global VLANs are not associated to a global service profile, or a global port configuration, you must manually publish them to deploy them to Cisco UCS Manager. Cisco UCS Central provides a command to manually publish the global VLAN to sync with Cisco UCS Manager. For more information on Publishing VLANs see Cisco UCS Central CLI Reference Manual.
You must have created the VLAN in Cisco UCS Central prior to publishing it to push it down to Cisco UCS Manager.
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.
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
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
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.
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.