Cisco Systems 57712 User Manual

Size:
4.41 Mb
Download

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

First Published: March 04, 2013

Americas Headquarters

Cisco Systems, Inc. 170 West Tasman Drive

San Jose, CA 95134-1706USA http://www.cisco.com Tel: 408526-4000

800 553-NETS(6387) Fax: 408527-0883

Text Part Number: OL-28893-01

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 THEABOVE-NAMEDSUPPLIERS 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.

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: http:// www.cisco.com/go/trademarks.Third-partytrademarks 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)

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

© 2009-2013Cisco Systems, Inc. All rights reserved.

C O N T E N T S

P r e f a c e

 

Preface xi

 

 

 

Audience xi

 

 

 

Conventions xi

 

 

 

New and Changed Information for this Release xiii

 

 

Related Cisco UCS Documentation xv

 

 

Overview 1

 

C H A P T E R

1

 

 

 

Overview of the Cisco UCS C-SeriesRack-MountServers1

 

 

Overview of the Server Software 1

 

 

Cisco Integrated Management Controller 2

 

 

CIMC CLI 3

 

 

 

Command Modes 3

 

 

 

Command Mode Table 5

 

 

Complete a Command

8

 

 

Command History 8

 

 

 

Committing, Discarding, and Viewing Pending Commands 8

 

 

Command Output Formats 8

 

 

Online Help for the CLI 9

 

 

Installing the Server OS 11

 

C H A P T E R

2

 

 

 

OS Installation Methods

11

 

 

KVM Console 11

 

 

 

PXE Installation Servers

12

 

 

Installing an OS Using a PXE Installation Server 12

 

 

Managing the Server 13

 

C H A P T E R

3

 

 

 

Toggling the Locator LED 13

 

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

 

iii

Contents

C H A P T E R 4

Toggling the Locator LED for a Hard Drive 14

Managing the Server Boot Order 14

Server Boot Order 14

Configuring the Server Boot Order 15

Viewing the Actual Server Boot Order 16

Resetting the Server 16

Shutting Down the Server 17

Managing Server Power 18

Powering On the Server 18

Powering Off the Server 18

Power Cycling the Server 19

Configuring Power Policies 20

Viewing the Power Statistics 20

Power Capping Policy 21

Configuring the Power Cap Policy 21

Configuring the Power Restore Policy 23

Managing the Flexible Flash Controller 24

Cisco Flexible Flash 24

Configuring the Flexible Flash Controller Properties 25

Booting from the Flexible Flash 27

Resetting the Flexible Flash Controller 28

Resetting the Configuration of the Cards in the Cisco Flexible Flash Controller 28

Retaining the Configuration of the Flexible Flash Controller 29

Configuring BIOS Settings 30

Viewing BIOS Status 30

Configuring Main BIOS Settings 31

Configuring Advanced BIOS Settings 32

Configuring Server Management BIOS Settings 33

Restoring BIOS Defaults 34

Restoring BIOS Manufacturing Custom Defaults 34

Viewing Server Properties 37

Viewing Server Properties 37

Viewing CIMC Properties 38

Viewing CPU Properties 38

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

iv

OL-28893-01

Contents

 

 

Viewing Memory Properties

39

 

 

 

 

Viewing Power Supply Properties 40

 

 

 

 

Viewing Storage Properties

40

 

 

 

 

 

Viewing Storage Adapter Properties 40

 

 

 

 

Viewing the Flexible Flash Controller Properties

42

 

 

 

Viewing Physical Drive Properties 43

 

 

 

 

Viewing Virtual Drive Properties 44

 

 

 

 

Viewing Nvidia GPU Card Information 45

 

 

 

 

Viewing PCI Adapter Properties 46

 

 

 

 

Viewing Network Related Properties 46

 

 

 

 

Viewing LOM Properties

46

 

 

 

 

 

Viewing Server Sensors 49

 

 

 

 

 

C H A P T E R

5

 

 

 

 

 

 

 

Viewing Power Supply Sensors

49

 

 

 

 

Viewing Fan Sensors 50

 

 

 

 

 

 

 

Viewing Temperature Sensors

50

 

 

 

 

Viewing Voltage Sensors

51

 

 

 

 

 

 

Viewing Current Sensors

52

 

 

 

 

 

 

Viewing Storage Sensors

52

 

 

 

 

 

 

Managing Remote Presence 55

 

 

 

 

C H A P T E R

6

 

 

 

 

 

 

Managing the Virtual KVM

55

 

 

 

 

 

KVM Console 55

 

 

 

 

 

 

 

Enabling the Virtual KVM 56

 

 

 

 

Disabling the Virtual KVM

56

 

 

 

 

Configuring the Virtual KVM 57

 

 

 

 

Configuring Virtual Media 58

 

 

 

 

 

Configuring Network Mounted vMedia Mapping

59

 

 

 

Viewing Network Mount vMedia Mapping Properties

60

 

 

Removing Network Mounted vMedia Mapping 60

 

 

 

Managing Serial over LAN

61

 

 

 

 

 

Serial Over LAN 61

 

 

 

 

 

 

 

Guidelines and Restrictions for Serial Over LAN

61

 

 

Configuring Serial Over LAN 62

 

 

 

 

Launching Serial Over LAN

63

 

 

 

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

 

 

 

 

 

v

Contents

C H A P T E R

7

Managing User Accounts

65

 

 

 

 

Configuring Local Users 65

 

 

 

 

Configuring Active Directory 66

 

 

 

 

Active Directory

66

 

 

 

 

Configuring the Active Directory Server 66

 

 

Configuring Active Directory in CIMC

68

 

 

Configuring Active Directory Groups in CIMC 69

 

 

Viewing User Sessions 71

 

 

 

 

Terminating a User Session 71

 

 

 

 

Configuring Network-RelatedSettings73

 

C H A P T E R

8

 

 

 

Server NIC Configuration 73

 

 

 

 

Server NICs 73

 

 

 

 

 

Configuring Server NICs 74

 

 

 

 

Configuring Common Properties

75

 

 

 

Configuring IPv4 76

 

 

 

 

 

Configuring the Server VLAN 77

 

 

 

Connecting to a Port Profile 78

 

 

 

 

Network Security Configuration

80

 

 

 

Network Security

80

 

 

 

 

Configuring Network Security

80

 

 

 

Network Time Protocol Configuration 81

 

 

 

Configuring Network Time Protocol Settings 81

 

 

Managing Network Adapters 83

 

 

C H A P T E R

9

 

 

 

 

Overview of the Cisco UCS C-SeriesNetwork Adapters83

 

 

Viewing Network Adapter Properties 85

 

 

 

Configuring Network Adapter Properties

85

 

 

Managing vHBAs 86

 

 

 

 

Guidelines for Managing vHBAs 86

 

 

 

Viewing vHBA Properties 87

 

 

 

 

Modifying vHBA Properties 88

 

 

 

Creating a vHBA

92

 

 

 

 

Deleting a vHBA

93

 

 

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

vi

OL-28893-01

Contents

vHBA Boot Table

94

 

 

 

 

Viewing the Boot Table 94

 

 

 

 

Creating a Boot Table Entry

94

 

 

 

Deleting a Boot Table Entry

95

 

 

 

vHBA Persistent Binding 96

 

 

 

 

Enabling Persistent Binding

97

 

 

 

Disabling Persistent Binding

97

 

 

 

Rebuilding Persistent Binding 98

 

 

Managing vNICs 99

 

 

 

 

 

Guidelines for Managing vNICs

99

 

 

Viewing vNIC Properties 99

 

 

 

 

Modifying vNIC Properties

100

 

 

 

Creating a vNIC

105

 

 

 

 

Deleting a vNIC

106

 

 

 

 

Configuring iSCSI Boot Capability 107

 

 

Configuring iSCSI Boot Capability for vNICs

107

Configuring iSCSI Boot Capability on a vNIC

107

Deleting an iSCSI Boot Configuration for a vNIC 109

Managing VM FEX 109

 

 

 

 

Virtual Machine Fabric Extender 109

 

 

Viewing VM FEX Properties 110

 

 

VM FEX Settings

111

 

 

 

 

Managing Storage Adapters 115

 

 

 

Create Virtual Drive from Unused Physical Drives

115

Create Virtual Drive from an Existing Drive Group

116

Clearing Foreign Configuration

117

 

 

Deleting a Virtual Drive 118

 

 

 

 

Initializing a Virtual Drive 119

 

 

 

Set as Boot Drive

 

120

 

 

 

 

Modifying Attributes of a Virtual Drive

120

 

Making a Dedicated Hot Spare

121

 

 

Making a Global Hot Spare

122

 

 

 

Preparing a Drive for Removal

122

 

 

Removing a Drive from Hot Spare Pools

123

 

Undo Preparing a Drive for Removal 124

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

 

 

 

 

 

vii

Contents

Enabling Auto Learn Cycles for the Battery Backup Unit 124

Disabling Auto Learn Cycles for the Battery Backup Unit 125

Starting a Learn Cycle for a Battery Backup Unit 125

Toggling the Locator LED for a Physical Drive 126

Viewing Storage Controller Logs 127

Backing Up and Restoring the Adapter Configuration 127

Exporting the Adapter Configuration 127

Importing the Adapter Configuration 128

Restoring Adapter Defaults 129

Managing Adapter Firmware 130

Adapter Firmware 130

Installing Adapter Firmware 130

Activating Adapter Firmware 131

 

 

Resetting the Adapter 131

 

 

 

 

Configuring Communication Services

133

C H A P T E R

1 0

 

 

Configuring HTTP 133

 

 

 

 

Configuring SSH 134

 

 

 

 

Configuring XML API 135

 

 

 

 

XML API for CIMC 135

 

 

 

 

Enabling XML API 135

 

 

 

 

Configuring IPMI 136

 

 

 

 

IPMI Over LAN 136

 

 

 

 

Configuring IPMI over LAN

136

 

 

 

Configuring SNMP 137

 

 

 

 

SNMP 137

 

 

 

 

Configuring SNMP Properties 137

 

 

Configuring SNMP Trap Settings

139

 

 

Sending a Test SNMP Trap Message 140

 

 

Configuring SNMPv3 Users

140

 

 

 

Managing Certificates 143

 

 

C H A P T E R

1 1

 

 

Managing the Server Certificate 143

Generating a Certificate Signing Request 143

Creating a Self-Signed Certificate 145

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

viii

OL-28893-01

Contents

Uploading a Server Certificate 147

C H A P T E R 1 2

C H A P T E R 1 3

C H A P T E R 1 4

C H A P T E R 1 5

Configuring Platform Event Filters 149

Platform Event Filters 149

Enabling Platform Event Alerts 149

Disabling Platform Event Alerts 150

Configuring Platform Event Filters 150

Configuring Platform Event Trap Settings 152

Interpreting Platform Event Traps 153

CIMC Firmware Management 157

Overview of Firmware 157

Obtaining Firmware from Cisco 158

Installing CIMC Firmware from a Remote Server 159

Activating Installed CIMC Firmware 160

Installing BIOS Firmware from a Remote Server 162

Viewing Logs 165

Viewing the Faults and Logs Summary 165

CIMC Log 166

Viewing the CIMC Log 166

Clearing the CIMC Log 167

Configuring the CIMC Log Threshold 167

Sending the CIMC Log to a Remote Server 168

System Event Log 170

Viewing the System Event Log 170

Clearing the System Event Log 171

Server Utilities 173

Exporting Technical Support Data 173

Rebooting the CIMC 175

Clearing the BIOS CMOS 175

Recovering from a Corrupted BIOS 176

Resetting the CIMC to Factory Defaults 177

Exporting and Importing the CIMC Configuration 178

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

ix

Contents

Exporting and Importing the CIMC Configuration 178

Exporting the CIMC Configuration 178

Importing a CIMC Configuration 179

Generating Non maskable Interrupts to the Host 180

A P P E N D I X A

BIOS Parameters by Server Model 183

C22 and C24 Servers 183

Main BIOS Parameters for C22 and C24 Servers 183

Advanced BIOS Parameters for C22 and C24 Servers 184

Server Management BIOS Parameters for C22 and C24 Servers 200

C220 and C240 Servers 203

Main BIOS Parameters for C220 and C240 Servers 203

Advanced BIOS Parameters for C220 and C240 Servers 203

Server Management BIOS Parameters for C220 and C240 Servers 219

C260 Servers 222

 

 

 

Main BIOS Parameters for C260 Servers

222

 

 

Advanced BIOS Parameters for C260 Servers

222

 

Server Management BIOS Parameters for C260 Servers

232

C420 Servers 235

 

 

 

Main BIOS Parameters for C420 Servers

235

 

 

Advanced BIOS Parameters for C420 Servers

235

 

Server Management BIOS Parameters for C420 Servers

251

C460 Servers 253

 

 

 

Main BIOS Parameters for C460 Servers

253

 

 

Advanced BIOS Parameters for C460 Servers

253

 

Server Management BIOS Parameters for C460 Servers

263

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

x

OL-28893-01

Preface

This preface includes the following sections:

Audience, page xi

Conventions, page xi

New and Changed Information for this Release, page xiii

Related Cisco UCS Documentation, page xv

Audience

This guide is intended primarily for data center administrators with responsibilities and expertise in one or more of the following:

Server administration

Storage administration

Network administration

Network security

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-basedUser Interface, text the system displays appears inthis font.

System output

Terminal sessions and information that the system displays appear in this

 

font.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

xi

Preface

Conventions

Text Type

Indication

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 Meansreader 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 Meansreader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data.

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

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

xii

OL-28893-01

Preface

New and Changed Information for this Release

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

New and Changed Information for this Release

The following tables provide an overview of the significant changes to this guide for the current release. The tables do not provide an exhaustive list of all changes made to the configuration guides or of the new features in this release.

For a complete list of all C-Seriesdocumentation, see theCisco UCS C-Series Servers Documentation Roadmap available at the following URL:http://www.cisco.com/go/unifiedcomputing/c-series-doc .

New Features and Significant Behavioral Changes in Cisco Integrated Management Controller software, Release 1.4(6)

Release Notes for Cisco UCS C-Series Software, Release 1.4(6)

Feature

Description

Where Documented

Cisco UCS VIC1225 Virtual

Support added for the Cisco UCS

Managing Network Adapters,

Interface Card

VIC1225 Virtual Interface Card.

on page 83

BIOS Properties

Support for additional BIOS properties

BIOS Parameters by Server

 

for the Cisco UCS C22 M3 Server,

Model, on page 183

 

Cisco UCS C24 M3 Server, Cisco UCS

 

 

C220

M3

Server, and the Cisco UCS

 

 

C240

M3

Server.

 

New Features and Significant Behavioral Changes in Cisco Integrated Management Controller software, Release 1.4(5)

Release Notes for Cisco UCS C-Series Software, Release 1.4(5)

Feature

Description

Where Documented

Hard Disk Drive LED

Support added for toggling the LED on

Managing the Server, on page

 

an installed hard disk drive.

13

BIOS Properties

Support for additional BIOS properties

BIOS Parameters by Server

 

for the Cisco UCS C220 M3 Server and

Model, on page 183

 

the Cisco UCS C240 M3 Server.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

xiii

Preface

New and Changed Information for this Release

New Features and Significant Behavioral Changes in Cisco Integrated Management Controller software, Release 1.4(4)

Release Notes for Cisco UCS C-Series Software, Release 1.4(4)

Feature

Description

Where Documented

Platform support

The features available in Release 1.4(3)

Release Notes for Cisco UCS

 

are now available on the Cisco UCS

C-SeriesSoftware, Release

 

C220

M3

Server and the Cisco UCS

1.4(4)

 

C240

M3

Server.

 

BIOS Properties

Support for additional BIOS properties

BIOS Parameters by Server

 

for the Cisco UCS C220 M3 Server and

Model, on page 183

 

the Cisco UCS C240 M3 Server.

 

New Features and Significant Behavioral Changes in Cisco Integrated Management Controller software, Release 1.4(3)

Release Notes for Cisco UCS C-Series Software, Release 1.4(3)

Feature

Description

Where Documented

Integration with Cisco UCS

The supported servers can be integrated

Manager

into a Cisco UCS domain.

See the Hardware Installation Guide(HIG) for the type of server you are using. The C-Series HIGs are available at the following URL: http:// www.cisco.com/en/US/ products/ps10493/prod_ installation_guides_list.html

Technical support

Support added for downloading the

Server Utilities, on page 173

 

tech support information file from a

 

 

browser.

 

BIOS parameters

Support added for additional BIOS

BIOS Parameters by Server

 

properties.

Model, on page 183

New Features and Significant Behavioral Changes in Cisco Integrated Management Controller software, Release 1.4(2)

Release Notes for Cisco UCS C-Series Software, Release 1.4(2)

Feature

Description

Where Documented

Platform support

The features available in Release 1.4(1)

 

are now available on the Cisco UCS

 

C460 M2 Server and the Cisco UCS

 

C260 M2 Server.

Release Notes for Cisco UCS C-Series Software, Release 1.4(2)

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

xiv

OL-28893-01

Preface

Related Cisco UCS Documentation

Feature

Description

Where Documented

BIOS parameters

Support added for additional BIOS

BIOS Parameters by Server

 

properties.

Model, on page 183

New Features and Significant Behavioral Changes in Cisco Integrated Management Controller software, Release 1.4(1)

Release Notes for Cisco UCS C-Series Software, Release 1.4(1)

Feature

Description

Where Documented

Platform support

The features in this release apply to the

 

Cisco UCS C200 M1 Server, the Cisco

 

UCS C210 M1 Server, and the Cisco

 

UCS C250 M1 Server.

Release Notes for Cisco UCS C-Series Software, Release 1.4(1)

VM FEX

Support is added for virtual machine

Managing Network Adapters,

 

fabric extenders (VM FEX).

on page 83

Create vHBAs

Support added in the CLI to create up

Managing Network Adapters,

 

to 16 vHBAs.

on page 83

Active Directory groups

Support added for Active Directory

Managing User Accounts, on

 

authorization groups.

page 65

Enhanced SNMP features

Enhanced SNMPv3 and SNMP trap

Configuring Communication

 

configuration is relocated in the user

Services, on page 133

 

interface.

 

XML API

Support added for CIMC control by an

Configuring Communication

 

XML API.

Services, on page 133

HTTP redirect

Support added for redirection of HTTP

Configuring Communication

 

requests to HTTPS.

Services, on page 133

BIOS parameters

Support added for additional BIOS

BIOS Parameters by Server

 

properties.

Model, on page 183

Related Cisco UCS Documentation

Documentation Roadmaps

For a complete list of all B-Seriesdocumentation, see theCisco UCS B-Series Servers Documentation Roadmap available at the following URL:http://www.cisco.com/go/unifiedcomputing/b-series-doc.

For a complete list of all C-Seriesdocumentation, see theCisco UCS C-Series Servers Documentation Roadmap available at the following URL:http://www.cisco.com/go/unifiedcomputing/c-series-doc .

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

xv

Preface

Related Cisco UCS Documentation

Other Documentation Resources

An ISO file containing all B and C-Seriesdocuments is available at the following URL:http://www.cisco.com/ cisco/software/type.html?mdfid=283853163&flowid=25821. From this page, clickUnified Computing System (UCS) Documentation Roadmap Bundle.

The ISO file is updated after every major documentation release.

Follow Cisco UCS Docs on Twitter to receive document update notifications.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

xvi

OL-28893-01

C H A P T E R 1

Overview

This chapter includes the following sections:

Overview of the Cisco UCS C-SeriesRack-MountServers, page 1

Overview of the Server Software, page 1

Cisco Integrated Management Controller, page 2

CIMC CLI, page 3

Overview of the Cisco UCS C-SeriesRack-MountServers

The Cisco UCS C-Seriesrack-mountservers include the following models:

Cisco UCS C200 Rack-MountServer

Cisco UCS C210 Rack-MountServer

Cisco UCS C220 Rack-MountServer

Cisco UCS C240 Rack-MountServer

Cisco UCS C250 Rack-MountServer

Cisco UCS C260 Rack-MountServer

Cisco UCS C460 Rack-MountServer

Note To determine which Cisco UCSC-Seriesrack-mountservers are supported by this firmware release, see the associatedRelease Notes. TheC-Seriesrelease notes are available at the following URL:http:// www.cisco.com/en/US/products/ps10739/prod_release_notes_list.html

Overview of the Server Software

The Cisco UCS C-SeriesRack-MountServer ships with two major software systems installed.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

1

Overview

Cisco Integrated Management Controller

CIMC Firmware

CIMC is a separate management module built into the motherboard. A dedicated ARM-basedprocessor, separate from the main server CPU, runs the CIMC firmware. The system ships with a running version of the CIMC firmware. You can update the CIMC firmware, but no initial installation is needed.

Server OS

The main server CPU runs an OS such as Windows or Linux. The server ships with a pre-installedOS, but you can install a different OS using the DVD drive or over the network. You can use CIMC to install the new OS using the KVM console and vMedia.

Note You can access the available OS installation documentation from theCisco UCS C-Series Servers Documentation Roadmap athttp://www.cisco.com/go/unifiedcomputing/c-series-doc.

Cisco Integrated Management Controller

The CIMC is the management service for the C-Seriesservers. CIMC runs within the server.

Note The CIMC management service is used only when the server is operating in Standalone Mode. If yourC-Seriesserver is integrated into a UCS system, you must manage it using UCS Manager. For information about using UCS Manager, see the configuration guides listed in theCisco UCS B-Series Servers Documentation Roadmap athttp://www.cisco.com/go/unifiedcomputing/b-series-doc.

Management Interfaces

You can use a web-basedGUI orSSH-basedCLI to access, configure, administer, and monitor the server. Almost all tasks can be performed in either interface, and the results of tasks performed in one interface are displayed in another. However, you cannot do the following:

Use CIMC GUI to invoke CIMC CLI

View a command that has been invoked through CIMC CLI in CIMC GUI

Generate CIMC CLI output from CIMC GUI

Tasks You Can Perform in CIMC

You can use CIMC to perform the following server management tasks:

Power on, power off, power cycle, reset and shut down the server

Toggle the locator LED

Configure the server boot order

View server properties and sensors

Manage remote presence

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

2

OL-28893-01

Overview

CIMC CLI

Create and manage local user accounts, and enable remote user authentication through Active Directory

Configure network-relatedsettings, including NIC properties, IPv4, VLANs, and network security

Configure communication services, including HTTP, SSH, and IPMI Over LAN

Manage certificates

Configure platform event filters

Update CIMC firmware

Monitor faults, alarms, and server status

No Operating System or Application Provisioning or Management

CIMC provisions servers, and as a result, exists below the operating system on a server. Therefore, you cannot use it to provision or manage operating systems or applications on servers. For example, you cannot do the following:

Deploy an OS, such as Windows or Linux

Deploy patches for software, such as an OS or an application

Install base software components, such as anti-virussoftware, monitoring agents, or backup clients

Install software applications, such as databases, application server software, or web servers

Perform operator actions, including restarting an Oracle database, restarting printer queues, or handling non-CIMCuser accounts

Configure or manage external storage on the SAN or NAS storage

CIMC CLI

The CIMC CLI is a command-linemanagement interface for Cisco UCSC-Seriesservers. You can launch the CIMC CLI and manage the server over the network by SSH or Telnet. By default, Telnet access is disabled.

A user of the CLI will be one of three roles: admin, user (can control, cannot configure), and read-only.

Note To recover from a lost admin password, see the Cisco UCSC-Seriesserver installation and service guide for your platform.

Command Modes

The CLI is organized into a hierarchy of command modes, with the EXEC mode being the highest-levelmode of the hierarchy.Higher-levelmodes branch intolower-levelmodes. You use thescope command to move fromhigher-levelmodes to modes in the next lower level , and theexit command to move up one level in the mode hierarchy. Thetop command returns to the EXEC mode.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

3

Overview

Command Modes

Note Most command modes are associated with managed objects. Thescope command does not create managed objects and can only access modes for which managed objects already exist.

Each mode contains a set of commands that can be entered in that mode. Most of the commands available in each mode pertain to the associated managed object. Depending on your assigned role, you may have access to only a subset of the commands available in a mode; commands to which you do not have access are hidden.

The CLI prompt for each mode shows the full path down the mode hierarchy to the current mode. This helps you to determine where you are in the command mode hierarchy and can be an invaluable tool when you need to navigate through the hierarchy.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

4

OL-28893-01

Overview

Command Modes

Command Mode Table

The following table lists the first four levels of command modes, the commands used to access each mode, and the CLI prompt associated with each mode.

Mode Name

EXEC

bios

advanced

main

server-management

certificate

chassis

adapter

host-eth-if

host-fc-if

port-profiles

vmfex

dimm-summary

flexflash

operational-profiles

Command to Access

Mode Prompt

top command from any mode

#

scope bios command from EXEC

/bios #

mode

 

scope advanced command from

/bios/advanced #

bios mode

 

scope main command from bios

/bios/main #

mode

 

scope server-management

/bios/server-management#

command from bios mode

 

scope certificate command from

/certificate #

EXEC mode

 

scope chassis command from

/chassis #

EXEC mode

 

scope adapter index command

/chassis/adapter #

from chassis mode

 

scope host-eth-ifcommand from

/chassis/adapter/host-eth-if#

adapter mode

 

scope host-fc-ifcommand from

/chassis/adapter/host-fc-if#

adapter mode

 

scope port-profilescommandfrom

/chassis/adapter/port-profiles#

adapter mode

 

scope vmfex index commandfrom

/chassis/adapter/vmfex #

adapter mode

 

scope dimm-summaryindex

/chassis/dimm-summary#

command from chassis mode

 

scope flexflash index command

/chassis/flexflash #

from chassis mode

 

scope operational-profile

/chassis/flexflash/operational-profile

command from flexflash mode

#

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

5

Overview

Command Modes

Mode Name

storageadapter

physical-drive

virtual-drive

cimc

firmware

import-export

log

server

network

ipblocking

tech-support

fault

pef

http

ipmi

kvm

ldap

Command to Access

Mode Prompt

scope storageadapter slot

/chassis/storageadapter #

command from chassis mode

 

scope physical-drivecommand

/chassis/storageadapter/physical-drive

from storageadapter mode

#

scope virtual-drivecommand

/chassis/storageadapter/virtual-drive

from storageadapter mode

#

scope cimc command from EXEC

/cimc #

mode

 

scope firmware command from

/cimc/firmware #

cimc mode

 

scope import-exportcommand

/cimc/import-export#

from cimc mode

 

scope log command from cimc

/cimc/log #

mode

 

scope server index command from

/cimc/log/server #

log mode

 

scope network command from

/cimc/network #

cimc mode

 

scope ipblocking command from

/cimc/network/ipblocking #

network mode

 

scope tech-supportcommand

/cimc/tech-support#

from cimc mode

 

scope fault command from EXEC

/fault #

mode

 

scope pef command from fault

/fault/pef #

mode

 

scope http command from EXEC

/http #

mode

 

scope ipmi command from EXEC

/ipmi #

mode

 

scope kvm command from EXEC

/kvm #

mode

 

 

/ldap #

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

6

OL-28893-01

Overview

Command Modes

Mode Name

role-group

power-cap

sel

sensor

snmp

trap-destinations

v3users

sol

ssh

user

user-session

vmedia

xmlapi

Command to Access

Mode Prompt

scope ldap command from EXEC

 

mode

 

scope role-groupcommand from

/ldap/role-group#

ldap mode

 

scope power-capcommand from

/power-cap#

EXEC mode

 

scope sel command from EXEC

/sel #

mode

 

scope sensor command from

/sensor #

EXEC mode

 

scope snmp commandfromEXEC

/snmp #

mode

 

scope trap-destinationscommand

/snmp/trap-destinations#

from snmp mode

 

scope v3users command from

/snmp/v3users #

snmp mode

 

scope sol command from EXEC

/sol #

mode

 

scope ssh command from EXEC

/ssh #

mode

 

scope user user-numbercommand

/user #

from EXEC mode

 

scope user-sessionsession-number

/user-session#

command from EXEC mode

 

scope vmedia command from

/vmedia #

EXEC mode

 

scope xmlapi command from

/xmlapi #

EXEC mode

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

7

Overview

Complete a Command

Complete a Command

You can use the Tab key in any mode to complete a command. Partially typing a command name and pressing Tab causes the command to be displayed in full or to the point where another keyword must be chosen or an argument value must be entered.

Command History

The CLI stores all commands used in the current session. You can step through the previously used commands by using the Up Arrow or Down Arrow keys. The Up Arrow key steps to the previous command in the history, and the Down Arrow key steps to the next command in the history. If you get to the end of the history, pressing the Down Arrow key does nothing.

All commands in the history can be entered again by simply stepping through the history to recall the desired command and pressing Enter. The command is entered as if you had manually typed it. You can also recall a command and change it before you press Enter.

Committing, Discarding, and Viewing Pending Commands

When you enter a configuration command in the CLI, the command is not applied until you enter the commit command. Until committed, a configuration command is pending and can be discarded by entering adiscard command. When any command is pending, an asterisk (*) appears before the command prompt. The asterisk disappears when you enter thecommit command, as shown in this example:

Server# scope chassis

Server /chassis # setlocator-ledoff

Server /chassis *# commit

Server /chassis #

You can accumulate pending changes in multiple command modes and apply them together with a single commit command. You can view the pending commands by entering theshow configuration pending command in any command mode.

Note Committing multiple commands together is not an atomic operation. If any command fails, the successful commands are applied despite the failure. Failed commands are reported in an error message.

Command Output Formats

Most CLI show commands accept an optionaldetail keyword that causes the output information to be displayed as a list rather than a table. You can configure either of two presentation formats for displaying the output information when thedetail keyword is used. The format choices are as follows:

DefaultForeasy viewing, the command output is presented in a compact list.

This example shows command output in the default format:

Server /chassis # set cli output default

Server /chassis # show hdd detail

Name HDD_01_STATUS:

Status : present

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

8

OL-28893-01

Overview

Online Help for the CLI

Name HDD_02_STATUS:

Status : present

Name HDD_03_STATUS:

Status : present

Name HDD_04_STATUS:

Status : present

Server /chassis #

YAMLForeasy parsing by scripts, the command output is presented in the YAML (YAML Ain't Markup Language) data serialization language, delimited by defined character strings.

This example shows command output in the YAML format:

Server /chassis # set cli output yaml

Server /chassis # show hdd detail

---

name: HDD_01_STATUS hdd-status:present

---

name: HDD_02_STATUS hdd-status:present

---

name: HDD_03_STATUS hdd-status:present

---

name: HDD_04_STATUS hdd-status:present

...

Server /chassis #

For detailed information about YAML, see http://www.yaml.org/about.html.

In most CLI command modes, you can enter set cli output default to configure the default format, orset cli output yaml to configure the YAML format.

Online Help for the CLI

At any time, you can type the ? character to display the options available at the current state of the command syntax.

If you have not typed anything at the prompt, typing ? lists all available commands for the mode you are in. If you have partially typed a command, typing ? lists all available keywords and arguments available at your current position in the command syntax.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

9

Overview

Online Help for the CLI

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

10

OL-28893-01

C H A P T E R 2

Installing the Server OS

This chapter includes the following sections:

OS Installation Methods, page 11

KVM Console, page 11

PXE Installation Servers, page 12

OS Installation Methods

C-Seriesservers support several operating systems. Regardless of the OS being installed, you can install it on your server using one of the following tools:

KVM console

PXE installation server

KVM Console

The KVM console is an interface accessible from CIMC that emulates a direct keyboard, video, and mouse (KVM) connection to the server. The KVM console allows you to connect to the server from a remote location.

Instead of using CD/DVD or floppy drives physically connected to the server, the KVM console uses virtual media, which are actual disk drives or disk image files that are mapped to virtual CD/DVD or floppy drives. You can map any of the following to a virtual drive:

CD/DVD or floppy drive on your computer

Disk image files (ISO or IMG files) on your computer

USB flash drive on your computer

CD/DVD or floppy drive on the network

Disk image files (ISO or IMG files) on the network

USB flash drive on the network

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

11

Installing the Server OS

PXE Installation Servers

You can use the KVM console to install an OS on the server.

PXE Installation Servers

A Preboot Execution Environment (PXE) installation server allows a client to boot and install an OS from a remote location. To use this method, a PXE environment must be configured and available on your VLAN, typically a dedicated provisioning VLAN. Additionally, the server must be set to boot from the network.

When the server boots, it sends a PXE request across the network. The PXE installation server acknowledges the request, and starts a sequence of events that installs the OS on the server.

PXE servers can use installation disks, disk images, or scripts to install an OS. Proprietary disk images can also be used to install an OS, additional components, or applications.

Note PXE installation is an efficient method for installing an OS on a large number of servers. However, considering that this method requires setting up a PXE environment, it might be easier to use another installation method.

Installing an OS Using a PXE Installation Server

Before You Begin

Verify that the server can be reached over a VLAN.

You must log in as a user with admin privileges to install an OS.

Procedure

Step 1 Set the boot order toPXE first.

Step 2 Reboot the server.

If a PXE install server is available on the VLAN, the installation process begins when the server reboots. PXE installations are typically automated and require no additional user input. Refer to the installation guide for the OS being installed to guide you through the rest of the installation process.

What to Do Next

After the OS installation is complete, reset the LAN boot order to its original setting.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

12

OL-28893-01

C H A P T E R 3

Managing the Server

This chapter includes the following sections:

Toggling the Locator LED, page 13

Toggling the Locator LED for a Hard Drive, page 14

Managing the Server Boot Order, page 14

Resetting the Server, page 16

Shutting Down the Server, page 17

Managing Server Power, page 18

Configuring Power Policies, page 20

Managing the Flexible Flash Controller, page 24

Configuring BIOS Settings, page 30

Toggling the Locator LED

Before You Begin

You must log in with user or admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server # scope chassis

Enters chassis command mode.

Step 2

Server /chassis # set locator-led {on |off}

Enables or disables the chassis locator LED.

Step 3

Server /chassis # commit

Commits the transaction to the system

 

 

configuration.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

13

Managing the Server

Toggling the Locator LED for a Hard Drive

This example disables the chassis locator LED and commits the transaction:

Server# scope chassis

Server /chassis # setlocator-ledoff

Server /chassis *# commit

Server /chassis #

Toggling the Locator LED for a Hard Drive

Before You Begin

You must log in with user or admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server # scope chassis

Enters chassis command mode.

Step 2

Server/chassis # scope hdd

Enters hard disk drive (HDD) command mode.

Step 3

Server /chassis/hdd # set locateHDD

 

drivenum {1 | 2}

Where drivenum is the number of the hard drive whose locator LED you want to set. A value of 1 turns the LED on while a value of 2 turns the LED off.

This example turns on the locator LED on HDD 2:

Server# scope chassis

 

 

Server /chassis # scope hdd

 

Server /chassis/hdd # locateHDD 2 1

 

HDD Locate LED Status changed to 1

 

Server /chassis/hdd # show

LocateLEDStatus

Name

Status

--------------------

--------------------

--------------------

HDD1_STATUS

present

TurnOFF

HDD2_STATUS

present

TurnON

HDD3_STATUS

absent

TurnOFF

HDD4_STATUS

absent

TurnOFF

Server /chassis/hdd #

Managing the Server Boot Order

Server Boot Order

Using CIMC, you can configure the order in which the server attempts to boot from available boot device types.

When you change the boot order configuration, CIMC sends the configured boot order to the BIOS the next time the server is rebooted. To implement the new boot order, reboot the server after making the configuration change. The new boot order will take effect on any subsequent reboot. The configured boot order is not sent again until the configuration is changed again.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

14

OL-28893-01

Managing the Server

Configuring the Server Boot Order

Note The actual boot order will differ from the configured boot order if either of the following conditions occur:

The BIOS encounters issues while trying to boot using the configured boot order.

A user changes the boot order directly through the BIOS.

Configuring the Server Boot Order

Note Do not change the boot order while the host is performing BIOSpower-onself test (POST).

Before You Begin

You must log in with user or admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope bios

Enters bios command mode.

Step 2

Server /bios # set boot-order

Specifies the boot device options and order. You can

 

device1[,device2[,device3

select one or more of the following:

 

[,device4[,device5]]]]

cdromBootableCD-ROM

 

 

 

 

fddFloppydisk drive

 

 

hddHarddisk drive

 

 

pxePXEboot

 

 

efiExtensibleFirmware Interface

Step 3

Server /bios # commit

Commits the transaction to the system configuration.

The new boot order will be used on the next BIOS boot.

This example sets the boot order and commits the transaction:

Server# scope bios

Server /bios # setboot-orderhdd,cdrom,fdd,pxe,efi

Server /bios *# commit

Server /bios # show detail

BIOS:

Boot Order: HDD,CDROM,FDD,PXE,EFI

Server /bios #

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

15

Managing the Server

Viewing the Actual Server Boot Order

What to Do Next

Reboot the server to boot with your new boot order.

Viewing the Actual Server Boot Order

The actual server boot order is the boot order actually used by the BIOS when the server last booted. The actual boot order can differ from the boot order configured in CIMC.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope bios

Enters bios command mode.

Step 2

Server /bios # showactual-boot-order

Displays the boot order actually used by the BIOS

 

[detail]

when the server last booted.

This example displays the actual boot order from the last boot:

Server# scope bios

 

 

 

 

Server /bios

# showactual-boot-order

 

 

 

 

Boot Order

Type

Boot Device

 

 

------------

-------------------------

-----------------------------------

1

CD/DVD

CD-ROM

Virtual CD/DVD

1.18

2

CD/DVD

Cisco

3

Network Device (PXE)

Cisco NIC 23:0.0

 

4

Network Device (PXE)

MBA v5.0.5

Slot 0100

 

5

Network Device (PXE)

MBA v5.0.5

Slot 0101

 

6

Network Device (PXE)

MBA v5.0.5

Slot 0200

 

7

Network Device (PXE)

MBA v5.0.5

Slot 0201

 

8

Network Device (PXE)

Cisco NIC 22:0.0

 

9

Internal EFI Shell

Internal EFI Shell

1.18

10

FDD

Cisco

Virtual HDD

11

FDD

Cisco

Virtual Floppy

1.18

Server /bios

#

 

 

 

 

Resetting the Server

Important If any firmware or BIOS updates are in progress, do not reset the server until those tasks are complete.

Before You Begin

You must log in with user or admin privileges to perform this task.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

16

OL-28893-01

Managing the Server

Shutting Down the Server

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # power hard-reset

After a prompt to confirm, resets the server.

This example resets the server:

Server# scope chassis

Server /chassis # power hard-reset

This operation will change the server's power state.

Continue?[y|N]

Shutting Down the Server

Important If any firmware or BIOS updates are in progress, do not shut down the server until those tasks are complete.

Before You Begin

You must log in with user or admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters chassis mode.

Step 2

Server /chassis # power shutdown

Shuts down the server.

The following example shuts down the server:

Server# scope chassis

Server /chassis # power shutdown

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

17

Managing the Server

Managing Server Power

Managing Server Power

Powering On the Server

Note If the server was powered off other than through the CIMC, the server will not become active immediately when powered on. In this case, the server will enter standby mode until the CIMC completes initialization.

Important If any firmware or BIOS updates are in progress, do not change the server power until those tasks are complete.

Before You Begin

You must log in with user or admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # power on

Turns on the server.

This example turns on the server:

Server# scope chassis

Server /chassis # power on

This operation will

change the server's power state.

Continue?[y|N]y

 

 

Server /chassis # show

UUID

Power Serial Number

Product Name

------------------

-------------

------------------------------------

on

Not Specified

Not Specified

208F0100020F000000BEA80000DEAD00

Powering Off the Server

Important If any firmware or BIOS updates are in progress, do not power off the server until those tasks are complete.

Before You Begin

You must log in with user or admin privileges to perform this task.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

18

OL-28893-01

Managing the Server

Power Cycling the Server

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # power off

Turns off the server.

This example turns off the server:

 

Server# scope chassis

 

Server /chassis # power off

 

This operation will change the server's power state.

 

Continue?[y|N]y

 

Server /chassis # show

 

Power Serial Number Product Name UUID

 

-----

--------------------------------------------------------------

off

Not Specified Not Specified 208F0100020F000000BEA80000DEAD00

Power Cycling the Server

Important If any firmware or BIOS updates are in progress, do not power cycle the server until those tasks are complete.

Before You Begin

You must log in with user or admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # power cycle

Power cycles the server.

This example power cycles the server:

Server# scope chassis

Server /chassis # power cycle

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

19

Managing the Server

Configuring Power Policies

Configuring Power Policies

Viewing the Power Statistics

Procedure

 

Command or Action

Purpose

Step 1

Server# showpower-cap[detail]

Displays the server power consumption statistics

 

 

and the power cap policy.

The displayed fields are described in the following table:

Name

Description

Current Consumption

The power currently being used by the server, in watts.

Maximum Consumption

The maximum number of watts consumed by the server since the last

 

time it was rebooted.

Minimum Consumption

The minimum number of watts consumed by the server since the last

 

time it was rebooted.

Minimum Configurable Limit

The minimum amount of power that can be specified as the peak power

 

cap for this server, in watts.

Maximum Configurable Limit

The maximum amount of power that can be specified as the peak power

 

cap for this server, in watts.

Additional fields are described in the following table:

Name

Description

Enable Power Capping

, the system monitors how much power is allocated to the server and

 

takes the specified action if the server goes over its maximum allotment.

Peak Power

The maximum number of watts that can be allocated to this server. If

 

the server requests more power than specified in this field, the system

 

takes the action defined in the Non-Compliance Action field.

 

Enter a number of watts within the range defined by the Minimum

 

Configurable Limit field and the Maximum Configurable Limit

 

field.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

20

OL-28893-01

Managing the Server

Power Capping Policy

Name

Description

Non-ComplianceAction

The action the system should take if power capping is enabled and the

 

server requests more than its peak power allotment. This can be one of

 

the following:

 

Theserver is forced to reduce its power consumption by any

 

means necessary. This option is available only on some C-Series

 

servers.

 

Noaction is taken and the server is allowed to use more power

 

than specified in the Peak Power field.

 

Theserver is shut down.

 

Processesrunning on the server are throttled to bring the total

 

power consumption down.

This example displays the detailed power statistics:

Server# showpower-capdetail

Cur Consumption (W): 247

Max Consumption (W): 286

Min Consumption (W): 229

Minimum Configurable Limit (W): 285

Maximum Configurable Limit (W): 1250

Power Cap Enabled: yes

Peak Power: 0

Non Compliance Action: throttle

Server#

Power Capping Policy

The power capping policy determines how server power consumption is actively managed. When power capping is enabled, the system monitors how much power is allocated to the server and attempts to keep the power consumption below the allocated power. If the server exceeds its maximum allotment, the power capping policy triggers the specified non-complianceaction.

Configuring the Power Cap Policy

Note This feature is not available on some servers.

Before You Begin

You must log in with admin privileges to perform this task.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

21

Managing the Server

Configuring the Power Cap Policy

Procedure

 

Command or Action

Purpose

Step 1

Server# scopepower-cap

Enters the power cap command mode.

Step 2

Server /power-cap#set

Enables or disables the capping of power to the server.

 

enabled {yes| no}

 

Step 3 Server /power-cap#set peak-power watts

Step 4 Server /power-cap#set non-compliance-action {force-power-reduction |none |power-off-host |throttle}

Step 5 Server /power-cap#commit

Specifies the maximum number of watts that can be allocated to this server. Enter a number of watts within the range defined by theMinimum Configurable Limit field and theMaximum Configurable Limit field of theshow power-cap detail command output. These fields are determined by the server model.

If the server requests more power than specified in this command, the system takes the action defined by the set non-compliance-action command.

Specifies the action the system should take if power capping is enabled and the server requests more than its peak power allotment. This can be one of the following:

force-power-reductionTheserver is forced to reduce its power consumption by any means necessary. This option is not available on some server models.

noneNoaction is taken and the server is allowed to use more power than specified in the peak power setting.

power-off-hostTheserver is shut down.

throttleProcessesrunning on the server are throttled to bring the total power consumption down.

Commits the transaction to the system configuration.

This example enables and configures a power cap policy and commits the transaction:

Server# scopepower-cap

Server /power-cap#set enabled yes

Server /power-cap*#set peak-power 1000

Server /power-cap *# setnon-compliance-actionthrottle

Server /power-cap*#commit

Server /power-cap#show detail

Cur Consumption (W): 688

Max Consumption (W): 1620

Min Consumption (W): 48

Minimum Configurable Limit (W): 500

Maximum Configurable Limit (W): 2000

Power Cap Enabled: yes

Peak Power: 1000

Non Compliance Action: throttle

Server /power-cap#

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

22

OL-28893-01

Managing the Server

Configuring the Power Restore Policy

Configuring the Power Restore Policy

The power restore policy determines how power is restored to the server after a chassis power loss.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # set policy

Specifies the action to be taken when chassis power is restored.

 

{power-off| power-on|

Select one of the following:

 

restore-last-state}

power-offServerpower will remain off until manually

 

 

 

 

turned on. This is the default action.

 

 

power-onServerpower will be turned on when chassis

 

 

power is restored.

 

 

restore-last-stateServerpower will return to the state

 

 

before chassis power was lost.

 

 

When the selected action is power-on,you can select a delay

 

 

in the restoration of power to the server.

Step 3

Server /chassis # set delay

(Optional)

 

{fixed| random}

Specifies whether server power will be restored after a fixed

 

 

or random time. The default is fixed. This command is accepted

 

 

only if the power restore action is power-on.

Step 4

Server /chassis # set

(Optional)

 

delay-valuedelay

Specifies the delay time in seconds. The range is 0 to 240; the

 

 

default is 0.

Step 5

Server /chassis # commit

Commits the transaction to the system configuration.

This example sets the power restore policy to power-onwith a fixed delay of 180 seconds (3 minutes) and commits the transaction:

Server# scope chassis

Server /chassis # set policypower-on

Server /chassis *# set delay fixed

Server /chassis *# set delay-value 180

Server /chassis *# commit

Server /chassis # show detail

Chassis:

Power: on

Serial Number: QCI1404A1IT

Product Name: UCS C200 M1

PID : R200-1120402

UUID: 01A6E738-D8FE-DE11-76AE-8843E138AE04

Locator LED: off

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

23

Managing the Server

Managing the Flexible Flash Controller

Description: Testing power restore

Power Restore Policy: power-on

Power Delay Type: fixed

Power Delay Value(sec): 180

Server /chassis #

Managing the Flexible Flash Controller

Cisco Flexible Flash

Some C-SeriesRack-MountServers support an internal Secure Digital (SD) memory card for storage of server software tools and utilities. The SD card is hosted by the Cisco Flexible Flash storage adapter.

The SD storage is available to CIMC as four virtual USB drives. Three are preloaded with Cisco software and the fourth can hold a user-installedhypervisor or other content. The four virtual drives are as follows:

Cisco UCS Server Configuration Utility (bootable)

User-installed(may be bootable)

Cisco drivers (not bootable)

Cisco Host Upgrade Utility (bootable)

For information about the Cisco software utilities and packages, see the Cisco UCS C-Series Servers Documentation Roadmap at this URL:

http://www.cisco.com/go/unifiedcomputing/c-series-doc

Dual Card Management in the Cisco Flexible Flash Controller

The Cisco Flexible Flash controller supports management of two SD cards as a RAID-1pair. With the introduction of dual card management, you can perform the following tasks:

Action

Description

Reset Cisco Flex Flash

Allows you to reset the controller.

Reset Configuration

Allows you to reset the configuration in the selected

 

slot to the default configuration.

Retain Configuration

Allows you to retain the configuration for an SD card

 

that supports firmware version 1.2.253.

Configure Operational Profile

Allows you to configure the SD cards on the selected

 

Cisco Flexible Flash controller.

RAID Partition Enumeration

Non-RAIDpartitions are always enumerated from the primary card and the enumeration does not depend on the status of the primary card.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

24

OL-28893-01

Managing the Server

Configuring the Flexible Flash Controller Properties

Following is the behavior of the RAID partition enumeration when there are two cards in the Cisco Flexible Flash controller:

Scenario

Behavior

Single card

RAID partitions are enumerated if the card is healthy,

 

and if the mode is either Primary or

 

Secondary-active.

Dual paired cards

RAID partitions are enumerated if one of the cards

 

is healthy.

 

When only one card is healthy, all read/write

 

operations occur on this healthy card. You must use

 

UCS SCU to synchronize the two RAID partitions.

Dual unpaired cards

If this scenario is detected when the server is

 

restarting, then neither one of the RAID partitions is

 

enumerated.

 

If this scenario is detected when the server is running,

 

when a user connects a new SD card, then the cards

 

are not managed by the Cisco Flexible Flash

 

controller. This does not affect the host enumeration.

 

You must pair the cards to manage them. You can

 

pair the cards using the Reset Configuration or

 

Retain Configuration options.

Configuring the Flexible Flash Controller Properties

Before You Begin

You must log in with admin privileges to perform this task.

Cisco Flexible Flash must be supported by your platform.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope flexflash

Enters the Cisco Flexible Flash controller command mode

 

index

for the specified controller. At this time, the only permissible

 

 

index value is FlexFlash-0.

Step 3

Server /chassis/flexflash # scope

Enters the operational profile command mode.

 

operational-profile

 

Step 4

Server

Specifies the slot in which the primary copy of the data

 

/chassis/flexflash/operational-profile

resides.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

25

Managing the Server

Configuring the Flexible Flash Controller Properties

 

Command or Action

Purpose

 

 

# setraid-primary-member{slot1

Important

Currently, Cisco Flexible Flash cards are

 

| slot2}

 

supported in slot 1 and slot 2. Therefore, you

 

 

 

can specify slot1 orslot2.

Step 5

Server

The role of the secondary RAID. The currently supported

 

/chassis/flexflash/operational-profile

value is active.

 

# setraid-secondary-role{active|

 

 

 

initializing}

 

 

Step 6

Server

Specifies the number of read errors that are permitted while

 

/chassis/flexflash/operational-profile

accessing the Cisco Flexible Flash card. If the number of

 

# setread-error-count-threshold

errors exceeds this threshold, the Cisco Flexible Flash card

 

 

is disabled and you must reset it manually before CIMC

 

 

attempts to access it again.

 

 

To specify a read error threshold, enter an integer between

 

 

1 and 255. To specify that the card should never be disabled

 

 

regardless of the number of errors encountered, enter 0 (zero).

Step 7

Server

Specifies the number of write errors that are permitted while

 

/chassis/flexflash/operational-profile

accessing the Cisco Flexible Flash card. If the number of

 

# setwrite-error-count-threshold

errors exceeds this threshold, the Cisco Flexible Flash card

 

 

is disabled and you must reset it manually before CIMC

 

 

attempts to access it again.

 

 

To specify a write error threshold, enter an integer between

 

 

1 and 255. To specify that the card should never be disabled

 

 

regardless of the number of errors encountered, enter 0 (zero).

Step 8

Server

Specifies a list of virtual drives to be made available to the

 

/chassis/flexflash/operational-profile

server as a USB-styledrive. The options are as follows:

 

# setvirtual-drives-enabledlist

SCUTheserver can access the Cisco UCS Server

 

 

 

 

Configuration Utility.

 

 

DRIVERSTheserver can access the Cisco drivers

 

 

volume.

 

 

HVTheserver can access auser-installedhypervisor.

 

 

HUUTheserver can access the Cisco Host Upgrade

 

 

Utility.

 

 

 

When specifying more than one option, you must enclose

 

 

the list in quotation marks (").

Step 9

Server /chassis/adapter # commit

Commits the transaction to the system configuration.

This example shows how to configure the properties of the Flash controller:

Server# scope chassis

Server /chassis # scope flexflashFlexFlash-0

Server /chassis/flexflash # scope operational-profile

Server /chassis/flexflash/operational-profile#set read-error-count-threshold 100

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

26

OL-28893-01

Managing the Server

Booting from the Flexible Flash

Server /chassis/flexflash/operational-profile#set write-error-count-threshold 100 Server /chassis/flexflash/operational-profile*#set raid-primary-member slot1 Server /chassis/flexflash/operational-profile#set raid-secondary-role active Server /chassis/flexflash/operational-profile*#set virtual-drives-enabled "SCU HUU" Server /chassis/flexflash/operational-profile*#commit

Server /chassis/flexflash/operational-profile#

Booting from the Flexible Flash

You can specify a bootable virtual drive on the Cisco Flexible Flash card that will override the default boot priority the next time the server is restarted, regardless of the default boot order defined for the server. The specified boot device is used only once. After the server has rebooted, this setting is ignored.

Note Before you reboot the server, ensure that the virtual drive you select is enabled on the Cisco Flexible Flash card.

Before You Begin

You must log in with admin privileges to perform this task.

Cisco Flexible Flash must be supported by your platform.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope bios

Enters the BIOS command mode.

Step 2

Server /bios # setboot-override

The virtual drive from which the server attempts to boot the

 

{None| SCU| HV| HUU}

next time it is restarted. This can be one of the following:

 

 

NoneTheserver uses the default boot order

 

 

SCUTheserver boots from the Cisco UCS Server

 

 

Configuration Utility

 

 

HVTheserver boots from the hypervisor virtual drive

 

 

HUUTheserver boots from the Cisco Host Upgrade

 

 

Utility

Step 3

Server /bios # commit

Commits the transaction to the system configuration.

This example specifies that the server boots from the Cisco UCS Server Configuration Utility the next time it is restarted:

Server# scope bios

Server /bios # setboot-overrideSCU

Committing the boot override BIOS will try boot to the specified boot device first. Failure to detect the boot device BIOS will boot from the list configured in the BIOS boot order.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

27

Managing the Server

Resetting the Flexible Flash Controller

Server /bios *# commit

Server /bios #

Resetting the Flexible Flash Controller

In normal operation, it should not be necessary to reset the Cisco Flexible Flash. We recommend that you perform this procedure only when explicitly directed to do so by a technical support representative.

Note This operation will disrupt traffic to the virtual drives on the Cisco Flexible Flash controller.

Before You Begin

You must log in with admin privileges to perform this task.

Cisco Flexible Flash must be supported by your platform.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope flexflash

Enters the Cisco Flexible Flash controller command

 

index

mode for the specified controller. At this time, the only

 

 

permissible index value isFlexFlash-0.

Step 3

Server /chassis/flexflash # reset

Resets the Cisco Flexible Flash controller.

This example resets the flash controller:

Server# scope chassis

Server /chassis # scope flexflashFlexFlash-0

Server /chassis/flexflash # reset

This operation will reset Cisco Flexible Flash controller.

Host traffic to VDs on this device will be disrupted.

Continue?[y|N] y

Server /chassis/flexflash #

Resetting the Configuration of the Cards in the Cisco Flexible Flash Controller

You can reset the configuration of a selected slot in the Cisco Flexible Flash controller to the default configuration.

When you reset the configuration of the slots in the Cisco Flexible Flash card, the following situations occur:

The card in the selected slot is marked as primary healthy.

The card in the other slot is marked as secondary-activeunhealthy.

Three non-RAIDpartitions and one RAID partition are created.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

28

OL-28893-01

Managing the Server

Retaining the Configuration of the Flexible Flash Controller

The card read/write error counts and read/write threshold are set to 0.

Host connectivity could be disrupted.

Before You Begin

You must log in with admin privileges to perform this task.

Cisco Flexible Flash must be supported on your server.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope flexflash index

Enters the Cisco Flexible Flash controller command

 

 

mode for the specified controller. At this time, the

 

 

only permissible index value isFlexFlash-0.

Step 3

Server /chassis/flexflash # reset-config

Resets the configuration of the selected slot to the

 

primary slot ID

default configuration.

Step 4

Server /chassis/flexflash # commit

Commits the transaction to the system configuration.

This example shows how to reset the configuration from a slot to the default configuration:

Server# scope chassis

Server /chassis # scope flexflashFlexFlash-0

Server /chassis/flexflash # reset-config slot1

This action will mark the slot1 as the healthy primary slot, and slot2 (if card exists) as unhealthy secondary active.

This operation may disturb the host connectivity as well. Continue? [y|N] y

Server /chassis/flexflash/operational-profile*#commit

Server /chassis/flexflash/operational-profile#

Retaining the Configuration of the Flexible Flash Controller

You can copy the configuration of a given slot in the Cisco Flexible Flash card to the other slot. However, the slot from which the configuration is copied from must be of the SDK523 type. You can retain the configuration in the following situations:

There are two unpaired SD cards

The server is operating from a single SD card, and an unpaired SD card is in the other slot.

One SD card supports firmware version 1.2.253, and the other SD card is either unpartitioned or supports firmware version 1.2.247.

Before You Begin

You must log in with admin privileges to perform this task.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

29

Managing the Server

Configuring BIOS Settings

Cisco Flexible Flash must be supported on your server.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope flexflash index

Enters the Cisco Flexible Flash controller command

 

 

mode for the specified controller. At this time, the

 

 

only permissible index value isFlexFlash-0.

Step 3

Server /chassis/flexflash # retain

Copies the configuration from the primary slot to the

 

config primary slot ID

secondary slot.

Step 4

Server /chassis/flexflash # commit

Commits the transaction to the system configuration.

This example shows how to copy the configuration from one slot to the other:

Server# scope chassis

Server /chassis # scope flexflashFlexFlash-0

Server /chassis/flexflash # retain-config slot1

This action will copy the config of slot1 to both the slots, mark slot1 as healthy, primary slot and slot2 (card must be present) as unhealthy secondary active.

This operation may disturb the host connectivity as well. Continue? [y|N] y

Server /chassis/flexflash/operational-profile*#commit

Server /chassis/flexflash/operational-profile#

Configuring BIOS Settings

Viewing BIOS Status

Procedure

 

Command or Action

Purpose

Step 1

Server# scope bios

Enters the BIOS command mode.

Step 2

Server /bios # show detail

Displays details of the BIOS status.

The BIOS status information contains the following fields:

Name

Description

BIOS Version

The version string of the running BIOS.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

30

OL-28893-01

Managing the Server

Configuring Main BIOS Settings

Name

Description

Boot Order

The order of bootable target types that the server will

 

attempt to use.

Boot Override Priority

This can be None, SCU, HV, or HUU.

FW Update/Recovery Status

The status of any pending firmware update or

 

recovery action.

FW Update/Recovery Progress

The percentage of completion of the most recent

 

firmware update or recovery action.

This example displays the BIOS status:

Server# scope bios

Server /bios # show detail

BIOS Version: "C460M1.1.2.2a.0 (Build Date: 01/12/2011)"

Boot Order: EFI,CDROM,HDD

Boot Override Priority:

FW Update/Recovery Status: NONE

FW Update/Recovery Progress: 100

Server /bios #

Configuring Main BIOS Settings

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope bios

Enters the BIOS command mode.

Step 2

Server /bios # scope main

Enters the main BIOS settings command mode.

Step 3

Configure the BIOS

The BIOS parameters available depend on the model of the server

 

settings.

that you are using. For descriptions and information about the options

 

 

for each BIOS setting, see one the following topics:

 

 

Main BIOS Parameters for C22 and C24 Servers , on page

 

 

183

 

 

Main BIOS Parameters for C200 and C210 Servers

 

 

Main BIOS Parameters for C250 Servers

 

 

Main BIOS Parameters for C260 Servers , on page 222

 

 

Main BIOS Parameters for C460 Servers , on page 253

Step 4

Server /bios/main #

Commits the transaction to the system configuration.

 

commit

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

31

Managing the Server

Configuring Advanced BIOS Settings

Command or Action

Purpose

Changes are applied on the next server reboot. If server power is on, you are prompted to choose whether to reboot now.

This example configures the BIOS to pause the boot upon a critical POST error and commits the transaction:

Server# scope bios

Server /bios # scope main

Server /bios/main # set POSTErrorPause Enabled

Server /bios/main *# commit

Changes to BIOS set-upparameters will require a reboot.

Do you want to reboot the system?[y|N] n

Changes will be applied on next reboot.

Server /bios/main #

Configuring Advanced BIOS Settings

Note Depending on your installed hardware, some configuration options described in this topic may not appear.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope bios

Enters the BIOS command mode.

Step 2

Server /bios # scope

Enters the advanced BIOS settings command mode.

 

advanced

 

Step 3 Configure the BIOS

settings.

Step 4 Server /bios/advanced #commit

The BIOS parameters available depend on the model of the server that you are using. For descriptions and information about the options for each BIOS setting, see one the following topics:

Advanced BIOS Parameters for C22 and C24 Servers , on page 184

Advanced BIOS Parameters for C200 and C210 Servers

Advanced BIOS Parameters for C250 Servers

Advanced BIOS Parameters for C260 Servers , on page 222

Advanced BIOS Parameters for C460 Servers , on page 253

Commits the transaction to the system configuration.

Changes are applied on the next server reboot. If server power is on, you are prompted to choose whether to reboot now.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

32

OL-28893-01

Managing the Server

Configuring Server Management BIOS Settings

Command or Action

Purpose

This example enables low voltage DDR memory mode and commits the transaction:

Server# scope bios

Server /bios # scope advanced

Server /bios/advanced # set LvDDRMode Enabled

Server /bios/advanced *# commit

Changes to BIOS set-upparameters will require a reboot.

Do you want to reboot the system?[y|N] n

Changes will be applied on next reboot.

Server /bios/advanced #

Configuring Server Management BIOS Settings

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope bios

Enters the BIOS command mode.

Step 2

Server /bios # scope

Enters the server management BIOS settings command mode.

 

server-management

 

Step 3 Configure the BIOS settings.

Step 4

Server

 

/bios/server-management#

 

commit

The BIOS parameters available depend on the model of the server that you are using. For descriptions and information about the options for each BIOS setting, see one the following topics:

Server Management BIOS Parameters for C22 and C24 Servers , on page 200

Server Management BIOS Parameters for C200 and C210 Servers

Server Management BIOS Parameters for C250 Servers

Server Management BIOS Parameters for C260 Servers , on page 232

Server Management BIOS Parameters for C460 Servers , on page 263

Commits the transaction to the system configuration.

Changes are applied on the next server reboot. If server power is on, you are prompted to choose whether to reboot now.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

33

Managing the Server

Restoring BIOS Defaults

This example enables automatic detection of the BMC and commits the transaction:

Server# scope bios

Server /bios # scopeserver-management

Server /bios/server-management#set BMCPnP Enabled

Server /bios/server-management*#commit

Changes to BIOS set-upparameters will require a reboot.

Do you want to reboot the system?[y|N] n

Changes will be applied on next reboot.

Server /bios/server-management#

Restoring BIOS Defaults

Before You Begin

You must log in as a user with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope bios

Enters the BIOS command mode.

Step 2

Server /bios # bios-setup-default

Restores BIOS default settings. This command

 

 

initiates a reboot.

This example restores BIOS default settings:

Server# scope bios

Server /bios # bios-setup-default

This operation will reset the BIOS set-uptokens to factory defaults.

All your configuration will be lost.

Changes to BIOS set-upparameters will initiate a reboot.

Continue?[y|N]y

Restoring BIOS Manufacturing Custom Defaults

In instances where the components of the BIOS no longer function as desired, you can restore the BIOS set up tokens to the manufacturing default values.

Note This action is only available for someC-Seriesservers.

Before You Begin

You must log in with admin privileges to perform this task.

The server must be powered off.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

34

OL-28893-01

Managing the Server

Restoring BIOS Manufacturing Custom Defaults

Procedure

 

Command or Action

Purpose

Step 1

Server# scope bios

Enters the BIOS command mode.

Step 2

Server /bios # restore-mfg-defaults

Restores the set up tokens to the manufacturing

 

 

default values.

This example shows how to restore the BIOS set up tokens to the manufacturing default values:

Server # scope bios

Server /bios # restore-mfg-defaults

This operation will reset the BIOS set-uptokens to manufacturing defaults.

The system will be powered on.

Continue? [y|n] N

Server /bios #

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

35

Managing the Server

Restoring BIOS Manufacturing Custom Defaults

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

36

OL-28893-01

C H A P T E R 4

Viewing Server Properties

This chapter includes the following sections:

Viewing Server Properties, page

37

Viewing CIMC Properties, page 38

Viewing CPU Properties, page 38

Viewing Memory Properties, page 39

Viewing Power Supply Properties, page 40

Viewing Storage Properties, page

40

Viewing PCI Adapter Properties,

page 46

Viewing Network Related Properties, page 46

Viewing Server Properties

Procedure

 

Command or Action

Purpose

Step 1

Server# show chassis[detail]

Displays server properties.

This example displays server properties:

Server# show chassis detail

Chassis:

Power: on

Serial Number: QCI140205ZG

Product Name: UCS C210 M2

PID : R210-2121605W

UUID: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF

Locator LED: off

Description:

Power Restore Policy: power-off

Power Delay Type: fixed

Power Delay Value(sec): 0

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

37

Viewing Server Properties

Viewing CIMC Properties

Server#

Viewing CIMC Properties

Note CIMC gets the current date and time from the server BIOS. To change this information, reboot the server and pressF2 when prompted to access the BIOS configuration menu. Then change the date or time using the options on the main BIOS configuration tab.

Procedure

 

Command or Action

Purpose

Step 1

Server# show cimc[detail]

Displays CIMC properties.

This example displays CIMC properties:

Server# show cimc detail

CIMC:

Firmware Version: 1.4(2.18)

Current Time: Wed Jan 11 07:01:50 2012

Boot-loaderVersion: 1.4(2.18).16

Server#

Viewing CPU Properties

Before You Begin

The server must be powered on, or the properties will not display.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # show cpu [detail]

Displays CPU properties.

This example displays CPU properties:

 

 

Server# scope chassis

 

 

 

Server /chassis # show cpu

 

 

Name

Cores

Version

 

 

------------

--------

--------------------------------------------------

CPU1

4

Intel(R) Xeon(R) CPU

E5520

@ 2.27GHz

CPU2

4

Intel(R) Xeon(R) CPU

E5520

@ 2.27GHz

Server /chassis #

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

38

OL-28893-01

Viewing Server Properties

Viewing Memory Properties

Viewing Memory Properties

Before You Begin

The server must be powered on, or the properties will not display.

Procedure

 

Command or Action

 

Purpose

Step 1

Server# scope chassis

 

Enters chassis command mode.

Step 2

Server /chassis # show dimm [detail]

Displays memory properties.

Step 3

Server /chassis # show dimm-summary

Displays DIMM summary information.

This example displays memory properties:

 

 

 

Server# scope chassis

 

 

 

 

Server /chassis # show dimm

Channel Speed (MHz)

Channel Type

Name

Capacity

-----------------------------------

-------------------

---------------

DIMM_A1

2048

MB

1067

 

Other

DIMM_A2

2048

MB

1067

 

Other

DIMM_B1

2048

MB

1067

 

Other

DIMM_B2

2048

MB

1067

 

Other

DIMM_C1

Not Installed

Unknown

 

Other

DIMM_C2

Not Installed

Unknown

 

Other

DIMM_D1

2048

MB

1067

 

Other

DIMM_D2

2048

MB

1067

 

Other

DIMM_E1

2048

MB

1067

 

Other

DIMM_E2

2048

MB

1067

 

Other

DIMM_F1

Not Installed

Unknown

 

Other

DIMM_F2

Not Installed

Unknown

 

Other

Server /chassis #

This example displays detailed information about memory properties:

Server# scope chassis

Server /chassis # show dimm detail Name DIMM_A1:

Capacity: 2048 MB Channel Speed (MHz): 1067 Channel Type: Other

Memory Type Detail: Synchronous

Bank Locator: NODE 0 CHANNEL 0 DIMM 0 Visibility: Yes

Operability: Operable

Manufacturer: 0x802C

Part Number: 18JSF25672PY-1G1D1Serial Number: 0xDA415F3F Asset Tag: Unknown

Data Width: 64 bits Name DIMM_A2:

Capacity: 2048 MB --More--

Server /chassis #

This example displays DIMM summary information:

Server# scope chassis

Server /chassis # show dimm-summary

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

39

Viewing Server Properties

Viewing Power Supply Properties

DIMM Summary:

Memory Speed: 1067 MHz

Total Memory: 16384 MB

Effective Memory: 16384 MB

Redundant Memory: 0 MB

Failed Memory: 0 MB

Ignored Memory: 0 MB

Number of Ignored Dimms: 0

Number of Failed Dimms: 0

Memory RAS possible: Memory configuration can support mirroring

Memory Configuration: Maximum Performance

Server /chassis #

Viewing Power Supply Properties

Before You Begin

The server must be powered on, or the properties will not display.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis #

show psu [detail]

Displays power supply properties.

This example displays power supply properties:

 

 

Server# scope chassis

 

 

 

Server /chassis # show psu

Out. Power (Watts)

Firmware

Status

Name

In. Power (Watts)

----------

----------------------------------------

--------

----------

PSU1

74

650

R0E

Present

PSU2

83

650

R0E

Present

Server /chassis #

Viewing Storage Properties

Viewing Storage Adapter Properties

Before You Begin

The server must be powered on, or the properties will not display.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

40

OL-28893-01

Viewing Server Properties

Viewing Storage Adapter Properties

Procedure

 

Command or Action

Step 1

Server# scope chassis

Step 2

Server /chassis # show storageadapter

 

[slot] [detail]

Purpose

Enters the chassis command mode.

Displays installed storage cards.

Note This command displays all MegaRAID controllers on the server that can be managed through CIMC. If an installed controller or storage device is not displayed, then it cannot be managed through CIMC.

Step 3

Server /chassis # scope storageadapterslot

Enters command mode for an installed storage

 

 

 

card.

 

Step 4

Server /chassis/storageadapter # show bbu Displays battery backup unit information for the

 

[detail]

 

storage card.

Step 5

Server /chassis/storageadapter #

show

Displays RAID levels supported by the storage

 

capabilites [detail]

 

card.

 

Step 6

Server /chassis/storageadapter #

show

Displays number of errors seen by the storage

 

error-counters[detail]

 

card.

 

Step 7

Server /chassis/storageadapter #

show

Displays firmware version information for the

 

firmware-versions[detail]

 

storage card.

Step 8

Server /chassis/storageadapter #

show

Displays hardware information for the storage

 

hw-config[detail]

 

card.

 

Step 9

Server /chassis/storageadapter #

show

Displays manufacturer data for the storage card.

 

mfg-data[detail]

 

 

 

Step 10

Server /chassis/storageadapter #

show

Displays adapter PCI information for the storage

 

pci-info[detail]

 

card.

 

Step 11

Server /chassis/storageadapter #

show

Displays running firmware information for the

 

running-firmware-images[detail]

storage card.

Step 12

Server /chassis/storageadapter #

show

Displays adapter firmware settings for the storage

 

settings [detail]

 

card.

 

Step 13

Server /chassis/storageadapter #

show

Displays firmware images to be activated on

 

startup-firmware-images[detail]

startup for the storage card.

This example displays storage properties:

 

 

 

Server# scope chassis

 

 

 

Server /chassis # show storageadapter

Serial Number

Firmware Package Build

PCI Slot Product Name

--------

------------------------------------------------

-------------------------

SAS

LSI MegaRAID SAS 9260-8i

SV93404392

12.12.0-0038

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

41

Viewing Server Properties

Viewing the Flexible Flash Controller Properties

Product ID

Battery Status

Cache Memory Size

------------------

--------------

--------------

LSI Logic

fully charged

0 MB

Server /chassis #

This example displays battery backup unit information for the storage card named SAS:

Server# scope chassis

storageadapter SAS

 

 

Server /chassis # scope

 

 

Server /chassis/storageadapter # show bbu

Current

Charge Charging State

Controller Battery Type

Battery Present

Voltage

----------------------

---------------

----------

----------

--------------------

SAS

iBBU

true

4.051 V

0.000 A

100% fully charged

Server /chassis/storageadapter #

Viewing the Flexible Flash Controller Properties

Before You Begin

Cisco Flexible Flash must be supported by your platform.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # show flexflash [detail]

(Optional) Displays the available Cisco Flexible

 

 

Flash controllers.

Step 3

Server /chassis # scope flexflash index

Enters the Cisco Flexible Flash controller command

 

 

mode for the specified controller. At this time, the

 

 

only permissible index value isFlexFlash-0.

Step 4

Server /chassis/flexflash # show

Displays the operational profile properties.

 

operational-profile[detail]

 

This example displays the properties of the flash controller:

Server# scope chassis

 

 

 

 

Server /chassis # show flexflash

Firmware Version

Vendor

Internal State

Controller

Product Name

Has Error

------------

----------------

----------

-----------------

--------

---------------

FlexFlash-0

Cisco FlexFlash

No

1.2 build 247

Cypress

Connected

Server /chassis # scope flexflashFlexFlash-0

Server /chassis # showoperational-profile

Host Accessible VDs

Primary Member Slot

I/O Error Threshold

--------------------

--------------------

--------------------

slot1

100

SCU Drivers

Server /chassis/flexflash #

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

42

OL-28893-01

Viewing Server Properties

Viewing Physical Drive Properties

Viewing Physical Drive Properties

Procedure

 

Command or Action

 

Purpose

Step 1

Server# scope chassis

 

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed

 

 

 

storage card.

Step 3

Server /chassis/storageadapter #

show

Displays physical drive information for the

 

physical-drive[drive-number] [detail]

storage card.

Step 4

Server /chassis/storageadapter #

show

Displays the number of physical drives on

 

physical-drive-count[detail]

 

the storage card.

Step 5

Server /chassis/storageadapter #

scope

Enters command mode for the specified

 

physical-drivedrive-number

 

physical drive.

Step 6

Server /chassis/storageadapter/physical-drive#

Displays general information about the

 

show general [detail]

 

specified physical drive.

Step 7

Server /chassis/storageadapter/physical-drive#

Displays inquiry data about the specified

 

show inquiry-data[detail]

 

physical drive.

Step 8

Server /chassis/storageadapter/physical-drive#

Displays status information about the

 

show status [detail]

 

specified physical drive.

This example displays general information about physical drive number 1 on the storage card named SAS:

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # scope physical-drive 1

Server /chassis/storageadapter/physical-drive#show general

Slot Number 1:

Controller: SAS

Enclosure Device ID: 27

Device ID: 34

Sequence Number: 2

Media Error Count: 0

Other Error Count: 0

Predictive Failure Count: 0

Link Speed: 6.0 Gb/s

Interface Type: SAS

Media Type: HDD

Block Size: 512

Block Count: 585937500

Raw Size: 286102 MB

Non Coerced Size: 285590 MB

Coerced Size: 285568 MB

SAS Address 0: 500000e112693fa2

SAS Address 1:

Connected Port 0:

Connected Port 1:

Connected Port 2:

Connected Port 3:

Connected Port 4:

Connected Port 5:

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

43

Viewing Server Properties

Viewing Virtual Drive Properties

Connected Port 6:

Connected Port 7:

Power State: powersave

Server /chassis/storageadapter/physical-drive#

This example displays inquiry data about physical drive number 1 on the storage card named SAS:

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # scope physical-drive 1

Server /chassis/storageadapter/physical-drive#show inquiry-data

Slot Number 1:

Controller: SAS

Product ID: MBD2300RC

Drive Firmware: 5701

Drive Serial Number: D010P9A0016D

Server /chassis/storageadapter/physical-drive#

This example displays status information about physical drive number 1 on the storage card named SAS:

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # scope physical-drive 1

Server /chassis/storageadapter/physical-drive#show inquiry-data

Slot Number 1:

Controller: SAS

State: online

Online: true

Fault: false

Server /chassis/storageadapter/physical-drive#

Viewing Virtual Drive Properties

Procedure

 

Command or Action

 

Purpose

Step 1

Server# scope chassis

 

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed storage

 

 

 

card.

Step 3

Server /chassis/storageadapter #

show

Displays virtual drive information for the

 

virtual-drive[drive-number] [detail]

storage card.

Step 4

Server /chassis/storageadapter #

show

Displays the number of virtual drives

 

virtual-drive-count[detail]

 

configured on the storage card.

Step 5

Server /chassis/storageadapter #

scope

Enters command mode for the specified

 

virtual-drivedrive-number

 

virtual drive.

Step 6

Server /chassis/storageadapter/virtual-drive#

Displays physical drive information about the

 

show physical-drive[detail]

 

specified virtual drive.

This example displays information about virtual drives on the storage card named SAS:

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # show virtual-drive

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

44

OL-28893-01

Viewing Server Properties

Viewing Nvidia GPU Card Information

Virtual Drive

Status

Name

Size

 

RAID Level

--------------

---------------

------------------------

----------

----------

0

Optimal

SLES1SP1beta5

30720

MB

RAID 0

1

Optimal

RHEL5.5

30720

MB

RAID 0

2

Optimal

W2K8R2_DC

30720

MB

RAID 0

3

Optimal

VD_3

30720

MB

RAID 0

4

Optimal

ESX4.0u2

30720

MB

RAID 0

5

Optimal

VMs

285568 MB

RAID 0

6

Optimal

RHEL6-35GB

35840

MB

RAID 0

7

Optimal

OS_Ins_Test_DR

158720 MB

RAID 0

8

Optimal

 

285568 MB

RAID 1

Server /chassis/storageadapter #

This example displays physical drive information about virtual drive number 1 on the storage card named SAS:

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # scope virtual-drive 1

Server /chassis/storageadapter/virtual-drive#

show physical-drive

Span

Physical Drive

Status

Starting Block

Number Of Blocks

-----

--------------

----------

--------------

----------------

0

12

online

62914560

62914560

Server /chassis/storageadapter/virtual-drive#

Viewing Nvidia GPU Card Information

These commands are not available on all UCS C-seriesservers.

Before You Begin

The server must be powered on to view information on the Nvidia GPU cards.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # show gpu

Displays the available Nvidia GPU cards on the

 

 

system.

Step 3

Server /chassis # scope gpu

Enters the GPU card command mode. Specify the

 

slot-number

slot number of the GPU card.

Step 4

Server /chassis/gpu # show gpu-list

Displays temperature information on the GPU

 

 

cards.

This example shows how to view the temperature information of the available GPU cards on the system:

Server # scope chassis

Server /chassis # show gpu

Slot

Product Name

Num of GPUs

----

------------

-----------

5

Nvidia GRID K2 @ BD

2

Server /chassis # scope gpu 5

Server /chassis/gpu # show gpu-list

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

45

Viewing Server Properties

Viewing PCI Adapter Properties

GPU ID

Temperature

------

-----------

032

1 33

Server /chassis/gpu #

Viewing PCI Adapter Properties

Before You Begin

The server must be powered on, or the properties will not display.

Procedure

 

Command or Action

 

Purpose

Step 1

Server# scope chassis

 

Enters the chassis command mode.

Step 2

Server /chassis # show pci-adapter [detail] Displays PCI adapter properties.

This example displays PCI adapter properties:

 

Server# scope chassis

pci-adapter

 

 

Server /chassis # show

Device ID

Product Name

Name

Slot

Vendor ID

---------------------

------------

------------

-------------------------

PCIe Adapter1

1

0x1137

0x0042

Cisco UCS P81E Virtual...

PCIe Adapter2

5

0x1077

0x2432

Qlogic QLE2462 4Gb dua...

Server /chassis #

Viewing Network Related Properties

Viewing LOM Properties

You can view the MAC addresses of the LAN On Motherboard (LOM) Ethernet ports.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope cimc

Enters the CIMC command mode.

Step 2

Server /cimc # scope network

Enters the network command mode.

Step 3

Server /cimc/network # show lom-mac-list

Displays the MAC addresses of the LOM

 

[detail]

ports.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

46

OL-28893-01

Viewing Server Properties

Viewing LOM Properties

This example shows how to display the MAC addresses of the LOM ports:

Server# scope cimc

network

Server /cimc # scope

Server /cimc/network

# showlom-mac-list

Interface

MAC Address

---------------

--------------------

eth0

010000002000

eth1

010000002000

Server /cimc/network

#

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

47

Viewing Server Properties

Viewing LOM Properties

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

48

OL-28893-01

C H A P T E R 5

Viewing Server Sensors

This chapter includes the following sections:

Viewing Power Supply Sensors, page 49

Viewing Fan Sensors, page 50

 

Viewing Temperature Sensors, page 50

Viewing Voltage Sensors,

page

51

Viewing Current Sensors,

page

52

Viewing Storage Sensors,

page

52

Viewing Power Supply Sensors

Procedure

 

Command or Action

Purpose

Step 1

Server# scope sensor

Enters sensor command mode.

Step 2

Server /sensor #

show psu [detail]

Displays power supply sensor statistics for the

 

 

 

server.

Step 3

Server /sensor #

show psu-redundancy

Displays power supply redundancy sensor status

 

[detail]

 

for the server.

This example displays power supply sensor statistics:

Server# scope sensor

 

 

 

 

 

Server /sensor # show psu

Reading

Units

Min. Warning

Max. Warning

Name

Sensor Status

Min. Failure

Max. Failure

 

 

 

 

---------------------------------------------------------------------------

---------------------------------------------

 

 

 

PSU1_STATUS

Normal

present

 

 

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

49

Viewing Server Sensors

Viewing Fan Sensors

PSU2_STATUS

Normal

present

Server /sensor # showpsu-redundancy

Name

Reading

Sensor Status

--------------------

----------

--------------------

PSU_REDUNDANCY

full

Normal

Server /sensor #

Viewing Fan Sensors

Procedure

 

 

Command or Action

 

 

Purpose

 

Step 1

 

Server# scope sensor

 

 

Enters sensor command mode.

Step 2

 

Server /sensor # show fan [detail]

 

Displays fan sensor statistics for the server.

This example displays fan sensor statistics:

 

 

 

 

Server# scope sensor

 

 

 

 

Server /sensor # show fan

Reading

Units

Min. Warning

Max. Warning

Name

 

Sensor Status

Min. Failure

 

Max. Failure

 

 

 

 

------------------------------------------------------------------------------------

------------------------------

2400

RPM

N/A

N/A

W793_FAN2_TACH1

Normal

800

 

N/A

2400

RPM

N/A

N/A

W793_FAN2_TACH2

Normal

800

 

N/A

2300

RPM

N/A

N/A

W793_FAN3_TACH1

Normal

800

 

N/A

2300

RPM

N/A

N/A

W793_FAN3_TACH2

Normal

800

 

N/A

2400

RPM

N/A

N/A

W793_FAN4_TACH1

Normal

800

 

N/A

1600

RPM

N/A

N/A

W793_FAN4_TACH2

Normal

800

 

N/A

 

 

 

 

Server /sensor #

 

 

 

 

Viewing Temperature Sensors

 

 

 

 

Procedure

 

 

 

 

 

 

 

 

Command or Action

 

 

Purpose

 

Step 1

Server# scope sensor

 

 

Enters sensor command mode.

Step 2

Server /sensor # show temperature[detail]

Displays temperature sensor statistics for the

 

 

 

 

 

server.

 

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

50

OL-28893-01

Viewing Server Sensors

Viewing Voltage Sensors

This example displays temperature sensor statistics:

Server# scope sensor

 

 

 

 

 

Server /sensor # show temperature

Reading

Units

Min. Warning Max. Warning

Name

 

Sensor Status

Min. Failure Max. Failure

 

 

----------------------------------

-------------------------------------------------

------------------------

Normal

32.0

C

N/A

80.0

IOH_TEMP_SENS

85.0

N/A

Normal

31.0

C

N/A

80.0

P2_TEMP_SENS

81.0

N/A

Normal

34.0

C

N/A

80.0

P1_TEMP_SENS

81.0

N/A

Normal

20.0

C

N/A

90.0

DDR3_P2_D1_TMP

N/A

95.0

Normal

21.0

C

N/A

90.0

DDR3_P1_A1_TMP

N/A

95.0

Normal

28.0

C

N/A

40.0

FP_AMBIENT_TEMP

N/A

45.0

 

 

 

 

 

Server /sensor #

Viewing Voltage Sensors

Procedure

 

Command or Action

 

Purpose

 

 

Step 1

Server# scope sensor

 

Enters sensor command mode.

Step 2

Server /sensor # show voltage [detail]

Displays voltage sensor statistics for the

 

 

 

 

server.

 

 

This example displays voltage sensor statistics:

 

 

 

 

Server# scope sensor

 

 

 

 

 

Server /sensor # show voltage

Reading

Units

Min. Warning Max. Warning

Name

 

Sensor Status

Min. Failure Max. Failure

 

 

----------------------------------

-------------------------------------------------

------------------------

Normal

3.022

V

N/A

N/A

P3V_BAT_SCALED

2.798

3.088

Normal

12.154

V

N/A

N/A

P12V_SCALED

12.331

11.623

Normal

5.036

V

N/A

N/A

P5V_SCALED

5.157

4.844

Normal

3.318

V

N/A

N/A

P3V3_SCALED

3.381

3.191

Normal

5.109

V

N/A

N/A

P5V_STBY_SCALED

4.844

5.157

Normal

0.950

V

N/A

N/A

PV_VCCP_CPU1

1.391

0.725

Normal

0.891

V

N/A

N/A

PV_VCCP_CPU2

1.391

0.725

Normal

1.499

V

N/A

N/A

P1V5_DDR3_CPU1

1.450

1.548

Normal

1.499

V

N/A

N/A

P1V5_DDR3_CPU2

1.450

1.548

Normal

1.087

V

N/A

N/A

P1V1_IOH

1.136

1.068

Normal

1.773

V

N/A

N/A

P1V8_AUX

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

51

Viewing Server Sensors

Viewing Current Sensors

1.744 1.852

Server /sensor #

Viewing Current Sensors

Procedure

 

Command or Action

 

Purpose

 

 

Step 1

Server# scope sensor

 

Enters sensor command mode.

Step 2

Server /sensor # show current [detail]

Displays current sensor statistics for the server.

This example displays current sensor statistics:

 

 

 

 

Server# scope sensor

 

 

 

 

Server /sensor # show current

Reading

Units

Min. Warning Max. Warning

Name

Sensor Status

Min. Failure Max. Failure

 

 

 

 

-----------------------------------------------------------------------------------

------------------------

16.00

AMP

N/A

147.20

VR_P2_IMON

Normal

N/A

164.80

27.20

AMP

N/A

147.20

VR_P1_IMON

Normal

N/A

164.80

 

 

 

 

Server /sensor #

 

 

 

 

Viewing Storage Sensors

 

 

 

 

Procedure

 

 

 

 

 

 

Command or Action

 

Purpose

 

 

Step 1

Server# scope chassis

 

Enters chassis command mode.

Step 2

Server /chassis # show hdd [detail]

Displays storage sensor information.

The displayed fields are described in the following table:

Name

Description

Name column

The name of the storage device.

Status column

A brief description of the storage device status.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

52

OL-28893-01

Viewing Server Sensors

Viewing Storage Sensors

Name

Description

LED Status column

The current LED color, if any.

 

To make the physical LED on the storage device blink, select Turn On

 

from the drop-downlist. To let the storage device control whether the

 

LED blinks, select Turn Off.

 

Note

This information is only available for some C-Series

 

 

servers.

This example displays storage sensor information:

Server# scope chassis

Server /chassis # show hdd

Name

Status

--------------------

--------------------

HDD_01_STATUS

present

HDD_02_STATUS

present

HDD_03_STATUS

present

HDD_04_STATUS

present

Server /chassis #

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

53

Viewing Server Sensors

Viewing Storage Sensors

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

54

OL-28893-01

C H A P T E R 6

Managing Remote Presence

This chapter includes the following sections:

Managing the Virtual KVM, page 55

Configuring Virtual Media, page 58

Managing Serial over LAN, page 61

Managing the Virtual KVM

KVM Console

The KVM console is an interface accessible from CIMC that emulates a direct keyboard, video, and mouse (KVM) connection to the server. The KVM console allows you to connect to the server from a remote location.

Instead of using CD/DVD or floppy drives physically connected to the server, the KVM console uses virtual media, which are actual disk drives or disk image files that are mapped to virtual CD/DVD or floppy drives. You can map any of the following to a virtual drive:

CD/DVD or floppy drive on your computer

Disk image files (ISO or IMG files) on your computer

USB flash drive on your computer

CD/DVD or floppy drive on the network

Disk image files (ISO or IMG files) on the network

USB flash drive on the network

You can use the KVM console to install an OS on the server.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

55

Managing Remote Presence

Enabling the Virtual KVM

Enabling the Virtual KVM

Before You Begin

You must log in as a user with admin privileges to enable the virtual KVM.

Procedure

 

Command or Action

 

Purpose

 

Step 1

Server# scope kvm

 

Enters KVM command mode.

Step 2

Server /kvm # set enabled yes

Enables the virtual KVM.

Step 3

Server /kvm #

commit

 

Commits the transaction to the system

 

 

 

 

configuration.

Step 4

Server /kvm #

show [detail]

(Optional) Displays the virtual KVM

 

 

 

 

configuration.

This example enables the virtual KVM:

 

 

 

Server# scope kvm

 

 

 

 

Server /kvm # set enabled yes

 

 

 

Server /kvm *# commit

 

 

 

 

Server /kvm # show

 

Active Sessions Enabled KVM Port

Encryption Enabled Local Video

--------------------------------------------------------

--------

no

yes

 

0

yes

2068

Server /kvm #

Disabling the Virtual KVM

Before You Begin

You must log in as a user with admin privileges to disable the virtual KVM.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope kvm

Enters KVM command mode.

Step 2

Server /kvm # set enabled no

Disables the virtual KVM.

 

 

Note

Disabling the virtual KVM disables access to

 

 

 

the virtual media feature, but does not detach

 

 

 

the virtual media devices if virtual media is

 

 

 

enabled.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

56

OL-28893-01

Managing Remote Presence

Configuring the Virtual KVM

 

Command or Action

 

Purpose

 

Step 3

Server /kvm #

commit

 

Commits the transaction to the system configuration.

Step 4

Server /kvm #

show [detail]

(Optional) Displays the virtual KVM configuration.

This example disables the virtual KVM:

 

 

 

Server# scope kvm

 

 

 

 

Server /kvm # set enabled no

 

 

 

Server /kvm *# commit

 

 

 

 

Server /kvm # show

 

Active Sessions Enabled KVM Port

Encryption Enabled Local Video

----------------------------------------------------------------

no

yes

 

0

no

2068

Server /kvm #

Configuring the Virtual KVM

Before You Begin

You must log in as a user with admin privileges to configure the virtual KVM.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope kvm

Enters KVM command mode.

Step 2

Server /kvm # set enabled {yes |no}

Enables or disables the virtual KVM.

Step 3

Server /kvm #

set encrypted {yes|

If encryption is enabled, the server encrypts all video

 

no}

 

information sent through the KVM.

Step 4

Server /kvm # set kvm-port port

Specifies the port used for KVM communication.

Step 5

Server /kvm #

set local-video{yes|

If local video is yes, the KVM session is also

 

no}

 

displayed on any monitor attached to the server.

Step 6

Server /kvm # setmax-sessions

Specifies the maximum number of concurrent KVM

 

sessions

 

sessions allowed. The sessions argument is an integer

 

 

 

between 1 and 4.

Step 7

Server /kvm #

commit

Commits the transaction to the system configuration.

Step 8

Server /kvm #

show [detail]

(Optional) Displays the virtual KVM configuration.

This example configures the virtual KVM and displays the configuration:

Server# scope kvm

Server /kvm # set enabled yes

Server /kvm *# set encrypted no

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

57

Managing Remote Presence

Configuring Virtual Media

Server /kvm *# setkvm-port2068

Server /kvm *# setmax-sessions4

Server /kvm *# setlocal-videoyes

Server /kvm *# commit

Server /kvm # show detail

KVM Settings:

Encryption Enabled: no

Max Sessions: 4

Local Video: yes

Active Sessions: 0

Enabled: yes

KVM Port: 2068

Server /kvm #

What to Do Next

Launch the virtual KVM from the GUI.

Configuring Virtual Media

Before You Begin

You must log in as a user with admin privileges to configure virtual media.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope vmedia

Enters virtual media command mode.

Step 2

Server /vmedia #

set enabled {yes|

Enables or disables virtual media. By default, virtual

 

no}

 

media is disabled.

 

 

 

Note

Disabling virtual media detaches the virtual

 

 

 

 

CD, virtual floppy, and virtual HDD devices

 

 

 

 

from the host.

Step 3

Server /vmedia # set encryption {yes

Enables or disables virtual media encryption.

 

| no}

 

 

 

Step 4

Server /vmedia #

commit

Commits the transaction to the system configuration.

Step 5

Server /vmedia #

show [detail]

(Optional) Displays the virtual media configuration.

This example configures virtual media encryption:

Server# scope vmedia

Server /vmedia # set enabled yes

Server /vmedia *# set encryption yes

Server /vmedia *# commit Server /vmedia #show detail vMedia Settings:

Encryption Enabled: yes Enabled: yes

Max Sessions: 1 Active Sessions: 0

Server /vmedia #

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

58

OL-28893-01

Managing Remote Presence

Configuring Network Mounted vMedia Mapping

What to Do Next

Use the KVM to attach virtual media devices to a host.

Configuring Network Mounted vMedia Mapping

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

Command or Action Step 1Server # scope vmedia

Step 2 Server /vmedia #map-cifs

{volume-name| remote-share| remote-file-path[mount options]

Purpose

Enters the virtual media command mode.

Maps a CIFS file for vMedia. You must specify the following:

Name of the volume to create

Remote share including IP address and the exported directory

Path of the remote file corresponding to the exported directory.

(Optional) Mapping options

Username and password to connect to the server

Step 3

Server /vmedia # map-nfs

Maps an NFS file for vMedia. You must specify the

 

{volume-name| remote-share|

following:

 

remote-file-path} [mount options]

Name of the volume to create

 

 

 

 

Remote share including IP address and the exported

 

 

directory

 

 

Path of the remote file corresponding to the exported

 

 

directory.

 

 

(Optional) Mapping options

Step 4

Server /vmedia # map-www

Maps an HTTPS file for vMedia. You must specify the

 

{volume-name| remote-share|

following:

 

remote-file-path[mount options]

Name of the volume to create

 

 

 

 

Remote share including IP address and the exported

 

 

directory

 

 

Path of the remote file corresponding to the exported

 

 

directory.

 

 

(Optional) Mapping options

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

59

Managing Remote Presence

Viewing Network Mount vMedia Mapping Properties

Command or Action

Purpose

Username and password to connect to the server

This example shows how to create a CIFS network mounted vMedia mapping:

Server # scope vmedia

Server /vmedia # map-cifssample-volume //10.10.10.10/project /test/sample

Server username:

Server password: ****

Confirm password: ****

Server /vmedia #

Viewing Network Mount vMedia Mapping Properties

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server # scope vmedia

Enters the virtual media command mode.

Step 2

Server /vmedia # show mappings detail

Displays information on all the vmedia mapping

 

 

that are configured.

This example shows how to view the properties of all the configured vmedia mapping:

Server # scope vmedia

Server /vmedia # show mappings

Volume

Map-status

Drive-type

remote-share

remote-file

mount-type

------

----------

------------

----------------------------------------

-----------

Huu

OK

removable

http://10.104.236.99/ rhel-server-6.1-x86_6.iso

www

Rhel

OK

CD

http://10.104.236.99/ rhel-server-6.1-x86_6.iso

www

Removing Network Mounted vMedia Mapping

Before You Begin

You must log in with admin privileges to perform this task.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

60

OL-28893-01

Managing Remote Presence

Managing Serial over LAN

Procedure

 

Command or Action

Purpose

Step 1

Server # scope vmedia

Enters the virtual media command mode.

Step 2

Server /vmedia # unmap volume_name

Specifies the volume name to unmap.

This example shows how to unmap a local vmedia volume:

Server # scope vmedia

Server /vmedia # show mappings

Volume

Map-status

Drive-type

remote-share

remote-file

mount-type

------

----------

------------

----------------------------------------

-----------

Huu

OK

removable

http://10.104.236.99/ rhel-server-6.1-x86_6.iso

www

Rhel

OK

CD

http://10.104.236.99/ rhel-server-6.1-x86_6.iso

www

Server /vmedia # unmap huu

 

 

 

 

Server /vmedia # show mappings

 

 

 

 

Volume

Map-status

Drive-type

remote-share

remote-file

mount-type

------

----------

------------

----------------------------------------

-----------

Rhel

OK

CD

http://10.104.236.99/ rhel-server-6.1-x86_6.iso

www

Server /vmedia #

Managing Serial over LAN

Serial Over LAN

Serial over LAN (SoL) is a mechanism that enables the input and output of the serial port of a managed system to be redirected via an SSH session over IP. SoL provides a means of reaching the host console via CIMC.

Guidelines and Restrictions for Serial Over LAN

For redirection to SoL, the server console must have the following configuration:

console redirection to serial port A

no flow control

baud rate the same as configured for SoL

VT-100terminal type

legacy OS redirection disabled

The SoL session will display line-orientedinformation such as boot messages, andcharacter-orientedscreen menus such as BIOS setup menus. If the server boots an operating system or application with abitmap-oriented

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

61

Managing Remote Presence

Configuring Serial Over LAN

display, such as Windows, the SoL session will no longer display. If the server boots a command-line-orientedoperating system (OS), such as Linux, you may need to perform additional configuration of the OS in order to properly display in an SoL session.

In the SoL session, your keystrokes are transmitted to the console except for the function key F2. To send an F2 to the console, press the Escape key, then press 2.

Configuring Serial Over LAN

Before You Begin

You must log in as a user with admin privileges to configure serial over LAN (SoL).

Procedure

 

Command or Action

Purpose

Step 1

Server# scope sol

Enters SoL command mode.

Step 2

Server /sol # set enabled

Enables or disables SoL on this server.

 

{yes| no}

 

Step 3 Server /sol #set baud-rate {9600 |19200 |38400 |57600 |115200}

Step 4 Server /sol #set comport

{com0| com1

Sets the serial baud rate the system uses for SoL communication.

Note The baud rate must match the baud rate configured in the server serial console.

(Optional)

Sets the serial port through which the system routes SoL communications.

Note This field is only available on someC-Seriesservers. If it is not available, the server always uses COM port 0 for SoL communication.

You can specify:

com0SoLcommunication is routed through COM port 0, an externally accessible serial port that supports either a physical RJ45 connection to an external device or a virtual SoL connection to a network device.

If you select this option, the system enables SoL and disables the RJ45 connection, which means that the server can no longer support an external serial device.

com1SoLcommunication is routed through COM port 1, an internal port accessible only through SoL.

If you select this option, you can use SoL on COM port 1 and the physical RJ45 connection on COM port 0.

Note Changing the comport setting disconnects any existing SoL sessions.

Step 5

Server /sol # commit

Commits the transaction to the system configuration.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

62

OL-28893-01

Managing Remote Presence

Launching Serial Over LAN

 

Command or Action

Purpose

Step 6

Server /sol # show [detail]

(Optional) Displays the SoL settings.

This example configures SoL:

Server# scope sol

Server /sol # set enabled yes

Server /sol *# setbaud-rate115200

Server /sol

*# commit

 

Server /sol

# show

Com Port

Enabled Baud Rate(bps)

----------------------

--------

yes

115200

com2

Server /sol # show detail

Serial Over LAN:

Enabled: yes

Baud Rate(bps): 115200

Com Port: com2

Server /sol #

Launching Serial Over LAN

Procedure

 

Command or Action

Purpose

Step 1

Server# connect host

Opens a serial over LAN (SoL) connection to the redirected

 

 

server console port. You can enter this command in any

 

 

command mode.

What to Do Next

To end the SoL session, you must close the CLI session. For example, to end an SoL session over an SSH connection, disconnect the SSH connection.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

63

Managing Remote Presence

Launching Serial Over LAN

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

64

OL-28893-01

C H A P T E R 7

Managing User Accounts

This chapter includes the following sections:

Configuring Local Users, page

65

Configuring Active Directory,

page 66

Viewing User Sessions, page 71

Terminating a User Session, page 71

Configuring Local Users

Before You Begin

You must log in as a user with admin privileges to configure or modify local user accounts.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope userusernumber

Enters user command mode for user number usernumber.

Step 2

Server /user #

set enabled {yes

Enables or disables the user account on the CIMC.

 

| no}

 

 

Step 3

Server /user #

set name

Specifies the username for the user.

 

username

 

 

Step 4

Server /user #

set password

You are prompted to enter the password twice.

Step 5

Server /user # set role{readonly

Specifies the role assigned to the user. The roles are as

 

| user| admin}

follows:

readonlyThisuser can view information but cannot make any changes.

userThisuser can do the following:

View all information

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

65

Managing User Accounts

Configuring Active Directory

Command or Action

Purpose

Manage the power control options such as power on, power cycle, and power off

Launch the KVM console and virtual media

Clear all logs

Toggle the locator LED

adminThisuser can perform all actions available through the GUI, CLI, and IPMI.

Step 6

Server /user # commit

Commits the transaction to the system configuration.

This example configures user 5 as an admin:

Server# scope user 5

 

 

Server

/user # set enabled yes

 

Server

/user *# set name john

 

Server

/user *# set password

 

Please

enter password:

 

 

Please

confirm password:

 

 

Server

/user *# set role readonly

 

Server

/user *# commit

 

 

Server

/user # show

Role

Enabled

User

Name

------

----------------

----------------

5

john

readonly yes

Configuring Active Directory

Active Directory

Active Directory is a technology that provides a variety of network services including LDAP-likedirectory services,Kerberos-basedauthentication, andDNS-basednaming. The CIMC utilizes theKerberos-basedauthentication service of Active Directory.

When Active Directory is enabled in the CIMC, user authentication and role authorization is performed by Active Directory for user accounts not found in the local user database.

you can require the server to encrypt data sent to Active Directory.

Configuring the Active Directory Server

The CIMC can be configured to use Active Directory for user authentication and authorization. To use Active Directory, configure users with an attribute that holds the user role and locale information for the CIMC. You can use an existing LDAP attribute that is mapped to the CIMC user roles and locales or you can modify the Active Directory schema to add a new custom attribute, such as the CiscoAVPair attribute, which has an

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

66

OL-28893-01

Managing User Accounts

Configuring the Active Directory Server

attribute ID of 1.3.6.1.4.1.9.287247.1. For more information about altering the Active Directory schema, see the article at http://technet.microsoft.com/en-us/library/bb727064.aspx.

The following steps are to be performed on the Active Directory server.

Note This example creates a custom attribute named CiscoAVPair, but you can also use an existing LDAP attribute that is mapped to the CIMC user roles and locales.

Procedure

Step 1 Ensure that the Active Directory schemasnap-inis installed.

Step 2 Using the Active Directory schema snap-in, add a new attribute with the following properties:

Properties

Value

Common Name

CiscoAVPair

LDAP Display Name

CiscoAVPair

Unique X500 Object ID

1.3.6.1.4.1.9.287247.1

Description

CiscoAVPair

Syntax

Case Sensitive String

Step 3 Add the CiscoAVPair attribute to the user class using the Active Directorysnap-in:

a)Expand the Classes node in the left pane and type U to select the user class.

b)Click the Attributes tab and clickAdd.

c)Type C to select the CiscoAVPair attribute.

d)Click OK.

Step 4 Add the following user role values to the CiscoAVPair attribute, for the users that you want to have access to CIMC:

Role

CiscoAVPair Attribute Value

admin

shell:roles="admin"

user

shell:roles="user"

read-only

shell:roles="read-only"

Note For more information about adding values to attributes, see the article athttp://technet.microsoft.com/ en-us/library/bb727064.aspx.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

67

Managing User Accounts

Configuring Active Directory in CIMC

What to Do Next

Use the CIMC to configure Active Directory.

Configuring Active Directory in CIMC

Configure Active Directory (AD) in CIMC when you want to use an AD server for local user authentication and authorization.

Before You Begin

You must log in as a user with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope ldap

Enters the LDAP command mode for AD configuration.

Step 2

Server /ldap # set enabled

Enables or disables AD. When AD is enabled, user

 

{yes| no}

authentication and role authorization is performed by AD for

 

 

user accounts not found in the local user database.

Step 3

Server /ldap # set dcn dc-host

Specifies an Active Directory domain controller (DC) host

 

 

name or IP address. You can specify up to three DCs using

 

 

index n values from 1 to 3.

Step 4

Server /ldap # set gcn gc-host

Specifies an Active Directory global catalog (GC) server host

 

 

name or IP address. You can specify up to three GCs using

 

 

index n values from 1 to 3.

Step 5

Server /ldap # set timeout

Specifies the number of seconds the CIMC waits until the

 

seconds

LDAP search operation times out.

Step 6

Server /ldap # set encrypted

If encryption is enabled, the server encrypts all information

 

{yes| no}

sent to AD.

Step 7

Server /ldap # set base-dn

Specifies the domain that all users must be in.

 

domain-name

 

Step 8

Server /ldap # set attribute

 

name

Specify an LDAP attribute that contains the role and locale information for the user. This property is always a name-valuepair. The system queries the user record for the value that matches this attribute name.

You can use an existing LDAP attribute that is mapped to the CIMC user roles and locales or you can create a custom attribute, such as the CiscoAVPair attribute, which has the following attribute ID:

1.3.6.1.4.1.9.287247.1

Note If you do not specify this property, user access is restricted toread-only.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

68

OL-28893-01

Managing User Accounts

Configuring Active Directory Groups in CIMC

 

Command or Action

Purpose

Step 9

Server /ldap # commit

Commits the transaction to the system configuration.

Step 10

Server /ldap # show [detail]

(Optional) Displays the AD configuration.

This example configures AD using the CiscoAVPair attribute:

Server# scope ldap

Server /ldap # set enabled yes

Server /ldap *# set dc1 192.0.20.123

Server /ldap *# set gc1 192.0.20.11

Server /ldap *# set timeout 60

Server /ldap *# set encrypted yes

Server /ldap *# setbase-dnexample.com

Server /ldap *# set attribute CiscoAVPair

Server /ldap *# commit

Server /ldap # show detail

LDAP Settings:

Domain Controller 1: 192.0.20.123

Domain Controller 2: 0.0.0.0

Domain Controller 3: 0.0.0.0

BaseDN: example.com

Encrypted: yes

Timeout: 60

Enabled: yes

Attribute: CiscoAvPair

Group Authorization: no

Global Catalog 1: 192.0.20.11

Global Catalog 2: 0.0.0.0

Global Catalog 3: 0.0.0.0

Server /ldap #

What to Do Next

If you want to use Active Directory groups for group authorization, see Configuring Active Directory Groups in CIMC.

Configuring Active Directory Groups in CIMC

Note When Active Directory (AD) group authorization is enabled and configured, user authentication is also done on the group level for users that are not found in the local user database or who are not individually authorized to use CIMC in the Active Directory.

Before You Begin

You must log in as a user with admin privileges to perform this task.

Active Directory (or LDAP) must be enabled and configured.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

69

Managing User Accounts

Configuring Active Directory Groups in CIMC

Procedure

 

Command or Action

Purpose

Step 1

Server# scope ldap

Enters the LDAP command mode for AD configuration.

Step 2

Server /ldap #

set group-auth

Enables or disables AD group authorization.

 

{yes| no}

 

 

Step 3

Server /ldap #

scope role-group

Selects one of the five available group profiles for

 

index

 

configuration, where index is a number between 1 and 5.

Step 4

Server /ldap/role-group#set name Specifies the name of the group in the AD database that is

 

group-name

 

authorized to access the server.

Step 5

Server /ldap/role-group#set

Specifies the AD domain the group must reside in.

 

domain domain-name

 

Step 6

Server /ldap/role-group#set role

Specifies the permission level (role) assigned to all users in

 

{admin| user| readonly}

this AD group. This can be one of the following:

 

 

 

adminTheuser can perform all actions available.

 

 

 

userTheuser can perform the following tasks:

 

 

 

View all information

 

 

 

Manage the power control options such as power

 

 

 

on, power cycle, and power off

 

 

 

Launch the KVM console and virtual media

 

 

 

Clear all logs

 

 

 

Toggle the locator LED

 

 

 

readonlyTheuser can view information but cannot

 

 

 

make any changes.

Step 7

Server /ldap/role-group#commit Commits the transaction to the system configuration.

This example shows how to configure AD group authorization:

Server# scope ldap

 

 

Server

/ldap # setgroup-authyes

 

Server

/ldap *# scoperole-group5

 

Server

/ldap/role-group*#set name Training

Server

/ldap/role-group *# set domain example.com

Server

/ldap/role-group*#set role readonly

Server

/ldap/role-group*#commit

 

ucs-c250-M2 /ldap#show role-group

Role

Group

Name

Domain

------

----------------

----------------

--------

1

(n/a)

(n/a)

admin

2

(n/a)

(n/a)

user

3

(n/a)

(n/a)

readonly

4

(n/a)

(n/a)

(n/a)

5

Training

example.com

readonly

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

70

OL-28893-01

Managing User Accounts

Viewing User Sessions

Server /ldap/role-group#

Viewing User Sessions

Procedure

 

Command or Action

Purpose

Step 1

Server# showuser-session

Displays information about current user sessions.

The command output displays the following information about current user sessions:

Name

Description

Session ID column

The unique identifier for the session.

Username column

The username for the user.

IP Address column

The IP address from which the user accessed the server.

Type column

The method by which the user accessed the server.

Action column

If your user account is assigned the admin user role, this column

 

displays Terminate if you can force the associated user session to end.

 

Otherwise it displays N/A.

 

Note

You cannot terminate your current session from this

 

 

tab.

This example displays information about current user sessions:

Server# show

user-session

Type

Killable

ID

Name

IP Address

------

---------------------------------

------------

--------

15

admin

10.20.30.138

CLI

yes

Server

/user

#

 

 

Terminating a User Session

Before You Begin

You must log in as a user with admin privileges to terminate a user session.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

71

Managing User Accounts

Terminating a User Session

Procedure

 

Command or Action

 

Purpose

Step 1

Server# showuser-session

Displays information about current user sessions. The

 

 

 

user session to be terminated must be eligible to be

 

 

 

terminated (killable) and must not be your own session.

Step 2

Server /user-session#

scope

Enters user session command mode for the numbered

 

user-session session-number

user session that you want to terminate.

Step 3

Server /user-session#

terminate

Terminates the user session.

This example shows how the admin at user session 10 terminates user session 15:

Server# show

user-session

Type

Killable

ID

Name

IP Address

------

---------------------------------

------------

--------

10

admin

10.20.41.234

CLI

yes

15

admin

10.20.30.138

CLI

yes

Server# scopeuser-session15

 

 

Server

/user-session#terminate

 

 

User session

15 terminated.

 

 

Server

/user-session#

 

 

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

72

OL-28893-01

C H A P T E R 8

Configuring Network-RelatedSettings

This chapter includes the following sections:

Server NIC Configuration, page 73

 

Configuring Common Properties, page 75

Configuring IPv4, page 76

 

Configuring the Server VLAN, page 77

Connecting to a Port Profile, page 78

 

Network Security Configuration, page

80

Network Time Protocol Configuration,

page 81

Server NIC Configuration

Server NICs

NIC Mode

The NIC mode setting determines which ports can reach the CIMC. The following network mode options are available, depending on your platform:

DedicatedThemanagement port is used to access the CIMC.

Shared LOMAnyLOM (LAN On Motherboard) port can be used to access the CIMC.

Shared LOM 10GAny10G LOM port can be used to access the CIMC. This option is only available for some adapter cards.

Cisco CardAnyport on the adapter card can be used to access the CIMC. The Cisco adapter card has to be installed in a slot with Network Communications Services Interface protocol (NCSI) support.

Shared LOM ExtendedAnyLOM port or adapter card port can be used to access the CIMC. The Cisco adapter card has to be installed in a slot with NCSI support.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

73

Configuring Network-RelatedSettings

Configuring Server NICs

NIC Redundancy

The following NIC redundancy options are available, depending on the selected NIC mode and your platform:

noneEachport associated with the configured NIC mode operates independently. The ports do not fail over if there is a problem.

active-activeIfsupported, all ports associated with the configured NIC mode operate simultaneously. This increases throughput and provides multiple paths to the CIMC.

active-standbyIfa port associated with the configured NIC mode fails, traffic will fail over to one of the other ports associated with the NIC mode.

Note If you select this option, make sure all ports associated with the configured NIC mode are connected to the same subnet to ensure that traffic is secure regardless of which port is used.

The available redundancy modes vary depending on the selected network mode and your platform. For the available modes, see the Hardware Installation Guide (HIG) for the type of server you are using. TheC-SeriesHIGs are available at the following URL:http://www.cisco.com/en/US/products/ps10493/prod_installation_ guides_list.html

Configuring Server NICs

Configure a server NIC when you want to set the NIC mode and NIC redundancy.

Before You Begin

You must log in as a user with admin privileges to configure the NIC.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope cimc

Enters the CIMC command mode.

Step 2

Server /cimc # scope network Enters the CIMC network command mode.

Step 3 Server /cimc/network #set mode {dedicated |shared_lom |shared_lom_10g |shipping |cisco_card}

Sets the NIC mode to one of the following:

DedicatedThemanagement Ethernet port is used to access the CIMC.

Shared LOMTheLAN On Motherboard (LOM) Ethernet host ports are used to access the CIMC.

Note If you select Shared LOM, make sure that all host ports belong to the same subnet.

Shared LOM 10GThe10G LOM Ethernet host ports are used to access the CIMC.

ShippingAlimited configuration for initial connection. Select another mode for normal operation.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

74

OL-28893-01

Configuring Network-RelatedSettings

Configuring Common Properties

 

Command or Action

Purpose

 

 

CiscocardTheports on the adapter card are used to access

 

 

the CIMC.

Step 4

Server /cimc/network # set

Sets the NIC redundancy mode when the NIC mode is Shared

 

redundancy {none|

LOM. The redundancy mode can be one of the following:

 

active-active|

noneTheLOM Ethernet ports operate independently and

 

active-standby}

 

do not fail over if there is a problem.

 

 

 

 

active-activeIfsupported, all LOM Ethernet ports are

 

 

utilized.

Step 5 Server /cimc/network #commit

active-standbyIfone LOM Ethernet port fails, traffic fails over to another LOM port.

Commits the transaction to the system configuration.

Note The available NIC mode and NIC redundancy mode options may vary depending on your platform. If you select a mode not supported by your server, an error message displays when you save your changes.

This example configures the CIMC network interface:

Server# scope cimc

network

Server /cimc # scope

Server /cimc/network

# set mode dedicated

Server

/cimc/network

*# commit

Server

/cimc/network

#

Configuring Common Properties

Use common properties to describe your server.

Before You Begin

You must log in as a user with admin privileges to configure common properties.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope cimc

Enters the CIMC command mode.

Step 2

Server /cimc # scope network

Enters the CIMC network command mode.

Step 3

Server /cimc/network # set hostname

Specifies the name of the host.

 

host-name

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

75

Configuring Network-RelatedSettings

Configuring IPv4

 

Command or Action

Purpose

Step 4

Server /cimc/network # commit

Commits the transaction to the system

 

 

configuration.

This example configures the common properties:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set hostname Server

Server /cimc/network *# commit

Server /cimc/network #

Configuring IPv4

Before You Begin

You must log in as a user with admin privileges to configure IPv4 network settings.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope cimc

Enters the CIMC command mode.

Step 2

Server /cimc # scope network

Enters the CIMC network command mode.

Step 3

Server /cimc/network # set dhcp-enabled

Selects whether the CIMC uses DHCP.

 

{yes| no}

Note

If DHCP is enabled, we recommend that

 

 

 

the DHCP server be configured to reserve

 

 

 

a single IP address for the CIMC. If the

 

 

 

CIMC is reachable through multiple ports

 

 

 

on the server, the single IP address must

 

 

 

be reserved for the full range of MAC

 

 

 

addresses of those ports.

Step 4

Server /cimc/network #

set v4-addr

Specifies the IP address for the CIMC.

 

ipv4-address

 

 

Step 5

Server /cimc/network #

set v4-netmask

Specifies the subnet mask for the IP address.

 

ipv4-netmask

 

 

Step 6

Server /cimc/network #

set v4-gateway

Specifies the gateway for the IP address.

 

gateway-ipv4-address

 

 

Step 7

Server /cimc/network # set dns-use-dhcp

Selects whether the CIMC retrieves the DNS server

 

{yes| no}

 

addresses from DHCP.

Step 8

Server /cimc/network #

set

Specifies the IP address of the primary DNS server.

preferred-dns-serverdns1-ipv4-address

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

76

OL-28893-01

Configuring Network-RelatedSettings

Configuring the Server VLAN

 

Command or Action

 

Purpose

Step 9

Server /cimc/network #

set

Specifies the IP address of the secondary DNS

 

alternate-dns-serverdns2-ipv4-address

server.

Step 10

Server /cimc/network #

commit

Commits the transaction to the system

 

 

 

configuration.

Step 11

Server /cimc/network #

show [detail]

(Optional) Displays the IPv4 network settings.

This example configures and displays the IPv4 network settings:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set dhcp-enabled yes

Server /cimc/network *# set v4-addr 10.20.30.11

Server /cimc/network *# setv4-netmask255.255.248.0

Server /cimc/network *# setv4-gateway10.20.30.1

Server /cimc/network *# setdns-use-dhcp-enabledno

Server /cimc/network *# setpreferred-dns-server192.168.30.31

Server /cimc/network *# setalternate-dns-server192.168.30.32

Server /cimc/network *# commit

Server /cimc/network # show detail

Network Setting:

IPv4 Address: 10.20.30.11

IPv4 Netmask: 255.255.248.0

IPv4 Gateway: 10.20.30.1

DHCP Enabled: yes

Obtain DNS Server by DHCP: no

Preferred DNS: 192.168.30.31

Alternate DNS: 192.168.30.32

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Hostname: Server

MAC Address: 01:23:45:67:89:AB

NIC Mode: dedicated

NIC Redundancy: none

Server /cimc/network #

Configuring the Server VLAN

Before You Begin

You must be logged in as admin to configure the server VLAN.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope cimc

Enters the CIMC command mode.

Step 2

Server /cimc # scope network

Enters the CIMC network command mode.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

77

Configuring Network-RelatedSettings

Connecting to a Port Profile

 

Command or Action

 

Purpose

Step 3

Server /cimc/network #

set vlan-enabled

Selects whether the CIMC is connected to a

 

{yes| no}

 

VLAN.

Step 4

Server /cimc/network # set vlan-id id

Specifies the VLAN number.

Step 5

Server /cimc/network #

set vlan-priority

Specifies the priority of this system on the

 

priority

 

VLAN.

Step 6

Server /cimc/network #

commit

Commits the transaction to the system

 

 

 

configuration.

Step 7

Server /cimc/network #

show [detail]

(Optional) Displays the network settings.

This example configures the server VLAN:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set vlan-enabled yes

Server /cimc/network *# set vlan-id 10

Server /cimc/network *# set vlan-priority 32

Server /cimc/network *# commit

Server /cimc/network # show detail

Network Setting:

IPv4 Address: 10.20.30.11

IPv4 Netmask: 255.255.248.0

IPv4 Gateway: 10.20.30.1

DHCP Enabled: yes

Obtain DNS Server by DHCP: no

Preferred DNS: 192.168.30.31

Alternate DNS: 192.168.30.32

VLAN Enabled: yes

VLAN ID: 10

VLAN Priority: 32

Hostname: Server

MAC Address: 01:23:45:67:89:AB

NIC Mode: dedicated

NIC Redundancy: none

Server /cimc/network #

Connecting to a Port Profile

Note You can configure a port profile or a VLAN, but you cannot use both. If you want to use a port profile, make sure theset vlan-enabled command is set to no.

Before You Begin

You must be logged in as admin to connect to a port profile.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

78

OL-28893-01

Configuring Network-RelatedSettings

Connecting to a Port Profile

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope cimc

Enters the CIMC command mode.

Step 2

Server /cimc # scope network

Enters the CIMC network command mode.

Step 3

Server /cimc/network # set

Specifies the port profile CIMC should use to configure the

 

port-profile port_profile_name

management interface, the virtual Ethernet, and the VIF on

 

 

supported adapter cards such as the Cisco UCS VIC1225

 

 

Virtual Interface Card.

 

 

Enter up to 80 alphanumeric characters. You cannot use

 

 

spaces or other special characters except for - (hyphen) and

 

 

_ (underscore). In addition, the port profile name cannot begin

 

 

with a hyphen.

 

 

Note

The port profile must be defined on the switch to

 

 

 

which this server is connected.

Step 4

Server /cimc/network # commit

Commits the transaction to the system configuration.

Step 5

Server /cimc/network # show

(Optional)

 

[detail]

Displays the network settings.

This example connects to port profile abcde12345:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # setport-profileabcde12345

Server /cimc/network *# commit

Server /cimc/network # show detail

Network Setting:

IPv4 Address: 10.193.66.174

IPv4 Netmask: 255.255.248.0

IPv4 Gateway: 10.193.64.1

DHCP Enabled: no

Obtain DNS Server by DHCP: no

Preferred DNS: 0.0.0.0

Alternate DNS: 0.0.0.0

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Port Profile: abcde12345

Hostname: Server

MAC Address: 50:3D:E5:9D:63:3C

NIC Mode: dedicated

NIC Redundancy: none

Server /cimc/network #

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

79

Configuring Network-RelatedSettings

Network Security Configuration

Network Security Configuration

Network Security

The CIMC uses IP blocking as network security. IP blocking prevents the connection between a server or website and certain IP addresses or ranges of addresses. IP blocking effectively bans undesired connections from those computers to a website, mail server, or other Internet servers.

IP banning is commonly used to protect against denial of service (DoS) attacks. CIMC bans IP addresses by setting up an IP blocking fail count.

Configuring Network Security

Configure network security if you want to set up an IP blocking fail count.

Before You Begin

You must log in as a user with admin privileges to configure network security.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope cimc

Enters the CIMC command mode.

Step 2

Server /cimc # scope network

Enters the CIMC network command mode.

Step 3

Server /cimc/network # scope

Enters the IP blocking command mode.

 

ipblocking

 

Step 4

Server /cimc/network/ipblocking #

Enables or disables IP blocking.

 

set enabled {yes| no}

 

Step 5

Server /cimc/network/ipblocking #

Sets the number of times a user can attempt to log in

 

set fail-countfail-count

unsuccessfully before the system locks that user out for

 

 

a specified length of time.

 

 

The number of unsuccessful login attempts must occur

 

 

within the time frame specified in the IP Blocking Fail

 

 

Window field.

 

 

Enter an integer between 3 and 10.

Step 6

Server /cimc/network/ipblocking #

Sets the length of time, in seconds, in which the

 

set fail-windowfail-seconds

unsuccessful login attempts must occur in order for the

 

 

user to be locked out.

 

 

Enter an integer between 60 and 120.

Step 7

Server /cimc/network/ipblocking #

Sets the number of seconds the user remains locked out

 

set penalty-timepenalty-seconds

if they exceed the maximum number of login attempts

 

 

within the specified time window.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

80

OL-28893-01

Configuring Network-RelatedSettings

Network Time Protocol Configuration

Command or Action

Purpose

Enter an integer between 300 and 900.

Step 8

Server /cimc/network/ipblocking #

Commits the transaction to the system configuration.

 

commit

 

This example configures IP blocking:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # scope ipblocking

Server /cimc/network/ipblocking # set enabled yes

Server /cimc/network/ipblocking *# set fail-count 5

Server /cimc/network/ipblocking *# set fail-window 90

Server /cimc/network/ipblocking *# set penalty-time 600

Server /cimc/network/ipblocking *# commit

Server /cimc/network/ipblocking #

Network Time Protocol Configuration

Configuring Network Time Protocol Settings

By default, when CIMC is reset, it synchronizes the time with the host. With the introduction of the NTP service, you can configure CIMC to synchronize the time with an NTP server. The NTP server does not run in CIMC by default. You must enable and configure the NTP service by specifying the IP/DNS address of at least one server or a maximum of four servers that function as NTP servers or time source servers. When you enable the NTP service, CIMC synchronizes the time with the configured NTP server. The NTP service can be modified only through CIMC.

Note To enable the NTP service, it is preferable to specify the IP address of a server rather than the DNS address.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server # scope cimc

Enters CIMC command mode.

Step 2

Server /cimc # scope network

Enters network command mode.

Step 3

Server /cimc/network # scope ntp

Enters NTP service command mode.

Step 4

Server /cimc/network/ntp # set enabled

Enables the NTP service on the server.

 

yes

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

81

Configuring Network-RelatedSettings

Configuring Network Time Protocol Settings

 

Command or Action

Purpose

Step 5

Server /cimc/network/ntp* # commit

Commits the transaction.

Step 6

Server /cimc/network/ntp # set server-1

Specifies the IP/DNS address of one of the four

 

10.120.33.44

servers that act as an NTP server or the time source

 

 

server.

Step 7

Server /cimc/network/ntp # set server-2

Specifies the IP/DNS address of one of the four

 

10.120.34.45

servers that act as an NTP server or the time source

 

 

server.

Step 8

Server /cimc/network/ntp # set server-3

Specifies the IP/DNS address of one of the four

 

10.120.35.46

servers that act as an NTP server or the time source

 

 

server.

Step 9

Server /cimc/network/ntp # set server-4

Specifies the IP/DNS address of one of the four

 

10.120.36.48

servers that act as an NTP server or the time source

 

 

server.

Step 10

Server /cimc/network/ntp # commit

Commits the transaction.

This example shows how to configure the NTP service:

Server # scope cimc

Server /cimc # scope network Server /cimc/network #scope ntp

Server /cimc/network/ntp # set enabled yes Warning: IPMI Set SEL Time Command will be disabled if NTP is enabled.

Do you

wish to continue? [y|N]

y

/cimc/network/ntp* # commit

Server

Server

/cimc/network/ntp # setserver-110.120.33.44

Server

/cimc/network/ntp* # setserver-210.120.34.45

Server

/cimc/network/ntp* # setserver-310.120.35.46

Server

/cimc/network/ntp* # setserver-410.120.36.48

Server

/cimc/network/ntp* # commit

Server

/cimc/network/ntp #

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

82

OL-28893-01

C H A P T E R 9

Managing Network Adapters

This chapter includes the following sections:

Overview of the Cisco UCS C-SeriesNetwork Adapters, page 83

Viewing Network Adapter Properties, page 85

Configuring Network Adapter Properties, page 85

Managing vHBAs, page 86

Managing vNICs, page 99

Managing VM FEX, page 109

Managing Storage Adapters, page 115

Backing Up and Restoring the Adapter Configuration, page 127

Managing Adapter Firmware, page 130

Resetting the Adapter, page 131

Overview of the Cisco UCS C-SeriesNetwork Adapters

Note The procedures in this chapter are available only when a Cisco UCSC-Seriesnetwork adapter is installed in the chassis.

A Cisco UCS C-Seriesnetwork adapter can be installed to provide options for I/O consolidation and virtualization support. The following adapters are available:

Cisco UCS P81E Virtual Interface Card

Cisco UCS VIC1225 Virtual Interface Card

The interactive UCS Hardware and Software Interoperability Utilitylets you view the supported components and configurations for a selected server model and software release. The utility is available at the following URL: http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

83

Managing Network Adapters

Overview of the Cisco UCS C-SeriesNetwork Adapters

Cisco UCS P81E Virtual Interface Card

The Cisco UCS P81E Virtual Interface Card is optimized for virtualized environments, for organizations that seek increased mobility in their physical environments, and for data centers that want reduced costs through NIC, HBA, cabling, and switch reduction and reduced management overhead. This Fibre Channel over Ethernet (FCoE) PCIe card offers the following benefits:

Allows up to 16 virtual Fibre Channel and 16 virtual Ethernet adapters to be provisioned in virtualized or nonvirtualized environments using just-in-timeprovisioning, providing tremendous system flexibility and allowing consolidation of multiple physical adapters.

Delivers uncompromising virtualization support, including hardware-basedimplementation of CiscoVN-Linktechnology andpass-throughswitching.

Improves system security and manageability by providing visibility and portability of network polices and security all the way to the virtual machine.

The virtual interface card makes Cisco VN-Linkconnections to the parent fabric interconnects, which allows virtual links to connect virtual NICs in virtual machines to virtual interfaces in the interconnect. In a Cisco Unified Computing System environment, virtual links then can be managed, network profiles applied, and interfaces dynamically reprovisioned as virtual machines move between servers in the system.

Cisco UCS VIC1225 Virtual Interface Card

The Cisco UCS VIC1225 Virtual Interface Card is a high-performance,converged network adapter that provides acceleration for the various new operational modes introduced by server virtualization. It brings superior flexibility, performance, and bandwidth to the new generation of Cisco UCSC-SeriesRack-MountServers.

The Cisco UCS VIC 1225 implements the Cisco Virtual Machine Fabric Extender (VM-FEX),which unifies virtual and physical networking into a single infrastructure. It providesvirtual-machinevisibility from the physical network and a consistent network operations model for physical and virtual servers. In virtualized environments, this highly configurable andself-virtualizedadapter provides integrated, modular LAN interfaces on Cisco UCSC-SeriesRack-MountServers. Additional features and capabilities include:

Supports up to 256 PCIe virtual devices, either virtual network interface cards (vNICs) or virtual host bus adapters (vHBAs), with high I/O operations per second (IOPS), support for lossless Ethernet, and 20 Gbps to servers.

PCIe Gen2 x16 helps assure optimal bandwidth to the host for network-intensiveapplications with a redundant path to the fabric interconnect.

Half-heightdesign reservesfull-heightslots in servers for Cisco certifiedthird-partyadapters.

Centrally managed by Cisco UCS Manager with support for Microsoft Windows, Red Hat Enterprise Linux, SUSE Linux, VMware vSphere, and Citrix XenServer.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

84

OL-28893-01

Managing Network Adapters

Viewing Network Adapter Properties

Viewing Network Adapter Properties

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # show adapter

Displays adapter properties. To display the properties

 

[index] [detail]

of a single adapter, specify the PCI slot number as the

 

 

index argument.

This example displays the properties of adapter 2:

Server# scope chassis

 

 

 

Server

/chassis # show adapter

Product ID

Vendor

PCI Slot Product Name

Serial Number

----------------------

--------------

----------------------------------

1

UCS VIC 1225

FCH1613796C

UCSC-PCIE-C...Cisco Systems Inc

Server

/chassis # show adapter 2 detail

 

 

PCI Slot 2:

 

 

 

Product Name: UCS VIC 1225

 

 

Serial Number: FCH1613796C

 

 

Product ID: UCSC-PCIE-CSC-02

 

 

Adapter Hardware Revision: 4

 

 

Current FW Version: 2.1(0.291)

 

 

NIV: Disabled

 

 

 

FIP: Enabled

 

 

 

Configuration Pending: no

 

 

CIMC Management Enabled : no

 

 

VID: V00

 

 

 

Vendor: Cisco Systems Inc

 

 

Description:

 

 

 

Bootloader Version: 2.1(0.291)

 

 

FW

Image 1 Version: 2.1(0.291)

 

 

FW

Image 1 State: RUNNING ACTIVATED

 

 

FW

Image 2 Version: 1.6(0.547)

 

 

FW

Image 2 State: BACKUP INACTIVATED

 

FW

Update Status: Idle

 

 

FW

Update Error: No error

 

 

FW

Update Stage: No operation (0%)

 

 

FW

Update Overall Progress: 0%

 

 

Server

/chassis #

 

 

 

Configuring Network Adapter Properties

Before You Begin

You must log in with admin privileges to perform this task.

A supported Virtual Interface Card (VIC) must be installed in the chassis and the server must be powered on.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

85

Managing Network Adapters

Managing vHBAs

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # show adapter

(Optional) Displays the available adapter devices.

Step 3

Server /chassis # scope adapter

Enters the command mode for the adapter card at the PCI

 

index

slot number specified by index.

 

 

Note

The server must be powered on before you can view

 

 

 

or change adapter settings.

Step 4

Server /chassis/adapter # set

Enables or disables FCoE Initialization Protocol (FIP) on

 

fip-mode{disable| enable}

the adapter card. FIP is enabled by default.

 

 

Note

We recommend that you disable this option only

 

 

 

when explicitly directed to do so by a technical

 

 

 

support representative.

Step 5

Server /chassis/adapter # set

Enables or disables Network Interface Virtualization (NIV)

 

niv-mode{disable| enable}

on the adapter card. NIV is disabled by default.

 

 

If NIV mode is enabled, vNICs:

 

 

Can be assigned to a specific channel

 

 

Can be associated with a port profile

 

 

Can fail over to another vNIC if there are

 

 

 

communication problems

Step 6

Server /chassis/adapter #

If NIV mode is enabled, port-count specifies the number of

 

configure-vmfexport-count

VM FEX interfaces you want CIMC to create, from 0 to 112.

Step 7

Server /chassis/adapter # commit

Commits the transaction to the system configuration.

This example configures the properties of adapter 1:

Server# scope chassis

adapter 1

Server /chassis # scope

Server /chassis/adapter

# setfip-modeenable

Server

/chassis/adapter

*# commit

Server

/chassis/adapter

#

Managing vHBAs

Guidelines for Managing vHBAs

When managing vHBAs, consider the following guidelines and restrictions:

The Cisco UCS P81E Virtual Interface Card and Cisco UCS VIC1225 Virtual Interface Card provide two vHBAs (fc0 and fc1). You can create up to 16 additional vHBAs on these adapter cards.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

86

OL-28893-01

Managing Network Adapters

Viewing vHBA Properties

Note If Network Interface Virtualization (NIV) mode is enabled for the adapter, you must assign a channel number to a vHBA when you create it.

When using the Cisco UCS P81E Virtual Interface Card or Cisco UCS VIC1225 Virtual Interface Card in an FCoE application, you must associate the vHBA with the FCoE VLAN. Follow the instructions in to assign the VLAN.

After making configuration changes, you must reboot the host for settings to take effect.

Viewing vHBA Properties

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter index

Enters the command mode for the adapter card at the

 

 

PCI slot number specified by index.

 

 

Note

The server must be powered on before you

 

 

 

can view or change adapter settings.

Step 3

Server /chassis/adapter # show

Displays properties of a single vHBA, if specified, or

 

host-fc-if[fc0| fc1| name] [detail]

all vHBAs.

This example displays all vHBAs on adapter card 1 and the detailed properties of fc0:

Server# scope chassis

 

 

Server /chassis # scope adapter 1

 

 

Server /chassis/adapter # show host-fc-if

 

Name

World Wide Port Name

FC SAN Boot Uplink Port

--------

------------------------

----------------------

fc0

20:00:00:22:BD:D6:5C:35

Disabled

0

fc1

20:00:00:22:BD:D6:5C:36

Disabled

1

Server /chassis/adapter # show host-fc-if fc0 detail

Name fc0:

World Wide Node Name: 10:00:00:22:BD:D6:5C:35

World Wide Port Name: 20:00:00:22:BD:D6:5C:35

FC SAN Boot: Disabled

Persistent LUN Binding: Disabled

Uplink Port: 0

MAC Address: 00:22:BD:D6:5C:35

CoS: 3

VLAN: NONE

Rate Limiting: OFF

PCIe Device Order: ANY

EDTOV: 2000

RATOV: 10000

Maximum Data Field Size: 2112

Channel Number: 3

Port Profile:

Server /chassis/adapter #

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

87

Managing Network Adapters

Modifying vHBA Properties

Modifying vHBA Properties

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # show adapter

(Optional) Displays the available adapter devices.

Step 3

Server /chassis # scope adapter index

Enters the command mode for the adapter card at the

 

 

PCI slot number specified by index.

 

 

Note

The server must be powered on before you

 

 

 

can view or change adapter settings.

Step 4

Server /chassis/adapter # scope host-fc-if

Enters the host Fibre Channel interface command

 

{fc0| fc1| name}

mode for the specified vHBA.

Step 5

Server /chassis/adapter/host-fc-if#set

Specifies a unique World Wide Node Name (WWNN)

 

wwnn wwnn

for the adapter in the form hh:hh:hh:hh:hh:hh:hh:hh.

 

 

Unless specified by this command, the WWNN is

 

 

generated automatically by the system.

Step 6

Server /chassis/adapter/host-fc-if#set

Specifies a unique World Wide Port Name (WWPN)

 

wwpn wwpn

for the adapter in the form hh:hh:hh:hh:hh:hh:hh:hh.

 

 

Unless specified by this command, the WWPN is

 

 

generated automatically by the system.

Step 7

Server /chassis/adapter/host-fc-if#set

Enables or disables FC SAN boot. The default is

 

boot {disable| enable}

disable.

 

Step 8

Server /chassis/adapter/host-fc-if#set

Enables or disables persistent LUN binding. The

 

persistent-lun-binding{disable|

default is disable.

 

enable}

 

 

Step 9

Server /chassis/adapter/host-fc-if#set

Specifies a MAC address for the vHBA.

 

mac-addrmac-addr

 

 

Step 10

Server /chassis/adapter/host-fc-if#set

Specifies the default VLAN for this vHBA. Valid

 

vlan {none| vlan-id}

VLAN numbers are 1 to 4094; the default is none.

Step 11

Server /chassis/adapter/host-fc-if#set

Specifies the class of service (CoS) value to be marked

 

cos cos-value

on received packets unless the vHBA is configured

 

 

to trust host CoS. Valid CoS values are 0 to 6; the

 

 

default is 0. Higher values indicate more important

 

 

traffic.

 

This setting is not functional in NIV mode.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

88

OL-28893-01

Managing Network Adapters

Modifying vHBA Properties

 

Command or Action

Purpose

Step 12

Server /chassis/adapter/host-fc-if#set

Specifies a maximum data rate for the vHBA. The

 

rate-limit{off| rate}

range is 1 to 10000 Mbps; the default is off.

 

 

This setting is not functional in NIV mode.

Step 13

Server /chassis/adapter/host-fc-if#set

Specifies the relative order of this device for PCIe bus

 

order {any| 0-99}

device number assignment; the default is any.

Step 14

Server /chassis/adapter/host-fc-if#set

Specifies the error detect timeout value (EDTOV),

 

error-detect-timeoutmsec

the number of milliseconds to wait before the system

 

 

assumes that an error has occurred. The range is 1000

 

 

to 100000; the default is 2000 milliseconds.

Step 15

Server /chassis/adapter/host-fc-if#set

Specifies the resource allocation timeout value

 

resource-allocation-timeoutmsec

(RATOV), the number of milliseconds to wait before

 

 

the system assumes that a resource cannot be properly

 

 

allocated. The range is 5000 to 100000; the default is

 

 

10000 milliseconds.

Step 16

Server /chassis/adapter/host-fc-if#set

Specifies the maximum size of the Fibre Channel

 

max-field-sizesize

frame payload (in bytes) that the vHBA supports. The

 

 

range is 1 to 2112; the default is 2112 bytes.

Step 17

Server /chassis/adapter/host-fc-if#scope

Enters the Fibre Channel error recovery command

 

error-recovery

mode.

Step 18

Server

Enables or disables FCP Error Recovery. The default

 

/chassis/adapter/host-fc-if/error-recovery

is disable.

 

# setfcp-error-recovery{disable|

 

 

enable}

 

Step 19

Server

Specifies the link down timeout value, the number of

 

/chassis/adapter/host-fc-if/error-recovery

milliseconds the uplink port should be offline before

 

# setlink-down-timeoutmsec

it informs the system that the uplink port is down and

 

 

fabric connectivity has been lost. The range is 0 to

 

 

240000; the default is 30000 milliseconds.

Step 20

Server

Specifies the port down I/O retries value, the number

 

/chassis/adapter/host-fc-if/error-recovery

of times an I/O request to a port is returned because

 

# setport-down-io-retry-countcount

the port is busy before the system decides the port is

 

 

unavailable. The range is 0 to 255; the default is 8

 

 

retries.

Step 21

Server

Specifies the port down timeout value, the number of

 

/chassis/adapter/host-fc-if/error-recovery

milliseconds a remote Fibre Channel port should be

 

# setport-down-timeoutmsec

offline before informing the SCSI upper layer that the

 

 

port is unavailable. The range is 0 to 240000; the

 

 

default is 10000 milliseconds.

Step 22

Server

Exits to the host Fibre Channel interface command

 

/chassis/adapter/host-fc-if/error-recovery

mode.

 

# exit

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

89

Managing Network Adapters

Modifying vHBA Properties

Command or Action

Purpose

Step 23 Server /chassis/adapter/host-fc-if#scope Enters the interrupt command mode.interrupt

Step 24

Server

 

/chassis/adapter/host-fc-if/interrupt#set

 

interrupt-mode{intx| msi| msix}

Step 25

Server

 

/chassis/adapter/host-fc-if/interrupt#exit

Step 26

Server /chassis/adapter/host-fc-if#scope

 

port

Specifies the Fibre Channel interrupt mode. The modes are as follows:

intx Line-basedinterrupt (INTx)

msi Message-SignaledInterrupt (MSI)

msix MessageSignaled Interrupts with the optional extension (MSIx). This is the recommended and default option.

Exits to the host Fibre Channel interface command mode.

Enters the Fibre Channel port command mode.

Step 27

Server /chassis/adapter/host-fc-if/port#

Specifies the I/O throttle count, the number of I/O

 

set outstanding-io-countcount

operations that can be pending in the vHBA at one

 

 

time. The range is 1 to 1024; the default is 512

 

 

operations.

Step 28

Server /chassis/adapter/host-fc-if/port#

Specifies the maximum logical unit numbers (LUNs)

 

set max-target-lunscount

per target, the maximum number of LUNs that the

 

 

driver will discover. This is usually an operating

 

 

system platform limitation. The range is 1 to 1024;

 

 

the default is 256 LUNs.

Step 29

Server /chassis/adapter/host-fc-if/port#

Exits to the host Fibre Channel interface command

 

exit

mode.

Step 30

Server /chassis/adapter/host-fc-if#scope

Enters the Fibre Channel fabric login command mode.

 

port-f-logi

 

Step 31

Server

 

/chassis/adapter/host-fc-if/port-f-logi#

 

set flogi-retries{infinite| count}

Specifies the fabric login (FLOGI) retries value, the number of times that the system tries to log in to the fabric after the first failure. Enter a number between 0 and 4294967295 or enter infinite ; the default is infinite retries.

Step 32

Server

 

/chassis/adapter/host-fc-if/port-f-logi#

 

set flogi-timeoutmsec

Step 33

Server

 

/chassis/adapter/host-fc-if/port-f-logi#

 

exit

Specifies the fabric login (FLOGI) timeout value, the number of milliseconds that the system waits before it tries to log in again. The range is 1 to 255000; the default is 2000 milliseconds.

Exits to the host Fibre Channel interface command mode.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

90

OL-28893-01

Managing Network Adapters

Modifying vHBA Properties

 

Command or Action

Purpose

Step 34

Server /chassis/adapter/host-fc-if#scope

Enters the Fibre Channel port login command mode.

 

port-p-logi

 

Step 35

Server

 

/chassis/adapter/host-fc-if/port-p-logi#

 

set plogi-retriescount

Specifies the port login (PLOGI) retries value, the number of times that the system tries to log in to the fabric after the first failure. The range is 0 and 255; the default is 8 retries.

Step 36

Server

 

/chassis/adapter/host-fc-if/port-p-logi#

 

set plogi-timeoutmsec

Specifies the port login (PLOGI) timeout value, the number of milliseconds that the system waits before it tries to log in again. The range is 1 to 255000; the default is 2000 milliseconds.

Step 37

Server

Exits to the host Fibre Channel interface command

 

/chassis/adapter/host-fc-if/port-p-logi#

mode.

 

exit

 

Step 38

Server /chassis/adapter/host-fc-if#scope

Enters the SCSI I/O command mode.

 

scsi-io

 

Step 39

Server /chassis/adapter/host-fc-if/scsi-io

The number of command descriptor block (CDB)

 

# setcdb-wq-countcount

transmit queue resources to allocate. The range is 1

 

 

to 8; the default is 1.

Step 40

Server /chassis/adapter/host-fc-if/scsi-io

The number of descriptors in the command descriptor

 

# setcdb-wq-ring-sizesize

block (CDB) transmit queue. The range is 64 to 512;

 

 

the default is 512.

Step 41

Server /chassis/adapter/host-fc-if/scsi-io

 

# exit

Step 42

Server /chassis/adapter/host-fc-if#scope

 

trans-queue

Step 43

Server

 

/chassis/adapter/host-fc-if/trans-queue#

 

set fc-wq-ring-sizesize

Exits to the host Fibre Channel interface command mode.

Enters the Fibre Channel transmit queue command mode.

The number of descriptors in the Fibre Channel transmit queue. The range is 64 to 128; the default is 64.

Step 44

Server

Exits to the host Fibre Channel interface command

 

/chassis/adapter/host-fc-if/trans-queue#

mode.

 

exit

 

Step 45

Server /chassis/adapter/host-fc-if#scope

 

recv-queue

Step 46

Server

 

/chassis/adapter/host-fc-if/recv-queue#

 

set fc-rq-ring-sizesize

Enters the Fibre Channel receive queue command mode.

The number of descriptors in the Fibre Channel receive queue. The range is 64 to 128; the default is 64.

Step 47

Server

Exits to the host Fibre Channel interface command

 

/chassis/adapter/host-fc-if/recv-queue#

mode.

 

exit

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

91

Managing Network Adapters

Creating a vHBA

Command or Action

Step 48 Server /chassis/adapter/host-fc-if#commit

Purpose

Commits the transaction to the system configuration.

Note The changes will take effect upon the next server reboot.

This example configures the properties of a vHBA:

Server# scope chassis

 

 

 

Server /chassis # show adapter

Product ID

Vendor

PCI Slot

Product Name

Serial Number

--------

--------------

--------------

--------------

--------------------

1

UCS VIC P81E

QCI1417A0QK

N2XX-ACPCI01

Cisco Systems Inc

Server /chassis # scope

adapter 1

 

 

Server /chassis/adapter

# scopehost-fc-iffc1

 

Server /chassis/adapter/host-fc-if#set boot enable

Server /chassis/adapter/host-fc-if*#scope scsi-io

Server /chassis/adapter/host-fc-if/scsi-io*#set cdb-wq-count 2

Server /chassis/adapter/host-fc-if/scsi-io*#exit

Server /chassis/adapter/host-fc-if*#commit

Server /chassis/adapter/host-fc-if#

What to Do Next

Reboot the server to apply the changes.

Creating a vHBA

The adapter provides two permanent vHBAs. If NIV mode is enabled, you can create up to 16 additional vHBAs.

Before You Begin

You must log in with user or admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter

Enters the command mode for the adapter card at the PCI

 

index

slot number specified by index.

 

 

Note

The server must be powered on before you can

 

 

 

view or change adapter settings.

Step 3

Server /chassis/adapter # create

Creates a vHBA and enters the host Fibre Channel

 

host-fc-ifname

interface command mode. The name argument can be up

 

 

to 32 ASCII characters.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

92

OL-28893-01

Managing Network Adapters

Deleting a vHBA

 

Command or Action

Purpose

 

Step 4

Server /chassis/adapter/host-fc-if#

(Optional)

 

set channel-numbernumber

If NIV mode is enabled for the adapter, you must assign

 

 

a channel number to this vHBA. The range is 1 to 1000.

Step 5

Server /chassis/adapter/host-fc-if#

Commits the transaction to the system configuration.

 

commit

Note

The changes will take effect upon the next server

 

 

reboot.

This example creates a vHBA on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # create host-fc-if Vhba5

Server /chassis/adapter/host-fc-if*#commit

New host-fc-ifsettings will take effect upon the next server reset

Server /chassis/adapter/host-fc-if#

What to Do Next

Reboot the server to create the vHBA.

If configuration changes are required, configure the new vHBA as described in Modifying vHBA Properties, on page 88.

Deleting a vHBA

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter

Enters the command mode for the adapter card at the PCI

 

index

slot number specified by index.

 

 

Note

The server must be powered on before you can

 

 

 

view or change adapter settings.

Step 3

Server /chassis/adapter # delete

 

host-fc-ifname

Step 4

Server /chassis/adapter # commit

Deletes the specified vHBA.

Note You cannot delete either of the two default vHBAs, fc0 or fc1.

Commits the transaction to the system configuration.

Note The changes will take effect upon the next server reboot.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

93

Managing Network Adapters

vHBA Boot Table

This example deletes a vHBA on adapter 1:

Server# scope chassis

adapter 1

Server /chassis # scope

Server /chassis/adapter

# deletehost-fc-ifVhba5

Server

/chassis/adapter

*# commit

Server

/chassis/adapter

#

vHBA Boot Table

In the vHBA boot table, you can specify up to four LUNs from which the server can boot.

Viewing the Boot Table

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter index

Enters the command mode for the adapter card at the

 

 

PCI slot number specified by index.

 

 

Note

The server must be powered on before you

 

 

 

can view or change adapter settings.

Step 3

Server /chassis/adapter # scope

Enters the host Fibre Channel interface command mode

 

host-fc-if{fc0| fc1| name}

for the specified vHBA.

Step 4

Server /chassis/adapter/host-fc-if#

Displays the boot table of the Fibre Channel interface.

 

show boot

 

 

This example displays the boot table for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if#show boot

Boot Table Entry

Boot Target WWPN

Boot LUN ID

-----------------

--------------------------

------------

0

20:00:00:11:22:33:44:55

3

1

20:00:00:11:22:33:44:56

5

Server /chassis/adapter/host-fc-if#

Creating a Boot Table Entry

You can create up to four boot table entries.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

94

OL-28893-01

Managing Network Adapters

Deleting a Boot Table Entry

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter

Enters the command mode for the adapter card at the PCI

 

index

slot number specified by index.

 

 

Note

The server must be powered on before you can

 

 

 

view or change adapter settings.

Step 3

Server /chassis/adapter # scope

 

host-fc-if{fc0| fc1| name}

Step 4

Server /chassis/adapter/host-fc-if#

 

create-boot-entrywwpn lun-id

Step 5

Server /chassis/adapter/host-fc-if#

 

commit

Enters the host Fibre Channel interface command mode for the specified vHBA.

Creates a boot table entry.

wwpn The World Wide Port Name (WWPN) for the boot target in the form hh:hh:hh:hh:hh:hh:hh:hh.

lun-id TheLUN ID of the boot LUN. The range is 0 to 255.

Commits the transaction to the system configuration.

Note The changes will take effect upon the next server reboot.

This example creates a boot table entry for vHBA fc1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if # create-boot-entry20:00:00:11:22:33:44:55 3

Server /chassis/adapter/host-fc-if*#commit

New boot table entry will take effect upon the next server reset

Server /chassis/adapter/host-fc-if#

Deleting a Boot Table Entry

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter

Enters the command mode for the adapter card at the PCI

 

index

slot number specified by index.

 

 

Note

The server must be powered on before you can

 

 

 

view or change adapter settings.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

95

Managing Network Adapters

vHBA Persistent Binding

 

Command or Action

Purpose

 

Step 3

Server /chassis/adapter # scope

Enters the host Fibre Channel interface command mode

 

host-fc-if{fc0| fc1| name}

for the specified vHBA.

Step 4

Server /chassis/adapter/host-fc-if#

Displays the boot table. From the Boot Table Entry field,

 

show boot

locate the number of the entry to be deleted.

Step 5

Server /chassis/adapter/host-fc-if#

Deletes the boot table entry at the specified position in

 

delete boot entry

the table. The range of entry is 0 to 3. The change will

 

 

take effect upon the next server reset.

Step 6

Server /chassis/adapter/host-fc-if#

Commits the transaction to the system configuration.

 

commit

Note

The changes will take effect upon the next server

 

 

reboot.

This example deletes boot table entry number 1 for the vHBA fc1:

Server# scope chassis

 

 

Server /chassis #

scope adapter 1

 

 

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if

# show boot

Boot Table Entry

Boot Target WWPN

 

Boot LUN ID

-----------------

--------------------------

------------

0

20:00:00:11:22:33:44:55

3

1

20:00:00:11:22:33:44:56

5

Server /chassis/adapter/host-fc-if

# delete boot 1

Server /chassis/adapter/host-fc-if

*# commit

 

New host-fc-ifsettings will take effect upon the next server reset

Server /chassis/adapter/host-fc-if#show boot

Boot Table Entry

Boot Target WWPN

Boot LUN ID

-----------------

--------------------------

------------

0

20:00:00:11:22:33:44:55

3

Server /chassis/adapter/host-fc-if#

What to Do Next

Reboot the server to apply the changes.

vHBA Persistent Binding

Persistent binding ensures that the system-assignedmapping of Fibre Channel targets is maintained after a reboot.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

96

OL-28893-01

Managing Network Adapters

Enabling Persistent Binding

Enabling Persistent Binding

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter index

Enters the command mode for the adapter card at

 

 

the PCI slot number specified by index.

 

 

Note

The server must be powered on before you

 

 

 

can view or change adapter settings.

Step 3

Server /chassis/adapter # scope host-fc-if

Enters the host Fibre Channel interface command

 

{fc0| fc1| name}

mode for the specified vHBA.

Step 4

Server /chassis/adapter/host-fc-if#scope

Enters the persistent binding command mode for

 

perbi

the vHBA.

Step 5

Server /chassis/adapter/host-fc-if/perbi#

Enables persistent binding for the vHBA.

 

set persistent-lun-bindingenable

 

 

Step 6

Server /chassis/adapter/host-fc-if/perbi#

Commits the transaction to the system

 

commit

configuration.

This example enables persistent binding for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 4

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if#scope perbi

Server /chassis/adapter/host-fc-if/perbi#set persistent-lun-binding enable

Server /chassis/adapter/host-fc-if/perbi*#commit

Server /chassis/adapter/host-fc-if/perbi#

Disabling Persistent Binding

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter index

Enters the command mode for the adapter card at

 

 

the PCI slot number specified by index.

 

 

Note

The server must be powered on before you

 

 

 

can view or change adapter settings.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

97

Managing Network Adapters

Rebuilding Persistent Binding

 

Command or Action

Purpose

Step 3

Server /chassis/adapter # scope host-fc-if

Enters the host Fibre Channel interface command

 

{fc0| fc1| name}

mode for the specified vHBA.

Step 4

Server /chassis/adapter/host-fc-if#scope

Enters the persistent binding command mode for

 

perbi

the vHBA.

Step 5

Server /chassis/adapter/host-fc-if/perbi#

Disables persistent binding for the vHBA.

 

set persistent-lun-bindingdisable

 

Step 6

Server /chassis/adapter/host-fc-if/perbi#

Commits the transaction to the system

 

commit

configuration.

This example disables persistent binding for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 4

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if#scope perbi

Server /chassis/adapter/host-fc-if/perbi#set persistent-lun-binding disable

Server /chassis/adapter/host-fc-if/perbi*#commit

Server /chassis/adapter/host-fc-if/perbi#

Rebuilding Persistent Binding

Before You Begin

Persistent binding must be enabled in the vHBA properties.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter index

Enters the command mode for the adapter card at the

 

 

PCI slot number specified by index.

 

 

Note

The server must be powered on before you

 

 

 

can view or change adapter settings.

Step 3

Server /chassis/adapter # scope

Enters the host Fibre Channel interface command

 

host-fc-if{fc0| fc1| name}

mode for the specified vHBA.

Step 4

Server /chassis/adapter/host-fc-if#

Enters the persistent binding command mode for the

 

scope perbi

vHBA.

 

Step 5

Server /chassis/adapter/host-fc-if/perbi

Rebuilds the persistent binding table for the vHBA.

 

# rebuild

 

 

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

98

OL-28893-01

Managing Network Adapters

Managing vNICs

This example rebuilds the persistent binding table for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 4

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if#scope perbi

Server /chassis/adapter/host-fc-if/perbi#rebuild

Server /chassis/adapter/host-fc-if/perbi#

Managing vNICs

Guidelines for Managing vNICs

When managing vNICs, consider the following guidelines and restrictions:

The Cisco UCS P81E Virtual Interface Card and Cisco UCS VIC1225 Virtual Interface Card provide two default vNICs (eth0 and eth1). You can create up to 16 additional vNICs on these adapter cards.

Note If Network Interface Virtualization (NIV) mode is enabled for the adapter, you must assign a channel number to a vNIC when you create it.

After making configuration changes, you must reboot the host for settings to take effect.

Viewing vNIC Properties

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter index

Enters the command mode for the adapter card at the

 

 

PCI slot number specified by index.

 

 

Note

The server must be powered on before you

 

 

 

can view or change adapter settings.

Step 3

Server /chassis/adapter # show

Displays properties of a single vNIC, if specified, or

 

host-eth-if[eth0| eth1| name] [detail]

all vNICs.

This example displays the brief properties of all vNICs and the detailed properties of eth0:

Server# scope

chassis

 

 

 

Server /chassis # scope adapter 1

 

 

Server /chassis/adapter # show host-eth-if

CoS VLAN PXE Boot

Name

MTU

Uplink Port MAC Address

--------

----

----------------------------

---------------

eth0

1500

0

00:22:BD:D6:5C:33

0

NONE Enabled

eth1

1500

1

00:22:BD:D6:5C:34

0

NONE Enabled

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

99

Managing Network Adapters

Modifying vNIC Properties

Server /chassis/adapter # showhost-eth-ifeth0 detail

Name eth0:

MTU: 1500

Uplink Port: 0

MAC Address: 00:22:BD:D6:5C:33

CoS: 0

Trust Host CoS: disabled

PCI Order: ANY

VLAN: NONE

VLAN Mode: TRUNK

Rate Limiting: OFF

PXE Boot: enabled

Channel Number: N/A

Port Profile: N/A

Uplink Failover: N/A

Uplink Failback Timeout: N/A

Server /chassis/adapter #

Modifying vNIC Properties

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # show adapter

(Optional) Displays the available adapter devices.

Step 3

Server /chassis # scope adapter index

Enters the command mode for the adapter card at the

 

 

PCI slot number specified by index.

 

 

Note

The server must be powered on before you can

 

 

 

view or change adapter settings.

Step 4

Server /chassis/adapter # scope

Enters the host Ethernet interface command mode for

 

host-eth-if{eth0| eth1| name}

the specified vNIC.

Step 5

Server /chassis/adapter/host-eth-if#set

Specifies the maximum transmission unit (MTU) or

 

mtu mtu-value

packet size that the vNIC accepts. Valid MTU values

 

 

are 1500 to 9000 bytes; the default is 1500.

Step 6

Server /chassis/adapter/host-eth-if#set

Specifies the uplink port associated with this vNIC. All

 

uplink {0| 1}

traffic for this vNIC goes through this uplink port.

Step 7

Server /chassis/adapter/host-eth-if#set

Specifies a MAC address for the vNIC in the form

 

mac-addrmac-addr

hh:hh:hh:hh:hh:hh or hhhh:hhhh:hhhh.

Step 8

Server /chassis/adapter/host-eth-if#set

Specifies the class of service (CoS) value to be marked

 

cos cos-value

on received packets unless the vNIC is configured to

 

 

trust host CoS. Valid CoS values are 0 to 6; the default

 

 

is 0. Higher values indicate more important traffic.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

100

OL-28893-01

Managing Network Adapters

Modifying vNIC Properties

 

Command or Action

Purpose

 

 

Note

If NIV is enabled, this setting is determined

 

 

 

by the switch, and the command is ignored.

Step 9

Server /chassis/adapter/host-eth-if#set

Specifies whether the vNIC will trust host CoS or will

 

trust-host-cos{disable| enable}

remark packets. The behavior is as follows:

 

 

disable Receivedpackets are remarked with

 

 

 

the configured CoS. This is the default.

 

 

enable Theexisting CoS value of received

 

 

 

packets (host CoS) is preserved.

Step 10

Server /chassis/adapter/host-eth-if#set

Specifies the relative order of this device for PCI bus

 

order {any| 0-99}

device number assignment; the default is any.

Step 11

Server /chassis/adapter/host-eth-if#set

Specifies the default VLAN for this vNIC. Valid VLAN

 

vlan {none| vlan-id}

numbers are 1 to 4094; the default is none.

 

 

Note

If NIV is enabled, this setting is determined

 

 

 

by the switch, and the command is ignored.

Step 12

Server /chassis/adapter/host-eth-if#set

Specifies the VLAN mode for the vNIC. The modes

 

vlan-mode{access| trunk}

are as follows:

 

 

access ThevNIC belongs to only one VLAN.

 

 

trunk ThevNIC can belong to more than one

 

 

 

VLAN. This is the default.

 

 

Note

If NIV is enabled, this setting is determined

 

 

 

by the switch, and the command is ignored.

Step 13

Server /chassis/adapter/host-eth-if#set

Specifies a maximum data rate for the vNIC. The range

 

rate-limit{off| rate}

is 1 to 10000 Mbps; the default is off.

 

 

Note

If NIV is enabled, this setting is determined

 

 

 

by the switch, and the command is ignored.

Step 14

Server /chassis/adapter/host-eth-if#set

Specifies whether the vNIC can be used to perform a

 

boot {disable| enable}

PXE boot. The default is enable for the two default

 

 

vNICs, and disable for user-createdvNICs.

Step 15

Server /chassis/adapter/host-eth-if#set

If NIV mode is enabled for the adapter, select the

 

channel-numbernumber

channel number that will be assigned to this vNIC. The

 

 

range is 1 to 1000.

Step 16

Server /chassis/adapter/host-eth-if#set

If NIV mode is enabled for the adapter, select the port

 

port-profilename

profile that should be associated with the vNIC.

 

 

Note

The name must be a port profile defined on

 

 

 

the switch to which this server is connected.

Step 17

Server /chassis/adapter/host-eth-if#set

If NIV mode is enabled for the adapter, enable this

 

uplink-failover{disable| enable}

setting if traffic on this vNIC should fail over to the

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

101

Managing Network Adapters

Modifying vNIC Properties

 

Command or Action

Purpose

 

 

secondary interface if there are communication

 

 

problems.

Step 18

Server /chassis/adapter/host-eth-if#set

After a vNIC has started using its secondary interface,

 

uplink-failback-timeoutseconds

this setting controls how long the primary interface

 

 

must be available before the system resumes using the

 

 

primary interface for the vNIC.

 

 

Enter a number of seconds between 0 and 600.

Step 19

Server /chassis/adapter/host-eth-if#

Enters the interrupt command mode.

 

scope interrupt

 

Step 20

Server

Specifies the number of interrupt resources. The range

 

/chassis/adapter/host-eth-if/interrupt#

is 1 to 514; the default is 8. In general, you should

 

set interrupt-countcount

allocate one interrupt resource for each completion

 

 

queue.

Step 21

Server

 

/chassis/adapter/host-eth-if/interrupt#

 

set coalescing-timeusec

The time to wait between interrupts or the idle period that must be encountered before an interrupt is sent.

The range is 1 to 65535 microseconds; the default is 125. To turn off coalescing, enter 0 (zero).

Step 22

Server

 

/chassis/adapter/host-eth-if/interrupt#

 

set coalescing-type{idle| min}

Step 23

Server

 

/chassis/adapter/host-eth-if/interrupt#

 

set interrupt-mode{intx| msi| msix}

Step 24

Server

 

/chassis/adapter/host-eth-if/interrupt#

 

exit

Step 25

Server /chassis/adapter/host-eth-if#

 

scope recv-queue

The coalescing types are as follows:

idle Thesystem does not send an interrupt until there is a period of no activity lasting as least as long as the time specified in the coalescing time configuration.

min Thesystem waits for the time specified in the coalescing time configuration before sending another interrupt event. This is the default.

Specifies the Ethernet interrupt mode. The modes are as follows:

intx Line-basedinterrupt (PCI INTx)

msi Message-SignaledInterrupt (MSI)

msix MessageSignaled Interrupts with the optional extension(MSI-X).This is the recommended and default option.

Exits to the host Ethernet interface command mode.

Enters receive queue command mode.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

102

OL-28893-01

Managing Network Adapters

Modifying vNIC Properties

 

Command or Action

Purpose

Step 26

Server

The number of receive queue resources to allocate. The

 

/chassis/adapter/host-eth-if/recv-queue

range is 1 to 256; the default is 4.

 

# setrq-countcount

 

Step 27

Server

The number of descriptors in the receive queue. The

 

/chassis/adapter/host-eth-if/recv-queue

range is 64 to 4094; the default is 512.

 

# setrq-ring-sizesize

 

Step 28

Server

Exits to the host Ethernet interface command mode.

 

/chassis/adapter/host-eth-if/recv-queue

 

 

# exit

 

Step 29

Server /chassis/adapter/host-eth-if#

Enters transmit queue command mode.

 

scope trans-queue

 

Step 30

Server

The number of transmit queue resources to allocate.

 

/chassis/adapter/host-eth-if/trans-queue

The range is 1 to 256; the default is 1.

 

# setwq-countcount

 

Step 31

Server

The number of descriptors in the transmit queue. The

 

/chassis/adapter/host-eth-if/trans-queue

range is 64 to 4094; the default is 256.

 

# setwq-ring-sizesize

 

Step 32

Server

Exits to the host Ethernet interface command mode.

 

/chassis/adapter/host-eth-if/trans-queue

 

 

# exit

 

Step 33

Server /chassis/adapter/host-eth-if#

Enters completion queue command mode.

 

scope comp-queue

 

Step 34

Server

 

/chassis/adapter/host-eth-if/comp-queue

 

# setcq-countcount

The number of completion queue resources to allocate. The range is 1 to 512; the default is 5.

In general, the number of completion queues equals the number of transmit queues plus the number of receive queues.

Step 35

Server

Exits to the host Ethernet interface command mode.

 

/chassis/adapter/host-eth-if/comp-queue

 

 

# exit

 

Step 36

Server /chassis/adapter/host-eth-if#

Enters TCP offload command mode.

 

scope offload

 

Step 37

Server

 

/chassis/adapter/host-eth-if/offload#

 

set tcp-segment-offload{disable|

 

enable}

Enables or disables TCP Segmentation Offload as follows:

disable TheCPU segments large TCP packets.

enable TheCPU sends large TCP packets to the hardware to be segmented. This option may reduce CPU overhead and increase throughput rate. This is the default.

Note This option is also known as Large Send Offload (LSO).

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

103

Managing Network Adapters

Modifying vNIC Properties

 

Command or Action

Step 38

Server

 

/chassis/adapter/host-eth-if/offload#

 

set tcp-rx-checksum-offload{disable

 

| enable}

Purpose

Enables or disables TCP Receive Offload Checksum Validation as follows:

disable TheCPU validates all packet checksums.

Step 39

Server

 

/chassis/adapter/host-eth-if/offload#

 

set tcp-tx-checksum-offload{disable

 

| enable}

enable TheCPU sends all packet checksums to the hardware for validation. This option may reduce CPU overhead. This is the default.

Enables or disables TCP Transmit Offload Checksum Validation as follows:

disable TheCPU validates all packet checksums.

Step 40

Server

 

/chassis/adapter/host-eth-if/offload#

 

set tcp-large-receive-offload{disable

 

| enable}

enable TheCPU sends all packet checksums to the hardware for validation. This option may reduce CPU overhead. This is the default.

Enables or disables TCP Large Packet Receive Offload as follows:

disable TheCPU processes all large packets.

enable Thehardwarereassemblesallsegmentedpackets before sending them to the CPU. This option may reduce CPU utilization and increase inbound throughput. This is the default.

Step 41

Server

Exits to the host Ethernet interface command mode.

 

/chassis/adapter/host-eth-if/offload#

 

 

exit

 

Step 42

Server /chassis/adapter/host-eth-if#

Enters Receive-sideScaling (RSS) command mode.

 

scope rss

 

Step 43

Server /chassis/adapter/host-eth-if/rss#

Enables or disables RSS, which allows the efficient

 

set rss {disable| enable}

distribution of network receive processing across

 

 

multiple CPUs in multiprocessor systems. The default

 

 

is enable for the two default vNICs, and disable for

 

 

user-createdvNICs.

Step 44

Server /chassis/adapter/host-eth-if/rss#

Enables or disables IPv4 RSS. The default is enable.

 

set rss-hash-ipv4{disable| enable}

 

Step 45

Server /chassis/adapter/host-eth-if/rss#

Enables or disables TCP/IPv4 RSS. The default is

 

set rss-hash-tcp-ipv4{disable|

enable.

 

enable}

 

Step 46

Server /chassis/adapter/host-eth-if/rss#

Enables or disables IPv6 RSS. The default is enable.

 

set rss-hash-ipv6{disable| enable}

 

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

104

OL-28893-01

Managing Network Adapters

Creating a vNIC

 

Command or Action

Purpose

Step 47

Server /chassis/adapter/host-eth-if/rss#

Enables or disables TCP/IPv6 RSS. The default is

 

set rss-hash-tcp-ipv6{disable|

enable.

 

enable}

 

Step 48

Server /chassis/adapter/host-eth-if/rss#

Enables or disables IPv6 Extension RSS. The default

 

set rss-hash-ipv6-ex{disable| enable}

is disable.

Step 49

Server /chassis/adapter/host-eth-if/rss#

Enables or disables TCP/IPv6 Extension RSS. The

 

set rss-hash-tcp-ipv6-ex{disable|

default is disable.

 

enable}

 

Step 50 Server /chassis/adapter/host-eth-if/rss# Exits to the host Ethernet interface command mode.

 

exit

 

 

Step 51

Server /chassis/adapter/host-eth-if#

Commits the transaction to the system configuration.

 

commit

Note

The changes will take effect upon the next

 

 

server reboot.

This example configures the properties of a vNIC:

Server# scope chassis

 

 

 

Server /chassis # show adapter

Product ID

Vendor

PCI Slot Product Name

Serial Number

--------

--------------

--------------

--------------

--------------------

1

UCS VIC P81E

QCI1417A0QK

N2XX-ACPCI01

Cisco Systems Inc

Server /chassis # scope

adapter 1

 

 

Server /chassis/adapter

# scopehost-eth-ifTest1

 

Server /chassis/adapter/host-eth-if#set uplink 1

 

Server /chassis/adapter/host-eth-if*#

scope offload

 

Server /chassis/adapter/host-eth-if/offload*#set tcp-segment-offload enable

Server /chassis/adapter/host-eth-if/offload*#exit

Server /chassis/adapter/host-eth-if*#commit

Server /chassis/adapter/host-eth-if#

What to Do Next

Reboot the server to apply the changes.

Creating a vNIC

The adapter provides two permanent vNICs. You can create up to 16 additional vNICs.

Before You Begin

You must log in with user or admin privileges to perform this task.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

105

Managing Network Adapters

Deleting a vNIC

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter

Enters the command mode for the adapter card at the PCI

 

index

slot number specified by index.

 

 

Note

The server must be powered on before you can

 

 

 

view or change adapter settings.

Step 3

Server /chassis/adapter # create

Creates a vNIC and enters the host Ethernet interface

 

host-eth-ifname

command mode. The name argument can be up to 32

 

 

ASCII characters.

Step 4

Server /chassis/adapter/host-eth-if#

(Optional)

 

set channel-numbernumber

If NIV mode is enabled for the adapter, you must assign

 

 

a channel number to this vNIC. The range is 1 to 1000.

Step 5 Server /chassis/adapter/host-eth-if# Commits the transaction to the system configuration.

commit

Note

The changes will take effect upon the next server

 

 

 

reboot.

This example creates a vNIC on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # create host-eth-if Vnic5

Server /chassis/adapter/host-eth-if*#commit

New host-eth-ifsettings will take effect upon the next server reset

Server /chassis/adapter/host-eth-if#

Deleting a vNIC

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter

Enters the command mode for the adapter card at the PCI

 

index

slot number specified by index.

 

 

Note

The server must be powered on before you can

 

 

 

view or change adapter settings.

Step 3

Server /chassis/adapter # delete

 

host-eth-ifname

Step 4

Server /chassis/adapter # commit

Deletes the specified vNIC.

Note You cannot delete either of the two default vNICs, eth0 or eth1.

Commits the transaction to the system configuration.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

106

OL-28893-01

Managing Network Adapters

Configuring iSCSI Boot Capability

Command or Action

Purpose

Note The changes will take effect upon the next server reboot.

This example deletes a vNIC on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # delete host-eth-if Vnic5

Server /chassis/adapter *# commit

Server /chassis/adapter #

Configuring iSCSI Boot Capability

Configuring iSCSI Boot Capability for vNICs

When the rack-serversare configured in a standalone mode, and when the VIC adapters are directly attached to the Nexus 5000 family of switches, you can configure these VIC adapters to boot the servers remotely from iSCSI storage targets. You can configure Ethernet vNICs to enable a rack server to load the host OS image from remote iSCSI target devices.

To configure the iSCSI boot capability on a vNIC:

You must log in with admin privileges to perform this task.

To configure a vNIC to boot a server remotely from an iSCSI storage target, you must enable the PXE boot option on the vNIC.

Note You can configure a maximum of 2 iSCSI vNICs for each host.

Configuring iSCSI Boot Capability on a vNIC

You can configure a maximum of 2 iSCSI vNICs for each host.

Before You Begin

To configure a vNIC to boot a server remotely from an iSCSI storage target, you must enable the PXE boot option on the vNIC.

You must log in with admin privileges to perform this task.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

107

Managing Network Adapters

Configuring iSCSI Boot Capability

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter index

Enters the command mode for the adapter card at

 

 

the PCI slot number specified by index.

 

 

Note

The server must be powered on before

 

 

 

you can view or change adapter settings.

Step 3

Server /chassis/adapter # scope host-eth-if

Enters the host Ethernet interface command mode

 

{eth0| eth1| name}

for the specified vNIC.

Step 4

Server /chassis/adapter/host-eth-if#create

Creates the iSCSI boot index for the vNIC. At this

 

iscsi-bootindex

moment, only 0 is allowed as the index.

Step 5

Server

Creates an iSCSI target for the vNIC. The value

 

/chassis/adapter/host-eth-if/iscsi-boot*#

can either be 0 or 1.

 

create iscsi-targetindex

 

 

Step 6

Server

Enables the DHCP network settings for the iSCSI

 

/chassis/adapter/host-eth-if/iscsi-boot*#set

boot.

 

 

dhcp-net-settingsenabled

 

 

Step 7

Server

 

/chassis/adapter/host-eth-if/iscsi-boot*#set

 

initiator-namestring

Sets the initiator name. It cannot be more than 223 characters.

Step 8

Server

 

/chassis/adapter/host-eth-if/iscsi-boot*#set

 

dhcp-iscsi-settingsenabled

Step 9

Server

 

/chassis/adapter/host-eth-if/iscsi-boot*#

 

commit

Enables the DHCP iSCSI settings.

Commits the transaction to the system configuration.

Note The changes will take effect upon the next server reboot.

This example shows how to configure the iSCSI boot capability for a vNIC:

Server # scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-eth-if eth0

Server /chassis/adapter/host-eth-if#create iscsi-boot 0

Server /adapter/host-eth-if/iscsi-boot*#set dhcp-net-settings enabled

Server /adapter/host-eth-if/iscsi-boot *# setinitiator-nameiqn.2012-01.com.adser:abcde

Server /adapter/host-eth-if/iscsi-boot*#set dhcp-iscsi-settings enabled Server /adapter/host-eth-if/iscsi-boot*#commit

New host-eth-ifsettings will take effect upon the next server reset

Server /adapter/host-eth-if/iscsi-boot#

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

108

OL-28893-01

Managing Network Adapters

Managing VM FEX

Deleting an iSCSI Boot Configuration for a vNIC

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter index

Enters the command mode for the adapter card at the

 

 

PCI slot number specified by index.

 

 

Note

The server must be powered on before you

 

 

 

can view or change adapter settings.

Step 3

Server /chassis/adapter # scope

Enters the host Ethernet interface command mode for

 

host-eth-if{eth0| eth1| name}

the specified vNIC.

Step 4

Server /chassis/adapter/host-eth-if#

Deletes the iSCSI boot capability for the vNIC.

 

delete iscsi-boot0

 

 

Step 5

Server /chassis/adapter/host-eth-if*#

Commits the transaction to the system configuration

 

commit

Note

The changes will take effect upon the next

 

 

server reboot.

This example shows how to delete the iSCSI boot capability for a vNIC:

Server # scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-eth-if eth0

Server /chassis/adapter/host-eth-if#delete iscsi-boot 0

Server /adapter/host-eth-if/iscsi-boot*#commit

New host-eth-ifsettings will take effect upon the next server reset

Server /adapter/host-eth-if/iscsi-boot#

Managing VM FEX

Virtual Machine Fabric Extender

Cisco Virtual Machine Fabric Extender (VM FEX) extends the (prestandard) IEEE 802.1Qbh port extender architecture to virtual machines. In this architecture, each VM interface is provided with a virtual Peripheral Component Interconnect Express (PCIe) device and a virtual port on a switch.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

109

Managing Network Adapters

Viewing VM FEX Properties

Viewing VM FEX Properties

Before You Begin

The server must be powered on, or the properties will not display.

A supported Virtual Interface Card (VIC) must be installed in the chassis and the server must be powered on.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter index

Enters the command mode for the adapter card at the

 

 

PCI slot number specified by index.

 

 

Note

The server must be powered on before you can

 

 

 

view or change adapter settings.

Step 3

Server /chassis/adapter # show vmfex Displays the general VM FEX properties. For field

 

[detail]

descriptions, see General Properties Settings, on page

 

 

111.

 

Step 4

Server /chassis/adapter # scope vmfex Enters the command mode for the specified VM FEX

 

name

interface.

Step 5

Server /chassis/adapter/vmfex # show Displays Ethernet interrupt settings. For field

 

interrupt [detail]

descriptions, see Ethernet Interrupt Settings, on page

 

 

112.

 

Step 6

Server /chassis/adapter/vmfex # show Displays Ethernet receive queue settings. For field

 

recv-queue[detail]

descriptions, see Ethernet Receive Queue Settings, on

 

 

page 113.

Step 7

Server /chassis/adapter/vmfex # show Displays Ethernet transmit queue settings. For field

 

trans-queue[detail]

descriptions, see Ethernet Transmit Queue Settings, on

 

 

page 113.

Step 8

Server /chassis/adapter/vmfex # show Displays completion queue settings. For field

 

comp-queue[detail]

descriptions, see Completion Queue Settings, on page

 

 

113.

 

Step 9

Server /chassis/adapter/vmfex # show Displays TCP offload settings. For field descriptions,

 

offload [detail]

see TCP Offload Settings, on page 114.

Step 10

Server /chassis/adapter/vmfex # show Displays RSS settings. For field descriptions, see

 

rss [detail]

Receive Side Scaling Settings, on page 114.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

110

OL-28893-01

Managing Network Adapters

VM FEX Settings

This example displays the VM FEX properties:

Server /chassis/adapter # show vmfex detail

Name pts0:

MTU: 1500

Uplink Port: 0

MAC Address: 00:00:00:00:00:00

CoS: N/A

Trust Host CoS:

PCI Order:

VLAN: N/A

VLAN Mode: N/A

Rate Limiting:

PXE Boot: disabled

Channel Number: 0

Port Profile:

Uplink Failover: Enabled

Uplink Failback Timeout: 5

Server /chassis/adapter # scope

vmfex pts0

 

Server /chassis/adapter/vmfex #

show

interrupt

 

Interrupt Count Coalescing Time

(us)

Coalescing Type Interrupt Mode

---------------

--------------------

------------------------------

6

125

 

 

 

MIN

MSI

Server /chassis/adapter/vmfex #

show

recv-queue

 

Receive Queue Count Receive Queue Ring Size

 

-------------------

------------------------------

 

4

 

512

 

 

 

 

Server /chassis/adapter/vmfex #

show

trans-queue

 

Transmit Queue Count Transmit Queue Ring Size

 

--------------------

-------------------------------

 

1

 

256

 

 

 

 

Server /chassis/adapter/vmfex #

show

comp-queue

 

Completion Queue Count

Completion

Queue Ring Size

 

---------------------------------------------------

 

5

 

 

1

 

 

 

Server /chassis/adapter/vmfex #

show

offload

Large Receive

TCP Segment Offload

TCP Rx Checksum

TCP Tx Checksum

-----------------------------------------------------------------

enabled

enabled

enabled

enabled

Server

/chassis/adapter/vmfex # show rss

 

TCP Rx

Side Scaling

 

 

--------------------

 

 

enabled

 

 

 

Server

/chassis/adapter/vmfex #

 

 

VM FEX Settings

The following tables describe the VM FEX settings that you can view.

General Properties Settings

 

Name

Description

Name

A user-definedname for the VM FEX.

MTU

The maximum transmission unit, or packet size, that this VM FEX

 

accepts.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

111

Managing Network Adapters

VM FEX Settings

Name

Description

Uplink Port

The uplink port associated with this VM FEX. All traffic for this VM

 

FEX goes through this uplink port.

MAC Address

The MAC address associated with the VM FEX.

Class of Service

The class of service to associate with traffic from this VM FEX.

Trust Host CoS

Whether the VM FEX can use the class of service provided by the host

 

operating system.

PCI Order

The order in which this VM FEX will be used.

Default VLAN

The default VLAN for this VM FEX.

VLAN Mode

Whether VLAN trunking or access is configured.

Rate Limit

If rate limiting is configured, the maximum rate.

Enable PXE Boot

Whether the VM FEX can be used to perform a PXE boot.

Channel Number

If NIV mode is enabled for the adapter, the channel number assigned

 

to this VM FEX.

Port Profile

If NIV mode is enabled for the adapter, the port profile associated with

 

theVM FEX.

 

Note

This field displays the port profiles defined on the switch to

 

 

which this server is connected.

Enable Uplink Failover

If NIV mode is enabled for the adapter, whether traffic on this VM FEX

 

should fail over to the secondary interface if there are communication

 

problems.

Failback Timeout

After a VM FEX has started using its secondary interface, this setting

 

controls how long the primary interface must be available before the

 

system resumes using the primary interface for the VM FEX.

Ethernet Interrupt Settings

 

Name

Description

Interrupt Count field

The number of interrupt resources allocated to this VM FEX.

Coalescing Time field

The time CIMC waits between interrupts or the idle period that must

 

be encountered before an interrupt is sent.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

112

OL-28893-01

Managing Network Adapters

VM FEX Settings

Name

Description

Coalescing Type field

This can be one of the following:

 

MINThesystem waits for the time specified in theCoalescing

 

Time field before sending another interrupt event.

 

IDLEThesystem does not send an interrupt until there is a

 

period of no activity lasting as least as long as the time specified

 

in the Coalescing Timefield.

Interrupt Mode field

The preferred driver interrupt mode. This can be one of the following:

MSIxMessageSignaled Interrupts (MSI) with the optional extension.

MSIMSIonly.

INTxPCIINTx interrupts.

Ethernet Receive Queue Settings

 

Name

Description

Receive Queue Count field

The number of receive queue resources allocated to this VM FEX.

Receive Queue Ring Size field

The number of descriptors in each receive queue.

Ethernet Transmit Queue Settings

 

Name

Description

Transmit Queue Count field

The number of transmit queue resources allocated to this VM FEX.

Transmit Queue Ring Size field

The number of descriptors in each transmit queue.

Completion Queue Settings

 

Name

Description

Completion Queue Count field

The number of completion queue resources allocated to this VM FEX.

Completion Queue Ring Size

The number of descriptors in each completion queue.

field

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

113

Managing Network Adapters

VM FEX Settings

TCP Offload Settings

 

 

Name

Description

Enable TCP Segmentation

If enabled, the CPU sends large TCP packets to the hardware to be

Offload field

segmented. If disabled, the CPU segments large packets.

 

Note

This option is also known as Large Send Offload

 

 

(LSO).

Enable TCP Rx Offload

If enabled, the CPU sends all packet checksums to the hardware for

Checksum Validation field

validation. If disabled, the CPU validates all packet checksums.

Enable TCP Tx Offload

If enabled, the CPU sends all packets to the hardware so that the

Checksum Generation field

checksum can be calculated. If disabled, the CPU calculates all packet

 

checksums.

Enable Large Receive field

If enabled, the hardware reassembles all segmented packets before

 

sending them to the CPU. If disabled, the CPU processes all large

 

packets.

 

Receive Side Scaling Settings

 

Name

Description

Enable TCP Receive Side Scaling field

Enable IPv4 RSS field

Enable TCP-IPv4RSSfield

Enable IPv6 RSS field

Enable TCP-IPv6RSSfield

Enable IPv6 Extension RSS field

Enable TCP-IPv6Extension RSSfield

Receive Side Scaling (RSS) distributes network receive processing across multiple CPUs in multiprocessor systems.

If enabled, network receive processing is shared across processors whenever possible. If disabled, network receive processing is always handled by a single processor even if additional processors are available.

If enabled, RSS is enabled on IPv4 networks.

If enabled, RSS is enabled for TCP transmissions across IPv4 networks.

If enabled, RSS is enabled on IPv6 networks.

If enabled, RSS is enabled for TCP transmissions across IPv6 networks.

If enabled, RSS is enabled for IPv6 extensions.

If enabled, RSS is enabled for TCP transmissions across IPv6 networks.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

114

OL-28893-01

Managing Network Adapters

Managing Storage Adapters

Managing Storage Adapters

Create Virtual Drive from Unused Physical Drives

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope

Enters command mode for an installed storage card.

 

storageadapter slot

 

Step 3

Server /chassis/storageadapter #

At this point, you are prompted to enter information

 

create virtual-drive

corresponding to the RAID level, the physical drives to be

 

 

used, the size and the write policy for the new virtual drive.

 

 

Enter the appropriate information at each prompt.

 

 

When you have finished specifying the virtual drive

 

 

information, you are prompted to confirm that the

 

 

information is correct. Enter y (yes) to confirm, orn (no)

 

 

to cancel the operation.

Step 4

Server /chassis/storageadapter #

Displays the existing virtual drives.

 

show virtual-drive

 

This example shows how to create a new virtual drive that spans two unused physical drives.

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # create-virtual-drive Please enter RAID level

(0, 1, 5, 6, 10, 50, 60) -->1

Please choose from the following 2 unused physical drives:

Slot 6: size 68664 MB

Slot 7: size 68664 MB

Specify physical disks for span 0:

Enter comma-separatedPDs from abovelist-->6,7

Please enter Virtual Drive name (15 characters maximum)-->test_v_drive

Please enter Virtual Drive size in MB, GB, or TB

Example format: '400 GB' -->1000 MB

Optional attribute:

Write Policy: defaults to Write Back

OK? (y or n)-->n

0:Write Through

1:Write Back

2:Write Back with Bad BBU

3:Write Back Adaptive

Choose number from above options-->2

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

115

Managing Network Adapters

Create Virtual Drive from an Existing Drive Group

Write Policy will be set to Write Back with Bad BBU (2 and 'write-policy\:2')

New virtual drive will have the following characteristics: - Spans: '[6.7]'

- RAID level: '1'

- Name: 'test_v_drive' - Size: 1000 MB

- Write Policy: Write Back with Bad BBU

OK? (y or n)-->y

 

 

 

 

Server /chassis/storageadapter # show virtual-drive

Size

RAID Level

Virtual Drive Health

Status

Name

Boot Drive

--------------------------------------------------

--------------------

-------------

----------

Good

Optimal

 

150528 MB

RAID 0

0

 

false

Good

Optimal

 

20480 MB

RAID 0

1

 

true

Good

Optimal

 

114140 MB

RAID 0

2

 

false

Good

Optimal

test_v_drive

1000 MB

RAID 1

3

false

Good

Optimal

new_from_test

500 MB

RAID 1

4

false

 

 

 

 

 

Server /chassis/storageadapter #

Create Virtual Drive from an Existing Drive Group

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope

Enters command mode for an installed storage card.

 

storageadapter slot

 

Step 3

Server /chassis/storageadapter #

At this point, you are prompted to enter information

 

carve-virtual-drive

corresponding to the virtual drives to be used, and the size

 

 

and the write policy for the new virtual drive. Enter the

 

 

appropriate information at each prompt.

 

 

When you have finished specifying the virtual drive

 

 

information, you are prompted to confirm that the

 

 

information is correct. Enter y (yes) to confirm, orn (no)

 

 

to cancel the operation.

Step 4

Server /chassis/storageadapter #

Displays the existing virtual drives.

 

show virtual-drive

 

This example shows how to carve a new virtual drive out of unused space in an existing RAID 1 drive group:

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

116

OL-28893-01

Managing Network Adapters

Clearing Foreign Configuration

Server /chassis/storageadapter # carve-virtual-drive

 

<

Fetching virtual drives...>

 

 

ID

Name

RL

VDSize

MaxPossibleSize PD(s)

----------------------------------------------------------------

3

test_v_drive

1

1000 MB

67664 MB

6,7

Please choose from the above list the virtual drive number

whose space the new virtual drive will share-->3

 

New

virtual drive will share space with VD 3

 

Please enter Virtual Drive name (15 characters maximum)

--> new_from_test

Please enter Virtual Drive size in MB, GB, or TB (maximum: 67664 MB)

Example format: '400 GB'

--> 500 MB

 

 

Optional attribute:

 

 

 

Write Policy: defaults to Write Back

 

 

 

OK? (y or n)--

> y

 

 

 

New virtual drive will have the following characteristics:

-It will share space with virtual drive 3

-Name: 'new_from_test'

-Size: 500 MB

OK? (y or n)--

> y

 

 

 

 

Server /chassis/storageadapter # show virtual-drive

Size

RAID Level

Virtual Drive

Health

Status

Name

Boot Drive

--------------

------------------------------------

----------

----------

-------------

----------

Good

Optimal

 

150528 MB

RAID 0

0

 

false

Good

Optimal

 

20480 MB

RAID 0

1

 

true

Good

Optimal

 

114140 MB

RAID 0

2

 

false

Good

Optimal

test_v_drive

1000 MB

RAID 1

3

false

Good

Optimal

new_from_test

500 MB

RAID 1

4

false

 

 

 

 

 

Server /chassis/storageadapter #

Clearing Foreign Configuration

Important This task clears all foreign configuration on the controller. Also, all configuration information from all physical drives hosting foreign configuration is deleted. This action cannot be reverted.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapter

Enters command mode for an installed storage card.

 

slot

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

117

Managing Network Adapters

Deleting a Virtual Drive

 

Command or Action

Purpose

 

Step 3

Server /chassis/storageadapter #

You are prompted to confirm the action. Enter yes

 

clear-foreign-config

to confirm.

 

 

Note

If you do not enter yes, the action is

 

 

 

aborted.

This example shows how to clear all foreign configurations on the MegaRAID controller in slot 3:

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # clear-foreign-config

Are you sure you want to clear all foreign configurations on this controller?

All data on the drive(s) will be lost.

Enter 'yes' to confirm ->yes

Server /chassis/storageadapter #

Deleting a Virtual Drive

Important This task deletes a virtual drive, including the drives that run the booted operating system. So back up any data that you want to retain before you delete a virtual drive.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed storage

 

 

card.

 

Step 3

Server /chassis/storageadapter # scope

Enters command mode for the specified virtual

 

virtual-drivedrive-number

drive.

 

Step 4

Server /chassis/storageadapter/virtual-drive

You are prompted to confirm the action. Enter

 

# delete-virtual-drive

yes to confirm.

 

 

Note

If you do not enter yes, the action is

 

 

 

aborted.

This example shows how to delete virtual drive 3.

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive#delete-virtual-drive

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

118

OL-28893-01

Managing Network Adapters

Initializing a Virtual Drive

Are you sure you want to delete virtual drive 3?

All data on the drive will be lost. Enter 'yes' to confirm ->yes

Server /chassis/storageadapter/virtual-drive#

Initializing a Virtual Drive

All data on a virtual drive is lost when you initialize the drive. Before you run an initialization, back up any data on the virtual drive that you want to save.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed

 

 

storage card.

Step 3

Server /chassis/storageadapter # scope

Enters command mode for the specified

 

virtual-drivedrive-number

virtual drive.

Step 4

Server /chassis/storageadapter/virtual-drive#

Initializes the specified virtual drive.

 

start-initialization

 

Step 5

Server /chassis/storageadapter/virtual-drive#

(Optional) Cancels the initialization of the

 

cancel-initialization

specified virtual drive.

Step 6

Server /chassis/storageadapter/physical-drive

Displays the status of the task that is in

 

# get-operation-status

progress on the drive.

This example shows how to initialize virtual drive 3 using fast initialization:

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive#start-initialization

Are you sure you want to initialize virtual drive 3?

All data on the drive will be lost. Enter 'yes' to confirm ->yes

Fast (0) or full (1) initialization? ->0

Server /chassis/storageadapter/virtual-drive#get-operation-status

progress-percent:20% elapsed-seconds:30

operation-in-progress:initializing virtual drive

Server /chassis/storageadapter/virtual-drive#

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

119

Managing Network Adapters

Set as Boot Drive

Set as Boot Drive

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed storage

 

 

card.

Step 3

Server /chassis/storageadapter # scope

Enters command mode for the specified virtual

 

virtual-drivedrive-number

drive.

Step 4

Server /chassis/storageadapter #

Specifies the controller to boot from this

 

set-boot-drive

virtual drive.

This example shows how to specify the controller to boot from virtual drive 3:

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive

#

set-boot-drive

Are you sure you want to set virtual drive 3

as the boot drive?

Enter 'yes' to confirm ->yes

#

 

Server /chassis/storageadapter/virtual-drive

 

Modifying Attributes of a Virtual Drive

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed

 

 

storage card.

Step 3

Server /chassis/storageadapter # scope

Enters the command mode for the virtual

 

virtual-drive3

drive.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

120

OL-28893-01

Managing Network Adapters

Making a Dedicated Hot Spare

 

Command or Action

Purpose

Step 4

Server /chassis/storageadapter/virtual-drive#

Prompts you to select a different current

 

modify-attributes

policy.

This example shows how to carve a new virtual drive out of unused space in an existing RAID 1 drive group:

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # scope virtual-drive

Server /chassis/storageadapter/virtual-drive#modify-attributes

Current write policy: Write Back

0:Write Through

1:Write Back

2:Write Back even if Bad BBU

Choose number from above options -->0

The following attribute will be modified:

- Write policy: Write Through

OK? (y or n) -->y

operation in progress.

Server /chassis/storageadapter/virtual-drive#

Making a Dedicated Hot Spare

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed storage

 

 

card.

Step 3

Server /chassis/storageadapter # scope

Enters command mode for the specified

 

physical-drivedrive-number

physical drive.

Step 4

Server /chassis/storageadapter/physical-drive

You are prompted to choose a virtual drive for

 

# make-dedicated-hot-spare

which the dedicated hot spare is being created.

This example shows how to make physical drive 3 a dedicated hot spare for virtual drive 6:

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

121

Managing Network Adapters

Making a Global Hot Spare

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive#make-dedicated-hot-spare

5:VD_OS_1, RAID 0, 102400 MB, physical disks: 1

6:VD_OS_2, RAID 0, 12288 MB, physical disks: 1

7:VD_OS_3, RAID 0, 12288 MB, physical disks: 1

8:VD_DATA_1, RAID 0, 12512 MB, physical disks: 1

9:RAID1_2358, RAID 1, 40000 MB, physical disks: 2,3,5,8

11:JFB_RAID1_67, RAID 1, 20000 MB, physical disks: 6,7

12:JFB_Crv_R1_40, RAID 1, 40000 MB, physical disks: 6,7

13:JFB_R1_10GB, RAID 1, 10000 MB, physical disks: 6,7

Please choose from the above 8 virtual drives-->6

Server /chassis/storageadapter/physical-drive#

Making a Global Hot Spare

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed

 

 

storage card.

Step 3

Server /chassis/storageadapter # scope

Enters command mode for the specified

 

physical-drivedrive-number

physical drive.

Step 4

Server /chassis/storageadapter/physical-drive#

 

 

make-global-hot-spare

 

Step 5

Server /chassis/storageadapter/physical-drive#

Displays the status of the task that is in

 

get-operation-status

progress on the drive.

This example shows how to make physical drive 3 a global hot spare:

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive#make-global-hot-spare

Server /chassis/storageadapter/physical-drive#

Preparing a Drive for Removal

You can confirm this task only on physical drives that display the Unconfigured Good status.

Before You Begin

You must log in with admin privileges to perform this task.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

122

OL-28893-01

Managing Network Adapters

Removing a Drive from Hot Spare Pools

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed

 

 

storage card.

Step 3

Server /chassis/storageadapter # scope

Enters command mode for the specified

 

physical-drivedrive-number

physical drive.

Step 4

Server /chassis/storageadapter/physical-drive#

 

 

prepare-for-removal

 

This example shows how to prepare physical drive 3 for removal.

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive#prepare-for-removal

Server /chassis/storageadapter/physical-drive#

Removing a Drive from Hot Spare Pools

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed

 

 

storage card.

Step 3

Server /chassis/storageadapter # scope

Enters command mode for the specified

 

physical-drivedrive-number

physical drive.

Step 4

Server /chassis/storageadapter/physical-drive

Removes a drive from the host spare pool.

 

# remove-hot-spare

 

This example shows how to remove physical drive 3 from the hot spare pools:

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive#remove-hot-spare

Server /chassis/storageadapter/physical-drive#

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

123

Managing Network Adapters

Undo Preparing a Drive for Removal

Undo Preparing a Drive for Removal

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed

 

 

storage card.

Step 3

Server /chassis/storageadapter # scope

Enters command mode for the specified

 

physical-drivedrive-number

physical drive.

Step 4

Server /chassis/storageadapter/physical-drive#

 

 

undo-prepare-for-removal

 

This example shows how to respin physical drive 3 after preparing the drive for removal.

Server# scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive#undo-prepare-for-removal

Server /chassis/storageadapter/physical-drive#

Enabling Auto Learn Cycles for the Battery Backup Unit

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed storage

 

 

card.

Step 3

Server /chassis/storageadapter # scope bbu

Enter the battery backup unit command mode.

Step 4

Server /chassis/storageadapter #

Enables the battery auto-learncycles

 

enable-auto-learn

 

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

124

OL-28893-01

Managing Network Adapters

Disabling Auto Learn Cycles for the Battery Backup Unit

This example shows how to enable the battery auto-learncycles:

Server # scope chassis

Server /chassis # scope storageadapterSLOT-2

Server /chassis/storageadapter # scope bbu

Server /chassis/storageadapter/bbu # enable-auto-learn Automatic BBU learn cycles will occur without notice if enabled. Are you sure? [y/n]-->y

enable-auto-learninitiated

Server /chassis/storageadapter/bbu #

Disabling Auto Learn Cycles for the Battery Backup Unit

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed storage

 

 

card.

Step 3

Server /chassis/storageadapter # scope bbu

Enter the battery backup unit command mode.

Step 4

Server /chassis/storageadapter #

Disables the battery auto-learncycles

 

disable-auto-learn

 

This example shows how to disables the battery auto-learncycles:

Server # scope chassis

Server /chassis # scope storageadapterSLOT-2

Server /chassis/storageadapter # scope bbu

Server /chassis/storageadapter/bbu # disable-auto-learn Automatic BBU learn cycles will no longer occur if disabled. Are you sure? [y/n]-->y

disable-auto-learninitiated

Server /chassis/storageadapter/bbu #

Starting a Learn Cycle for a Battery Backup Unit

Before You Begin

You must be logged in as an admin to use this command.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

125

Managing Network Adapters

Toggling the Locator LED for a Physical Drive

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed storage

 

 

card.

Step 3

Server /chassis/storageadapter # scope bbu

Enter the battery backup unit command mode.

Step 4

Server /chassis/storageadapter #

Starts the learn cycle for the battery.

 

start-learn-cycle

 

This example shows how to initiate the learn cycles for a battery:

Server # scope chassis

Server /chassis # scope storageadapterSLOT-2

Server /chassis/storageadapter # scope bbu

Server /chassis/storageadapter/bbu # start-learn-cycle

Server /chassis/storageadapter/bbu #

Toggling the Locator LED for a Physical Drive

Before You Begin

You must be logged in as an admin to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed

 

 

storage card.

Step 3

Server /chassis/storageadapter # scope

Enters the physical drive command mode.

 

physical-drive3

 

Step 4

Server /chassis/storageadapter/physical-drive

Enables or disables the physical drive locator

 

# locator-led{on | off}

LED.

This example shows how to enable the locator LED for physical drive 3:

Server # scope chassis

Server /chassis # scope storageadapterSLOT-2

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive#locator-led on

Server /chassis/storageadapter/physical-drive*#commit

Server /chassis/storageadapter/physical-drive#

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

126

OL-28893-01

Managing Network Adapters

Viewing Storage Controller Logs

Viewing Storage Controller Logs

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope storageadapterslot

Enters command mode for an installed storage

 

 

card.

Step 3

Server /chassis/storageadapter # show log

Displays the storage controller logs.

This example shows how to display storage controller logs:

Server # scope chassis

Server /chassis # scope storageadapterSLOT-3

Server /chassis/storageadapter # show log

Time

 

Severity

Description

----

 

--------

-------------

Fri March 1 09:52:19 2013

Warning

Predictive Failure

Fri March 1 07:50:19 2013

Info

Battery charge complete

Fri March 1 07:50:19 2013

Info

Battery charge started

Fri March 1 07:48:19 2013

Info

Battery relearn complete

Fri March 1

07:47:19 2013

Info

Battery is discharging

Fri March 1

07:45:19 2013

Info

Battery relearn started

Server /chassis/storageadapter #

Backing Up and Restoring the Adapter Configuration

Exporting the Adapter Configuration

The adapter configuration can be exported as an XML file to a TFTP server.

Important If any firmware or BIOS updates are in progress, do not export the adapter configuration until those tasks are complete.

Before You Begin

A supported Virtual Interface Card (VIC) must be installed in the chassis and the server must be powered on. Obtain the TFTP server IP address.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

127

Managing Network Adapters

Importing the Adapter Configuration

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter

Enters the command mode for the adapter card at the PCI

 

index

slot number specified by index.

 

 

Note

The server must be powered on before you can view

 

 

 

or change adapter settings.

Step 3 Server /chassis/adapter #export-vnic protocol remote server IP address

Starts the export operation. The adapter configuration file will be stored at the specified path and filename on the remote server at the specified IP address. The protocol can be one of the following:

TFTP

FTP

SFTP

SCP

HTTP

This example exports the configuration of adapter 1:

Server# scope chassis

adapter 1

Server /chassis # scope

Server

/chassis/adapter

# export-vnicftp192.0.20.34 //test/dnld-ucs-k9-bundle.1.0.2h.bin

Server

/chassis/adapter

#

Importing the Adapter Configuration

Important If any firmware or BIOS updates are in progress, do not import the adapter configuration until those tasks are complete.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope adapter

Enters the command mode for the adapter card at the PCI

 

index

slot number specified by index.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

128

OL-28893-01

Managing Network Adapters

Restoring Adapter Defaults

Command or Action

Step 3 Server /chassis/adapter #import-vnic tftp-ip-address path-and-filename

Purpose

Note The server must be powered on before you can view or change adapter settings.

Starts the import operation. The adapter downloads the configuration file from the specified path on the TFTP server at the specified IP address. The configuration will be installed during the next server reboot.

This example imports a configuration for the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # import-vnic192.0.2.34 /ucs/backups/adapter4.xml

Import succeeded.

New VNIC adapter settings will take effect upon the next server reset.

Server /chassis/adapter #

What to Do Next

Reboot the server to apply the imported configuration.

Restoring Adapter Defaults

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis #

Restores factory default settings for the adapter at

 

adapter-reset-defaultsindex

the PCI slot number specified by the index

 

 

argument.

This example restores the default configuration of the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # adapter-reset-defaults1

This operation will reset the adapter to factory default.

All your configuration will be lost.

Continue?[y|N] y

Server /chassis #

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

129

Managing Network Adapters

Managing Adapter Firmware

Managing Adapter Firmware

Adapter Firmware

A Cisco UCS C-Seriesnetwork adapter contains the following firmware components:

Adapter firmwareThemain operating firmware, consisting of an active and a backup image, can be installed from the CIMC GUI or CLI interface or from the Host Upgrade Utility (HUU). You can upload a firmware image from either a local file system or a TFTP server.

Bootloader firmwareThebootloader firmware cannot be installed from the CIMC GUI or CLI. You can install this firmware using the Host Upgrade Utility.

Installing Adapter Firmware

Important If any firmware or BIOS updates are in progress, do not install the adapter firmware until those tasks are complete.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # update-adapter-fw

Downloads the specified adapter firmware file from the

 

tftp-ip-addresspath-and-filename

TFTP server, then installs the firmware as the backup

 

{activate| no-activate} [ pci-slot ]

image on one or two specified adapters or, if no adapter

 

[ pci-slot]

is specified, on all adapters. If the activate keyword is

 

 

specified, the new firmware is activated after installation.

Step 3

Server /chassis #

(Optional)

 

recover-adapter-update[ pci-slot ]

Clears an incomplete firmware update condition on one

 

[ pci-slot]

or two specified adapters or, if no adapter is specified,

 

 

on all adapters.

This example begins an adapter firmware upgrade on the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # update-adapter-fw192.0.2.34 /ucs/adapters/adapter4.bin activate 1

Server /chassis #

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

130

OL-28893-01

Managing Network Adapters

Activating Adapter Firmware

What to Do Next

To activate the new firmware, see Activating Adapter Firmware, on page 131.

Activating Adapter Firmware

Important While the activation is in progress, do not:

Reset, power off, or shut down the server.

Reboot or reset CIMC.

Activate any other firmware.

Export technical support or configuration data.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # activate-adapter-fw

Activates adapter firmware image 1 or 2 on the adapter

 

pci-slot{1 | 2}

in the specified PCI slot.

 

 

Note

The changes will take effect upon the next

 

 

 

server reboot.

This example activates adapter firmware image 2 on the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # activate-adapter-fw1 2

Firmware image activation suceeded

Please reset the server to run the activated image

Server /chassis #

What to Do Next

Reboot the server to apply the changes.

Resetting the Adapter

Before You Begin

You must log in with admin privileges to perform this task.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

131

Managing Network Adapters

Resetting the Adapter

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope chassis

Enters the chassis command mode.

Step 2

Server/chassis # adapter-reset index

Resets the adapter at the PCI slot number specified by

 

 

the index argument.

 

 

Note

Resetting the adapter also resets the

 

 

 

host.

This example resets the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # adapter-reset 1

This operation will reset the adapter and the host if it is on.

You may lose connectivity to the CIMC and may have to log in again.

Continue?[y|N] y

Server /chassis #

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

132

OL-28893-01

C H A P T E R 10

Configuring Communication Services

This chapter includes the following sections:

Configuring HTTP, page 133

Configuring SSH, page 134

Configuring XML API, page 135

Configuring IPMI, page 136

Configuring SNMP, page 137

Configuring HTTP

Before You Begin

You must log in as a user with admin privileges to configure HTTP.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope http

Enters the HTTP command mode.

Step 2

Server /http # set enabled {yes |no}

Enables or disables HTTP and HTTPS service on the

 

 

CIMC.

Step 3

Server /http # set http-port number

Sets the port to use for HTTP communication. The

 

 

default is 80.

Step 4

Server /http # set https-port number Sets the port to use for HTTPS communication. The

 

 

default is 443.

Step 5

Server /http # sethttp-redirect{yes

Enables or disables the redirection of an HTTP request

 

| no}

to HTTPS.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

133

Configuring Communication Services

Configuring SSH

 

Command or Action

Purpose

Step 6

Server /http # set timeout seconds

Sets the number of seconds to wait between HTTP

 

 

requests before the CIMC times out and terminates the

 

 

session.

 

 

Enter an integer between 60 and 10,800. The default is

 

 

1,800 seconds.

Step 7

Server /http # commit

Commits the transaction to the system configuration.

This example configures HTTP for the CIMC:

Server# scope http

 

 

 

 

Server /http # set enabled yes

 

 

 

Server /http *# set http-port 80

 

 

Server /http *# set https-port

443

 

 

Server /http *# sethttp-redirectyes

 

 

Server /http *# set timeout 1800

 

 

Server /http *# commit

 

 

 

 

Server /http # show

 

Active Sessions Enabled HTTP Redirected

HTTP Port

HTTPS Port Timeout

--------------------

--------

---------------

-------

----------------

80

443

1800

0

yes

yes

Server /http #

Configuring SSH

Before You Begin

You must log in as a user with admin privileges to configure SSH.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope ssh

Enters the SSH command mode.

Step 2

Server /ssh # set enabled {yes |no}

Enables or disables SSH on the CIMC.

Step 3

Server /ssh #

set ssh-portnumber

Sets the port to use for secure shell access. The default

 

 

 

is 22.

Step 4

Server /ssh #

set timeout seconds

Sets the number of seconds to wait before the system

 

 

 

considers an SSH request to have timed out.

 

 

 

Enter an integer between 60 and 10,800. The default

 

 

 

is 300 seconds.

Step 5

Server /ssh #

commit

Commits the transaction to the system configuration.

Step 6

Server /ssh #

show [detail]

(Optional) Displays the SSH configuration.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

134

OL-28893-01

Configuring Communication Services

Configuring XML API

This example configures SSH for the CIMC:

Server# scope

ssh

 

Server /ssh

#

set enabled yes

Server /ssh

*# set

ssh-port22

Server

/ssh

*#

set

timeout 600

Server

/ssh

*#

commit

Server /ssh # show

Active Sessions Enabled

SSH Port

Timeout

----------

--------

----------------------

22

600

1

yes

Server /ssh #

Configuring XML API

XML API for CIMC

The Cisco CIMC XML application programming interface (API) is a programmatic interface to CIMC for a C-SeriesRack-MountServer. The API accepts XML documents through HTTP or HTTPS.

For detailed information about the XML API, see Cisco UCS Rack-Mount Servers CIMC XML API Programmers Guide.

Enabling XML API

Before You Begin

You must log in as a user with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope xmlapi

Enters XML API command mode.

Step 2

Server /xmlapi # set enabled {yes |no}

Enables or disables XML API control of CIMC.

Step 3

Server /xmlapi # commit

Commits the transaction to the system

 

 

configuration.

This example enables XML API control of CIMC and commits the transaction:

Server# scope xmlapi

Server /xmlapi # set enabled yes

Server /xmlapi *# commit

Server /xmlapi # show detail

XMLAPI Settings:

Enabled: yes

Active Sessions: 0

Max Sessions: 4

Server /xmlapi #

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

135

Configuring Communication Services

Configuring IPMI

Configuring IPMI

IPMI Over LAN

Intelligent Platform Management Interface (IPMI) defines the protocols for interfacing with a service processor embedded in a server platform. This service processor is called a Baseboard Management Controller (BMC) and resides on the server motherboard. The BMC links to a main processor and other on-boardelements using a simple serial bus.

During normal operations, IPMI lets a server operating system obtain information about system health and control system hardware. For example, IPMI enables the monitoring of sensors, such as temperature, fan speeds and voltages, for proactive problem detection. If server temperature rises above specified levels, the server operating system can direct the BMC to increase fan speed or reduce processor speed to address the problem.

Configuring IPMI over LAN

Configure IPMI over LAN when you want to manage the CIMC with IPMI messages.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope ipmi

Enters the IPMI command mode.

Step 2

Server /ipmi #

set enabled

Enables or disables IPMI access on this server.

 

{yes| no}

 

 

Step 3

Server /ipmi #

set

Specifies the highest privilege level that can be assigned to an IPMI

privilege-level {readonly | session on this server. This can be:

user | admin}

readonly IPMI users can view information but cannot make any changes. If you select this option, IPMI users with the "Administrator", "Operator", or "User" user roles can only createread-onlyIPMI sessions, regardless of their other IPMI privileges.

user IPMI users can perform some functions but cannot perform administrative tasks. If you select this option, IPMI users with the "Administrator" or "Operator" user role can create user andread-onlysessions on this server.

admin IPMIusers can perform all available actions. If you select this option, IPMI users with the "Administrator" user role can create admin, user, andread-onlysessions on this server.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

136

OL-28893-01

Configuring Communication Services

Configuring SNMP

 

Command or Action

Purpose

Step 4

Server /ipmi #

set

Sets the IPMI encryption key to use for IPMI communications. The

 

encryption-keykey

key value must be 40 hexadecimal numbers.

Step 5

Server /ipmi #

commit

Commits the transaction to the system configuration.

This example configures IPMI over LAN for the CIMC:

Server# scope ipmi

Server /ipmi # set enabled yes

Server /ipmi *# setprivilege-leveladmin

Server /ipmi *# setencryption-keyabcdef01234567890abcdef01234567890abcdef

Server /ipmi *# commit

 

Server /ipmi # show

Privilege Level Limit

Enabled Encryption Key

-----------------------------------------------

---------------------

yes

abcdef01234567890abcdef01234567890abcdef

admin

Server /ipmi #

Configuring SNMP

SNMP

The Cisco UCS C-SeriesRack-MountServers support the Simple Network Management Protocol (SNMP) for viewing server configuration and status and for sending fault and alert information by SNMP traps. For information on Management Information Base (MIB) files supported by CIMC, see theMIB Quick Reference for Cisco UCS at this URL:http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/mib/reference/UCS_ MIBRef.html.

Configuring SNMP Properties

Before You Begin

You must log in as a user with admin privileges to perform this task.

Procedure

 

Command or Action

Step 1

Server# scope snmp

Step 2

Server /snmp # set enabled {yes

 

| no}

Purpose

Enters SNMP command mode.

Enables or disables SNMP.

Note SNMP must be enabled and saved before additional SNMP configuration commands are accepted.

Step 3

Server /snmp # commit

Commits the transaction to the system configuration.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

137

Configuring Communication Services

Configuring SNMP Properties

 

Command or Action

Purpose

Step 4

Server /snmp # set

Specifies the default SNMP v1 or v2c community name that

 

community-strcommunity

CIMC includes on any trap messages it sends to the SNMP

 

 

host. The name can be up to 18 characters.

Step 5

Server /snmp #

This can be one of the following : Disabled, Limited, or Full.

 

setcommunity-access

 

Step 6

Server /snmp #

Specifies the SNMP community group to which trap

 

settrap-community-str

information should be sent. The name can be up to 18

 

 

characters

Step 7

Server /snmp # set sys-contact

Specifies the system contact person responsible for the SNMP

 

contact

implementation. The contact information can be up to 254

 

 

characters, such as an email address or a name and telephone

 

 

number. To enter a value that contains spaces, you must

 

 

enclose the entry with quotation marks.

Step 8

Server /snmp # setsys-location

Specifies the location of the host on which the SNMP agent

 

location

(server) runs. The location information can be up to 254

 

 

characters. To enter a value that contains spaces, you must

 

 

enclose the entry with quotation marks.

Step 9

Server /snmp # commit

Commits the transaction to the system configuration.

This example configures the SNMP properties and commits the transaction:

Server# scope snmp

Server /snmp # set enabled yes

Server /snmp *# commit

Server /snmp # setcommunity-strcimcpublic

Server /snmp # setcommunity-accessFull

Server /snmp # settrap-community-strpublic

Server /snmp *# setsys-contact"User Name <username@example.com>+1-408-555-1212"

Server /snmp *# setsys-location"San Jose, California"

Server /snmp *# commit

Server /snmp # show detail

SNMP Settings:

SNMP Port: 161

System Contact: User Name <username@example.com> +1-408-555-1212

System Location: San Jose, California

SNMP Community: cimcpublic

SNMP Trap community: public

SNMP Community access: Full

Enabled: yes

Server /snmp #

What to Do Next

Configure SNMP trap settings as described in Configuring SNMP Trap Settings, on page 139.

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

138

OL-28893-01

Configuring Communication Services

Configuring SNMP Trap Settings

Configuring SNMP Trap Settings

Before You Begin

You must log in with admin privileges to perform this task.

SNMP must be enabled and saved before trap settings can be configured.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope snmp

Enters the SNMP command mode.

Step 2

Server /snmp # scope

Enters the SNMP trap destination command mode for

 

trap-destinationsnumber

the specified destination. Four SNMP trap destinations

 

 

are available. The destination number is an integer

 

 

between 1 and 15.

Step 3

Server /snmp/trap-destinations#set

 

enabled {yes| no}

Step 4

Server /snmp/trap-destinations#set

 

version {1| 2| 3}

Step 5

Server /snmp/trap-destinations#set

 

type {trap| inform}

Step 6

Server /snmp/trap-destinations#set

 

user user

Step 7

Server /snmp/trap-destination#set

 

v4-addr ip-address

Step 8

Server /snmp/trap-destination#

 

commit

Enables or disables the SNMP trap destination.

Specify the desired SNMP version of the trap message.

Note SNMPv3 traps will be delivered only to locations where the SNMPv3 user and key values are configured correctly.

Specifies whether SNMP notification messages are sent as simple traps or as inform requests requiring acknowledgment by the receiver.

Note The inform option can be chosen only for V2 users.

Specifies the destination IP address to which SNMP trap information is sent.

Commits the transaction to the system configuration.

This example configures general SNMP trap settings and trap destination number 1 and commits the transaction:

Server# scope snmp

Server /snmp # Scopetrap-destinations1

Server /snmp/trap-destination*#set enabled yes

Server /snmp/trap-destination*#set version 2

Server /snmp/trap-destination*#set type inform

Server /snmp/trap-destination*#set user user1

Server /snmp/trap-destination*#set v4-addr 192.2.3.4

Server /snmp/trap-destination*#commit

Server /snmp/trap-destination#show detail

Trap Destination 1:

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

139

Configuring Communication Services

Sending a Test SNMP Trap Message

Enabled: yes

SNMP version: 2

Trap type: inform

SNMP user: user1

IPv4 Address: 192.2.3.4

Delete Trap: no

Server /snmp/trap-destination#

Sending a Test SNMP Trap Message

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

 

Command or Action

Purpose

 

Step 1

Server# scope snmp

Enters the SNMP command mode.

Step 2

Server /snmp # sendSNMPtrap

Sends an SNMP test trap to the configured SNMP trap

 

 

destination that are enabled.

 

 

Note

The trap must be configured and enabled in order

 

 

 

to send a test message.

This example sends a test message to all the enabled SNMP trap destinations:

Server# scope snmp

Server /snmp # sendSNMPtrap

SNMP Test Trap sent to the destination.

Server /snmp #

Configuring SNMPv3 Users

Before You Begin

You must log in as a user with admin privileges to perform this task.

SNMP must be enabled and saved before these configuration commands are accepted.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope snmp

Enters the SNMP command mode.

Step 2

Server /snmp # scope v3users

Enters the SNMPv3 users command mode for the

 

number

specified user number.

Step 3

Server /snmp/v3users # set v3add

Adds or deletes an SNMPv3 user. This can be one of the

 

{yes| no}

following:

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

140

OL-28893-01

Configuring Communication Services

Configuring SNMPv3 Users

 

Command or Action

Purpose

 

 

 

yesThisuser is enabled as an SNMPv3 user and

 

 

is allowed to access the SNMP OID tree.

 

 

Note

The security name and security level must

 

 

 

also be configured at this time or the user

 

 

 

addition will fail.

 

 

noThisuser configuration is deleted.

Step 4

Server /snmp/v3users # set

Enter an SNMP username for this user.

 

v3security-namesecurity-name

 

 

Step 5

Server /snmp/v3users # set

Select a security level for this user. This can be one of the

 

v3security-level{noauthnopriv|

following:

 

 

authnopriv | authpriv}

noauthnoprivTheuser does not require an

 

 

 

 

authorization or privacy password.

 

 

authnoprivTheuser requires an authorization

 

 

password but not a privacy password. If you select

 

 

this option, you must configure an authentication

 

 

key.

 

 

 

authprivTheuser requires both an authorization

 

 

password and a privacy password. If you select this

 

 

option, you must configure an authentication key

 

 

and a private encryption key.

Step 6

Server /snmp/v3users # set v3proto

Select an authentication protocol for this user.

 

{MD5| SHA}

 

 

Step 7

Server /snmp/v3users # set

Enter an authorization password for this user.

 

v3auth-keyauth-key

 

 

Step 8

Server /snmp/v3users # set

Select an encryption protocol for this user.

 

v3priv-proto{DES| AES}

 

 

Step 9

Server /snmp/v3users # set

Enter a private encryption key (privacy password) for this

 

v3priv-auth-keypriv-auth-key

user.

 

Step 10

Server /snmp/v3users # commit

Commits the transaction to the system configuration.

This example configures SNMPv3 user number 2 and commits the transaction:

Server# scope snmp

v3users 2

Server /snmp # scope

Server /snmp/v3users

# set v3add yes

Server /snmp/v3users

*# setv3security-nameucsSNMPV3user

Server /snmp/v3users

*# setv3security-levelauthpriv

Server /snmp/v3users

*# set v3proto SHA

Server /snmp/v3users

*# setv3auth-key

Please enter v3auth-key:ex4mp1ek3y

Please confirm v3auth-key:ex4mp1ek3y

Server /snmp/v3users

*# setv3priv-protoAES

Server /snmp/v3users

*# setv3priv-auth-key

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

141

Configuring Communication Services

Configuring SNMPv3 Users

Please enter v3priv-auth-key:!1@2#3$4%5^6&7*8

Please confirm v3priv-auth-key:!1@2#3$4%5^6&7*8

Server /snmp/v3users *# commit

Settings are being applied ... allow a few minutes for the process to complete

Server /snmp/v3users # show detail

User 2:

Add User: yes

Security Name: ucsSNMPV3user

Security Level: authpriv

Auth Type: SHA

Auth Key: ******

Encryption: AES

Private Key: ******

Server /snmp/v3users #

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

142

OL-28893-01

C H A P T E R 11

Managing Certificates

This chapter includes the following sections:

Managing the Server Certificate, page 143

Generating a Certificate Signing Request, page 143

Creating a Self-Signed Certificate, page 145

Uploading a Server Certificate, page 147

Managing the Server Certificate

You can generate a certificate signing request (CSR) to obtain a new certificate, and you can upload the new certificate to the CIMC to replace the current server certificate. The server certificate may be signed either by a public Certificate Authority (CA), such as Verisign, or by your own certificate authority.

Procedure

Step 1 Generate the CSR from the CIMC.

Step 2 Submit the CSR file to a certificate authority that will issue and sign your certificate. If your organization generates its ownself-signedcertificates, you can use the CSR file to generate aself-signedcertificate.

Step 3 Upload the new certificate to the CIMC.

Note The uploaded certificate must be created from a CSR generated by the CIMC. Do not upload a certificate that was not created by this method.

Generating a Certificate Signing Request

Before You Begin

You must log in as a user with admin privileges to configure certificates.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

143

Managing Certificates

Generating a Certificate Signing Request

Procedure

 

Command or Action

Purpose

Step 1

Server# scope certificate

Enters the certificate command mode.

Step 2

Server /certificate # generate-csr

Launches a dialog for the generation of a certificate

 

 

signing request (CSR).

You will be prompted to enter the following information for the certificate signing request:

Common Name (CN)

The fully qualified hostname of the CIMC.

Organization Name (O)

The organization requesting the certificate.

Organization Unit (OU)

The organizational unit.

Locality (L)

The city or town in which the company requesting

 

the certificate is headquartered.

StateName (S)

The state or province in which the company

 

requesting the certificate is headquartered.

Country Code (CC)

The two-letterISO country code for the country in

 

which the company is headquartered.

Email

The administrative email contact at the company.

After you have entered the requested information, the system will generate and display a certificate signing request in the console output. A CSR file will not be created, but you can copy the CSR information from the console output and paste the information into a text file.

This example generates a certificate signing request:

Server# scope certificate

Server /certificate # generate-csr

Common Name (CN): test.example.com

Organization Name (O): Example, Inc.

Organization Unit (OU): Test Department

Locality (L): San Jose

StateName (S): CA

Country Code (CC): US

Email: user@example.com

Continue to generate CSR?[y|N]y

-----BEGINCERTIFICATEREQUEST-----

MIIB/zCCAWgCAQAwgZkxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEVMBMGA1UE

BxMMU2FuIEpvc2UsIENBMRUwEwYDVQQKEwxFeGFtcGxlIEluYy4xEzARBgNVBAsT

ClRlc3QgR3JvdXAxGTAXBgNVBAMTEHRlc3QuZXhhbXBsZS5jb20xHzAdBgkqhkiG

9w0BCQEWEHVzZXJAZXhhbXBsZS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ

AoGBAMZw4nTepNIDhVzb0j7Z2Je4xAG56zmSHRMQeOGHemdh66u2/XAoLx7YCcYU

ZgAMivyCsKgb/6CjQtsofvzxmC/eAehuK3/SINv7wd6Vv2pBt6ZpXgD4VBNKONDl

GMbkPayVlQjbG4MD2dx2+H8EH3LMtdZrgKvPxPTE+bF5wZVNAgMBAAGgJTAjBgkq

hkiG9w0BCQcxFhMUQSBjaGFsbGVuZ2UgcGFzc3dvcmQwDQYJKoZIhvcNAQEFBQAD

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

144

OL-28893-01

Managing Certificates

Creating a Self-SignedCertificate

gYEAG61CaJoJaVMhzCl903O6Mg51zq1zXcz75+VFj2I6rH9asckCld3mkOVx5gJU

Ptt5CVQpNgNLdvbDPSsXretysOhqHmp9+CLv8FDuy1CDYfuaLtvlWvfhevskV0j6

mK3Ku+YiORnv6DhxrOoqau8r/hyI/L43l7IPN1HhOi3oha4=

-----ENDCERTIFICATEREQUEST-----

Copy everything from "-----BEGIN ..."to "END CERTIFICATEREQUEST-----",paste to a file, send to your chosen CA for signing,

and finally upload the signed certificate via upload command.

---OR---

Continue to self sign CSR and overwrite the current certificate? All HTTPS and SSH sessions will be disconnected. [y|N]N

What to Do Next

Perform one of the following tasks:

If you do not want to obtain a certificate from a public certificate authority, and if your organization does not operate its own certificate authority, you can allow CIMC to internally generate a self-signedcertificate from the CSR and upload it immediately to the server. Typey after the final prompt in the example to perform this action.

If your organization operates its own certificate server for generating self-signedcertificates, copy the command output from"-----BEGIN ..."to "END CERTIFICATEREQUEST-----"and paste to a file named csr.txt. Input the CSR file to your certificate server to generate aself-signedcertificate.

If you will obtain a certificate from a public certificate authority, copy the command output from "-----BEGIN ..."to "END CERTIFICATEREQUEST-----"and paste to a file named csr.txt. Submit the CSR file to the certificate authority to obtain a signed certificate.

If you did not use the first option, in which CIMC internally generates and uploads a self-signedcertificate, you must upload the new certificate using theupload command in certificate command mode.

Creating a Self-SignedCertificate

As an alternative to using a public Certificate Authority (CA) to generate and sign a server certificate, you can operate your own CA and sign your own certificates. This section shows commands for creating a CA and generating a server certificate using the OpenSSL certificate server running on Linux. For detailed information about OpenSSL, see http://www.openssl.org.

Note These commands are to be entered on a Linux server with the OpenSSL package, not in the CIMC CLI.

Before You Begin

Obtain and install a certificate server software package on a server within your organization.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

145

Managing Certificates

Creating a Self-SignedCertificate

Procedure

Command or Action

Step 1 openssl genrsa-outCA_keyfilename keysize

Example:

# openssl genrsa -outca.key 1024

Purpose

This command generates an RSA private key that will be used by the CA.

Note To allow the CA to access the key without user input, do not use the-des3option for this command.

The specified file name contains an RSA key of the specified key size.

Step 2 openssl req-new-x509-daysnumdays

-key CA_keyfilename-out CA_certfilename

Example:

# openssl req -new-x509-days365-keyca.key-outca.crt

Step 3 echo "nsCertType = server" > openssl.conf

Example:

# echo "nsCertType = server" > openssl.conf

This command generates a new self-signedcertificate for the CA using the specified key. The certificate is valid for the specified period. The command prompts the user for additional certificate information.

The certificate server is an active CA.

This command adds a line to the OpenSSL configuration file to designate the certificate as a server-onlycertificate. This designation is a defense against aman-in-the-middleattack, in which an authorized client attempts to impersonate the server.

The OpenSSL configuration file openssl.conf contains the statement "nsCertType = server".

Step 4 openssl x509-req-daysnumdays -in

CSR_filename -CA CA_certfilename

-set_serial04-CAkeyCA_keyfilename -outserver_certfilename -extfileopenssl.conf

Example:

# openssl x509 -req-days365-incsr.txt-CAca.crt-set_serial04-CAkeyca.key-outmyserver05.crt-extfileopenssl.conf

This command directs the CA to use your CSR file to generate a server certificate.

Your server certificate is contained in the output file.

This example shows how to create a CA and to generate a server certificate signed by the new CA. These commands are entered on a Linux server running OpenSSL.

# /usr/bin/openssl genrsa-outca.key 1024

Generating RSA private key, 1024 bit long modulus

.............++++++

.....++++++

e is 65537 (0x10001)

# /usr/bin/openssl req-new-x509-days365-keyca.key-outca.crt

You are about to be asked to enter information that will be incorporated into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank For some fields there will be a default value,

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

146

OL-28893-01

Managing Certificates

Uploading a Server Certificate

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [GB]:US

State or Province Name (full name) [Berkshire]:California Locality Name (eg, city) [Newbury]:San Jose

Organization Name (eg, company) [My Company Ltd]:Example Incorporated Organizational Unit Name (eg, section) []:Unit A

Common Name (eg, your name or your server's hostname) []:example.com

Email Address []:admin@example.com

#echo "nsCertType = server" > openssl.conf

#/usr/bin/openssl x509 -req-days365-incsr.txt-CAca.crt-set_serial01-CAkeyca.key-outserver.crt-extfileopenssl.conf

Signature ok

subject=/C=US/ST=California/L=San Jose/O=Example Inc./OU=Unit A/CN=example.com/emailAddress=john@example.com

Getting CA Private Key

What to Do Next

Upload the new certificate to the CIMC.

Uploading a Server Certificate

Before You Begin

You must log in as a user with admin privileges to upload a certificate.

The certificate to be uploaded must be available as readable text. During the upload procedure, you will copy the certificate text and paste it into the CLI.

Note You must first generate a CSR using the CIMC certificate management CSR generation procedure, and you must use that CSR to obtain the certificate for uploading. Do not upload a certificate that was not obtained by this method.

Note All current HTTPS and SSH sessions are disconnected when the new server certificate is uploaded.

Procedure

 

Command or Action

Purpose

Step 1

Server# scope certificate

Enters the certificate command mode.

Step 2

Server /certificate # upload

Launches a dialog for entering and uploading the

 

 

new server certificate.

Copy the certificate text, paste it into the console when prompted, and type CTRL+D to upload the certificate.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

147

Managing Certificates

Uploading a Server Certificate

This example uploads a new certificate to the server:

Server# scope certificate

Server /certificate # upload

Please paste your certificate here, when finished, press CTRL+D.

-----BEGINCERTIFICATE-----

MIIB/zCCAWgCAQAwgZkxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEVMBMGA1UE

BxMMU2FuIEpvc2UsIENBMRUwEwYDVQQKEwxFeGFtcGxlIEluYy4xEzARBgNVBAsT

ClRlc3QgR3JvdXAxGTAXBgNVBAMTEHRlc3QuZXhhbXBsZS5jb20xHzAdBgkqhkiG

9w0BCQEWEHVzZXJAZXhhbXBsZS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ

AoGBAMZw4nTepNIDhVzb0j7Z2Je4xAG56zmSHRMQeOGHemdh66u2/XAoLx7YCcYU

ZgAMivyCsKgb/6CjQtsofvzxmC/eAehuK3/SINv7wd6Vv2pBt6ZpXgD4VBNKONDl

GMbkPayVlQjbG4MD2dx2+H8EH3LMtdZrgKvPxPTE+bF5wZVNAgMBAAGgJTAjBgkq

hkiG9w0BCQcxFhMUQSBjaGFsbGVuZ2UgcGFzc3dvcmQwDQYJKoZIhvcNAQEFBQAD

gYEAG61CaJoJaVMhzCl903O6Mg51zq1zXcz75+VFj2I6rH9asckCld3mkOVx5gJU

Ptt5CVQpNgNLdvbDPSsXretysOhqHmp9+CLv8FDuy1CDYfuaLtvlWvfhevskV0j6

mK3Ku+YiORnv6DhxrOoqau8r/hyI/L43l7IPN1HhOi3oha4=

-----ENDCERTIFICATE-----

<CTRL+D>

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

148

OL-28893-01

C H A P T E R 12

Configuring Platform Event Filters

This chapter includes the following sections:

Platform Event Filters, page 149

Enabling Platform Event Alerts, page 149

Disabling Platform Event Alerts, page 150

Configuring Platform Event Filters, page 150

Configuring Platform Event Trap Settings, page 152

Interpreting Platform Event Traps, page 153

Platform Event Filters

A platform event filter (PEF) can trigger an action and generate an alert when a critical hardware-relatedevent occurs. For each PEF, you can choose the action to be taken (or take no action) when a platform event occurs. You can also choose to generate and send an alert when a platform event occurs. Alerts are sent as an SNMP trap, so you must configure an SNMP trap destination before the alerts can be sent.

You can globally enable or disable the generation of platform event alerts. When disabled, alerts are not sent even if PEFs are configured to send them.

Enabling Platform Event Alerts

Procedure

 

Command or Action

Purpose

Step 1

Server# scope fault

Enters the fault command mode.

Step 2

Server /fault # set

Enables platform event alerts.

 

platform-event-enabledyes

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

149

Configuring Platform Event Filters

Disabling Platform Event Alerts

 

Command or Action

Purpose

Step 3

Server /fault #

commit

Commits the transaction to the system

 

 

 

configuration.

Step 4

Server /fault #

show [detail]

(Optional) Displays the platform event alert

 

 

 

configuration.

The following example enables platform event alerts:

Server# scope

fault

 

Server /fault

# setplatform-event-enabledyes

Server /fault

*# commit

Server /fault

# show

Platform Event Enabled

SNMP Community String

---------------------

-----------------------

public

 

yes

Server /fault

#

 

Disabling Platform Event Alerts

Procedure

 

Command or Action

Purpose

Step 1

Server# scope fault

Enters the fault command mode.

Step 2

Server /fault #

set

Disables platform event alerts.

 

platform-event-enabledno

 

Step 3

Server /fault #

commit

Commits the transaction to the system

 

 

 

configuration.

Step 4

Server /fault #

show [detail]

(Optional) Displays the platform event alert

 

 

 

configuration.

The following example disables platform event alerts:

Server# scope

fault

 

Server /fault

# setplatform-event-enabledno

Server /fault

*# commit

Server /fault

# show

Platform Event Enabled

SNMP Community String

---------------------

-----------------------

public

 

no

Server /fault

#

 

Configuring Platform Event Filters

You can configure actions and alerts for the following platform event filters:

 

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

150

OL-28893-01

Configuring Platform Event Filters

Configuring Platform Event Filters

ID

Platform Event Filter

1Temperature Critical Assert Filter

2Temperature Warning Assert Filter

3Voltage Critical Assert Filter

4Current Assert Filter

5Fan Critical Assert Filter

6Processor Assert Filter

7Power Supply Critical Assert Filter

8Power Supply Warning Assert Filter

9Power Supply Redundancy Lost Filter

10Discrete Power Supply Assert Filter

11Memory Assert Filter

12Drive Slot Assert Filter

Procedure

 

Command or Action

Purpose

Step 1

Server# scope fault

Enters the fault command mode.

Step 2

Server /fault # scope pef id

Enters the platform event filter command mode for the

 

 

specified event.

 

 

See the Platform Event Filter table for event ID numbers.

Step 3

Server /fault/pef # set action

Selects the desired system action when this event occurs. The

 

{none| reboot| power-cycle|

action can be one of the following:

 

power-off}

none Nosystem action is taken.

 

 

 

 

reboot Theserver is rebooted.

 

 

power-cycle Theserver is power cycled.

 

 

power-off Theserver is powered off.

Step 4

Server /fault/pef # set send-alert

Enables or disables the sending of a platform event alert for

 

{yes| no}

this event.

Cisco UCS C-SeriesServers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01

151

Configuring Platform Event Filters

Configuring Platform Event Trap Settings

 

Command or Action

Purpose

 

 

 

Note

For an alert to be sent, the filter trap settings must

 

 

 

be configured properly and platform event alerts

 

 

 

must be enabled.

Step 5

Server /fault/pef # commit

Commits the transaction to the system configuration.

This example configures the platform event alert for an event:

Server# scope fault

 

 

 

Server /fault # scope pef 11

 

 

Server /fault/pef # set action reboot

 

 

Server /fault/pef *# set send-alert yes

 

 

Server /fault/pef *# commit

 

 

Server /fault/pef # show

Action

Send Alert

Platform Event Filter Event

---------------------

------------------------