Chapter 1. Overview

Cisco UCS Director

Features and Benefits

Physical and Virtual Management Features

POODLE Vulnerability

Cisco UCS Director for VMware vSphere

Prerequisites

Minimum System Requirements for a Single-Node Setup

About Licenses

Fulfilling the Product Access Key

Upgrading a Single Node

Chapter 2. Installing Cisco UCS Director

Installing Cisco UCS Director on VMware vSphere

Configuring the Network Interface using Shelladmin

Changing the Default Password

Updating the License

Reserving System Resources

Changing the Maximum Packet Size

Chapter 3. Restarting Cisco UCS Director

Restarting Cisco UCS Director

Appendix A. Ports

Cisco UCS Director TCP and UDP Port Usage

Port List

Multi-Node Port Requirements

Preface

Audience

Conventions

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. Overview

This chapter contains the following sections:

- Cisco UCS Director

- Cisco UCS Director for VMware vSphere

- Prerequisites

- Minimum System Requirements for a Single-Node Setup

- About Licenses

- Upgrading a Single Node

Cisco UCS Director

Cisco UCS Director is a complete, highly secure, end-to-end management, orchestration, and automation solution for a wide array of Cisco and non-Cisco data infrastructure components, and for the industry's leading converged infrastructure solutions based on the Cisco UCS and Cisco Nexus platforms. For a complete list of supported infrastructure components and solutions, see the Cisco UCS Director Compatibility Matrix.

Cisco UCS Director is a 64-bit appliance that uses the following standard templates:

- Open Virtualization Format (OVF) for VMware vSphere

- Virtual Hard Disk (VHD) for Microsoft Hyper-V

Management through Cisco UCS Director

Cisco UCS Director extends the unification of computing and network layers through Cisco UCS to provide you with comprehensive visibility and management of your data center infrastructure components. You can use Cisco UCS Director to configure, administer, and monitor supported Cisco and non-Cisco components. The tasks you can perform include the following:

- Create, clone, and deploy service profiles and templates for all Cisco UCS servers and compute applications.

- Monitor organizational usage, trends, and capacity across a converged infrastructure on a continuous basis. For example, you can view heat maps that show virtual machine (VM) utilization across all your data centers.

- Deploy and add capacity to converged infrastructures in a consistent, repeatable manner.

- Manage, monitor, and report on data center components, such as Cisco UCS domains or Cisco Nexus network devices.

- Extend virtual service catalogs to include services for your physical infrastructure.

- Manage secure multi-tenant environments to accommodate virtualized workloads that run with non-virtualized workloads.

Automation and Orchestration with Cisco UCS Director

Cisco UCS Director enables you to build workflows that provide automation services, and to publish the workflows and extend their services to your users on demand. You can collaborate with other experts in your company to quickly and easily create policies. You can build Cisco UCS Director workflows to automate simple or complex provisioning and configuration processes.

Once built and validated, these workflows perform the same way every time, no matter who runs the workflows. An experienced data center administrator can run them, or you can implement role-based access control to enable your users and customers to run the workflows on a self-service, as needed, basis.

With Cisco UCS Director, you can automate a wide array of tasks and use cases across a wide variety of supported Cisco and non-Cisco hardware and software data center components. A few examples of the use cases that you can automate include, but are not limited to:

- VM provisioning and lifecycle management

- Network resource configuration and lifecycle management

- Storage resource configuration and lifecycle management

- Tenant onboarding and infrastructure configuration

- Application infrastructure provisioning

- Self-service catalogs and VM provisioning

- Bare metal server provisioning, including installation of an operating system

- Features and Benefits

- Physical and Virtual Management Features

- POODLE Vulnerability

Features and Benefits

The features and benefits of Cisco UCS Director are as follows:

Feature

Benefit

Central management

- Provides a single interface for administrators to monitor, provision, and manage the system across physical, virtual, and bare metal environments

- Provides unified dashboards, reports, and heat maps, which reduce troubleshooting and performance bottlenecks

Self-service catalog

- Allows end users to order and deploy new infrastructure instances following IT-prescribed policies and governance

Adaptive provisioning

- Provides a real-time available capability, internal policies, and application workload requirements to optimize the availability of your resources

Dynamic capacity management

- Provides continuous monitoring that indicates real-time infrastructure consumption to improve capacity planning and management

- Identifies underutilized and overutilized resources

Multiple hypervisor support

- Supports VMware ESX, ESXi, Microsoft Hyper-V, and Red Hat hypervisors

Computing management

- Monitors, manages, and provisions physical, virtual, and bare metal servers, as well as blades

- Allows end users to implement virtual machine life-cycle management and business continuance through snapshots

- Allows administrators to access server utilization trending analysis

Network management

- Provides policy-based provisioning of physical and virtual switches and dynamic network topologies

- Allows administrators to configure VLANs, virtual network interface cards (vNICs), port groups and port profiles, IP and Dynamic Host Control Protocol (DHCP) allocation, and access control lists (ACLs) across network devices

Storage management

- Provides policy-based provisioning and management of filers, virtual filers (vFilers), logical unit numbers (LUNs), and volumes

- Provides unified dashboards that allow administrators comprehensive visibility into organizational usage, trends, and capacity analysis details.

Physical and Virtual Management Features

Physical Server Management

- Discover and collect configurations and changes

- Monitor and manage physical servers

- Perform policy-based server provisioning

- Manage blade power

- Manage the server life cycle

- Perform server use trending and capacity analysis

- Perform bare metal provisioning using preboot execution environment (PXE) boot management

Virtual Computing Management

- Discover, collect, and monitor virtual computing environments

- Perform policy-based provisioning and dynamic resource allocation

- Manage the host server load and power

- Manage the VM life cycle and snapshots

- Perform analytics to assess VM capacity, sprawl, and host utilization

Physical Storage Management

- Discover, collect, and monitor storage filers

- Perform policy-based provisioning of vFilers

- Provision and map volumes

- Create and map Logical Unit Number (LUN) and iGroup instances

- Perform SAN zone management

- Monitor and manage network-attached storage (NAS) and SAN-based storage

- Implement storage best practices and recommendation

Virtual Storage Management

- Discover, collect, and monitor storage of vFilers and storage pools

- Perform policy-based storage provisioning for thick and thin clients

- Create new datastores and map them to virtual device contexts (VDCs)

- Add and resize disks to VMs

- Monitor and manage organizational storage use

- Perform virtual storage trend and capacity analysis

Physical Network Management

- Discover, collect, and monitor physical network elements

- Provision VLANs across multiple switches

- Configure Access Control Lists (ACLs) on network devices

- Configure the storage network

- Implement dynamic network topologies

Virtual Network Management

- Add networks to VMs

- Perform policy-based provisioning with IP and DHCP allocation

- Configure and connect Virtual Network Interface Cards ( vNICs) to VLANs and private VLANs

- Create port groups and port profiles for VMs

- Monitor organizational use of virtual networks

POODLE Vulnerability

To avoid POODLE vulnerability, SSL Version 2 and SSL Version 3 are disabled on Cisco UCS Director north-bound HTTP interface by configuring Apache Tomcat to allow only TLS . Hence, any north-bound applications accessing Cisco UCS Director through REST API will be connected through TLS. Also, the browsers will be connected to Cisco UCS Director through TLS. For more information, refer Click Here .

Cisco UCS Director for VMware vSphere

Cisco UCS Director can be hosted on VMware vSphere or vCenter as well as HyperV Manager.

Note

The appliance and boot-up logs are located in the /var/log/ucsd directory.

- install.log contains the one time appliance installation logs.

- bootup.log contains the appliance boot-up sequence information, such as startup messages for the database and infrastructure services.

Prerequisites

- Installation of VMware vSphere or vCenter

- Configure a user account with system administrator privileges on VMware vCenter

- Cisco UCS Director deployed on a VMware vSphere host

Minimum System Requirements for a Single-Node Setup

The minimum system requirements depend on the number of VMs you plan to manage. We recommend deploying a Cisco UCS Director VM on a local datastore with a minimum of 25 MBps I/O speed, or on an external datastore with a minimum of 50 MBps I/O speed.

Note

- For optimal performance, reserve additional CPU and memory resources. We recommend that you reserve the following resources in addition to the minimum system requirements listed in the tables below: CPU resources of more than or equal to 3000MHz, and memory reservation of more than or equal to 4GB. You should add more vCPUs if the Cisco UCS Director VM’s CPU usage is consistently high.

- The minimum memory required for the inframgr service is automatically set during deployment. However, if you want to modify the memory for the inframgr service, edit the inframgr.env file available in the following location:

/opt/infra/bin/inframgr.env

In this file, update the "MEMORY_MAX" parameter to the value you want. After changing this parameter, restart the service for the changes to take effect. The default memory settings are MEMORY_MIN=128m and MEMORY_MAX=6144m.

For information about minimum system requirements for a multi-node setup, see the Cisco UCS Director Multi-Node Installation and Configuration Guide.

Up to 2,000 VMs

If you plan to manage up to 2,000 VMs, the Cisco UCS Director environment must meet at least the minimum system requirements in the following table.

Minimum System Requirements for up to 2,000 VMs

Element

Minimum Supported Requirement

vCPU

4

Memory

12 GB

Hard Disk

100 GB

Up to 5,000 VMs

If you plan to manage no more than 5,000 VMs, the Cisco UCS Director environment must meet at least the minimum system requirements and recommended configurations in the following tables.

Minimum System Requirements for up to 5,000 VMs

Element

Minimum Supported Requirement

vCPU

8

Memory

20 GB

Hard Disk

100 GB

Minimum Database Configuration

Element

Minimum Supported Configuration

thread_cache_size

100

max_connections

1000

innodb_lock_wait_timeout

100

query_cache_size

128 MB

innodb_buffer_pool_size

4096 MB

max_connect_errors

10000

connect_timeout

20

innodb_read_io_threads

64

innodb_write_io_threads

64

About Licenses

You must obtain a license to use Cisco UCS Director, as follows:

1. Before you install Cisco UCS Director, generate the Cisco UCS Director license key and claim a certificate (Product Access Key).

2. Register the Product Access Key (PAK) on the Cisco software license site, as described in Fulfilling the Product Access Key.

3. After you install Cisco UCS Director, update the license in Cisco UCS Director as described in Updating the License.

4. After the license has been validated, you can start to use Cisco UCS Director.

- Fulfilling the Product Access Key

Fulfilling the Product Access Key

Before You Begin

You need the PAK number.

Step 1

Navigate to the Cisco Software License website.

Step 2

If you are directed to the Product License Registration page, you can take the training or click Continue to Product License Registration.

Step 3

On the Product License Registration page, click Get New Licenses from a PAK or Token.

Step 4

In the Enter a Single PAK or TOKEN to Fulfill field, enter the PAK number.

Step 5

Click Fulfill Single PAK/TOKEN.

Step 6

Complete the additional fields in License Information to register your PAK:

Name

Description

Organization Name

The organization name.

Site Contact Name

The site contact name.

Street Address

The street address of the organization.

City or Town

The city or town.

State or Province

The state or province.

Zip or Postal Code

The zip code or postal code.

Country

The country name.

Step 7

Click Issue Key.
The features for your license appear, and you receive an email with the Digital License Agreement and a zipped license file.

Upgrading a Single Node

For more information on upgrading see Cisco UCS Director Upgrade Guide, Release 5.5.

Chapter 2. Installing Cisco UCS Director

This chapter contains the following sections:

- Installing Cisco UCS Director on VMware vSphere

- Configuring the Network Interface using Shelladmin

- Changing the Default Password

- Updating the License

- Reserving System Resources

- Changing the Maximum Packet Size

Installing Cisco UCS Director on VMware vSphere

Note

We recommend that you use VMware vCenter for OVF deployment. VMware vCenter versions 5.x and above are supported. OVF deployment wizards support only IPv4 addresses. If you require IPv6, you can deploy OVF and use the shelladmin option to configure IPv6 address.

Before You Begin

You need administrator privileges to connect to VMware vCenter. Cisco UCS Director requires a user account with system administrator privileges to discover, manage and automate VMware vCenter configuration from Cisco UCS Director. These operations include creating, deleting and modifying VMs, ESXi hosts and clusters, datastores and datastore clusters, standard and DV switches, and virtual network port groups.

Note

If you do not want to use DHCP, you need the following information: IPv4 address, subnet mask, and default gateway.

Step 1

Log in to VMware vSphere Client.

Step 2

In the Navigation pane, choose the Data Center for Cisco UCS Director deployment.

Step 3

Choose File > Deploy OVF Template.
The Deploy OVF Template window appears.

Step 4

In the Source pane, do one of the following to choose your OVF source location:

- Browse to the location, choose the file, and click Open.

- Deploy from a URL on your local area network. Replace FQDN (Fully Qualified Domain Name) with the IP address or domain name, and click Next.

Step 5

In the OVF Template Details pane, verify the details, and click Next.

Step 6

In the End User License Agreement pane, read the license agreement, and click Accept. Click Next.

Step 7

In the Name and Location pane, do the following:

1. Optional: In the Name field, edit the VM name.

2. From the Inventory Location area, choose the inventory location where Cisco UCS Director is being deployed, and click Next.

Note:   If Data Center was chosen in a previous step, option b is not available.

Step 8

In the Host/Cluster pane, choose the required host, cluster, or resource pool, and click Next.

Step 9

In the Storage pane, choose the location to store Cisco UCS Director VM files, and click Next.

Step 10

In the Disk Format pane, choose one of the following radio buttons and click Next:

- Thick Provisioned (Lazy Zeroed) format—To allocate storage immediately in thick format. This is the recommended option.

- Thick Provisioned (Eager Zeroed) format—To allocate storage in thick format. It might take longer to create disks using this option.

- Thin Provisioned format—To allocate storage on demand as data is written to disk.

Step 11

In the Network Mapping pane, choose your network and click Next.

Step 12

In the Properties pane, enter the following information and click Next:

- Root Password

- Shelladmin Password

- Management IP Address

- Management IP Subnet Mask

- Gateway IP Address

Note:
If the root password and shell admin password are not configured, default values are used.

The management IP address and management IP subnet mask are set to 0.0.0.0 to use DHCP by default.

Step 13

In the Ready to Complete pane, verify the options selected, and click Finish.

Step 14

Make sure you have sufficient vCPU and memory to power on the VM.

Step 15

Power on the VM.
Note:
If the Power on after deployment check box on the Ready to Complete pane is checked, the appliance powers on automatically after deployment.

Step 16

After the appliance has booted up, transfer the Cisco UCS Director IP address (from the IP address that is shown) into a supported web browser to access the Login page.

Step 17

On the Login page, enter admin as the username and admin for the login password.
Note:
Change your admin password after this initial login.

Step 18

On the menu bar, choose Administration > License and click the License Keys tab.

Step 19

Click Manage Personalities.

Step 20

In the Personality Configuration dialog box, check the check box for the required personalities.
You can check either UCSD or Big Data or both personalities if required.

Step 21

Click Submit.

Configuring the Network Interface using Shelladmin

This procedure is optional.

Step 1

Log in to the Cisco UCS Director VM console with the following credentials:

1. User—shelladmin

2. Password—changeme

If you have already logged into the shelladmin and changed the default password, use your new password instead.

After you have logged in, you can choose Change shelladmin password to change the default password.

Step 2

Choose Configure Network Interface.

Step 3

At the Do you want to Configure DHCP/STATIC IP [D/S] prompt, enter one of the following choices:

- If DHCP is enabled, enter D (IP addresses are assigned automatically)

- To configure static IP, enter S, and then choose the interface you want to configure at the next prompt followed by the option to select IPv4 or IPv6. This is followed by the confirmation of the interface selected and the version of IP for which you select Y to continue. Then enter the following details:

- IP address

- Netmask

- Gateway

- DNS Server 1

- DNS Server 2

Step 4

Confirm when prompted.

Changing the Default Password

Change the default password for administration after initial logging.

Step 1

On the menu bar, choose Administration > Users and Groups.

Step 2

Click the Users tab.

Step 3

Choose the administration user for which you want to change the default password.

Step 4

Click Change Passwrod.

Step 5

In the Change Password dialog box, enter the new password and confirm it.

Step 6

Click Save.

Updating the License

Before You Begin

If you received a zipped license file by an email, extract and save the license (.lic) file to your local machine.

Step 1

Choose Administration > License.

Step 2

Click the License Keys tab.

Step 3

Click Update License.

Step 4

In the Update License dialog box, do the following:

- To upload a .lic file, click Browse to the base license's .lic file and select the .lic file, then click Upload.

Step 5

Click Submit.
The license file is processed, and a message appears confirming the successful update.

Reserving System Resources

For optimal performance, we recommend reserving extra system resources for Cisco UCS Director beyond the minimum system requirements listed in Minimum System Requirements for a Single-Node Setup.

Note

For more information about how to reserve system resources, see the VMWare documentation.

Step 1

Log in to VMware vCenter.

Step 2

Choose the VM for Cisco UCS Director.

Step 3

Shut down the VM.

Step 4

In VMware vCenter, click the Resource Allocation tab to view the current resource allocations, and click Edit.

Step 5

In the Virtual Machine Properties pane, edit resource allocations by choosing a resource and entering the new values.

Step 6

Verify that the new resource allocations have been made.

Changing the Maximum Packet Size

The default maximum packet (query) size for the Cisco UCS Director database queries is 4 MB. If one or more of your pods requires a larger size, we recommend that you increase the configuration of the maximum packet size to 100 MB. For example, the import of large open automation modules typically requires a larger packet size.

Note

For a multi-node setup, perform this configuration on the inventory database and monitoring database nodes.

Step 1

In the shelladmin, choose Login as Root to log in to Cisco UCS Director.

Step 2

Navigate to the /etc folder.

Step 3

Open the my.cnf file and locate the max_allowed_packet parameter.

Step 4

Change the value of the max_allowed_packet parameter to max_allowed_packet=100M

Step 5

Save the my.cnf file.

Step 6

In the shelladmin, stop and restart the Cisco UCS Director services on every node, as follows:

1. Choose Stop services.

2. To verify that all services are stopped, choose Display services status.

3. After all services have stopped on the node, choose Start services.

Chapter 3. Restarting Cisco UCS Director

This chapter contains the following sections:

- Restarting Cisco UCS Director

Restarting Cisco UCS Director

If you see errors after installing Cisco UCS Director, log in to the Secure Shell (SSH) client and run scripts to verify whether services are running or not.

Step 1

Using the Cisco UCS Director IP address, log in with the following credentials:

1. User—shelladmin

2. Password—changeme

If you have already logged into the shelladmin and changed the default password, use your new password instead.

After you have logged in, you can choose Change shelladmin password to change the default password.

Step 2

To display the status of all services, choose Display services status.
If this option is not available, you can use SSH to restart the services.

Step 3

Verify that the following services appear:

1. Broker
2. Controller
3. Eventmgr
4. Client
5. Idaccessmgr
6. Inframgr
7. Websock
8. Tomcat
9. Flashpolicyd

Note:
Services that start in the background do not appear in the window.

Step 4

Choose Stop services.

Step 5

To verify that all services are stopped, choose Display services status.

Step 6

To restart services, choose Start services.

Appendix A. Ports

This appendix contains the following sections:

- Cisco UCS Director TCP and UDP Port Usage

- Port List

- Multi-Node Port Requirements

Cisco UCS Director TCP and UDP Port Usage

This section provides a list of the TCP and UDP ports that Cisco UCS Director uses for connections and communications with external applications or devices.

The following figure shows the network ports used for communication between the Cisco UCS Director appliance and managed devices, ESX servers, Bare Metal Agent, PowerShell Agent, NTP, and Active Directory.

Cisco UCS Director TCP and UDP Port Usage

Port List

Default Port

Protocol

Description

22

TCP

SSH

80

TCP/UDP

HTTP

443

UDP

HTTPS

27000/7279/8082 (Mgmt)

TCP

Citrix licensing

2598/1494/2112/2513

TCP

Virtual Desktop Agent for Desktops

67/68

UDP

DHCP

389/636

3268/3269

TCP/UDP

TCP

Active Directory

53

TCP/UDP

DNS

123

TCP/UDP

NTP

3306

TCP/UDP

MySQL

8787/5900-5964

TCP

Cisco UCS Director + VNC Connectivity

3389

TCP/UDP

Cisco UCS Director + RDP Connectivity

80/443/8080

TCP/UDP

Cisco UCS Director + NetApp Connectivity

80/443

UDP

Cisco UCS Director + Cisco UCS Manager Connectivity

80/443

UDP

Cisco UCS Director + vCenter Connectivity

3389

TCP/UDP

RDP

135/445

TCP

SMB/RPC

88

TCP/UDP

Kerberos

137

TCP/UDP

NetBIOS Name (nbname)

138

TCP/UDP

NetBIOS datagram (nbdatagram)

139

TCP

NetBIOS session (nbsession)

80/443

UDP

Desktop Delivery Controller <--> vCenter

8080 through ICA

TCP

Desktop Delivery Controller <--> Virtual Desktops

1494/2598/2512/2513

TCP

Users (Citrix Recvr) <--> Virtual Desktops

389/636 (LDAP Ports)

TCP/UDP

Desktop Delivery Controller <--> Active Directory

389/636, 3268/3269, 53

TCP/UDP

Virtual Desktops <--> Active Directory + DNS

5985/5986

TCP

PowerShell Agent <-> Xendesktop through WinRM

43891

TCP/UDP

Cisco UCS Director <--> PowerShell Agent

80/8081

TCP

XenApp

902

TCP

VMwareESXi host management and VM customization and to execute VIX tasks

903

TCP

VMwareESXi host management and VM customization and to execute VIX tasks (for Vmware vCenter releases prior to 5.0)

9443

TCP

VMware vSphere Web Client HTTPS (to access HTML5 based VM console in vCenter 6.0 and above)

7343

TCP

VMware vSphere Web Client - HTML5 Remote Console, HTTPS (vCenter 5.5 Update 2 and later)

Multi-Node Port Requirements

The ports listed in Cisco UCS Director TCP and UDP Port Usage are applicable for both single and multi-node setups.

For a multi-node setup, the following ports need to be opened between the nodes:

- From the primary and service node(s) to database nodes: port 3306

- From the primary node to service node(s): ports 80 and 443

Preface

- Audience

- Conventions

- Related Documentation

- Documentation Feedback

- Obtaining Documentation and Submitting a Service Request

Audience

This guide is intended primarily for data center administrators who use Cisco UCS Director and who have responsibilities and expertise in one or more of the following:

- Server administration

- Storage administration

- Network administration

- Network security

- Virtualization and virtual machines

Conventions

Text Type

Indication

GUI elements

GUI elements such as tab titles, area names, and field labels appear in this font.

Main titles such as window, dialog box, and wizard titles appear in this font.

Document titles

Document titles appear in this font.

TUI elements

In a Text-based User Interface, text the system displays appears in this font.

System output

Terminal sessions and information that the system displays appear in this font.

CLI commands

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

[ ]

Elements in square brackets are optional.

{x | y | z}

Required alternative keywords are grouped in braces and separated by vertical bars.

[x | y | z]

Optional alternative keywords are grouped in brackets and separated by vertical bars.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

< >

Nonprinting characters such as passwords are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Note

Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.

Caution

Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data.

Tip

Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.

Timesaver

Means the described action saves time. You can save time by performing the action described in the paragraph.

Warning

IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.

SAVE THESE INSTRUCTIONS

Related Documentation

Cisco UCS Director Documentation Roadmap

For a complete list of Cisco UCS Director documentation, see the Cisco UCS Director Documentation Roadmap available at the following URL: Click Here .

Cisco UCS Documentation Roadmaps

For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: Click Here .

For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: Click Here .

Note

The Cisco UCS B-Series Servers Documentation Roadmap includes links to documentation for Cisco UCS Manager and Cisco UCS Central. The Cisco UCS C-Series Servers Documentation Roadmap includes links to documentation for Cisco Integrated Management Controller.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to ucs-director-docfeedback@cisco.com. We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in Cisco Product Documentation RSS feed. RSS feeds are a free service.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)