Cisco_Systems_Network_Card

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.

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.

Preface

This preface includes the following sections:

???Audience, page xi

???Conventions, page xi

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

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

Preface

Conventions

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.

Tip Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.

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

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

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

Preface

New and Changed Information for this Release

Warning IMPORTANT SAFETY INSTRUCTIONS

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

SAVE THESE INSTRUCTIONS

New and Changed Information for this Release

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

For a complete list of all C-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)

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)

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

Preface

New and Changed Information for this Release

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

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

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

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

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

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

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

Preface

Other Documentation Resources

An ISO file containing all B and C-Series documents is available at the following URL: http://www.cisco.com/ cisco/software/type.html?mdfid=283853163&flowid=25821. From this page, click Unified Computing

System (UCS) Documentation Roadmap Bundle.

The ISO file is updated after every major documentation release.

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

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

C H A P T E R 1

Overview

This chapter includes the following sections:

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:// www.cisco.com/en/US/products/ps10739/prod_release_notes_list.html

Overview of the Server Software

The Cisco UCS C-Series Rack-Mount Server ships with two major software systems installed.

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

Overview

Cisco Integrated Management Controller

CIMC Firmware

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.

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 Servers Documentation 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

???Toggle the locator LED

???Configure the server boot order

???View server properties and sensors

???Manage remote presence

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

Overview

CIMC CLI

???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

???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

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 To recover from a lost admin password, see the Cisco UCS C-Series server installation and service guide for your platform.

Command Modes

The CLI is organized into a hierarchy of command modes, with the EXEC mode being the highest-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.

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

Overview

Command Modes

Note 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.

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

Overview

Complete a Command

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

Command History

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

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

Committing, Discarding, and Viewing Pending Commands

When you enter a configuration command in the CLI, the command is not applied until you enter the commit command. Until committed, a configuration command is pending and can be discarded by entering 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:

Status : present

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

Overview

Online Help for the CLI

Name HDD_02_STATUS:

Status : present

Name HDD_03_STATUS:

Status : present

Name HDD_04_STATUS:

Status : present

Server /chassis #

???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

---

hdd-status: present

---

hdd-status: present

---

hdd-status: present

---

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 cli output yaml to configure the YAML format.

Online Help for the CLI

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

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

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

C H A P T E R 2

Installing the Server OS

This chapter includes the following sections:

??? OS Installation Methods, page 11

??? KVM Console, page 11

??? PXE Installation Servers, page 12

OS Installation Methods

C-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

KVM Console

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

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

???CD/DVD or floppy drive on your computer

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

???USB flash drive on your computer

???CD/DVD or floppy drive on the network

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

???USB flash drive on the network

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

Installing the Server OS

PXE Installation Servers

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

PXE Installation Servers

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

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

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

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

Installing an OS Using a PXE Installation Server

Before You Begin

???Verify that the server can be reached over a VLAN.

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

Procedure

Step 1 Set the boot order to PXE first.

Step 2 Reboot the server.

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

What to Do Next

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

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

Managing the Server

Toggling the Locator LED for a Hard Drive

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

Server# scope chassis

Server /chassis # 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

This example turns on the locator LED on HDD 2:

Server /chassis/hdd #

Managing the Server Boot Order

Server Boot Order

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

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

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

Managing the Server

Configuring the Server Boot Order

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

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

???A user changes the boot order directly through the BIOS.

Configuring the Server Boot Order

Note Do not change the boot order while the host is performing BIOS power-on self test (POST).

Before You Begin

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

Procedure

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

This example sets the boot order and commits the transaction:

Server# scope bios

Server /bios # set boot-order hdd,cdrom,fdd,pxe,efi

Server /bios *# commit

Server /bios # show detail

BIOS:

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

Server /bios #

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

Managing the Server

Viewing the Actual Server Boot Order

What to Do Next

Reboot the server to boot with your new boot order.

Viewing the Actual Server Boot Order

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

Procedure

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

Resetting the Server

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

Before You Begin

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

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

Managing the Server

Shutting Down the Server

Procedure

This example resets the server:

Server# scope chassis

Server /chassis # power hard-reset

This operation will change the server's power state.

Continue?[y|N]

Shutting Down the Server

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

Before You Begin

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

Procedure

The following example shuts down the server:

Server# scope chassis

Server /chassis # power shutdown

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

Managing the Server

Managing Server Power

Powering On the Server

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

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

Before You Begin

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

Procedure

This example turns on the server:

Server# scope chassis

Server /chassis # power on

Powering Off the Server

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

Before You Begin

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

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

Managing the Server

Power Cycling the Server

Procedure

Power Cycling the Server

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

Before You Begin

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

Procedure

This example power cycles the server:

Server# scope chassis

Server /chassis # power cycle

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

Managing the Server

Power Capping Policy

This example displays the detailed power statistics:

Server# show power-cap detail

Cur Consumption (W): 247

Max Consumption (W): 286

Min Consumption (W): 229

Minimum Configurable Limit (W): 285

Maximum Configurable Limit (W): 1250

Power Cap Enabled: yes

Peak Power: 0

Non Compliance Action: throttle

Server#

Power Capping Policy

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

Configuring the Power Cap Policy

Note This feature is not available on some servers.

Before You Begin

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

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

Managing the Server

Configuring the Power Cap Policy

Procedure

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

Server# scope power-cap

Server /power-cap # set enabled yes

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

Server /power-cap *# set non-compliance-action throttle

Server /power-cap *# commit

Server /power-cap # show detail

Cur Consumption (W): 688

Max Consumption (W): 1620

Min Consumption (W): 48

Minimum Configurable Limit (W): 500

Maximum Configurable Limit (W): 2000

Power Cap Enabled: yes

Peak Power: 1000

Non Compliance Action: throttle

Server /power-cap #

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

Managing the Server

Configuring the Power Restore Policy

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

Before You Begin

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

Procedure

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

Server# scope chassis

Server /chassis # set policy power-on

Server /chassis *# set delay fixed

Server /chassis *# set delay-value 180

Server /chassis *# commit

Server /chassis # show detail

Chassis:

Power: on

Serial Number: QCI1404A1IT

Product Name: UCS C200 M1

PID : R200-1120402

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

Locator LED: off

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

Managing the Server

Managing the Flexible Flash Controller

Description: Testing power restore

Power Restore Policy: power-on

Power Delay Type: fixed

Power Delay Value(sec): 180

Server /chassis #

Managing the Flexible Flash Controller

Cisco Flexible Flash

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

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

???Cisco UCS Server Configuration Utility (bootable)

???User-installed (may be bootable)

???Cisco drivers (not bootable)

???Cisco Host Upgrade Utility (bootable)

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

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

Dual Card Management in the Cisco Flexible Flash Controller

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

RAID Partition Enumeration

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

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

Managing the Server

Configuring the Flexible Flash Controller Properties

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

Configuring the Flexible Flash Controller Properties

Before You Begin

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

???Cisco Flexible Flash must be supported by your platform.

Procedure

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

Managing the Server

Booting from the Flexible Flash

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

Server /chassis/flexflash/operational-profile #

Booting from the Flexible Flash

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

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

Before You Begin

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

???Cisco Flexible Flash must be supported by your platform.

Procedure

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

Server# scope bios

Server /bios # set boot-override SCU

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

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

Managing the Server

Resetting the Flexible Flash Controller

Server /bios *# commit

Server /bios #

Resetting the Flexible Flash Controller

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

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

Before You Begin

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

???Cisco Flexible Flash must be supported by your platform.

Procedure

This example resets the flash controller:

Server# scope chassis

Server /chassis # scope flexflash FlexFlash-0

Server /chassis/flexflash # reset

This operation will reset Cisco Flexible Flash controller.

Host traffic to VDs on this device will be disrupted.

Continue?[y|N] y

Server /chassis/flexflash #

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

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

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

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

???The card in the other slot is marked as secondary-active unhealthy.

???Three non-RAID partitions and one RAID partition are created.

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

Managing the Server

Retaining the Configuration of the Flexible Flash Controller

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

???Host connectivity could be disrupted.

Before You Begin

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

???Cisco Flexible Flash must be supported on your server.

Procedure

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

Server# scope chassis

Server /chassis # scope flexflash FlexFlash-0

Server /chassis/flexflash # reset-config slot1

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

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

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

Server /chassis/flexflash/operational-profile #

Retaining the Configuration of the Flexible Flash Controller

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

???There are two unpaired SD cards

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

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

Before You Begin

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

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

Managing the Server

Configuring BIOS Settings

??? Cisco Flexible Flash must be supported on your server.

Procedure

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

Server# scope chassis

Server /chassis # scope flexflash FlexFlash-0

Server /chassis/flexflash # retain-config slot1

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

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

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

Server /chassis/flexflash/operational-profile #

Configuring BIOS Settings

Viewing BIOS Status

Procedure

The BIOS status information contains the following fields:

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

Managing the Server

Configuring Main BIOS Settings

This example displays the BIOS status:

Server# scope bios

Server /bios # show detail

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

Boot Order: EFI,CDROM,HDD

Boot Override Priority:

FW Update/Recovery Status: NONE

FW Update/Recovery Progress: 100

Server /bios #

Configuring Main BIOS Settings

Before You Begin

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

Procedure

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

Managing the Server

Configuring Advanced BIOS Settings

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

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

Server# scope bios

Server /bios # scope main

Server /bios/main # set POSTErrorPause Enabled

Server /bios/main *# commit

Changes to BIOS set-up parameters will require a reboot.

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

Changes will be applied on next reboot.

Server /bios/main #

Configuring Advanced BIOS Settings

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

Before You Begin

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

Procedure

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

Managing the Server

Configuring Server Management BIOS Settings

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

Server# scope bios

Server /bios # scope advanced

Server /bios/advanced # set LvDDRMode Enabled

Server /bios/advanced *# commit

Changes to BIOS set-up parameters will require a reboot.

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

Changes will be applied on next reboot.

Server /bios/advanced #

Configuring Server Management BIOS Settings

Before You Begin

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

Procedure

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

Managing the Server

Restoring BIOS Defaults

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

Server# scope bios

Server /bios # scope server-management

Server /bios/server-management # set BMCPnP Enabled

Server /bios/server-management *# commit

Changes to BIOS set-up parameters will require a reboot.

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

Changes will be applied on next reboot.

Server /bios/server-management #

Restoring BIOS Defaults

Before You Begin

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

Procedure

This example restores BIOS default settings:

Server# scope bios

Server /bios # bios-setup-default

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

All your configuration will be lost.

Changes to BIOS set-up parameters will initiate a reboot.

Continue?[y|N]y

Restoring BIOS Manufacturing Custom Defaults

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

Note This action is only available for some C-Series servers.

Before You Begin

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

???The server must be powered off.

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

Managing the Server

Restoring BIOS Manufacturing Custom Defaults

Procedure

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

Server # scope bios

Server /bios # restore-mfg-defaults

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

The system will be powered on.

Continue? [y|n] N

Server /bios #

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

C H A P T E R 4

Viewing Server Properties

This chapter includes the following sections:

Viewing Server Properties

Procedure

This example displays server properties:

Server# show chassis detail

Chassis:

Power: on

Serial Number: QCI140205ZG

Product Name: UCS C210 M2

PID : R210-2121605W

UUID: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF

Locator LED: off

Description:

Power Restore Policy: power-off

Power Delay Type: fixed

Power Delay Value(sec): 0

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

Viewing Server Properties

Viewing CIMC Properties

Server#

Viewing CIMC Properties

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

Procedure

This example displays CIMC properties:

Server# show cimc detail

CIMC:

Firmware Version: 1.4(2.18)

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

Boot-loader Version: 1.4(2.18).16

Server#

Viewing CPU Properties

Before You Begin

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

Procedure

Server /chassis #

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

Viewing Server Properties

Viewing Memory Properties

Before You Begin

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

Procedure

Server /chassis #

This example displays detailed information about memory properties:

Server# scope chassis

Server /chassis # show dimm detail Name DIMM_A1:

Capacity: 2048 MB

Channel Speed (MHz): 1067

Channel Type: Other

Memory Type Detail: Synchronous

Bank Locator: NODE 0 CHANNEL 0 DIMM 0

Visibility: Yes

Operability: Operable

Manufacturer: 0x802C

Part Number: 18JSF25672PY-1G1D1

Serial Number: 0xDA415F3F

Asset Tag: Unknown

Data Width: 64 bits Name DIMM_A2:

Capacity: 2048 MB --More--

Server /chassis #

This example displays DIMM summary information:

Server# scope chassis

Server /chassis # show dimm-summary

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

Viewing Server Properties

Viewing Power Supply Properties

DIMM Summary:

Memory Speed: 1067 MHz

Total Memory: 16384 MB

Effective Memory: 16384 MB

Redundant Memory: 0 MB

Failed Memory: 0 MB

Ignored Memory: 0 MB

Number of Ignored Dimms: 0

Number of Failed Dimms: 0

Memory RAS possible: Memory configuration can support mirroring

Memory Configuration: Maximum Performance

Server /chassis #

Viewing Power Supply Properties

Before You Begin

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

Procedure

Server /chassis #

Viewing Storage Properties

Viewing Storage Adapter Properties

Before You Begin

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

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

Viewing Server Properties

Viewing the Flexible Flash Controller Properties

Server /chassis #

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

Server /chassis/storageadapter #

Viewing the Flexible Flash Controller Properties

Before You Begin

??? Cisco Flexible Flash must be supported by your platform.

Procedure

This example displays the properties of the flash controller:

Server /chassis # scope flexflash FlexFlash-0

Server /chassis/flexflash #

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

Viewing Server Properties

Viewing Physical Drive Properties

Procedure

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

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # scope physical-drive 1

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

Slot Number 1:

Controller: SAS

Enclosure Device ID: 27

Device ID: 34

Sequence Number: 2

Media Error Count: 0

Other Error Count: 0

Predictive Failure Count: 0

Link Speed: 6.0 Gb/s

Interface Type: SAS

Media Type: HDD

Block Size: 512

Block Count: 585937500

Raw Size: 286102 MB

Non Coerced Size: 285590 MB

Coerced Size: 285568 MB

SAS Address 0: 500000e112693fa2

SAS Address 1:

Connected Port 0:

Connected Port 1:

Connected Port 2:

Connected Port 3:

Connected Port 4:

Connected Port 5:

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

Viewing Server Properties

Viewing Virtual Drive Properties

Connected Port 6:

Connected Port 7:

Power State: powersave

Server /chassis/storageadapter/physical-drive #

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

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # scope physical-drive 1

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

Slot Number 1:

Controller: SAS

Product ID: MBD2300RC

Drive Firmware: 5701

Drive Serial Number: D010P9A0016D

Server /chassis/storageadapter/physical-drive #

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

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # scope physical-drive 1

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

Slot Number 1:

Controller: SAS

State: online

Online: true

Fault: false

Server /chassis/storageadapter/physical-drive #

Viewing Virtual Drive Properties

Procedure

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

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # show virtual-drive

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

Viewing Server Properties

Viewing Nvidia GPU Card Information

Server /chassis/storageadapter #

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

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # scope virtual-drive 1

Server /chassis/storageadapter/virtual-drive #

Viewing Nvidia GPU Card Information

These commands are not available on all UCS C-series servers.

Before You Begin

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

Procedure

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

Server # scope chassis

Server /chassis # show gpu

Server /chassis # scope gpu 5

Server /chassis/gpu # show gpu-list

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

Viewing Server Properties

Viewing PCI Adapter Properties

032

133

Server /chassis/gpu #

Viewing PCI Adapter Properties

Before You Begin

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

Procedure

Server /chassis #

Viewing Network Related Properties

Viewing LOM Properties

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

Procedure

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

C H A P T E R 6

Managing Remote Presence

This chapter includes the following sections:

??? Managing the Virtual KVM, page 55

??? Configuring Virtual Media, page 58

??? Managing Serial over LAN, page 61

Managing the Virtual KVM

KVM Console

???CD/DVD or floppy drive on your computer

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

???USB flash drive on your computer

???CD/DVD or floppy drive on the network

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

???USB flash drive on the network

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

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

Managing Remote Presence

Enabling the Virtual KVM

Before You Begin

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

Procedure

Server /kvm #

Disabling the Virtual KVM

Before You Begin

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

Procedure

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

Managing Remote Presence

Configuring the Virtual KVM

Server /kvm #

Configuring the Virtual KVM

Before You Begin

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

Procedure

This example configures the virtual KVM and displays the configuration:

Server# scope kvm

Server /kvm # set enabled yes

Server /kvm *# set encrypted no

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

Managing Remote Presence

Configuring Virtual Media

Server /kvm *# set kvm-port 2068

Server /kvm *# set max-sessions 4

Server /kvm *# set local-video yes

Server /kvm *# commit

Server /kvm # show detail

KVM Settings:

Encryption Enabled: no

Max Sessions: 4

Local Video: yes

Active Sessions: 0

Enabled: yes

KVM Port: 2068

Server /kvm #

What to Do Next

Launch the virtual KVM from the GUI.

Configuring Virtual Media

Before You Begin

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

Procedure

This example configures virtual media encryption:

Server# scope vmedia

Server /vmedia # set enabled yes

Server /vmedia *# set encryption yes

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

Encryption Enabled: yes

Enabled: yes

Max Sessions: 1

Active Sessions: 0 Server /vmedia #

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

Managing Remote Presence

Viewing Network Mount vMedia Mapping Properties

??? Username and password to connect to the server

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

Server # scope vmedia

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

Server username:

Server password: ****

Confirm password: ****

Server /vmedia #

Viewing Network Mount vMedia Mapping Properties

Before You Begin

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

Procedure

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

Server # scope vmedia

Server /vmedia # show mappings

Removing Network Mounted vMedia Mapping

Before You Begin

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

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

Managing Remote Presence

Managing Serial over LAN

Procedure

This example shows how to unmap a local vmedia volume:

Server # scope vmedia

Server /vmedia # show mappings

Server /vmedia #

Managing Serial over LAN

Serial Over LAN

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

Guidelines and Restrictions for Serial Over LAN

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

???console redirection to serial port A

???no flow control

???baud rate the same as configured for SoL

???VT-100 terminal type

???legacy OS redirection disabled

The SoL session will display line-oriented information such as boot messages, and character-oriented screen menus such as BIOS setup menus. If the server boots an operating system or application with a bitmap-oriented

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

Managing Remote Presence

Configuring Serial Over LAN

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

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

Configuring Serial Over LAN

Before You Begin

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

Procedure

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

Managing Remote Presence

Launching Serial Over LAN

This example configures SoL:

Server# scope sol

Server /sol # set enabled yes

Server /sol *# set baud-rate 115200

Server /sol # show detail

Serial Over LAN:

Enabled: yes

Baud Rate(bps): 115200

Com Port: com2

Server /sol #

Launching Serial Over LAN

Procedure

What to Do Next

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

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

Managing User Accounts

Configuring Active Directory

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

??? Launch the KVM console and virtual media

??? Clear all logs

??? Toggle the locator LED

??? admin???This user can perform all actions available through the GUI, CLI, and IPMI.

This example configures user 5 as an admin:

Configuring Active Directory

Active Directory

Active Directory is a technology that provides a variety of network services including LDAP-like directory services, Kerberos-based authentication, and DNS-based naming. The CIMC utilizes the Kerberos-based authentication service of Active Directory.

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

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

Configuring the Active Directory Server

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

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

Managing User Accounts

Configuring the Active Directory Server

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

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

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

Procedure

Step 1 Ensure that the Active Directory schema snap-in is installed.

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

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

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

b)Click the Attributes tab and click Add.

c)Type C to select the CiscoAVPair attribute.

d)Click OK.

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

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

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

Managing User Accounts

Configuring Active Directory in CIMC

What to Do Next

Use the CIMC to configure Active Directory.

Configuring Active Directory in CIMC

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

Before You Begin

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

Procedure

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

Managing User Accounts

Configuring Active Directory Groups in CIMC

This example configures AD using the CiscoAVPair attribute:

Server# scope ldap

Server /ldap # set enabled yes

Server /ldap *# set dc1 192.0.20.123

Server /ldap *# set gc1 192.0.20.11

Server /ldap *# set timeout 60

Server /ldap *# set encrypted yes

Server /ldap *# set base-dn example.com

Server /ldap *# set attribute CiscoAVPair

Server /ldap *# commit

Server /ldap # show detail

LDAP Settings:

Domain Controller 1: 192.0.20.123

Domain Controller 2: 0.0.0.0

Domain Controller 3: 0.0.0.0

BaseDN: example.com

Encrypted: yes

Timeout: 60

Enabled: yes

Attribute: CiscoAvPair

Group Authorization: no

Global Catalog 1: 192.0.20.11

Global Catalog 2: 0.0.0.0

Global Catalog 3: 0.0.0.0

Server /ldap #

What to Do Next

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

Configuring Active Directory Groups in CIMC

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

Before You Begin

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

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

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

Managing User Accounts

Viewing User Sessions

Server /ldap/role-group #

Viewing User Sessions

Procedure

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

This example displays information about current user sessions:

Terminating a User Session

Before You Begin

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

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

C H A P T E R 8

Configuring Network-Related Settings

This chapter includes the following sections:

Server NIC Configuration

Server NICs

NIC Mode

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

???Dedicated???The management port is used to access the CIMC.

???Shared LOM???Any LOM (LAN On Motherboard) port can be used to access the CIMC.

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

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

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

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

Configuring Network-Related Settings

Configuring Server NICs

NIC Redundancy

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

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

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

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

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

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

Configuring Server NICs

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

Before You Begin

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

Procedure

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

Configuring Network-Related Settings

Configuring the Server VLAN

This example configures and displays the IPv4 network settings:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set dhcp-enabled yes

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

Server /cimc/network *# set v4-netmask 255.255.248.0

Server /cimc/network *# set v4-gateway 10.20.30.1

Server /cimc/network *# set dns-use-dhcp-enabled no

Server /cimc/network *# set preferred-dns-server 192.168.30.31

Server /cimc/network *# set alternate-dns-server 192.168.30.32

Server /cimc/network *# commit

Server /cimc/network # show detail

Network Setting:

IPv4 Address: 10.20.30.11

IPv4 Netmask: 255.255.248.0

IPv4 Gateway: 10.20.30.1

DHCP Enabled: yes

Obtain DNS Server by DHCP: no

Preferred DNS: 192.168.30.31

Alternate DNS: 192.168.30.32

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Hostname: Server

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

NIC Mode: dedicated

NIC Redundancy: none

Server /cimc/network #

Configuring the Server VLAN

Before You Begin

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

Procedure

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

Configuring Network-Related Settings

Connecting to a Port Profile

This example configures the server VLAN:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set vlan-enabled yes

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

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

Server /cimc/network *# commit

Server /cimc/network # show detail

Network Setting:

IPv4 Address: 10.20.30.11

IPv4 Netmask: 255.255.248.0

IPv4 Gateway: 10.20.30.1

DHCP Enabled: yes

Obtain DNS Server by DHCP: no

Preferred DNS: 192.168.30.31

Alternate DNS: 192.168.30.32

VLAN Enabled: yes

VLAN ID: 10

VLAN Priority: 32

Hostname: Server

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

NIC Mode: dedicated

NIC Redundancy: none

Server /cimc/network #

Connecting to a Port Profile

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

Before You Begin

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

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

Configuring Network-Related Settings

Connecting to a Port Profile

Procedure

This example connects to port profile abcde12345:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set port-profile abcde12345

Server /cimc/network *# commit

Server /cimc/network # show detail

Network Setting:

IPv4 Address: 10.193.66.174

IPv4 Netmask: 255.255.248.0

IPv4 Gateway: 10.193.64.1

DHCP Enabled: no

Obtain DNS Server by DHCP: no

Preferred DNS: 0.0.0.0

Alternate DNS: 0.0.0.0

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Port Profile: abcde12345

Hostname: Server

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

NIC Mode: dedicated

NIC Redundancy: none

Server /cimc/network #

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

Configuring Network-Related Settings

Network Security Configuration

Network Security

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

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

Configuring Network Security

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

Before You Begin

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

Procedure

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

Configuring Network-Related Settings

Network Time Protocol Configuration

This example configures IP blocking:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # scope ipblocking

Server /cimc/network/ipblocking # set enabled yes

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

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

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

Server /cimc/network/ipblocking *# commit

Server /cimc/network/ipblocking #

Network Time Protocol Configuration

Configuring Network Time Protocol Settings

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

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

Before You Begin

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

Procedure

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

C H A P T E R 9

Managing Network Adapters

This chapter includes the following sections:

Overview of the Cisco UCS C-Series Network Adapters

Note The procedures in this chapter are available only when a Cisco UCS C-Series network adapter is installed in the chassis.

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

???Cisco UCS P81E Virtual Interface Card

???Cisco UCS VIC1225 Virtual Interface Card

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

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

Managing Network Adapters

Overview of the Cisco UCS C-Series Network Adapters

Cisco UCS P81E Virtual Interface Card

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

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

???Delivers uncompromising virtualization support, including hardware-based implementation of Cisco VN-Link technology and pass-through switching.

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

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

Cisco UCS VIC1225 Virtual Interface Card

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

The Cisco UCS VIC 1225 implements the Cisco Virtual Machine Fabric Extender (VM-FEX), which unifies virtual and physical networking into a single infrastructure. It provides virtual-machine visibility from the physical network and a consistent network operations model for physical and virtual servers. In virtualized environments, this highly configurable and self-virtualized adapter provides integrated, modular LAN interfaces on Cisco UCS C-Series Rack-Mount Servers. Additional features and capabilities include:

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

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

???Half-height design reserves full-height slots in servers for Cisco certified third-party adapters.

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

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

Managing Network Adapters

Viewing Network Adapter Properties

Procedure

This example displays the properties of adapter 2:

Configuring Network Adapter Properties

Before You Begin

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

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

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

Managing Network Adapters

Managing vHBAs

Procedure

This example configures the properties of adapter 1:

Managing vHBAs

Guidelines for Managing vHBAs

When managing vHBAs, consider the following guidelines and restrictions:

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

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

Managing Network Adapters

Viewing vHBA Properties

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

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

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

Viewing vHBA Properties

Procedure

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

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

Name fc0:

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

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

FC SAN Boot: Disabled

Persistent LUN Binding: Disabled

Uplink Port: 0

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

CoS: 3

VLAN: NONE

Rate Limiting: OFF

PCIe Device Order: ANY

EDTOV: 2000

RATOV: 10000

Maximum Data Field Size: 2112

Channel Number: 3

Port Profile:

Server /chassis/adapter #

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

Managing Network Adapters

Creating a vHBA

This example configures the properties of a vHBA:

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

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

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

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

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

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

What to Do Next

Reboot the server to apply the changes.

Creating a vHBA

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

Before You Begin

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

Procedure

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

Managing Network Adapters

Deleting a vHBA

This example creates a vHBA on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

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

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

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

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

What to Do Next

???Reboot the server to create the vHBA.

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

Deleting a vHBA

Procedure

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

Managing Network Adapters

vHBA Boot Table

This example deletes a vHBA on adapter 1:

vHBA Boot Table

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

Viewing the Boot Table

Procedure

This example displays the boot table for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 1

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

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

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

Creating a Boot Table Entry

You can create up to four boot table entries.

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

Managing Network Adapters

Deleting a Boot Table Entry

Procedure

This example creates a boot table entry for vHBA fc1:

Server# scope chassis

Server /chassis # scope adapter 1

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

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

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

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

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

Deleting a Boot Table Entry

Procedure

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

Managing Network Adapters

vHBA Persistent Binding

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

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

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

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

What to Do Next

Reboot the server to apply the changes.

vHBA Persistent Binding

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

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

Managing Network Adapters

Enabling Persistent Binding

Procedure

This example enables persistent binding for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 4

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

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

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

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

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

Disabling Persistent Binding

Procedure

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

Managing Network Adapters

Rebuilding Persistent Binding

This example disables persistent binding for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 4

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

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

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

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

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

Rebuilding Persistent Binding

Before You Begin

Persistent binding must be enabled in the vHBA properties.

Procedure

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

Managing Network Adapters

Managing vNICs

This example rebuilds the persistent binding table for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 4

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

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

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

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

Managing vNICs

Guidelines for Managing vNICs

When managing vNICs, consider the following guidelines and restrictions:

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

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

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

Viewing vNIC Properties

Procedure

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

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

Managing Network Adapters

Modifying vNIC Properties

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

Name eth0:

MTU: 1500

Uplink Port: 0

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

CoS: 0

Trust Host CoS: disabled

PCI Order: ANY

VLAN: NONE

VLAN Mode: TRUNK

Rate Limiting: OFF

PXE Boot: enabled

Channel Number: N/A

Port Profile: N/A

Uplink Failover: N/A

Uplink Failback Timeout: N/A

Server /chassis/adapter #

Modifying vNIC Properties

Before You Begin

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

Procedure

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

Managing Network Adapters

Creating a vNIC

This example configures the properties of a vNIC:

Server /chassis/adapter/host-eth-if/offload *# set tcp-segment-offload enable

Server /chassis/adapter/host-eth-if/offload *# exit

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

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

What to Do Next

Reboot the server to apply the changes.

Creating a vNIC

The adapter provides two permanent vNICs. You can create up to 16 additional vNICs.

Before You Begin

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

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

Managing Network Adapters

Deleting a vNIC

Procedure

This example creates a vNIC on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # create host-eth-if Vnic5

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

New host-eth-if settings will take effect upon the next server reset

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

Deleting a vNIC

Procedure

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

Managing Network Adapters

Configuring iSCSI Boot Capability

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

This example deletes a vNIC on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # delete host-eth-if Vnic5

Server /chassis/adapter *# commit

Server /chassis/adapter #

Configuring iSCSI Boot Capability

Configuring iSCSI Boot Capability for vNICs

When the rack-servers are configured in a standalone mode, and when the VIC adapters are directly attached to the Nexus 5000 family of switches, you can configure these VIC adapters to boot the servers remotely from iSCSI storage targets. You can configure Ethernet vNICs to enable a rack server to load the host OS image from remote iSCSI target devices.

To configure the iSCSI boot capability on a vNIC:

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

???To configure a vNIC to boot a server remotely from an iSCSI storage target, you must enable the PXE boot option on the vNIC.

Note You can configure a maximum of 2 iSCSI vNICs for each host.

Configuring iSCSI Boot Capability on a vNIC

You can configure a maximum of 2 iSCSI vNICs for each host.

Before You Begin

???To configure a vNIC to boot a server remotely from an iSCSI storage target, you must enable the PXE boot option on the vNIC.

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

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

Managing Network Adapters

Configuring iSCSI Boot Capability

Procedure

This example shows how to configure the iSCSI boot capability for a vNIC:

Server # scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-eth-if eth0

Server /chassis/adapter/host-eth-if # create iscsi-boot 0

Server /adapter/host-eth-if/iscsi-boot *# set dhcp-net-settings enabled

Server /adapter/host-eth-if/iscsi-boot *# set initiator-name iqn.2012-01.com.adser:abcde

Server /adapter/host-eth-if/iscsi-boot *# set dhcp-iscsi-settings enabled

Server /adapter/host-eth-if/iscsi-boot *# commit

New host-eth-if settings will take effect upon the next server reset

Server /adapter/host-eth-if/iscsi-boot #

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

Managing Network Adapters

Managing VM FEX

Deleting an iSCSI Boot Configuration for a vNIC

Before You Begin

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

Procedure

This example shows how to delete the iSCSI boot capability for a vNIC:

Server # scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-eth-if eth0

Server /chassis/adapter/host-eth-if # delete iscsi-boot 0

Server /adapter/host-eth-if/iscsi-boot *# commit

New host-eth-if settings will take effect upon the next server reset

Server /adapter/host-eth-if/iscsi-boot #

Managing VM FEX

Virtual Machine Fabric Extender

Cisco Virtual Machine Fabric Extender (VM FEX) extends the (prestandard) IEEE 802.1Qbh port extender architecture to virtual machines. In this architecture, each VM interface is provided with a virtual Peripheral Component Interconnect Express (PCIe) device and a virtual port on a switch.

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

Managing Network Adapters

VM FEX Settings

This example displays the VM FEX properties:

Server /chassis/adapter # show vmfex detail

Name pts0:

MTU: 1500

Uplink Port: 0

MAC Address: 00:00:00:00:00:00

CoS: N/A

Trust Host CoS:

PCI Order:

VLAN: N/A

VLAN Mode: N/A

Rate Limiting:

PXE Boot: disabled

Channel Number: 0

Port Profile:

Uplink Failover: Enabled

Uplink Failback Timeout: 5

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

VM FEX Settings

The following tables describe the VM FEX settings that you can view.

General Properties Settings

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

Managing Network Adapters

Managing Storage Adapters

Create Virtual Drive from Unused Physical Drives

Before You Begin

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

Procedure

This example shows how to create a new virtual drive that spans two unused physical drives.

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # create-virtual-drive Please enter RAID level

(0, 1, 5, 6, 10, 50, 60) --> 1

Please choose from the following 2 unused physical drives:

Slot 6: size 68664 MB

Slot 7: size 68664 MB

Specify physical disks for span 0:

Enter comma-separated PDs from above list--> 6,7

Please enter Virtual Drive name (15 characters maximum)--> test_v_drive

Please enter Virtual Drive size in MB, GB, or TB

Example format: '400 GB' --> 1000 MB

Optional attribute:

Write Policy: defaults to Write Back

OK? (y or n)--> n

0:Write Through

1:Write Back

2:Write Back with Bad BBU

3:Write Back Adaptive

Choose number from above options--> 2

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

Managing Network Adapters

Create Virtual Drive from an Existing Drive Group

Write Policy will be set to Write Back with Bad BBU (2 and 'write-policy\:2')

New virtual drive will have the following characteristics: - Spans: '[6.7]'

- RAID level: '1'

- Name: 'test_v_drive'

- Size: 1000 MB

- Write Policy: Write Back with Bad BBU

Server /chassis/storageadapter #

Create Virtual Drive from an Existing Drive Group

Before You Begin

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

Procedure

This example shows how to carve a new virtual drive out of unused space in an existing RAID 1 drive group:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

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

Managing Network Adapters

Clearing Foreign Configuration

New virtual drive will have the following characteristics:

-It will share space with virtual drive 3

-Name: 'new_from_test'

-Size: 500 MB

Server /chassis/storageadapter #

Clearing Foreign Configuration

Important This task clears all foreign configuration on the controller. Also, all configuration information from all physical drives hosting foreign configuration is deleted. This action cannot be reverted.

Before You Begin

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

Procedure

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

Managing Network Adapters

Deleting a Virtual Drive

This example shows how to clear all foreign configurations on the MegaRAID controller in slot 3:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # clear-foreign-config

Are you sure you want to clear all foreign configurations on this controller?

All data on the drive(s) will be lost.

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter #

Deleting a Virtual Drive

Important This task deletes a virtual drive, including the drives that run the booted operating system. So back up any data that you want to retain before you delete a virtual drive.

Before You Begin

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

Procedure

This example shows how to delete virtual drive 3.

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive # delete-virtual-drive

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

Managing Network Adapters

Initializing a Virtual Drive

Are you sure you want to delete virtual drive 3?

All data on the drive will be lost. Enter 'yes' to confirm -> yes

Server /chassis/storageadapter/virtual-drive #

Initializing a Virtual Drive

All data on a virtual drive is lost when you initialize the drive. Before you run an initialization, back up any data on the virtual drive that you want to save.

Before You Begin

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

Procedure

This example shows how to initialize virtual drive 3 using fast initialization:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive # start-initialization

Are you sure you want to initialize virtual drive 3?

All data on the drive will be lost. Enter 'yes' to confirm -> yes

Fast (0) or full (1) initialization? -> 0

Server /chassis/storageadapter/virtual-drive # get-operation-status

progress-percent: 20%

elapsed -seconds: 30

operation-in-progress: initializing virtual drive

Server /chassis/storageadapter/virtual-drive #

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

Managing Network Adapters

Set as Boot Drive

Before You Begin

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

Procedure

This example shows how to specify the controller to boot from virtual drive 3:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Modifying Attributes of a Virtual Drive

Before You Begin

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

Procedure

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

Managing Network Adapters

Making a Dedicated Hot Spare

This example shows how to carve a new virtual drive out of unused space in an existing RAID 1 drive group:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope virtual-drive

Server /chassis/storageadapter/virtual-drive # modify-attributes

Current write policy: Write Back

0:Write Through

1:Write Back

2:Write Back even if Bad BBU

Choose number from above options --> 0

The following attribute will be modified:

- Write policy: Write Through

OK? (y or n) --> y

operation in progress.

Server /chassis/storageadapter/virtual-drive #

Making a Dedicated Hot Spare

Before You Begin

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

Procedure

This example shows how to make physical drive 3 a dedicated hot spare for virtual drive 6:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

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

Managing Network Adapters

Making a Global Hot Spare

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # make-dedicated-hot-spare

5:VD_OS_1, RAID 0, 102400 MB, physical disks: 1

6:VD_OS_2, RAID 0, 12288 MB, physical disks: 1

7:VD_OS_3, RAID 0, 12288 MB, physical disks: 1

8:VD_DATA_1, RAID 0, 12512 MB, physical disks: 1

9:RAID1_2358, RAID 1, 40000 MB, physical disks: 2,3,5,8

11:JFB_RAID1_67, RAID 1, 20000 MB, physical disks: 6,7

12:JFB_Crv_R1_40, RAID 1, 40000 MB, physical disks: 6,7

13:JFB_R1_10GB, RAID 1, 10000 MB, physical disks: 6,7

Please choose from the above 8 virtual drives-->6

Server /chassis/storageadapter/physical-drive #

Making a Global Hot Spare

Before You Begin

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

Procedure

This example shows how to make physical drive 3 a global hot spare:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # make-global-hot-spare

Server /chassis/storageadapter/physical-drive #

Preparing a Drive for Removal

You can confirm this task only on physical drives that display the Unconfigured Good status.

Before You Begin

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

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

Managing Network Adapters

Removing a Drive from Hot Spare Pools

Procedure

This example shows how to prepare physical drive 3 for removal.

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # prepare-for-removal

Server /chassis/storageadapter/physical-drive #

Removing a Drive from Hot Spare Pools

Before You Begin

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

Procedure

This example shows how to remove physical drive 3 from the hot spare pools:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # remove-hot-spare

Server /chassis/storageadapter/physical-drive #

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

Managing Network Adapters

Undo Preparing a Drive for Removal

Before You Begin

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

Procedure

This example shows how to respin physical drive 3 after preparing the drive for removal.

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # undo-prepare-for-removal

Server /chassis/storageadapter/physical-drive #

Enabling Auto Learn Cycles for the Battery Backup Unit

Before You Begin

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

Procedure

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

Managing Network Adapters

Disabling Auto Learn Cycles for the Battery Backup Unit

This example shows how to enable the battery auto-learn cycles:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-2

Server /chassis/storageadapter # scope bbu

Server /chassis/storageadapter/bbu # enable-auto-learn

Automatic BBU learn cycles will occur without notice if enabled. Are you sure? [y/n] --> y

enable-auto-learn initiated

Server /chassis/storageadapter/bbu #

Disabling Auto Learn Cycles for the Battery Backup Unit

Before You Begin

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

Procedure

This example shows how to disables the battery auto-learn cycles:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-2

Server /chassis/storageadapter # scope bbu

Server /chassis/storageadapter/bbu # disable-auto-learn Automatic BBU learn cycles will no longer occur if disabled. Are you sure? [y/n] --> y

disable-auto-learn initiated

Server /chassis/storageadapter/bbu #

Starting a Learn Cycle for a Battery Backup Unit

Before You Begin

You must be logged in as an admin to use this command.

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

Managing Network Adapters

Toggling the Locator LED for a Physical Drive

Procedure

This example shows how to initiate the learn cycles for a battery:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-2

Server /chassis/storageadapter # scope bbu

Server /chassis/storageadapter/bbu # start-learn-cycle

Server /chassis/storageadapter/bbu #

Toggling the Locator LED for a Physical Drive

Before You Begin

You must be logged in as an admin to perform this task.

Procedure

This example shows how to enable the locator LED for physical drive 3:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-2

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # locator-led on

Server /chassis/storageadapter/physical-drive* # commit

Server /chassis/storageadapter/physical-drive #

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

Managing Network Adapters

Viewing Storage Controller Logs

Before You Begin

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

Procedure

This example shows how to display storage controller logs:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # show log

Server /chassis/storageadapter #

Backing Up and Restoring the Adapter Configuration

Exporting the Adapter Configuration

The adapter configuration can be exported as an XML file to a TFTP server.

Important If any firmware or BIOS updates are in progress, do not export the adapter configuration until those tasks are complete.

Before You Begin

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

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

Managing Network Adapters

Importing the Adapter Configuration

Procedure

This example exports the configuration of adapter 1:

Importing the Adapter Configuration

Important If any firmware or BIOS updates are in progress, do not import the adapter configuration until those tasks are complete.

Before You Begin

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

Procedure

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

Managing Network Adapters

Restoring Adapter Defaults

This example imports a configuration for the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # import-vnic 192.0.2.34 /ucs/backups/adapter4.xml

Import succeeded.

New VNIC adapter settings will take effect upon the next server reset.

Server /chassis/adapter #

What to Do Next

Reboot the server to apply the imported configuration.

Restoring Adapter Defaults

Before You Begin

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

Procedure

This example restores the default configuration of the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # adapter-reset-defaults 1

This operation will reset the adapter to factory default.

All your configuration will be lost.

Continue?[y|N] y

Server /chassis #

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

Managing Network Adapters

Managing Adapter Firmware

Adapter Firmware

A Cisco UCS C-Series network adapter contains the following firmware components:

???Adapter firmware???The main operating firmware, consisting of an active and a backup image, can be installed from the CIMC GUI or CLI interface or from the Host Upgrade Utility (HUU). You can upload a firmware image from either a local file system or a TFTP server.

???Bootloader firmware???The bootloader firmware cannot be installed from the CIMC GUI or CLI. You can install this firmware using the Host Upgrade Utility.

Installing Adapter Firmware

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

Before You Begin

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

Procedure

This example begins an adapter firmware upgrade on the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # update-adapter-fw 192.0.2.34 /ucs/adapters/adapter4.bin activate 1

Server /chassis #

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

Managing Network Adapters

Activating Adapter Firmware

What to Do Next

To activate the new firmware, see Activating Adapter Firmware, on page 131.

Activating Adapter Firmware

Important While the activation is in progress, do not:

???Reset, power off, or shut down the server.

???Reboot or reset CIMC.

???Activate any other firmware.

???Export technical support or configuration data.

Before You Begin

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

Procedure

This example activates adapter firmware image 2 on the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # activate-adapter-fw 1 2

Firmware image activation suceeded

Please reset the server to run the activated image

Server /chassis #

What to Do Next

Reboot the server to apply the changes.

Resetting the Adapter

Before You Begin

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

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

Managing Network Adapters

Resetting the Adapter

Procedure

This example resets the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # adapter-reset 1

This operation will reset the adapter and the host if it is on.

You may lose connectivity to the CIMC and may have to log in again.

Continue?[y|N] y

Server /chassis #

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

Configuring Communication Services

Configuring XML API

This example configures SSH for the CIMC:

Server /ssh #

Configuring XML API

XML API for CIMC

The Cisco CIMC XML application programming interface (API) is a programmatic interface to CIMC for a C-Series Rack-Mount Server. The API accepts XML documents through HTTP or HTTPS.

For detailed information about the XML API, see Cisco UCS Rack-Mount Servers CIMC XML API

Programmer???s Guide.

Enabling XML API

Before You Begin

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

Procedure

This example enables XML API control of CIMC and commits the transaction:

Server# scope xmlapi

Server /xmlapi # set enabled yes

Server /xmlapi *# commit

Server /xmlapi # show detail

XMLAPI Settings:

Enabled: yes

Active Sessions: 0

Max Sessions: 4

Server /xmlapi #

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

Configuring Communication Services

Configuring IPMI

IPMI Over LAN

Intelligent Platform Management Interface (IPMI) defines the protocols for interfacing with a service processor embedded in a server platform. This service processor is called a Baseboard Management Controller (BMC) and resides on the server motherboard. The BMC links to a main processor and other on-board elements using a simple serial bus.

During normal operations, IPMI lets a server operating system obtain information about system health and control system hardware. For example, IPMI enables the monitoring of sensors, such as temperature, fan speeds and voltages, for proactive problem detection. If server temperature rises above specified levels, the server operating system can direct the BMC to increase fan speed or reduce processor speed to address the problem.

Configuring IPMI over LAN

Configure IPMI over LAN when you want to manage the CIMC with IPMI messages.

Before You Begin

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

Procedure

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

Configuring Communication Services

Configuring SNMP

This example configures IPMI over LAN for the CIMC:

Server# scope ipmi

Server /ipmi # set enabled yes

Server /ipmi *# set privilege-level admin

Server /ipmi *# set encryption-key abcdef01234567890abcdef01234567890abcdef

Server /ipmi #

Configuring SNMP

SNMP

The Cisco UCS C-Series Rack-Mount Servers support the Simple Network Management Protocol (SNMP) for viewing server configuration and status and for sending fault and alert information by SNMP traps. For information on Management Information Base (MIB) files supported by CIMC, see the MIB Quick Reference for Cisco UCS at this URL: http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/mib/reference/UCS_ MIBRef.html.

Configuring SNMP Properties

Before You Begin

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

Procedure

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

Configuring Communication Services

Configuring SNMP Properties

This example configures the SNMP properties and commits the transaction:

Server# scope snmp

Server /snmp # set enabled yes

Server /snmp *# commit

Server /snmp # set community-str cimcpublic

Server /snmp # set community-access Full

Server /snmp # set trap-community-str public

Server /snmp *# set sys-contact "User Name <username@example.com> +1-408-555-1212"

Server /snmp *# set sys-location "San Jose, California"

Server /snmp *# commit

Server /snmp # show detail

SNMP Settings:

SNMP Port: 161

System Contact: User Name <username@example.com> +1-408-555-1212

System Location: San Jose, California

SNMP Community: cimcpublic

SNMP Trap community: public

SNMP Community access: Full

Enabled: yes

Server /snmp #

What to Do Next

Configure SNMP trap settings as described in Configuring SNMP Trap Settings, on page 139.

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

Configuring Communication Services

Configuring SNMP Trap Settings

Before You Begin

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

???SNMP must be enabled and saved before trap settings can be configured.

Procedure

This example configures general SNMP trap settings and trap destination number 1 and commits the transaction:

Server# scope snmp

Server /snmp # Scope trap-destinations 1

Server /snmp/trap-destination *# set enabled yes

Server /snmp/trap-destination *# set version 2

Server /snmp/trap-destination *# set type inform

Server /snmp/trap-destination *# set user user1

Server /snmp/trap-destination *# set v4-addr 192.2.3.4

Server /snmp/trap-destination *# commit

Server /snmp/trap-destination # show detail

Trap Destination 1:

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

Configuring Communication Services

Sending a Test SNMP Trap Message

Enabled: yes

SNMP version: 2

Trap type: inform

SNMP user: user1

IPv4 Address: 192.2.3.4

Delete Trap: no

Server /snmp/trap-destination #

Sending a Test SNMP Trap Message

Before You Begin

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

Procedure

This example sends a test message to all the enabled SNMP trap destinations:

Server# scope snmp

Server /snmp # sendSNMPtrap

SNMP Test Trap sent to the destination.

Server /snmp #

Configuring SNMPv3 Users

Before You Begin

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

???SNMP must be enabled and saved before these configuration commands are accepted.

Procedure

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

Configuring Communication Services

Configuring SNMPv3 Users

Please enter v3priv-auth-key:!1@2#3$4%5^6&7*8

Please confirm v3priv-auth-key:!1@2#3$4%5^6&7*8

Server /snmp/v3users *# commit

Settings are being applied ... allow a few minutes for the process to complete

Server /snmp/v3users # show detail

User 2:

Add User: yes

Security Name: ucsSNMPV3user

Security Level: authpriv

Auth Type: SHA

Auth Key: ******

Encryption: AES

Private Key: ******

Server /snmp/v3users #

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

C H A P T E R 11

Managing Certificates

This chapter includes the following sections:

??? Managing the Server Certificate, page 143

??? Generating a Certificate Signing Request, page 143

??? Creating a Self-Signed Certificate, page 145

??? Uploading a Server Certificate, page 147

Managing the Server Certificate

You can generate a certificate signing request (CSR) to obtain a new certificate, and you can upload the new certificate to the CIMC to replace the current server certificate. The server certificate may be signed either by a public Certificate Authority (CA), such as Verisign, or by your own certificate authority.

Procedure

Step 1 Generate the CSR from the CIMC.

Step 2 Submit the CSR file to a certificate authority that will issue and sign your certificate. If your organization generates its own self-signed certificates, you can use the CSR file to generate a self-signed certificate.

Step 3 Upload the new certificate to the CIMC.

Note The uploaded certificate must be created from a CSR generated by the CIMC. Do not upload a certificate that was not created by this method.

Generating a Certificate Signing Request

Before You Begin

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

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

Managing Certificates

Generating a Certificate Signing Request

Procedure

You will be prompted to enter the following information for the certificate signing request:

After you have entered the requested information, the system will generate and display a certificate signing request in the console output. A CSR file will not be created, but you can copy the CSR information from the console output and paste the information into a text file.

This example generates a certificate signing request:

Server# scope certificate

Server /certificate # generate-csr

Common Name (CN): test.example.com

Organization Name (O): Example, Inc.

Organization Unit (OU): Test Department

Locality (L): San Jose

StateName (S): CA

Country Code (CC): US

Email: user@example.com

Continue to generate CSR?[y|N]y

-----BEGIN CERTIFICATE REQUEST-----

MIIB/zCCAWgCAQAwgZkxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEVMBMGA1UE

BxMMU2FuIEpvc2UsIENBMRUwEwYDVQQKEwxFeGFtcGxlIEluYy4xEzARBgNVBAsT

ClRlc3QgR3JvdXAxGTAXBgNVBAMTEHRlc3QuZXhhbXBsZS5jb20xHzAdBgkqhkiG

9w0BCQEWEHVzZXJAZXhhbXBsZS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ

AoGBAMZw4nTepNIDhVzb0j7Z2Je4xAG56zmSHRMQeOGHemdh66u2/XAoLx7YCcYU

ZgAMivyCsKgb/6CjQtsofvzxmC/eAehuK3/SINv7wd6Vv2pBt6ZpXgD4VBNKONDl

GMbkPayVlQjbG4MD2dx2+H8EH3LMtdZrgKvPxPTE+bF5wZVNAgMBAAGgJTAjBgkq

hkiG9w0BCQcxFhMUQSBjaGFsbGVuZ2UgcGFzc3dvcmQwDQYJKoZIhvcNAQEFBQAD

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

Managing Certificates

Creating a Self-Signed Certificate

gYEAG61CaJoJaVMhzCl903O6Mg51zq1zXcz75+VFj2I6rH9asckCld3mkOVx5gJU

Ptt5CVQpNgNLdvbDPSsXretysOhqHmp9+CLv8FDuy1CDYfuaLtvlWvfhevskV0j6

mK3Ku+YiORnv6DhxrOoqau8r/hyI/L43l7IPN1HhOi3oha4=

-----END CERTIFICATE REQUEST-----

Copy everything from "-----BEGIN ..." to "END CERTIFICATE REQUEST-----", paste to a file, send to your chosen CA for signing,

and finally upload the signed certificate via upload command.

---OR---

Continue to self sign CSR and overwrite the current certificate? All HTTPS and SSH sessions will be disconnected. [y|N]N

What to Do Next

Perform one of the following tasks:

???If you do not want to obtain a certificate from a public certificate authority, and if your organization does not operate its own certificate authority, you can allow CIMC to internally generate a self-signed certificate from the CSR and upload it immediately to the server. Type y after the final prompt in the example to perform this action.

???If your organization operates its own certificate server for generating self-signed certificates, copy the command output from "-----BEGIN ..." to "END CERTIFICATE REQUEST-----" and paste to a file named csr.txt. Input the CSR file to your certificate server to generate a self-signed certificate.

???If you will obtain a certificate from a public certificate authority, copy the command output from "-----BEGIN ..." to "END CERTIFICATE REQUEST-----" and paste to a file named csr.txt. Submit the CSR file to the certificate authority to obtain a signed certificate.

If you did not use the first option, in which CIMC internally generates and uploads a self-signed certificate, you must upload the new certificate using the upload command in certificate command mode.

Creating a Self-Signed Certificate

As an alternative to using a public Certificate Authority (CA) to generate and sign a server certificate, you can operate your own CA and sign your own certificates. This section shows commands for creating a CA and generating a server certificate using the OpenSSL certificate server running on Linux. For detailed information about OpenSSL, see http://www.openssl.org.

Note These commands are to be entered on a Linux server with the OpenSSL package, not in the CIMC CLI.

Before You Begin

Obtain and install a certificate server software package on a server within your organization.

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

Managing Certificates

Creating a Self-Signed Certificate

Procedure

This example shows how to create a CA and to generate a server certificate signed by the new CA. These commands are entered on a Linux server running OpenSSL.

# /usr/bin/openssl genrsa -out ca.key 1024

Generating RSA private key, 1024 bit long modulus

.............++++++

.....++++++

e is 65537 (0x10001)

# /usr/bin/openssl req -new -x509 -days 365 -key ca.key -out ca.crt

You are about to be asked to enter information that will be incorporated into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank For some fields there will be a default value,

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

Managing Certificates

Uploading a Server Certificate

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [GB]:US

State or Province Name (full name) [Berkshire]:California

Locality Name (eg, city) [Newbury]:San Jose

Organization Name (eg, company) [My Company Ltd]:Example Incorporated

Organizational Unit Name (eg, section) []:Unit A

Common Name (eg, your name or your server's hostname) []:example.com

Email Address []:admin@example.com

#echo "nsCertType = server" > openssl.conf

#/usr/bin/openssl x509 -req -days 365 -in csr.txt -CA ca.crt -set_serial 01 -CAkey ca.key -out server.crt -extfile openssl.conf

Signature ok

subject=/C=US/ST=California/L=San Jose/O=Example Inc./OU=Unit A/CN=example.com/emailAddress=john@example.com

Getting CA Private Key

What to Do Next

Upload the new certificate to the CIMC.

Uploading a Server Certificate

Before You Begin

You must log in as a user with admin privileges to upload a certificate.

The certificate to be uploaded must be available as readable text. During the upload procedure, you will copy the certificate text and paste it into the CLI.

Note You must first generate a CSR using the CIMC certificate management CSR generation procedure, and you must use that CSR to obtain the certificate for uploading. Do not upload a certificate that was not obtained by this method.

Note All current HTTPS and SSH sessions are disconnected when the new server certificate is uploaded.

Procedure

Copy the certificate text, paste it into the console when prompted, and type CTRL+D to upload the certificate.

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

Managing Certificates

Uploading a Server Certificate

This example uploads a new certificate to the server:

Server# scope certificate

Server /certificate # upload

Please paste your certificate here, when finished, press CTRL+D.

-----BEGIN CERTIFICATE-----