Chapter 1. New and Changed Information for this Release

New and Changed Information for this Release

Chapter 2. Overview

About HP Integrated Lights-Out

Chapter 3. Managing Servers

Adding a Pod

Adding an HP Account

Testing the Connection to an HP Account

Verifying the Discovery of an HP Account

Chapter 4. Managing Reports

About Managing Reports

Viewing the HP Server Report

Preface

Audience

Conventions

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. New and Changed Information for this Release

- New and Changed Information for this Release

New and Changed Information for this Release

No significant changes were made to this guide for the current release.

Chapter 2. Overview

This chapter contains the following section:

- About HP Integrated Lights-Out

About HP Integrated Lights-Out

Integrated Lights-Out (iLO) is a proprietary embedded server management technology from Hewlett-Packard (HP) that provides out-of-band management facilities for HP ProLiant servers. HP integrates iLO into HP ProLiant servers to enable administrators to perform activities on the HP servers from a remote location.

Cisco UCS Director provides the capability to access and manage HP ProLiant servers remotely using HP iLO. Cisco UCS Director provides workflows to automate the server administration tasks and monitor the state of the servers. For more information about pod licenses, see Cisco UCS Director Orchestration Guide.

Using Cisco UCS Director, you can perform the following operations on the HP ProLiant servers that support HP iLO:

1. Power on

2. Power off

3. Set power saver mode

4. Auto power on configuration

5. View the HP server inventory details

6. View the HP server NICs

7. View the HP server slots

8. View the HP server memory

9. View the HP server processors

10. Boot PXE

For more information on how to perform these operations on the servers, see Cisco UCS Director Orchestration Guide.

Chapter 3. Managing Servers

This chapter contains the following sections:

- Adding a Pod

- Adding an HP Account

- Testing the Connection to an HP Account

- Verifying the Discovery of an HP Account

Adding a Pod

A pod is a logical grouping of physical and virtual components, including one or more physical or virtual accounts, such as an HP account for computing or a NetApp ONTAP account for storage. Typically, a pod represents a single converged infrastructure stack, such as FlexPod, Vblock, or VSPEX.

Step 1

On the menu bar, choose Administration > Physical Accounts.

Step 2

Click the Pods tab.

Step 3

Click Add.

Step 4

In the Add Pod dialog box, complete the following fields:

Name

Description

Name field

A descriptive name for the pod.

Site drop-down list

Choose the site where you want to add the pod. If your environment does not include sites, you can omit this step.

Type drop-down list

Choose Generic as the type of pod.

A generic pod does not require a specific pod license. You can add any type of physical or virtual component to a generic pod. If you choose any type of pod except the generic type, you must have a license for that pod type. In addition, the nongeneric pod types accommodate only specific physical and virtual components. For more information about pod licenses, see Cisco UCS Director Install and Upgrade Guides.

Description field

(Optional) A description of the pod.

Address field

The physical location of the pod. For example, this field could include the city or other internal identification used for the pod.

Hide Pod check box

Check this check box to hide the pod if you do not want it to show in the Converged Check View. You can continue to add or delete accounts from the pod.

For example, you can use this check box to ensure that a pod that does not have any physical or virtual elements is not displayed in the Converged View.

Step 5

Click Add.

What to Do Next

Add one or more accounts to the pod.

Adding an HP Account

Cisco UCS Director supports the HP ILO version 2, 3, and 4. Cisco UCS Director performs auto-discovery of the HP ILO version and manages all infrastructure elements in the server that are associated with the HP account.

Before You Begin

Add the pod to which this HP account belongs.

Step 1

On the menu bar, choose Administration > Physical Accounts.

Step 2

Click the Physical Accounts tab.

Step 3

Click Add.

Step 4

In the Add Account dialog box, complete the following fields:

Name

Description

Pod drop-down list

Choose the pod to which this account belongs.

Category Type drop-down list

Choose the category type. You must choose Computing. This is the type of infrastructure for the account.

Account Type drop-down list

Choose the account type. You must choose HP ILO.

Account Name field

A unique name that you assign to this account.

Server Address field

The IP address of the HP server. For a cluster configuration, this is the virtual IP address.

User ID field

The username that this account will use to access the HP server. This username must be a valid account in the HP server.

Password field

The password associated with the username.

Transport Type drop-down list

Choose one of the following transport types that you want to use for this account:

- http

- https

Port field

The port used to access the HP account.

Description field

(Optional) A description of this account.

Contact Email field

The email address that you can use to contact the administrator or other person responsible for this account.

Location field

The location of this account.

Service Provider field

(Optional) The name of the service provider associated with this account, if any.

Step 5

Click Add.

Cisco UCS Director tests the connection to the HP server. If that test is successful, it adds the HP account and discovers all infrastructure elements in the server that are associated with that account, including servers information, slots, processors, memory, and NICs. This discovery process and inventory collection cycle takes approximately five minutes to complete.

The polling interval configured on the System Tasks tab on the Administration > System window specifies the frequency of inventory collection. For more information about configuring the polling interval, see the Cisco UCS Director Network Devices Management Guide.

Testing the Connection to an HP Account

You can test the connection at any time after you add an account to a pod.

Step 1

On the menu bar, choose Administration > Physical Accounts.

Step 2

Click the Physical Accounts tab.

Step 3

In the table, click the row of the account for which you want to test the connection.

Step 4

Click Test Connection.

Step 5

When the connection test has completed, click Close.

What to Do Next

If the connection fails, verify the configuration of the account, including the username and password. If those items are correct, determine whether there is a network connectivity problem.

Verifying the Discovery of an HP Account

Step 1

On the menu bar, choose Physical > Compute.

Step 2

In the left pane, choose the pod that includes the HP account that you want to verify.
Note:   The left column tree structure lists nodes for Sites, Unassigned Pods, and Multi-Domain Managers. When a Sites node is expanded, all the pods for that site node are displayed. When you expand an Unassigned Pods node, all the pods that are not assigned to any site are displayed. When you expand the Multi-Domain Managers list, all multi-domain manager account types that you added to Cisco UCS Director are displayed.

Step 3

Click the Compute Accounts tab.

Step 4

In the table, click the row of the account that you want to verify.

Step 5

Click View Details.
Cisco UCS Director displays the iLO server details of that account that it has discovered.

Step 6

Click Back to return to the Compute Accounts tab.

Chapter 4. Managing Reports

This chapter contains the following sections:

- About Managing Reports

- Viewing the HP Server Report

About Managing Reports

All discovered and managed components of HP iLO servers are displayed at the HP account level.

You can view the reports for each of the discovered/added components in the following categories:

- NIC

- Memory

- Processor

- Slots

Viewing the HP Server Report

You can view the status of the HP server and details about the specific component in the HP server.

Step 1

On the menu bar, choose Physical > Compute.

Step 2

In the left pane, expand the site and then click a pod. Cisco UCS Director displays HP Overview and HP account details in the Summary tab.

Step 3

Expand the pod and then click the HP account. Cisco UCS Director displays the iLO servers available under the HP account.

Step 4

Click the row in the table for the server that you want to monitor.

Step 5

Click View Details.
Cisco UCS Director displays information about the current status of the selected component. Click the tabs in the window for more details about that component.

Step 6

Click on one of the following tabs to view the status of the server or a specific component in the server:

Name

Description

Summary tab

Overview of the selected HP server details such as the IP address, MAC address, product name, product ID, serial number, and UUID.

Server NICs tab

List of the NICs with their details such as the MAC type, port, and MAC address.

Server Memory tab

List of the memory available in the server by size and speed.

Server Processor tab

List of the processors with their name, speed, execution technology, and memory technology.

Server Slots tab

List of the slots in the server with their name, type, and width.

Step 7

To return to the main window, click Back.

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)