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
Text Part Number: OL-28893-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
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.
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)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown
for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
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 appear in this font.
In a Text-based User Interface, text the system displays appears in this font.TUI elements
Terminal sessions and information that the system displays appear in thisfont.
Conventions
Preface
IndicationText Type
CLI commands
{x | y | z}
[x | y | z]
string
!, #
CLI command keywords appear in this font.
Variables in a CLI command appear in this font.
Elements in square brackets are optional.[ ]
Required alternative keywords are grouped in braces and separated by vertical
bars.
Optional alternative keywords are grouped in brackets and separated by vertical
bars.
A nonquoted set of characters. Do not use quotation marks around the string or
the string will include the quotation marks.
Nonprinting characters such as passwords are in angle brackets.< >
Default responses to system prompts are in square brackets.[ ]
An exclamation point (!) or a pound sign (#) at the beginning of a line of code
indicates a comment line.
Note
Tip
Caution
Timesaver
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.
Means reader be careful. In this situation, you might perform an action that could result in equipment
damage or loss of data.
Means the described action saves time. You can save time by performing the action described in the
paragraph.
This warning symbol means danger. You are in a situation that could cause bodily injury. Before you
work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with
standard practices for preventing accidents. Use the statement number provided at the end of each warning
to locate its translation in the translated safety warnings that accompanied this device.
SAVE THESE INSTRUCTIONS
New and Changed Information for this Release
The following tables provide an overview of the significant changes to this guide for the current release. The
tables do not provide an exhaustive list of all changes made to the configuration guides or of the new features
in this release.
For a complete list of all C-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 .
New Features and Significant Behavioral Changes in Cisco Integrated Management Controller software,
Release 1.4(6)
Release Notes for Cisco UCS C-Series Software, Release 1.4(6)
Where DocumentedDescriptionFeature
Cisco UCS VIC1225 Virtual
Interface Card
BIOS Properties
New Features and Significant Behavioral Changes in Cisco Integrated Management Controller software,
Release 1.4(5)
Release Notes for Cisco UCS C-Series Software, Release 1.4(5)
Hard Disk Drive LED
BIOS Properties
Support added for the Cisco UCS
VIC1225 Virtual Interface Card.
Support for additional BIOS properties
for the Cisco UCS C22 M3 Server,
Cisco UCS C24 M3 Server, Cisco UCS
C220 M3 Server, and the Cisco UCS
C240 M3 Server.
Support added for toggling the LED on
an installed hard disk drive.
Support for additional BIOS properties
for the Cisco UCS C220 M3 Server and
the Cisco UCS C240 M3 Server.
New Features and Significant Behavioral Changes in Cisco Integrated Management Controller software,
Release 1.4(1)
Release Notes for Cisco UCS C-Series Software, Release 1.4(1)
Platform support
VM FEX
Create vHBAs
Active Directory groups
Support added for additional BIOS
properties.
The features in this release apply to the
Cisco UCS C200 M1 Server, the Cisco
UCS C210 M1 Server, and the Cisco
UCS C250 M1 Server.
Support is added for virtual machine
fabric extenders (VM FEX).
Support added in the CLI to create up
to 16 vHBAs.
Support added for Active Directory
authorization groups.
BIOS Parameters by Server
Model, on page 183
Where DocumentedDescriptionFeature
Release Notes for Cisco UCS
C-Series Software, Release
1.4(1)
Managing Network Adapters,
on page 83
Managing Network Adapters,
on page 83
Managing User Accounts, on
page 65
Enhanced SNMP features
XML API
HTTP redirect
BIOS parameters
Enhanced SNMPv3 and SNMP trap
configuration is relocated in the user
interface.
Support added for CIMC control by an
XML API.
Support added for redirection of HTTP
requests to HTTPS.
Support added for additional BIOS
properties.
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 .
Overview of the Cisco UCS C-Series Rack-Mount Servers, page 1
•
Overview of the Server Software, page 1
•
Cisco Integrated Management Controller, page 2
•
CIMC CLI, page 3
•
Overview of the Cisco UCS C-Series Rack-Mount Servers
The Cisco UCS C-Series rack-mount servers include the following models:
Cisco UCS C200 Rack-Mount Server
•
Cisco UCS C210 Rack-Mount Server
•
Cisco UCS C220 Rack-Mount Server
•
Cisco UCS C240 Rack-Mount Server
•
Cisco UCS C250 Rack-Mount Server
•
Cisco UCS C260 Rack-Mount Server
•
Cisco UCS C460 Rack-Mount Server
•
Note
To determine which Cisco UCS C-Series rack-mount servers are supported by this firmware release, see
the associated Release Notes. The C-Series release notes are available at the following URL: http://
CIMC is a separate management module built into the motherboard. A dedicated ARM-based processor,
separate from the main server CPU, runs the CIMC firmware. The system ships with a running version of the
CIMC firmware. You can update the CIMC firmware, but no initial installation is needed.
Server OS
The main server CPU runs an OS such as Windows or Linux. The server ships with a pre-installed OS, but
you can install a different OS using the DVD drive or over the network. You can use CIMC to install the new
OS using the KVM console and vMedia.
Overview
Note
You can access the available OS installation documentation from the Cisco UCS C-Series Servers
Documentation Roadmap at http://www.cisco.com/go/unifiedcomputing/c-series-doc.
Cisco Integrated Management Controller
The CIMC is the management service for the C-Series servers. CIMC runs within the server.
Note
The CIMC management service is used only when the server is operating in Standalone Mode. If your
C-Series server is integrated into a UCS system, you must manage it using UCS Manager. For information
about using UCS Manager, see the configuration guides listed in the Cisco UCS B-Series ServersDocumentation Roadmap at http://www.cisco.com/go/unifiedcomputing/b-series-doc.
Management Interfaces
You can use a web-based GUI or SSH-based CLI to access, configure, administer, and monitor the server.
Almost all tasks can be performed in either interface, and the results of tasks performed in one interface are
displayed in another. However, you cannot do the following:
Use CIMC GUI to invoke CIMC CLI
•
View a command that has been invoked through CIMC CLI in CIMC GUI
•
Generate CIMC CLI output from CIMC GUI
•
Tasks You Can Perform in CIMC
You can use CIMC to perform the following server management tasks:
Power on, power off, power cycle, reset and shut down the server
Create and manage local user accounts, and enable remote user authentication through Active Directory
•
Configure network-related settings, including NIC properties, IPv4, VLANs, and network security
•
Configure communication services, including HTTP, SSH, and IPMI Over LAN
•
Manage certificates
•
Configure platform event filters
•
Update CIMC firmware
•
Monitor faults, alarms, and server status
•
No Operating System or Application Provisioning or Management
CIMC provisions servers, and as a result, exists below the operating system on a server. Therefore, you cannot
use it to provision or manage operating systems or applications on servers. For example, you cannot do the
following:
Deploy an OS, such as Windows or Linux
•
•
•
•
•
•
CIMC CLI
The CIMC CLI is a command-line management interface for Cisco UCS C-Series servers. You can launch
the CIMC CLI and manage the server over the network by SSH or Telnet. By default, Telnet access is disabled.
A user of the CLI will be one of three roles: admin, user (can control, cannot configure), and read-only.
Note
Command Modes
To recover from a lost admin password, see the Cisco UCS C-Series server installation and service guide
for your platform.
Deploy patches for software, such as an OS or an application
Install base software components, such as anti-virus software, monitoring agents, or backup clients
Install software applications, such as databases, application server software, or web servers
Perform operator actions, including restarting an Oracle database, restarting printer queues, or handling
non-CIMC user accounts
Configure or manage external storage on the SAN or NAS storage
The CLI is organized into a hierarchy of command modes, with the EXEC mode being the highest-level mode
of the hierarchy. Higher-level modes branch into lower-level modes. You use the scope command to move
from higher-level modes to modes in the next lower level , and the exit command to move up one level in the
mode hierarchy. The top command returns to the EXEC mode.
Most command modes are associated with managed objects. The scope command does not create managed
objects and can only access modes for which managed objects already exist.
Each mode contains a set of commands that can be entered in that mode. Most of the commands available in
each mode pertain to the associated managed object. Depending on your assigned role, you may have access
to only a subset of the commands available in a mode; commands to which you do not have access are hidden.
The CLI prompt for each mode shows the full path down the mode hierarchy to the current mode. This helps
you to determine where you are in the command mode hierarchy and can be an invaluable tool when you need
to navigate through the hierarchy.
You can use the Tab key in any mode to complete a command. Partially typing a command name and pressing
Tab causes the command to be displayed in full or to the point where another keyword must be chosen or an
argument value must be entered.
Command History
The CLI stores all commands used in the current session. You can step through the previously used commands
by using the Up Arrow or Down Arrow keys. The Up Arrow key steps to the previous command in the history,
and the Down Arrow key steps to the next command in the history. If you get to the end of the history, pressing
the Down Arrow key does nothing.
All commands in the history can be entered again by simply stepping through the history to recall the desired
command and pressing Enter. The command is entered as if you had manually typed it. You can also recall
a command and change it before you press Enter.
Overview
Committing, Discarding, and Viewing Pending Commands
When you enter a configuration command in the CLI, the command is not applied until you enter the commit
command. Until committed, a configuration command is pending and can be discarded by entering a discard
command. When any command is pending, an asterisk (*) appears before the command prompt. The asterisk
disappears when you enter the commit command, as shown in this example:
Server# scope chassis
Server /chassis # set locator-led off
Server /chassis *# commit
Server /chassis #
You can accumulate pending changes in multiple command modes and apply them together with a single
commit command. You can view the pending commands by entering the show configuration pending
command in any command mode.
Note
Committing multiple commands together is not an atomic operation. If any command fails, the successful
commands are applied despite the failure. Failed commands are reported in an error message.
Command Output Formats
Most CLI show commands accept an optional detail keyword that causes the output information to be displayed
as a list rather than a table. You can configure either of two presentation formats for displaying the output
information when the detail keyword is used. The format choices are as follows:
• Default—For easy viewing, the command output is presented in a compact list.
This example shows command output in the default format:
Server /chassis # set cli output default
Server /chassis # show hdd detail
Name HDD_01_STATUS:
• YAML—For easy parsing by scripts, the command output is presented in the YAML (YAML Ain't
Markup Language) data serialization language, delimited by defined character strings.
This example shows command output in the YAML format:
Server /chassis # set cli output yaml
Server /chassis # show hdd detail
--name: HDD_01_STATUS
hdd-status: present
--name: HDD_02_STATUS
hdd-status: present
--name: HDD_03_STATUS
hdd-status: present
--name: HDD_04_STATUS
hdd-status: present
...
Server /chassis #
For detailed information about YAML, see http://www.yaml.org/about.html.
In most CLI command modes, you can enter set cli output default to configure the default format, or set clioutput yaml to configure the YAML format.
Online Help for the CLI
At any time, you can type the ? character to display the options available at the current state of the command
syntax.
If you have not typed anything at the prompt, typing ? lists all available commands for the mode you are in.
If you have partially typed a command, typing ? lists all available keywords and arguments available at your
current position in the command syntax.
C-Series servers support several operating systems. Regardless of the OS being installed, you can install it
on your server using one of the following tools:
KVM console
•
PXE installation server
•
CHAPTER 2
KVM Console
The KVM console is an interface accessible from CIMC that emulates a direct keyboard, video, and mouse
(KVM) connection to the server. The KVM console allows you to connect to the server from a remote location.
Instead of using CD/DVD or floppy drives physically connected to the server, the KVM console uses virtual
media, which are actual disk drives or disk image files that are mapped to virtual CD/DVD or floppy drives.
You can map any of the following to a virtual drive:
CD/DVD or floppy drive on your computer
•
Disk image files (ISO or IMG files) on your computer
•
USB flash drive on your computer
•
CD/DVD or floppy drive on the network
•
Disk image files (ISO or IMG files) on the network
You can use the KVM console to install an OS on the server.
PXE Installation Servers
A Preboot Execution Environment (PXE) installation server allows a client to boot and install an OS from a
remote location. To use this method, a PXE environment must be configured and available on your VLAN,
typically a dedicated provisioning VLAN. Additionally, the server must be set to boot from the network.
When the server boots, it sends a PXE request across the network. The PXE installation server acknowledges
the request, and starts a sequence of events that installs the OS on the server.
PXE servers can use installation disks, disk images, or scripts to install an OS. Proprietary disk images can
also be used to install an OS, additional components, or applications.
Installing the Server OS
Note
PXE installation is an efficient method for installing an OS on a large number of servers. However,
considering that this method requires setting up a PXE environment, it might be easier to use another
installation method.
Installing an OS Using a PXE Installation Server
Before You Begin
Verify that the server can be reached over a VLAN.
•
You must log in as a user with admin privileges to install an OS.
•
Procedure
Step 1
Step 2
Set the boot order to PXE first.
Reboot the server.
If a PXE install server is available on the VLAN, the installation process begins when the server reboots. PXE
installations are typically automated and require no additional user input. Refer to the installation guide for
the OS being installed to guide you through the rest of the installation process.
What to Do Next
After the OS installation is complete, reset the LAN boot order to its original setting.
Enables or disables the chassis locator LED.Server /chassis # set locator-led {on | off}
Commits the transaction to the system
configuration.
Toggling the Locator LED for a Hard Drive
This example disables the chassis locator LED and commits the transaction:
Server# scope chassis
Server /chassis # set locator-led off
Server /chassis *# commit
Server /chassis #
Toggling the Locator LED for a Hard Drive
Before You Begin
You must log in with user or admin privileges to perform this task.
Procedure
PurposeCommand or Action
Managing the Server
Step 1
Step 2
Step 3
Server /chassis/hdd # set locateHDDdrivenum {1 | 2}
This example turns on the locator LED on HDD 2:
Server# scope chassis
Server /chassis # scope hdd
Server /chassis/hdd # locateHDD 2 1
HDD Locate LED Status changed to 1
Server /chassis/hdd # show
NameStatusLocateLEDStatus
Enters hard disk drive (HDD) command mode.Server/chassis # scope hdd
Where drivenum is the number of the hard drive whose
locator LED you want to set. A value of 1 turns the
LED on while a value of 2 turns the LED off.
Server Boot Order
Using CIMC, you can configure the order in which the server attempts to boot from available boot device
types.
When you change the boot order configuration, CIMC sends the configured boot order to the BIOS the next
time the server is rebooted. To implement the new boot order, reboot the server after making the configuration
change. The new boot order will take effect on any subsequent reboot. The configured boot order is not sent
again until the configuration is changed again.