Deploying Global VLANs and VSANs

VLAN and VSAN Policy Push

In Cisco UCS Central you can publish, or push, global VLANs, and VSANs down to the Cisco UCS domains. You no longer have to configure and associate a global service profile to deliver a globally defined VLAN or VSAN.

Cisco UCS Central makes all applicable global VLANs and VSANs available for publishing to the registered Cisco UCS domain.


Note

This assumes that the global VLANs or VSANs are available to the domain group. You can automate the publishing of the global VLAN or VSAN with either direct API integration or the use of Cisco UCS Central CLI. This functionality is not available through the UI.

Publishing VLANs and VSANs Manually

The following CLI code shows an example of publishing a VLAN and a VSAN manually. It first queries the system for publishable VLANs and VSANs, and then publishes the VLAN.


Note

This mechanism is only for publishing. The VLAN or VSAN must have been previously created in Cisco UCS Central. 

UCSC-A# connect resource-mgr 
UCSC-A(resource-mgr)# scope domain-mgmt 
UCSC-A(resource-mgr) /domain-mgmt # show ucs-domain 
UCSC-A(resource-mgr) /domain-mgmt # scope ucs-domain 1008
UCSC-A(resource-mgr) /domain-mgmt/ucs-domain # publish ?
vlan vlan-name
vsan Vsan

Deleting Global VLANs

When you delete VLANs, make sure that the VLAN does not reference any vNIC template or LAN connectivity policy. Also make sure that no service profile uses that global VLAN. If you choose to delete a global VLAN, make sure that you delete its organization permissions first, prior to deleting the global VLAN.

Global VLANs and VSANs Persisting Locally

Once you push global VLANs and VSANs down to a UCS domain, they persist there, even if you disassociate them from the global service profile. This is by design. If you are not going to use the global VLAN or VSAN again, and you wish to delete the deployed VLAN or VSAN in the UCS domain, use the Make Local function for the specific VLAN or VSAN. Once it is localized, then you can delete the VLAN or VSAN.

Once a domain is deregistered, Cisco UCS Central converts all global VLANs, VSANs, policies, and service profiles to local objects, as long as you are NOT using the Deep Remove Global feature. You can use Deep Remove Global during deregistration. It removes all global objects from the Cisco UCS domain.

Note

Consult Cisco TAC before deregistering a product UCS Domain from UCS Central.

FCoE VLAN ID Conflicts

When you create new global VSANs from the SAN cloud, the default FCoE VLAN ID value is 1. This is in conflict with the global default VLAN ID value.

Change the FCoE VLAN ID when creating new global VSANs, and specify a VLAN ID that is not currently in use.

Deploying Global VLANS and VSANS from the CLI

You can deploy global VLANs and VSANs to a UCS domain without using a global service profile to deliver them. This feature is only available with the CLI. It can benefit those customers using local service profiles, who want to utilize and access global objects from Cisco UCS Central.

Manually Publishing a Global VLAN from the CLI

Type the following commands, in the CLI, to publish a global VLAN to a UCS domain:

Before You Begin

Create the global VLAN Cisco UCS Central.

    Step 1   # connect resource-mgr
    Step 2   # scope domain-mgmt
    Step 3   # show ucs-domain

    Displays the UCS domain IDs for use with the next command.

    Step 4   # scope ucs-domain [domain_name]
    Step 5   # publish vlan [vlan_name]

    Manually Publishing a Global VSAN from the CLI

    Type the following commands, in the CLI, to publish a global VLAN to a UCS domain:

    Before You Begin

    Create the global VSAN Cisco UCS Central.

      Step 1   # connect resource-mgr
      Step 2   # scope domain-mgmt
      Step 3   # show ucs-domain

      Displays the UCS domain IDs for use with the next command.

      Step 4   # scope ucs-domain [domain_name]
      Step 5   # publish vsan [vsan_name] [fabric]

      Designate the intended Fabric with either an a or b at the end of the command.

      CLI Troubleshooting Commands

      The following CLI commands are the most common and helpful commands used for troubleshooting.

      Show Disk Speed

      # show disk-speed
      
/dev/mapper/VolGroup00-LogVol00:
Timing cached reads:  12606 MB in 2.00 seconds = 6317.87 MB/sec
Timing buffered disk reads: 106 MB in 3.01 seconds = 35.21 MB/sec

/dev/mapper/VolGroup01-LogVol00:
Timing cached reads:  12600 MB in 2.00 seconds = 6315.33 MB/sec
Timing buffered disk reads: 320 MB in 3.00 seconds = 109.28 MB/sec

      Show Disk Usage

      # show disk-usage
      
Filesystem   			Size Used Avail Use%  Mounted on
/dev/mapper/VolGroup00-LogVol00:
																37G			3.2G	32G		10%		/
/dev/sda1							99M			13M		81M		14%  /boot				

/dev/mapper/VolGroup01-LogVol00:
																39G			177M	37G		1%		/bootflash
tmpfs											5.9G		728K	5.9G	1%  /dev/shm

      Show Registered Domain IDs

      # connect service-reg
      
Cisco UCS Central
TAC support: http://www.cisco.com/tac
.
.
.

      # show clients
      
Registered Clients:
	ID: 1008
	Registered Client IP: 172.22.251.106
	Registered Client IPv6:  ::
	Registered Client Connection Protocol: Ipv4
	Registered Client Name: L14-UCS1
	Registered Client Type: Managed Endpoint

	ID: 1009
	Registered Client IP: 172.22.251.10
 Registered Client IPv6:  ::
	Registered Client Connection Protocol: Ipv4
	Registered Client Name: SJC18-L12-UCS1
	Registered Client Type: Managed Endpoint