Chapter 1. Overview

Cisco UCS Director Express for Big Data Baremetal Agent

Minimum System Requirements

Guidelines and Limitations

Upgrade of Baremetal Agent

Chapter 2. Installation of Cisco UCS Director Express for Big Data Baremetal Agent

Installing Cisco UCS Director Express for Big Data Baremetal Agent on VMware vSphere

NTP Server Configuration on Cisco UCS Director Express for Big Data Baremetal Agent

Installation of User Defined Software Post Hadoop Cluster Creation

Configuring the Network Interface using Shelladmin

Configuring the DHCP Server for a Baremetal Agent Account

Adding a New Red Hat Version for Hadoop Cluster

New RHEL Version

Chapter 3. Upgrading Cisco UCS Director Baremetal Agent

Supported Upgrade Paths for Baremetal Agent, Release 5.4

Overview of the Upgrade to Baremetal Agent, Release 5.4

Preparing a Baremetal Agent, Release 5.3 VM for Upgrade

Upgrading to Baremetal Agent, Release 5.4

Completing the Upgrade to Baremetal Agent, Release 5.4

Chapter 4. Network Configuration for Cisco UCS Director Express Baremetal Agent

About the Network Configuration Options

Single Network for Management and PXE

Prerequisites and Assumptions for a Single Network Configuration

Separate Networks for Management and PXE

Prerequisites and Assumptions for a Separate Network Configuration

Preface

Audience

Conventions

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. Overview

- Cisco UCS Director Express for Big Data Baremetal Agent

- Minimum System Requirements

- Guidelines and Limitations

- Upgrade of Baremetal Agent

Cisco UCS Director Express for Big Data Baremetal Agent

Cisco UCS Director Express for Big Data Baremetal Agent (Baremetal Agent) automates the process of using a Preboot Execution Environment (PXE) to install operating systems on baremetal servers or virtual machines. Baremetal Agent provides the following services that are required for a functional PXE install environment:

- Dynamic Host Control Protocol (DHCP)

- Hypertext Transfer Protocol (HTTP)

- Trivial File Transfer Protocol (TFTP)

When this environment is operational and Baremetal Agent and Cisco UCS Director Express for Big Data are correctly configured, you can build PXE installation tasks into any Cisco UCS Director Express for Big Data infrastructure workflow.

You can access Baremetal Agent through Cisco UCS Director Express for Big Data or Secure Shell (SSH).

Minimum System Requirements

For proper installation and operation of Baremetal Agent, your environment must meet the minimum system requirements.

Minimum Requirements for VMware vSphere

Name

Requirements

VMware vCenter Server

4.0 and later

Minimum reservation in VMware vCenter

Minimum number of CPUs—2

Memory—3 GB

Hard disk—40 GB

Guidelines and Limitations

Before you install Baremetal Agent, take note of the following guidelines and limitations.

Number of Cisco UCS Director Express for Big Data applications per Cisco UCS Director Express for Big Data application.

Each Baremetal Agent application can connect to only one Cisco UCS Director Express for Big Data node.

A single Cisco UCS Director Express for Big Data node cannot support multiple Baremetal Agent applications.

Network Reachability

After installation and configuration, your environment must have the following network reachability:

- Baremetal Agent must be able to reach Cisco UCS Director Express for Big Data over the network.

- Cisco UCS Director Express for Big Data must be able to reach Baremetal Agent over the network.

- The baremetal servers must be on the same network as Baremetal Agent.

DHCP Configuration

If you use DHCP, you must locate one DHCP server in the same PXE VLAN as Baremetal Agent and configure that DHCP server with the IP address range required by your DHCP server.

VLAN Configuration

When setting up the network configuration, the most common configuration uses one PXE VLAN and one Management VLAN (separate VLANs). However, Baremetal Agent supports one VLAN for both, if you prefer. For more information about the network configuration options, see Click Here .

You must configure the VLANs end-to-end between Cisco UCS, Cisco UCS Director Express for Big Data, and Baremetal Agent. However, when you configure Baremetal Agent, do not assume that routing will occur between the PXE_VLAN Layer 2 network and the Management VLAN network.

If you configure Baremetal Agent to use DHCP, you must locate and configure the DHCP server in the PXE VLAN and its subnet. This DHCP server serves the transient IP address required for the PXE process. In an environment with two VLANs, the server is allocated an IP address from the subnet of the Management VLAN. This IP address is typically assigned from an IP address pool that is managed by Cisco UCS Director Express for Big Data.

If you configure Baremetal Agent with two VLANs, you must set up two IP address attributes:

- One IP address for Baremetal Agent in the PXE VLAN

- A second IP address for Baremetal Agent in the Management VLAN

TFTP Server

With Baremetal Agent, you use the Cisco UCS Director Express for Big Data TFTP server to ensure that configurations, such as dynamic variables, function properly.

When you add a Baremetal Agent account, Baremetal Agent configures the TFTP server when services are started.

Upgrade of Baremetal Agent

For detailed information on upgrading Baremetal Agent, see the Cisco UCS Director Upgrade Guide.

Chapter 2. Installation of Cisco UCS Director Express for Big Data Baremetal Agent

This chapter contains the following sections:

- Installing Cisco UCS Director Express for Big Data Baremetal Agent on VMware vSphere

- NTP Server Configuration on Cisco UCS Director Express for Big Data Baremetal Agent

- Installation of User Defined Software Post Hadoop Cluster Creation

- Configuring the Network Interface using Shelladmin

- Configuring the DHCP Server for a Baremetal Agent Account

- Adding a New Red Hat Version for Hadoop Cluster

Installing Cisco UCS Director Express for Big Data Baremetal Agent on VMware vSphere

Before You Begin

- You must have system administrator privileges for VMware vSphere or vCenter.

- If you want to use a static IP address rather than DHCP, you must know the following information:

- IP address

- Subnet mask

- Default gateway

Step 1

On the Cisco.com download site for Cisco UCS Director, download Cisco UCS Director Baremetal Agent and unzip the OVF file in to the folder.

Step 2

Log in to VMware vSphere Client.

Step 3

In the Navigation pane, click the vSphere host on which you want to deploy Cisco UCS Director Express for Big Data Baremetal Agent.

Step 4

Choose File > Deploy OVF Template.

Step 5

In the Source screen of the Deploy OVF Template window, do one of the following to choose your OVF source location and then click Next:

- If the OVF file is stored on your local computer, browse to the location, choose the file, and click Open.

- If the OVF file is stored on a server on your local area network, enter the location of the file including the IP address or fully qualified domain name of the server.

Step 6

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

Step 7

In the End User License Agreement screen, review the license agreement and click Accept.

Step 8

In the Name and Location screen, do the following:

1. In the Name field, enter a unique name for the VM.

2. In the Inventory Location area, choose the location where you want the VM to reside.

3. Click Next.

Step 9

In the Storage screen, choose the storage location for the VM and click Next.

Step 10

In the Disk Format screen, click Next to accept the default radio button for Thick Provision (Lazy Zeroed) format.

Step 11

In the Network Mapping screen, choose the network for the VM and click Next.

Step 12

In the Properties screen, do the following:

1. In the BMA Root User Password field, enter the password that you want to use as the root password.

2. Configure the IP addresses for both the NICs (eth0 and eth1) that you want to assign, as follows:

- To use DHCP to assign the IP addresses, leave the default of 0.0.0.0 in the IP address fields.

- To use static IP addresses, enter the desired IP addresses in the IP address fields. If you only want to configure one NIC, only complete one set of IP addresses and leave the second set at the default.

3. Click Next.

Step 13

In the Ready to Complete screen, verify the settings and click Finish.
A message appears to indicate that Cisco UCS Director Express for Big Data Baremetal Agent is being deployed.

Step 14

Log in to the Cisco UCS Director Express for Big Data Baremetal Agent server with root privileges, and check if you are able to ping the Cisco UCS Director Express for Big Data Baremetal Agent server.

Step 15

In the Navigation pane, right-click the Cisco UCS Director Express for Big Data Baremetal Agent server and choose Edit Settings.

1. Choose the Resources tab.

2. In the Resource Allocation window, set CPU and Memory Reservation settings to the maximum.

3. Click OK.

Step 16

Power on the VM.

NTP Server Configuration on Cisco UCS Director Express for Big Data Baremetal Agent

You can configure Cisco UCS Director Express for Big Data Baremetal Agent to have its clock synchronized to an external NTP server. This ensures that the correct calendar time is maintained on the Baremetal Agent.

Ensure that you synchronize Cisco UCS Director Express for Big Data and Cisco UCS Director Express for Big Data Baremetal Agent before you deploy any Hadoop cluster. It is recommended that you also synchronize Cisco UCS Manager and Cisco UCS Director Express for Big Data on the configured NTP server.

Locate the ntp_server_config.sh here: /opt/cnsaroot/bigdata_templates/ntp_server_config.sh, add execute permissions (chmod+x ntp_server_config.sh), and execute ( ./ntp_server_config.sh <ntp_server_ip or hostname>) on the Cisco UCS Director Express for Big Data Baremetal Agent Baremetal Agent server.

Installation of User Defined Software Post Hadoop Cluster Creation

Cisco UCS Director Express for Big Data provides an option to add user defined installation packages (RPMs) post Hadoop distribution specific to a version. In Cisco UCS Director Express for Big Data, you cannot install additional Hadoop related software other than what is required for the selected type of Hadoop distribution when creating an instant Hadoop cluster or customizing a Hadoop cluster.

To install user defined Hadoop related software, you can mention a list of RPMs in the HadoopDistributionRPM.txt file. You can locate the HadoopDistributionRPM.txt here: /opt/cnsaroot/bigdata_templates/common_templates in the Cisco UCS Director Express for Big Data Baremetal Agent server.

For example, you can mention a list of RPMs in the HadoopDistributionRPM.txt file for MapR-5.0.0:

- mapr-v5.0.0GA.rpm.tgz,mapr-ecosystem-5.x-20150709.rpm.tgz

- mapr-whirr-0.8.1.18380-GA.noarch.rpm for MapR-5.0.0

Configuring the Network Interface using Shelladmin

This procedure is optional.

Step 1

Log into the Cisco UCS Director Express for Big Data 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 will be 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.

Configuring the DHCP Server for a Baremetal Agent Account

Note

For a multi-home DHCP configuration, use this procedure to configure the first subnet for the DHCP server. For the remaining subnets, you must manually edit the DHCP configuration file (/etc/dhcpd.conf).

Before You Begin

To provide required DHCP services, ensure that at least one DHCP server is located in the same PXE VLAN as Baremetal Agent and configure that DHCP server with an appropriate IP address range. The DHCP server, together with the TFTP server, are used to communicate with a PXE server.

Step 1

On the menu bar, choose Administration > Physical Accounts.

Step 2

Click the Bare Metal Agents tab.

Step 3

Click the row for the Baremetal Agent account for which you want to configure the DHCP server.

Step 4

Click Service Status to verify that services for the Baremetal Agent account are stopped.

Step 5

Click Configure DHCP.

Step 6

In the Configure DHCP dialog box, complete the following fields and click Submit.

- DHCP Subnet

- DHCP Netmask

- DHCP Start IP

- DHCP End IP

- Router IP Address

The DHCP IP address assignments are updated, and the DHCP service is restarted.

Step 7

Click the row for the Baremetal Agent account and click Start Services.

Step 8

After the services have started, do the following:

- Verify that the status of the account in the Status column is Active.

- Verify that the Enabled Services column shows that all services are running. If this status indicates that one or more services are stopped, verify the configuration of your DHCP server and try again.

- Click Service Status to verify that the status of all expected services are up.

- Network Services status in the Baremetal Agent appliance

- Database connectivity status from the Baremetal Agent appliance

What to Do Next

Set up PXE boot requests.

Adding a New Red Hat Version for Hadoop Cluster

For more information on uploading supported Red Hat Enterprise Linux versions, see the Uploading Required OS and Hadoop Software to Cisco UCS Director Baremetal Agent section in Chapter 12, Hadoop Cluster Configuration Settings in Cisco UCS Director Express for Big Data Management Guide, Release 2.0

Step 1

On the menu bar, choose Solutions > Big Data > Settings.

Step 2

Click the Software Catalogs tab.

Step 3

Click Add.

Step 4

Click Upload.

Step 5

Choose the target Cisco UCS Director Express for Big Data Baremetal Agent from the Target BMA drop-down list.

Step 6

Check the Restart BMA Services to restart Cisco UCS Director Express for Big Data Baremetal Agent after uploading the required files.

Step 7

To verify that the new Red Hat version (operating system software) is available in the Cisco UCS Director Express for Big Data server, perform the following:

1. Log in to the Cisco UCS Director Express for Big Data user interface.

2. On the menu bar, choose Administration > Physical Accounts.

3. Click the Bare Metal Agents tab.

You can find the new Red Hat version listed in the Image Catalogs column of the Bare Metal Agents report.

- New RHEL Version

New RHEL Version

Red Hat Enterprise Linux 6.6

Download the following file:

- rhel-server-6.6-x86_64-dvd.iso from Red Hat Enterprise Linux

Chapter 3. Upgrading Cisco UCS Director Baremetal Agent

- Supported Upgrade Paths for Baremetal Agent, Release 5.4

- Overview of the Upgrade to Baremetal Agent, Release 5.4

- Preparing a Baremetal Agent, Release 5.3 VM for Upgrade

- Upgrading to Baremetal Agent, Release 5.4

- Completing the Upgrade to Baremetal Agent, Release 5.4

Supported Upgrade Paths for Baremetal Agent, Release 5.4

The upgrade path to Cisco UCS Director Express for Big Data Baremetal Agent (Baremetal Agent), Release 5.4 depends upon your current version of Baremetal Agent.

Upgrade Paths for Baremetal Agent, Release 5.3

From Release 5.3, you can upgrade directly to Release 5.4.

Upgrade Paths for Baremetal Agent, Release 5.2

From Release 5.2, you can upgrade directly to Release 5.4.

Upgrade Paths for Baremetal Agent, Release 5.0

From Release 5.0, you can upgrade directly to Release 5.4.

Overview of the Upgrade to Baremetal Agent, Release 5.4

Cisco UCS Director Baremetal Agent (Baremetal Agent), Release 5.4 uses a new version of Java and the CentOS operating system. Due to this, the upgrade procedure for Release 5.4 is slightly different from previous upgrades. In previous releases, only the Baremetal Agent code was upgraded.

For Release 5.4, you are upgrading the following:

- Baremetal Agent, Release 5.3 software and database schema to Release 5.4

- Java version 1.6 to version 1.8

- CentOS version 5.4 to version 6.6

Note

We recommend assigning your current Release 5.3 IP address to your new Release 5.4 VM, to minimize the impact to your production environment.

Note

You must have Active Directory on your VM to integrate with LDAP.

Preparing a Baremetal Agent, Release 5.3 VM for Upgrade

Before You Begin

Upgrade Cisco UCS Director to Release 5.4, as described in Upgrading Cisco UCS Director.

Step 1

In your hypervisor, take a snapshot of the Baremetal Agent, Release 5.x VM.
Note:
Release 5.x can be Release 5.0, Release 5.2, or Release 5.3.

Step 2

Log in to your Baremetal Agent, Release 5.x. appliance.

Step 3

Stop all services through the Cisco UCS Director UI, or by running the /opt/infra/stopInfraAll.sh script:

Step 4

If your current version of Baremetal Agent is not supported for upgrade, you must upgrade to one of Release 5.0, Release 5.2, or Release 5.3.
For information about how to upgrade from previous releases of Baremetal Agent, see the installation and upgrade guide for that release.

Step 5

Enable root access for that VM.

Step 6

If you want to use the same IP address for your Baremetal Agent, Release 5.4 VM, reconfigure the Release 5.x VM with a temporary IP address.
Note:
The temporary IP address must be in the same subnet and reachable from the Release 5.4 VM to which you are assigning the original IP address. If the new VM cannot reach the old VM, the migration script will fail.

What to Do Next

Upgrading to Baremetal Agent, Release 5.4

Upgrading to Baremetal Agent, Release 5.4

Before You Begin

- Upgrade Cisco UCS Director to Release 5.4.

- Complete the steps in Preparing a Baremetal Agent, Release 5.3 VM for Upgrade.

Step 1

Download the Baremetal Agent, Release 5.4 software.

Step 2

Deploy a VM and install Baremetal Agent, Release 5.4 as described in Installing Cisco UCS Director Express Baremetal Agent for Big Data
If you want to use the IP address that was assigned to the Release 5.3 VM, /opt/scripts/configStaticIP.sh script to configure the Release 5.4 VM with that IP address.

Step 3

Log in to the Release 5.4 VM as root.

Step 4

On the Release 5.4 VM, run /opt/infra/migration/performBMAMigration.sh to migrate the images, templates, and configuration files from the Baremetal Agent, Release 5.3 VM to the Release 5.4 VM.
When prompted, provide the temporary IP address that you assigned to the Release 5.3 VM.

Step 5

In Cisco UCS Director, Release 5.4, do the following:

1. Delete the account for Baremetal Agent, Release 5.3.

2. Add an account for Baremetal Agent, Release 5.4, as described in Configuring Cisco UCS Director Express for Big Data Baremetal Agent.

Step 6

Log in toCisco UCS Director as an admin and verify that all the images from the Release 5.3 BMA has been migrated successfully

What to Do Next

Completing the Upgrade to Baremetal Agent, Release 5.4.

Completing the Upgrade to Baremetal Agent, Release 5.4

The migration script cannot anticipate all operating system level customizations that you might have performed on the Baremetal Agent, Release 5.3 VM. You must, therefore, ensure that all customizations are duplicated in your Baremetal Agent, Release 5.4 VM.

Note

All of the following steps are optional. Complete them only if you customized or otherwise changed the defaults for the specified file. If you made any changes to file and folders that are not listed below, ensure that you also copy or merge those files from the Baremetal Agent, Release 5.3 VM to the Release 5.4 VM.

Before You Begin

Complete the steps in Upgrading to Baremetal Agent, Release 5.4.

Step 1

Copy the following files from the Release 5.3 VM to the Release 5.4 VM:

- /etc/hosts

- /etc/resolv.conf

Step 2

Evaluate and merge the following files from the Release 5.3 VM to the same files on the Release 5.4 VM:

- Changes in /etc/ntp.conf

- mysql tuning in /etc/my.cnf

- Changes in the following property file:

- /opt/infra/networkServices/service.properties

Step 3

For any Windows images migrated from the Baremetal Agent, Release 5.3 VM, update the WinPE file with the new IP address of the Baremetal Agent, Release 5.4 VM.
You do not need to edit WinPE if the Baremetal Agent IP address was not changed.

For more information, see Adding Windows Operating System Images.

Chapter 4. Network Configuration for Cisco UCS Director Express Baremetal Agent

This chapter contains the following sections:

- About the Network Configuration Options

- Single Network for Management and PXE

- Separate Networks for Management and PXE

About the Network Configuration Options

You can choose between the following network configuration options for Cisco UCS Director Express for Big Data Baremetal Agent:

- Single network for management and Preboot Execution Environment (PXE)

- Separate networks for management and PXE

Choose the network configuration option that best meets the requirements of your environment.

Single Network for Management and PXE

We recommend that you choose this network configuration option if your environment permits the following to be hosted on the same network interface and Layer 2 network (see the following figure):

- Services provided by Baremetal Agent, such as DHCP, TFTP, and HTTP

- Management traffic between Baremetal Agent and Cisco UCS Director Express for Big Data or other devices and appliances

Sample Topology for a Single Network

- Prerequisites and Assumptions for a Single Network Configuration

Prerequisites and Assumptions for a Single Network Configuration

If you plan to configure Baremetal Agent with a single network configuration, ensure that your environment meets the following prerequisites and assumptions:

- Cisco UCS Director Express for Big Data has been installed and the network interface configured, as described in the appropriate Cisco UCS Director Express for Big Data installation guide.

- Cisco UCS Director Express for Big Data is reachable through a web browser and you can log in.

- Baremetal Agent has been installed, as described in the Cisco UCS Director Express for Big Data Baremetal Agent Installation and Configuration Guide and no additional configuration has been performed.

- The required single Management and PXE VLAN is provisioned and available as a virtual port group or port profile that virtual machines (VMs) can be attached to or leverage.

Separate Networks for Management and PXE

We recommend that you choose this network configuration option if your environment does not permit the following to be hosted on the same network interface and Layer 2 network (see the following figure):

- On the PXE network, services provided by Baremetal Agent, such as DHCP, TFTP, and HTTP

- On the Management network, traffic between Baremetal Agent and Cisco UCS Director Express for Big Data or other devices and appliances

Sample Topology for Separate PXE and Management Networks

- Prerequisites and Assumptions for a Separate Network Configuration

Prerequisites and Assumptions for a Separate Network Configuration

If you plan to configure Baremetal Agent with a separate network configuration, ensure that your environment meets the following prerequisites and assumptions:

- Cisco UCS Director Express for Big Data has been installed and the network interface configured, as described in the appropriate Cisco UCS Director Express for Big Data installation guide.

- Cisco UCS Director Express for Big Data Baremetal Agent is reachable through a web browser and you can log in.

- Baremetal Agent has been installed, as described in the Cisco UCS Director Express for Big Data Baremetal Agent Installation and Configuration Guide, and no additional configuration has been performed.

- The following networks are provisioned and available as a virtual port group or port profile that VMs can be attached to or leverage:

- Management (MGMT) network—Used for traffic between Baremetal Agent and Cisco UCS Director Express for Big Data Baremetal Agent

- PXE network—Used for PXE services traffic, such as DHCP, HTTP, and TFTP

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 Express for Big Data 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.

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.

Caution

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

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, at: Click Here .

Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The 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)