- Preface
- New and Changed Information for this Release
- Overview
- Managing Users and Groups
- Setting Up the End User Portal
- Managing System Administration Settings
- Managing Integration Settings
- Managing a Physical Infrastructure
- Managing a Virtual Infrastructure
- Managing Policies
- Managing Virtual Data Centers
- Managing Catalogs
- Using Self-Service Provisioning
- Multiple Disk VM Provisioning
- Using the Chargeback Module
- System Monitoring and Reporting
- Managing Lifecycles
- Managing CloudSense Analytics
- Managing VM Power Settings
- Managing VM Snapshots
- Configuring the Lease Time for a Virtual Machine
- Managing VM Actions
- Viewing VM Details
- Resizing VMs
- Using the Stack View Option
- Creating a VM Disk
- Resizing a VM Disk
- Locking VMs in Cisco UCS Director
- Adding vNICs
- Replacing a vNIC
- Launching the VM Client
- Enabling the VNC Console on a VM
- Accessing VM Console using VNC Client
- Configuring ESX/ESXi Server for VNC Access to VM Console
- Assigning a VM
- VM Credentials
- Initiating Inventory Collection for a VM
- Testing VNC Connectivity
- Cloning a VM
- Moving a VM to VDC
- Resynchronizing a VM
- Applying a Tag to a VM
Managing
Lifecycles
This chapter contains the following sections:
- Managing VM Power Settings
- Managing VM Snapshots
- Configuring the Lease Time for a Virtual Machine
- Managing VM Actions
- Applying a Tag to a VM
Managing VM Power Settings
You must be logged in to the appliance to complete this task.
Managing VM Snapshots
This process includes the following tasks:
-
Create Snapshot—You can create a snapshot of all the VM’s resources in their current state.
-
Revert Snapshot—If the VM crashes or malfunctions (For example, if the OS becomes corrupt), you can revert to the most recent snapshot of the VM. Where there are multiple snapshots for a VM, you can revert to a specific snapshot.
-
Mark Golden Snapshot—You can mark a specific snapshot for a VM as a Golden Snapshot. This feature protects the snapshot from accidental deletion.
-
Delete a Snapshot—You can delete a snapshot, if necessary. A Golden Snapshot must be first unmarked before it can be deleted.
-
Delete All Snapshots—You can delete all snapshots for a VM. However, you cannot delete all snapshots if they include Golden Snapshots. You must first unmark any Golden Snapshot and then delete all snapshots.
- Creating VM Snapshots
- Reverting to a Snapshot
- Marking a Golden Snapshot
- Deleting a Snapshot
- Deleting All Snapshots
Creating VM Snapshots
| Step 1 | On the menu bar, choose . | ||||||||||||
| Step 2 | Choose a cloud name. | ||||||||||||
| Step 3 | Choose the VMs tab. | ||||||||||||
| Step 4 | Choose a VM and click the down arrow option displayed on the right side of the toolbar. | ||||||||||||
| Step 5 | From the drop-down list, choose Create Snapshot. | ||||||||||||
| Step 6 | In the
Create
Virtual Machine Snapshot dialog box, complete the following fields:
| ||||||||||||
| Step 7 | Click Proceed. |
Reverting to a Snapshot
You must be logged in to the appliance to complete this task.
| Step 1 | On the menu bar, choose . |
| Step 2 | Choose the cloud name. |
| Step 3 | Choose the VMs tab. |
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. |
| Step 5 | From the drop-down list, choose Revert Snapshot. |
| Step 6 | In the Revert Snapshot Task dialog box, choose a snapshot from the list by checking the check box that is next to the snapshot name. |
| Step 7 | Click Proceed. |
Marking a Golden Snapshot
| Step 1 | On the menu bar, choose . |
| Step 2 | Choose the cloud name. |
| Step 3 | Choose the VMs tab. |
| Step 4 | Choose a VM and click the down arrow option displayed on the right side of the toolbar. |
| Step 5 | From the drop-down list, choose Mark Golden Snapshot. |
| Step 6 | In the Mark Golden Snapshot Task dialog box, check the check box next to the name of the desired snapshot. |
| Step 7 | Check the Mark as Golden Snapshot check box. |
| Step 8 | Click Proceed. |
Deleting a Snapshot
| Step 1 | On the menu bar, choose . |
| Step 2 | Choose the cloud name. |
| Step 3 | Choose the VMs tab. |
| Step 4 | Choose a VM and click the down arrow option displayed on the right side of the toolbar. |
| Step 5 | From the drop-down list, choose Delete Snapshot. |
| Step 6 | In the Delete Snapshot Task dialog box, check the check box next to the name of the desired snapshot. |
| Step 7 | Check the Delete Children check box to delete child snapshots of the selected snapshot. |
| Step 8 | Click Proceed. |
Deleting All Snapshots
| Step 1 | On the menu bar, choose . |
| Step 2 | Choose the cloud name. |
| Step 3 | Choose the VMs tab. |
| Step 4 | Choose a VM and click the down arrow option displayed on the right side of the toolbar. |
| Step 5 | From the drop-down list, choose Delete All Snapshots. |
| Step 6 | In the VM Snapshot Task dialog box, enter an optional comment. |
| Step 7 | Click Proceed. |
Configuring the Lease Time for a Virtual Machine
A user can configure a lease expiration time for a selected virtual machine (VM). Once the lease time expires, the VM is powered down. The lease time end is a calendar selection.
| Step 1 | On the menu bar, choose . | ||||||
| Step 2 | Choose the cloud name. | ||||||
| Step 3 | Choose the VMs tab. | ||||||
| Step 4 | Choose a VM. | ||||||
| Step 5 | On the toolbar, click the Configure Lease Time button. | ||||||
| Step 6 | In the
Configure
Lease Time dialog box, check the
Set
Lease Time check box. Complete the following fields:
| ||||||
| Step 7 | Click Submit. |
Managing VM Actions
After creating a VM, you can perform additional tasks on it, by using menus available in the user interface. You can access these menus in one of the following ways:
-
Right clicking on a VM to view a list of limited options,
-
Choosing a VM and clicking the down arrow option on the toolbar for a complete list of options.
Following are the other VM actions:
-
View VM Details—You can access individual VMs to view details, such as summary reports, vNICs, disks, and snapshots.
-
Stack View—You can view stacks of information about a particular VM including, OS, hypervisor, and infrastructure information.
-
Delete a VM—You can delete a VM from the list. Only a powered-off VM can be deleted.
-
Create a VM Disk—You can add an additional disk with a custom size to a VM.
-
Delete a VM Disk—You can delete a disk.
-
Add vNICs—You can add multiple vNICs to a VM. You also have the option to add or replace a vNIC in a VM. The options for vNICs depend on the network policy mapped to the VDC associated with the VM.
-
Launch VM Client—You can set up either web access, remote desktop, or VNC console preferences for a VM.
-
Assign VM—You can assign a VM to a group or VDC and modify the category of the VM. You can set the provisioning time, termination time, and label for a VM.
-
Access VM Credentials—You can access a VM’s login credentials when it is set up for web or remote desktop access, but only if the administrator provides the privileges in the catalog from which the VM is provisioned.
-
Inventory Collection Request for VM—You can choose a VM and request on-demand inventory collection.
-
Test VNC—You can test VNC connectivity, for troubleshooting purposes.
-
Clone—You can clone or make a copy of an existing VM to make a new VM with the same or similar qualities.
-
Move a VM to VDC—You can move a VM to a VDC so that the rules of the VDC system policy are followed in the VM.
-
VM Resync—You can choose to set the number of minutes to have a VM resynchronize its time periodically with Cisco UCS Director.
- Viewing VM Details
- Resizing VMs
- Using the Stack View Option
- Creating a VM Disk
- Resizing a VM Disk
- Locking VMs in Cisco UCS Director
- Adding vNICs
- Replacing a vNIC
- Launching the VM Client
- Enabling the VNC Console on a VM
- Accessing VM Console using VNC Client
- Configuring ESX/ESXi Server for VNC Access to VM Console
- Assigning a VM
- VM Credentials
- Initiating Inventory Collection for a VM
- Testing VNC Connectivity
- Cloning a VM
- Moving a VM to VDC
- Resynchronizing a VM
Viewing VM Details
Resizing VMs
| Step 1 | On the menu bar, choose . | ||||||||||||||||||||
| Step 2 | Choose the cloud name. | ||||||||||||||||||||
| Step 3 | Choose the VMs tab. | ||||||||||||||||||||
| Step 4 | Choose a VM and click the down arrow button displayed on the right side of the toolbar. | ||||||||||||||||||||
| Step 5 | From the drop-down list, choose Resize VM. | ||||||||||||||||||||
| Step 6 | In the
Resize
VM dialog box, complete the following fields:
| ||||||||||||||||||||
| Step 7 | Click Resize. |
Using the Stack View Option
Creating a VM Disk
| Step 1 | On the menu bar, choose . | ||||||||||||||||||||||||
| Step 2 | In the navigation pane, choose a cloud name. | ||||||||||||||||||||||||
| Step 3 | Choose the VMs tab. | ||||||||||||||||||||||||
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. | ||||||||||||||||||||||||
| Step 5 | Click the down arrow button on the right side of the toolbar, and choose Create VM Disk from the drop-down list. | ||||||||||||||||||||||||
| Step 6 | In the
Create VM Disk dialog box, complete the
following fields:
| ||||||||||||||||||||||||
| Step 7 | Click Create. |
Resizing a VM Disk
| Step 1 | On the menu bar, choose . | ||||||||||||||||
| Step 2 | Choose the cloud name. | ||||||||||||||||
| Step 3 | Choose the VMs tab. | ||||||||||||||||
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. | ||||||||||||||||
| Step 5 | From the drop-down list, choose Resize VM Disk. | ||||||||||||||||
| Step 6 | In the
Resize VM Disk dialog box, complete the
following fields:
| ||||||||||||||||
| Step 7 | Click Resize. |
Locking VMs in Cisco UCS Director
As an administrator in Cisco UCS Director, you can create a list of VMs that you would like locked. Locking VMs implies preventing actions from running on the specified VMs. These actions could be shutting down, resetting, or powering off VMs.
| Step 1 | Create an XML
file titled
VMControls.xml which is similar to the
following:
<VMControlList>
--<VMControl>
<ControlType>lock</ControlType>
<MatchType>VM-IPAddress</MatchType>
<MatchValue>19.19.19.19</MatchValue>
<IsRegex>false</IsRegex>
<ContactEmail>admin@admin.com</ContactEmail>
--<Label>
Do not shutdown or delete my machine.
--</Label>
--</VMControl>
--<VMControl>
<ControlType>lock</ControlType>
<MatchType>VM-IPAddress</MatchType>
<MatchValue>19.29.29.29*</MatchValue>
<IsRegex>true</IsRegex>
<ContactEmail>admin@admin.com</ContactEmail>
--<Label>
Do not shutdown or delete this machine.
--</Label>
--</VMControl>
</VMControlList>
|
| Step 2 | Host this file on a server that is accessible from the system that is running Cisco UCS Director. |
| Step 3 | On the menu bar, choose . |
| Step 4 | Choose the System Parameters tab. |
| Step 5 | In the
Download
VM Locking Controls From URL field, enter the URL of the XML file.
The URL will look similar to this: <ip_address>:8000/VMControls.xml. |
| Step 6 | Click Save. |
| Step 7 | Choose the System Tasks tab. |
| Step 8 | Search for and select the VM Control List Poller Task. |
| Step 9 | Click
Run
Now.
This system task downloads the VMControls.xml file and saves it in the inventory database. After this system task is run, actions such as powering off, or shutting down are prevented from running on VMs that match the IP addresses specified in the XML file. |
Adding vNICs
![]() Note | When you add a vNIC VM, the values of the Port Group Name and Adapter Type parameters are modified. The IP address of the VM is changed only if DHCP is enabled on the selected port group. However, the IP address is not modified if it is sourced from a static pool policy. |
| Step 1 | On the menu bar, choose . | ||||||||||||||||||||
| Step 2 | Choose the cloud name. | ||||||||||||||||||||
| Step 3 | Choose the VMs tab. | ||||||||||||||||||||
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. | ||||||||||||||||||||
| Step 5 | From the drop-down list, choose Add vNICs. | ||||||||||||||||||||
| Step 6 | In the
Add VM
vNICS window, choose
Add from the
Operation drop-down list.
This addition is not allowed if the vNIC limit configured in the network policy will be exceeded. | ||||||||||||||||||||
| Step 7 | Click Add (+). | ||||||||||||||||||||
| Step 8 | In the
Add Entry
to VM Networks dialog box, complete the following fields:
| ||||||||||||||||||||
| Step 9 | Click Submit. |
Replacing a vNIC
![]() Note | When you replace a vNIC VM, the values for the Port Group Name and Adapter Type parameters are modified. The IP address of the VM is changed only if DHCP is enabled on the selected port group. However, the IP address is not modified if it is sourced from a static pool policy. |
| Step 1 | On the menu bar, choose . | ||||||||||||||||
| Step 2 | Choose the cloud name. | ||||||||||||||||
| Step 3 | Choose the VMs tab. | ||||||||||||||||
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. | ||||||||||||||||
| Step 5 | From the drop-down list, choose Add vNICs. | ||||||||||||||||
| Step 6 | In the
Add VM
vNICS window, choose
Replace from the
Operation drop-down list.
This replacement is not allowed if the additional vNIC limit configured in the network policy will be exceeded. | ||||||||||||||||
| Step 7 | Choose a vNIC. | ||||||||||||||||
| Step 8 | In the
Add
vNIC dialog box, complete the following fields:
| ||||||||||||||||
| Step 9 | Click
Submit.
|
Launching the VM Client
| Step 1 | On the menu bar, choose . |
| Step 2 | Choose the cloud name. |
| Step 3 | Choose the VMs tab. |
| Step 4 | Choose a VM from the list. |
| Step 5 | On the toolbar, choose Launch VM Client. |
| Step 6 | In the
Launch
Client dialog box, choose an access scheme for the VM Client.
If a VM is provisioned through Cisco UCS Director, the access schemes displayed in this dialog box are defined by the options enabled in the catalog used to provision the VM. For a VM that is discovered, the options, Remote Desktop, Web Access, VMRC Console (Browser Plug-in), and VMRC Console (Standalone Plug-in) are displayed. The VNC Console option is displayed only if you have chosen the Configure VNC Console option for the VM. |
| Step 7 | Click Proceed. |
Enabling the VNC Console on a VM
| Step 1 | On the menu bar, choose . |
| Step 2 | Choose the cloud name. |
| Step 3 | Choose the VMs tab. |
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. |
| Step 5 | From the drop-down list, choose Configure VNC. |
| Step 6 | In the Configure VNC dialog box, choose a keyboard mapping language from the drop down. |
| Step 7 | Click Submit. |
| Step 8 | Click
OK.
The system automatically configures VNC console access to a VM when a request is submitted. |
Accessing VM Console using VNC Client
The VNC client is an Ajax-based application that provides access to a VM console. The console window can be launched by using any standalone web browser. It does not require a dedicated browser plug-in and it provides full VM control capabilities. However, you must disable pop-up blockers in the browser for the VNC console to launch.
![]() Note | If the access to a VM is secured through the https protocol, the VNC console does not launch in Internet Explorer. For accessing VMs secured through the https protocol, use the Chrome or Firefox browser to launch the VNC console. |
-
You must configure ESX/ESXi server for VNC access to VM console. For information on how to do this, see Configuring ESX/ESXi Server for VNC Access to VM Console.
-
Cisco UCS Director provides automatic configuration of the VM console access using VNC client. To configure, you must open ports 5901-6000 in the ESX/ESXi server to the Cisco UCS Director appliance.
-
Import a self-signed certificate or a CA certificate using Cisco UCS Director admin shell. Importing a certificate enables secured access to the VM console using the VNC client. For more information on importing certificates, see the Cisco UCS Director Shell Guide available at the following link:
-
Disable pop-up blockers in your browser.
![]() Note | VMware with ESX 4.x and ESXi 5.x versions is supported for configuring VM console access using the VNC client. |
| Step 1 | On the menu bar, choose . | ||
| Step 2 | Choose the cloud name. | ||
| Step 3 | Choose the VMs tab. | ||
| Step 4 | Choose a VM from the list. | ||
| Step 5 | On the toolbar, choose Launch VM Client. | ||
| Step 6 | In the
Launch
Client dialog box, choose
VNC
Console as the Access Schema.
| ||
| Step 7 | Click
Proceed.
|
Configuring ESX/ESXi Server for VNC Access to VM Console
VMware with ESX 4.x and ESXi 5.x versions is supported to configure VNC access to the VM console.
| Step 1 | Log in to ESXi5.x host. | ||
| Step 2 | Using the shell, disable the firewall configuration. | ||
| Step 3 | Copy and paste
the following XML configuration to the
vnc.xml file.
# cat /etc/vmware/firewall/vnc.xml
<!-- Firewall configuration information for VNC -->
<ConfigRoot>
<service>
<id>VNC</id>
<rule id='0000'>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>
<begin>5901</begin>
<end>6000</end>
</port>
</rule>
<rule id='0001'>
<direction>outbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>
<begin>0</begin>
<end>65535</end>
</port>
</rule>
<enabled>true</enabled>
<required>false</required>
</service>
</ConfigRoot>
| ||
| Step 4 | Refresh the
firewall rules and verify that the new configuration is accurately loaded.
~ # esxcli network firewall refresh ~ # esxcli network firewall ruleset list | grep VNC VNC true #**************************************** | ||
| Step 5 | Repeat these steps on all ESXi hosts in an ESXi cluster. |
Assigning a VM
You can assign a resource or a VM to a user group. If the resource or VM is in a VMWare cloud, then you can also assign it to a specific end user in Cisco UCS Director.
| Step 1 | On the menu bar, choose . | ||||||||||||||||||||||||||||||||||||
| Step 2 | Choose the cloud name. | ||||||||||||||||||||||||||||||||||||
| Step 3 | Click the VMs tab. | ||||||||||||||||||||||||||||||||||||
| Step 4 | Choose a VM from the list. | ||||||||||||||||||||||||||||||||||||
| Step 5 | On the toolbar, click the Assign VM button. | ||||||||||||||||||||||||||||||||||||
| Step 6 | In the
Assign
VM dialog box, complete the following fields:
| ||||||||||||||||||||||||||||||||||||
| Step 7 | Click Assign. | ||||||||||||||||||||||||||||||||||||
| Step 8 | Click OK. | ||||||||||||||||||||||||||||||||||||
VM Credentials
The web or remote access login credentials for a VM can only be viewed if the administrator provides the necessary privileges in the Catalog from which the VM is provisioned.
Viewing VM Credentials
You must be logged in to the appliance to complete this task.
Initiating Inventory Collection for a VM
Testing VNC Connectivity
Testing VNC connectivity is used for troubleshooting purposes. A successful test for VNC connectivity displays the host node IP address and VNC port number. For example: VNC connectivity intact at 172.16.0.1:5921.
However if connectivity fails, a failure message displays. For example: VM is not configured for VNC yet.
| Step 1 | On the menu bar, choose . | ||
| Step 2 | Choose the cloud name. | ||
| Step 3 | Choose the VMs tab. | ||
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. | ||
| Step 5 | From the drop-down list, choose Test VNC. | ||
| Step 6 | In the Test VNC Connectivity dialog box, click Submit. | ||
| Step 7 | Use the result
to troubleshoot VNC connectivity.
|
Cloning a VM
Cloning a VM allows you to create a new VM in the system, by using some of the parameters defined in an existing VM. The cloning option helps you create a VM faster, especially if you need to modify only a few parameters of an existing VM. The name that you specify for the cloned VM is defined by the system policy.
| Step 1 | On the menu bar, choose . | ||||||||||||||||||||||||||||
| Step 2 | Choose the cloud name. | ||||||||||||||||||||||||||||
| Step 3 | Choose the VMs tab. | ||||||||||||||||||||||||||||
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. | ||||||||||||||||||||||||||||
| Step 5 | From the drop-down list, choose Clone. | ||||||||||||||||||||||||||||
| Step 6 | In the
Clone
VM dialog box, complete the following fields:
| ||||||||||||||||||||||||||||
| Step 7 | Click Next. | ||||||||||||||||||||||||||||
| Step 8 | In the
Customization Options pane, complete the following
fields:
| ||||||||||||||||||||||||||||
| Step 9 | Click Next. | ||||||||||||||||||||||||||||
| Step 10 | In the
Deployment Configuration pane, complete the following
fields:
| ||||||||||||||||||||||||||||
| Step 11 | Click Next. | ||||||||||||||||||||||||||||
| Step 12 | In the
Custom
Specification pane, complete the following fields:
| ||||||||||||||||||||||||||||
| Step 13 | Click Next. | ||||||||||||||||||||||||||||
| Step 14 | In the
Select
Datastores pane, complete the following field:
| ||||||||||||||||||||||||||||
| Step 15 | In the
Edit VM
Disks Entry pane, complete the following fields:
| ||||||||||||||||||||||||||||
| Step 16 | Click Submit. | ||||||||||||||||||||||||||||
| Step 17 | Click Next. | ||||||||||||||||||||||||||||
| Step 18 | In the
Select
VM Networks pane, click the
VM Networks pencil icon to edit a VM network.
| ||||||||||||||||||||||||||||
| Step 19 | In the Select dialog box, choose the cloud(s) that you want associated with the VM. | ||||||||||||||||||||||||||||
| Step 20 | Click Submit. | ||||||||||||||||||||||||||||
| Step 21 | If you checked
the
Perform deployment assessment check box, then review
the report of the assessment displayed in the
Deployment Assessment pane.
If this assessment report identifies errors, then you must return to the previous panes and rectify the errors before submitting the request. If the assessment report shows no errors, then click Next. | ||||||||||||||||||||||||||||
| Step 22 | Review the cloned VM information in the Summary pane. | ||||||||||||||||||||||||||||
| Step 23 | Click
Submit.
The cloned VM gets its new name from the VDC policy. |
Moving a VM to VDC
A VM is moved to a VDC so that the rules of the VDC system policy are followed in the VM. The existing VM is replaced by the one that is moved to the VDC.
![]() Note | The old VM is deleted. The new VM name is given according to the system policy. |
You must be logged in to the appliance to complete this task.
| Step 1 | On the menu bar, choose . |
| Step 2 | Choose the cloud name. |
| Step 3 | Choose the VMs tab. |
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. |
| Step 5 | From the drop-down list, choose Move VM to VDC. |
| Step 6 | In the Move VM to VDC dialog box, you can make modifications to the VM that you are moving in the same way you did when cloning a VDC. For more information, see Cloning a VM. |
Resynchronizing a VM
You must be logged in to the appliance to complete this task.
| Step 1 | On the menu bar, choose . |
| Step 2 | Choose the cloud name. |
| Step 3 | Choose the VMs tab. |
| Step 4 | Choose a VM and click the down arrow button on the right side of the toolbar. |
| Step 5 | From the drop-down list, choose Resync VM. |
| Step 6 | In the Resync VM dialog box, choose the number of minutes from 0 to 30 from the Max Wait Time drop-down list. |
| Step 7 | Click Submit. |
Applying a Tag to a VM
With the introduction of tagging support for a VM, you can manage tags in Cisco UCS Director to categorize and identify specific VMs as firewall VMs or as load balancer VMs.
| Step 1 | On the menu bar, choose . | ||||||
| Step 2 | Choose the cloud name. | ||||||
| Step 3 | Choose the VMs tab. | ||||||
| Step 4 | Choose a VM from the table. | ||||||
| Step 5 | On the tool bar, choose Add Tags. | ||||||
| Step 6 | In the
Add Tags dialog box, complete the following
fields:
| ||||||
| Step 7 | Click Submit. |
What to Do Next
You can create a tag-based cost model for the VMs. For more information, see Creating a Tag-Based Cost Model.

Feedback