B Cisco UCS Manager Server MGMT Guide 3 1

Cisco UCS Manager Server Management Guide, Release 3.
1
First Published: 2016-01-20
Last Modified: 2016-09-17
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
2016
Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
Preface xv
Audience xv
Conventions xv
Related Cisco UCS Documentation xvii
Documentation Feedback xvii
CHAPTER 1
New and Changed Information 1

New and Changed Information for this Release 1
CHAPTER 2
Server Management Overview 3

Server Management Overview 3
Cisco UCS Manager User Documentation 3
CHAPTER 3
Server License Management 5

Licenses 5
C-Direct Rack Licensing Support 7
Obtaining the Host ID for a Fabric Interconnect 8
Obtaining a License 8
Downloading Licenses to the Fabric Interconnect from the Local File System 9
Downloading Licenses to the Fabric Interconnect from a Remote Location 10
Installing a License 11
Viewing the Licenses Installed on a Fabric Interconnect 12
Determining the Grace Period Available for a Port or Feature 12
Determining the Expiry Date of a License 12
Uninstalling a License 13
CHAPTER 4
Registering Cisco UCS Domains with Cisco UCS Central 15
Cisco UCS Manager Server Management Guide, Release 3.1

iii
Contents
Registration of Cisco UCS Domains 15

Policy Resolution between Cisco UCS Manager and Cisco UCS Central 16
Registering a Cisco UCS Domain with Cisco UCS Central 17
Configuring Policy Resolutions between Cisco UCS Manager and Cisco UCS Central 18
Setting Cisco UCS Central Registration Properties in Cisco UCS Manager 19
Unregistering a Cisco UCS Domain from Cisco UCS Central 20
CHAPTER 5
Power Capping in Cisco UCS and Power Management for Blades 21

Power Capping in Cisco UCS 22
Power Policy Configuration 23
Power Policy for Cisco UCS Servers 23
Configuring the Power Policy 23
Power Supply for Redundancy Method 24
Configuring Policy Driven Chassis Group Power Capping 24
Policy Driven Chassis Group Power Capping 24
Power Control Policy 24
Creating a Power Control Policy 25
Deleting a Power Control Policy 27
Power Groups in UCS Manager 27
Creating a Power Group 29
Adding a Chassis to a Power Group 31
Removing a Chassis from a Power Group 31
Deleting a Power Group 32
Blade Level Power Capping 32
Manual Blade Level Power Cap 32
Setting the Blade-Level Power Cap for a Server 32
Viewing the Blade-Level Power Cap 33
Global Power Profiling Policy Configuration 34
Global Power Profiling Policy 34
Configuring the Global Power Profile Policy 34
Global Power Allocation Policy Configuration 35
Global Power Allocation Policy 35
Configuring the Global Power Allocation Policy 35
Power Management During Power-on Operations 35
Power Sync Policy Configuration 36

iv
Contents
Power Sync Policy 36

Power Synchronization Behavior 37
Creating a Power Sync Policy 37
Changing a Power Sync Policy 39
Deleting a Power Sync Policy 39
Rack Server Power Management 40
UCS Mini Power Management 40
CHAPTER 6
Blade Server Hardware Management 41

Blade Server Management 42
Guidelines for Removing and Decommissioning Blade Servers 42
Recommendations for Avoiding Unexpected Server Power Changes 42
Booting a Blade Server 43
Booting a Rack-Mount Server from the Service Profile 44
Determining the Boot Order of a Blade Server 44
Shutting Down a Blade Server 45
Shutting Down a Server from the Service Profile 45
Resetting a Blade Server 46
Resetting a Blade Server to Factory Default Settings 47
Reacknowledging a Blade Server 48
Removing a Server from a Chassis 48
Deleting the Inband Configuration from a Blade Server 49
Decommissioning a Blade Server 49
Recommissioning a Blade Server 50
Reacknowledging a Server Slot in a Chassis 50
Removing a Non-Existent Blade Server from the Configuration Database 51
Turning the Locator LED for a Blade Server On and Off 51
Turning the Local Disk Locator LED on a Blade Server On and Off 52
Resetting the CMOS for a Blade Server 52
Resetting the CIMC for a Blade Server 53
Clearing TPM for a Blade Server 53
Viewing the POST Results for a Blade Server 54
Issuing an NMI from a Blade Server 54
Viewing Health Events for a Blade Server 55
Health LED Alarms 57

v
Contents
Viewing Health LED Alarms 57
CHAPTER 7
Rack-Mount Server Hardware Management 59

Rack-Mount Server Management 60
Guidelines for Removing and Decommissioning Rack-Mount Servers 60
Recommendations for Avoiding Unexpected Server Power Changes 61
Booting a Rack-Mount Server 61
Determining the Boot Order of a Rack-Mount Server 62
Shutting Down a Rack-Mount Server 63
Resetting a Rack-Mount Server 64
Resetting a Rack-Mount Server to Factory Default Settings 65
Reacknowledging a Rack-Mount Server 65
Deleting the Inband Configuration from a Rack-Mount Server 66
Decommissioning a Rack-Mount Server 67
Recommissioning a Rack-Mount Server 67
Renumbering a Rack-Mount Server 67
Removing a Non-Existent Rack-Mount Server from the Configuration Database 68
Turning the Locator LED for a Rack-Mount Server On and Off 69
Turning the Local Disk Locator LED on a Rack-Mount Server On and Off 69
Resetting the CMOS for a Rack-Mount Server 70
Resetting the CIMC for a Rack-Mount Server 70
Clearing TPM for a Rack-Mount Server 70
Issuing an NMI from a Rack-Mount Server 71
Viewing Health Events for a Rack-Mount Server 71
Viewing the POST Results for a Rack-Mount Server 73
CHAPTER 8
Compute Cartridge Hardware Management 75

Compute Cartridges 75
Removing a Cartridge 75
Acknowledging a Cartridge Slot in a Chassis 76
CHAPTER 9
Modular Server Hardware Management 77

Modular Server Management 77

vi
Contents
Booting a Modular Server 78

Determining the Boot Order of a Modular Server 79
Shutting Down a Modular Server 79
Resetting a Modular Server 80
Reacknowledging a Modular Server 81
Deleting the Inband Configuration from a Modular Server 81
Decommissioning a Server 82
Recommissioning a Modular Server 83
Turning the Locator LED for a Server On and Off 83
Turning the Local Disk Locator LED on a Modular Server On and Off 83
Resetting the CMOS for a Modular Server 84
Resetting the CIMC for a Modular Server 84
Issuing an NMI from a Server 85
Viewing Health Events on a Server 85
Viewing the POST Results for a Modular Server 87
CHAPTER 10
C3X60 Server Node Hardware Management 89

Cisco UCS C3X60 Server Node Management 90
Booting a C3X60 Server Node 90
Booting a C3X60 Server Node from the Service Profile 90
Determining the Boot Order of a C3X60 Server Node 91
Shutting Down a C3X60 Server Node 91
Shutting Down a C3X60 Server Node from the Service Profile 92
Resetting a C3X60 Server Node 92
Resetting a C3X60 Server Node to Factory Default Settings 93
Reacknowledging a C3X60 Server Node 94
Removing a C3X60 Server Node from a Chassis 94
Deleting the Inband Configuration from a C3X60 Server Node 95
Decommissioning a C3X60 Server Node 95
Recommissioning a C3X60 Server Node 96
Reacknowledging a Server Slot in a C3260 Chassis 96

vii
Contents
Removing a Non-Existent C3X60 Server Node from the Configuration Database 97

Turning the Locator LED for a C3X60 Server Node On and Off 97
Turning the Local Disk Locator LED on a C3X60 Server Node On and Off 98
Resetting the CIMC for a C3X60 Server Node 98
Resetting the CMOS for a C3X60 Server Node 99
Issuing an NMI from a C3X60 Server Node 99
Viewing the POST Results for a C3X60 Server Node 100
Viewing Health Events for a C3X60 Server Node 100
CHAPTER 11
Server Pools 103

Configuring Server Pools 103
Server Pools 103
Creating a Server Pool 103
Deleting a Server Pool 104
Adding Servers to a Server Pool 105
Removing Servers from a Server Pool 105
Configuring UUID Suffix Pools 105
UUID Suffix Pools 105
Creating a UUID Suffix Pool 106
Deleting a UUID Suffix Pool 107
Configuring IP Pools 108
IP Pools 108
Creating an IP Pool 108
Adding a Block to an IP Pool 110
Deleting a Block from an IP Pool 112
Deleting an IP Pool 112
CHAPTER 12
Server Boot 113

Boot Policy 113
UEFI Boot Mode 114
UEFI Secure Boot 115
CIMC Secure Boot 115
Determining the CIMC Secure Boot Status 116

viii
Contents
Enabling CIMC Secure Boot on a Rack Server 116

Creating a Boot Policy 117
SAN Boot 118
Configuring a SAN Boot for a Boot Policy 118
iSCSI Boot 119
iSCSI Boot Process 120
iSCSI Boot Guidelines and Prerequisites 121
Initiator IQN Configuration 122
Enabling MPIO on Windows 123
Configuring iSCSI Boot 123
Creating an iSCSI Adapter Policy 124
Deleting an iSCSI Adapter Policy 126
Creating an iSCSI Authentication Profile 126
Deleting an iSCSI Authentication Profile 127
Creating an iSCSI Initiator IP Pool 128
Creating an iSCSI Boot Policy 129
Creating an iSCSI vNIC for a Service Profile 130
Deleting an iSCSI vNIC from a Service Profile 132
Setting the Initiator IQN at the Service Profile Level 132
Changing the Initiator IQN at the Service Profile Level 133
Setting iSCSI Boot Parameters 133
Modifying iSCSI Boot Parameters 137
IQN Pools 141
Creating an IQN Pool 141
Adding a Block to an IQN Pool 143
Deleting a Block from an IQN Pool 143
Deleting an IQN Pool 144
LAN Boot 144
Configuring a LAN Boot for a Boot Policy 145
Local Devices Boot 145
Configuring a Local Disk Boot for a Boot Policy 146
Configuring a Virtual Media Boot for a Boot Policy 147
Adding a Boot Policy to a vMedia Service Profile 148
Deleting a Boot Policy 150
UEFI Boot Parameters 150

ix
Contents
Guidelines and Limitations for UEFI Boot Parameters 151

Setting UEFI Boot Parameters 151
Modifying UEFI Boot Parameters 152
CHAPTER 13
Service Profiles 155

Service Profiles in UCS Manager 155
Service Profiles that Override Server Identity 156
Service Profiles that Inherit Server Identity 157
Guidelines and Recommendations for Service Profiles 157
Methods of Creating Service Profiles 158
Creating a Service Profile with the Expert Wizard 158
Creating a Service Profile that Inherits Server Identity 159
Creating a Hardware Based Service Profile for a Blade Server 159
Creating a Hardware Based Service Profile for a Rack-Mount Server 160
Inband Service Profiles 161
Deleting the Inband Configuration from a Service Profile 161
Service Profile Tasks 161
Renaming a Service Profile 161
Cloning a Service Profile 162
Changing the UUID in a Service Profile 163
Modifying the Boot Order in a Service Profile 164
Creating a vNIC for a Service Profile 166
Deleting a vNIC from a Service Profile 167
Creating a vHBA for a Service Profile 167
Changing the WWPN for a vHBA 168
Clearing Persistent Binding for a vHBA 168
Deleting a vHBA from a Service Profile 169
Adding a vHBA Initiator Group to a Service Profile 169
Deleting a Service Profile 171
Service Profile Association 171
Associating a Service Profile with a Server or Server Pool 171
Disassociating a Service Profile from a Server or Server Pool 172
Service Profile Templates 173
Initial and Existing Templates 173
Creating a Service Profile Template 174

x
Contents
Creating One or More Service Profiles from a Service Profile Template 175
Creating a Template Based Service Profile for a Blade Server 175
Creating a Template Based Service Profile for a Rack-Mount Server 176
Creating a Service Profile Template from a Service Profile 177
Service Profile Template Tasks 177
Binding a Service Profile to a Service Profile Template 177
Unbinding a Service Profile from a Service Profile Template 178
Changing the UUID in a Service Profile Template 178
Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile
Template 179
Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template 180
Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template 180
Deleting the Inband Configuration from a Service Profile Template 181
Service Profile Association 181
Associating a Service Profile with a Server or Server Pool 181
Associating a Service Profile Template with a Server Pool 182
Disassociating a Service Profile from a Server or Server Pool 183
Disassociating a Service Profile Template from its Server Pool 184
CHAPTER 14
Server-Related Policies 185

BIOS Settings 185
Server BIOS Settings 185
Main BIOS Settings 186
Processor BIOS Settings 188
Intel Directed I/O BIOS Settings 201
RAS Memory BIOS Settings 202
Serial Port BIOS Settings 205
USB BIOS Settings 205
PCI Configuration BIOS Settings 209
QPI BIOS Settings 211
LOM and PCIe Slots BIOS Settings 212
Graphics Configuration BIOS Settings 218
Boot Options BIOS Settings 219
Server Management BIOS Settings 221
BIOS Policy 226

xi
Contents
Default BIOS Settings 227

Creating a BIOS Policy 227
Modifying the BIOS Defaults 228
Viewing the Actual BIOS Settings for a Server 229
Trusted Platform Module 229
Trusted Platform Module 229
Intel Trusted Execution Technology 230
Configuring Trusted Platform 230
Configuring Trusted Platform 231
Clearing TPM for a Modular Server 232
Viewing TPM Properties 232
Consistent Device Naming 233
Guidelines and Limitations for Consistent Device Naming 233
Configuring Consistent Device Naming in a BIOS Policy 235
Configuring a CDN Name for a vNIC 236
CIMC Security Policies 236
IPMI Access Profile 237
Creating an IPMI Access Profile 237
Deleting an IPMI Access Profile 238
KVM Management Policy 239
Creating a KVM Management Policy 239
Local Disk Policies 239
Local Disk Configuration Policy 239
Guidelines for all Local Disk Configuration Policies 240
Guidelines for Local Disk Configuration Policies Configured for RAID 241
Creating a Local Disk Configuration Policy 243
Changing a Local Disk Configuration Policy 245
Deleting a Local Disk Configuration Policy 246
FlexFlash Support 247
FlexFlash FX3S Support 249
Starting Up Blade Servers with FlexFlash SD Cards 250
Enabling FlexFlash SD Card Support 251
Enabling Auto-Sync 251
Formatting the SD Cards 252
Resetting the FlexFlash Controller 252

xii
Contents
Scrub Policy 252

Scrub Policy Settings 252
Creating a Scrub Policy 254
Deleting a Scrub Policy 255
DIMM Error Management 255
DIMM Correctable Error Handling 255
Resetting Memory Errors 255
DIMM Blacklisting 256
Enabling DIMM Blacklisting 256
Serial over LAN Policy Settings 257
Serial over LAN Policy Overview 257
Creating a Serial over LAN Policy 257
Deleting a Serial over LAN Policy 258
Server Autoconfiguration Policies 258
Server Autoconfiguration Policy Overview 258
Creating an Autoconfiguration Policy 259
Deleting an Autoconfiguration Policy 260
Server Discovery Policy Settings 261
Server Discovery Policy Overview 261
Creating a Server Discovery Policy 261
Deleting a Server Discovery Policy 262
Server Inheritance Policy Settings 262
Server Inheritance Policy Overview 262
Creating a Server Inheritance Policy 263
Deleting a Server Inheritance Policy 264
Server Pool Policy Settings 264
Server Pool Policy Overview 264
Creating a Server Pool Policy 264
Deleting a Server Pool Policy 265
Server Pool Policy Qualifications Settings 265
Server Pool Policy Qualification Overview 265
Creating Server Pool Policy Qualifications 266
Deleting Server Pool Policy Qualifications 271
Deleting Qualifications from Server Pool Policy Qualifications 271
vNIC/vHBA Placement Policy Settings 272

xiii
Contents
vNIC/vHBA Placement Policies 272

vCon to Adapter Placement 273
vCon to Adapter Placement for N20-B6620-2 and N20-B6625-2 Blade Servers 273
vCon to Adapter Placement for All Other Supported Servers 273
vNIC/vHBA to vCon Assignment 274
Creating a vNIC/vHBA Placement Policy 276
Deleting a vNIC/vHBA Placement Policy 279
Explicitly Assigning a vNIC to a vCon 279
Explicitly Assigning a vHBA to a vCon 281
Placing Static vNICs Before Dynamic vNICs 282
vNIC/vHBA Host Port Placement 284
Configuring Host Port Placement 284
CIMC Mounted vMedia 285
Creating a vMedia Policy 286
Adding a vMedia Policy to a Service Profile 289
Viewing CIMC vMedia Policy 292
CHAPTER 15
Firmware Upgrades 293

Firmware Upgrades 293
Verifying Firmware Versions on Components 293

xiv
Preface
Audience, page xv
Conventions, page xv
Related Cisco UCS Documentation, page xvii
Documentation Feedback, page xvii
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-based User Interface, text the system displays appears in this font.
System output
Terminal sessions and information that the system displays appear in this
font.

xv
Preface
Conventions
Text Type
Indication
CLI commands
CLI command keywords appear in this font.

Variables in a CLI command appear in this font.
Note
Tip
[]
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.
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
document.
Means the following information will help you solve a problem. The tips information might not be
troubleshooting or even an action, but could be useful information, similar to a Timesaver.
Timesaver
Means the described action saves time. You can save time by performing the action described in the
paragraph.
Caution
Means reader be careful. In this situation, you might perform an action that could result in equipment
damage or loss of data.

xvi
Preface
Related Cisco UCS Documentation
Warning
IMPORTANT SAFETY INSTRUCTIONS

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

Documentation Roadmaps
For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap
available at the following URL: http://www.cisco.com/go/unifiedcomputing/b-series-doc.
For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap
available at the following URL: http://www.cisco.com/go/unifiedcomputing/c-series-doc.
For information on supported firmware versions and supported UCS Manager versions for the rack servers
that are integrated with the UCS Manager for management, refer to Release Bundle Contents for Cisco UCS
Software.
Other Documentation Resources
Follow Cisco UCS Docs on Twitter to receive document update notifications.
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments
to [email protected]. We appreciate your feedback.

xvii
Preface
Documentation Feedback

xviii
CHAPTER
New and Changed Information
New and Changed Information for this Release, page 1
New and Changed Information for this Release

The following table provides an overview of the significant changes to this guide for this current release. The
table does not provide an exhaustive list of all changes made to this guide or of all new features in this release.
Table 1: New Features and Changed Behavior in Cisco UCS Manager, Release 3.1(2)
Feature
Description
Where Documented
Updated Power Sync Policy
Cisco UCS Manager does not power

on the blade server after shallow
discovery when the power state for a
service profile is set to ON.
Power Sync Policy, on page

36

1
New and Changed Information

New and Changed Information for this Release

2
CHAPTER
Server Management Overview

Server Management Overview, page 3
Cisco UCS Manager User Documentation, page 3

Important
Cisco UCS Manager Release 3.1(2) and later releases do not support Cisco UCS M-Series Servers.
Cisco UCS Manager enables you to manage general and complex server deployments. For example, you can
manage a general deployment with a pair of Fabric Interconnects (FIs), which is the redundant server access
layer that you get with the first chassis that can scale up to 20 chassis' and up to 160 physical servers. This
can be a combination of blades and rack mount servers to support the workload in your environment. As you
add more servers, you can continue to perform server provisioning, device discovery, inventory, configuration,
diagnostics, monitoring, fault detection, and auditing.
By default, the Cisco UCS 6332 40 GB FIs, the UCS Mini 6324 40 GB FIs, and the UCS 6200 Series 10 GB
FIs include centralized management. You can manage the UCS Blade Servers, Rack-Mount Servers, and
M-Series Modular Servers that are in the same domain from one console. You can also manage the UCS Mini
from the Cisco UCS Manager.
To ensure the optimum server performance, you can configure the amount of power that you allocate to
servers. You can also set the server boot policy, the location from which the server boots, and the order in
which the boot devices are invoked. You can create service profiles for the UCS B-Series Blade Servers, UCS
M-Series Modular Servers, and the UCS Mini to assign to servers. Service profiles enable you to assign BIOS
settings, security settings, the number of vNICs and vHBAs, and anything else that you want to apply to a
server.
Cisco UCS Manager User Documentation

Cisco UCS Manager offers you a new set of smaller, use-case based documentation described in the following
table:

3

Cisco UCS Manager User Documentation
Guide
Description
Cisco UCS Manager Getting Started Guide
Discusses Cisco UCS architecture and Day 0

operations, including Cisco UCS Manager initial
configuration and configuration best practices.
Cisco UCS Manager Administration Guide
Discusses password management, role-based

access configuration, remote authentication,
communication services, CIMC session
management, organizations, backup and restore,
scheduling options, BIOS tokens, and deferred
deployments.
Cisco UCS Manager Infrastructure Management Guide Discusses physical and virtual infrastructure
components used and managed by Cisco UCS
Manager.
Cisco UCS Manager Firmware Management Guide
Discusses downloading and managing firmware,

upgrading through Auto Install, upgrading through
service profiles, directly upgrading at endpoints
using firmware auto sync, managing the capability
catalog, deployment scenarios, and
troubleshooting.
Cisco UCS Manager Server Management Guide
Discusses the new licenses, registering Cisco UCS

domain with Cisco UCS Central, power capping,
server boot, server profiles, and server-related
policies.
Cisco UCS Manager Storage Management Guide
Discusses all aspects of storage management, such

as SAN and VSAN in Cisco UCS Manager.
Cisco UCS Manager Network Management Guide
Discusses all aspects of network management,

such as LAN and VLAN connectivity in Cisco
UCS Manager.
Cisco UCS Manager System Monitoring Guide
Discusses all aspects of system and health

monitoring, including system statistics in Cisco
UCS Manager.

4
CHAPTER
Server License Management

Licenses, page 5
C-Direct Rack Licensing Support, page 7
Obtaining the Host ID for a Fabric Interconnect, page 8
Obtaining a License, page 8
Downloading Licenses to the Fabric Interconnect from the Local File System, page 9
Downloading Licenses to the Fabric Interconnect from a Remote Location, page 10
Installing a License, page 11
Viewing the Licenses Installed on a Fabric Interconnect, page 12
Determining the Grace Period Available for a Port or Feature, page 12
Determining the Expiry Date of a License, page 12
Uninstalling a License, page 13
Licenses
Each Cisco UCS fabric interconnect comes with several port licenses that are factory installed and shipped
with the hardware. You can purchase fabric interconnects fully licensed or partially licensed. You can also
purchase additional licenses after delivery.
The following four new licenses are added for the 6300 Series FI and are only valid on the 6332 and 6332-16UP
Fis.
40G_ETH_PORT_ACTIVATION_PKG Licenses used for 40 GB Ethernet ports
40G_ETH_C_PORT_ACTIVATION_PKG Licenses used for 40 GB Ethernet ports directly connected
to rack servers (C-Direct)
10G_C_PORT_ACTIVATION_PKG Licenses used for the first 16 10 GB unified ports on the
6332-16UP that are directly connected to rack servers (C-Direct)
10G_PORT_ACTIVATION_PKG Licenses used for the first 16 10 GB unified ports on the 6332-16UP

5

Licenses
Note
The 10G_PORT_ACTIVATION_PKG and 10G_C_PORT_ACTIVATION_PKG

licenses are only valid for the 6332-16UP FIs, and can only be installed on them.
At a minimum, each fabric interconnect ships with the following counted licenses pre-installed:
Fabric Interconnect
Default Base Licenses
Cisco UCS 6248 (unified ports)
For the 12 first enabled Ethernet ports and any Fibre

Channel ports in the expansion module.
Cisco UCS 6296 (unified ports)
For the first 18 enabled Ethernet ports and any Fibre

Channel ports in the expansion module.
Cisco UCS 6324
For 4 non-breakout ports only. The fifth port, which

does not include a license, is further broken in to four
10 GB ports.
Cisco UCS 6332 16UP
For four 40 GB ports and eight 10 GB ports.

Note
The first 16 ports are 10 GB. The remaining
are 40 GB.
Cisco UCS 6332
For eight 40 GB ports.
Port License Consumption

Port licenses are not bound to physical ports. When you disable a licensed port, that license is retained for
use with the next enabled port. To use additional fixed ports, you must purchase and install licenses for those
ports. All ports, regardless of their type (fibre, ethernet) consume licenses if they are enabled.
For breakout capable ports available in the 6332 and the 6332-16UP platforms, 40 GB licenses remain applied
to the main port even if that port is a breakout port, and that port continues to consume only one 40 GB license.
Note
The initial configuration of a port will enable it, and consume a license.
Important
Licenses are not portable across product generations. Licenses purchased for 6200 series fabric interconnects
cannot be used to enable ports on 6300 series fabric interconnects or vice-versa.
Each Cisco UCS 6324 Fabric Interconnect comes with a factory installed port license that is shipped with the
hardware. This license is for the eight 40 GB unified ports, and can be used for any supported purpose. The
C-direct port license is factory installed with a grace period, and can be used for Cisco UCS rack servers.
Grace Period
If you attempt to use a port that does not have an installed license, Cisco UCS initiates a 120 day grace period.
The grace period is measured from the first use of the port without a license and is paused when a valid license
file is installed. The amount of time used in the grace period is retained by the system.

6

C-Direct Rack Licensing Support
Note
Each physical port has its own grace period. Initiating the grace period on a single port does not initiate
the grace period for all ports.
If a licensed port is unconfigured, that license is transferred to a port functioning within a grace period. If
multiple ports are acting within grace periods, the license is moved to the port whose grace period is closest
to expiring.
High Availability Configurations
To avoid inconsistencies during failover, we recommend that both fabric interconnects in the cluster have the
same number of ports licensed. If symmetry is not maintained and failover occurs, Cisco UCS enables the
missing licenses and initiates the grace period for each port being used on the failover node.
C-Direct Rack Licensing Support

Each Cisco UCS fabric interconnect is shipped with a default number of port licenses that are factory licensed
and shipped with the hardware. C-direct support is only applicable on ports that are connected to the rack
servers. The 10G_C_PORT_ACTIVATION_PKG and the 40G_ETH_C_PORT_ACTIVATION _PKG are
added to the existing license package with all the same properties as the existing licensing feature. The
Subordinate Quantity property is added to the 10G_PORT_ACTIVATION_PKG and
40G_ETH_PORT_ACTIVATION_PKG to track ports connected to rack servers.
The License Tab in the Cisco UCS Manager GUI displays the new license and the Subordinate Quantity
for the license. You can also use the show feature and show usage commands under scope license to view
the license feature, the vendor version type, and the grace period for each license.
Ports connected to rack servers can use existing 10G_PORT_ACTIVATION_PKG and
40G_ETH_PORT_ACTIVATION_PKG if the license is available or if the license is not in use. Otherwise,
you must purchase a 10G_C_PORT_ACTIVATION_PKG and 40G_ETH_C_PORT_ACTIVATION to avoid
the license grace period.
There is no change in the 10 GB ports. The 10G_PORT_ACTIVATION_PKG and
10G_C_PORT_ACTIVATION_PKG license packages include all of the same properties as the existing the
ETH_PORT_ACTIVATION_PKG and the ETH_PORT_C_ACTIVATION_PKG license features.
Configuration and Restrictions
The C-Direct rack licensing feature accounts for the rack server ports that are directly connected to the
FI, but not to a CIMC port. The default quantity for the 10G_C_PORT_ACTIVATION_PKG and
40G_ETH_C_PORT_ACTIVATION_PKG is always 0.
When a 40 GB port, or a breakout port under a 40 GB breakout port is enabled without any connections,
this port is allotted a license under the 40G_ETH_PORT_ACTIVATION_PKG, if available. If this port
is connected to a Direct-Connect rack server after a time lag, it triggers a complete re-allocation of
licenses, then this port passes through one of the following license allocation scenarios occurs:
When you enable a breakout port under a 40 GB breakout port, if that port is connected to a
Direct-Connect rack server, and the 40G_C_PORT_ACTIVATION_PKG license files are installed on
the FI, the following license allocation occurs:

7

Obtaining the Host ID for a Fabric Interconnect
If no other ports under the breakout port are enabled, the parent 40 GB port is allotted a license
under the 40G_C_PORT_ACTIVATION_PKG, and the used quantity is incremented for this
instance.
If other ports are enabled, and if at least one port is not connected to a Direct Connect rack server,
even if the port is not being used, the parent 40 GB port is allotted a license under the
40G_ETH_PORT_ACTIVATION_PKG, and the used quantity is incremented for this instance.
When you enable a breakout port under a 40 GB breakout port and that port is connected to a
Direct-Connect rack server, and the 40G_C_PORT_ACTIVATION_PKG license files are not installed
on the FI, the following license allocation occurs:
If no ports under the breakout port are enabled, the parent 40 GB port is allotted a license under
the 40G_ETH_PORT_ACTIVATION_PKG. The subordinate quantity is increased if the licenses
are available in the 40G_ETH_PORT_ACTIVATION_PKG. If the licenses are not available, the
used quantity under this feature is increased and the entire port goes in to the grace period.
If other ports are enabled and at least one port is not connected to a Direct Connect rack server,
even if the port is not being used, the parent 40 GB port is allotted a license under the
40G_ETH_PORT_ACTIVATION_PKG, and the used quantity is incremented for this instance.
Obtaining the Host ID for a Fabric Interconnect

The host ID is also known as the serial number.
Procedure
Step 1
In the Navigation pane, click Equipment.
Step 2
Step 3
Step 4
Expand Equipment > Fabric Interconnects.

Click the node for the fabric interconnect for which you want to obtain the host ID.
In the Work pane, click the General tab.
Step 5
In the Properties area, the host ID is listed in the Serial Number (SN) field.
What to Do Next
Obtain the required licenses from Cisco.
Obtaining a License
Note
This process may change after the release of this document. If one or more of these steps no longer applies,
contact your Cisco representative for information on how to obtain a license file.

8

Downloading Licenses to the Fabric Interconnect from the Local File System
Before You Begin

Obtain the following:
Host ID or serial number for the fabric interconnect
Claim certificate or other proof of purchase document for the fabric interconnect or expansion module
Procedure
Step 1
Step 2
Step 3
Obtain the product authorization key (PAK) from the claim certificate or other proof of purchase document.
Locate the website URL in the claim certificate or proof of purchase document.
Access the website URL for the fabric interconnect and enter the serial number and the PAK.
Cisco sends you the license file by email. The license file is digitally signed to authorize use on only the
requested fabric interconnect. The requested features are also enabled once Cisco UCS Manager accesses the
license file.
What to Do Next
Install the license on the fabric interconnect.
Downloading Licenses to the Fabric Interconnect from the Local

File System
Note
In a cluster setup, Cisco recommends that you download and install licenses to both fabric interconnects
in matching pairs. An individual license is only downloaded to the fabric interconnect that is used to
initiate the download.
Before You Begin

Procedure
Step 1
In the Navigation pane, click Admin.
Step 2
Step 3
Step 4
Expand All > License Management.

Click the node for the fabric interconnect to which you want to download the license.
In the Work pane, click the Download Tasks tab.
Step 5
Step 6
Click Download License.

In the Download License dialog box, click the Local File System radio button in the Location of the Image
File field.
In the Filename field, type the full path and name of the license file.
Step 7

9

Downloading Licenses to the Fabric Interconnect from a Remote Location
You cannot have spaces anywhere in the path name or the file name. For example,
c:\Path\Folder_Name\License.lic is a valid path, but c:\Path\Folder Name\License.lic
is invalid due to the space in "Folder Name".
If you do not know the exact path to the folder where the license file is located, click Browse and navigate
to the file.
Step 8
Click OK.
Cisco UCS Manager GUI begins downloading the license to the fabric interconnect.
Step 9
(Optional) Monitor the status of the download on the Download Tasks tab.
Note
If Cisco UCS Manager reports that the bootflash is out of space, delete obsolete bundles on the
Packages tab to free up space. To view the available space in bootflash, navigate to the fabric
interconnect, click Equipment, and expand the Local Storage Information area on the General
tab.
Step 10 Repeat this task until all the required licenses have been downloaded to the fabric interconnect.
What to Do Next
After all of the download tasks complete, install the licenses.
Downloading Licenses to the Fabric Interconnect from a Remote

Location
Note
In a cluster setup, Cisco recommends that you download and install licenses to both fabric interconnects
in matching pairs. An individual license is only downloaded to the fabric interconnect that is used to
initiate the download.
Before You Begin

Procedure
Step 1
Step 2
Step 3
Step 4

Click the node for the fabric interconnect to which you want to download the license.
In the Work pane, click the Download Tasks tab.
Step 5
Step 6
Click Download License.

In the Download License dialog box, click the Remote File System radio button in the Location of the
Image File field.
Specify the protocol, and enter the required information.
Step 7

10

Installing a License
You cannot have spaces anywhere in the path name or the file name. For example,
c:\Path\Folder_Name\License.lic is a valid path, but c:\Path\Folder Name\License.lic
is invalid due to the space in "Folder Name".
If you use a hostname rather than an IPv4 or IPv6 address, you must configure a DNS server. If the
Cisco UCS domain is not registered with Cisco UCS Central or DNS management is set to local,
configure a DNS server in Cisco UCS Manager. If the Cisco UCS domain is registered with Cisco
UCS Central and DNS management is set to global, configure a DNS server in Cisco UCS Central.
Click OK.
Cisco UCS Manager GUI begins downloading the license to the fabric interconnect.
Note
Step 8
Step 9
(Optional) Monitor the status of the download on the Download Tasks tab.
Note
If Cisco UCS Manager reports that the bootflash is out of space, delete obsolete bundles on the
Packages tab to free up space. To view the available space in bootflash, navigate to the fabric
interconnect, click Equipment, and expand the Local Storage Information area on the General
tab.
Step 10 Repeat this task until all the required licenses have been downloaded to the fabric interconnect.
What to Do Next
After all of the download tasks complete, install the licenses.
Installing a License
Before You Begin
Procedure
Step 1
Step 2
Step 3

In the Work pane, click the Downloaded License Files tab.
Step 4
Choose the license you want to install from the table.

Note
There is no downtime required or impact to traffic when installing a new port license.
Step 5
Step 6
Click the Install License button.

In the Install License dialog box, click Yes.
Cisco UCS Manager GUI installs the license and activates the unlicensed port or feature.

11

Viewing the Licenses Installed on a Fabric Interconnect
Viewing the Licenses Installed on a Fabric Interconnect

Procedure
Step 1
Step 2
Step 3

In the Work pane, click the Installed Licenses tab to view the details of all licenses installed on the fabric
interconnect.
Click a license in the table to view the details of that license in the Contents tab.
You may need to expand the license file to view the details of individual licenses in the file.
Step 4
Determining the Grace Period Available for a Port or Feature

Procedure
Step 1
Step 2
Step 3

Step 4
Click a feature in the table to view details for that feature, including the operational state and used grace
period.
Determining the Expiry Date of a License

Procedure
Step 1
Step 2
Step 3

In the Work pane, click the Installed Licenses tab.
Step 4
Step 5
Step 6
Click a license in the table to view the details of that license in the Contents tab below.
In the Contents tab, expand the license file to view all licenses in the file.
In the Expiry column, view the expiry date of the license.

12

Uninstalling a License
Note
Permanent licenses cannot be uninstalled if they are in use. You can only uninstall a permanent license
that is not in use. If you try to delete a permanent license that is being used, Cisco UCS Manager rejects
the request and display an error message.
Before You Begin

Back up the Cisco UCS Manager configuration.
Procedure
Step 1
Step 2
Step 3

In the Work pane, click the Installed Licenses tab.
Step 4
Step 5
Step 6
Choose the license you want to uninstall from the table.

Click the Clear License button.
If a confirmation dialog box displays, click Yes.
Cisco UCS Manager deactivates the license, removes the license from the list of licenses, and deletes the
license from the fabric interconnect. The port is moved into unlicensed mode. In a cluster setup, you must
uninstall the license from the other fabric interconnect.

13


14
CHAPTER
Registering Cisco UCS Domains with Cisco UCS

Central
Registration of Cisco UCS Domains, page 15
Policy Resolution between Cisco UCS Manager and Cisco UCS Central, page 16
Registering a Cisco UCS Domain with Cisco UCS Central, page 17
Configuring Policy Resolutions between Cisco UCS Manager and Cisco UCS Central , page 18
Setting Cisco UCS Central Registration Properties in Cisco UCS Manager, page 19
Unregistering a Cisco UCS Domain from Cisco UCS Central, page 20
Registration of Cisco UCS Domains

You can have Cisco UCS Central manage some or all of the Cisco UCS domains in your data center.
If you want Cisco UCS Central to manage a Cisco UCS domain, you need to register that domain. When you
register, you must choose which types of policies and other configurations will be managed by Cisco UCS
Central and Cisco UCS Manager. Cisco UCS Central can manage the same types of policies and configurations
for all registered Cisco UCS domains. You can also choose to have different settings for each registered Cisco
UCS domain.
Perform the following before registering a Cisco UCS domain with Cisco UCS Central:
Configure an NTP server and the correct time zone in both Cisco UCS Manager and Cisco UCS Central
to ensure that they are in sync. If the time and date in the Cisco UCS domain and Cisco UCS Central
are out of sync, the registration might fail.
Obtain the hostname or IP address of Cisco UCS Central
Obtain the shared secret that was configured when Cisco UCS Central was deployed.

15
Registering Cisco UCS Domains with Cisco UCS Central

Policy Resolution between Cisco UCS Manager and Cisco UCS Central
Note
You cannot change or swap the IP addresses used by Cisco UCS Manager in a domain that is registered
with Cisco UCS Central. If you need to change or swap that IP address, you must first unregister the
domain from Cisco UCS Central. You can reregister the Cisco UCS domain after you have changed or
swapped the IP address.
Policy Resolution between Cisco UCS Manager and Cisco UCS

Central
For each Cisco UCS domain that you register with Cisco UCS Central, you can choose which application will
manage certain policies and configuration settings. This policy resolution does not have to be the same for
every Cisco UCS domain that you register with the same Cisco UCS Central.
You have the following options for resolving these policies and configuration settings:
LocalThe policy or configuration is determined and managed by Cisco UCS Manager.
GlobalThe policy or configuration is determined and managed by Cisco UCS Central.
The following table contains a list of the policies and configuration settings that you can choose to have
managed by either Cisco UCS Manager or Cisco UCS Central:
Name
Description
Infrastructure & Catalog

Firmware
Determines whether the Capability Catalog and infrastructure firmware

policy are defined locally or come from Cisco UCS Central.
Time Zone Management
Determines whether the date and time is defined locally or comes from
Cisco UCS Central.
Communication Services
Determines whether HTTP, CIM XML, Telnet, SNMP, web session

limits, and Management Interfaces Monitoring Policy settings are
defined locally or in Cisco UCS Central.
Global Fault Policy
Determines whether the Global Fault Policy is defined locally or in

Cisco UCS Central.
User Management
Determines whether authentication and native domains, LDAP,

RADIUS, TACACS+, trusted points, locales, and user roles are defined
locally or in Cisco UCS Central.
DNS Management
Determines whether DNS servers are defined locally or in Cisco UCS

Central.
Backup & Export Policies
Determines whether the Full State Backup Policy and All Configuration
Export Policy are defined locally or in Cisco UCS Central.

16

Registering a Cisco UCS Domain with Cisco UCS Central
Name
Description
Monitoring
Determines whether Call Home, Syslog, and TFTP Core Exporter

settings are defined locally or in Cisco UCS Central.
SEL Policy
Determines whether managed endpoints are defined locally or in Cisco

UCS Central.
Power Management
Determines whether the power management is defined locally or in

Cisco UCS Central.
Power Supply Unit
Determines whether power supply units are defined locally or in Cisco

UCS Central.
Registering a Cisco UCS Domain with Cisco UCS Central

Note
You cannot change or swap the IP addresses used by Cisco UCS Manager in a domain that is registered
with Cisco UCS Central. If you need to change or swap that IP address, you must first unregister the
domain from Cisco UCS Central. You can reregister the Cisco UCS domain after you have changed or
swapped the IP address.
Before You Begin

Configure an NTP server and the correct time zone in both Cisco UCS Manager and Cisco UCS Central to
ensure that they are in sync. If the time and date in the Cisco UCS domain and Cisco UCS Central are out of
sync, the registration might fail.
Procedure
Step 1
Step 2
Expand All > Communication Management.

Click the UCS Central node.
In the Actions area, click UCS Central.
In the Actions area, click Register With UCS Central.
In the Register with UCS Central dialog box, do the following:
a) Complete the following fields:
Step 3
Step 4
Step 5
Step 6

17

Configuring Policy Resolutions between Cisco UCS Manager and Cisco UCS Central
Name
Description
Hostname/IP Address field
The hostname or IP address of the virtual machine where Cisco UCS

Central is deployed.
Note
Shared Secret field
If you use a hostname rather than an IPv4 or IPv6 address,

you must configure a DNS server. If the Cisco UCS domain
is not registered with Cisco UCS Central or DNS
management is set to local, configure a DNS server in Cisco
UCS Manager. If the Cisco UCS domain is registered with
Cisco UCS Central and DNS management is set to global,
configure a DNS server in Cisco UCS Central.
The shared secret (or password) that was configured when Cisco UCS
Central was deployed.
b) In the Policy Resolution Control area, click one of the following radio buttons for each of the fields:
c) Click OK.
Configuring Policy Resolutions between Cisco UCS Manager

and Cisco UCS Central
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

In the Policy Resolution Control area, click one of the following radio buttons for each of the fields:
Step 6
Click Save Changes.

18

Setting Cisco UCS Central Registration Properties in Cisco UCS Manager
Setting Cisco UCS Central Registration Properties in Cisco UCS

Manager
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

In the Status area, complete the following as appropriate:
a) Click the radio button for the Cleanup Mode that you want to use.
This can be one of the following:
Localize GlobalWhen a Cisco UCS domain is unregistered, all global policies in the Cisco UCS
domain will be localized to Cisco UCS Manager. The policies remain in the Cisco UCS domain,
policy ownership is now local to Cisco UCS Manager, and Cisco UCS Manager admin users can
make changes.
Note
If you reregister the Cisco UCS domain with Cisco UCS Central, there can be policy conflicts
due to the policies existing both in Cisco UCS Central and in Cisco UCS Manager. Either
delete the local policies, or set the local policies to global before you try to create and
associate a global service profile.
Deep Remove GlobalThis option should only be used after careful consideration. When a Cisco
UCS domain is unregistered, all global policies in the Cisco UCS domain are removed. If there are
global service profiles, they will now refer to Cisco UCS Manager local default policies, and one of
the following occurs:
If there are local default policies present, the server will reboot.
If there are no local default policies, the service profile association fails with a configuration
error.
Note
The deep remove global cleanup mode does not remove global VSANs and VLANs when
you unregister from Cisco UCS Central. Those must be removed manually if desired.
b) Optionally check the Suspend State check box.

If checked, the Cisco UCS domain is temporarily removed from Cisco UCS Central, and all global policies
revert to their local counterparts. All service profiles maintain their current identities. However, global
pools are no longer visible and cannot be accessible by new service profiles.
c) Optionally check the Acknowledge State check box.
If the event ID stream that represents time and consistency between Cisco UCS Manager and Cisco UCS
Central becomes skewed or inconsistent, Cisco UCS Manager places itself in a Suspended State and
disconnects itself from Cisco UCS Central.
If you check this check box, you acknowledge that inconsistencies exist between Cisco UCS Manager
and Cisco UCS Central and are still willing to reconnect the Cisco UCS domain with Cisco UCS Central.

19

Unregistering a Cisco UCS Domain from Cisco UCS Central
Step 6
Click Save Changes.
Unregistering a Cisco UCS Domain from Cisco UCS Central

When you unregister a Cisco UCS domain from Cisco UCS Central, Cisco UCS Manager no longer receives
updates to global policies.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7

In the Actions area, click Unregister From UCS Central.
Click OK.
For more information on the impact of unregistering and registering a Cisco UCS Domain with Cisco UCS
Central, see Policy Resolution between Cisco UCS Manager and Cisco UCS Central.

20
CHAPTER
Power Capping in Cisco UCS and Power

Management for Blades
Power Capping in Cisco UCS, page 22
Power Policy Configuration, page 23
Power Policy for Cisco UCS Servers, page 23
Configuring the Power Policy, page 23
Power Supply for Redundancy Method, page 24
Configuring Policy Driven Chassis Group Power Capping, page 24
Policy Driven Chassis Group Power Capping, page 24
Power Control Policy, page 24
Power Groups in UCS Manager, page 27
Blade Level Power Capping, page 32
Manual Blade Level Power Cap, page 32
Setting the Blade-Level Power Cap for a Server, page 32
Viewing the Blade-Level Power Cap, page 33
Global Power Profiling Policy Configuration, page 34
Global Power Profiling Policy, page 34
Configuring the Global Power Profile Policy, page 34
Global Power Allocation Policy Configuration, page 35
Global Power Allocation Policy, page 35
Configuring the Global Power Allocation Policy, page 35
Power Management During Power-on Operations, page 35
Power Sync Policy Configuration, page 36
Power Sync Policy, page 36

21
Power Capping in Cisco UCS and Power Management for Blades

Power Capping in Cisco UCS
Power Synchronization Behavior, page 37

Creating a Power Sync Policy, page 37
Changing a Power Sync Policy, page 39
Deleting a Power Sync Policy, page 39
Rack Server Power Management, page 40
UCS Mini Power Management , page 40
Power Capping in Cisco UCS

You can control the maximum power consumption on a server through power capping, as well as manage the
power allocation in the Cisco UCS Manager for the UCS B-Series Blade Servers, UCS Mini, and mixed UCS
domains.
UCS Manager supports power capping on the following servers:
UCS Mini 6324
UCS 6300 Series Fabric Interconnects
You can use Policy Driven Chassis Group Power Cap, or Manual Blade Level Power Cap methods to allocate
power that applies to all of the servers in a chassis.
Cisco UCS Manager provides the following power management policies to help you allocate power to your
servers:
Power Management Policies
Description
Power Policy
Specifies the redundancy for power supplies in all

chassis in a Cisco UCS domain.
Power Control Policies
Specifies the priority to calculate the initial power

allocation for each blade in a chassis.
Global Power Allocation
Specifies the Policy Driven Chassis Group Power

Cap or the Manual Blade Level Power Cap to apply
to all servers in a chassis.
Global Power Profiling
Specifies how the power cap values of the servers are

calculated. If it is enabled, the servers will be profiled
during discovery through benchmarking. This policy
applies when the Global Power Allocation Policy is
set to Policy Driven Chassis Group Cap.

22

Power Policy Configuration
Power Policy Configuration

Power Policy for Cisco UCS Servers
The power policy is global and is inherited by all of the chassis' managed by the Cisco UCS Manager instance.
You can add the power policy to a service profile to specify the redundancy for power supplies in all chassis'
in the Cisco UCS domain. This policy is also known as the PSU policy.
For more information about power supply redundancy, see Cisco UCS 5108 Server Chassis Hardware
Installation Guide.
Configuring the Power Policy

Procedure
Step 1
Step 2
Step 3
Click the Equipment node.

In the Work pane, click the Policies tab.
Step 4
Step 5
Click the Global Policies subtab.

In the Power Policy area, click one of the following radio buttons in the Redundancy field:
Non RedundantCisco UCS Manager turns on the minimum number of power supplies (PSUs) needed
and balances the load between them. If any additional PSUs are installed, Cisco UCS Manager sets them
to a "turned-off" state. If the power to any PSU is disrupted, the system may experience an interruption
in service until Cisco UCS Manager can activate a new PSU and rebalance the load.
In general, a Cisco UCS chassis requires at least two PSUs for non redundant operation. Only smaller
configurations (requiring less than 2500W) can be powered by a single PSU.
N+1The total number of PSUs to satisfy non-redundancy, plus one additional PSU for redundancy,
are turned on and equally share the power load for the chassis. If any additional PSUs are installed, Cisco
UCS Manager sets them to a "turned-off" state. If the power to any PSU is disrupted, Cisco UCS Manager
can recover without an interruption in service.
In general, a Cisco UCS chassis requires at least three PSUs for N+1 operation.
GridTwo power sources are turned on, or the chassis requires greater than N+1 redundancy. If one
source fails (which causes a loss of power to one or two PSUs), the surviving PSUs on the other power
circuit continue to provide power to the chassis.
For more information about power supply redundancy, see Cisco UCS 5108 Server Chassis Hardware
Installation Guide.
Step 6
Click Save Changes.

23

Power Supply for Redundancy Method
Power Supply for Redundancy Method

PSU Redundancy
Max Power @ 220 V (Watts)
Max Power @ 110 V (Watts)
1+1 (N+1) OR 1 (N)
2500
1300
2+1 (N+1) OR 2 (N) or 2+2 (Grid) 5000
2600
3+1 (N+1) OR 3 (N)
5472
3900
4 (N)
5472
5200
Configuring Policy Driven Chassis Group Power Capping

Policy Driven Chassis Group Power Capping
When you select the Policy Driven Chassis Group Power Cap in the Global Cap Policy, Cisco UCS can
maintain the over-subscription of servers without risking power failures. You can achieve over-subscription
through a two-tier process. For example, at the chassis level, Cisco UCS divides the amount of power available
among members of the power group, and at the blade level, the amount of power allotted to a chassis is divided
among blades based on priority.
Each time a service profile is associated or disassociated, Cisco UCS Manager recalculates the power allotment
for each blade server within the chassis. If necessary, power from lower-priority service profiles is redistributed
to higher-priority service profiles.
UCS power groups cap power in less than one second to safely protect data center circuit breakers. A blade
must stay at its cap for 20 seconds before the chassis power distribution is optimized. This is intentionally
carried out over a slower timescale to prevent reacting to transient spikes in demand.
Note
The system reserves enough power to boot a server in each slot, even if that slot is empty. This reserved
power cannot be leveraged by servers requiring more power. Blades that fail to comply with the power
cap are penalized.
Power Control Policy

Cisco UCS uses the priority set in the power control policy along with the blade type and configuration to
calculate the initial power allocation for each blade within a chassis. During normal operation, the active
blades within a chassis can borrow power from idle blades within the same chassis. If all blades are active
and reach the power cap, service profiles with higher priority power control policies take precedence over
service profiles with lower priority power control policies.

24

Creating a Power Control Policy
Priority is ranked on a scale of 1-10, where 1 indicates the highest priority and 10 indicates lowest priority.
The default priority is 5.
For mission-critical application a special priority called no-cap is also available. Setting the priority to no-cap
prevents Cisco UCS from leveraging unused power from a particular server. With this setting, the server is
allocated the maximum amount of power possible for that type of server.
Note
You must include the power control policy in a service profile and that service profile must be associated
with a server for it to take effect.

Procedure
Step 1
In the Navigation pane, click Servers.
Step 2
Step 3
Expand Servers > Policies.

Expand the node for the organization where you want to create the policy.
If the system does not include multitenancy, expand the root node.
Step 4
Step 5
Right-click Power Control Policies and choose Create Power Control Policy.
In the Create Power Control Policy dialog box, complete the following fields:
Name
Description
Name field
The name of the policy.

This name can be between 1 and 16 alphanumeric
characters. You cannot use spaces or any special
characters other than - (hyphen), _ (underscore), :
(colon), and . (period), and you cannot change this
name after the object is saved.
Description field
A description of the policy. Cisco recommends

including information about where and when to use
the policy.
Enter up to 256 characters. You can use any
characters or spaces except ` (accent mark), \
(backslash), ^ (carat), " (double quote), = (equal sign),
> (greater than), < (less than), or ' (single quote).

25

Name
Description
Fan Speed Policy drop-down
Fan speed is for rack servers only. This can be one

of the following:
Low PowerThe fan runs at the minimum
speed required to keep the server cool.
BalancedThe fan runs faster when needed
based on the heat generated by the server. When
possible, the fan returns to the minium required
speed.
PerformanceThe fan is kept at the speed
needed for better server performance. This
draws more power but means the fan is already
at speed if the server begins to heat up.
High PowerThe fan is kept at an even higher
speed that emphasizes performance over power
consumption.
Max PowerThe fan is kept at the maximum
speed at all times. This option provides the most
cooling and uses the most power.
AnyThe server determines the optimal fan
speed.
Power Capping field
What happens to a server when the demand for power

within a power group exceeds the power supply. This
can be one of the following:
No CapThe server runs at full capacity
regardless of the power requirements of the
other servers in its power group.
capThe server is allocated a minimum amount
of power capacity based on the the server's
priority relative to the other servers in its server
group. If more power becomes available, Cisco
UCS allows the capped servers to exceed their
original allocations. It only lowers the
allocations if there is a drop in the total power
available to the power group.
When you select cap, Cisco UCS Manager GUI
displays the Priority field.
Priority field
The priority the server has within its power group

when power capping is in effect.
Enter an integer between 1 and 10, where 1 is the
highest priority.

26

Deleting a Power Control Policy
Step 6
Click OK.
What to Do Next
Include the policy in a service profile or service profile template.
Deleting a Power Control Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Expand Servers > Policies > Organization_Name.

Expand the Power Control Policies node.
Right-click the policy you want to delete and select Delete.
Power Groups in UCS Manager

A power group is a set of chassis that all draw power from the same power distribution unit (PDU). In Cisco
UCS Manager, you can create power groups that include one or more chassis, then set a peak power cap in
AC watts for that power grouping.
Implementing power capping at the chassis level requires the following:
IOM, CIMC, and BIOS version 1.4 or higher
Two Power Supply Units (PSUs)
The peak power cap is a static value that represents the maximum power available to all blade servers within
a given power group. If you add or remove a blade from a power group, but do not manually modify the peak
power value, the power group adjusts the peak power cap to accommodate the basic power-on requirements
of all blades within that power group.
A minimum of 890 AC watts should be set for each chassis. This converts to 800 watts of DC power, which
is the minimum amount of power required to power an empty chassis. To associate a half-width blade, the
group cap needs to be set to 1475 AC watts. For a full-width blade, it needs to be set to 2060 AC watts.
After a chassis is added to a power group, all service profile associated with the blades in the chassis become
part of that power group. Similarly, if you add a new blade to a chassis, that blade inherently becomes part
of the chassis' power group.

27

Power Groups in UCS Manager
Note
Creating a power group is not the same as creating a server pool. However, you can populate a server pool
with members of the same power group by creating a power qualifier and adding it to server pool policy.
When a chassis is removed or deleted, the chassis gets removed from the power group.
UCS Manager supports explicit and implicit power groups.
Explicit: You can create a power group, add chassis' and racks, and assign a budget for the group.
Implicit: Ensures that the chassis is always protected by limiting the power consumption within safe
limits. By default, all chassis that are not part of an explicit power group are assigned to the default
group and the appropriate caps are placed. New chassis that connect to UCS Manager are added to the
default power group until you move them to a different power group.
The following table describes the error messages you might encounter while assigning power budget and
working with power groups.
Error Message
Cause
Insufficient budget for One of these messages displays if

you did not meet the minimum
power group
limit when assigning the power cap
POWERGROUP_NAME
for a chassis, or the power
and/or
requirement increased because of
Chassis N cannot be
the addition of blades or change of
capped as group cap is
power policies.
low. Please consider
raising the cap.
and/or
Recommended Action
Increase the power cap limit to the
Minimum Power Cap for
Allowing Operations (W) value
displayed on the Power Group
page for the specified power group.
Admin committed
insufficient for power
group GROUP_NAME, using
previous value N
and/or
Power cap application
failed for chassis N
Chassis N cannot be
capped as the available
PSU power is not enough
for the chassis and the
blades. Please correct
the problem by checking
input power or replace
the PSU
Displays when the power budget

requirement for the chassis is more
than the PSU power that is
available.
Power cap application

failed for server N
Displays when the server is

Do not power on un-associated
consuming more power than
servers.
allocated and cannot be capped, or
the server is powered on when no
power is allocated.
If a PSU failed, replace the PSU.

28
Check the PSU input power and

redundancy policy to ensure that
enough power is available for the
chassis.

Creating a Power Group
Error Message
Cause
Recommended Action
P-State lowered as
consumption hit power
cap for server
Displays when the server is capped This is an information message.

to reduce the power consumption If a server should not be capped, in
below the allocated power.
the service profile set the value of
the power control policy Power
Capping field to no-cap.
Chassis N has a mix of

high-line and low-line
PSU input power
sources.
This fault is raised when a chassis This is an unsupported

has a mix of high-line and low-line configuration. All PSUs must be
PSU input sources connected.
connected to similar power sources.

Before You Begin
Make sure that the global power allocation policy is set to Policy Driven Chassis Group Cap on the Global
Policies tab.
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Click the Power Groups subtab.

On the icon bar to the right of the table, click +.
If the + icon is disabled, click an entry in the table to enable it.
Step 6
On the first page of the Create Power Group wizard, complete the following fields:
a) Enter a unique name and description for the power group.
This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special
characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name
after the object is saved.
b) Click Next.
Step 7
On the Add Chassis Members page of the Create Power Group wizard, do the following:
a) In the Chassis table, choose one or more chassis to include in the power group.
b) Click the >> button to add the chassis to the Selected Chassis table that displays all chassis included in
the power group.
You can use the << button to remove one or more chassis from the power group.
c) Click Next.
Step 8
On the Add Rack Members page of the Create Power Group wizard, do the following:
a) In the Rack Unit table, choose one or more rack units to include in the power group.

29

b) Click the >> button to add the rack to the Selected Rack Unit table that displays all racks included in the
power group.
You can use the << button to remove one or more rack units from the power group.
c) Click Next.
Step 9
On the Add FEX Members page of the Create Power Group wizard, do the following:
a) In the FEX table, choose one or more FEX to include in the power group.
b) Click the >> button to add the chassis to the Selected FEX table that displays all FEX included in the
power group.
You can use the << button to remove one or more FEX from the power group.
c) Click Next.
Step 10 On the Add FI Members page of the Create Power Group wizard, do the following:
a) In the FI table, choose one or more FI to include in the power group.
b) Click the >> button to add the FI to the Selected FI table that displays all chassis included in the power
group.
You can use the << button to remove one or more FI from the power group.
c) Click Next.
Step 11 On the Power Group Attributes page of the Create Power Group wizard, do the following:
Name
Description
Power Cap field
The maximum peak power (in watts) available to the power group.
Enter an integer between 0 and 10000000.
Enable Dynamic Reallocation

field

ChassisCisco UCS monitors power usage and changes the
blade allocations as required to maximize power utilization.
NoneBlade allocations are not adjusted dynamically.
b) Click Finish.

30

Adding a Chassis to a Power Group
Adding a Chassis to a Power Group

Procedure
Step 1
Step 2
Step 3

In the Work pane, click the Power Groups tab.
Step 4
Step 5
Right-click the power group to which you want to add a chassis and choose Add Chassis Members.
In the Add Chassis Members dialog box, do the following:
a) In the Chassis table, choose one or more chassis to include in the power group.
b) Click the >> button to add the chassis to the Selected Chassis table that displays all chassis included in
the power group.
You can use the << button to remove one or more chassis from the power group.
c) Click OK.
Removing a Chassis from a Power Group

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Step 6
Expand the power group from which you want to remove a chassis.
Right-click the chassis that you want to remove from the power group and choose Delete.

31

Deleting a Power Group
Deleting a Power Group

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click the power group that you want to delete and choose Delete.
Blade Level Power Capping

Manual Blade Level Power Cap
When manual blade-level power cap is configured in the global cap policy, you can set a power cap for each
blade server in a Cisco UCS domain.
The following configuration options are available:
WattsYou can specify the maximum amount of power that the server can consume at one time. This
maximum can be any amount between 0 watts and 1100 watts.
UnboundedNo power usage limitations are imposed on the server. The server can use as much power
as it requires.
If the server encounters a spike in power usage that meets or exceeds the maximum configured for the server,
Cisco UCS Manager does not disconnect or shut down the server. Instead, Cisco UCS Manager reduces the
power that is made available to the server. This reduction can slow down the server, including a reduction in
CPU speed.
Note
If you configure the manual blade-level power cap using Equipment > Policies > Global Policies >
Global Power Allocation Policy, the priority set in the Power Control Policy is no longer relevant.
Setting the Blade-Level Power Cap for a Server

Before You Begin
Make sure the global power allocation policy is set to Manual Blade Level Cap on the Global Policies tab.

32

Viewing the Blade-Level Power Cap
Procedure
Step 1
Step 2
Step 3
Step 4
Expand Equipment > Chassis > Chassis Number > Servers.

Choose the server for which you want to set the power budget.
Step 5
In the Power Budget area, do the following:

a) Click the Expand icon to the right of the heading to display the fields.
b) Complete the following fields:
Name
Description
Admin Status field
Whether this server is power capped. This can be one of the following:
UnboundedThe server is not power capped under any
circumstances.
EnabledThe Cisco UCS Manager GUI displays the Watts
field.
Note
Watts field
Power capping goes into effect only if there is insufficient

power available to the chassis to meet the demand. If there
is sufficient power, the server can use as many watts as it
requires.
The maximum number of watts that the server can use if there is not
enough power to the chassis to meet the demand.
The value range is from 0 and 10000000.
Step 6
Click Save Changes.
Viewing the Blade-Level Power Cap

Procedure
Step 1
Step 2
Step 3
Step 4
Expand Equipment > Chassis.

Choose the chassis for which you want to view the server power usage.
Do one of the following:
To view the power usage for all servers in the chassis, click the Power tab in the Work pane.

33

Global Power Profiling Policy Configuration
To view the power usage for one server in the chassis, expand the chassis and click the server. Then
click the Power tab in the Work pane.
Step 5
If necessary, expand the Motherboards node to view the power counters.
Global Power Profiling Policy Configuration

Global Power Profiling Policy
The Global Power Profiling Policy specifies how power allocation is applied to all of the servers in a chassis.
The policy applies when you set the Global Power Allocation Policy to Policy Driven Chassis Group Cap.
You can set the Global Power Profiling Policy to one of the following:
DisabledThe minimum and maximum power cap values of the blades are calculated based on the
static power consumption values of each of the components.
EnabledThe minimum and maximum power cap values of the blades are measured as part of the
server discovery. These values are similar to the actual power consumption of the blades.
Note
After enabling the Global Power Profiling Policy, you must re-acknowledge the blades to obtain the
minimum and maximum power cap.
Important
Power profiling is not supported in Cisco UCS B460 M4 blades.
Configuring the Global Power Profile Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5

In the Global Power Profiling Policy area, check the Profile Power checkbox to enable the Global Power
Profiling Policy.
Click Save Changes.
Step 6

34

Global Power Allocation Policy Configuration
Global Power Allocation Policy Configuration

Global Power Allocation Policy
The Global Power Allocation Policy allows you to specify the Policy Driven Chassis Group Power Cap or
Manual Blade-level Power Cap power allocation method applied to servers in a chassis.
Cisco recommends using the default Policy Driven Chassis Group Power Cap power allocation method.
Important
Any change to the Manual Blade level Power Cap configuration results in the loss of any groups or
configuration options set for the Policy Driven Chassis Group Power Cap.
Configuring the Global Power Allocation Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5

In the Global Power Allocation Policy area, click one of the following radio buttons in the Allocation Method
field to determine the power cap management mode used in the Cisco UCS domain:
Manual Blade Level CapPower allocation is configured on each individual blade server in all chassis.
If you select this option, you cannot create power groups.
Policy Driven Chassis Group CapPower allocation is configured at the chassis level through power
control policies included in the associated service profiles. If you select this option, you can also create
power groups that contain one or more chassis in the Cisco UCS domain.
By default, power allocation is done for each chassis through a power control policy.
Step 6
Click Save Changes.
Power Management During Power-on Operations

Boot Staggering during Power on
Cisco UCS Manager attempts to boot as many blades as possible based on the amount of available power. If
the power required to boot a blade is not available, Cisco UCS Manager staggers the boot in the Finite State

35

Power Sync Policy Configuration
Machine (FSM) CheckPowerAvailability stage, and raises the following fault on the blade: Insufficient power
available to power-on server x/y.
When the required power becomes available, the FSM proceeds with blade power on. After a blade powers
off, the allocated power budget is reclaimed.
Note
When the power budget that was allocated to the blade is reclaimed, the allocated power displays as 0
Watts.
Limitation
If you power on a blade outside of the Cisco UCS Manager, it does not allocate any power budget to the blade,
and raises the following fault: Power cap application failed for server x/y.
Power Allocation during Service Profile Association
The power allocated to a blade during service profile association depends on the Power Control Policy used,
and the power that is available from the power group. After the power is allocated to a server during a successful
service profile association, the blade is guaranteed the minimum power cap. If the Power Control Policy
priority is set to no-cap, a blade is allocated a potential maximum power cap, which might exceed the measured
maximum power cap that displays.
Note
If the priority of an associated blade is changed to no-cap, and is not able to allocate the maximum power
cap, you might see one of the following faults:
PSU-insufficientThere is not enough available power for the PSU.
Group-cap-insufficientThe group cap value is not sufficient for the blade.
Power Sync Policy Configuration

Power Sync Policy
Cisco UCS Manager includes a global (default) power sync policy to address power synchronization issues
between the associated service profiles and the servers. You can use the power sync policy to synchronize
the power state when the power state of the service profile differs from the actual power state of the server.
The policy allows you to control when to synchronize the power state on the associated service profiles for
the servers. The power sync policy does not affect other power-related policies.
The power synchronization policy applies to all the service profiles by default. You cannot delete the default
power sync policy, but you can edit the default policy. You can create your own power sync policies and
apply them to the service profiles. You can also create a power sync policy that is specific to a service profile
and it always takes precedence over the default policy.
Cisco UCS Manager creates a fault on the associated service profile when the power sync policy referenced
in the service profile does not exist. Cisco UCS Manager automatically clears the fault once you create a
power sync policy for the specified service profile or change the reference to an existing policy in the service
profile.

36

Power Synchronization Behavior
Power Synchronization Behavior

Cisco UCS Manager synchronizes the power state only when the actual power state of the server is OFF. The
current power synchronization behavior is based on the actual power state and the preferred power state after
shallow association occurs.
For example, the following events trigger shallow association:
Fabric Interconnects(FI) and IOM disconnected.
IOM reset
FI power loss or reboot
Chassis reacknowledgment
Chassis power loss
Service profile change
The following table describes the current power synchronization behavior:
Event
Preferred Power State
Actual Power State

Before Event
Actual Power State After

Event
Shallow Association
ON
OFF
ON
Shallow Association
OFF
OFF
OFF
Shallow Association
ON
ON
ON
Shallow Association
OFF
ON
ON
Creating a Power Sync Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click Power Sync Policies and choose Create Power Sync Policy.
In the Create Power Sync Policy dialog box, complete the following fields:

37

Creating a Power Sync Policy
Name
Description
Name field

Description field

the policy.
Sync-Option field
The options that allow you to synchronize the desired

power state of the associated service profile to the
physical server. This can be one of the following:
Default SyncAfter the initial server
association, any configuration change or
management connectivity changes that you
perform trigger a server reassociation. This
option synchronizes the desired power state to
the physical server if the physical server power
state is off and the desired power state is on.
This is the default behavior.
Always SyncWhen the initial server
association or the server reassociation occurs,
this option synchronizes the desired power state
to the physical power state, even if the physical
server power state is on and desired power state
is off.
Initial Only SyncThis option only
synchronizes the power to a server when a
service profile is associated to the server for the
first time, or when the server is
re-commissioned. When you set this option,
resetting the power state from the physical
server side does not affect the desired power
state on the service profile.
Step 6
Click OK.

38

Changing a Power Sync Policy
What to Do Next
Include the policy in a service profile or service profile template.
Changing a Power Sync Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Step 6
Choose a service profile policy from the root node.

Click the Change Power Sync Policy from the Actions area.
The information displayed depends on what you choose in the Select the Power Sync Policy drop-down list.
You can choose:
No Power Sync PolicyIf you choose this option, Cisco UCS Manager GUI does not display any other
information. When you choose this option, Cisco UCS Manager implicitly uses the default power sync
policy. Cisco UCS Manager searches for the default power sync policy under service profile organizations.
If the policy is not found, then it uses the default power sync policy under root.
Use an Existing Power Sync Policyif you want to select a global policy. Cisco UCS Manager GUI
displays the Power Sync Policy drop-down list that enables you to choose an existing policy.
Create a Local Power Sync Policyif you want to create a power sync policy that can only be accessed
by this service profile. You can also create a power sync policy by using the Create Power Sync Policy
link from the Power Sync Policy area.
Deleting a Power Sync Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the Power Sync Policies node.

39

Rack Server Power Management
Rack Server Power Management

Power capping is not supported for rack servers.
UCS Mini Power Management

You can manage power of the blade servers in 6324 Fabric Interconnect (FI), which is used for remote offices
and branch sites, and for limited server deployments. UCS Manager supports Dual Line Power Supply Unit
and 110V when used with the 6324 Fabric Interconnect. You can manager how you want to allocate power
when using 110V power supplies, because they might not provide enough power for a fully loaded chassis.
Dual power supplies is standard for both AC and DC-48V on the UCS Mini 6324.

40
CHAPTER
Blade Server Hardware Management

Blade Server Management, page 42
Booting a Blade Server, page 43
Booting a Rack-Mount Server from the Service Profile , page 44
Determining the Boot Order of a Blade Server, page 44
Shutting Down a Blade Server, page 45
Shutting Down a Server from the Service Profile , page 45
Resetting a Blade Server, page 46
Resetting a Blade Server to Factory Default Settings, page 47
Reacknowledging a Blade Server, page 48
Removing a Server from a Chassis, page 48
Deleting the Inband Configuration from a Blade Server, page 49
Decommissioning a Blade Server, page 49
Recommissioning a Blade Server, page 50
Reacknowledging a Server Slot in a Chassis, page 50
Removing a Non-Existent Blade Server from the Configuration Database, page 51
Turning the Locator LED for a Blade Server On and Off, page 51
Turning the Local Disk Locator LED on a Blade Server On and Off, page 52
Resetting the CMOS for a Blade Server, page 52
Resetting the CIMC for a Blade Server, page 53
Clearing TPM for a Blade Server, page 53
Viewing the POST Results for a Blade Server, page 54
Issuing an NMI from a Blade Server, page 54
Viewing Health Events for a Blade Server, page 55
Health LED Alarms, page 57

41

Blade Server Management
Blade Server Management

You can manage and monitor all blade servers in a Cisco UCS domain through Cisco UCS Manager. You
can perform some blade server management tasks, such as changes to the power state, from the server and
service profile.
The remaining management tasks can only be performed on the server.
The power supply units go into power save mode when a chassis has two blades or less. When a third blade
is added to the chassis and is fully discovered, the power supply units return to regular mode.
If a blade server slot in a chassis is empty, Cisco UCS Manager provides information, errors, and faults for
that slot. You can also re-acknowledge the slot to resolve server mismatch errors and to have Cisco UCS
Manager rediscover the blade server in the slot.
Guidelines for Removing and Decommissioning Blade Servers

Consider the following guidelines when deciding whether to remove or decommission a blade server using
Cisco UCS Manager:
Decommissioning a Blade Server
If you want to temporarily decommission a physically present and connected blade server, you can temporarily
remove it from the configuration. A portion of the server's information is retained by Cisco UCS Manager
for future use, in case the blade server is recommissioned.
Removing a Blade Server
Removing is performed when you physically remove a blade server from the Cisco UCS Manager by
disconnecting it from the chassis. You cannot remove a blade server from Cisco UCS Manager if it is physically
present and connected to a chassis. After the physical removal of the blade server is completed, the configuration
for that blade server can be removed in Cisco UCS Manager.
During removal, active links to the blade server are disabled, all entries from databases are removed, and the
server is automatically removed from any server pools that it was assigned to during discovery.
Note
Only servers added to a server pool automatically during discovery are removed automatically. Servers
that were manually added to a server pool must be removed manually.
To add a removed blade server back to the configuration, it must be reconnected, then rediscovered. When a
server is reintroduced to Cisco UCS Manager, it is treated as a new server and is subject to the deep discovery
process. For this reason, it is possible for Cisco UCS Manager to assign the server a new ID that might be
different from the ID that it held before.
Recommendations for Avoiding Unexpected Server Power Changes

If a server is not associated with a service profile, you can use any available means to change the server power
state, including the physical Power or Reset buttons on the server.

42

Booting a Blade Server
If a server is associated with, or assigned to, a service profile, you should only use the following methods to
change the server power state:
In Cisco UCS Manager GUI, go to the General tab for the server or the service profile associated with
the server and select Boot Server or Shutdown Server from the Actions area.
In Cisco UCS Manager CLI, scope to the server or the service profile associated with the server and use
the power up or power down commands.
Important
Do not use any of the following options on an associated server that is currently powered off:
Reset in the GUI
cycle cycle-immediate or reset hard-reset-immediate in the CLI
The physical Power or Reset buttons on the server
If you reset, cycle, or use the physical power buttons on a server that is currently powered off, the server's
actual power state might become out of sync with the desired power state setting in the service profile. If the
communication between the server and Cisco UCS Manager is disrupted or if the service profile configuration
changes, Cisco UCS Manager might apply the desired power state from the service profile to the server,
causing an unexpected power change.
Power synchronization issues can lead to an unexpected server restart, as shown below:
Desired Power State in Service
Profile
Current Server Power State
Server Power State After

Communication Is Disrupted
Up
Powered Off
Powered On
Down
Powered On
Powered On
Note
Running servers are not

shut down regardless of
the desired power state in
the service profile.
Booting a Blade Server

If the Boot Server link is dimmed in the Actions area, you must shut down the server first.

43

Booting a Rack-Mount Server from the Service Profile
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server that you want to boot.
Step 5
Step 6
In the Actions area, click Boot Server.

After the server boots, the Overall Status field on the General tab displays an OK status.

Procedure
Step 1
Step 2
Step 3
Expand Servers > Service Profiles.

Expand the node for the organization where you want to create the service profile.
Step 4
Step 5
Choose the service profile that requires the associated server to boot.
Step 6
Step 7
Step 8

Click OK in the Boot Server dialog box.
After the server boots, the Overall Status field on the General tab displays an ok status or an up status.
Determining the Boot Order of a Blade Server

Tip
You can also view the boot order tabs from the General tab of the service profile associated with a server.

44

Shutting Down a Blade Server
Procedure
Step 1
Step 2
Step 3
Step 4

Click the server for which you want to determine the boot order.
Step 5
Step 6
Step 7
If the Boot Order Details area is not expanded, click the Expand icon to the right of the heading.
To view the boot order assigned to the server, click the Configured Boot Order tab.
To view what will boot from the various devices in the physical server configuration, click the Actual Boot
Order tab.
Note
The Actual Boot Order tab always shows "Internal EFI Shell" at the bottom of the boot order
list.
Shutting Down a Blade Server

When you use this procedure to shut down a server with an installed operating system, Cisco UCS Manager
triggers the OS into a graceful shutdown sequence.
If the Shutdown Server link is dimmed in the Actions area, the server is not running.
Note
When a blade server that is associated with a service profile is shut down, the VIF down alerts F0283 and
F0479 are automatically suppressed.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server that you want to shut down.
Step 5
Step 6
In the Actions area, click Shutdown Server.

After the server has been successfully shut down, the Overall Status field on the General tab displays a
power-off status.
Shutting Down a Server from the Service Profile


45

Resetting a Blade Server
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Choose the service profile that requires the associated server to shut down.
Step 6
Step 7

After the server successfully shuts down, the Overall Status field on the General tab displays a down status
or a power-off status.
Resetting a Blade Server

When you reset a server, Cisco UCS Manager sends a pulse on the reset line. You can choose to gracefully
shut down the operating system. If the operating system does not support a graceful shutdown, the server is
power cycled. The option to have Cisco UCS Manager complete all management operations before it resets
the server does not guarantee the completion of these operations before the server is reset.
Note
If you are trying to boot a server from a power-down state, you should not use Reset.
If you continue the power-up with this process, the desired power state of the servers become out of sync
with the actual power state and the servers might unexpectedly shut down at a later time. To safely reboot
the selected servers from a power-down state, click Cancel, then select the Boot Server action.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server that you want to reset.
Step 5
Step 6
In the Actions area, click Reset.

In the Reset Server dialog box, do the following:
a) Click the Power Cycle option.
b) (Optional) Check the check box if you want Cisco UCS Manager to complete all management operations
that are pending on this server.
c) Click OK.

46

Resetting a Blade Server to Factory Default Settings
The reset may take several minutes to complete. After the server has been reset, the Overall Status field on
the General tab displays an ok status.
Resetting a Blade Server to Factory Default Settings

You can now reset a blade server to its factory settings. By default, the factory reset operation does not affect
storage drives and flexflash drives. This is to prevent any loss of data. However, you can choose to reset these
devices to a known state as well.
Important
Resetting storage devices will result in loss of data.
Perform the following procedure to reset the server to factory default settings.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server that you want to reset to its factory default settings.
Step 5
Step 6
In the Actions area, click Server Maintenance.

In the Maintenance dialog box, do the following:
a) Click Reset to Factory Default.
b) Click OK.
Step 7
From the Maintenance Server dialog box that appears, select the appropriate options:
To delete all storage, check the Scrub Storage checkbox.
To place all disks into their initial state after deleting all storage, check the Create Initial Volumes
checkbox.
You can check this checkbox only if you check the Scrub Storage checkbox. For servers that support
JBOD, the disks will be placed in a JBOD state. For servers that do not support JBOD, each disk will
be initialized with a single R0 volume that occupies all the space in the disk.
Important
Do not check the Create Initial Volumes box if you want to use storage profiles. Creating
initial volumes when you are using storage profiles may result in configuration errors.
To delete all flexflash storage, check the Scrub FlexFlash checkbox.

Cisco UCS Manager resets the server to its factory default settings.

47

Reacknowledging a Blade Server
Reacknowledging a Blade Server

Perform the following procedure to rediscover the server and all endpoints in the server. For example, you
can use this procedure if a server is stuck in an unexpected state, such as the discovery state.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server that you want to acknowledge.
Step 5
Step 6
In the Maintenance dialog box, click Re-acknowledge, then click OK.

Cisco UCS Manager disconnects the server and then builds the connections between the server and the fabric
interconnect or fabric interconnects in the system. The acknowledgment may take several minutes to complete.
After the server has been acknowledged, the Overall Status field on the General tab displays an OK status.
Removing a Server from a Chassis

Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server that you want to remove from the chassis.
Step 5
Step 6

In the Maintenance dialog box, click Decommission, then click OK.
The server is removed from the Cisco UCS configuration.
Step 7
Go to the physical location of the chassis and remove the server hardware from the slot.
For instructions on how to remove the server hardware, see the Cisco UCS Hardware Installation Guide for
your chassis.
What to Do Next
If you physically re-install the blade server, you must re-acknowledge the slot for the Cisco UCS Manager to
rediscover the server.
For more information, see Reacknowledging a Server Slot in a Chassis, on page 50.

48

Deleting the Inband Configuration from a Blade Server
Deleting the Inband Configuration from a Blade Server

This procedure removes the inband management IP address configuration from a blade server. If this action
is greyed out, no inband configuration was completed.
Procedure
Step 1
Step 2
Step 3
Expand Equipment > Chassis > Chassis Number > Servers > Server Name.
In the Work area, click the Inventory tab.
Step 4
Step 5
Click the CIMC subtab.

In the Actions area, click Delete Inband Configuration.
Step 6
Click Yes in the Delete confirmation dialog box.

The inband configuration for the server is deleted.
Note
If an inband service profile is configured in Cisco UCS Manager with a default VLAN and pool
name, the server CIMC will automatically get an inband configuration from the inband profile
approximate one minute after deleting the inband configuration here.
Decommissioning a Blade Server

Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server that you want to decommission.
Step 5
Step 6

a) Click Decommission.
b) Click OK.
What to Do Next
If you physically re-install the blade server, you must re-acknowledge the slot for the Cisco UCS Manager to
rediscover the server.
For more information, see Reacknowledging a Server Slot in a Chassis, on page 50.

49

Recommissioning a Blade Server
Recommissioning a Blade Server

Procedure
Step 1
Step 2
Step 3
Step 4
Expand Equipment node.

Click the Chassis node.
In the Work pane, click the Decommissioned tab.
Step 5
Step 6
On the row for each blade server that you want to recommission, check the check box in the Recommission
column, then click Save Changes.
Step 7
(Optional) Monitor the progress of the server recommission and discovery on the FSM tab for the server.
Reacknowledging a Server Slot in a Chassis

Perform the following procedure if you decommissioned a blade server without removing the physical hardware
from the chassis, and you want Cisco UCS Manager to rediscover and recommission the server.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server whose slot you want to reacknowledge.
If Cisco UCS Manager displays a Resolve Slot Issue dialog box, do one of the following:
Option
Description
The here link in the

Situation area
Click this link and then click Yes in the confirmation dialog box. Cisco UCS
Manager reacknowledges the slot and discovers the server in the slot.
OK
Click this button if you want to proceed to the General tab. You can use the
Reacknowledge Slot link in the Actions area to have Cisco UCS Manager
reacknowledge the slot and discover the server in the slot.

50

Removing a Non-Existent Blade Server from the Configuration Database
Removing a Non-Existent Blade Server from the Configuration

Database
Perform the following procedure if you physically removed the server hardware without first decommissioning
the server. You cannot perform this procedure if the server is physically present.
If you want to physically remove a server, see Removing a Server from a Chassis, on page 48.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

In the Maintenance dialog box, click Remove, then click OK.
Cisco UCS Manager removes all data about the server from its configuration database. The server slot is now
available for you to insert new server hardware.
Choose the server that you want to remove from the configuration database.
Turning the Locator LED for a Blade Server On and Off

Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to turn the locator LED on or off.
Step 5
In the Actions area, click one of the following:

Turn on Locator LEDTurns on the LED for the selected server.
Turn off Locator LEDTurns off the LED for the selected server.
Turn on Master Locator LEDFor the Cisco UCS B460 M4 blade server, turns on the LED for the
master node.
Turn off Master Locator LEDFor the Cisco UCS B460 M4 blade server, turns off the LED for the
master node.
Turn on Slave Locator LEDFor the Cisco UCS B460 M4 blade server, turns on the LED for the
slave node.

51

Turning the Local Disk Locator LED on a Blade Server On and Off
Turn off Locator LEDFor the Cisco UCS B460 M4 blade server, turns off the LED for the slave
node.
Turning the Local Disk Locator LED on a Blade Server On and

Off
Before You Begin
Ensure the server, on which the disk is located, is powered on. If the server is off, you are unable to turn
on or off the local disk locator LED.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to turn the local disk locator LED on or off.
In the Work pane, click the Inventory > Storage > Disks tabs.
The Storage Controller inventory appears.
Step 5
Click a disk.
The disk details appear.
In the Details area, click Toggle Locator LED.
If the Locator LED state is On, it will turn Off. If the Locator LED state is Off, it will turn On.
Click Save Changes.
Step 6
Step 7
Resetting the CMOS for a Blade Server

Sometimes, troubleshooting a server might require you to reset the CMOS. Resetting the CMOS is not part
of the normal maintenance of a server.

52

Resetting the CIMC for a Blade Server
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to reset the CMOS.
Step 5
Step 6
In the Actions area, click Recover Server.

In the Recover Server dialog box, click Reset CMOS, then click OK.
Resetting the CIMC for a Blade Server

Sometimes, with the firmware, troubleshooting a server might require you to reset the CIMC. Resetting the
CIMC is not part of the normal maintenance of a server. After you reset the CIMC, the server boots with the
running version of the firmware for that server.
If the CIMC is reset, the power monitoring functions of Cisco UCS become briefly unavailable until the CIMC
reboots. Typically, the reset only takes 20 seconds; however, it is possible that the peak power cap can exceed
during that time. To avoid exceeding the configured power cap in a low power-capped environment, consider
staggering the rebooting or activation of CIMCs.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to reset the CIMC.
Step 5
Step 6

In the Recover Server dialog box, click Reset CIMC (Server Controller), then click OK.
Clearing TPM for a Blade Server

You can clear TPM only on Cisco UCS M4 blade and rack-mount servers that include support for TPM.
Caution
Clearing TPM is a potentially hazardous operation. The OS may stop booting. You may also see loss of
data.
Before You Begin

TPM must be enabled.

53

Viewing the POST Results for a Blade Server
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to clear TPM.
Step 5
Step 6

In the Recover Server dialog box, click Clear TPM, then click OK.
Viewing the POST Results for a Blade Server

You can view any errors collected during the Power On Self-Test process for a server and its adapters.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to view the POST results.
Step 5
In the Actions area, click View POST Results.

The POST Results dialog box lists the POST results for the server and its adapters.
Step 6
Step 7
(Optional) Click the link in the Affected Object column to view the properties of that adapter.
Click OK to close the POST Results dialog box.
Issuing an NMI from a Blade Server

Perform the following procedure if the system remains unresponsive and you need Cisco UCS Manager to
issue a Non-Maskable Interrupt (NMI) to the BIOS or operating system from the CIMC. This action creates
a core dump or stack trace, depending on the operating system installed on the server.

54

Viewing Health Events for a Blade Server
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server that you want to issue the NMI.
Step 5
Step 6

a) Click Diagnostic Interrupt.
b) Click OK.
Cisco UCS Manager sends an NMI to the BIOS or operating system.

Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to view health events.
In the Work pane, click the Health tab
The health events triggered for this server appear. The fields in this tab are:
Name
Description
Health Summary area

Health Qualifier field
Comma-separated names of all the heath events that

are triggered for the component.

55

Name
Description
Health Severity field
Highest severity of all the health events that are

triggered for the component. This can be one of the
following:
critical
major
minor
warning
info
cleared
Note
The severity levels listed here are from

highest to lowest severity.
Health Details area

Severity column
Severity of the health event. This can be one of the

following:
critical
major
minor
warning
info
cleared
Note
Name column
Name of the health event.
Description column
Detailed description of the health event.
Value column
Current value of the health event.
Details area
The Details area displays the Name, Description,

Severity, and Value details of any health event that
you select in the Health Details area.

56


Health LED Alarms
Health LED Alarms

The blade health LED is located on the front of each Cisco UCS B-Series blade server. Cisco UCS Manager
allows you to view the sensor faults that cause the blade health LED to change color from green to amber or
blinking amber.
The health LED alarms display the following information:
Name
Description
Severity column
The severity of the alarm. This can be one of the following:

CriticalThe blade health LED is blinking amber. This is
indicated with a red dot.
MinorThe blade health LED is amber. This is indicated with
an orange dot.
Description column
A brief description of the alarm.
Sensor ID column
The ID of the sensor the triggered the alarm.
Sensor Name column
The name of the sensor that triggered the alarm.
Viewing Health LED Alarms

Procedure
Step 1
Step 2
Step 3
Step 4

Click the server for which you want to view health LED alarms.
Step 5
In the Actions area, click View Health LED Alarms.

The View Health LED Alarms dialog box lists the health LED alarms for the selected server.
Step 6
Click OK to close the View Health LED Alarms dialog box.

57


58
CHAPTER
Rack-Mount Server Hardware Management

Rack-Mount Server Management, page 60
Guidelines for Removing and Decommissioning Rack-Mount Servers, page 60
Recommendations for Avoiding Unexpected Server Power Changes, page 61
Booting a Rack-Mount Server, page 61
Determining the Boot Order of a Rack-Mount Server, page 62
Shutting Down a Rack-Mount Server, page 63
Resetting a Rack-Mount Server, page 64
Resetting a Rack-Mount Server to Factory Default Settings, page 65
Reacknowledging a Rack-Mount Server, page 65
Deleting the Inband Configuration from a Rack-Mount Server, page 66
Decommissioning a Rack-Mount Server, page 67
Recommissioning a Rack-Mount Server, page 67
Renumbering a Rack-Mount Server, page 67
Removing a Non-Existent Rack-Mount Server from the Configuration Database, page 68
Turning the Locator LED for a Rack-Mount Server On and Off, page 69
Turning the Local Disk Locator LED on a Rack-Mount Server On and Off, page 69
Resetting the CMOS for a Rack-Mount Server, page 70
Resetting the CIMC for a Rack-Mount Server, page 70
Clearing TPM for a Rack-Mount Server, page 70
Issuing an NMI from a Rack-Mount Server, page 71
Viewing Health Events for a Rack-Mount Server, page 71
Viewing the POST Results for a Rack-Mount Server, page 73

59

Rack-Mount Server Management
Rack-Mount Server Management

You can manage and monitor all rack-mount servers that are integrated with a Cisco UCS domain through
Cisco UCS Manager. All management and monitoring features are supported for rack-mount servers except
power capping. Some rack-mount server management tasks, such as changes to the power state, can be
performed from both the server and service profile. The remaining management tasks can only be performed
on the server.
Cisco UCS Manager provides information, errors, and faults for each rack-mount server that it has discovered.
Tip
For information on how to integrate a supported Cisco UCS rack-mount server with Cisco UCS Manager,
see the Cisco UCS C-series server integration guide for your Cisco UCS Manager release.
Guidelines for Removing and Decommissioning Rack-Mount

Servers
Consider the following guidelines when deciding whether to remove or decommission a rack-mount server
using Cisco UCS Manager:
Decommissioning a Rack-Mount server
Decommissioning is performed when a rack-mount server is physically present and connected but you want
to temporarily remove it from the configuration. Because it is expected that a decommissioned rack-mount
server will be eventually recommissioned, a portion of the server's information is retained by Cisco UCS
Manager for future use.
Removing a Rack-Mount server
Removing is performed when you physically remove the server from the system by disconnecting the
rack-mount server from the fabric extender. You cannot remove a rack-mount server from Cisco UCS Manager
if it is physically present and connected to the fabric extender. Once the rack-mount server is disconnected,
the configuration for that rack-mount server can be removed in Cisco UCS Manager.
During removal, management interfaces are disconnected, all entries from databases are removed, and the
server is automatically removed from any server pools that it was assigned to during discovery.
Note
Only those servers added to a server pool automatically during discovery will be removed automatically.
Servers that have been manually added to a server pool have to be removed manually.
If you need to add a removed rack-mount server back to the configuration, it must be reconnected and then
rediscovered. When a server is reintroduced to Cisco UCS Manager it is treated like a new server and is subject
to the deep discovery process. For this reason, it's possible that Cisco UCS Manager will assign the server a
new ID that may be different from the ID that it held before.

60

Recommendations for Avoiding Unexpected Server Power Changes
Recommendations for Avoiding Unexpected Server Power

Changes
If a server is not associated with a service profile, you can use any available means to change the server power
state, including the physical Power or Reset buttons on the server.
If a server is associated with, or assigned to, a service profile, you should only use the following methods to
change the server power state:
In Cisco UCS Manager GUI, go to the General tab for the server or the service profile associated with
the server and select Boot Server or Shutdown Server from the Actions area.
In Cisco UCS Manager CLI, scope to the server or the service profile associated with the server and use
the power up or power down commands.
Important
Do not use any of the following options on an associated server that is currently powered off:
Reset in the GUI
cycle cycle-immediate or reset hard-reset-immediate in the CLI
The physical Power or Reset buttons on the server
If you reset, cycle, or use the physical power buttons on a server that is currently powered off, the server's
actual power state might become out of sync with the desired power state setting in the service profile. If the
communication between the server and Cisco UCS Manager is disrupted or if the service profile configuration
changes, Cisco UCS Manager might apply the desired power state from the service profile to the server,
causing an unexpected power change.
Power synchronization issues can lead to an unexpected server restart, as shown below:
Desired Power State in Service
Profile
Current Server Power State
Server Power State After

Communication Is Disrupted
Up
Powered Off
Powered On
Down
Powered On
Powered On
Note
Running servers are not

shut down regardless of
the desired power state in
Booting a Rack-Mount Server


61

Procedure
Step 1
Step 2
Step 3
Step 4
Expand Equipment > Rack Mounts > Servers.

Step 5
Step 6


Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Step 6
Step 7
Step 8

Determining the Boot Order of a Rack-Mount Server

Tip

62

Shutting Down a Rack-Mount Server
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6
Step 7
Order tab.
Note
list.
Shutting Down a Rack-Mount Server

If the Shutdown server link is dimmed in the Actions area, the server is not running.
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

power-off status.


63

Resetting a Rack-Mount Server
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Step 6
Step 7

Resetting a Rack-Mount Server

Note
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

c) Click OK.

64

Resetting a Rack-Mount Server to Factory Default Settings
The reset may take several minutes to complete. After the server is reset, the Overall Status field on the
General tab displays an ok status.
Resetting a Rack-Mount Server to Factory Default Settings

You can now reset a rack-mount server to its factory settings. By default, the factory reset operation does not
affect storage, including storage drives and flexflash drives. This is to prevent any loss of data. However, you
can choose to reset these devices to a known state as well.
Important
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

In the Maintenance dialog box, click Reset to Factory Default, then click OK.
Step 7
To delete all storage, check the Scrub Storage checkbox.
checkbox.
You can check this checkbox only if you check the Scrub Storage checkbox. For servers that support
Important
Do not check the Create Initial Volumes checkbox if you want to use storage profiles.
Creating initial volumes when you are using storage profiles may result in configuration
errors.
To delete all flexflash storage, check the Scrub FlexFlash checkbox.

Reacknowledging a Rack-Mount Server


65

Deleting the Inband Configuration from a Rack-Mount Server
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

a) Click Re-acknowledge.
b) Click OK.
Cisco UCS Manager disconnects the server, then builds the connections between the server and the fabric
After the server is acknowledged, the Overall Status field on the General tab displays an OK status.
Deleting the Inband Configuration from a Rack-Mount Server

This procedure removes the inband management IP address configuration from a rack server. If this action is
greyed out, no inband configuration was configured.
Procedure
Step 1
Step 2
Step 3
Expand Equipment > Rack Mounts > Servers > Server Number.
Step 4
Step 5

Step 6

Note
name, the server CIMC automatically gets an inband configuration from the inband profile approximate
one minute after deleting the inband configuration here.

66

Decommissioning a Rack-Mount Server
Decommissioning a Rack-Mount Server

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

Recommissioning a Rack-Mount Server

Procedure
Step 1
Step 2
Step 3
Under Equipment, click the Rack-Mounts node.

Step 4
On the row for each rack-mount server that you want to recommission, do the following:
a) In the Recommission column, check the check box.
b) Click Save Changes
Step 5
Step 6

Renumbering a Rack-Mount Server

Before You Begin
If you are swapping IDs between servers, you must first decommission both servers, then wait for the server
decommission FSM to complete before proceeding with the renumbering steps.

67

Removing a Non-Existent Rack-Mount Server from the Configuration Database
Procedure
Step 1
Step 2
Step 3

Expand the Servers node and verify that it does not include the following:
The rack-mount server you want to renumber
A rack-mount server with the number you want to use
If either of these servers are listed in the Servers node, decommission those servers. You must wait until the
decommission FSM is complete and the servers are not listed in the node before continuing. This might take
several minutes.
Step 4
Step 5
Step 6
Choose the rack-mount server that you want to renumber.
Step 7
On the row for each rack-mount server that you want to renumber, do the following:
a) Double-click in the ID field, and enter the new number that you want to assign to the rack-mount server.
b) In the Recommission column, check the check box.
c) Click Save Changes
Step 8
Step 9

On the Equipment tab, click the Rack-Mounts node.

Removing a Non-Existent Rack-Mount Server from the

Configuration Database
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6


68

Turning the Locator LED for a Rack-Mount Server On and Off
Turning the Locator LED for a Rack-Mount Server On and Off

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5

Turn on Locator LED
Turn off Locator LED
Turning the Local Disk Locator LED on a Rack-Mount Server On

and Off
Before You Begin
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Click a disk.
Click Save Changes.
Step 6
Step 7

69

Resetting the CMOS for a Rack-Mount Server
Resetting the CMOS for a Rack-Mount Server

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6
Resetting the CIMC for a Rack-Mount Server

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

Clearing TPM for a Rack-Mount Server

You can clear TPM only on Cisco UCS M4 blade and rack-mount servers that include support for TPM.
Caution
data.

70

Issuing an NMI from a Rack-Mount Server
Before You Begin

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

Issuing an NMI from a Rack-Mount Server

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

In the Maintenance dialog box, click Diagnostic Interrupt, then click OK.
Viewing Health Events for a Rack-Mount Server

Procedure
Step 1
Step 2
Step 3
Step 4


71

Viewing Health Events for a Rack-Mount Server
Name
Description
Health Summary area



following:
critical
major
minor
warning
info
cleared
Note

Health Details area

Severity column

following:
critical
major
minor
warning
info
cleared
Note
Name column
Description column
Value column
Details area


72


Viewing the POST Results for a Rack-Mount Server

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Step 6
Step 7

73


74
CHAPTER
Compute Cartridge Hardware Management

Compute Cartridges, page 75
Removing a Cartridge, page 75
Acknowledging a Cartridge Slot in a Chassis, page 76
Compute Cartridges
Compute cartridges consist of up to two Cisco UCS modular servers. Each individual server is independently
manageable through its own CIMC instance, and has its own memory and CPU. The cartridge does not contain
any I/O adapters or local storage within it.
Important
Removing a Cartridge
Physically remove the cartridge from its chassis before performing the following procedure.
Procedure
Step 1
Step 2
Step 3
Step 4
Expand Equipment > Chassis > Chassis Number > Cartridges

Choose the cartridge that you want to remove from the configuration database.
Step 5
In the Actions area, click Remove Cartridge, then click OK.

Cisco UCS Manager removes all data about the cartridge from its configuration database. The cartridge slot
is now available for you to insert new cartridge hardware.

75
Compute Cartridge Hardware Management

Acknowledging a Cartridge Slot in a Chassis
Acknowledging a Cartridge Slot in a Chassis

When a cartridge is replaced by another cartridge or relocated to a new slot in the same chassis or a different
chassis, it goes into the mismatch state and the Re-acknowledge Slot action becomes available. Perform the
following steps to re-acknowledge the cartridge slot if the cartridge slot is in the mismatch state.
Note
When you swap two cartridges, acknowledging one of the cartridges automatically resolves the slot status
of both slots.
Procedure
Step 1
Step 2
Step 3
Step 4
Expand Equipment > Chassis > Chassis Number > Cartridges

Choose the cartridge that you want to re-acknowledge.
Step 5
In the Actions area, click Re-acknowledge Slot, then click OK.

76
CHAPTER
Modular Server Hardware Management

Modular Server Management, page 77
Booting a Modular Server, page 78
Determining the Boot Order of a Modular Server, page 79
Shutting Down a Modular Server, page 79
Resetting a Modular Server, page 80
Reacknowledging a Modular Server, page 81
Deleting the Inband Configuration from a Modular Server, page 81
Decommissioning a Server, page 82
Recommissioning a Modular Server, page 83
Turning the Locator LED for a Server On and Off, page 83
Turning the Local Disk Locator LED on a Modular Server On and Off, page 83
Resetting the CMOS for a Modular Server, page 84
Resetting the CIMC for a Modular Server, page 84
Issuing an NMI from a Server, page 85
Viewing Health Events on a Server, page 85
Viewing the POST Results for a Modular Server, page 87
Modular Server Management

Modular servers, which are introduced in Cisco UCS M-Series, are contained in compute cartridges. You
cannot remove servers from their cartridges.

77

Booting a Modular Server
Important
Booting a Modular Server

Procedure
Step 1
Step 2
Expand Equipment > Chassis > Chassis Number > Cartridges > Cartridge Number > Servers
Step 3
Step 4

Step 5
Step 6

After the server has booted, the Overall Status field on the General tab displays an OK status.

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Step 6
Step 7
Step 8


78

Determining the Boot Order of a Modular Server
Determining the Boot Order of a Modular Server

Tip
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Order tab.
Note
list.
Shutting Down a Modular Server

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

power-off status.

79


Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Step 6
Step 7

Resetting a Modular Server

Note

80

Reacknowledging a Modular Server
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

c) Click OK.
Reacknowledging a Modular Server

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

Deleting the Inband Configuration from a Modular Server

This procedure removes the inband management IP address configuration from a server. If this action is greyed
out, no inband configuration was completed.

81

Decommissioning a Server
Procedure
Step 1
Step 2
Step 3
Step 4
Choose the server for which you want to delete the inband management IP configuration.
Step 5
Step 6

Step 7

Note
Decommissioning a Server
Decommissioning of a server is performed to temporarily remove the server from the UCSM configuration.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

b) Click OK.
What to Do Next
If you physically re-install the server, you must re-acknowledge the slot to have Cisco UCS Manager rediscover
the server.

82

Recommissioning a Modular Server
Recommissioning a Modular Server

Procedure
Step 1
Step 2
Step 3
Step 4
Expand Equipment node.

Step 5
Step 6
On the row for each server that you want to recommission, check the check box in the Recommission column,
then click Save Changes.
Step 7
Turning the Locator LED for a Server On and Off

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Turning the Local Disk Locator LED on a Modular Server On and

Off
Before You Begin

83

Resetting the CMOS for a Modular Server
Procedure
Step 1
Step 2
Step 3
Step 4
Click a disk.
Click Save Changes.
Step 5
Step 6
Step 7
Resetting the CMOS for a Modular Server

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

Resetting the CIMC for a Modular Server


84

Issuing an NMI from a Server
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

Issuing an NMI from a Server

Procedure
Step 1
Step 2
Step 3
Step 4
Choose the server from which you want to issue the NMI.
Step 5
Step 6

b) Click OK.
Viewing Health Events on a Server

Procedure
Step 1
Step 2
Step 3
Step 4

85

Viewing Health Events on a Server
Name
Description
Health Summary area



following:
critical
major
minor
warning
info
cleared
Note

Health Details area

Severity column

following:
critical
major
minor
warning
info
cleared
Note
Name column
Description column
Value column
Details area


86


Health LED Alarms
Health LED Alarms

The server health LED is located on the front of each Cisco UCS M-Series server. Cisco UCS Manager allows
you to view the sensor faults that cause the server health LED to change color from green to amber or blinking
amber.
Name
Description
Severity column
The severity of the alarm. This can be one of the following:

CriticalThe blade health LED is blinking amber. This is
indicated with a red dot.
MinorThe blade health LED is amber. This is indicated with
an orange dot.
Description column
Sensor ID column
The ID of the sensor the triggered the alarm.
Sensor Name column

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Step 6
Viewing the POST Results for a Modular Server

You can view any errors collected during the Power On Self-Test process for a server.

87

Viewing the POST Results for a Modular Server
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

The POST Results dialog box lists the POST results for the server.
Step 6

88
CHAPTER
10
C3X60 Server Node Hardware Management

Cisco UCS C3X60 Server Node Management, page 90
Booting a C3X60 Server Node, page 90
Booting a C3X60 Server Node from the Service Profile , page 90
Determining the Boot Order of a C3X60 Server Node, page 91
Shutting Down a C3X60 Server Node, page 91
Shutting Down a C3X60 Server Node from the Service Profile , page 92
Resetting a C3X60 Server Node, page 92
Resetting a C3X60 Server Node to Factory Default Settings, page 93
Reacknowledging a C3X60 Server Node, page 94
Removing a C3X60 Server Node from a Chassis, page 94
Deleting the Inband Configuration from a C3X60 Server Node, page 95
Decommissioning a C3X60 Server Node, page 95
Recommissioning a C3X60 Server Node, page 96
Reacknowledging a Server Slot in a C3260 Chassis, page 96
Removing a Non-Existent C3X60 Server Node from the Configuration Database, page 97
Turning the Locator LED for a C3X60 Server Node On and Off, page 97
Turning the Local Disk Locator LED on a C3X60 Server Node On and Off, page 98
Resetting the CIMC for a C3X60 Server Node, page 98
Resetting the CMOS for a C3X60 Server Node, page 99
Issuing an NMI from a C3X60 Server Node, page 99
Viewing the POST Results for a C3X60 Server Node, page 100
Viewing Health Events for a C3X60 Server Node, page 100

89

Cisco UCS C3X60 Server Node Management
Cisco UCS C3X60 Server Node Management

You can manage and monitor all Cisco UCS C3X60 server nodes in a Cisco UCS domain through Cisco UCS
Manager. You can perform some server management tasks, such as changes to the power state, from the server
and service profile.
The remaining management tasks can only be performed on the server.
If a server slot in a chassis is empty, Cisco UCS Manager provides information, errors, and faults for that slot.
You can also re-acknowledge the slot to resolve server mismatch errors and rediscover the server in the slot.
Booting a C3X60 Server Node

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

Booting a C3X60 Server Node from the Service Profile

Procedure
Step 1
Step 2
Step 3

Expand the node for the organization where you want to create the service profile, or where the appropriate
service profile already exists.
Step 4
Step 5
Step 6
Step 7
Step 8


90

Determining the Boot Order of a C3X60 Server Node
Determining the Boot Order of a C3X60 Server Node

Tip
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6
Step 7
Order tab.
Shutting Down a C3X60 Server Node

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

power-off status.

91

Shutting Down a C3X60 Server Node from the Service Profile
Shutting Down a C3X60 Server Node from the Service Profile

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the node for the organization with the associated service profile.
Choose the service profile associated with the server to be shut down.
Step 6
Step 7

Resetting a C3X60 Server Node

Note
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6


92

Resetting a C3X60 Server Node to Factory Default Settings
c) Click OK.
Resetting a C3X60 Server Node to Factory Default Settings

You can now reset a C3X60 Server Node to its factory settings. By default, the factory reset operation does
not affect storage drives. This is to prevent any loss of data. However, you can choose to reset these devices
to a known state as well.
The following guidelines apply to C3X60 Server Nodes when using scrub policies:
For C3X60 Server Nodes, you cannot delete storage by using the scrub policy.
C3X60 Server Nodes do not support FlexFlash drives.
For C3X60 Server Nodes, you can only reset the BIOS by using the scrub policy.
Important
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

a) Click Reset to Factory Default.
b) Click OK.
Step 7
To delete all storage, check the Scrub Storage check box.
Note
For C3X60 Server Nodes, you cannot delete storage using the scrub policy.
check box.
You can check this check box only if you check the Scrub Storage check box. For servers that support

93

Reacknowledging a C3X60 Server Node
Important
Do not check the Create Initial Volumes box if you want to use storage profiles. Creating
initial volumes when you are using storage profiles may result in configuration errors.
Reacknowledging a C3X60 Server Node

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

Removing a C3X60 Server Node from a Chassis

Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server that you want to remove from the chassis.
Step 5
Step 6

Step 7
Go to the physical location of the chassis and remove the server hardware from the slot.
For instructions on how to remove the server hardware, see the Cisco UCS Hardware Installation Guide for
your chassis.

94

Deleting the Inband Configuration from a C3X60 Server Node
What to Do Next
If you physically reinstall the server, you must re-acknowledge the slot for Cisco UCS Manager to re-discover
the server.
Deleting the Inband Configuration from a C3X60 Server Node

This procedure removes the inband management IP address configuration from a blade server. If this action
is grayed out, no inband configuration was completed.
Procedure
Step 1
Step 2
Step 3
Expand Equipment > Chassis > Chassis Number > Servers > Server Name.
Step 4
Step 5

Step 6

Note
Decommissioning a C3X60 Server Node

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

b) Click OK.

95

Recommissioning a C3X60 Server Node
What to Do Next
If you physically reinstall the server, you must re-acknowledge the slot for Cisco UCS Manager to rediscover
the server.
Recommissioning a C3X60 Server Node

Procedure
Step 1
Step 2
Step 3

Step 4
On the row for each server that you want to recommission, check the check box in the Recommission column,
then click Save Changes.
Step 5
Step 6
Reacknowledging a Server Slot in a C3260 Chassis

Perform the following procedure if you decommissioned a server without removing the physical hardware
from the chassis, and you want Cisco UCS Manager to rediscover and reacknowledge the server.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server whose slot you want to reacknowledge.
If Cisco UCS Manager displays a Resolve Slot Issue dialog box, do one of the following:
Option
Description
The here link in the

Situation area
Click this link and then click Yes in the confirmation dialog box. Cisco UCS
Manager reacknowledges the slot and discovers the server in the slot.
OK
Click this button if you want to proceed to the General tab. You can use the
Reacknowledge Slot link in the Actions area to have Cisco UCS Manager
reacknowledge the slot and discover the server in the slot.

96

Removing a Non-Existent C3X60 Server Node from the Configuration Database
Removing a Non-Existent C3X60 Server Node from the

Configuration Database
If you want to physically remove a server, see Removing a C3X60 Server Node from a Chassis, on page 94.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

Turning the Locator LED for a C3X60 Server Node On and Off
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5


97

Turning the Local Disk Locator LED on a C3X60 Server Node On and Off
Turning the Local Disk Locator LED on a C3X60 Server Node On

and Off
Before You Begin
Ensure that the disk is zoned. Turning the locator LED on and off cannot be done on disks that are not
zoned.
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Click a disk.
Click Save Changes.
Step 6
Step 7
Resetting the CIMC for a C3X60 Server Node


98

Resetting the CMOS for a C3X60 Server Node
Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

Resetting the CMOS for a C3X60 Server Node

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6

Issuing an NMI from a C3X60 Server Node

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5
Step 6


99

Viewing the POST Results for a C3X60 Server Node

b) Click OK.
Viewing the POST Results for a C3X60 Server Node

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5

Step 6
Step 7
Viewing Health Events for a C3X60 Server Node

Procedure
Step 1
Step 2
Step 3
Step 4

Name
Description
Health Summary area


100


Viewing Health Events for a C3X60 Server Node
Name
Description

following:
critical
major
minor
warning
info
cleared
Note

Health Details area

Severity column

following:
critical
major
minor
warning
info
cleared
Note

Name column
Description column
Value column
Details area


101

Health LED Alarms
Health LED Alarms

The server health LED is located on the front of each server. Cisco UCS Manager allows you to view the
sensor faults that cause the blade health LED to change color from green to amber or blinking amber.
Name
Description
Severity column
The severity of the alarm. This can be one of the

following:
Critical - The server health LED blinks amber.
This is indicated with a red dot.
Minor - The server health LED is amber. This
is indicated with an orange dot.
Description column
Sensor ID column
The ID of the sensor that triggered the alarm.
Sensor Name column

Procedure
Step 1
Step 2
Step 3
Step 4

Step 5

Step 6

102
CHAPTER
11
Server Pools
Configuring Server Pools, page 103
Configuring UUID Suffix Pools, page 105
Configuring IP Pools, page 108
Configuring Server Pools

Server Pools
A server pool contains a set of servers. These servers typically share the same characteristics. Those
characteristics can be their location in the chassis, or an attribute such as server type, amount of memory,
local storage, type of CPU, or local drive configuration. You can manually assign a server to a server pool,
or use server pool policies and server pool policy qualifications to automate the assignment.
If your system implements multitenancy through organizations, you can designate one or more server pools
to be used by a specific organization. For example, a pool that includes all servers with two CPUs could be
assigned to the Marketing organization, while all servers with 64 GB memory could be assigned to the Finance
organization.
A server pool can include servers from any chassis in the system. A given server can belong to multiple server
pools.
Creating a Server Pool

Procedure
Step 1
Step 2
Step 3
Expand Servers > Pools.

Expand the node for the organization where you want to create the pool.

103
Server Pools
Deleting a Server Pool
Step 4
Step 5
Right-click the Server Pools node and select Create Server Pool.
On the Set Name and Description page of the Create Server Pool wizard, complete the following fields:
Name
Description
Name field
The name of the server pool.

This name can be between 1 and 32 alphanumeric characters. You
cannot use spaces or any special characters other than - (hyphen), _
(underscore), : (colon), and . (period), and you cannot change this name
Description field
A user-defined description of the server pool.

Enter up to 256 characters. You can use any characters or spaces except
` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),
Step 6
Step 7
Click Next.
On the Add Servers page of the Create Server Pool wizard:
a) Select one or more servers from the Available Servers table.
b) Click the >> button to add the servers to the server pool.
c) When you have added all desired servers to the pool, click Finish.
Deleting a Server Pool

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Expand Servers > Pools > Organization_Name.

Expand the Server Pools node.
Right-click the pool you want to delete and select Delete.

104
Server Pools
Adding Servers to a Server Pool
Adding Servers to a Server Pool

Procedure
Step 1
Step 2
Step 3
Step 4

Right-click the pool to which you want to add one or more servers and select Add Servers to Server Pool.
In the Add Servers to Server Pool dialog box, do the following:
a) In the Servers table, select the servers that you want to add to the server pool.
You can use the Shift key or Ctrl key to select multiple entries.
b) Click the >> button to move those servers to the Pooled Servers table and add them to the server pool.
c) Click OK.
Removing Servers from a Server Pool

Procedure
Step 1
Step 2
Step 3

Right-click the pool from which you want to remove one or more servers and select Add Servers to Server
Pool.
In the Add Servers to Server Pool dialog box, do the following:
Step 4
a) In the Pooled Servers table, select the servers that you want to remove from the server pool.
You can use the Shift key or Ctrl key to select multiple entries.
b) Click the << button to move those servers to the Servers table and remove them from the server pool.
c) Click OK.
Configuring UUID Suffix Pools

UUID Suffix Pools
A UUID suffix pool is a collection of SMBIOS UUIDs that are available to be assigned to servers. The first
number of digits that constitute the prefix of the UUID are fixed. The remaining digits, the UUID suffix, are
variable. A UUID suffix pool ensures that these variable values are unique for each server associated with a
service profile which uses that particular pool to avoid conflicts.

105
Server Pools
Creating a UUID Suffix Pool
If you use UUID suffix pools in service profiles, you do not have to manually configure the UUID of the
server associated with the service profile.
Creating a UUID Suffix Pool

Procedure
Step 1
Step 2
Step 3
Expand Servers > Pools.

Step 4
Step 5
Right-click UUID Suffix Pools and select Create UUID Suffix Pool.
In the Define Name and Description page of the Create UUID Suffix Pool wizard, complete the following
fields:
Name
Description
Name field
The name of the UUID pool.

Description field
The user-defined description of the pool.

Prefix field

DerivedThe system creates the suffix.
otherYou specify the desired suffix. If you select this option,
Cisco UCS Manager GUI displays a text field where you can enter
the desired suffix, in the format XXXXXXXX-XXXX-XXXX.
Assignment Order field

DefaultCisco UCS Manager selects a random identity from the
pool.
SequentialCisco UCS Manager selects the lowest available
identity from the pool.

106
Server Pools
Deleting a UUID Suffix Pool
Step 6
Step 7
Click Next.
In the Add UUID Blocks page of the Create UUID Suffix Pool wizard, click Add.
Step 8
In the Create a Block of UUID Suffixes dialog box, complete the following fields:
Name
Description
From field
The first UUID in the block.
Size field
The number of UUIDs in the block.
Step 9 Click OK.

Step 10 Click Finish to complete the wizard.
What to Do Next
Include the UUID suffix pool in a service profile and/or template.
Deleting a UUID Suffix Pool

If you delete a pool, Cisco UCS Manager does not reallocate any addresses from that pool that were assigned
to vNICs or vHBAs. All assigned addresses from a deleted pool remain with the vNIC or vHBA to which
they are assigned until one of the following occurs:
The associated service profiles are deleted.
The vNIC or vHBA to which the address is assigned is deleted.
The vNIC or vHBA is assigned to a different pool.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the UUID Suffix Pools node.
Right-click the pool you want to delete and select Delete.

107
Server Pools
Configuring IP Pools
Configuring IP Pools
IP Pools
IP pools are collections of IP addresses that do not have a default purpose. You can create IPv4 or IPv6 address
pools in Cisco UCS Manager to do the following:
Replace the default management IP pool ext-mgmt for servers that have an associated service profile.
Cisco UCS Manager reserves each block of IP addresses in the IP pool for external access that terminates
in the Cisco Integrated Management Controller (CIMC) on a server. If there is no associated service
profile, you must use the ext-mgmt IP pool for the CIMC to get an IP address.
Replace the management inband or out-of-band IP addresses for the CIMC.
Note
You cannot create iSCSI boot IPv6 pools in Cisco UCS Manager.
You can create IPv4 address pools in Cisco UCS Manager to do the following:
Replace the default iSCSI boot IP pool iscsi-initiator-pool. Cisco UCS Manager reserves each block
of IP addresses in the IP pool that you specify.
Replace both the management IP address and iSCSI boot IP addresses.
Note
The IP pool must not contain any IP addresses that were assigned as static IP addresses for a server or
service profile.
Creating an IP Pool
Procedure
Step 1
In the Navigation pane, click LAN.
Step 2
Step 3
Step 4
In the LAN tab, expand LAN > Pools > Organization_Name .

Right-click IP Pools and select Create IP Pool.
In the Define Name and Description page of the Create IP Pool wizard, complete the following fields:

108
Server Pools
Creating an IP Pool
Name
Description
Name field
The name of the IP address pool.

Description field
The user-defined description of the IP address pool.


pool.
Step 5
Step 6
Click Next.
In the Add IPv4 Blocks page of the Create IP Pool wizard, click Add.
Step 7
In the Create a Block of IPv4 Addresses dialog box, complete the following fields:
Name
Description
From field
The first IPv4 address in the block.
Size field
The number of IP addresses in the pool.
Subnet Mask field
The subnet mask associated with the IPv4 addresses in the block.
Default Gateway field
The default gateway associated with the IPv4 addresses in the block.
Primary DNS field
The primary DNS server that this block of IPv4 addresses should access.
Secondary DNS field
The secondary DNS server that this block of IPv4 addresses should
access.
Step 8
Step 9 Click Next.
Step 10 In the Add IPv6 Blocks page of the Create IP Pool wizard, click Add.
Step 11 In the Create a Block of IPv6 Addresses dialog box, complete the following fields:

109
Server Pools
Adding a Block to an IP Pool
Name
Description
From field
Size field
The number of IP addresses in the pool.
Prefix
The network address prefix associated with the IPv6

addresses in the block.
The default gateway associated with the IPv6

addresses in the block.
Primary DNS field
The primary DNS server that this block of IPv6

addresses should access.
Secondary DNS field
The secondary DNS server that this block of IPv6

addresses should access.
Step 12 Click OK.

What to Do Next
Include the IP pool in a service profile and template.

You can add blocks of IPv4 or IPv6 addresses to IP pools.
Procedure
Step 1
Step 2
Step 3
Step 4

Expand the IP Pools node.
Right-click the desired IP pool and select one of:
Create Block of IPv4 Addresses
Create Block of IPv6 Addresses
Step 5
Complete the fields in the appropriate dialog box.

a) In the Create a Block of IPv4 Addresses dialog box, complete the following fields:
Name
Description
Name column
The range of IPv4 addresses assigned to the block.

110
Server Pools
Name
Description
From column
To column
The last IPv4 address in the block.
Subnet column
Default Gateway column
Primary DNS column
The primary DNS server that this block of IPv4 addresses should
access.
Secondary DNS column
access.
b) In the Create a Block of IPv6 Addresses dialog box, complete the following fields:
Step 6
Name
Description
Name column
From column
To column
Prefix column
The network address prefix associated with the IPv6 addresses in the
block.
Primary DNS column
The primary DNS server that this block of IPv6 addresses should
access.
access.
Click OK.

111
Server Pools
Deleting a Block from an IP Pool
Deleting a Block from an IP Pool

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
In the LAN tab, expand LAN > Pools > Root .

Expand the pool for which you want to delete a block of IP addresses.
Right-click the IP address block that you want to delete and select Delete.
Deleting an IP Pool
Procedure
Step 1
Step 2
Step 3
Step 4

Right-click the IP pool you want to delete and select Delete.
Note
You cannot delete the default pools ext-mgmt and
iscsi-initiator-pool.
Step 5

112
CHAPTER
12
Server Boot
Boot Policy, page 113
UEFI Boot Mode, page 114
UEFI Secure Boot, page 115
CIMC Secure Boot, page 115
Creating a Boot Policy, page 117
SAN Boot, page 118
iSCSI Boot, page 119
LAN Boot, page 144
Local Devices Boot, page 145
Deleting a Boot Policy, page 150
UEFI Boot Parameters, page 150
Boot Policy
Important
The Cisco UCS Manager enables you to create a boot policy for blade servers, rack servers, and modular
servers.
The Cisco UCS Manager boot policy overrides the boot order in the BIOS setup menu and determines the
following:
Selection of the boot device
Location from which the server boots
Order in which boot devices are invoked

113
Server Boot
UEFI Boot Mode
For example, you can have associated servers boot from a local device, such as a local disk or CD-ROM
(VMedia), or you can select a SAN boot or a LAN (PXE) boot.
You can either create a named boot policy to associate with one or more service profiles, or create a boot
policy for a specific service profile. A boot policy must be included in a service profile, and that service profile
must be associated with a server for it to take effect. If you do not include a boot policy in a service profile,
Cisco UCS Manager applies the default boot policy.
Note
Changes to a boot policy might be propagated to all servers created with an updating service profile
template that includes that boot policy. Re-association of the service profile with the server to rewrite the
boot order information in the BIOS is automatically triggered.
You can also specify the following for the boot policy:
Local LUN name. The name specified is the logical name in the storage profile, not the deployed
name. For modular servers, you can specify both a primary and secondary name. For other servers,
specify only a primary name. Specifying a secondary name results in a configuration error.
Specific JBOD disk number for booting from JBOD disks. This is not supported for the Modular
servers.
Any LUN for backward compatibility; however, we do not recommend this. Other devices must not
have bootable images to ensure a successful boot.
UEFI Boot Mode

Unified Extensible Firmware Interface (UEFI) is a specification that defines a software interface between an
operating system and platform firmware. Cisco UCS Manager uses UEFI to replace the BIOS firmware
interfaces. This allows the BIOS to run in UEFI mode while still providing legacy support.
You can choose either legacy or UEFI boot mode when you create a boot policy. Legacy boot mode is supported
for all Cisco UCS servers. UEFI boot mode is supported only on M3 and higher servers, and allows you to
enable UEFI secure boot mode.
UEFI PXE boot is supported with all Cisco VIC adapters on Cisco UCS rack servers integrated with Cisco
UCS Manager Release 2.2(4) and later releases. Beginning with Cisco UCS Manager Release 2.2(1), UEFI
PXE boot is supported on all Cisco blade servers.
The following limitations apply to the UEFI boot mode:
UEFI boot mode is not supported with the following combinations:
Gen-3 Emulex and QLogic adapters on Cisco UCS blade and rack servers integrated with Cisco
UCS Manager.
iSCSI boot for all adapters on Cisco UCS rack servers integrated with Cisco UCS Manager.
If you want to use UEFI boot mode with two iSCSI LUNs, you must manually specify a common iSCSI
initiator name in the service profile that is applied to both underlying iSCSI eNICs rather than allowing
Cisco UCS Manager to select the name from an IQN suffix pool. If you do not supply a common name,
Cisco UCS Manager will not be able to detect the second iSCSI LUN.
You cannot mix UEFI and legacy boot mode on the same server.

114
Server Boot
UEFI Secure Boot
The server will boot correctly in UEFI mode only if the boot devices configured in the boot policy have
UEFI-aware operating systems installed. If a compatible OS is not present, the boot device is not displayed
on the Actual Boot Order tab in the Boot Order Details area.
In some corner cases, the UEFI boot may not succeed because the UEFI boot manager entry was not
saved correctly in the BIOS NVRAM. You can use the UEFI shell to enter the UEFI boot manager entry
manually. This situation could occur in the following situations:
If a blade server with UEFI boot mode enabled is disassociated from the service profile, and the
blade is manually powered on using the Equipment tab or the front panel.
If a blade server with UEFI boot mode enabled is disassociated from the service profile, and a
direct VIC firmware upgrade is attempted.
If a blade or rack server with UEFI boot mode enabled is booted off SAN LUN, and the service
profile is migrated.
You can create UEFI boot parameters in Cisco UCS Manager. UEFI Boot Parameters, on page 150
provides more information.
UEFI Secure Boot

Cisco UCS Manager supports UEFI secure boot on Cisco UCS B-Series M3 and M4 Blade servers and Cisco
UCS C-Series M3 and M4 Rack servers. When UEFI secure boot is enabled, all executables, such as boot
loaders and adapter drivers, are authenticated by the BIOS before they can be loaded. To be authenticated,
the images must be signed by either the Cisco Certificate Authority (CA) or a Microsoft CA.
The following limitations apply to UEFI secure boot:
UEFI boot mode must be enabled in the boot policy.
The Cisco UCS Manager software and the BIOS firmware must be at Release 2.2 or greater.
Note
UEFI boot mode is supported on Cisco UCS C-Series rack servers beginning with
Release 2.2(3a).
User-generated encryption keys are not supported.

UEFI secure boot can only be controlled by Cisco UCS Manager.
If you want to downgrade to an earlier version of Cisco UCS Manager, and you have a server in secure
boot mode, you must disassociate, then re-associate the server before downgrading. Otherwise, server
discovery is not successful.
CIMC Secure Boot

With CIMC secure boot, only Cisco signed firmware images can be installed and run on the servers. When
the CIMC is updated, the image is certified before the firmware is flashed. If certification fails, the firmware
is not flashed. This prevents unauthorized access to the CIMC firmware.

115
Server Boot
Determining the CIMC Secure Boot Status
Guidelines and Limitations for CIMC Secure Boot

CIMC secure boot is supported on Cisco UCS M3 rack servers.
Note
CIMC secure boot is enabled by default on the Cisco UCS C220 M4 and C240 M4 rack
servers, and is automatically enabled on the Cisco UCS C460 M4 rack server after
upgrading to CIMC firmware release 2.2(3) or higher.
After CIMC secure boot is enabled, you cannot disable it.

After CIMC secure boot is enabled on a server, you cannot downgrade to a CIMC firmware image prior
to 2.1(3).
Determining the CIMC Secure Boot Status

Procedure
Step 1
Step 2
Step 3
Expand Equipment > Rack-Mounts > Servers > Server Name.

Step 4
Step 5

In the CIMC area, note the Secure Boot Operational State field.
UnsupportedCIMC secure boot is not supported on the server.
DisabledCIMC secure boot is supported, but is disabled on the server.
EnablingCIMC secure boot was enabled, and the operation is in process.
EnabledCIMC secure boot is enabled on the server.
Enabling CIMC Secure Boot on a Rack Server

Procedure
Step 1
Step 2
Step 3
Expand Equipment > Rack-Mounts > Servers > Server Name.

Step 4
Step 5

In the Actions area, click Enable Secure Boot.

116
Server Boot
Creating a Boot Policy
CIMC secure boot is only supported on Cisco UCS M3 rack servers. If CIMC secure boot is not supported
or is already enabled, this action is greyed.
Step 6
Click Yes in the Enable Secure Boot confirmation dialog box.

Note
After enabled, you cannot disable CIMC secure
boot.
Creating a Boot Policy

You can also create a local boot policy that is restricted to a service profile or service profile template. However,
Cisco recommends that you create a global boot policy that can be included in multiple service profiles or
service profile templates.
Procedure
Step 1
Step 2
Step 3

Step 4
Right-click Boot Policies and select Create Boot Policy.

The Create Boot Policy wizard displays.
Step 5
Enter a unique name and description for the policy.

This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters
other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the
object is saved.
Step 6
(Optional) After you make changes to the boot order, check the Reboot on Boot Order Change check box
to reboot all servers that use this boot policy.
For boot policies applied to a server with a non-Cisco VIC adapter, even if the Reboot on Boot Order Change
check box is not checked, when SAN devices are added, deleted, or their order is changed, the server always
reboots when boot policy changes are saved.
Step 7
(Optional) If desired, check the Enforce vNIC/vHBA/iSCSI Name check box.

If checked, Cisco UCS Manager displays a configuration error and reports whether one or more of the
vNICs, vHBAs, or iSCSI vNICs listed in the Boot Order table match the server configuration in the
service profile.
If not checked, Cisco UCS Manager uses the vNICs or vHBAs (as appropriate for the boot option) from
Step 8 In the Boot Mode field, choose the Legacy or UEFI radio button.
Step 9 If you selected UEFI, check the Boot Security checkbox if you want to enable UEFI boot security.
Step 10 Configure one or more of the following boot options for the boot policy and set their boot order:

117
Server Boot
SAN Boot
Local Devices bootTo boot from local devices, such as local disks on the server, virtual media, or
remote virtual disks, continue with Configuring a Local Disk Boot for a Boot Policy, on page 146.
SAN bootTo boot from an operating system image on the SAN, continue with Configuring a SAN
Boot for a Boot Policy, on page 118.
You can specify a primary and a secondary SAN boot. If the primary boot fails, the server attempts to
boot from the secondary.
LAN bootTo boot from a centralized provisioning server, continue with Configuring a LAN Boot for
a Boot Policy, on page 145.
iSCSI bootTo boot from an iSCSI LUN, continue with Creating an iSCSI Boot Policy, on page 129.
What to Do Next
Include the boot policy in a service profile and template.
After a server is associated with a service profile that includes this boot policy, you can verify the boot order
in the Boot Order Details area on the General tab for the server.
SAN Boot
You can configure a boot policy to boot one or more servers from an operating system image on the SAN.
The boot policy can include a primary and a secondary SAN boot. If the primary boot fails, the server attempts
to boot from the secondary.
Cisco recommends using a SAN boot, because it offers the most service profile mobility within the system.
If you boot from the SAN when you move a service profile from one server to another, the new server boots
from the same operating system image. Therefore, the new server appears as the same server to the network.
To use a SAN boot, ensure that the following is configured:
The Cisco UCS domain must be able to communicate with the SAN storage device that hosts the operating
system image.
A boot target LUN (Logical Unit Number) on the device where the operating system image is located.
Note
SAN boot is not supported on Gen-3 Emulex adapters on Cisco UCS blade and rack servers.
Configuring a SAN Boot for a Boot Policy


118
Server Boot
iSCSI Boot
Tip
If you configure a local disk and a SAN LUN for the boot order storage type and the operating system or
logical volume manager (LVM) is configured incorrectly, the server might boot from the local disk rather
than the SAN LUN.
For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV
names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are
two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local
disk.
This procedure continues directly from Creating a Boot Policy, on page 117.
Before You Begin
Note
If you are creating a boot policy that boots the server from a SAN LUN and you require reliable SAN
boot operations, Cisco recommends that you first remove all local disks from servers associated with a
service profile that includes the boot policy.
This does not apply for Cisco UCS M3 and M4 servers. This also does not apply to the UCS Mini Series.
Procedure
Step 1
Step 2
Step 3
Click the down arrows to expand the vHBAs area.

Click the Add SAN Boot link.
In the Add San Boot dialog box, specify the vHBA and type, then click OK.
Step 4
If this vHBA points to a bootable SAN image, click the Add SAN Boot Target link and, in the Add SAN
Boot Target dialog box, specify the boot target LUN, boot target WWPN, and type, then click OK:
Step 5

Add another boot device to the Boot Order table.
Click OK to finish.
What to Do Next
After a server is associated with a service profile that includes this boot policy, you can verify the actual boot
order in the Boot Order Details area on the General tab for the server.
iSCSI Boot
iSCSI boot enables a server to boot its operating system from an iSCSI target machine located remotely over
a network.
iSCSI boot is supported on the following Cisco UCS hardware:

119
Server Boot
iSCSI Boot Process
Cisco UCS blade servers that have the Cisco UCS M51KR-B Broadcom BCM57711 network adapter
and use the default MAC address provided by Broadcom.
Cisco UCS M81KR Virtual Interface Card
Cisco UCS VIC-1240 Virtual Interface Card
Cisco UCS VIC-1280 Virtual Interface Card
Cisco UCS rack servers that have the Cisco UCS M61KR-B Broadcom BCM57712 network adapter.
Cisco UCS P81E Virtual Interface Card
Cisco UCS VIC 1225 Virtual Interface Cardon Cisco UCS rack servers
There are prerequisites that must be met before you configure iSCSI boot. For a list of these prerequisites,
see iSCSI Boot Guidelines and Prerequisites, on page 121.
For a high-level procedure for implementing iSCSI boot, see Configuring iSCSI Boot, on page 123.
iSCSI Boot Process

Cisco UCS Manager uses the iSCSI vNIC and iSCSI boot information created for the service profile in the
association process to program the adapter, located on the server. After the adapter is programmed, the server
reboots with the latest service profile values. After the power on self-test (POST), the adapter attempts to
initialize using these service profile values. If the adapter can use the values and log in to its specified target,
the adapter initializes and posts an iSCSI Boot Firmware Table (iBFT) to the host memory and a valid bootable
LUN to the system BIOS. The iBFT that is posted to the host memory contains the initiator and target
configuration that is programmed on the primary iSCSI VNIC.
Note
Previously, the host could see only one of the boot paths configured, depending on which path completed
the LUN discovery first, and would boot from that path. Now, when there are two iSCSI boot vNICs
configured, the host sees both of the boot paths. So for multipath configurations, a single IQN must be
configured on both the boot vNICs. If there are different IQNs configured on the boot vNICs on a host,
the host boots with the IQN that is configured on the boot vNIC with the lower PCI order.
The next step, which is the installation of the operating system (OS), requires an OS that is iBFT capable.
During installation of the OS, the OS installer scans the host memory for the iBFT table and uses the information
in the iBFT to discover the boot device and create an iSCSI path to the target LUN. Some OSs requires a NIC
driver to complete this path. If this step is successful, the OS installer finds the iSCSI target LUN on which
to install the OS.
Note
The iBFT works at the OS installation software level and might not work with HBA mode (also known
as TCP offload). Whether iBFT works with HBA mode depends on the OS capabilities during installation.
Also, for a server that includes a Cisco UCS M51KR-B Broadcom BCM57711 adapter, the iBFT normally
works at a maximum transmission unit (MTU) size of 1500, regardless of the MTU jumbo configuration.
If the OS supports HBA mode, you might need to set HBA mode, dual-fabric support, and jumbo MTU
size after the iSCSI installation process.

120
Server Boot
iSCSI Boot Guidelines and Prerequisites
iSCSI Boot Guidelines and Prerequisites

These guidelines and prerequisites must be met before configuring iSCSI boot:
After the iSCSI boot policies are created, a user with ls-compute privileges can include them in a service
profile or service profile template. However, a user with only ls-compute privileges cannot create iSCSI
boot policies.
To set up iSCSI boot from a Windows 2008 server where the second vNIC (failover vNIC) must boot
from an iSCSI LUN, consult Microsoft Knowledge Base Article 976042. Microsoft has a known issue
where Windows might fail to boot from an iSCSI drive or cause a bugcheck error if the networking
hardware is changed. To work around this issue, follow the resolution recommended by Microsoft.
The storage array must be licensed for iSCSI boot and the array side LUN masking must be properly
configured.
Two IP addresses must be determined, one for each iSCSI initiator. If possible, the IP addresses should
be on the same subnet as the storage array. The IP addresses are assigned statically or dynamically using
the Dynamic Host Configuration Protocol (DHCP).
You cannot configure boot parameters in the Global boot policy. Instead, after configuring boot
parameters, include the boot policy in the appropriate service profile.
The operating system (OS) must be iSCSI Boot Firmware Table (iBFT) compatible.
For Cisco UCS M51KR-B Broadcom BCM57711 network adapters:
Servers that use iSCSI boot must contain the Cisco UCS M51KR-B Broadcom BCM57711 network
adapter. For information on installing or replacing an adapter card, see the Cisco UCS B250
Extended Memory Blade Server Installation and Service Note. The service note is accessible from
the Cisco UCS B-Series Servers Documentation Roadmap at http://www.cisco.com/go/
unifiedcomputing/b-series-doc.
Set the MAC addresses on the iSCSI device.
If you are using the DHCP Vendor ID (Option 43), configure the MAC address of an iSCSI device
in /etc/dhcpd.conf.
HBA mode (also known as TCP offload) and the boot to target setting are supported. However,
only Windows OS supports HBA mode during installation.
Before installing the OS, disable the boot to target setting in the iSCSI adapter policy, then after
installing the OS, re-enable the boot to target setting.
Note
Each time you change an adapter policy setting, the adapter reboots to apply the new
setting.
When installing the OS on the iSCSI target, the iSCSI target must be ordered before the device
where the OS image resides. For example, if you are installing the OS on the iSCSI target from a
CD, the boot order should be the iSCSI target and then the CD.
After the server is iSCSI booted, do not modify the Initiator Name, Target name, LUN, iSCSI
device IP, or Netmask/gateway using the Broadcom tool.

121
Server Boot
Initiator IQN Configuration
Do not interrupt the POST (power on self-test) process or the Cisco UCS M51KR-B Broadcom
BCM57711 network adapter will fail to initialize.
For Cisco UCS M81KR Virtual Interface Card and Cisco UCS VIC-1240 Virtual Interface Card:
For Cisco UCS VIC-1240 Virtual Interface Card:
Do not set MAC addresses on the iSCSI device.
HBA mode and the boot to target setting are not supported.
When installing the OS on the iSCSI target, the iSCSI target must be ordered after the device where
the OS image resides. For example, if you are installing the OS on the iSCSI target from a CD,
the boot order should be the CD and then the iSCSI target.
If you are using the DHCP Vendor ID (Option 43), the MAC address of the overlay vNIC must
be configured in /etc/dhcpd.conf.
After the server is iSCSI booted, do not modify the IP details of the overlay vNIC.
The VMware ESX/ESXi operating system does not support storing a core dump file to an iSCSI boot
target LUN. Dump files must be written to a local disk.
Initiator IQN Configuration

Cisco UCS uses the following rules to determine the initiator IQN for an adapter iSCSI vNIC at the time a
service profile is associated with a physical server:
An initiator IQN at the service profile level and at the iSCSI vNIC level cannot be used together in a
service profile.
If an initiator IQN is specified at the service profile level, all of the adaptor iSCSI vNICs are configured
to use the same initiator IQN, except in the case of DHCP Option 43, where the initiator IQN is set to
empty on the adapter iSCSI vNIC.
When an initiator IQN is set at the iSCSI vNIC level, the initiator IQN at the service profile level is
removed, if one is present.
If there are two iSCSI vNIC in a service profile and only one of them has the initiator IQN set, the second
one is configured with the default IQN pool. You can change this configuration later. The only exception
is if DHCP Option 43 is configured. In this case, the initiator IQN on the second iSCSI vNIC is removed
during service profile association.
Note
If you change an iSCSI vNIC to use the DHCP Option 43 by setting the vendor ID, it
does not remove the initiator IQN configured at the service profile level. The initiator
IQN at the service profile level can still be used by another iSCSI vNIC which does not
use the DHCP Option 43.

122
Server Boot
Enabling MPIO on Windows
Enabling MPIO on Windows

You can enable (MPIO) to optimize connectivity with storage arrays.
Note
If you change the networking hardware, Windows might fail to boot from an iSCSI drive. For more
information, see Microsoft support Article ID: 976042.
Before You Begin

The server on which you enable the Microsoft Multipath I/O (MPIO) must have a Cisco VIC driver.
If there are multiple paths configured to the boot LUN, only one path should be enabled when the LUN is
installed.
Procedure
Step 1
In the service profile associated with the server, configure the primary iSCSI vNIC.
For more information, see Creating an iSCSI vNIC for a Service Profile, on page 130.
Step 2
Step 3
Step 4
Using the primary iSCSI vNIC, install the Windows operating system on the iSCSI target LUN.
After Windows installation completes, enable MPIO on the host.
In the service profile associated with the server, add the secondary iSCSI vNIC to the boot policy.
For more information, see Creating an iSCSI Boot Policy, on page 129.
Configuring iSCSI Boot

When you configure an adapter or blade in Cisco UCS to iSCSI boot from a LUN target, complete all of the
following steps.
Procedure
Command or Action
Purpose
Step 1
Configure the iSCSI boot adapter policy.
(Optional)
For more information, see Creating an iSCSI Boot
Policy, on page 129
Step 2
Configure the authentication profiles for the (Optional)

initiator and target.
For more information, see Creating an iSCSI
Authentication Profile, on page 126
Step 3
To configure the iSCSI initiator to use an IP (Optional)

address from a pool of IP addresses, add a
For more information, see Creating an iSCSI
block of IP addresses to the iSCSI initiator Initiator IP Pool, on page 128
pool.

123
Server Boot
Creating an iSCSI Adapter Policy
Command or Action
Purpose
Step 4
Create a boot policy that can be used in any For more information about creating a boot policy
service profile. Alternatively, you can create that can be used in any service profile, see
a local boot policy only for the specific service Creating an iSCSI Boot Policy, on page 129.
policy. However, Cisco recommends that you
create a boot policy that can be shared with
multiple service profiles.
Step 5
If you created a boot policy that can be used You can assign the boot policy to the service
in any service profile, assign it to the service profile while configuring the iSCSI boot and vNIC
profile. Otherwise, proceed to the next step. parameters in the service profile in step 7.
Step 6
Create an iSCSI vNIC in a service profile.
For more information, see Creating an iSCSI vNIC

for a Service Profile, on page 130
Step 7
Configure the iSCSI boot parameters,

including the iSCSI qualifier name (IQN),
initiator, target interfaces, and iSCSI vNIC
parameters in a service profile in expert mode
or service profile template.
For more information, see Creating a Service

Profile with the Expert Wizard, on page 158 or
Creating a Service Profile Template, on page 174,
respectively.
Step 8
Verify the iSCSI boot operation.
For more information, see Verifying iSCSI Boot.
Step 9
Install the OS on the server.
For more information, see one of the following

guides:
Cisco UCS B-Series Blade Servers VMware
Installation Guide
Cisco UCS B-Series Blade Servers Linux
Installation Guide
Cisco UCS B-Series Blade Servers Windows
Installation Guide
Step 10
Boot the server.

Procedure
Step 1
Step 2
Step 3


124
Server Boot
Step 4
Step 5
Right-click Adapter Policies and choose Create iSCSI Adapter Policy.

In the Create iSCSI Adapter Policy dialog box, complete the following fields:
Name
Description
Name field

Connection Timeout field
The number of seconds to wait until Cisco UCS assumes that the initial
login has failed and the iSCSI adapter is unavailable.
Enter an integer between 0 and 255. If you enter 0, Cisco UCS uses the
value set in the adapter firmware (default: 15 seconds).
LUN Busy Retry Count field
The number of times to retry the connection in case of a failure during

iSCSI LUN discovery.
Enter an integer between 0 and 60. If you enter 0, Cisco UCS uses the
value set in the adapter firmware (default: 15 seconds).
DHCP Timeout field
The number of seconds to wait before the initiator assumes that the
DHCP server is unavailable.
Enter an integer between 60 and 300 (default: 60 seconds).
Enable TCP Timestamp check

box
Check this box if you want to use a TCP Timestamp. With this setting,
transmitted packets are given a time stamp of when the packet was sent
so that the packet's round-trip time can be calculated, when needed.
Note
HBA Mode check box
Check this box to enable HBA mode (also known as TCP offload).
Important
Boot to Target check box
This option only applies to servers with the Cisco UCS NIC
M51KR-B adapter.
This option should only be enabled for servers with the

Cisco UCS NIC M51KR-B adapter running the Windows
operating system.
Check this box to boot from the iSCSI target.

Note
This option only applies to servers with the Cisco UCS NIC
M51KR-B adapter. It should be disabled until you have
installed an operating system on the server.

125
Server Boot
Deleting an iSCSI Adapter Policy
Name
Description
Owner field

LocalThis policy is available only to service profiles and service
profile templates in this Cisco UCS domain.
Pending GlobalControl of this policy is being transferred to
Cisco UCS Central. Once the transfer is complete, this policy will
be available to all Cisco UCS domains registered with Cisco UCS
Central.
GlobalThis policy is managed by Cisco UCS Central. Any
changes to this policy must be made through Cisco UCS Central.
Step 6
Click OK.
What to Do Next
Include the adapter policy in a service profile and template.
Deleting an iSCSI Adapter Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Step 6
Expand the Adapter Policies node.

Right-click the adapter policy and choose Delete.
Creating an iSCSI Authentication Profile

For iSCSI boot, you need to create both an initiator and a target iSCSI authentication profile.

126
Server Boot
Deleting an iSCSI Authentication Profile
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click iSCSI Authentication Profiles and choose Create iSCSI Authentication Profile.
In the Create Authentication Profile dialog box, complete the following fields:
Name
Description
Name field
The name of the authentication profile.

User Id field
The user Id associated with this profile.

Enter between 1 and 128 characters, spaces, or special characters.
Password field
The password associated with this profile.

Enter between 12 and 16 characters, including special characters.
Confirm Password field
Step 6
The password again for confirmation purposes.
Click OK.
What to Do Next
Include the authentication profile in a service profile and template.
Deleting an iSCSI Authentication Profile

Procedure
Step 1
Step 2
Step 3


127
Server Boot
Creating an iSCSI Initiator IP Pool
Step 4
Step 5
Step 6
Expand the iSCSI Authentication Profiles node.

Right-click the IP pool you want to delete and choose Delete.
Creating an iSCSI Initiator IP Pool

You can create a group of IP addresses to be used for iSCSI boot. Cisco UCS Manager reserves the block of
IPv4 addresses you specify.
The IP pool must not contain any IP addresses that were assigned as static IP addresses for a server or service
profile.
Procedure
Step 1
Step 2
Step 3
Expand LAN > Pools.

Step 4
Step 5
Step 6

Right-click IP Pool iscsi-initiator-pool and choose Create Block of IPv4 Addresses.
In the Create a Block of IPv4 Addresses dialog box, complete the following fields:
Step 7
Name
Description
Name column
From column
To column
Subnet column
Primary DNS column
The primary DNS server that this block of IPv4 addresses should access.
access.
Click OK.

128
Server Boot
Creating an iSCSI Boot Policy
What to Do Next
Configure one or more service profiles or service profile templates to obtain the iSCSI initiator IP address
from the iSCSI initiator IP pool.
Creating an iSCSI Boot Policy

You can add up to two iSCSI vNICs per boot policy. One vNIC acts as the primary iSCSI boot source, and
the other acts as the secondary iSCSI boot source.
Procedure
Step 1
Step 2

Step 3
Step 4
Right-click Boot Policies and choose Create Boot Policy.

The Create Boot Policy wizard displays.
Step 5
Enter a unique name and description for the policy.

object is saved.
Step 6
(Optional) To reboot a server that uses this boot policy after you make changes to the boot order, check the
Reboot on Boot Order Change check box.
In the Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot
policy, and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not
directly affect the boot order and the server does not reboot.
This applies only to servers using the standard boot
order.
(Optional) If desired, check the Enforce vNIC/vHBA/iSCSI Name check box.
Note
Step 7
service profile.
Step 8
To add a iSCSI boot to the boot policy, do the following:

a) Click the down arrows to expand the iSCSI vNICs area.
b) Click the Add iSCSI Boot link.
c) In the Add iSCSI Boot dialog box, enter a name for the iSCSI vNIC, and click OK.
d) Repeat steps b and c to create another iSCSI vNIC.

129
Server Boot
Creating an iSCSI vNIC for a Service Profile
What to Do Next

Procedure
Step 1
Step 2

Expand the node for the organization that contains the service profile for which you want to create an iSCSI
vNIC.
Expand the service profile for which you want to create a iSCSI vNIC.
Right-click the iSCSI vNICs node and choose Create vNICs.
In the Create iSCSI vNIC dialog box, complete the following fields:
Step 3
Step 4
Step 5
Step 6
Name
Description
Name field
The name of the iSCSI vNIC.

Overlay vNIC drop-down list
The LAN vNIC associated with this iSCSI vNIC, if any.
iSCSI Adapter Policy drop-down The iSCSI adapter policy associated with this iSCSI vNIC, if any.
list
Create iSCSI Adapter Policy link Click this link to create a new iSCSI adapter policy that will be available
to all iSCSI vNICs.
MAC Address field
The MAC address associated with this iSCSI vNIC, if any. If the MAC
address is not set, the Cisco UCS Manager GUI displays Derived.
MAC Pool field
The MAC pool associated with this iSCSI vNIC, if any.

130
Server Boot
Name
Description
VLAN drop-down list
The virtual LAN associated with this iSCSI vNIC. The default VLAN
is default.
Note
For the Cisco UCS M81KR Virtual Interface Card and the
Cisco UCS VIC-1240 Virtual Interface Card, the VLAN that
you specify must be the same as the native VLAN on the
overlay vNIC.
For the Cisco UCS M51KR-B Broadcom BCM57711 Adapter,
the VLAN that you specify can be any VLAN assigned to the
overlay vNIC.
Step 7
In the MAC Address Assignment drop-down list in the iSCSI MAC Address area, choose one of the
following:
Leave the MAC address unassigned, select Select (None used by default). Select this option if the
server that will be associated with this service profile contains a Cisco UCS M81KR Virtual Interface
Card adapter or a Cisco UCS VIC-1240 Virtual Interface Card.
Important
If the server that will be associated with this service profile contains a Cisco UCS NIC
M51KR-B adapter, you must specify a MAC address.
A specific MAC address, select 00:25:B5:XX:XX:XX and enter the address in the MAC Address field.
To verify that this address is available, click the corresponding link.
A MAC address from a pool, select the pool name from the list. Each pool name is followed by a pair
of numbers in parentheses. The first number is the number of available MAC addresses in the pool and
the second is the total number of MAC addresses in the pool.
If this Cisco UCS domain is registered with Cisco UCS Central, there might be two pool categories.
Domain Pools are defined locally in the Cisco UCS domain and Global Pools are defined in Cisco UCS
Central.
Step 8
(Optional) If you want to create a MAC pool that will be available to all service profiles, click Create MAC
Pool and complete the fields in the Create MAC Pool wizard.
For more information, see the Creating a MAC Pool section in Cisco UCS Manager Network Management
Guide, Release 3.1.
Step 9 Click OK.

Step 10 (Optional) If you want to set or change the initiator name, from the iSCSI vNICs tab, click Reset Initiator
Name or Change Initiator Name and complete the fields in the Change Initiator Name dialog box or click
. For more information, seeSetting the Initiator IQN at the Service Profile Level, on page 132.

131
Server Boot
Deleting an iSCSI vNIC from a Service Profile
Deleting an iSCSI vNIC from a Service Profile

Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile from which you want to delete an iSCSI
vNIC.
Expand the service profile from which you want to delete an iSCSI vNIC.
Expand the iSCSI vNICs node.
Right-click the iSCSI vNIC you want to delete and choose Delete.
Step 4
Step 5
Step 6
Step 7
Setting the Initiator IQN at the Service Profile Level

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the desired node for the organization.
Click the service profile with the iSCSI vNIC that you want to change.
In the Work pane, click the iSCSI vNICs tab.
Step 6
Step 7
Click Reset Initiator Name.


132
Server Boot
Changing the Initiator IQN at the Service Profile Level
Changing the Initiator IQN at the Service Profile Level

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the desired node for the organization.
Click the service profile with the iSCSI vNIC that you want to change.
In the Work pane, click the iSCSI vNICs tab.
Step 6
Step 7
In the Actions area, click Change Initiator Name.

In the Change Initiator Name dialog box, change the values in the following fields
Step 8
Name
Description
Initiator Name Assignment drop-down list
Choose the IQN initiator name that you want to use

from the drop-down list.
Initiator Name field
If you selected a manual initiator name assignment,

enter the initiator name.
Create IQN Suffix Pool link
Click to create a new IQN suffix pool.
Click OK.
Setting iSCSI Boot Parameters

You can set iSCSI boot parameters, including the boot order, boot policy, iSCSI authentication profile, initiator
interface, and target interface for an iSCSI vNIC.

133
Server Boot
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile for which you want to create iSCSI boot
parameters. If the system does not include multi-tenancy, expand the root node.
Click the service profile for which you want to create iSCSI boot parameters.
Click the Boot Order tab.
In the Specific Boot Policy area, click the down arrows to expand the iSCSI vNICs area.
In the iSCSI vNICs area, double-click the iSCSI vNICs from which you want to boot the server to add them
to the Boot Order table.
In the iSCSI vNICs area, click the Set Boot Parameters link.
If there are two iSCSI vNICs, choose the one for which you want to set boot parameters.
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
In the Set iSCSI Boot Parameters dialog box, complete the following fields:
Name
Description
Name field
The name of the iSCSI vNIC for which you are setting the boot
parameters.
Authentication Profile drop-down The name of the associated iSCSI authentication profile.
list
Create Authentication Profile
link
Click this link to create a new iSCSI authentication profile that will be
available to all iSCSI vNICs.
Step 10 In the Initiator Name area, complete the following fields:

Name
Description
Initiator Name Assignment

drop-down list
Select how the iSCSI boot initiator name is assigned. Choose one of
the following methods:
ManualYou will enter a name in the Initiator Name field. The
initiator name can contain up to 223 characters.
PoolsChoose an IQN suffix pool from which the name will be
assigned.
Setting the Initiator Name from the Set iSCSI Boot Parameters
dialog box sets the initiator IQN at the iSCSI vNIC level and
not at the service profile level. If more than one path is
configured, you must set the initiator IQN from the iSCSI
vNICs tab or when creating a service profile.
If you need to, you can change or reset the initiator name. For more
information, see Changing the Initiator IQN at the Service Profile Level,
on page 133.
Note

134
Server Boot
Name
Description
Click this link to create a new IQN suffix pool that will be available to
all iSCSI vNICs.
A regular expression that defines the name of the iSCSI initiator.

You can enter any alphanumeric string as well as the following special
characters:
. (period)
: (colon)
- (dash)
Step 11 From the Initiator IP Address Policy drop-down list, choose of the following:
Option
Description
Select (DHCP used by

default)
The system selects an interface automatically using DHCP.
Static
A static IPv4 address is assigned to the iSCSI boot vNIC based on the
information entered in this area.
Proceed to Step 13.
Proceed to Step 12.

Pool
An IPv4 address is assigned to the iSCSI boot vNIC from the management
IP address pool.
Proceed to Step 13.
Step 12 If you chose Static from the Initiator IP Address Policy drop-down list, complete the following fields:
Name
Description
IPv4 Address field
The IPv4 address assigned to the iSCSI boot vNIC.

If you want to specify this address, you must select Static in the
Initiator IP Address Policy drop-down list.
Subnet Mask field
The subnet mask associated with the IPv4 address.
The default gateway associated with the IPv4 address.
Primary DNS field
The primary DNS server address.
Secondary DNS field
The secondary DNS server address.
Step 13 For the iSCSI target interface, choose one of the following radio buttons:

135
Server Boot
Option
Description
iSCSI Static Target Interface
The system creates a static target interface that you need to configure.
Proceed to Step 14.
iSCSI Auto Target Interface
The system creates an auto target interface. You need to specify whether
the auto target uses an initiator or a DCHP vendor ID.
Proceed to Step 16.
Step 14 If you chose iSCSI Static Target Interface, in the Static Target Interface table, click Add.
Step 15 In the Create iSCSI Static Target dialog box, complete the following fields:
Name
Description
iSCSI Target Name field
A regular expression that defines the iSCSI Qualified Name (IQN) or

Extended Unique Identifier (EUI) name of the iSCSI target.
You can enter any alphanumeric characters as well as the following
special characters:
. (period)
: (colon)
- (dash)
This name must be properly formatted using standard IQN
or EUI guidelines.
The following examples show properly formatted iSCSI target names:
Important
iqn.2001-04.com.example
iqn.2001-04.com.example:storage:diskarrays-sn-a8675309
iqn.2001-04.com.example:storage.tape1.sys1.xyz
iqn.2001-04.com.example:storage.disk2.sys1.xyz
eui.02004567A425678D
Priority field
The system-assigned priority for the iSCSI target.
Port field
The port associated with the iSCSI target.

Enter an integer between 1 and 65535. The default is 3260.
list
Create iSCSI Authentication
Profile link
IPv4 Address field
The IPv4 address assigned to the iSCSI target.

136
Server Boot
Modifying iSCSI Boot Parameters
Name
Description
LUN Id field
The LUN identifier in the iSCSI target.
Step 16 If you chose iSCSI Auto Target Interface, enter either the initiator name or the DHCP vendor ID in the
DHCP Vendor Id field. The initiator must have already been configured. The vendor ID can be up to 32
alphanumeric characters.
Step 17 Click OK.

You can modify iSCSI boot parameters, including the boot order, boot policy, iSCSI authentication profile,
initiator interface, and target interface for an iSCSI vNIC.
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile for which you want to modify iSCSI
boot parameters. If the system does not include multi-tenancy, expand the root node.
Click the service profile for which you want to modify iSCSI boot parameters.
Click the Boot Order tab.
In the Specific Boot Policy area, click the down arrows to expand the iSCSI vNICs area.
To add or delete an iSCSI vNIC from the boot order or to change the boot order, do one of the following:
Step 4
Step 5
Step 6
Step 7
To add an iSCSI vNIC, in the iSCSI vNICs area, double-click an iSCSI vNICs to add it to the Boot
Order table.
To delete an iSCSI vNIC from the boot order, in the Boot Order table, select the iSCSI vNIC and click
Delete.
To change the iSCSI vNIC boot order, in the Boot Order table, select the iSCSI vNIC and click either
Move Up or Move Down.
Step 8
To change the boot parameters, in the iSCSI vNICs area, click the Set Boot Parameters link.
If there are two iSCSI vNICs, choose the one for which you want to change boot parameters.
Step 9
In the Set iSCSI Boot Parameters dialog box, change the values in any of the following fields:
Name
Description
Name field
The name of the iSCSI vNIC for which you are setting the boot
parameters.

137
Server Boot
Name
Description
list
Create Authentication Profile
link
Step 10 In the Initiator Name area, complete the following fields:

Name
Description
Initiator Name Assignment

drop-down list
Select how the iSCSI boot initiator name is assigned. Choose one of
the following methods:
ManualYou will enter a name in the Initiator Name field. The
initiator name can contain up to 223 characters.
PoolsChoose an IQN suffix pool from which the name will be
assigned.
Setting the Initiator Name from the Set iSCSI Boot Parameters
dialog box sets the initiator IQN at the iSCSI vNIC level and
not at the service profile level. If more than one path is
configured, you must set the initiator IQN from the iSCSI
vNICs tab or when creating a service profile.
If you need to, you can change or reset the initiator name. For more
information, see Changing the Initiator IQN at the Service Profile Level,
on page 133.
Note
Click this link to create a new IQN suffix pool that will be available to
all iSCSI vNICs.
A regular expression that defines the name of the iSCSI initiator.

You can enter any alphanumeric string as well as the following special
characters:
. (period)
: (colon)
- (dash)
Step 11 From the Initiator IP Address Policy drop-down list, change the selection to one of the following:
Option
Description
Select (DHCP used by

default)
The system selects an interface automatically using DHCP.

Proceed to Step 13.

138
Server Boot
Option
Description
Static
A static IPv4 address is assigned to the iSCSI boot vNIC based on the
information entered in this area.
Proceed to Step 12.
Pool
An IPv4 address is assigned to the iSCSI boot vNIC from the management
IP address pool.
Proceed to Step 13.
Step 12 If you chose Static from the Initiator IP Address Policy drop-down list, complete or change the following
fields:
Name
Description
IPv4 Address field
The IPv4 address assigned to the iSCSI boot vNIC.

If you want to specify this address, you must select Static in the
Initiator IP Address Policy drop-down list.
Subnet Mask field
The subnet mask associated with the IPv4 address.
The default gateway associated with the IPv4 address.
Primary DNS field
The primary DNS server address.
Secondary DNS field
The secondary DNS server address.
Step 13 For the iSCSI target interface, choose one of the following radio buttons:
Option
Description
iSCSI Static Target Interface
The system creates a static target interface that you need to configure.
Proceed to Step 14.
iSCSI Auto Target Interface
The system creates an auto target interface. You need to specify whether
the auto target uses an initiator or a DCHP vendor ID.
Proceed to Step 15.
Step 14 If you chose iSCSI Static Target Interface, do one of the following in the Static Target Interface table:
To add an iSCSI static target interface, click Add or to modify an iSCSI target interface, select the iSCSI
target interface that you want to change and click Modify. Then and complete or change the following
fields in the Create iSCSI Static Target dialog box:

139
Server Boot
Name
Description
iSCSI Target Name field
A regular expression that defines the iSCSI Qualified Name (IQN)

or Extended Unique Identifier (EUI) name of the iSCSI target.
You can enter any alphanumeric characters as well as the following
special characters:
. (period)
: (colon)
- (dash)
This name must be properly formatted using standard
IQN or EUI guidelines.
The following examples show properly formatted iSCSI target
names:
Important
iqn.2001-04.com.example
iqn.2001-04.com.example:storage:diskarrays-sn-a8675309
iqn.2001-04.com.example:storage.tape1.sys1.xyz
iqn.2001-04.com.example:storage.disk2.sys1.xyz
eui.02004567A425678D
Priority field
The system-assigned priority for the iSCSI target.
Port field
The port associated with the iSCSI target.

Enter an integer between 1 and 65535. The default is 3260.
Authentication Profile
drop-down list
The name of the associated iSCSI authentication profile.
Create iSCSI Authentication

Profile link
Click this link to create a new iSCSI authentication profile that will
be available to all iSCSI vNICs.
IPv4 Address field
The IPv4 address assigned to the iSCSI target.
LUN Id field
The LUN identifier in the iSCSI target.
To delete an iSCSI target interface, select the iSCSI target interface that you want to delete and click
Delete.
Note
If you have two iSCSI static targets and you delete the first priority target, the second priority target
becomes the first priority target, although Cisco UCS Manager still shows it as the second priority
target.

140
Server Boot
IQN Pools
Step 15 If you chose iSCSI Auto Target Interface, change the entry to either the initiator name or the DHCP vendor
ID in the DHCP Vendor Id field. The initiator must have already been configured. The vendor ID can be up
to 32 alphanumeric characters.
Step 16 Click OK.
IQN Pools
An IQN pool is a collection of iSCSI Qualified Names (IQNs) for use as initiator identifiers by iSCSI vNICs
in a Cisco UCS domain.
IQN pool members are of the form prefix:suffix:number, where you can specify the prefix, suffix, and a block
(range) of numbers.
An IQN pool can contain more than one IQN block, with different number ranges and different suffixes, but
sharing the same prefix.
Creating an IQN Pool

Note
In most cases, the maximum IQN size (prefix + suffix + additional characters) is 223 characters. When
using the Cisco UCS NIC M51KR-B adapter, you must limit the IQN size to 128 characters.
Procedure
Step 1
In the Navigation pane, click SAN.
Step 2
Step 3
Expand SAN > Pools.

Step 4
Step 5
Right-click IQN Pools and select Create IQN Suffix Pool.

In the Define Name and Description page of the Create IQN Suffix Pool wizard, fill in the following fields:
Field
Description
Name
The name of the iSCSI Qualified Name (IQN) pool.

Description
The user-defined description of the pool.


141
Server Boot
Creating an IQN Pool
Field
Description
Prefix
The prefix for any IQN blocks created for this pool.
Enter from 1 to 150 characters. You can use any letter or number, as
well as the special characters . (period), : (colon), and - (hyphen). For
example, you could use iqn1.alpha.com.

pool.
Step 6
Step 7
Click Next.
In the Add IQN Blocks page of the Create IQN Suffix Pool wizard, click Add.
Step 8
In the Create a Block of IQN Suffixes dialog box, fill in the following fields:
Name
Description
Suffix field
The suffix for this bock of iSCSI Qualified Names (IQNs).

Enter from 1 to 64 characters. You can use any letter or number, as well
as the special characters . (period), : (colon), and - (hyphen). For
example, you could use alphadc-1.
From field
The first suffix number in the block.
Size field
The number of suffixes in the block.
Step 9 Click OK.

What to Do Next
Include the IQN suffix pool in a service profile and template.

142
Server Boot
Adding a Block to an IQN Pool
Adding a Block to an IQN Pool

Procedure
Step 1
Step 2
Step 3
Expand SAN > Pools.

Expand the node for the organization containing the pool.
Step 4
Step 5
Step 6
Expand the IQN Pools node.

Right-click the desired IQN pool and select Create a Block of IQN Suffixes.
In the Create a Block of IQN Suffixes dialog box, fill in the following fields:
Name
Description
Suffix field
The suffix for this bock of iSCSI Qualified Names (IQNs).

Enter from 1 to 64 characters. You can use any letter or number, as well
as the special characters . (period), : (colon), and - (hyphen). For
example, you could use alphadc-1.
Step 7
From field
The first suffix number in the block.
Size field
The number of suffixes in the block.
Click OK.
Deleting a Block from an IQN Pool

If you delete an address block from a pool, Cisco UCS Manager does not reallocate any addresses in that
block that were assigned to vNICs or vHBAs. All assigned addresses from a deleted block remain with the
vNIC or vHBA to which they are assigned until one of the following occurs:
Procedure
Step 1
Step 2
Step 3
Expand SAN > Pools.


143
Server Boot
Deleting an IQN Pool
Step 4
Step 5
Step 6

Choose the IQN pool for which you want to delete a block of IQN suffixes.
In the Work pane, click the IQN Blocks tab.
Step 7
Step 8
Step 9
Right-click the block to be deleted and select Delete.

Click Yes to confirm the deletion.
Click Save Changes.
Deleting an IQN Pool

Procedure
Step 1
Step 2
Step 3
Expand SAN > Pools.

Step 4
Step 5
Step 6

Right-click the pool that you want to delete and select Delete.
LAN Boot
You can configure a boot policy to boot one or more servers from a centralized provisioning server on the
LAN. A LAN (or PXE) boot is frequently used to install operating systems on a server from that LAN server.
You can add more than one type of boot device to a LAN boot policy. For example, you could add a local
disk or virtual media boot as a secondary boot device.

144
Server Boot
Configuring a LAN Boot for a Boot Policy
Configuring a LAN Boot for a Boot Policy

You can add more than one type of boot device to a boot policy. For example, you can add a local disk or
virtual media boot as a secondary boot device.
Procedure
Step 1
Step 2
Click the down arrows to expand the vNICs area.

Click the Add LAN Boot link.
Step 3
In the Add LAN Boot dialog box, enter the name of the vNIC that you want to use for the LAN boot in the
vNIC field, then click OK.
Step 4

Click OK to finish.
What to Do Next
Include the boot policy in the service profile template.
Local Devices Boot

Cisco UCS Manager allows you to boot from different local devices.
Note
For Cisco UCS M3 and M4 blade and rack servers using enhanced boot order, you can select both top-level
and second-level boot devices. For Cisco UCS M1 and M2 blade and rack servers using standard boot
order, you can only select a top-level device.
Local Disk Boot

If a server has a local drive, you can configure a boot policy to boot the server from the top-level local disk
device or from any of the following second-level devices:
Local LUNEnables boot from local disk or local LUN.
Local JBODEnables boot from a bootable JBOD.

145
Server Boot
Configuring a Local Disk Boot for a Boot Policy
SD cardEnables boot from SD card.

Internal USBEnables boot for internal USB.
External USBEnables boot from external USB.
Embedded Local LUNEnables boot from the embedded local LUN on the Cisco UCS 240 M4 server.
Embedded Local DiskEnables boot from the embedded local disk on the Cisco UCS C240 M4SX
and the M4L servers.
Note
Second-level devices are only available for Cisco UCS M3 and M4 blade and rack servers using enhanced
boot order. For Cisco UCS M1 and M2 blade and rack servers using standard boot order, you can choose
only the top-level Add Local Disk.
Virtual Media Boot

You can configure a boot policy to boot one or more servers from a virtual media device that is accessible
from the server. A virtual media device mimics the insertion of a physical CD/DVD disk (read-only) or floppy
disk (read-write) into a server. This type of server boot is typically used to manually install operating systems
on a server.
Note
Second-level devices are only available for Cisco UCS M3 and M4 blade and rack servers using enhanced
boot order. For Cisco UCS M1 and M2 blade and rack servers using standard boot order, you can choose
only the top-level Add CD/DVD or Add Floppy.
Remote Virtual Drive Boot

You can configure a boot policy to boot one or more servers from a remote virtual drive that is accessible
from the server.
Configuring a Local Disk Boot for a Boot Policy

You can add more than one type of boot device to a boot policy. For example, you could add an SD card boot
as a secondary boot device.
Procedure
Step 1
Step 2
Click the down arrows to expand the Local Devices area.

Click any of the following links to add the device to the Boot Order table:
Add Local Disk or

146
Server Boot
Configuring a Virtual Media Boot for a Boot Policy
Add Local LUN

Add SD Card
Add Internal USB
Add External USB
For Cisco UCS M3 and M4 blade and rack servers using enhanced boot order, you can select both
top-level and second-level boot devices. For Cisco UCS M1 and M2 blade and rack servers using
standard boot order, you can only select a top-level device.
Note
Step 3

Click OK to finish.
What to Do Next
Configuring a Virtual Media Boot for a Boot Policy

You can add more than one type of boot device to a boot policy. For example, you could add a local disk boot
as a second boot device.
Note
Virtual Media requires the USB to be enabled. If you modify the BIOS settings that affect the USB
functionality, you also affect the Virtual Media. Therefore, Cisco recommends that you leave the following
USB BIOS defaults for best performance:
Make Device Non Bootableset to disabled
USB Idle Power Optimizing Settingset to high-performance
Procedure
Step 1
Step 2
Click the down arrows to expand the Local Devices area.

Click any of the following links to add the device to the Boot Order table:
Add CD/DVD or

147
Server Boot
Adding a Boot Policy to a vMedia Service Profile
Add Local CD/DVD

Add Remote CD/DVD
Add Floppy or
Add Local Floppy
Add Remote Floppy
Add Remote Virtual Drive
For Cisco UCS M3 and M4 blade and rack servers using enhanced boot order, you can select both
top-level and second-level boot devices. For Cisco UCS M1 and M2 blade and rack servers using
standard boot order, you can only select a top-level device.
Note
Step 3

Click OK to finish.
What to Do Next

This procedure describes how to set the boot policy options for vMedia on the Server Boot Order page of
the Create Service Profile (expert) wizard.
Procedure
Step 1
Step 2
Step 3

Step 4
Right-click the organization and select Create Service Profile (expert).

The Unified Computing System Manager pane displays.
Step 5
In the Name field, enter a unique name that you can use to identify the service profile.
other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service
profiles and service profile templates within the same organization.
This name must be unique within the organization or sub-organization in which you are creating the service
profile.

148
Server Boot
Step 6
From the UUID Assignment drop-down list, do one of the following:

Option
Description
Select (pool default used by default)
Assigns a UUID from the default UUID Suffix

pool.
Continue with Step 8.
Hardware Default
Uses the UUID assigned to the server by the

manufacturer.
If you choose this option, the UUID remains
unassigned until the service profile is
associated with a server. At that point, the
UUID is set to the UUID value assigned to
the server by the manufacturer. If the service
profile is later moved to a different server, the
UUID is changed to match the new server.
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX Uses the UUID that you manually assign.

Pools Pool_Name
Assigns a UUID from the UUID Suffix pool

that you select from the list at the bottom of
the drop-down list.
Each pool name is followed by two numbers
in parentheses that show the number of UUIDs
available in the pool and the total number of
UUIDs in the pool.
If you do not want use any of the existing
pools, but want to create a pool that all service
profiles can access, continue with Step 4.
Otherwise, continue with Step 8.
Step 7
(Optional) If you selected the XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX option, do the

following:
a) In the UUID field, enter the valid UUID that you want to assign to the server that uses this service profile.
Step 8
(Optional) If you want to create a new UUID Suffix pool to use in this service profile, click Create UUID
Suffix Pool and complete the fields in the Create UUID Suffix Pool wizard.
For more information, see Creating a UUID Suffix Pool, on page 106.
Step 9
(Optional) In the text box, enter a description of this service profile.

The user-defined description for this service profile.
Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^
(carat), " (double quote), = (equal sign), > (greater than), < (less than), or ' (single quote).
Step 10 Click Next.

Step 11 Navigate to Create Service Profile (expert) and click Server Boot Order.

149
Server Boot
Deleting a Boot Policy
The Boot Policy pane displays.

Step 12 From the Boot Policy drop-down list, choose one of the following:
Option
Description
Select Boot Policy to use
Assigns the default boot policy to this service profile.

Create a Specific Boot Policy Enables you to create a local boot policy that can only be accessed by this
service profile.
Boot Policies Policy_Name
Assigns an existing boot policy to the service profile. If you choose this
option, Cisco UCS Manager displays the details of the policy.
If you do not want use any of the existing policies, but want to create a
policy that all service profiles can access, click Create Boot Policy.
Otherwise, choose a policy from the list and continue with Step 13.
Step 13 If you created a new boot policy accessible to all service profiles and template, choose that policy from the
Boot Policy drop-down list .
Step 14 Click Next.
What to Do Next
Associate your Service Profile with a Cisco UCS server.
Deleting a Boot Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the Boot Policies node.
Right-click the policy you want to delete and choose Delete.
UEFI Boot Parameters

UEFI boot mode for servers is dependent on information that is stored on the platform hardware. The boot
entry, which contains information about the UEFI OS boot loader, is stored in the BIOS flash of the server.
In Cisco UCS Manager releases earlier than Release 2.2(4), when a service profile is migrated from one server
to another server, the boot loader information is not available on the destination server. Hence, the BIOS
cannot load the boot loader information for the server to boot in UEFI boot mode.

150
Server Boot
Guidelines and Limitations for UEFI Boot Parameters
Cisco UCSM Release 2.2(4) introduces UEFI boot parameters to provide the BIOS with information about
the location of the UEFI OS boot loader on the destination server from where the BIOS loads it. Now, the
server can use the boot loader information and boot in UEFI boot mode.
Guidelines and Limitations for UEFI Boot Parameters

You can configure UEFI boot parameters only if the boot mode is UEFI.
When you upgrade Cisco UCS Manager to Release 2.2(4) and higher UEFI boot failure during service
profile migration is not handled automatically. You must explicitly create the UEFI boot parameters in
the target device to successfully boot to the UEFI-capable OS.
UEFI boot parameters are supported on all M3 and higher servers that support second-level boot order.
You can specify UEFI boot parameters for the following device types:
SAN LUN
ISCSI LUN
Local LUN
UEFI boot parameters are specific to each operating system. You can specify UEFI boot parameters for
the following operating systems:
VMware ESX
SuSE Linux
Microsoft Windows
Red Hat Enterprise Linux 7
Setting UEFI Boot Parameters

Before You Begin
Ensure that the Boot Mode of the boot policy is Uefi.
Procedure
Step 1
Step 2
Step 3
Step 4

Expand Boot Policies and select the boot policy for which you want to configure UEFI boot parameters.
Step 5
To set UEFI boot parameters for a LUN, select the LUN in the Boot Order area and click Set Uefi Boot
Parameters.
Important
You can configure UEFI boot parameters only for local LUNs, SAN LUNs, and iSCSI LUNs.
Step 6
In the Set Uefi Boot Parameters dialog box, enter the following information:

151
Server Boot
Modifying UEFI Boot Parameters
Field
Description
Boot Loader Name
Specifies the name of the boot loader. This is a mandatory field.

Examplegrub.efi
Boot Loader Path
Specifies the path where the boot loader is located. This is a mandatory
field. The name of the boot loader must not be included in this field. Only
the path must be specified.
Example\EFI\RedHat
Boot Loader Description
Step 7
Step 8
Describes the boot loader. This is the human readable name that appears
in the F6 boot menu.
Click OK
Click Save Changes.

Before You Begin
Ensure that the Boot Mode of the boot policy is Uefi.
Procedure
Step 1
Step 2
Step 3
Step 4

Expand Boot Policies, and select the boot policy for which you want to modify UEFI boot parameters.
Step 5
To modify UEFI boot parameters for a LUN with UEFI boot parameters, select the LUN in the Boot Order
area and click Modify Uefi Boot Parameters.
Important
You can configure UEFI boot parameters only for local LUNs, SAN LUNs, and iSCSI LUNs.
Step 6
In the Modify Uefi Boot Parameters dialog box, enter the following information:
Field
Description
Boot Loader Name
Specifies the name of the boot loader. This is a mandatory field.
Boot Loader Path
Specifies the path where the boot loader is located. This is a

mandatory field.

152
Server Boot
Step 7
Step 8
Field
Description
Boot Loader Description
Describes the boot loader.
Click OK
Click Save Changes.

153
Server Boot

154
CHAPTER
13
Service Profiles
Service Profiles in UCS Manager, page 155
Service Profiles that Override Server Identity, page 156
Service Profiles that Inherit Server Identity, page 157
Guidelines and Recommendations for Service Profiles, page 157
Methods of Creating Service Profiles, page 158
Inband Service Profiles, page 161
Service Profile Tasks, page 161
Service Profile Association, page 171
Service Profile Templates, page 173
Service Profile Template Tasks, page 177
Service Profile Association, page 181
Service Profiles in UCS Manager

Important
A service profile defines a single server and its storage and networking characteristics. You can create a service
profile for the Cisco UCS Manager , UCS M-Series Modular servers, and the UCS Mini. When a service
profile is deployed to a server, UCS Manager automatically configures the server, adapters, fabric extenders,
and fabric interconnects to match the configuration specified in the service profile.
A service profile includes four types of information:
Server definition: Defines the resources (e.g. a specific server or a blade inserted to a specific chassis)
that are required to apply to the profile.
Identity information: Includes the UUID, MAC address for each virtual NIC (vNIC), and WWN
specifications for each HBA.

155
Service Profiles
Service Profiles that Override Server Identity
Firmware revision specifications: Used when a certain tested firmware revision is required to be
installed or for some other reason a specific firmware is used.
Connectivity definition: Configures network adapters, fabric extenders, and parent interconnects,
however this information is abstract as it does not include the details of how each network component
is configured.
The UCS system provides two types of service profiles: Service profiles that inherit server identity and service
profiles that override server identity.
Service Profiles that Override Server Identity

Important
This type of service profile provides the maximum amount of flexibility and control. This profile allows you
to override the identity values that are on the server at the time of association and use the resource pools and
policies set up in Cisco UCS Manager to automate some administration tasks.
You can disassociate this service profile from one server, then associate it with another server. This
re-association can be done either manually or through an automated server pool policy. The burned-in settings,
such as UUID and MAC address on the new server are overwritten with the configuration in the service profile.
As a result, the change in the server is transparent to your network. You do not need to reconfigure any
component or application on your network to begin using the new server.
This profile allows you to take advantage of and manage system resources through resource pools and policies,
such as the following:
Virtualized identity information, including pools of MAC addresses, WWN addresses, and UUIDs
Ethernet and Fibre Channel adapter profile policies
Firmware package policies
Operating system boot order policies
Unless the service profile contains power management policies, a server pool qualification policy, or another
policy that requires a specific hardware configuration, you can use the profile for any type of server in the
Cisco UCS domain.
You can associate these service profiles with either a rack-mount server or a blade server. The ability to
migrate the service profile depends upon whether you choose to restrict migration of the service profile.
Note
If you choose not to restrict migration, Cisco UCS Manager does not perform any compatibility checks
on the new server before migrating the existing service profile. If the hardware of both servers are not
similar, the association might fail.

156
Service Profiles
Service Profiles that Inherit Server Identity
Service Profiles that Inherit Server Identity

This hardware-based service profile is the simplest to use and create. This profile uses the default values in
the server and mimics the management of a rack-mounted server. It is tied to a specific server and cannot be
moved or migrated to another server.
You do not need to create pools or configuration policies to use this service profile.
This service profile inherits and applies the identity and configuration information that is present at the time
of association, such as the following:
MAC addresses for the two NICs
For a converged network adapter or a virtual interface card, the WWN addresses for the two HBAs
BIOS versions
Server UUID
Important
The server identity and configuration information inherited through this service profile might not have
the values burned into the server hardware at the manufacturer if those values were changed before this
profile is associated with the server.
Guidelines and Recommendations for Service Profiles

In addition to any guidelines or recommendations that are specific to policies and pools included in service
profiles and service profile templates, such as the local disk configuration policy, adhere to the following
guidelines and recommendations that impact the ability to associate a service profile with a server:
Limit to the Number of vNICs that Can Be Configured on a Rack-Mount Server
You can configure up to 56 vNICs per supported adapter, such as the Cisco UCS P81E Virtual Interface Card
(N2XX-ACPCI01), on any rack-mount server that is integrated with Cisco UCS Manager.
No Power Capping Support for Rack-Mount Servers
Power capping is not supported for rack servers. If you include a power control policy in a service profile that
is associated with a rack-mount server, the policy is not implemented.
QoS Policy Guidelines for vNICs
You can only assign a QoS policy to a vNIC if the priority setting for that policy is not set to fc, which
represents the Fibre Channel system class. You can configure the priority for the QoS policy with any other
system class.
QoS Policy Guidelines for vHBAs
You can only assign a QoS policy to a vHBA if the priority setting for that policy is set to fc, which represents
the Fibre Channel system class.
The Host Control setting for a QoS policy applies to vNICs only. It has no effect on a vHBA.

157
Service Profiles
Methods of Creating Service Profiles
Methods of Creating Service Profiles

Creating a Service Profile with the Expert Wizard
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5

In the Identify Service Profile panel, specify the service profile Name, UUID assignment and click Next.
You can provide an optional description for this service profile. If the UUID is not available, you can also
create a UUID Suffix Pool from this panel.
To create a service profile quickly, you can click Finish after specifying the name. Cisco UCS
Manager creates a new service profile with the specified name and all system default values.
(Optional) In the Networking panel, specify the required information for the Dynamic vNIC Connection
Policy and LAN Connectivity sections, then click Next.
You can create a dynamic vNIC connection policy and LAN connectivity policy from this panel.
Note
Step 6
Dynamic vNICs, usNICs, and VMQs are not supported when creating a vNIC for a LAN Connectivity
Policy. RoCE, VXLAN, NvGRE are not supported when configuring the Ethernet Adapter Policy.
(Optional) In the Storage panel, specify the SAN configuration information such as, Local Storage Policy,
SAN Connectivity, WWNN and VSAN, then click Next.
You can create a local disk configuration policy and SAN connectivity policy from this panel.
Note
Step 7
Note
FC vNICs are not supported when configuring vHBA under the Storage Policy.
Step 8
(Optional) In the Zoning panel, specify the required zoning information, then clickNext.
You can create the vHBA initiator groups from this panel.
Step 9
(Optional) In the vNIC/vHBA Placement panel, specify the placement method and PCI order, then clickNext.
You can create a placement policy from this panel.
Step 10 (Optional) In the Server Boot Order panel, specify the Boot Policy from the drop-down list, then click Next.
You can create a boot policy from this panel.
Step 11 (Optional) In the Maintenance Policy panel, specify the maintenance policy, then click Next.
You can create a new maintenance policy and specify a maintenance schedule from this panel.
Step 12 (Optional) In the Server Assignment panel, specify the Server Assignment from the drop down list and the
power state to apply on assignment, then click Next.
You can create a server pool or a host firmware package from this panel.
Step 13 (Optional) In the Operational Policies panel, specify the system operational information such as, BIOS
Configuration, External IPMI Management Configuration, Management IP Address, Monitoring
Configuration (Thresholds), Power Control Policy Configuration, and Scrub Policy, then click Finish.

158
Service Profiles
Creating a Service Profile that Inherits Server Identity
To set up an Outband IPv4 address or an Inband IPv4 or IPv6 address, click the respective tabs and
complete the required fields.
If you do not find the policies you need for each of these configurations, you can create them from this panel.
Note
Creating a Service Profile that Inherits Server Identity

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Right-click the organization and select Create Service Profile.

In the Naming area of the Create Service Profile dialog box, complete the following fields:
a) In the Name field, enter a unique name that you can use to identify the service profile.
characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique
across all service profiles and service profile templates within the same organization.
b) In the Description field, enter a description of this service profile.
Step 6
In the vNICs area of the Create Service Profile dialog box, choose the primary and secondary vNICs.
Step 7
In the vHBAs area of the Create Service Profile dialog box, choose the primary and secondary vHBAs.
Step 8
In the Boot Order area of the Create Service Profile dialog box, choose the primary and secondary boot
devices.
Step 9 (Optional) In the Select column of the Server Association (optional) area, click the radio button for a server
to associate this service profile with that server.
Step 10 Click OK.
Creating a Hardware Based Service Profile for a Blade Server

You cannot move a hardware based service profile to another server.

159
Service Profiles
Creating a Hardware Based Service Profile for a Rack-Mount Server
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to create a hardware based service profile.
Step 5
Step 6
In the Actions area, click Create Service Profile.

In the Create Service Profile for Server dialog box, do the following:
a) From the Create Service Profile in Organization drop-down list, select the organization in which you
want to create the service profile.
b) Click the Hardware Based Service Profile radio button.
c) In the Name field, enter a unique name for the service profile.
d) If you want Cisco UCS Manager to create vNICs for the service profile, check the Create Default vNICs
check box.
e) If you want Cisco UCS Manager to create vHBAs for the service profile, check the Create Default vHBAs
check box.
f) Click OK.
Cisco UCS Manager inherits and automatically applies the identity and configuration information in the server,
creates the service profile, and associates it with the server.
Creating a Hardware Based Service Profile for a Rack-Mount Server

You cannot move a hardware based service profile to another server.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to create a hardware based service profile.
Step 5
Step 6

a) From the Create Service Profile in Organization drop-down list, select the organization in which you
want to create the service profile.
b) Click the Hardware Based Service Profile radio button.
c) In the Name field, enter a unique name for the service profile.

160
Service Profiles
Inband Service Profiles
d) If you want Cisco UCS Manager to create vNICs for the service profile, check the Create Default vNICs
check box.
e) If you want Cisco UCS Manager to create vHBAs for the service profile, check the Create Default vHBAs
check box.
f) Click OK.
Cisco UCS Manager inherits and automatically applies the identity and configuration information in the server,
creates the service profile, and associates it with the server.
Inband Service Profiles

Deleting the Inband Configuration from a Service Profile
This procedure removes the inband management IP address configuration from a service profile. If this action
is greyed out, no inband configuration was configured.
Procedure
Step 1
Step 2
Step 3
Expand Servers > Service Profiles > Service_Profile_Name.

Step 4
Step 5

The inband management IP address configuration for the service profile is deleted.
Service Profile Tasks

Renaming a Service Profile
When you rename a service profile, the following occurs:
Event logs and audit logs that reference the previous name for the service profile are retained under that
name.
A new audit record is created to log the rename operation.

161
Service Profiles
Cloning a Service Profile
All records of faults against the service profile under its previous name are transferred to the new service
profile name.
Note
You cannot rename a service profile with pending changes.
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that includes the service profile you want to rename.
Step 4
Step 5
Click the service profile you want to rename.

Step 6
Step 7
In the Actions area, click Rename Service Profile.

In the Rename Service Profile dialog box, enter the new name for the service profile in the New Name field.
Step 8
Click OK.
Cloning a Service Profile

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click the service profile you want to clone and select Create a Clone.
In the Create Clone From Service Profile dialog box:
a) Enter the name you want to use for the new profile in the Clone Name field.
profile.

162
Service Profiles
Changing the UUID in a Service Profile
b) Click OK.
Step 6
Navigate to the service profile you just created and make sure that all options are correct.
Changing the UUID in a Service Profile

Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile for which you want to change the UUID.
Step 4
Step 5
Choose the service profile that requires the UUID for the associated server to be changed.
Step 6
Step 7
In the Actions area, click Change UUID.

Option
Description

pool.
Hardware Default

manufacturer.


163
Service Profiles
Modifying the Boot Order in a Service Profile
Option
Description
Pools Pool_Name

the drop-down list.
still available in the pool and the total number
of UUIDs in the pool.
Step 8

following:
a) In the UUID field, enter the valid UUID that you want to assign to the server which uses this service
profile.
b) To verify that the selected UUID is available, click the here link.
Step 9
Click OK.

Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that includes the service profile for which you want to change the boot
order.
If the system does not include multi-tenancy, expand the root node.
Step 4
Step 5
Click the service profile for which you want to change the boot order.
In the Work pane, click the Boot Order tab.
Step 6
Step 7
Click Modify Boot Policy to change the existing boot policy.

In the Modify Boot Policy dialog box, choose one of the following from the Boot Policy drop-down list:
Option
Description
Select Boot Policy to use
Assigns the default boot policy to this service profile.

Create a Specific Boot Policy Enables you to create a local boot policy that can only be accessed by this
service profile.

164
Service Profiles
Option
Description
Boot Policies Policy_Name
Assigns an existing boot policy to the service profile. If you choose this
If you do not want use any of the existing policies, but instead want to create
a policy that all service profiles can access, click Create Boot Policy and
continue with Step 2. Otherwise, continue with Step 14.
Step 8
If you chose to create a boot policy, in the Create Boot Policy dialog box, enter a unique name and description
for the policy.
object is saved.
Step 9
(Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the
Reboot on Boot Order Change check box.
In the Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot
policy, and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not
directly affect the boot order and the server does not reboot.
Step 10 (Optional) If desired, check the Enforce vNIC/vHBA/iSCSI Name check box.
service profile.
Step 11 To add a local disk, virtual CD-ROM, or virtual floppy to the boot order, do the following:
a) Click the down arrows to expand the Local Devices area.
b) Click one of the following links to add the device to the Boot Order table:
Add Local Disk or
Add Local LUN
Add SD Card
Add Internal USB
Add External USB
Add CD/DVD or
Add Local CD/DVD
Add Local Remote CD/DVD
c) Add another boot device to the Boot Order table, or click OK to finish.
Step 12 To add a LAN boot to the boot order, do the following:
a) Click the down arrows to expand the vNICs area.

165
Service Profiles
Creating a vNIC for a Service Profile
b) Click the Add LAN Boot link.

c) In the Add LAN Boot dialog box, enter the name of the vNIC that you want to use for the LAN boot in
the vNIC field, then click OK.
d) Add another device to the Boot Order table, or click OK to finish.
Step 13 To add a SAN boot to the boot order, do the following:
a) Click the down arrows to expand the vHBAs area.
b) Click the Add SAN Boot link.
c) In the Add San Boot dialog box, specify the vHBA and type, then click OK.
d) If this vHBA points to a bootable SAN image, click the Add SAN Boot Target link and, in the Add SAN
Boot Target dialog box, specify the boot target LUN, boot target WWPN, and type, then click OK.
e) Add another boot device to the Boot Order table, or click OK to finish.
Step 14 Click OK.
Creating a vNIC for a Service Profile

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

Expand the node for the organization that contains the service profile for which you want to create a vNIC.
Expand the service profile for which you want to create a vNIC.
Right-click the vNICs node and choose Create vNICs.
In the Create vNIC dialog box, enter the name, select a MAC Address Assignment, and check the Use
vNIC Template check box if you want to use an existing vNIC template.
You can also create a MAC pool from this area.
Step 7
Choose the Fabric ID, select the VLANs that you want to use, enter the CDN Name and MTU, and choose
a Pin Group.
You can also create a VLAN and a LAN pin group from this area.
Step 8
Step 9
In the Operational Parameters area, choose a Stats Threshold Policy.

In the Adapter Performance Profile area, choose an Adapter Policy, QoS Policy, and a Network Control
Policy.
You can also create an Ethernet adapter policy, QoS policy, and network control policy from this area.
Step 10 In the Connection Policies area, choose the Dynamic vNIC, usNIC or VMQ radio button, then choose the
corresponding policy.
You can also create a dynamic vNIC, usNIC, or VMQ connection policy from this area.
Step 11 Click OK.

166
Service Profiles
Deleting a vNIC from a Service Profile
Deleting a vNIC from a Service Profile

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7

Expand the node for the organization that contains the service profile from which you want to delete a vNIC.
Expand the service profile from which you want to delete a vNIC.
Expand the vNICs node.
Right-click the vNIC you want to delete and choose Delete.
Creating a vHBA for a Service Profile

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

Expand the node for the organization that contains the service profile for which you want to create a vHBA.
Expand the service profile for which you want to create a vHBA.
Right-click the vHBAs node and choose Create vHBAs.
In the Create vHBAs dialog box, enter the name and optional description.
Step 7
Choose the Fabric ID, Select VSAN, Pin Group, Persistent Binding, and Max Data Field Size.
You can also create a VSAN or SAN pin group from this area.
Step 8
Step 9
In the Operational Parameters area, choose the Stats Threshold Policy.

In the Adapter Performance Profile area, choose the Adapter Policy and QoS Policy.
You can also create a fibre channel adapter policy or QoS policy from this area.
Step 10 Click OK.

167
Service Profiles
Changing the WWPN for a vHBA
Changing the WWPN for a vHBA

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

Expand the node for the organization that contains the service profile for which you want to change the
WWPN.
Expand Service_Profile_Name > vHBAs.
Click the vHBA for which you want to change the WWPN.
Step 7
In the Actions area, click Change World Wide Name.
Step 8
In the Change World Wide Port Name dialog box, complete the required fields.
Step 9
Click OK.
Clearing Persistent Binding for a vHBA

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

Expand the node for the organization that contains the service profile for which you want to modify the vHBA.
Click the vHBA for which you want to clear the persistent binding.
Step 7
Step 8
In the Actions area, click Clear Persistent Binding.


168
Service Profiles
Deleting a vHBA from a Service Profile
Deleting a vHBA from a Service Profile

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7

Expand the node for the organization that contains the service profile from which you want to delete a vHBA.
Expand the service profile from which you want to delete a vHBA.
Expand the vHBAs node.
Right-click the vHBA you want to delete and choose Delete.
Adding a vHBA Initiator Group to a Service Profile

Procedure
Step 1
Step 2

Expand the node for the organization that contains the service profile to which you want to add a vHBA
initiator group.
Step 3
Step 4
Choose the service profile to which you want to add a vHBA initiator group.
In the Work pane, click the Storage > vHBA Initiator Groups.
Step 5
Step 6
On the icon bar at the right of the Select vHBA Initiator Groups table, click +.
In the Create vHBA Initiator Group dialog box, complete the following fields to set the name and description:
Name
Description
Name field
The name of the vHBA initiator group.

(underscore), : (colon), and . (period), and you cannot change this
Description field
A description of the group.

Enter up to 256 characters. You can use any characters or spaces
except ` (accent mark), \ (backslash), ^ (carat), " (double quote), =
(equal sign), > (greater than), < (less than), or ' (single quote).

169
Service Profiles
Adding a vHBA Initiator Group to a Service Profile
Step 7
Step 8
In the Select vHBA Initiators table, check the check box in the Select column for each vHBA you want to
include in the vHBA initiator group.
To add a storage connection policy to the initiator group, choose one of the following options:
Choose an existing storage connection policy from the Storage Connection Policy drop-down list.
Click the Create Storage Connection Policy link if you want to create a new storage connection policy
that will be available for use by other vHBA initiator groups within the Cisco UCS domain. For more
information, see Creating a Fibre Channel Storage Connection Policy. After you create the storage
connection policy, continue with Step 10.
Choose the Specific Storage Connection Policy option to create a storage connection policy that is
only available to this vHBA initiator group. Continue with Step 9.
Step 9
In the Specific Storage Connection Policy area, complete the following fields to create a storage connection
policy that is only available to this vHBA initiator group:
Name
Description
Description field
A description of the policy. Cisco recommends including information

about where and when to use the policy.
Zoning Type field

NoneCisco UCS Manager does not configure Fibre Channel
zoning.
Single Initiator Single TargetCisco UCS Manager
automatically creates one zone for each vHBA and storage port
pair. Each zone has two members. We recommend that you
configure this type of zoning unless you expect the number of
zones to exceed the maximum supported.
Single Initiator Multiple TargetsCisco UCS Manager
automatically creates one zone for each vHBA. We recommend
that you configure this type of zoning if you expect the number
of zones to reach or exceed the maximum supported.

170
Service Profiles
Deleting a Service Profile
Name
Description
FC Target Endpoints table
The Fibre Channel target endpoints associated with this policy. This
table contains the following columns and buttons:
WWPN columnThe World Wide Port Name associated with
the endpoint.
Path columnThe path to the endpoint.
VSAN columnThe VSAN associated with the endpoint.
Add buttonCreates a new FC target endpoint.
Delete buttonDeletes the selected endpoint.
Properties buttonDisplays all properties for the selected
endpoint.
Step 10 Click OK.

Step 11 If a confirmation dialog box displays, click Yes.
Deleting a Service Profile

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Expand Servers > Service Profiles > Organization_Name .

Right-click the service profile you want to delete and select Delete.
Click OK.
Service Profile Association

Associating a Service Profile with a Server or Server Pool
Follow this procedure if you did not associate the service profile with a blade server or server pool when you
created it, or to change the blade server or server pool with which a service profile is associated.

171
Service Profiles
Disassociating a Service Profile from a Server or Server Pool
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile that you want to associate with a new
server or server pool.
Step 4
Step 5
Right-click the service profile you want to associate with a server and select Associate Service Profile.
In the Associate Service Profile dialog box, select one of the following options:
Option
Description
Server Pool
Select a server pool from the drop-down list. Cisco UCS Manager assigns a server
from this pool to the service profile.
Server
Navigate to the desired available server in the navigation tree and select the server
which will be assigned to the service profile.
Custom Server
Specifies the chassis and slot that contains the server that will be assigned to the
service profile. If the server is not in the slot or is otherwise unavailable, the service
profile will be associated with the server when it becomes available.
Step 6
If you chose Custom Server, do the following:

a) In the Chassis Id field, enter the number of the chassis where the selected server is located.
b) In the Server Id field, enter the number of the slot where the selected server is located.
Step 7
If you want to restrict the migration of the service profile after it is associated with a server, check the Restrict
Migration. check box.
If you choose not to restrict migration, Cisco UCS Manager does not perform any compatibility checks on
the new server before migrating the existing service profile. If the hardware of both servers are not similar,
the association might fail.
Step 8
Click OK.

When you disassociate a service profile, Cisco UCS Manager attempts to shutdown the operating system on
the server. If the operating system does not shutdown within a reasonable length of time, Cisco UCS Manager
forces the server to shutdown.

172
Service Profiles
Service Profile Templates
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile that you want to disassociate from a
Step 4
Step 5
Right-click the service profile you want to disassociate from a server and select Disassociate Service Profile.
In the Disassociate Service Profile dialog box, click Yes to confirm that you want to disassociate the service
profile.
(Optional) Monitor the status and FSM for the server to confirm that the disassociation completed.
Step 6
Service Profile Templates

Initial and Existing Templates
With a service profile template, you can quickly create several service profiles with the same basic parameters,
such as the number of vNICs and vHBAs, and with identity information drawn from the same pools.
Tip
If you need only one service profile with similar values to an existing service profile, you can clone a
service profile in the Cisco UCS Manager GUI.
For example, if you need several service profiles with similar values to configure servers to host database
software, you can create a service profile template, either manually or from an existing service profile. You
then use the template to create the service profiles.
Cisco UCS supports the following types of service profile templates:
Initial template
Service profiles created from an initial template inherit all the properties of the template. Service profiles
created from an initial service profile template are bound to the template. However, changes to the
initial template do not automatically propagate to the bound service profiles. If you want to propagate
changes to bound service profiles, unbind and rebind the service profile to the initial template.
Updating template
Service profiles created from an updating template inherit all the properties of the template and remain
connected to the template. Any changes to the template automatically update the service profiles created
from the template.

173
Service Profiles
Creating a Service Profile Template
Note
Service profiles that are created from the initial template and normal service profiles fetch the lowest
available IDs in the sequential pool when you presReset.
Service profiles created from updating template might attempt to retain the same ID when you pressReset
even when lower IDs of sequential pool are free.
Creating a Service Profile Template

Procedure
Step 1
Step 2
Step 3
Expand Servers > Service Profile Templates.

Expand the node for the organization where you want to create the service profile template.
Step 4
Step 5
Right-click the organization and choose Create Service Profile Template.

In the Identify Service Profile Template panel, specify the service profile Name, Type, and UUID
Assignment, then click Next.
You can provide an optional description for this service profile template.
To create a service profile template quickly, you can click Finish after specifying the name. Cisco
UCS Manager creates a new service profile template with the specified name and all system default
values.
(Optional) In the Networking panel, specify the required information for the Dynamic vNIC Connection
Policy and LAN Connectivity sections, then click Next
You can create a dynamic vNIC connection policy and LAN connectivity policy from this panel.
Note
Step 6
Step 7
(Optional) In the Storage panel, specify the SAN configuration information such as, Local Storage Policy,
SAN Connectivity, WWNN, and vHBAs, then click Next.
You can create a local disk configuration policy and SAN connectivity policy from this panel.
Step 8
(Optional) In the Zoning panel, specify the required zoning information, then clickNext.
You can create the vHBA initiator groups from this panel.
Step 9
(Optional) In the vNIC/vHBA Placement panel, specify the placement method and PCI order, then clickNext.
You can create a placement policy from this panel.
Step 10 (Optional) In the Server Boot Order panel, specify the Boot Policy from the drop-down list, then click Next.
You can create a boot policy from this panel.
Step 11 (Optional) In the Maintenance Policy panel, specify the maintenance policy, then click Next.
You can create a new maintenance policy and specify a maintenance schedule from this panel.
Step 12 (Optional) In the Server Assignment panel, specify the Pool Assignment from the drop down list and the
power state to apply on assignment, then click Next.
You can create a server pool or a host firmware package from this panel.

174
Service Profiles
Creating One or More Service Profiles from a Service Profile Template
Step 13 (Optional) In the Operational Policies panel, specify the system operational information such as, BIOS
Configuration, External IPMI Management Configuration, Management IP Address, Monitoring
Configuration (Thresholds), Power Control Policy Configuration, and Scrub Policy, then click Finish.
Note
To set up an Outband IPv4 address or an Inband IPv4 or IPv6 address, click the respective tabs and
complete the required fields.
If you do not find the policies you need for each of these configurations, you can create them from this panel.
Creating One or More Service Profiles from a Service Profile Template

Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile template that you want to use as the
basis for your service profiles.
Step 4
Step 5
Right-click the service profile template from which you want to create the profiles and select Create Service
Profiles From Template.
In the Create Service Profiles From Template dialog box, complete the required fields.
Step 6
Click OK.
Creating a Template Based Service Profile for a Blade Server

Before You Begin
A qualified service profile template with the desired values must exist in Cisco UCS Manager.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to create a template based service profile.
Step 5
Step 6

a) Click the Template Based Service Profile radio button.
b) In the Name field, enter a unique name for the service profile.

175
Service Profiles
Creating a Template Based Service Profile for a Rack-Mount Server
c) From the Service Profile Template drop-down list, select the template from which you want to create
the service profile associated with this server.
Note
The drop-down list only lists service profile templates compatible with the selected blade server.
d) Click OK.
Creating a Template Based Service Profile for a Rack-Mount Server

Before You Begin
A qualified service profile template with the desired values must exist in Cisco UCS Manager.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to create a template based service profile.
Step 5
Step 6

a) Click the Template Based Service Profile radio button.
b) In the Name field, enter a unique name for the service profile.
c) From the Service Profile Template drop-down list, select the template from which you want to create
the service profile associated with this server.
d) Click OK.

176
Service Profiles
Creating a Service Profile Template from a Service Profile
Creating a Service Profile Template from a Service Profile

Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile that you want to use as the basis for
your template.
Step 4
Step 5
Right-click the service profile from which you want to create the template and select Create a Service Profile
Template.
In the Create Template From Service Profile dialog box, complete the required fields.
Step 6
Click OK.
Service Profile Template Tasks

Binding a Service Profile to a Service Profile Template
You can bind a service profile to a service profile template. When you bind the service profile to a template,
Cisco UCS Manager configures the service profile with the values defined in the service profile template. If
the existing service profile configuration does not match the template, Cisco UCS Manager reconfigures the
service profile. You can only change the configuration of a bound service profile through the associated
template.
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that includes the service profile you want to bind.
Step 4
Step 5
Click the service profile you want to bind.

Step 6
Step 7
In the Actions area, click Bind to a Template.

In the Bind to a Service Profile Template dialog box, do the following:
a) From the Service Profile Template drop-down list, choose the template to which you want to bind the
service profile.
b) Click OK.

177
Service Profiles
Unbinding a Service Profile from a Service Profile Template
Unbinding a Service Profile from a Service Profile Template

Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that includes the service profile you want to unbind.
Step 4
Step 5
Click the service profile you want to unbind.

Step 6
In the Actions area, click Unbind from the Template.
Step 7
Changing the UUID in a Service Profile Template

Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile template for which you want to change
the UUID.
Step 4
Step 5
Choose the service profile template whose UUID assignment you want to change.
Step 6
Step 7
In the Actions area, click Change UUID.

From the UUID Assignment drop-down list, choose one of the following:
Option
Description
Select (pool default used

by default)
Assigns a UUID from the default UUID Suffix pool.
Hardware Default
Uses the UUID assigned to the server by the manufacturer.

If you choose this option, the UUID remains unassigned until the service profile
is associated with a server. At that point, the UUID is set to the UUID value
assigned to the server by the manufacturer. If the service profile is later moved
to a different server, the UUID is changed to match the new server.

178
Service Profiles
Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile Template
Option
Description
Pools Pool_Name
Assigns a UUID from the UUID Suffix pool that you select from the list at the
bottom of the drop-down list.
Each pool name is followed by two numbers in parentheses that show the
number of UUIDs still available in the pool and the total number of UUIDs in
the pool.
Step 8
Click OK.
Resetting the UUID Assigned to a Service Profile from a Pool in a Service

Profile Template
If you change the UUID suffix pool assigned to an updating service profile template, Cisco UCS Manager
does not change the UUID assigned to a service profile created with that template. If you want Cisco UCS
Manager to assign a UUID from the newly assigned pool to the service profile, and therefore to the associated
server, you must reset the UUID. You can only reset the UUID assigned to a service profile and its associated
server under the following circumstances:
The service profile was created from an updating service profile template and includes a UUID assigned
from a UUID suffix pool.
The UUID suffix pool name is specified in the service profile. For example, the pool name is not empty.
The UUID value is not 0, and is therefore not derived from the server hardware.
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile for which you want to reset the UUID.
Step 4
Choose the service profile that requires the UUID for the associated server to be reset to a different UUID
suffix pool.
Step 5
Step 6
In the Actions area, click Reset UUID.

If this action is not visible, then the UUID configuration in the service profile does not meet the requirements
for resetting a UUID.
Step 7
Step 8

Click OK

179
Service Profiles
Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template
Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile
Template
If you change the MAC pool assigned to an updating service profile template, Cisco UCS Manager does not
change the MAC address assigned to a service profile created with that template. If you want Cisco UCS
Manager to assign a MAC address from the newly assigned pool to the service profile, and therefore to the
associated server, you must reset the MAC address. You can only reset the MAC address assigned to a service
profile and its associated server under the following circumstances:
The service profile was created from an updating service profile template and includes a MAC address
assigned from a MAC pool.
The MAC pool name is specified in the service profile. For example, the pool name is not empty.
The MAC address value is not 0, and is therefore not derived from the server hardware.
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile for which you want to reset the MAC
address.
Step 4
Step 5
Step 6
Expand Service_Profile_Name > vNICs.

Click the vNIC for which you want to reset the MAC address.
Step 7
Step 8
Step 9
In the Actions area, click Reset MAC Address.

Click OK.
Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile

Template
If you change the WWPN pool assigned to an updating service profile template, Cisco UCS Manager does
not change the WWPN assigned to a service profile created with that template. If you want Cisco UCS Manager
to assign a WWPN from the newly assigned pool to the service profile, and therefore to the associated server,
you must reset the WWPN. You can only reset the WWPN assigned to a service profile and its associated
server under the following circumstances:
The service profile was created from an updating service profile template and includes a WWPN assigned
from a WWPN pool.
The WWPN pool name is specified in the service profile. For example, the pool name is not empty.

180
Service Profiles
Deleting the Inband Configuration from a Service Profile Template
The WWPN value is not 0, and is therefore not derived from the server hardware.
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile for which you want to reset the WWPN.
Step 4
Step 5
Step 6

Click the vHBA for which you want to reset the WWPN.
Step 7
In the Actions area, click Reset WWPN.

Click OK.
Step 8
Step 9
Deleting the Inband Configuration from a Service Profile Template

This procedure removes the inband management IP address configuration from a service profile template. If
this action is greyed out, no inband configuration was configured.
Procedure
Step 1
Step 2
Step 3
Expand Servers > Service Profile Template > Service_Profile_Template_Name.

Step 4
Step 5

The inband management IP address configuration for the service profile template is deleted.
Service Profile Association

Associating a Service Profile with a Server or Server Pool
Follow this procedure if you did not associate the service profile with a blade server or server pool when you
created it, or to change the blade server or server pool with which a service profile is associated.

181
Service Profiles
Associating a Service Profile Template with a Server Pool
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile that you want to associate with a new
Step 4
Step 5
Right-click the service profile you want to associate with a server and select Associate Service Profile.
In the Associate Service Profile dialog box, select one of the following options:
Option
Description
Server Pool
Select a server pool from the drop-down list. Cisco UCS Manager assigns a server
from this pool to the service profile.
Server
Navigate to the desired available server in the navigation tree and select the server
which will be assigned to the service profile.
Custom Server
Specifies the chassis and slot that contains the server that will be assigned to the
service profile. If the server is not in the slot or is otherwise unavailable, the service
profile will be associated with the server when it becomes available.
Step 6
If you chose Custom Server, do the following:

a) In the Chassis Id field, enter the number of the chassis where the selected server is located.
b) In the Server Id field, enter the number of the slot where the selected server is located.
Step 7
If you want to restrict the migration of the service profile after it is associated with a server, check the Restrict
Migration. check box.
If you choose not to restrict migration, Cisco UCS Manager does not perform any compatibility checks on
the new server before migrating the existing service profile. If the hardware of both servers are not similar,
the association might fail.
Step 8
Click OK.
Associating a Service Profile Template with a Server Pool

Follow this procedure if you did not associate the service profile template with a server pool when you created
it, or to change the server pool with which a service profile created from this template is associated.

182
Service Profiles
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile that you want to associate with a server
pool.
Step 4
Right-click the service profile template you want to associate with a server pool and select Associate with
Server Pool.
The Associate with Server Pool dialog box opens.
Step 5
From the Server Pool section of the Pool Assignment drop-down list, select a server pool.
If you select Assign Later, the service profile template is not associated with a server pool.
Step 6
(Optional) From the Select Qualification drop-down list, select the server pool policy qualifications you
want to apply to a server that is associated with a service profile created from this template.
Click OK.
Step 7

When you disassociate a service profile, Cisco UCS Manager attempts to shutdown the operating system on
the server. If the operating system does not shutdown within a reasonable length of time, Cisco UCS Manager
forces the server to shutdown.
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile that you want to disassociate from a
Step 4
Step 5
Right-click the service profile you want to disassociate from a server and select Disassociate Service Profile.
In the Disassociate Service Profile dialog box, click Yes to confirm that you want to disassociate the service
profile.
(Optional) Monitor the status and FSM for the server to confirm that the disassociation completed.
Step 6

183
Service Profiles
Disassociating a Service Profile Template from its Server Pool
Disassociating a Service Profile Template from its Server Pool

Procedure
Step 1
Step 2
Step 3

Expand the node for the organization that contains the service profile that you want to disassociate from its
server pool.
Step 4
Right-click the service profile template you want to disassociate from its server pool and select Disassociate
Template.
Step 5

184
CHAPTER
14
Server-Related Policies
BIOS Settings, page 185
Trusted Platform Module, page 229
Consistent Device Naming, page 233
CIMC Security Policies, page 236
Local Disk Policies, page 239
Scrub Policy, page 252
DIMM Error Management, page 255
Serial over LAN Policy Settings, page 257
Server Autoconfiguration Policies, page 258
Server Discovery Policy Settings, page 261
Server Inheritance Policy Settings, page 262
Server Pool Policy Settings, page 264
Server Pool Policy Qualifications Settings, page 265
vNIC/vHBA Placement Policy Settings, page 272
CIMC Mounted vMedia, page 285
BIOS Settings
Server BIOS Settings
Cisco UCS provides two methods for making global modifications to the BIOS settings on servers in an Cisco
UCS domain. You can create one or more BIOS policies that include a specific grouping of BIOS settings
that match the needs of a server or set of servers, or you can use the default BIOS settings for a specific server
platform.

185
Both the BIOS policy and the default BIOS settings for a server platform enable you to fine tune the BIOS
settings for a server managed by Cisco UCS Manager.
Depending upon the needs of the data center, you can configure BIOS policies for some service profiles and
use the BIOS defaults in other service profiles in the same Cisco UCS domain, or you can use only one of
them. You can also use Cisco UCS Manager to view the actual BIOS settings on a server and determine
whether they are meeting current needs.
Note
Cisco UCS Manager pushes BIOS configuration changes through a BIOS policy or default BIOS settings
to the Cisco Integrated Management Controller (CIMC) buffer. These changes remain in the buffer and
do not take effect until the server is rebooted.
We recommend that you verify the support for BIOS settings in the server that you want to configure.
Some settings, such as Mirroring Mode for RAS Memory, are not supported by all Cisco UCS servers.
Main BIOS Settings

The following table lists the main server BIOS settings that you can configure through a BIOS policy or the
default BIOS settings:
Name
Description
Reboot on BIOS Settings Change
When the server is rebooted after you change one or more BIOS
settings.
If you enable this setting, the server is rebooted according to
the maintenance policy in the server's service profile. For
example, if the maintenance policy requires user
acknowledgment, the server is not rebooted and the BIOS
changes are not applied until a user acknowledges the pending
activity.
If you do not enable this setting, the BIOS changes are not
applied until the next time the server is rebooted, whether as a
result of another server configuration change or a manual reboot.
Quiet Boot
What the BIOS displays during Power On Self-Test (POST).

disabledThe BIOS displays all messages and Option
ROM information during boot.
enabledThe BIOS displays the logo screen, but does
not display any messages or Option ROM information
during boot.
Platform DefaultThe BIOS uses the value for this
attribute contained in the BIOS defaults for the server type
and vendor.

186
Name
Description
Post Error Pause
What happens when the server encounters a critical error during

POST. This can be one of the following:
disabledThe BIOS continues to attempt to boot the
server.
enabledThe BIOS pauses the attempt to boot the server
and opens the Error Manager when a critical error occurs
during POST.
and vendor.
Resume Ac On Power Loss
How the server behaves when power is restored after an

unexpected power loss. This can be one of the following:
stay-offThe server remains off until manually powered
on.
last-stateThe server is powered on and the system
attempts to restore its last state.
resetThe server is powered on and automatically reset.
and vendor.
Front Panel Lockout
Whether the power and reset buttons on the front panel are
ignored by the server. This can be one of the following:
disabledThe power and reset buttons on the front panel
are active and can be used to affect the server.
enabledThe power and reset buttons are locked out.
The server can only be reset or powered on or off from
the CIMC GUI.
and vendor.

187
Name
Description
Consistent Device Naming
Consistent Device Naming allows Ethernet interfaces to be

named in a consistent manner. This makes Ethernet interface
names more uniform, easy to identify, and persistent when
adapter or other configuration changes are made.
Whether consistent device naming is enabled or not. This can
be one of the following:
disabledConsistent device naming is disabled for the
BIOS policy.
enabledConsistent device naming is enabled for the
BIOS policy. This enables Ethernet interfaces to be named
consistently.
and vendor.
Processor BIOS Settings

The following table lists the processor BIOS settings that you can configure through a BIOS policy or the
Name
Description
Turbo Boost
Whether the processor uses Intel Turbo Boost Technology,

which allows the processor to automatically increase its
frequency if it is running below power, temperature, or voltage
specifications. This can be one of the following:
disabledThe processor does not increase its frequency
automatically.
enabledThe processor uses Turbo Boost Technology
if required.
and vendor.

188
Name
Description
Enhanced Intel Speedstep
Whether the processor uses Enhanced Intel SpeedStep

Technology, which allows the system to dynamically adjust
processor voltage and core frequency. This technology can result
in decreased average power consumption and decreased average
heat production. This can be one of the following:
disabledThe processor never dynamically adjusts its
voltage or frequency.
enabledThe processor utilizes Enhanced Intel SpeedStep
Technology and enables all supported processor sleep
states to further conserve power.
and vendor.
We recommend that you contact your operating system vendor
to make sure your operating system supports this feature.
Hyper Threading
Whether the processor uses Intel Hyper-Threading Technology,

which allows multithreaded software applications to execute
threads in parallel within each processor. This can be one of the
following:
disabledThe processor does not permit hyperthreading.
enabledThe processor allows for the parallel execution
of multiple threads.
and vendor.
to make sure the operating system supports this feature.

189
Name
Description
Core Multi Processing
Sets the state of logical processor cores per CPU in a package.

If you disable this setting, Intel Hyper Threading technology is
also disabled. This can be one of the following:
allEnables multiprocessing on all logical processor
cores.
1 through nSpecifies the number of logical processor
cores per CPU that can run on the server. To disable
multiprocessing and have only one logical processor core
per CPU running on the server, choose 1.
and vendor.
Execute Disabled Bit
Classifies memory areas on the server to specify where the

application code can execute. As a result of this classification,
the processor disables code execution if a malicious worm
attempts to insert code in the buffer. This setting helps to prevent
damage, worm propagation, and certain classes of malicious
buffer overflow attacks. This can be one of the following:
disabledThe processor does not classify memory areas.
enabledThe processor classifies memory areas.
and vendor.
Virtualization Technology (VT)
Whether the processor uses Intel Virtualization Technology,

which allows a platform to run multiple operating systems and
applications in independent partitions. This can be one of the
following:
disabledThe processor does not permit virtualization.
enabledThe processor allows multiple operating systems
in independent partitions.
and vendor.
Note

190
If you change this option, you must power cycle the

server before the setting takes effect.
Name
Description
Hardware Pre-fetcher
Whether the processor allows the Intel hardware prefetcher to

fetch streams of data and instruction from memory into the
unified second-level cache when necessary. This can be one of
the following:
disabledThe hardware prefetcher is not used.
enabledThe processor uses the hardware prefetcher
when cache issues are detected.
and vendor.
Note
Adjacent Cache Line Pre-fetcher
CPU Performance must be set to Custom in order to

specify this value. For any value other than Custom,
this option is overridden by the setting in the selected
CPU performance profile.
Whether the processor fetches cache lines in even/odd pairs

instead of fetching just the required line. This can be one of the
following:
disabledThe processor only fetches the required line.
enabledThe processor fetches both the required line
and its paired line.
and vendor.
Note
DCU Streamer Pre-fetch
CPU Performance must be set to Custom in order to

specify this value. For any value other than Custom,
this option is overridden by the setting in the selected
CPU performance profile.
Whether the processor uses the DCU IP Prefetch mechanism to

analyze historical cache access patterns and preload the most
relevant lines in the L1 cache. This can be one of the following:
disabledThe processor does not try to anticipate cache
read requirements and only fetches explicitly requested
lines.
enabledThe DCU prefetcher analyzes the cache read
pattern and prefetches the next line in the cache if it
determines that it may be needed.
and vendor.

191
Name
Description
DCU IP Pre-fetcher
Whether the processor uses the DCU IP Prefetch mechanism to

analyze historical cache access patterns and preload the most
relevant lines in the L1 cache. This can be one of the following:
disabledThe processor does not preload any cache data.
enabledThe DCU IP prefetcher preloads the L1 cache
with the data it determines to be the most relevant.
and vendor.
Direct Cache Access
Allows processors to increase I/O performance by placing data

from I/O devices directly into the processor cache. This setting
helps to reduce cache misses. This can be one of the following:
disabledData from I/O devices is not placed directly
into the processor cache.
enabledData from I/O devices is placed directly into
the processor cache.
and vendor.
Processor C State
Whether the system can enter a power savings mode during idle
periods. This can be one of the following:
disabledThe system remains in a high-performance
state even when idle.
enabledThe system can reduce power to system
components such as the DIMMs and CPUs.
and vendor.

192
Name
Description
Processor C1E
Allows the processor to transition to its minimum frequency

upon entering C1. This setting does not take effect until after
you have rebooted the server. This can be one of the following:
disabledThe CPU continues to run at its maximum
frequency in the C1 state.
enabledThe CPU transitions to its minimum frequency.
This option saves the maximum amount of power in the
C1 state.
and vendor.
Processor C3 Report
Whether the processor sends the C3 report to the operating

system. This can be one of the following:
disabledThe processor does not send the C3 report.
acpi-c2The processor sends the C3 report using the
advanced configuration and power interface (ACPI) C2
format.
acpi-c3The processor sends the C3 report using the
ACPI C3 format.
and vendor.
On the Cisco UCS B440 Server, the BIOS Setup menu uses
enabled and disabled for these options. If you specify acpi-c2
or acpi-c2, the server sets the BIOS value for that option to
enabled.
Processor C6 Report

enabledThe processor sends the C6 report.
and vendor.

193
Name
Description
Processor C7 Report

enabledThe processor sends the C7 report.
and vendor.
CPU Performance
Sets the CPU performance profile for the server. This can be
one of the following:
enterpriseFor M3 servers, all prefetchers and data reuse
are enabled. For M1 and M2 servers, data reuse and the
DCU IP prefetcher are enabled, and all other prefetchers
are disabled.
high-throughputData reuse and the DCU IP prefetcher
are enabled, and all other prefetchers are disabled.
hpcAll prefetchers are enabled and data reuse is
disabled. This setting is also known as high-performance
computing.
Max Variable MTRR Setting
Allows you to select the number of mean time to repair (MTRR)

variables. This can be one of the following:
auto-maxBIOS uses the default value for the processor.
8BIOS uses the number specified for the variable
MTRR.
and vendor.
Local X2 APIC
Allows you to set the type of Application Policy Infrastructure

Controller (APIC) architecture. This can be one of the following:
xapicUses the standard xAPIC architecture.
x2apicUses the enhanced x2APIC architecture to
support 32 bit addressability of processors.
autoAutomatically uses the xAPIC architecture that is
detected.
and vendor.

194
Name
Description
Power Technology
Enables you to configure the CPU power management settings

for the following options:
Enhanced Intel Speedstep Technology
Intel Turbo Boost Technology
Processor Power State C6
Power Technology can be one of the following:
disabledThe server does not perform any CPU power
management and any settings for the BIOS parameters
mentioned above are ignored.
Energy EfficientThe server determines the best settings
for the BIOS parameters mentioned above and ignores the
individual settings for these parameters.
performanceThe server automatically optimizes the
performance for the BIOS parameters mentioned above.
customThe server uses the individual settings for the
BIOS parameters mentioned above. You must select this
option if you want to change any of these BIOS
parameters.
and vendor.
Energy Performance
Allows you to determine whether system performance or energy

efficiency is more important on this server. This can be one of
the following:
performance
balanced-performance
balanced-energy
energy-efficient
and vendor.
Note
Power Technology must be set to Custom or the server

ignores the setting for this parameter.

195
Name
Description
Frequency Floor Override
Whether the CPU is allowed to drop below the maximum

non-turbo frequency when idle. This can be one of the following:
disabled The CPU can drop below the maximum
non-turbo frequency when idle. This option decreases
power consumption but may reduce system performance.
enabled The CPU cannot drop below the maximum
non-turbo frequency when idle. This option improves
system performance but may increase power consumption.
and vendor.
P-STATE Coordination
Allows you to define how BIOS communicates the P-state

support model to the operating system. There are 3 models as
defined by the Advanced Configuration and Power Interface
(ACPI) specification.
hw-allThe processor hardware is responsible for
coordinating the P-state among logical processors with
dependencies (all logical processors in a package).
sw-allThe OS Power Manager (OSPM) is responsible
for coordinating the P-state among logical processors with
dependencies (all logical processors in a physical package),
and must initiate the transition on all of the logical
processors.
sw-allThe OS Power Manager (OSPM) is responsible
for coordinating the P-state among logical processors with
dependencies (all logical processors in a package), and
may initiate the transition on any of the logical processors
in the domain.
and vendor.
Note

196
Power Technology must be set to Custom or the server

ignores the setting for this parameter.
Name
Description
DRAM Clock Throttling
Allows you to tune the system settings between the memory

bandwidth and power consumption. This can be one of the
following:
balanced DRAM clock throttling is reduced, providing
a balance between performance and power.
performanceDRAM clock throttling is disabled,
providing increased memory bandwidth at the cost of
additional power.
Energy EfficientDRAM clock throttling is increased
to improve energy efficiency.
and vendor.
Channel Interleaving
Whether the CPU divides memory blocks and spreads

contiguous portions of data across interleaved channels to enable
simultaneous read operations. This can be one of the following:
AutoThe CPU determines what interleaving is done.
1-waySome channel interleaving is used.
2-way
3-way
4-wayThe maximum amount of channel interleaving is
used.
and vendor.
Rank Interleaving
Whether the CPU interleaves physical ranks of memory so that

one rank can be accessed while another is being refreshed. This
1-waySome rank interleaving is used.
2-way
4-way
8-wayThe maximum amount of rank interleaving is
used.
and vendor.

197
Name
Description
Memory Interleaving
Whether the CPU interleaves the physical memory so that the

memory can be accessed while another is being refreshed. This
1-waySome memory interleaving is used.
2-way
4-way
and vendor.
Demand Scrub
Whether the system corrects single bit memory errors

encountered when the CPU or I/O makes a demand read. This
disabled Single bit memory errors are not corrected.
enabled Single bit memory errors are corrected in
memory and the corrected data is set in response to the
demand read.
and vendor.
Patrol Scrub
Whether the system actively searches for, and corrects, single

bit memory errors even in unused portions of the memory on
the server. This can be one of the following:
disabledThe system checks for memory ECC errors
only when the CPU reads or writes a memory address.
enabledThe system periodically reads and writes
memory searching for ECC errors. If any errors are found,
the system attempts to fix them. This option may correct
single bit errors before they become multi-bit errors, but
it may adversely affect performance when the patrol scrub
is running.
and vendor.

198
Name
Description
Altitude
The approximate number of meters above sea level at which the

physical server is installed. This can be one of the following:
autoThe CPU determines the physical elevation.
The server is approximately 300 meters above sea level.
The server is approximately 900 meters above sea level.
The server is approximately 1500 meters above sea
level.
The server is approximately 3000 meters above sea
level.
and vendor.

199
Name
Description
Package C State Limit
The amount of power available to the server components when

they are idle. This can be one of the following:
The server may enter any available C state.

The server provides all server components with full
power at all times. This option maintains the highest level
of performance and requires the greatest amount of power.
When the CPU is idle, the system slightly reduces the
power consumption. This option requires less power than
C0 and allows the server to return quickly to high
performance mode.
When the CPU is idle, the system reduces the power
consumption further than with the C1 option. This requires
less power than C1 or C0, but it takes the server slightly
longer to return to high performance mode.
consumption further than with the C3 option. This option
saves more power than C0, C1, or C3, but there may be
performance issues until the server returns to full power.
consumption further than with the C1 option. This requires
less power than C1 or C0, but it takes the server slightly
longer to return to high performance mode.
When the CPU is idle, the server makes a minimal
amount of power available to the components. This option
saves the maximum amount of power but it also requires
the longest time for the server to return to high
performance mode.
When the CPU is idle, the server makes a minimal
amount of power available to the components. This option
saves more power than C7, but it also requires the longest
time for the server to return to high performance mode.
and vendor.

200
Name
Description
CPU Hardware Power Management
Enables processor Hardware Power Management (HWPM).

and vendor.
HWPM is disabled.
HWPM native mode is enabled.
HWPM Out-Of-Box mode is enabled.
Intel Directed I/O BIOS Settings

The following table lists the Intel Directed I/O BIOS settings that you can configure through a BIOS policy
or the default BIOS settings:
Name
Description
VT for Directed IO
Whether the processor uses Intel Virtualization Technology for

Directed I/O (VT-d). This can be one of the following:
disabledThe processor does not use virtualization
technology.
enabledThe processor uses virtualization technology.
and vendor.
Note
Interrupt Remap
This option must be enabled if you want to change any

of the other Intel Directed I/O BIOS settings.
Whether the processor supports Intel VT-d Interrupt Remapping.

disabledThe processor does not support remapping.
enabledThe processor uses VT-d Interrupt Remapping
as required.
and vendor.

201
Name
Description
Coherency Support
Whether the processor supports Intel VT-d Coherency. This can

disabledThe processor does not support coherency.
enabledThe processor uses VT-d Coherency as required.
and vendor.
ATS Support
Whether the processor supports Intel VT-d Address Translation

Services (ATS). This can be one of the following:
disabledThe processor does not support ATS.
enabledThe processor uses VT-d ATS as required.
and vendor.
Pass Through DMA Support
Whether the processor supports Intel VT-d Pass-through DMA.

disabledThe processor does not support pass-through
DMA.
enabledThe processor uses VT-d Pass-through DMA
as required.
and vendor.
RAS Memory BIOS Settings

The following table lists the RAS memory BIOS settings that you can configure through a BIOS policy or
the default BIOS settings:

202
Name
Description
Memory RAS Config
How the memory reliability, availability, and serviceability

(RAS) is configured for the server. This can be one of the
following:
maximum-performanceSystem performance is
optimized.
mirroringSystem reliability is optimized by using half
the system memory as backup.
lockstepIf the DIMM pairs in the server have an
identical type, size, and organization and are populated
across the SMI channels, you can enable lockstep mode
to minimize memory access latency and provide better
performance. Lockstep is enabled by default for B440
servers.
and vendor.
NUMA
Whether the BIOS supports NUMA. This can be one of the

following:
disabledThe BIOS does not support NUMA.
enabledThe BIOS includes the ACPI tables that are
required for NUMA-aware operating systems. If you
enable this option, the system must disable Inter-Socket
Memory interleaving on some platforms.
and vendor.
Mirroring Mode
Memory mirroring enhances system reliability by keeping two

identical data images in memory.
This option is only available if you choose the mirroring option
for Memory RAS Config. It can be one of the following:
inter-socketMemory is mirrored between two Integrated
Memory Controllers (IMCs) across CPU sockets.
intra-socketOne IMC is mirrored with another IMC in
the same socket.
and vendor.

203
Name
Description
Sparing Mode
Sparing optimizes reliability by holding memory in reserve so

that it can be used in case other DIMMs fail. This option
provides some memory redundancy, but does not provide as
much redundancy as mirroring. The available sparing modes
depend on the current memory population.
This option is only available if you choose sparing option for
Memory RAS Config. It can be one of the following:
dimm-sparingOne DIMM is held in reserve. If a DIMM
fails, the contents of a failing DIMM are transferred to the
spare DIMM.
rank-sparingA spare rank of DIMMs is held in reserve.
If a rank of DIMMs fails, the contents of the failing rank
are transferred to the spare rank.
and vendor.
LV DDR Mode
Whether the system prioritizes low voltage or high frequency

memory operations. This can be one of the following:
power-saving-modeThe system prioritizes low voltage
memory operations over high frequency memory
operations. This mode may lower memory frequency in
order to keep the voltage low.
performance-modeThe system prioritizes high
frequency operations over low voltage operations.
and vendor.
DRAM Refresh Rate

set dram-refresh-rate-config
dram-refresh
The refresh interval rate for internal memory. This can be one
of the following:
1x
2x
3x
4x
auto
and vendor.

204
Name
Description
DDR3 Voltage Selection
The voltage to be used by the dual-voltage RAM. This can be

ddr3-1500mv
ddr3-1350mv
and vendor.
Serial Port BIOS Settings

The following table lists the serial port BIOS settings that you can configure through a BIOS policy or the
Name
Description
Serial Port A
Whether serial port A is enabled or disabled. This can be one

of the following:
disabledThe serial port is disabled.
enabledThe serial port is enabled.
and vendor.
USB BIOS Settings

The following table lists the USB BIOS settings that you can configure through a BIOS policy or the default
BIOS settings:
Name
Description
Make Device Non Bootable
Whether the server can boot from a USB device. This can be
disabledThe server can boot from a USB device.
enabledThe server cannot boot from a USB device.
and vendor.

205
Name
Description
Legacy USB Support
Whether the system supports legacy USB devices. This can be

disabledUSB devices are only available to EFI
applications.
enabledLegacy USB support is always available.
autoDisables legacy USB support if no USB devices
are connected.
and vendor.
USB System Idle Power Optimizing

Setting
Whether the USB System Idle Power Optimizing setting is used

to reduce USB EHCI idle power consumption. Depending upon
the value you choose, this setting can have an impact on
performance. This can be one of the following:
high-performanceThe USB System Idle Power
Optimizing setting is disabled, because optimal
performance is preferred over power savings.
Selecting this option can significantly improve
performance. We recommend you select this option unless
your site has server power restrictions.
lower-idle-powerThe USB System Idle Power
Optimizing setting is enabled, because power savings are
preferred over optimal performance.
and vendor.
USB Front Panel Access Lock
USB front panel lock is configured to enable or disable the front

panel access to USB ports. This can be one of the following:
disabled
enabled
and vendor.

206
Name
Description
Port 60/64 Emulation
Whether the system supports 60h/64h emulation for complete

USB keyboard legacy support. This can be one of the following:
disabled60h/64 emulation is not supported.
enabled60h/64 emulation is supported.
You should select this option if you are using a non-USB
aware operating system on the server.
and vendor.
USB Port:Front
Whether the front panel USB devices are enabled or disabled.

disabledDisables the front panel USB ports. Devices
connected to these ports are not detected by the BIOS and
operating system.
enabledEnables the front panel USB ports. Devices
connected to these ports are detected by the BIOS and
operating system.
and vendor.
USB Port:Internal
Whether the internal USB devices are enabled or disabled. This

disabledDisables the internal USB ports. Devices
operating system.
enabledEnables the internal USB ports. Devices
operating system.
and vendor.

207
Name
Description
USB Port:KVM
Whether the KVM ports are enabled or disabled. This can be

disabledDisables the KVM keyboard and/or mouse
devices. Keyboard and/or mouse will not work in the KVM
window.
enabledEnables the KVM keyboard and/or mouse
devices.
and vendor.
USB Port:Rear
Whether the rear panel USB devices are enabled or disabled.

disabledDisables the rear panel USB ports. Devices
operating system.
enabledEnables the rear panel USB ports. Devices
operating system.
and vendor.
USB Port:SD Card
Whether the SD card drives are enabled or disabled. This can

disabledDisables the SD card drives. The SD card drives
are not detected by the BIOS and operating system.
enabledEnables the SD card drives.
and vendor.
USB Port:VMedia
Whether the virtual media devices are enabled or disabled. This

disabledDisables the vMedia devices.
enabledEnables the vMedia devices.
and vendor.

208
Name
Description
All USB Devices
Whether all physical and virtual USB devices are enabled or

disabled. This can be one of the following:
disabledAll USB devices are disabled.
enabledAll USB devices are enabled.
and vendor.
xHCI Mode Support
Whether xHCI mode support is enabled or disabled. This can

disabledxHCI mode support is disabled.
enabledxHCI mode support is enabled.
and vendor.
PCI Configuration BIOS Settings

The following table lists the PCI configuration BIOS settings that you can configure through a BIOS policy
Name
Description
Max Memory Below 4G
Whether the BIOS maximizes memory usage below 4GB for

an operating system without PAE support, depending on the
system configuration. This can be one of the following:
disabledDoes not maximize memory usage. Choose
this option for all operating systems with PAE support.
enabledMaximizes memory usage below 4GB for an
operating system without PAE support.
and vendor.

209
Name
Description
Memory Mapped IO Above 4Gb Config Whether to enable or disable memory mapped I/O of 64-bit PCI
devices to 4GB or greater address space. Legacy option ROMs
are not able to access addresses above 4GB. PCI devices that
are 64-bit compliant but use a legacy option ROM may not
function correctly with this setting enabled. This can be one of
the following:
disabledDoes not map I/O of 64-bit PCI devices to 4GB
or greater address space.
enabledMaps I/O of 64-bit PCI devices to 4GB or
greater address space.
and vendor.
VGA Priority
Allows you to set the priority for VGA graphics devices if

multiple VGA devices are found in the system. This can be one
of the following:
onboardPriority is given to the onboard VGA device.
BIOS post screen and OS boot are driven through the
onboard VGA port.
offboardPriority is given to the PCIE Graphics adapter.
BIOS post screen and OS boot are driven through the
external graphics adapter port.
onboard-vga-disabledPriority is given to the PCIE
Graphics adapter, and the onboard VGA device is disabled.
Note
The vKVM does not function when the onboard

VGA is disabled.

and vendor.
Note

210
Only onboard VGA devices are supported with Cisco

UCS B-Series servers.
Name
Description
ASPM Support
Allows you to set the level of ASPM (Active Power State

Management) support in the BIOS. This can be one of the
following:
disabledASPM support is disabled in the BIOS.
autoThe CPU determines the power state.
forcel0Force all links to L0 standby (L0s) state.
and vendor.
QPI BIOS Settings

The following table lists the QPI BIOS settings that you can configure through a BIOS policy or the default
BIOS settings:
Name
Description
QPI Link Frequency
The Intel QuickPath Interconnect (QPI) link frequency, in megatransfers

per second (MT/s). This can be one of the following:
6400
7200
8000
9600
AutoThe CPU determines the QPI link frequency.
Platform DefaultThe BIOS uses the value for this attribute
contained in the BIOS defaults for the server type and vendor.

211
Name
Description
QPI Snoop Mode

home-snoopThe snoop is always spawned by the home agent
(centralized ring stop) for the memory controller. This mode has
a higher local latency than early snoop, but it provides extra
resources for a larger number of outstanding transactions.
cluster-on-dieThis mode is available only for processors that
have 10 or more cores. It is the best mode for highly NUMA
optimized workloads.
home-directory-snoop-with-osb
early-snoopThe distributed cache ring stops can send a snoop
probe or a request to another caching agent directly. This mode
has lower latency and it is best for workloads that have shared
data sets across threads and can benefit from a cache-to-cache
transfer, or for workloads that are not NUMA optimized.
auto
home-directory-snoop-with-osb
Platform DefaultThe BIOS uses the value for this attribute
contained in the BIOS defaults for the server type and vendor.
LOM and PCIe Slots BIOS Settings

The following table lists the USB BIOS settings that you can configure through a BIOS policy or the default
BIOS settings:
Name
Description
PCIe Slot:SAS OptionROM
Whether Option ROM is available on the SAS port.

disabledThe expansion slot is not available.
enabledThe expansion slot is available.
uefi-only
The expansion slot is available for UEFI
only.
legacy-onlyThe expansion slot is available
for legacy only.
Platform DefaultThe BIOS uses the value
for this attribute contained in the BIOS
defaults for the server type and vendor.

212
Name
Description
PCIe Slot:n Link Speed
This option allows you to restrict the maximum

speed of an adapter card installed in PCIe slot n.
gen12.5GT/s (gigatransfers per second) is
the maximum speed allowed.
gen25GT/s is the maximum speed allowed.
gen38GT/s is the maximum speed allowed.
autoThe maximum speed is set
automatically.
disabledThe maximum speed is not
restricted.
PCIe Slot:n OptionROM
Whether Option ROM is available on the port. This

uefi-only
only.
for legacy only.

213
Name
Description
PCIe Slot:HBA OptionROM
Whether Option ROM is available on the HBA port.

uefi-only
only.
for legacy only.
PCIe Slot:MLOM OptionROM
Whether Option ROM is available on the MLOM

port. This can be one of the following:
uefi-only
only.
for legacy only.
PCIe Slot:N1 OptionROM

uefi-only
only.
for legacy only.

214
Name
Description
PCIe Slot:N2 OptionROM

DisabledThe expansion slot is not available.
EnabledThe expansion slot is available.
uefi-only
only.
for legacy only.
Whether Option ROM is available on the 10G LOM

port. This can be one of the following:
PCIe 10G LOM 2 Link

PCI ROM CLP
set pci-rom-clp-support pci-rom-clp-config

SIOC1 Option ROM
set sioc1-optionrom-config sioc1-optionrom

uefi-only
only.
for legacy only.

215
Name
SIOC2 Option ROM
set sioc2-optionrom-config sioc2-optionrom
Description
uefi-only
only.
for legacy only.
SB MEZZ1 Option ROM

set sbmezz1-optionrom-config sbmezz1-optionrom

uefi-only
only.
for legacy only.
IOE Slot1 Option ROM

set ioeslot1-optionrom-config ioeslot1-optionrom

uefi-only
only.
for legacy only.

216
Name
Description
IOE MEZZ 1 Option ROM
set ioemezz1-optionrom-config ioemezz1-optionrom

uefi-only
only.
for legacy only.
IOE Slot2 Option ROM
set ioeslot2-optionrom-config ioeslot2-optionrom

uefi-only
only.
for legacy only.
IO ENVME1 Option ROM
set ioenvme1-optionrom-config ioenvme1-optionrom

uefi-only
only.
for legacy only.

217
Name
Description
IO ENVME2 Option ROM
set ioenvme2-optionrom-config ioenvme2-optionrom

uefi-only
only.
for legacy only.
SBNVME1 Option ROM
set sbnvme1-optionrom-config sbnvme1-optionrom

uefi-only
only.
for legacy only.
Graphics Configuration BIOS Settings

The following tables list the graphics configuration BIOS settings that you can configure through a BIOS
policy or the default BIOS settings:
Name
Description
Integrated Graphics
Enables integrated graphics. This can be one of the following:

and vendor.
Integrated graphic is enabled.
Integrated graphics is disabled.

218
Name
Description
Aperture Size
Allows you to set the size of mapped memory for the integrated
graphics controller. This can be one of the following:
and vendor.
Onboard Graphics
Enables onboard graphics (KVM). This can be one of the

following:
and vendor.
Onboard graphics is enabled.
Onboard graphics is disabled.
Boot Options BIOS Settings

The following table lists the boot options BIOS settings that you can configure through a BIOS policy or the
Name
Description
Boot Option Retry
Whether the BIOS retries NON-EFI based boot options without

waiting for user input. This can be one of the following:
disabledWaits for user input before retrying NON-EFI
based boot options.
enabledContinually retries NON-EFI based boot options
without waiting for user input.
and vendor.

219
Name
Description
Intel Entry SAS RAID
Whether the Intel SAS Entry RAID Module is enabled. This

disabledThe Intel SAS Entry RAID Module is disabled.
enabledThe Intel SAS Entry RAID Module is enabled.
and vendor.
Intel Entry SAS RAID Module
How the Intel SAS Entry RAID Module is configured. This can
it-ir-raidConfigures the RAID module to use Intel IT/IR
RAID.
intel-esrtiiConfigures the RAID module to use Intel
Embedded Server RAID Technology II.
and vendor.
Onboard SCU Storage Support
Whether the onboard software RAID controller is available to

the server. This can be one of the following:
disabledThe software RAID controller is not available.
enabledThe software RAID controller is available.
and vendor.
Note
BIOS parameter virtualization capability in Cisco UCS Manager maps a unified set of BIOS settings in
a service profile to the actual BIOS supporting parameters. However, not all BIOS setting items are
applicable to every server model/platform. When you create a custom BIOS policy and have the Boot
Option Retry selected, and when there is no bootable option available, the reboot fails on the Cisco UCS
B420 M3 or Cisco UCS B420 M4 servers and Cisco UCS Manager displays this message : Reboot and
Select proper Boot device or Insert Boot Media in selected Boot device and press a key. You must manually
set a boot option after the boot path is corrected, in order to enable the servers to reboot after a power
outage. For more information about BIOS default server policies and the BIOS options and their default
settings, see BIOS Policy, on page 226 and Server BIOS Settings, on page 185.

220
Server Management BIOS Settings

The following tables list the server management BIOS settings that you can configure through a BIOS policy
General Settings
Name
Description
Assert Nmi on Serr
Whether the BIOS generates a non-maskable interrupt (NMI)

and logs an error when a system error (SERR) occurs. This can
disabledThe BIOS does not generate an NMI or log an
error when a SERR occurs.
enabledThe BIOS generates an NMI and logs an error
when a SERR occurs. You must enable this setting if you
want to enable Assert Nmi on Perr.
and vendor.
Assert Nmi on Perr
Whether the BIOS generates a non-maskable interrupt (NMI)

and logs an error when a processor bus parity error (PERR)
occurs. This can be one of the following:
disabledThe BIOS does not generate an NMI or log an
error when a PERR occurs.
enabledThe BIOS generates an NMI and logs an error
when a PERR occurs. You must enable Assert Nmi on
Serr to use this setting.
and vendor.

221
Name
Description
OS Boot Watchdog Timer
Whether the BIOS programs the watchdog timer with a

predefined timeout value. If the operating system does not
complete booting before the timer expires, the CIMC resets the
system and an error is logged. This can be one of the following:
disabledThe watchdog timer is not used to track how
long the server takes to boot.
enabledThe watchdog timer tracks how long the server
takes to boot. If the server does not boot within the
predefined length of time, the CIMC resets the system and
logs an error.
and vendor.
This feature requires either operating system support or Intel
Management software.
OS Boot Watchdog Timer Timeout

Policy
What action the system takes if the watchdog timer expires.

power-offThe server is powered off if the watchdog
timer expires during OS boot.
resetThe server is reset if the watchdog timer expires
during OS boot.
and vendor.
This option is only available if you enable the OS Boot
Watchdog Timer.

222
Name
Description
OS Boot Watchdog Timer Timeout
What timeout value the BIOS uses to configure the watchdog

timer. This can be one of the following:
5-minutesThe watchdog timer expires 5 minutes after
the OS begins to boot.
and vendor.
This option is only available if you enable the OS Boot
Watchdog Timer.
FRB-2 Timer
Whether the FRB-2 timer is used to recover the system if it

hangs during POST. This can be one of the following:
DisabledThe FRB-2 timer is not used.
EnabledThe FRB-2 timer is started during POST and
used to recover the system if necessary.
and vendor.

223
Console Redirection Settings

Name
Description
Console Redirection
Allows a serial port to be used for console redirection during

POST and BIOS booting. After the BIOS has booted and the
operating system is responsible for the server, console redirection
is irrelevant and has no effect. This can be one of the following:
disabledNo console redirection occurs during POST.
serial-port-aEnables serial port A for console
redirection during POST. This option is valid for blade
servers and rack-mount servers.
serial-port-bEnables serial port B for console
redirection and allows it to perform server management
tasks. This option is only valid for rack-mount servers.
and vendor.
Note
Flow Control
If you enable this option, you also disable the display

of the Quiet Boot logo screen during POST.
Whether a handshake protocol is used for flow control. Request

to Send / Clear to Send (RTS/CTS) helps to reduce frame
collisions that can be introduced by a hidden terminal problem.
noneNo flow control is used.
rts-ctsRTS/CTS is used for flow control.
and vendor.
Note

224
This setting must match the setting on the remote

terminal application.
Name
Description
BAUD Rate
What BAUD rate is used for the serial port transmission speed.
If you disable Console Redirection, this option is not available.
9600A 9600 BAUD rate is used.
and vendor.
Note
Terminal Type

What type of character formatting is used for console redirection.

pc-ansiThe PC-ANSI terminal font is used.
vt100A supported vt100 video terminal and its character
set are used.
vt100-plusA supported vt100-plus video terminal and
its character set are used.
vt-utf8A video terminal with the UTF-8 character set
is used.
and vendor.
Note
Legacy OS Redirect

Whether redirection from a legacy operating system, such as

DOS, is enabled on the serial port. This can be one of the
following:
disabledThe serial port enabled for console redirection
is hidden from the legacy operating system.
enabled The serial port enabled for console redirection
is visible to the legacy operating system.
and vendor.

225
BIOS Policy
Name
Description
Putty KeyPad
Allows you to change the action of the PuTTY function keys

and the top row of the numeric keypad. This can be one of the
following:
set console-redir-config
putty-function-keypad
vt100The function keys generate ESC OP through ESC

O[.
linuxMimics the Linux virtual console. Function keys
F6 to F12 behave like the default mode, but F1 to F5
generate ESC [[A through ESC [[E.
xtermr6Function keys F5 to F12 behave like the default
mode. Function keys F1 to F4 generate ESC OP through
ESC OS, which are the sequences produced by the top
row of the keypad on Digital terminals.
scoThe function keys F1 to F12 generate ESC [M
through ESC [X. The function and shift keys generate ESC
[Y through ESC [j. The control and function keys generate
ESC [k through ESC [v. The shift, control and function
keys generate ESC [w through ESC [{.
escnThe default mode. The function keys match the
general behavior of Digital terminals. The function keys
generate sequences such as ESC [11~ and ESC [12~.
vt400The function keys behave like the default mode.
The top row of the numeric keypad generates ESC OP
through ESC OS.
and vendor.
BIOS Policy
The BIOS policy is a policy that automates the configuration of BIOS settings for a server or group of servers.
You can create global BIOS policies available to all servers in the root organization, or you can create BIOS
policies in sub-organizations that are only available to that hierarchy.
To use a BIOS policy, do the following:
1 Create the BIOS policy in Cisco UCS Manager.
2 Assign the BIOS policy to one or more service profiles.
3 Associate the service profile with a server.
During service profile association, Cisco UCS Manager modifies the BIOS settings on the server to match
the configuration in the BIOS policy. If you do not create and assign a BIOS policy to a service profile, the
server uses the default BIOS settings for that server platform.

226
Default BIOS Settings
Default BIOS Settings

Cisco UCS Manager includes a set of default BIOS settings for each type of server supported by Cisco UCS.
The default BIOS settings are available only in the root organization and are global. Only one set of default
BIOS settings can exist for each server platform supported by Cisco UCS. You can modify the default BIOS
settings, but you cannot create an additional set of default BIOS settings.
Each set of default BIOS settings are designed for a particular type of supported server and are applied to all
servers of that specific type which do not have a BIOS policy included in their service profiles.
Unless a Cisco UCS implementation has specific needs that are not met by the server-specific settings, we
recommend that you use the default BIOS settings that are designed for each type of server in the Cisco UCS
domain.
Cisco UCS Manager applies these server platform-specific BIOS settings as follows:
The service profile associated with a server does not include a BIOS policy.
The BIOS policy is configured with the platform-default option for a specific setting.
You can modify the default BIOS settings provided by Cisco UCS Manager. However, any changes to the
default BIOS settings apply to all servers of that particular type or platform. If you want to modify the BIOS
settings for only certain servers, we recommend that you use a BIOS policy.
Creating a BIOS Policy

Note
Cisco UCS Manager pushes BIOS configuration changes through a BIOS policy or default BIOS settings
to the Cisco Integrated Management Controller (CIMC) buffer. These changes remain in the buffer and
do not take effect until the server is rebooted.
We recommend that you verify the support for BIOS settings in the server that you want to configure.
Some settings, such as Mirroring Mode for RAS Memory, are not supported by all Cisco UCS servers.
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click BIOS Policies and select Create BIOS Policy.

On the Main page of the Create BIOS Policy wizard, enter a name for the BIOS policy in the Name field.
object is saved.
Step 6
In the Create BIOS Policy wizard, do the following to configure the BIOS settings:

227
Modifying the BIOS Defaults
a) If you want to change a BIOS setting, click the desired radio button or make the appropriate choice from
the drop-down list.
For descriptions and information about the options for each BIOS setting, see the following topics:
Main page: Main BIOS Settings, on page 186
Processor page: Processor BIOS Settings, on page 188
Intel Directed IO page: Intel Directed I/O BIOS Settings, on page 201
RAS Memory page: RAS Memory BIOS Settings, on page 202
Serial Port page: Serial Port BIOS Settings, on page 205
USB page: USB BIOS Settings, on page 205
PCI Configuration page: PCI Configuration BIOS Settings, on page 209
Boot Options page: Boot Options BIOS Settings, on page 219
Server Management page: Server Management BIOS Settings, on page 221
b) Click Next after each page.
Step 7
After you configure all of the BIOS settings for the policy, click Finish.
Modifying the BIOS Defaults

We recommend that you verify the support for BIOS settings in the server that you want to configure. Some
settings, such as Mirroring Mode for RAS Memory, are not supported by all Cisco UCS servers.
Unless a Cisco UCS implementation has specific needs that are not met by the server-specific settings, we
recommend that you use the default BIOS settings that are designed for each type of server in the Cisco UCS
domain.
Procedure
Step 1
Step 2
Step 3

Step 4
Expand BIOS Defaults and select the server model number for which you want to modify the default BIOS
settings.
In the Work pane, click the appropriate tab and then click the desired radio button or make a choice from the
drop-down list to modify the default BIOS settings:
For descriptions and information about the options for each BIOS setting, see the following topics. Not all
BIOS settings are available for each type of server.
Step 5
Main tab: Main BIOS Settings, on page 186

Advanced tab:

228
Viewing the Actual BIOS Settings for a Server
Processor subtab: Processor BIOS Settings, on page 188

Intel Directed IO subtab: Intel Directed I/O BIOS Settings, on page 201
RAS Memory subtab: RAS Memory BIOS Settings, on page 202
Serial Port subtab: Serial Port BIOS Settings, on page 205
USB subtab: USB BIOS Settings, on page 205
PCI Configuration subtab: PCI Configuration BIOS Settings, on page 209
Boot Options tab: Boot Options BIOS Settings, on page 219
Server Management tab: Server Management BIOS Settings, on page 221
Step 6
Click Save Changes.
Viewing the Actual BIOS Settings for a Server

Follow this procedure to see the actual BIOS settings on a server.
Procedure
Step 1
Step 2
Step 3
Step 4

Choose the server for which you want to view the actual BIOS settings.
On the Work pane, click the Inventory tab.
Step 5
Step 6
Click the Motherboard subtab.

In the BIOS Settings area, click the Expand icon to the right of the heading to open that area.
Each tab in the BIOS Settings area displays the settings for that server platform. Some of the tabs contain
subtabs with additional information.
Trusted Platform Module

Trusted Platform Module
Important
The Trusted Platform Module (TPM) is a component that can securely store artifacts that are used to authenticate
the server. These artifacts can include passwords, certificates, or encryption keys. A TPM can also be used

229
Intel Trusted Execution Technology
to store platform measurements that help ensure that the platform remains trustworthy. Authentication (ensuring
that the platform can prove that it is what it claims to be) and attestation (a process helping to prove that a
platform is trustworthy and has not been breached) are necessary steps to ensure safer computing in all
environments. It is a requirement for the Intel Trusted Execution Technology (TXT) security feature, which
must be enabled in the BIOS settings for a server equipped with a TPM. Cisco UCS modular servers, and M4
blade and rack-mount servers include support for TPM. TPM is enabled by default on these servers.
Important
If you upgrade Cisco UCS Manager to Release 2.2(4) and higher, TPM is enabled.
When TPM is enabled and you downgrade Cisco UCS Manager from Release 2.2(4), TPM is disabled.
Intel Trusted Execution Technology

Intel Trusted Execution Technology (TXT) provides greater protection for information that is used and stored
on the business server. A key aspect of that protection is the provision of an isolated execution environment
and associated sections of memory where operations can be conducted on sensitive data, invisible to the rest
of the system. Intel TXT provides for a sealed portion of storage where sensitive data such as encryption keys
can be kept, helping to shield them from being compromised during an attack by malicious code. Cisco UCS
M4 blade and rack-mount servers include support for TXT. TXT is disabled by default on these servers.
TXT can be enabled only after TPM, Intel Virtualization technology (VT) and Intel Virtualization Technology
for Directed I/O (VT-d) are enabled. When you only enable TXT, it also implicitly enables TPM, VT, and
VT-d.
Configuring Trusted Platform

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the node for the organization where you want to configure TPM.
Expand BIOS Policies and select the BIOS policy for which you want to configure TPM.
In the Work pane, click the Advanced tab.
Step 6
Step 7
Click the Trusted Platform subtab.

To configure TPM, click one of the following:
Option
Description
disabled
Disables TPM
enabled
Enables TPM

230
Step 8
Step 9
Option
Description
Platform Default
Enables TPM
To configure TXT, click one of the following:

Option
Description
disabled
Disables TXT
enabled
Enables TXT
Platform Default
Disables TXT
Click Save Changes.

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the node for the organization where you want to configure TPM.
Expand BIOS Policies and select the BIOS policy for which you want to configure TPM.
In the Work pane, click the Advanced tab.
Step 6
Step 7
Click the Trusted Platform subtab.

To configure TPM, click one of the following:
Step 8
Option
Description
disabled
Disables TPM
enable
Enables TPM
Platform Default
Enables TPM
To configure TXT, click one of the following:

Option
Description
disabled
Disables TXT
enable
Enables TXT

231
Clearing TPM for a Modular Server
Step 9
Option
Description
Platform Default
Disables TXT
Click Save Changes.
Clearing TPM for a Modular Server

Important
You can clear TPM only on the modular servers that include support for TPM.
Caution
data.
Before You Begin

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

Viewing TPM Properties

Important

232
Procedure
Step 1
Step 2
Step 3
Step 4
Choose the server for which you want to view the TPM settings.
On the Work pane, click the Inventory tab.
Step 5
Click the Motherboard subtab.

When there is no mechanism for the Operating System to label Ethernet interfaces in a consistent manner, it
becomes difficult to manage network connections with server configuration changes. Consistent Device
Naming (CDN), introduced in Cisco UCS Manager Release 2.2(4), allows Ethernet interfaces to be named
in a consistent manner. This makes Ethernet interface names more persistent when adapter or other configuration
changes are made.
To configure CDN for a vNIC, do the following:
Enable consistent device naming in the BIOS policy.
Associate the BIOS policy with a service profile.
Configure consistent naming for a vNIC.
Guidelines and Limitations for Consistent Device Naming

CDN is supported only on Windows 2012 R2. It is not supported on any other Operating System.
Consistent device naming (CDN) is supported on all M3 and higher blade and rack-mount servers.
BIOS and adapter firmware must be part of the Release 2.2(4) bundle to support CDN.
In Cisco UCS Manager Release 3.1, CDN is supported on the following adapters:
Cisco UCS VIC 1385 (UCSC-PCIE-C40Q-03)
Cisco UCS VIC 1387 (UCSC-MLOM-C40Q-03)
In Cisco UCS Manager Release 2.2(4), CDN is supported only on the following adapters:
Cisco UCS VIC 1225 (UCSC-PCIE-CSC-02)
Cisco UCS MLOM 1227 (UCSC-MLOM-CSC-02)
Cisco UCS VIC 1225T (UCSC-PCIE-C10T-02)
Cisco UCS MLOM 1227T (UCSC-MLOM-C10T-02)
Cisco UCS VIC 1240 (UCSB-MLOM-40G-01)

233
Guidelines and Limitations for Consistent Device Naming
Cisco UCS VIC 1280 (UCS-VIC-M82-8P)

Cisco UCS VIC 1340 (UCSB-MLOM-40G-03)
Cisco UCS VIC 1380 (UCSB-VIC-M83-8P)
CDN is not supported for vNIC template and dynamic vNIC.
Multiple vNICs within the same service profile cannot have the same CDN name.
When a CDN name is not specified for a vNIC, the vNIC name is used as the CDN name.
The CDN name that you configure for a vNIC appears as Admin CDN Name. The CDN name that is
finally applied to the vNIC appears as Oper CDN Name. For example, if the Admin CDN Name for
a vNIC called "vnic0" is cdn0, then the Oper CDN Name for this vNIC will be cdn0, but if the Admin
CDN Name for the same vNIC is not specified, the Oper CDN Name will be vnic0.
In Cisco UCS Manager Release 3.1, downgrade of the adapter firmware is prevented if a CDN-enabled
BIOS policy is assigned to a server.
In Cisco UCS Manager Release 2.2(4), downgrade of Cisco UCS Manager is prevented if CDN is enabled
in a BIOS policy that is assigned to an associated server.
In Cisco UCS Manager Release 2.2(4), downgrade of the BIOS firmware is prevented if a CDN-enabled
In Cisco UCS Manager Release 2.2(4), downgrade of the adapter firmware is prevented if a CDN-enabled
When the applied BIOS policy is changed from CDN-disabled to CDN-enabled or from CDN-enabled
to CDN-disabled, the host reboots with a warning, irrespective of whether reboot on BIOS update is
enabled or not.
It is recommended that you enable CDN in the BIOS policy and add CDN names to the vNICS before
the Windows Operating System is installed.
If the Windows Operating System is already installed on the server and CDN is then enabled in the
BIOS policy, do the following:
1 Uninstall the network drivers.
2 Scan the system for hidden devices and uninstall them.
3 Rescan the system for new hardware and install the network drivers again.
If this is not done, the vNICs will not come up with the configured CDN names.
When the applied BIOS policy is changed from CDN-disabled to CDN-enabled or from CDN-enabled
to CDN-disabled on a service profile, do the following:
1 Uninstall the network drivers.
2 Scan the system for hidden devices and delete them.
3 Re-scan the system for new hardware and install the network drivers again.

234
Configuring Consistent Device Naming in a BIOS Policy
Note
When the BIOS policy is changed from CDN-enabled to CDN-disabled, ensure that the
CDN names are removed from all the vNICs on the system.
If any change is made to the vNICs, the BDF of all the devices on the system also changes. Following
are some of the scenarios that trigger a change in the BDF of all the vNICs present on the system:
When a vNIC is added or deleted
When a vNIC is moved from one adapter on the system to another adapter on the system
When these changes are made to the system, do the following:
1 Uninstall the network driver from all the present network interfaces.
2 Scan the system for hidden devices and uninstall them.
3 Re-scan the system for new hardware and install the network driver on the network controllers again.
If the hidden devices are not deleted, the CDN names of the network adapters will not appear as configured
on Cisco UCS Manager.
CDN with a Mixed Set of Adapters
When a CDN name is configured for a vNIC in a system with a mixed set of CDN-supported adapters and
CDN-unsupported adapters, then system placement may not place CDN-configured vNICs on adapters that
support CDN.
If CDN is enabled in the BIOS policy, and system placement places a CDN-configured vNIC (Admin CDN
configured) on an adapter that does not support CDN, an info fault will be raised, but the configuration issue
for the service profile will be ignored.
If CDN is enabled in the BIOS policy, and system placement places a vNIC (Admin CDN not configured)
on an adapter that does not support CDN, an info fault will be raised, but the configuration issue for the service
profile will be ignored. The Oper CDN Name in this case will be empty and will not be derived from the
vNIC name.
If you want to deploy the CDN name as the host network interface name for a server, you must manually
place a vNIC on a supported adapter.
Configuring Consistent Device Naming in a BIOS Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the node for the organization where you want to configure Consistent Device Naming (CDN).
Step 6
In the Properties area, click one of the following in the Consistent Device Naming field to configure CDN:
Expand BIOS Policies and select the BIOS policy for which you want to configure CDN.
In the Work pane, click the Main tab.

235
Configuring a CDN Name for a vNIC
Step 7
Option
Description
disabled
Disables CDN in the BIOS policy
enable
Enables CDN in the BIOS policy
Platform Default
The BIOS uses the value for this attribute contained in the BIOS defaults
for the server type and vendor.
Click Save Changes.
Configuring a CDN Name for a vNIC

When a CDN name is not specified for a vNIC, the vNIC name is used as the CDN name.
Procedure
Step 1
Step 2
Step 3
Step 4

Expand the node for the organization that contains the vNIC for which you want to configure a CDN name.
Expand the service profile and vNICs node that contain the vNIC for which you want to configure a CDN
name.
Select the vNIC.
Step 5
Step 6
Step 7
Step 8
In the Properties area, enter the CDN name for the vNIC in theAdmin CDN Name field.
Note
The CDN name that you configure for a vNIC appears as Admin CDN Name. The CDN name that
is finally applied to the vNIC appears as Oper CDN Name. For example, if the Admin CDN Name
for a vNIC called "vnic0" is cdn0, then the Oper CDN Name for this vNIC will be cdn0, but if the
Admin CDN Name for the same vNIC is not specified, the Oper CDN Name will be vnic0.
Click Save Changes.
CIMC Security Policies

Cisco UCS Manager provides the following policies to increase security:
KVM Management Policy
IPMI Access Profile

236
IPMI Access Profile
IPMI Access Profile

This policy allows you to determine whether IPMI commands can be sent directly to the server, using the IP
address. For example, you can send commands to retrieve sensor data from the CIMC. This policy defines
the IPMI access, including a username and password that can be authenticated locally on the server, and
whether the access is read-only or read-write.
You can also restrict remote connectivity by disabling or enabling IPMI over LAN in the IPMI access profile.
IPMI over LAN is disabled by default on all unassociated servers, and on all servers without an IPMI access
policy. When an IPMI access policy is created, the IPMI over LAN is set to enabled by default. If you do not
change the value to disabled, IPMI over LAN will be enabled on all associated servers.
You must include this policy in a service profile and that service profile must be associated with a server for
it to take effect.
Creating an IPMI Access Profile

Before You Begin
An IPMI profile requires that one or more of the following resources already exist in the system:
Username with appropriate permissions that can be authenticated by the operating system of the server
Password for the username
Permissions associated with the username
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click IPMI Access Profiles and select Create IPMI Access Profile.
In the Create IPMI Access Profile dialog box:
a) Enter a unique name and description for the profile.
b) In the IPMI Over LAN field, choose whether to allow or restrict remote connectivity.
c) Click OK.
Step 6
Step 7
In the IPMI Users area of the navigator, click +.

In the Create IPMI User dialog box:

237
Deleting an IPMI Access Profile
Name
Description
Name field
The username to associate with this IPMI profile.

Enter 1 to 16 alphanumeric characters. You can also use @ (at sign),
_ (underscore), and - (hyphen). You cannot change this name once
the profile has been saved.
Password field
The password associated with this username.

Enter 1 to 20 standard ASCII characters, except for = (equal sign), $
(dollar sign), and | (vertical bar).
Confirm Password field
The password a second time for confirmation purposes.
Role field
The user role. This can be one of the following:

Admin
Read Only
b) Click OK.
Step 8
Step 9
Repeat Steps 6 and 7 to add another user.

Click OK to return to the IPMI profiles in the Work pane.
What to Do Next
Include the IPMI profile in a service profile and/or template.
Deleting an IPMI Access Profile

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the IPMI Profiles node.
Right-click the profile you want to delete and select Delete.

238

The KVM Management policy allows you to determine whether vMedia encryption is enabled when you
access a server via KVM.
it to take effect.
Note
After a KVM vMedia session is mapped, if you change the KVM management policy, it will result in a
loss of the vMedia session. You must re-map the KVM vMedia session again.
Creating a KVM Management Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click KVM Management Policies and select Create KVM Management Policy.
In the Create KVM Management Policy dialog box:
a) Enter a unique name and description for the policy.
b) In the vMedia Encryption field, choose whether to enable vMedia encryption.
c) Click OK.
Note
After a KVM vMedia session is mapped, if you change the KVM management policy, it will result
in a loss of the vMedia session. You must re-map the KVM vMedia session again.
Local Disk Policies

Local Disk Configuration Policy
This policy configures any optional SAS local drives that have been installed on a server through the onboard
RAID controller of the local drive. This policy enables you to set a local disk mode for all servers that are
associated with a service profile that includes the local disk configuration policy.
The local disk modes include the following:
No Local StorageFor a diskless server or a SAN only configuration. If you select this option, you
cannot associate any service profile which uses this policy with a server that has a local disk.

239
Guidelines for all Local Disk Configuration Policies
RAID 0 StripedData is striped across all disks in the array, providing fast throughput. There is no
data redundancy, and all data is lost if any disk fails.
RAID 1 MirroredData is written to two disks, providing complete data redundancy if one disk fails.
The maximum array size is equal to the available space on the smaller of the two drives.
Any ConfigurationFor a server configuration that carries forward the local disk configuration without
any changes.
No RAIDFor a server configuration that removes the RAID and leaves the disk MBR and payload
unaltered.
If you choose No RAID and you apply this policy to a server that already has an operating system with
RAID storage configured, the system does not remove the disk contents. Therefore, there may be no
visible differences on the server after you apply the No RAID mode. This can lead to a mismatch between
the RAID configuration in the policy and the actual disk configuration shown in the Inventory > Storage
tab for the server.
To make sure that any previous RAID configuration information is removed from a disk, apply a scrub
policy that removes all disk information after you apply the No RAID configuration mode.
RAID 5 Striped ParityData is striped across all disks in the array. Part of the capacity of each disk
stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data
throughput for applications with high read request rates.
RAID 6 Striped Dual ParityData is striped across all disks in the array and two parity disks are used
to provide protection against the failure of up to two physical disks. In each row of data blocks, two sets
of parity data are stored.
RAID 10 Mirrored and StripedRAID 10 uses mirrored pairs of disks to provide complete data
redundancy and high throughput rates.
RAID 50 Striped Parity and Striped Data is striped across multiple striped parity disk sets to provide
high throughput and multiple disk failure tolerance.
RAID 60 Striped Dual Parity and Striped Data is striped across multiple striped dual parity disk
sets to provide high throughput and greater disk failure tolerance.
the policy to take effect.
Note
For a Cisco UCS C-Series server integrated with Cisco UCS Manager, with an embedded on-board RAID
controller, the local disk mode should always be Any Configuration, and the RAID must be configured
directly on the controller.
Guidelines for all Local Disk Configuration Policies

Before you create a local disk configuration policy, consider the following guidelines:
No Mixed HDDs and SSDs
Do not include HDDs and SSDs in a single server or RAID configuration.

240
Guidelines for Local Disk Configuration Policies Configured for RAID
Do Not Assign a Service Profile with the Default Local Disk Configuration Policy from a B200 M1 or M2 to a
B200 M3
Due to the differences in the RAID/JBOD support provided by the storage controllers of B200 M1 and M2
servers and those of the B200 M3 server, you cannot assign or re-assign a service profile that includes the
default local disk configuration policy from a B200M1 or M2 server to a B200 M3 server. The default local
disk configuration policy includes those with Any Configuration or JBOD configuration.
JBOD Mode Support
The B200 M3 server supports JBOD mode for local disks.
Note
Only B200 M1, B200 M2, B200 M3, B250 M1, B250 M2 and B22 M3 blade servers support the JBOD
mode for local disks.

Configure RAID Settings in Local Disk Configuration Policy for Servers with MegaRAID Storage Controllers
If a blade server or integrated rack-mount server has a MegaRAID controller, you must configure RAID
settings for the drives in the Local Disk Configuration policy included in the service profile for that server.
You can do this either by configuring the local disk configuration policy in the service profile using one of
the defined RAID modes for that server, or you can use the Any Configuration mode with the LSI Utilities
toolset to create the RAID volumes.
If you do not configure your RAID LUNs before installing the OS, disk discovery failures might occur during
the installation and you might see error messages such as No Device Found.
Server May Not Boot After RAID1 Cluster Migration if Any Configuration Mode Specified in Service Profile
After RAID1 clusters are migrated, you need to associate a service profile with the server. If the local disk
configuration policy in the service profile is configured with Any Configuration mode rather than RAID1,
the RAID LUN remains in "inactive" state during and after association. As a result, the server cannot boot.
To avoid this issue, ensure that the service profile you associate with the server contains the identical local
disk configuration policy as the original service profile before the migration and does not include the Any
Configuration mode.
Do Not Use JBOD Mode on Servers with MegaRAID Storage Controllers
Do not configure or use JBOD mode or JBOD operations on any blade server or integrated rack-mount server
with a MegaRAID storage controllers. JBOD mode and operations are not intended for nor are they fully
functional on these servers.
Maximum of One RAID Volume and One RAID Controller in Integrated Rack-Mount Servers
A rack-mount server that has been integrated with Cisco UCS Manager can have a maximum of one RAID
volume irrespective of how many hard drives are present on the server.
All the local hard drives in an integrated rack-mount server must be connected to only one RAID Controller.
Integration with Cisco UCS Manager does not support the connection of local hard drives to multiple RAID

241
Controllers in a single rack-mount server. We therefore recommend that you request a single RAID Controller
configuration when you order rack-mount servers to be integrated with Cisco UCS Manager.
In addition, do not use third party tools to create multiple RAID LUNs on rack-mount servers. Cisco UCS
Manager does not support that configuration.
Maximum of One RAID Volume and One RAID Controller in Blade Servers
A blade server can have a maximum of one RAID volume irrespective of how many drives are present in the
server. All the local hard drives must be connected to only one RAID controller. For example, a B200 M3
server has an LSI controller and an Intel Patsburg controller, but only the LSI controller can be used as a
RAID controller.
In addition, do not use third party tools to create multiple RAID LUNs on blade servers. Cisco UCS Manager
does not support that configuration.
Number of Disks Selected in Mirrored RAID Should Not Exceed Two
If the number of disks selected in the Mirrored RAID exceed two, RAID 1 is created as a RAID 10 LUN.
This issue can occur with the Cisco UCS B440 M1 and B440 M2 servers.
License Required for Certain RAID Configuration Options on Some Servers
Some Cisco UCS servers require a license for certain RAID configuration options. When Cisco UCS Manager
associates a service profile containing this local disk policy with a server, Cisco UCS Manager verifies that
the selected RAID option is properly licensed. If there are issues, Cisco UCS Manager displays a configuration
error during the service profile association.
For RAID license information for a specific Cisco UCS server, see the Hardware Installation Guide for that
server.
B420 M3 Server Does Not Support All Configuration Modes
The B420 M3 server does not support the following configuration modes in a local disk configuration policy:
No RAID
RAID 6 Striped Dual Parity
In addition, the B420 M3 does not support JBOD modes or operations.
Single-Disk RAID 0 Configurations Not Supported on Some Blade Servers
A single-disk RAID 0 configuration is not supported in the following blade servers:
Cisco UCS B200 M1
Cisco UCS B200 M2
Cisco UCS B250 M1
Cisco UCS B250 M2

242
Creating a Local Disk Configuration Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click Local Disk Config Policies and choose Create Local Disk Configuration Policy.
In the Create Local Disk Configuration Policy dialog box, complete the following fields:
Name
Description
Name field

Description field


243
Name
Description
Mode drop-down list
This can be one of the following local disk policy modes:

No Local Storage
RAID 0 Striped
RAID 1 Mirrored
Any Configuration
No RAID
If you choose No RAID and you apply this policy to a server that
already has an operating system with RAID storage configured,
the system does not remove the disk contents. Therefore, there
may be no visible differences on the server after you apply the No
RAID mode. This can lead to a mismatch between the RAID
configuration in the policy and the actual disk configuration shown
in the Inventory > Storage tab for the server.
To make sure that any previous RAID configuration information
is removed from a disk, apply a scrub policy that removes all disk
information after you apply the No RAID configuration mode.
RAID 5 Striped Parity
RAID 6 Striped Dual Parity
RAID 10 Mirrored and Striped
RAID 50 Striped Parity and Striped
RAID 60 Striped Dual Parity and Striped
Note
Some Cisco UCS servers require a license for certain RAID

configuration options. When Cisco UCS Manager associates
a service profile containing this local disk policy with a server,
Cisco UCS Manager verifies that the selected RAID option is
properly licensed. If there are issues, Cisco UCS Manager
displays a configuration error during the service profile
association.
For RAID license information for a specific Cisco UCS server,
see the Hardware Installation Guide for that server.

244
Changing a Local Disk Configuration Policy
Name
Description
Protect Configuration check box If checked, the server retains the configuration in the local disk
configuration policy even if the server is disassociated from the service
profile.
Protect Configuration becomes non-functional if one or more
disks in the server are defective or faulty.
This property is checked by default.
Caution
When a service profile is disassociated from a server and a new service

profile associated, the setting for the Protect Configuration property in
the new service profile takes precedence and overwrites the setting in
the previous service profile.
With this option enabled, the data on the disk is protected even after
the server is decommissioned and then recommissioned. Hence,
reassociation of the server with a service profile fails.
Note
FlexFlash State radio button
If you disassociate the server from a service profile with this

option enabled and then associate it with a new service profile
that includes a local disk configuration policy with different
properties, the server returns a configuration mismatch error
and the association fails.
To enable or disable the FlexFlash controller on the SD card click the

appropriate button.
Note
This parameter only applies to a server with an SD card

module.
FlexFlash RAID Reporting State To enable or disable RAID reporting click the appropriate button. When
radio button
RAID reporting is enabled, the RAID status is monitored and faults are
enabled.
Note
Step 6
If only one SD card is installed, the RAID state will be

displayed as Disabled and the RAID health as NA even if RAID
reporting is enabled.
Click OK.
Changing a Local Disk Configuration Policy

This procedure describes how to change a local disk configuration policy from an associated service profile.
You can also change a local disk configuration policy from the Policies node from Servers.

245
Deleting a Local Disk Configuration Policy
Procedure
Step 1
Step 2
Step 3

Expand the organization that includes the service profile with the local disk configuration policy you want to
change.
Step 4
Step 5
Click the service profile that contains the local disk configuration policy you want to change.
In the Work pane, click the Storage tab.
Step 6
Step 7
In the Actions area, click Change Local Disk Configuration Policy.

In the Change Local Disk Configuration Policy dialog box, choose one of the following options from the
Select the Local Disk Configuration Policy drop-down list.
Option
Description
Use a Disk Policy
Select an existing local disk configuration policy from the list below this
option. Cisco UCS Manager assigns this policy to the service profile.
Create a Local Disk Policy Enables you to create a local disk configuration policy that can only be accessed
by the selected service profile.
No Disk Policy
Step 8
Step 9
Selects the default local disk policy.

Note
If a UCS server is attached to the Cisco UCS Manager, selecting the
No Disk Policy can erase and replace the RAID with individual RAID
0 disks if the default RAID configuration is not supported on the
attached server.
Click OK.
(Optional) Expand the Local Disk Configuration Policy area to confirm that the change has been made.
Deleting a Local Disk Configuration Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the Local Disk Config Policies node.

246
FlexFlash Support
FlexFlash Support
Overview
Cisco UCS B-Series and C-Series M3 and M4 servers support internal Secure Digital (SD) memory cards.
The SD cards are hosted by the Cisco Flexible Flash storage controller, a PCI-based controller which has two
slots for SD cards. The cards contain a single partition called HV. When FlexFlash is enabled, Cisco UCS
Manager displays the HV partition as a USB drive to both the BIOS and the host operating system.
You can populate one or both the SD card slots that are provided. If two SD cards are populated, you can use
them in a mirrored mode.
Note
Do not mix different capacity cards in the same server.

The SD cards can be used to store operating system boot images or other information. The following figure
illustrates the SD card slots.
Figure 1: SD Card Slots

247
FlexFlash Support
FlexFlash is disabled by default. You can enable FlexFlash in a local disk policy used in a service profile.
When FlexFlash is enabled in a local disk policy, and the server is capable of supporting SD cards, the FlexFlash
controller is enabled during service profile association. If a server is not capable of supporting SD cards or
has an older CIMC version, a config failure message is displayed.
If you disable FlexFlash in a supported server, the Hypervisor or HV partition is immediately disconnected
from the host. The FlexFlash controller will also be disabled as part of a related service profile disassociation.
The FlexFlash controller supports RAID-1 for dual SD cards. You can configure new SD cards in a RAID
pair by creating a FlexFlash scrub policy and reacknowledging the server. The FlexFlash scrub policy erases
the HV partition in both cards, and brings the cards to a healthy RAID state.
Note
Disable the scrub policy as soon as the pairing is complete.

To boot from the HV partition, the SD card must be present in the boot policy used in the service profile.
FlexFlash Firmware Management
The FlexFlash controller firmware is bundled as part of the CIMC image. When you upgrade the CIMC, if a
newer firmware version is available for the FlexFlash controller, the controller can no longer be managed,
and the FlexFlash inventory displays the Controller State as Waiting For User Action and the Controller
Health as Old Firmware Running. To upgrade the FlexFlash controller firmware, you need to perform a
board controller update. For more information, see the appropriate Cisco UCS B-Series Firmware Management
Guide, available at the following URL: http://www.cisco.com/en/US/products/ps10281/products_installation_
and_configuration_guides_list.html.
Limitations for the Cisco Flexible Flash Storage Controller:
The Cisco Flexible Flash storage controller only supports 16 GB, 32 GB, and 64 GB SD cards.

248
FlexFlash Support
Note
16 GB and 32 GB cards are supported only on the B200-M3 blade servers, and the 64
GB SD cards are supported only on the B200-M4 blade servers.
We do not recommend using an SD card from a rack server in a blade server, or using an SD card from
a blade server in a rack server. Switching SD cards between server types might result in data loss from
the SD card.
Some Cisco UCS C-Series rack-mount servers have SD cards with four partitions: HV, HUU, SCU, and
Drivers. Only the HV partition is visible in Cisco UCS Manager. You can migrate a four-partition SD
card to a single HV partition card with a FlexFlash scrub policy.
The FlexFlash controller does not support RAID-1 sync (mirror rebuild). If the SD cards are in a degraded
RAID state, or if any metadata errors are reported by the controller, you must run the FlexFlash scrub
policy to pair the cards for RAID. For more information about the FlexFlash scrub policy, see
htp:/www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Server-Mgmt/3-1/b_Cisco_UCS_Manager_Server_Mgmt_Guide_3_1/server_related_policies.html#d33008e9751a1635.
The following conditions might result in degraded RAID or metadata errors:
Inserting a new or used SD card in one slot, when the server already has an SD card populated in
the second slot.
Inserting two SD cards from different servers.
The server firmware version must be at 2.2(1a) or higher.
FlexFlash FX3S Support

Beginning with Release 2.2(3), Cisco UCS Manager allows additional FlexFlash support with the FX3S
controller. The FX3S controller is present on the following servers:
Cisco UCS B200 M4 blade server
Cisco UCS C220 M4 rack server
Cisco UCS C240 M4 rack server
FlexFlash operations with the FX3S control are similar to those with the Cisco Flexible Flash storage controller.
FlexFlash is disabled by default, and is enabled using a local disk policy. You can also reset the controller,
format the SD cards, and enable automatic synchronization of your paired SD cards.
The SD cards for the FX3S controller contain a single partition called Hypervisor.
Limitations for the Cisco FX3S Controller:
The FX3S controller supports only 32 GB and 64 GB SD cards. 16 GB cards are not supported.
We do not recommend using an SD card from a rack server in a blade server, or using an SD card from
a blade server in a rack server. Switching SD cards between server types might result in data loss from
the SD card.
The server firmware version must be at 2.2(3a) or higher.

249
FlexFlash Support
Starting Up Blade Servers with FlexFlash SD Cards

Use this procedure to start up blade servers using FlexFlash cards 16 GB and larger. This procedure requires
that you know how to setup the blade server, software, and the associated infrastructure, and ensure that they
are working. This Cisco UCS Manager controlled procedure is applicable to all blade servers, running any
verison of firmware. This procedure does not apply to rack servers. Follow this procedure before you enable
FlexFlash cards in a working environment.
Caution
Note
If you use the following procedure with FlexFlash cards already in use, you will lose all data from the
cards.
This procedure does not cover FlexFlash card usage or other functions of the FlexFlash system.
Procedure
Step 1
Step 2

In the Work pane, check the details of the FlexFlash cards in the FlexFlash Controller window.
Step 3
Step 4

Step 5
Step 6
Expand the node for the organization containing the service profile and click Storage.
In the Work pane, click Change Local Disk Configuration Policy in the Actions area and expand Create
Local Disk Configuration Policy link. Follow the procedure in Creating a Local Disk Configuration Policy,
on page 243 to create a Local Disk Configuration Policy.
The FlexFlash policy name must not contain empty spaces or special characters.
Step 7
Expand Change Disk Local Configuration Policy, and select the policy you just created and click OK.
Step 8
Step 9

Follow the procedure in Creating a Scrub Policy, on page 254 and create a policy with a name such as
Scrub-FF-name and click OK.
The Scrub policy name must not contain empty spaces or special characters.
Step 10 Select the policy you created from the drop-down box.
Step 11 Expand Equipment > Chassis > Chassis Number > Servers.
Step 12 In the Work pane, click the General tab and select Server Maintenance from the Actions area.
Step 13 In the Maintenance Server dialogue box, click on the Re-acknowledge radio button, and then click OK.
Step 14 Click Server Maintenance in the Action area and click on the Re-acknowledge radio button again.
Step 15 From the Inventory tab, select the Storage sub-tab.
You can verify details of the enabled FlexFlash cards from the FlexFlash Controller window in the Work
area.
Step 16 Launch KVM Manager and log on to the operating system. Verify details of the Hypervisor partition from
the Devices and drives folder. Depending on the card size, the HV partition displays details of 32GB or 64GB.

250
FlexFlash Support
The FlexFlash cards are now synced and ready to use.
Enabling FlexFlash SD Card Support

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Expand Local Disk Config Policies and choose the local disk config policy for which you want to enable
FlexFlash support.
Step 6
Step 7
Step 8
In the FlexFlash State field, click the Enable radio button.

In the FlexFlash RAID Reporting State field, click the Enable radio button.
Click Save Changes.
Enabling Auto-Sync
Procedure
Step 1
Step 2
Step 3
Step 4

Click the server for which you want to enable auto-sync.
In the Work pane, click the Inventory tab.
Step 5
Step 6
Step 7
Click the Storage subtab.

In the Actions area, click Enable Auto-sync.
In the Enable Auto-sync dialog box, choose the Admin Slot Number for the SD card that you want to use
as the primary.
Click OK.
Step 8

251
Scrub Policy
Formatting the SD Cards

Procedure
Step 1
Step 2
Step 3
Step 4

Click the server for which you want to format the SD cards.
Step 5
Step 6
Step 7

In the Actions area, click Format SD Cards.
Click Yes to format the SD cards.
Resetting the FlexFlash Controller

Procedure
Step 1
Step 2
Step 3
Step 4

Click the server for which you want to reset the FlexFlash controller.
Step 5
Step 6
Step 7

In the Actions area, click Reset FlexFlash Controller.
Click Yes to reset the FlexFlash controller.
Scrub Policy
Scrub Policy Settings
This policy determines what happens to local data and to the BIOS settings on a server during the discovery
process, when the server is re-acknowledged, or when the server is disassociated from a service profile.
Note
Local disk scrub policies only apply to hard drives that are managed by Cisco UCS Manager and do not
apply to other devices such as USB drives.
Depending upon how you configure a scrub policy, the following can occur at those times:

252
Scrub Policy Settings
Disk scrub
One of the following occurs to the data on any local drives on disassociation:
If enabled, destroys all data on any local drives.
If disabled, preserves all data on any local drives, including local storage configuration.
BIOS Settings Scrub
One of the following occurs to the BIOS settings when a service profile containing the scrub policy is
disassociated from a server:
If enabled, erases all BIOS settings for the server and resets them to the BIOS defaults for that server
type and vendor.
If disabled, preserves the existing BIOS settings on the server.
FlexFlash Scrub
FlexFlash Scrub enables you to pair new or degraded SD cards, resolve FlexFlash metadata configuration
failures, and migrate older SD cards with 4 partitions to single partition SD cards. One of the following occurs
to the SD card when a service profile containing the scrub policy is disassociated from a server, or when the
server is reacknowledged:
If enabled, the HV partition on the SD card is formatted using the PNUOS formatting utility. If two SD
cards are present, the cards are RAID-1 paired, and the HV partitions in both cards are marked as valid.
The card in slot 1 is marked as primary, and the card in slot 2 is marked as secondary.
If disabled, preserves the existing SD card settings.
Note
Because the FlexFlash scrub erases the HV partition on the SD cards, we recommend that you take
a full backup of the SD card(s) using your preferred host operating system utilities before performing
the FlexFlash Scrub.
To resolve metadata config failures in a service profile, you need to disable FlexFlash in the local
disk config policy before you run the FlexFlash scrub, then enable FlexFlash after the server is
reacknowledged.
Disable the scrub policy as soon as the pairing is complete or the metadata failures are resolved.
FlexFlash scrub is not supported for Cisco UCS C3260 Dense Storage Server.

253
Creating a Scrub Policy
Creating a Scrub Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click Scrub Policies and select Create Scrub Policy.

In the Create Scrub Policy wizard, complete the following fields:
Name
Description
Name field

Description field

Step 6
Disk Scrub field
If this field is set to Yes, when a service profile containing this scrub
policy is disassociated from a server, all data on the server local drives
is completely erased. If this field is set to No, the data on the local drives
is preserved, including all local storage configuration.
BIOS Settings Scrub field
If the field is set to Yes, when a service profile containing this scrub
policy is disassociated from a server, the BIOS settings for that server
are erased and reset to the defaults for that server type and vendor. If
this field is set to No, the BIOS settings are preserved.
FlexFlash Scrub field
If the field is set to Yes, the HV partition on the SD card is formatted

using the PNUOS formatting utility when the server is reacknowledged.
If this field is set to No, the SD card is preserved.
Click OK.
Note
Disk scrub and FlexFlash Scrub options are not supported for Cisco UCS C3260 Dense Storage
Server.

254
Deleting a Scrub Policy
Deleting a Scrub Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the Scrub Policies node.
DIMM Error Management

DIMM Correctable Error Handling
In Cisco UCS Manager, when a DIMM encounters a significant correctable error in a given predefined window,
it is stated as degraded and considered as a non-functional device.
The DIMM correctable error handling feature enables you to reset all the correctable and uncorrectable memory
errors on all the DIMMs in a server. When you reset the error configuration, the error count of a given DIMM
is cleared, the status changes to operable, and it resets the sensor state of the given DIMM.
Resetting Memory Errors

Use this procedure to reset all correctable and uncorrectable memory errors encountered by Cisco UCS
Manager and the baseboard management controller (BMC).
Procedure
Step 1
Step 2
Step 3

Right-click on the server for which you want to reset the error configuration, and select Reset All Memory
Errors. You can also select Reset All Memory Errors from the Actions area.
If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.
Step 4

255
DIMM Blacklisting
DIMM Blacklisting
In Cisco UCS Manager, the state of the Dual In-line Memory Module (DIMM) is based on SEL event records.
When the BIOS encounters a noncorrectable memory error during memory test execution, the DIMM is
marked as faulty. A faulty DIMM is a considered a nonfunctional device.
If you enable DIMM blacklisting, Cisco UCS Manager monitors the memory test execution messages and
blacklists any DIMMs that encounter memory errors in the DIMM SPD data. To allow the host to map out
any DIMMs that encounter uncorrectable ECC errors.
Enabling DIMM Blacklisting

The memory policy is a global policy that you can apply to existing servers on a Cisco UCS domain and also
to the servers that are added after you set the memory policy.
Note
This feature is supported both on the Cisco UCS B-Series blade servers and UCS C-Series rack
servers.
Note
Cisco UCS C-Series 420 M3 rack servers do not support this feature.
This global policy cannot be added to a service profile.
Before You Begin

For Cisco B-Series blade server, the server firmware must be at Release 2.2(1) or a later release.
For Cisco C-Series rack server, the server firmware must be at Release 2.2(3).
You must be logged in with one of the following privileges:
Admin
Server policy
Server profile server policy
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization where you want to enable the blacklisting.
Expand Memory Policy and choose default.
In the Blacklisting area, click the Enabled radio button.
Step 4
Step 5

256
Serial over LAN Policy Settings
The DIMM blacklisting is enabled for the domain level policy and these changes apply to all the servers on
that particular domain.
Note
If the Cisco IMC of a server does not support DIMM blacklisting, an information level fault is generated.
Serial over LAN Policy Settings

Serial over LAN Policy Overview
This policy sets the configuration for the serial over LAN connection for all servers associated with service
profiles that use the policy. By default, the serial over LAN connection is disabled.
If you implement a serial over LAN policy, we recommend that you also create an IPMI profile.
it to take effect.
Creating a Serial over LAN Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click Serial over LAN Policies and select Create Serial over LAN Policy.
In the Create Serial over LAN Policy wizard, complete the following fields:
Name
Description
Name field

Description field

the policy.

257
Deleting a Serial over LAN Policy
Name
Description
Serial over LAN State field

DisableSerial over LAN access is blocked.
EnableSerial over LAN access is permitted.
Speed drop-down list

9600
19200
38400
57600
115200
Step 6
Click OK.
Deleting a Serial over LAN Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the Serial over LAN Policies node.
Server Autoconfiguration Policies

Server Autoconfiguration Policy Overview
Cisco UCS Manager uses this policy to determine how to configure a new server. If you create a server
autoconfiguration policy, the following occurs when a new server starts:
1 The qualification in the server autoconfiguration policy is executed against the server.

258
Creating an Autoconfiguration Policy
2 If the server meets the required qualifications, the server is associated with a service profile created from
the service profile template configured in the server autoconfiguration policy. The name of that service
profile is based on the name given to the server by Cisco UCS Manager.
3 The service profile is assigned to the organization configured in the server autoconfiguration policy.
Creating an Autoconfiguration Policy

Before You Begin
This policy requires that one or more of the following resources already exist in the system:
Server pool policy qualifications
Service profile template
Organizations, if a system implements multitenancy
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Click the Autoconfig Policies subtab.

Step 6
In the Create Autoconfiguration Policy dialog box, complete the following fields:
Name
Description
Name field

Description field


259
Deleting an Autoconfiguration Policy
Name
Description
Qualification drop-down list
The server pool policy qualification associated with this

auto-configuration policy.
If a new server is discovered that matches the criteria specified in the
server pool policy qualification, Cisco UCS automatically creates a
service profile based on the service profile template selected in the
Service Profile Template Name drop-down list and associates the
newly created service profile with the server.
Org drop-down list
The organization associated with this autoconfiguration policy.

If Cisco UCS automatically creates a service profile to associate with
a server, it places the service profile under the organization selected in
this field.
Service Profile Template Name

drop-down list
Step 7
The service profile template associated with this policy.
Click OK.
Deleting an Autoconfiguration Policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Step 6
Click the Autoconfig Policies subtab.

Right-click the autoconfiguration policy that you want to delete and choose Delete.

260
Server Discovery Policy Settings
Server Discovery Policy Settings

Server Discovery Policy Overview
Important
The server discovery policy determines how the UCS Manager reacts when you add a new UCS Blade Server,
UCS Mini or a UCS M-Series Modular server. If you create a server discovery policy, you can control whether
the system conducts a deep discovery when a server is added to a chassis, or whether a user must first
acknowledge the new server. By default, the system conducts a full discovery.
If you create a server discovery policy, the following occurs when a new server starts:
1 The qualification in the server discovery policy is executed against the server.
2 If the server meets the required qualifications, Cisco UCS Manager applies the following to the server:
Depending on the option that you select for the action, UCS Manager discovers the new server
immediately, or waits for a user acknowledgment of the new server
Applies the scrub policy to the server
Important
In Cisco UCS Manager Release 2.2(4), blade servers do not support drives with a block size of 4K, but
rack-mount servers support such drives. If a drive with a block size of 4K is inserted into a blade server,
discovery fails and the following error message appears:
Unable to get Scsi Device Information from the system
If this error occurs, do the following:
1 Remove the 4K drive.
2 Reacknowledge the server.
Note: Reacknowledging the server causes the server to reboot and results in loss of service.
Creating a Server Discovery Policy

Before You Begin
If you plan to associate this policy with a server pool, create server pool policy qualifications.

261
Deleting a Server Discovery Policy
Procedure
Step 1
Step 2
Step 3
Step 4
Click the Server Discovery Policies subtab.

Click the + icon on the table icon bar to open the Create Server Discovery Policy dialog box.
Step 5
Step 6
In the Description field, enter a description for the discovery policy.

In the Action field, select one of the following options:
ImmediateCisco UCS Manager attempts to discover new servers automatically
User AcknowledgedCisco UCS Manager waits until the user tells it to search for new servers
Step 7
Step 8
Step 9
(Optional) To associate this policy with a server pool, select server pool policy qualifications from the
Qualification drop-down list.
(Optional) To include a scrub policy, select a policy from the Scrub Policy drop-down list.
Click OK.
What to Do Next
Include the server discovery policy in a service profile and/or template.
Deleting a Server Discovery Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Click the Server Discovery Policies subtab.

Right-click the server discover policy that you want to delete and choose Delete.
Server Inheritance Policy Settings

Server Inheritance Policy Overview
This policy is invoked during the server discovery process to create a service profile for the server. All service
profiles created from this policy use the values burned into the blade at manufacture. The policy performs the
following:

262
Creating a Server Inheritance Policy
Analyzes the inventory of the server

If configured, assigns the server to the selected organization
Creates a service profile for the server with the identity burned into the server at manufacture
You cannot migrate a service profile created with this policy to another server.
Creating a Server Inheritance Policy

A blade server or rack-mount server with a VIC adapter, such as the Cisco UCS M81KR Virtual Interface
Card, does not have server identity values burned into the server hardware at manufacture. As a result, the
identity of the adapter must be derived from default pools. If the default pools do not include sufficient entries
for one to be assigned to the server, service profile association fails with a configuration error.
Procedure
Step 1
Step 2
Step 3
Step 4
Click the Server Inheritance Policies subtab.

Step 5
In the Create Server Inheritance Policy dialog box, complete the following fields:
Name
Description
Name field

Description field

Step 6
To associate this policy with one or more specific server pools, choose
the server pool qualification policy that identifies these pools.
Org drop-down list
If you want to associate an organization with this policy, or if you want

to change the current association, choose the organization from the
drop-down list.
Click OK.

263
Deleting a Server Inheritance Policy
Deleting a Server Inheritance Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Click the Server Inheritance Policies subtab.

Right-click the server inheritance policy that you want to delete and choose Delete.
Server Pool Policy Settings

Server Pool Policy Overview
This policy is invoked during the server discovery process. It determines what happens if server pool policy
qualifications match a server to the target pool specified in the policy.
If a server qualifies for more than one pool and those pools have server pool policies, the server is added to
all those pools.
Creating a Server Pool Policy

Before You Begin
This policy requires that one or more of the following resources already exist in the system:
A minimum of one server pool
Server pool policy qualifications, if you choose to have servers automatically added to pools
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click Server Pool Policies and select Create Server Pool Policy.
In the Create Server Pool Policy dialog box, complete the following fields:

264
Deleting a Server Pool Policy
Name
Description
Name field

Description field

Step 6
Target Pool drop-down list
If you want to associate this policy with a server pool, select that pool
from the drop-down list.
To associate this policy with one or more specific server pools, choose
the server pool qualification policy that identifies these pools.
Click OK.
Deleting a Server Pool Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the Server Pool Policies node.
Server Pool Policy Qualifications Settings

Server Pool Policy Qualification Overview
This policy qualifies servers based on the inventory of a server conducted during the discovery process. The
qualifications are individual rules that you configure in the policy to determine whether a server meets the

265
Creating Server Pool Policy Qualifications
selection criteria. For example, you can create a rule that specifies the minimum memory capacity for servers
in a data center pool.
Qualifications are used in other policies to place servers, not just by the server pool policies. For example, if
a server meets the criteria in a qualification policy, it can be added to one or more server pools or have a
service profile automatically associated with it.
You can use the server pool policy qualifications to qualify servers according to the following criteria:
Adapter type
Chassis location
Memory type and configuration
Power group
CPU cores, type, and configuration
Storage configuration and capacity
Server model
Depending upon the implementation, you might need to configure several policies with server pool policy
qualifications including the following:
Autoconfiguration policy
Chassis discovery policy
Server discovery policy
Server inheritance policy
Server pool policy

Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click the Server Pool Policy Qualifications node and select Create Server Pool Policy Qualification.
In the Create Server Pool Policy Qualification dialog box, enter a unique name and description for the
policy.
(Optional) To use this policy to qualify servers according to their adapter configuration, do the following:
a) Click Create Adapter Qualifications.
b) In the Create Adapter Qualifications dialog box, complete the following fields:
Step 6

266
Name
Description
Type drop-down list
The adapter type.

Once you save the adapter qualification, this type cannot be changed.
PID field
A regular expression that the adapter PID must match.
Maximum Capacity field
The maximum capacity for the selected type.

To specify a capacity, choose select and enter the desired maximum
capacity. You can enter an integer between 1 and 65535.
c) Click OK.
Step 7
(Optional) To use this policy to qualify servers according to the chassis in which they physically reside, do
the following:
a) Click Create Chassis/Server Qualifications.
b) In the Chassis Qualifications area of the Create Chassis and Server Qualifications dialog box, complete
the following fields to specify the range of chassis you want to use:
First Chassis ID fieldThe first chassis ID from which server pools associated with this policy can
draw.
Number of Chassis fieldThe total number of chassis to include in the pool, starting with the
chassis identified in the First Chassis ID field.
Example:
For example, if you want to use chassis 5, 6, 7, and 8, enter 5 in the First Chassis ID field and 4 in the
Number of Chassis field. If you want to use only chassis 3, enter 3 in the First Chassis ID field and 1
in the Number of Chassis field.
Tip
If you want to use chassis 5, 6, and 9, create a chassis/server qualification for the range 5-6 and
another qualification for chassis 9. You can add as many chassis/server qualifications as needed.
c) Click Finish.
Step 8
(Optional) To use this policy to qualify servers according to both the chassis and slot in which they physically
reside, do the following:
a) Click Create Chassis/Server Qualifications.
b) In the Chassis Qualifications area of the Create Chassis and Server Qualifications dialog box, complete
the following fields to specify the range of chassis you want to use:
First Chassis ID fieldThe first chassis ID from which server pools associated with this policy can
draw.
Number of Chassis fieldThe total number of chassis to include in the pool, starting with the
chassis identified in the First Chassis ID field.
c) In the Server Qualifications table, click Add.
d) In the Create Server Qualifications dialog box, complete the following fields to specify the range of
server locations you want to use:

267
First Slot ID fieldThe first slot ID from which server pools associated with this policy can draw.
Number of Slots fieldThe total number of slots from which server pools associated with this
policy can draw.
e) Click Finish Stage.
f) To add another range of slots, click Add and repeat steps d and e.
g) When you have finished specifying the slot ranges, click Finish.
Step 9
(Optional) To use this policy to qualify servers according to their memory configuration, do the following:
a) Click Create Memory Qualifications.
b) In the Create Memory Qualifications dialog box, complete the following fields:
Name
Description
Clock field
The minimum clock speed required, in megahertz.
Latency field
The maximum latency allowed, in nanoseconds.
Min Cap field
The minimum memory capacity required, in megabytes.
Max Cap field
The maximum memory capacity allowed, in megabytes.
Width field
The minimum width of the data bus.
Units field
The unit of measure to associate with the value in the Width field.
c) Click OK.
Step 10 (Optional) To use this policy to qualify servers according to their CPU/Cores configuration, do the following:
a) Click Create CPU/Cores Qualifications.
b) In the Create CPU/Cores Qualifications dialog box, complete the following fields:
Name
Description
Processor Architecture
drop-down list
The CPU architecture to which this policy applies.
PID field
A regular expression that the processor PID must match.
Min Number of Cores field
The minimum number of CPU cores required.

To specify a capacity, choose select and enter an integer between 1
and 65535 in the associated text field.
Max Number of Cores field
The maximum number of CPU cores allowed.


268
Name
Description
Min Number of Threads field
The minimum number of CPU threads required.

Max Number of Threads field
The maximum number of CPU threads allowed.

CPU Speed field
The minimum CPU speed required.

To specify a capacity, choose select and enter the minimum CPU
speed.
CPU Stepping field
The minimum CPU version required.

To specify a capacity, choose select and enter the maximum CPU
speed.
c) Click OK.
Step 11 (Optional) To use this policy to qualify servers according to their storage configuration and capacity, do the
following:
a) Click Create Storage Qualifications.
b) In the Create Storage Qualifications dialog box, complete the following fields:
Name
Description
Diskless field
Whether the available storage must be diskless. This can be one of

the following:
UnspecifiedEither storage type is acceptable.
YesThe storage must be diskless.
NoThe storage cannot be diskless.
Number of Blocks field
The minimum number of blocks required.

To specify a capacity, choose select and enter the number of blocks.
Block Size field
The minimum block size required, in bytes.

To specify a capacity, choose select and enter the block size.
Min Cap field
The minimum storage capacity across all disks in the server, in

megabytes.
To specify a capacity, choose select and enter the minimum storage
capacity.

269
Name
Description
Max Cap field
The maximum storage capacity allowed, in megabytes.

To specify a capacity, choose select and enter the maximum storage
capacity.
Per Disk Cap field
The minimum storage capacity per disk required, in gigabytes.

To specify a capacity, choose select and enter the minimum capacity
on each disk.
Units field
The number of units.

To specify a capacity, choose select and enter the desired units.
Number of Flex Flash Cards

field
The number of FlexFlash Cards.
Disk Type field
The disk type. This can be one of the following:
To specify a capacity, choose select and enter the desired units.
UnspecifiedEither disk type is acceptable.

HDDThe disk must be HDD.
SSDThe disk must be SSD (SATA or SAS).
c) Click OK.
Step 12 (Optional) To use this policy to qualify servers according to the model of the server, do the following:
a) Click Create Server Model Qualifications.
b) In the Create Server Model Qualifications dialog box, enter a regular expression that the server model
must match in the Model field.
c) Click OK.
Step 13 (Optional) To use this policy to qualify servers according to power group, do the following:
a) Click Create Power Group Qualifications.
b) In the Create Power Group Qualifications dialog box, choose a power group from the Power Group
drop-down list.
c) Click OK.
Step 14 (Optional) To use this policy to qualify the rack-mount servers that can be added to the associated server
pool, do the following:
a) Click Create Rack Qualifications.
b) In the Create Rack Qualifications dialog box, complete the following fields:
Name
Description
First Slot ID field
The first rack-mount server slot ID from which server pools associated
with this policy can draw.

270
Deleting Server Pool Policy Qualifications
Name
Description
Number of Slots field
The total number of rack-mount server slots from which server pools
associated with this policy can draw.
Step 15 Verify the qualifications in the table and correct if necessary.

Step 16 Click OK.
Deleting Server Pool Policy Qualifications

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the Server Pool Policy Qualifications node.
Right-click the policy qualifications you want to delete and select Delete.
Deleting Qualifications from Server Pool Policy Qualifications

Use this procedure to modify Server Pool Policy Qualifications by deleting one or more sets of qualifications.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the Server Pool Policy Qualifications node.
Choose the policy you want to modify.
In the Work pane, choose the Qualifications tab.
Step 6
To delete a set of qualifications:

a) In the table, choose the row that represents the set of qualifications.
b) Right-click the row and select Delete.
Step 7
Click Save Changes.

271
vNIC/vHBA Placement Policy Settings
vNIC/vHBA Placement Policy Settings

vNIC/vHBA Placement Policies
vNIC/vHBA placement policies are used to determine the following:
How the virtual network interface connections (vCons) are mapped to the physical adapters on a server.
What types of vNICs or vHBAs can be assigned to each vCon.
Each vNIC/vHBA placement policy contains four vCons that are virtual representations of the physical
adapters. When a vNIC/vHBA placement policy is assigned to a service profile, and the service profile is
associated with a server, the vCons in the vNIC/vHBA placement policy are assigned to the physical adapters
and the vNICs and vHBAs are assigned to those vCons.
For blade or rack servers that contain one adapter, Cisco UCS assigns all vCons to that adapter. For servers
that contain four adapters, Cisco UCS assigns vCon1 to Adapter1, vCon2 to Adapter2, vCon3 to Adapter3,
and vCon4 to Adapter4.
For blade or rack servers that contain two or three adapters, Cisco UCS assigns the vCons based on the type
of server and the selected virtual slot mapping scheme, which can be Round Robin or Linear Ordered. For
details about the available mapping schemes, see vCon to Adapter Placement, on page 273.
After Cisco UCS assigns the vCons, it assigns the vNICs and vHBAs based on the Selection Preference for
each vCon. This can be one of the following:
Note
You can specify the PCI order for the vHBA; however, the desired order works within a class of devices,
such as vNICs or vHBAs and not across them. Within an adapter, vNICs are always placed ahead of the
vHBAs.
AllAll configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly assigned
to it, unassigned, or dynamic. This is the default.
Assigned OnlyvNICs and vHBAs must be explicitly assigned to the vCon. You can assign them
explicitly through the service profile or the properties of the vNIC or vHBA.
Exclude DynamicDynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be
used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it.
Exclude UnassignedUnassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon can
be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly assigned to
it.
Exclude usNICCisco usNICs cannot be assigned to the vCon. The vCon can be used for all other
configured vNICs and vHBAs, whether they are explicitly assigned to it, unassigned, or dynamic.
Note
An SRIOV usNIC that is explicitly assigned to a vCon set to Exclude usNIC will remain
assigned to that vCon.

272
vCon to Adapter Placement
If you do not include a vNIC/vHBA placement policy in the service profile, Cisco UCS Manager defaults to
the Round Robin vCon mapping scheme and the All vNIC/vHBA selection preference, distributing the vNICs
and vHBAs between the adapters based on the capabilities and relative capacities of each adapter.
vCon to Adapter Placement

Cisco UCS maps every vCon in a service profile to a physical adapter on the server. How that mapping occurs
and how the vCons are assigned to a specific adapter in a server depends on the following:
The type of server. N20-B6620-2 and N20-B6625-2 blade servers with two adapter cards use a different
mapping scheme than other supported rack or blade servers.
The number of adapters in the server.
The setting of the virtual slot mapping scheme in the vNIC/vHBA placement policy, if applicable.
You must consider this placement when you configure the vNIC/vHBA selection preference to assign vNICs
and vHBAs to vCons.
Note
vCon to adapter placement is not dependent upon the PCIE slot number of the adapter. The adapter numbers
used for the purpose of vCon placement are not the PCIE slot numbers of the adapters, but the ID assigned
to them during server discovery.
vCon to Adapter Placement for N20-B6620-2 and N20-B6625-2 Blade Servers

In N20-B6620-2 and N20-B6625-2 blade servers, the two adapters are numbered left to right while vCons
are numbered right to left. If one of these blade servers has a single adapter, Cisco UCS assigns all vCons to
that adapter. If the server has two adapters, the vCon assignment depends upon the virtual slot mapping
scheme:
Round RobinCisco UCS assigns vCon2 and vCon4 to Adapter1 and vCon1 and vCon3 to Adapter2.
This is the default.
Linear OrderedCisco UCS assigns vCon3 and vCon4 to Adapter1 and vCon1 and vCon2 to Adapter2.
vCon to Adapter Placement for All Other Supported Servers

For all other servers supported by Cisco UCS in addition to the N20-B6620-2 and N20-B6625-2 blade servers,
the vCon assignment depends on the number of adapters in the server and the virtual slot mapping scheme.
For blade or rack servers that contain one adapter, Cisco UCS assigns all vCons to that adapter. For servers
that contain four adapters, Cisco UCS assigns vCon1 to Adapter1, vCon2 to Adapter2, vCon3 to Adapter3,
For blade or rack servers that contain two or three adapters, Cisco UCS assigns the vCons based on the selected
virtual slot mapping scheme: Round Robin or Linear Ordered.

273
vNIC/vHBA to vCon Assignment
Table 2: vCon to Adapter Placement Using the Round - Robin Mapping Scheme
Number of Adapters vCon1 Assignment
vCon2 Assignment
vCon3 Assignment
vCon4 Assignment
Adapter1
Adapter1
Adapter1
Adapter1
Adapter1
Adapter2
Adapter1
Adapter2
Adapter1
Adapter2
Adapter3
Adapter2
Adapter1
Adapter2
Adapter3
Adapter4
Round Robin is the default mapping scheme.

Table 3: vCon to Adapter Placement Using the Linear Ordered Mapping Scheme
Note
Number of Adapters vCon1 Assignment
vCon2 Assignment
vCon3 Assignment
vCon4 Assignment
Adapter1
Adapter1
Adapter1
Adapter1
Adapter1
Adapter1
Adapter2
Adapter2
Adapter1
Adapter2
Adapter3
Adapter3
Adapter1
Adapter2
Adapter3
Adapter4
If you are using a vCon policy with two adapters in the Cisco UCS B440 M2 Blade Server, be aware of
the following mapping.
vCon 2 to adapter 1 maps first
vCon 1 to adapter 2 maps second ZXA Q

Cisco UCS Manager provides two options for assigning vNICs and vHBAs to vCons through the vNIC/vHBA
placement policy: explicit assignment and implicit assignment.
Explicit Assignment of vNICs and vHBAs
With explicit assignment, you specify the vCon and, therefore, the adapter to which a vNIC or vHBA is
assigned. Use this assignment option when you need to determine how the vNICs and vHBAs are distributed
between the adapters on a server.
To configure a vCon and the associated vNICs and vHBAs for explicit assignment, do the following:

274
Set the vCon configuration to any of the available options. You can configure the vCons through a
vNIC/vHBA placement policy or in the service profile associated with the server. If a vCon is configured
for All, you can still explicitly assign a vNIC or vHBA to that vCon.
Assign the vNICs and vHBAs to a vCon. You can make this assignment through the virtual host interface
placement properties of the vNIC or vHBA or in the service profile associated with the server.
If you attempt to assign a vNIC or vHBA to a vCon that is not configured for that type of vNIC or vHBA,
Cisco UCS Manager displays a message advising you of the configuration error.
During service profile association, Cisco UCS Manager validates the configured placement of the vNICs and
vHBAs against the number and capabilities of the physical adapters in the server before assigning the vNICs
and vHBAs according to the configuration in the policy. Load distribution is based upon the explicit assignments
to the vCons and adapters configured in this policy.
If the adapters do not support the assignment of one or more vNICs or vHBAs, Cisco UCS Manager raises a
fault against the service profile.
Note
You can specify the PCI order for the vHBA; however, the desired order works within a class of devices,
such as vNICs or vHBAs and not across them. Within an adapter, vNICs are always placed ahead of the
vHBAs.
Implicit Assignment of vNICs and vHBAs

With implicit assignment, Cisco UCS Manager determines the vCon and, therefore, the adapter to which a
vNIC or vHBA is assigned according to the capability of the adapters and their relative capacity. Use this
assignment option if the adapter to which a vNIC or vHBA is assigned is not important to your system
configuration.
To configure a vCon for implicit assignment, do the following:
Set the vCon configuration to All, Exclude Dynamic, or Exclude Unassigned. You can configure the
vCons through a vNIC/vHBA placement policy or in the service profile associated with the server.
Do not set the vCon configuration to Assigned Only. Implicit assignment cannot be performed with
this setting.
Do not assign any vNICs or vHBAs to a vCon.
During service profile association, Cisco UCS Manager verifies the number and capabilities of the physical
adapters in the server and assigns the vNICs and vHBAs accordingly. Load distribution is based upon the
capabilities of the adapters, and placement of the vNICs and vHBAs is performed according to the actual
order determined by the system. For example, if one adapter can accommodate more vNICs than another, that
adapter is assigned more vNICs.
If the adapters cannot support the number of vNICs and vHBAs configured for that server, Cisco UCS Manager
raises a fault against the service profile.
Implicit Assignment of vNICs in a Dual Adapter Environment
When you use implicit vNIC assignment for a dual slot server with an adapter card in each slot, Cisco UCS
Manager typically assigns the vNICs/vHBAs as follows:

275
Creating a vNIC/vHBA Placement Policy
If the server has the same adapter in both slots, Cisco UCS Manager assigns half the vNICs and half the
vHBAs to each adapter.
If the server has one non-VIC adapter and one VIC adapter, Cisco UCS Manager assigns two vNICs
and two vHBAs to the non-VIC adapter and the remaining vNICs and vHBAs to the VIC adapter.
If the server has two different VIC adapters, Cisco UCS Manager assigns the vNICs and vHBAs
proportionally, based on the relative capabilities of the two adapters.
The following examples show how Cisco UCS Manager would typically assign the vNICs and vHBAs with
different combinations of supported adapter cards:
If you want to configure four vNICs and the server contains two Cisco UCS M51KR-B Broadcom
BCM57711 adapters (with two vNICs each), Cisco UCS Manager assigns two vNICs to each adapter.
If you want to configure 50 vNICs and the server contains a Cisco UCS CNA M72KR-E adapter (2
vNICs) and a Cisco UCS M81KR Virtual Interface Card adapter (128 vNICs), Cisco UCS Manager
assigns two vNICs to the Cisco UCS CNA M72KR-E adapter and 48 vNICs to the Cisco UCS M81KR
Virtual Interface Card adapter.
If you want to configure 150 vNICs and the server contains a Cisco UCS M81KR Virtual Interface Card
adapter (128 vNICs) and a Cisco UCS VIC-1240 Virtual Interface Card adapter (256 vNICs), Cisco
UCS Manager assigns 50 vNICs to the Cisco UCS M81KR Virtual Interface Card adapter and 100
vNICs to the Cisco UCS VIC-1240 Virtual Interface Card adapter.
Note
Exceptions to this implicit assignment occur if you configure the vNICs for fabric failover and if you
configure dynamic vNICs for the server.
For a configuration that includes vNIC fabric failover where one adapter does not support vNIC failover,
Cisco UCS Manager implicitly assigns all vNICs that have fabric failover enabled to the adapter that supports
them. If the configuration includes only vNICs that are configured for fabric failover, no vNICs are implicitly
assigned to the adapter that does not support them. If some vNICs are configured for fabric failover and some
are not, Cisco UCS Manager assigns all failover vNICs to the adapter that supports them and a minimum of
one nonfailover vNIC to the adapter that does not support them, according to the ratio above.
For a configuration that includes dynamic vNICs, the same implicit assignment would occur. Cisco UCS
Manager assigns all dynamic vNICs to the adapter that supports them. However, with a combination of
dynamic vNICs and static vNICs, at least one static vNIC is assigned to the adapter that does not support
dynamic vNICs.

Procedure
Step 1
Step 2
Step 3


276
Step 4
Step 5
Right-click vNIC/vHBA Placement Policies and choose Create Placement Policy.

In the Create Placement Policy dialog box, do the following:
Name
Description
Name field
The name for this placement policy.

(underscore), : (colon), and . (period), and you cannot change this

277
Name
Description
Virtual Slot Mapping Scheme

field
Cisco UCS assigns virtual network interface connections (vCons) to

the PCIe adapter cards in the server. Each vCon is a virtual
representation of a physical adapter that can be assigned vNICs and
vHBAs.
For blade or rack servers that contain one adapter, Cisco UCS assigns
all vCons to that adapter. For servers that contain four adapters, Cisco
UCS assigns vCon1 to Adapter1, vCon2 to Adapter2, vCon3 to
Adapter3, and vCon4 to Adapter4.
For blade or rack servers that contain two or three adapters, Cisco
UCS assigns the vCons based on the selected virtual slot mapping
scheme. This can be one of the following:
Round Robin In a server with two adapter cards, Cisco UCS
assigns vCon1 and vCon3 to Adapter1, then assigns vCon2 and
vCon4 to Adapter2.
In a server with three adapter cards, Cisco UCS assigns vCon1
to Adapter1, vCon2 and vCon4 to Adapter2, and vCon3 to
Adapter3.
This is the default scheme.
Linear Ordered In a server with two adapter cards, Cisco
UCS assigns vCon1 and vCon2 to Adapter1, then assigns vCon3
In a server with three adapter cards, Cisco UCS assigns vCon1
to Adapter1 and vCon2 to Adapter2, then assigns vCon3 and
vCon4 to Adapter3.
Note
In N20-B6620-2 and N20-B6625-2 blade servers, the two

adapters are numbered left to right while vCons are numbered
right to left. If one of these blade servers has a single adapter,
Cisco UCS assigns all vCons to that adapter. If the server
has two adapters, the vCon assignment depends upon the
virtual slot mapping scheme:
Round RobinCisco UCS assigns vCon2 and vCon4
to Adapter1 and vCon1 and vCon3 to Adapter2. This
is the default.
Linear OrderedCisco UCS assigns vCon3 and
vCon4 to Adapter1 and vCon1 and vCon2 to Adapter2.
After Cisco UCS assigns the vCons, it assigns the vNICs and vHBAs
based on the Selection Preference for each vCon.
b) In the Selection Preference column for each Virtual Slot, choose one of the following from the drop-down
list:

278
Deleting a vNIC/vHBA Placement Policy
AllAll configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly
assigned to it, unassigned, or dynamic. This is the default.
Assigned OnlyvNICs and vHBAs must be explicitly assigned to the vCon. You can assign them
explicitly through the service profile or the properties of the vNIC or vHBA.
Exclude DynamicDynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be
used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it.
Exclude UnassignedUnassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon
can be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly
assigned to it.
Exclude usNICCisco usNICs cannot be assigned to the vCon. The vCon can be used for all other
configured vNICs and vHBAs, whether they are explicitly assigned to it, unassigned, or dynamic.
Note
An SRIOV usNIC that is explicitly assigned to a vCon set to Exclude usNIC will remain
assigned to that vCon.
c) Click OK.
Deleting a vNIC/vHBA Placement Policy

Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Expand the vNIC/vHBA Placement Policies node.
Right-click the policy you want to delete and choose Delete.
Explicitly Assigning a vNIC to a vCon

Before You Begin
Configure the vCons through a vNIC/vHBA placement policy or in the service profile with one of the following
values:
Assigned Only
Exclude Dynamic
Exclude Unassigned
If a vCon is configured for All, you can explicitly assign a vNIC or vHBA to that vCon. However, there is
less control with this configuration.

279
Explicitly Assigning a vNIC to a vCon
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization which contains the service profile whose vNICs you want to explicitly
assign to a vCon.
Step 4
Step 5
Step 6
Expand Service_Profile_Name > vNICs.

Click on the vNIC that you want to explicitly assign to a vCon.
Step 7
In the Virtual Host Interface Placement section, complete the following fields:
Name
Description
Desired Placement drop-down list The user-specified virtual network interface connection (vCon)
placement for the vNIC. This can be one of the following:
AnyAllows Cisco UCS Manager to determine the vCon to which
the vNIC is assigned.
1Explicitly assigns the vNIC to vCon1.
Actual Assignment field
The actual vCon assignment of the vNIC on the server.
If you attempt to assign a vNIC to a vCon that is not configured for that type of vNIC, Cisco UCS Manager
displays a message box to advise you of the configuration error. You must either assign the vNIC to another
vCon or change the vCon configuration in the service profile.
Step 8
In the Order section, complete the following fields:

Name
Description
Desired Order field
The user-specified PCI order for the vNIC.

Enter an integer between 0 and 128. You cannot create more than 128
vNICs for a server.
Actual Order field
Step 9
The actual PCI order of the vNIC on the server.
Click Save Changes.

280
Explicitly Assigning a vHBA to a vCon
Explicitly Assigning a vHBA to a vCon

Before You Begin
Configure the vCons through a vNIC/vHBA placement policy or in the service profile with one of the following
values:
Assigned Only
Exclude Dynamic
Exclude Unassigned
If a vCon is configured for All, you can explicitly assign a vNIC or vHBA to that vCon. However, there is
less control with this configuration.
Procedure
Step 1
Step 2
Step 3

Expand the node for the organization which contains the service profile whose vHBAs you want to explicitly
assign to a vCon.
Step 4
Step 5
Step 6

Click on the vHBA that you want to explicitly assign to a vCon.
Step 7
In the Virtual Host Interface Placement section, complete the following fields:
Name
Description
Desired Placement field
The user-specified virtual network interface

connection (vCon) placement for the vHBA. This can
AnyAllows Cisco UCS Manager to determine
the vCon to which the vHBA is assigned.
1Explicitly assigns the vHBA to vCon1.
Actual Assignment field
The actual vCon assignment of the vHBA on the

server.

281
Placing Static vNICs Before Dynamic vNICs
If you attempt to assign a vHBA to a vCon that is not configured for that type of vHBA, Cisco UCS Manager
displays a message box to advise you of the configuration error. You must either assign the vHBA to another
vCon or change the vCon configuration in the service profile.
Step 8
In the Order section, complete the following fields:

Name
Description
Desired Order field
The user-specified PCI order for the vHBA.

Enter an integer between 0 and 128. You cannot
create more than 128 vHBAs for a server.
Actual Order field
Step 9
The actual PCI order of the vHBA on the server.
Click Save Changes.

For optimal performance, static vNICs and vHBAs should be placed before dynamic vNICs on the PCIe bus.
Static vNICs refer to both static vNICs and vHBAs. Cisco UCS Manager Release 2.1 provides the following
functionality regarding the order of static and dynamic vNICs:
After upgrading to Cisco UCS Manager Release 2.1, if no change is made to existing service profiles
(profiles that are defined in releases prior to Cisco UCS Manager Release 2.1), the vNIC order does not
change.
After an upgrade to Cisco UCS Manager Release 2.1, any vNIC-related change would reorder the vNIC
map. As a result, all dynamic vNICs would be placed after the static vNICs.
For newly created service profiles in Cisco UCS Manager Release 2.1, static vNICs are always ordered
before dynamic vNICs.
The above behavior is independent of the sequence of creating or deleting static or dynamic vNICs.
For SRIOV-enabled service profiles, UCSM places the vNIC Physical Function(PF) before the
corresponding Virtual Functions (VFs). This scheme guarantees that the VFs are placed close to the parent
PF vNIC on the PCIe bus and BDFs are in successive incremental order for the VFs.
Example
Beginning Device Order in Cisco UCS Manager Release 2.0:
dyn-vNIC-1 1
dyn-vNIC-2 2
New Device Order in Cisco UCS Manager Release 2.0 (Add 2 static vNICs):
dyn-vNIC-1
dyn-vNIC-2
eth-vNIC-1
eth-vNIC-2
1
2
3
4

282
After upgrading to Cisco UCS Manager Release 2.1, (Before any vNIC-related change is made to the service
profile.)
dyn-vNIC-1
dyn-vNIC-2
eth-vNIC-1
eth-vNIC-2
1
2
3
4
New Device Order in Cisco UCS Manager Release 2.1 (Add 2 dynamic vNICs by changing the policy count
from 2 to 4.)
dyn-vNIC-1
dyn-vNIC-2
eth-vNIC-1
eth-vNIC-2
dyn-vNIC-3
dyn-vNIC-4
3
4
1
2
5
6
Dynamic vNICs as Multifunction PCIe Devices

Cisco UCS Manager Version 2.1 provisions static vNICs as 0-function devices (new BUS for every static
vNIC). Multifunction dynamic vNICs are placed from the new Bus-slot after the last static vNIC/vHBA.
Note
Cisco UCS Manager Version 2.1 supports the new StaticZero mode.
Table 4: Version Compatibility
Cisco UCS Manager

Version 1.4
Scheme: ZeroFunction
Version 2.0
Scheme: ZeroFunction /
MultiFunction
Static and Dynamic vNICs are all Static vNICs and Dynamic vNICs
on Bus [0-57], Function [0]
are on Bus [0-57], Function [0-7].
Bus 0, Function 0
< ZeroFunction Mode >
Bus 0, Function 7
Bus 1, Function 0
< MultiFunction Mode >
Upgrade from Balboa will not
renumber BDFs (remain in
ZeroFunction mode) until Bus <=
57.
Once devices exceed 58, switch to
MultiFunction mode.
Version 2.1
MultiFunction / StaticZero
Static vNICs or PFs will be on Bus
[0-57], Function [0]. SRIOV:
Corresponding VFs will be on the
same Bus and Functions [1-255]
No-SRIOV: Dynamic vNICs are
on Bus [0-57], Function [0-7]
< StaticZero Mode >
Upgrade from Balboa will not
renumber BDFs (remain in
ZeroFunction mode) until Bus
<=57. Once devices exceed 58 or
Platform specific maximum PCIe
Bus number or change to SRIOV
configuration, switch to StaticZero
mode.

283
vNIC/vHBA Host Port Placement
Cisco UCS Manager

Version 1.4
Scheme: ZeroFunction
Version 2.0
MultiFunction
Version 2.1
MultiFunction / StaticZero
Upgrade from Cisco UCS Manager
Version 2.0 will not renumber
BDFs (remain in ZeroFunction /
MultiFunction mode). Once
devices exceed 58 or Platfor
specific maximum PCIe Bus
number OR Change to SRIOV
configuration, switch to StaticZero
mode.
vNIC/vHBA Host Port Placement

After a vNIC/vHBA is assigned to a vCON, it can be placed on one of the host ports of specific adapters. You
can either explicitly specify the host port for placement, or allow Cisco UCS Manager to automatically assign
vNICs/vHBAs to host ports.
Note
You can perform vNIC/vHBA host port placement on servers that support Cisco UCS VIC 1340 and VIC
1380 adapters.
The host port placement of the vNIC/vHBA determines the order of the vNIC/vHBA on the adapter. The
vNICs/vHBAs placed on the first host port will be enumerated first, followed by the vNICs/vHBAs on the
second host port.
Configuring Host Port Placement

You can configure host port placement for vNICs on servers that support Cisco UCS VIC 1340 and VIC 1380
adapters, and the Cisco UCS VIC 1385 and Cisco UCS VIC 1387 adapters.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5

Select the service profile which is associated with the vNIC that you want to place on a host port.
Expand Service_Profile_Name > vNICs > vNIC_Name
Step 6
In the Host Port section in the Properties area, select the one of the following as Admin Host Port:
AnyAllows Cisco UCS Manager to determine the host port to which the vNIC is assigned.

284
CIMC Mounted vMedia
1Explicitly assigns the vNIC to host port 1.

2Explicitly assigns the vNIC to host port 2.
Actual Host Port displays the actual assignment of the vNIC on a host port. When this feature is not supported,
this will appear as None.
Step 7
Click Save Changes.
CIMC Mounted vMedia

Using Scriptable vMedia
Cisco UCS Manager allows provisioning of vMedia devices iso images for remote UCS servers. Using
Scriptable vMedia, you can programmatically mount an IMG or an ISO image on a remote server. CIMC
mounted vMedia provide communications between other mounted media inside your datacenter with no
additional requirements media connection. Scriptable vMedia allows you to control virtual media devices
without using a browser to manually map each UCS server individually.
Scriptable vMedia supports multiple share types including NFS, CIFS, HTTP, and HTTPS shares. Scriptable
vMedia is enabled through BIOS configuration and configured through a Web GUI and CLI interface.
Cisco UCS Manager Scriptable vMedia supports the following functionality:
Booting from a specific vMedia device
Copying files from a mounted share to a local disk
Installation and updating OS drivers
Note
Cisco UCS Manager support for Scriptable vMedia is applicable for CIMC mapped devices only. Existing
KVM based vMedia devices are not supported.
vMedia mount fails when the following conditions are met:
1 The remote vMedia image filename in the vMedia policy is set to Service-Profile-Name.
2 The service profile is renamed.
This is because the change in the name of the service profile does not change the remote vMedia image
filename in the vMedia policy. The image filename still points to the older image on the remote device, which
cannot be found.
Note
Cisco UCS B200M2 Blade Server and Cisco UCS B230M2 Blade Server cannot use a vMedia policy as
the policy is not supported on these blade servers.

285
Creating a vMedia Policy

A vMedia policy is used to configure the mapping information for remote vMedia devices. Two vMedia
devices and mappings for CD and HDD are allowed in a vMedia policy. You can configure one ISO and one
IMG at a time. ISO configurations maps to a CD drive and IMG configurations maps to a HDD device.
Note
If you want to map a device to a remote folder, you must create an IMG and map it as a HDD device.
Before You Begin

Make sure that you have access to the following:
Remote vMedia Server
vMedia Devices
Procedure
Step 1
Step 2
Step 3

Step 4
Step 5
Right-click vMedia Policies and select Create vMedia Policy.

In the Create vMedia Policy dialog box, complete the following fields:
Name
Description
Name
The name of the vMedia policy.

Description
A description of the policy. We recommend including information about

where and when the policy should be used.
Retry on Mount Failure
Designates if the vMedia will continue mounting when a mount failure

occurs. This can be:
Yes
No
Note

286
The default setting is Yes. When Yes is selected the remote

server will continue to try to mount the vMedia mount process
until it is successful or you disable this option. If you select
No, a warning message will appear indicating retry on mount
failure will not work in case of mount failure.
Step 6
Step 7

In the Create vMedia Mount dialog box, complete the following fields:
Name
Description
Name
Name of the vMedia Mount policy.
Device Type
The type of remote vMedia you plan to mount. This can be:
CDDScriptable vMedia CD.
HDDScriptable vMedia HDD.
Protocol
The protocol to use when communicating with the remote server. Click
one of the following radio buttons to indicate the protocol you want to
use to communicate with the mounted remote server. This can be:
NFS - Network Files System.
CIFS - Common Internet File System.
HTTP - Hypertext Transfer Protocol.
HTTPS - Hypertext Transfer Protocol over Secure.

287
Name
Description
Authentication Protocol
The protocol to use for authentication when you use CIFS as the protocol
for communicating with the remote server. When you use any protocol
other than CIFS, this field is not available. Select one of the following
from the drop-down list to specify the authentication protocol.
DefaultNT LAN Manager Security Support Provider
(NTLMSSP) protocol. Use this option only with Windows 2008
R2 and Windows 2012 R2.
NoneNo authentication is used
NtlmNT LAN Manager (NTLM) security protocol. Use this
option only with Windows 2008 R2 and Windows 2012 R2.
NtlmiNTLMi security protocol. Use this option only when you
enable Digital Signing in the CIFS Windows server.
NtlmsspNT LAN Manager Security Support Provider
(NTLMSSP) protocol. Use this option only with Windows 2008
R2 and Windows 2012 R2.
NtlmsspiNTLMSSPi protocol. Use this option only when you
enable Digital Signing in the CIFS Windows server.
Ntlmv2NTLMv2 security protocol. Use this option only with
Samba Linux.
Ntlmv2iNTLMv2i security protocol. Use this option only with
Samba Linux.
Note
Hostname/IPAddress
The authentication protocol options are available only when

you select CIFS as the protocol. For all other protocols, the
Authentication Protocol field is disabled.
Enter the IP address or hostname of the location where the backup file
is to be stored. This can be a server, storage array, local drive, or any
read/write media that the fabric interconnect can access through the
network.
If you use a hostname, you must configure Cisco UCS Manager to use
a DNS server. The hostname (DNS) can be used when Inband network
is configured for that server.

288
Adding a vMedia Policy to a Service Profile
Name
Description
Image Name Variable
The name to be used for the image. This can be:

NoneFilename must be entered in the Remote File field.
Service Profile NameFilename automatically becomes the
name of the service profile that the vMedia Policy is associated
with.
Note
If you select Service Profile Name as the Image Name

variable, the Remote File field is disabled.
If you select Service Profile Name as the Image Name
variable, do not rename the service profile. Renaming
the service profile can result in vMedia mount failure.
Remote File
Enter the full path to the ISO or other image file.

Ensure that the full path to the file begins with / after the
share name.
This field can contain the filename [with the file extension] only.
Note
Remote Path
Enter the share name on the remote server, for example Share.
Username
Enter the username that Cisco UCS Manager should use to log in to the
remote server.
This field does not apply if the protocol is NFS. This field is optional
if the protocol is HTTP.
Password
Enter the password associated with the username.

This field does not apply if the protocol is NFS. This field is optional
if the protocol is HTTP.
Step 8
Click OK.
The remote server details are listed in the vMedia Mounts area of the Create vMedia Mount dialog box.
What to Do Next
Create a vMedia boot policy.

Before you can use Scriptable vMedia, you must add the vMedia and Boot Policies to a Service Profile. After
the vMedia and Boot Policies are added to a service profile you can associate the service profile with a Cisco
UCS server. The following procedure describes how to add a vMedia policy to a Service Profile.

289
Before You Begin

Configure the vMedia Policy you want to add to a service profile.
Procedure
Step 1
Step 2
Step 3

Step 4

The Unified Computing System Manager pane displays.
Step 5
In the Name field, enter a unique name that you can use to identify the service profile.
profile.
Step 6

Option
Description

pool.
Hardware Default

manufacturer.


290
Option
Description
Pools Pool_Name

the drop-down list.
still available in the pool and the total number
of UUIDs in the pool.
If you do not want use any of the existing
pools, but instead want to create a pool that
all service profiles can access, continue with
Step 4. Otherwise, continue with Step 8.
Step 7

following:
a) In the UUID field, enter the valid UUID that you want to assign to the server which uses this service
profile.
b) To verify that the selected UUID is available, click the here link.
Step 8
(Optional) If you want to create a new UUID Suffix pool to use to use in this service profile, click Create
UUID Suffix Pool and complete the fields in the Create UUID Suffix Pool wizard.
Step 9
(Optional) In the text box, enter a description of this service profile.

The user-defined description for this service profile.
Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^
(carat), " (double quote), = (equal sign), > (greater than), < (less than), or ' (single quote).
Step 10 Click Next.

Step 11 From the vMedia drop down list, choose one of the following:
Option
Description
Select vMedia Policy to use
Enables you to assign a vMedia policy to this service profile.

Create a Specific vMedia

Policy
Enables you to create a local vMedia policy that can only be accessed by
this service profile.

291
Viewing CIMC vMedia Policy
Option
Description
vMedia Policies Policy_Name Assigns an existing vMedia policy to the service profile. If you choose this
If you do not want use any of the existing policies but instead want to
create a policy that all service profiles can access, click Create vMedia
Policy . Otherwise, choose a policy from the list and continue with Step
13.
Step 12 If you created a new vmedia policy accessible to all service profiles and template, choose that policy from
the vMedia drop down list .
Step 13 Click Next.
Viewing CIMC vMedia Policy

Before You Begin
vMedia Policies are configured.
Procedure
Step 1
Step 2
Step 3
Step 4
Expand Policies > vMedia Policies.

Expand the vMedia Policies node to view the list of vMedia Policies.
Double-click the name of a vMedia policy to view the properties for the selected vMedia Mount.
On the Properties page, you can modify the properties used for the vMedia Mounts.

292
CHAPTER
15
Firmware Upgrades
Firmware Upgrades, page 293
Verifying Firmware Versions on Components, page 293
Firmware Upgrades
Important
Beginning with Cisco UCS Manager Release 3.1, Cisco is releasing unified Cisco UCS Manager software
and firmware upgrades for each of the following platforms with every release of Cisco UCS Manager:
Cisco UCS 6300 Series Fabric Interconnect with Cisco UCS B-Series and C-Series Servers
Cisco UCS 6200 Series Fabric Interconnect with Cisco UCS B-Series, C-Series, and M-Series Servers
Cisco UCS 6324 Fabric Interconnect with Cisco UCS B-Series Servers and C-Series Servers, which is
also known as UCS Mini
You can upgrade the firmware through Auto Install, packages in service profiles, using the firmware automatic
synchronization server policy, and directly at endpoints. For more information on guidelines and installing
firmware, see the Cisco UCS Firmware Management Guide.
Verifying Firmware Versions on Components

Procedure
Step 1
Step 2
In the Work pane, click the Firmware Management tab.
Step 3
On the Installed Firmware tab, review the firmware versions listed for each component.
For more information on guidelines and installing firmware, see the Cisco UCS Firmware Management Guide.

293
Firmware Upgrades
Verifying Firmware Versions on Components

294

B Cisco UCS Manager Server MGMT Guide 3 1

Uploaded by

Document Informationclick to expand document informationCisco UCS Manager Server Mgmt Guide 3

Document Informationclick to expand document information

Copyright:

Available Formats

B Cisco UCS Manager Server MGMT Guide 3 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B Cisco UCS Manager Server MGMT Guide 3 1

Uploaded by

Copyright:

Available Formats

Cisco UCS Manager Server Management Guide, Release 3.

Cisco Systems, Inc. All rights reserved.

New and Changed Information 1

Server Management Overview 3

Server License Management 5

Registering Cisco UCS Domains with Cisco UCS Central 15

Cisco UCS Manager Server Management Guide, Release 3.1

Registration of Cisco UCS Domains 15

Power Capping in Cisco UCS and Power Management for Blades 21

Cisco UCS Manager Server Management Guide, Release 3.1

Power Sync Policy 36

Blade Server Hardware Management 41

Cisco UCS Manager Server Management Guide, Release 3.1

Viewing Health LED Alarms 57

Rack-Mount Server Hardware Management 59

Compute Cartridge Hardware Management 75

Modular Server Hardware Management 77

Cisco UCS Manager Server Management Guide, Release 3.1

Booting a Modular Server 78

C3X60 Server Node Hardware Management 89

Cisco UCS Manager Server Management Guide, Release 3.1

Removing a Non-Existent C3X60 Server Node from the Configuration Database 97

Server Pools 103

Server Boot 113

Cisco UCS Manager Server Management Guide, Release 3.1

Enabling CIMC Secure Boot on a Rack Server 116

Cisco UCS Manager Server Management Guide, Release 3.1

Guidelines and Limitations for UEFI Boot Parameters 151

Service Profiles 155

Cisco UCS Manager Server Management Guide, Release 3.1

Server-Related Policies 185

Cisco UCS Manager Server Management Guide, Release 3.1

Default BIOS Settings 227

Cisco UCS Manager Server Management Guide, Release 3.1

Scrub Policy 252

Cisco UCS Manager Server Management Guide, Release 3.1

vNIC/vHBA Placement Policies 272

Firmware Upgrades 293

Cisco UCS Manager Server Management Guide, Release 3.1

Document titles appear in this font.

Cisco UCS Manager Server Management Guide, Release 3.1

CLI command keywords appear in this font.

Elements in square brackets are optional.

Required alternative keywords are grouped in braces and separated by vertical

Optional alternative keywords are grouped in brackets and separated by vertical

Nonprinting characters such as passwords are in angle brackets.

Default responses to system prompts are in square brackets.

Cisco UCS Manager Server Management Guide, Release 3.1

IMPORTANT SAFETY INSTRUCTIONS

Related Cisco UCS Documentation

Cisco UCS Manager Server Management Guide, Release 3.1

Cisco UCS Manager Server Management Guide, Release 3.1

New and Changed Information

New and Changed Information for this Release, page 1

New and Changed Information for this Release

Updated Power Sync Policy

Cisco UCS Manager does not power