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

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

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

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 xviii

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

Preface

Related Cisco UCS Documentation

Documentation Roadmaps

For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/overview/ guide/UCS_roadmap.html

For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/overview/ guide/ucs_rack_roadmap.html

For information on supported firmware versions and supported UCS Manager versions for the rack servers that are integrated with the UCS Manager for management, refer to Release Bundle Contents for Cisco UCS

Software .

Other Documentation Resources

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

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

xix

Related Cisco UCS Documentation

Preface xx

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

C H A P T E R

Overview

This chapter includes the following sections:

•

Overview of the Cisco UCS C-Series Rack-Mount Servers, on page 1

•

Overview of the Server Software, on page 2

•

Server Ports, on page 2

•

Cisco Integrated Management Controller, on page 3

•

Cisco IMC CLI, on page 4

Overview of the Cisco UCS C-Series Rack-Mount Servers

The Cisco UCS C-Series rack-mount servers include the following models:

• Cisco UCS C220 M6 Rack-Mount Server

• Cisco UCS C240 M6 Rack-Mount Server

• Cisco UCS C225 M6 Rack-Mount Server

• Cisco UCS C245 M6 Rack-Mount Server

• Cisco UCS C240 SD M5 Rack-Mount Server

• Cisco UCS C125 Rack-Mount Server

• Cisco UCS C220 M5 Rack-Mount Server

• Cisco UCS C240 M5 Rack-Mount Server

• Cisco UCS C480 M5 Rack-Mount Server

• Cisco UCS C220 M4 Rack-Mount Server

• Cisco UCS C240 M4 Rack-Mount Server

• Cisco UCS C460 M4 Rack-Mount Server

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

Overview

Overview of the Server Software

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 the Cisco IMC firmware.

Cisco IMC Firmware

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

Server OS

The Cisco UCS C-Series rack servers support operating systems such as Windows, Linux, Oracle and so on.

For more information on supported operating systems, see the Hardware and Software Interoperability for

Standalone C-series servers at http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_ list.html

. You can use Cisco IMC to install an OS on the server using the KVM console and vMedia.

Server Ports

Following is a list of server ports and their default port numbers:

Table 1: Server Ports

Port Name

LDAP Port 1

LDAP Port 2

LDAP Port 3

LDAP Port 4

LDAP Port 5

LDAP Port 6

SSH Port

HTTP Port

HTTPS Port

SMTP Port

3268

443

Port Number

389

3268

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

Overview

Cisco Integrated Management Controller

Port Name

KVM Port

Andromeda Management Port

Andromeda Cloud Port

SOL SSH Port

SNMP Port

SNMP Traps

External Syslog

Port Number

2068

8889

8888

2400

161

162

514

Cisco Integrated Management Controller

The Cisco IMC is the management service for the C-Series servers. Cisco IMC runs within the server.

Note The Cisco IMC 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 or an XML-based API 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 Cisco IMC GUI to invoke Cisco IMC CLI

• View a command that has been invoked through Cisco IMC CLI in Cisco IMC GUI

• Generate Cisco IMC CLI output from Cisco IMC GUI

Tasks You Can Perform in Cisco IMC

You can use Cisco IMC to perform the following server management tasks:

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

• Toggle the locator LED

• Configuring BIOS settings

• 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 4.2

Overview

Cisco IMC 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, IPMI Over LAN, and SNMP.

• Manage certificates

• Configure platform event filters

• Update Cisco IMC firmware

• Monitor faults, alarms, and server status

• Set time zone and view local time

• Install and activate Cisco IMC firmware

• Install and activate BIOS firmware

No Operating System or Application Provisioning or Management

Cisco IMC 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-Cisco IMC user accounts

• Configure or manage external storage on the SAN or NAS storage

Cisco IMC CLI

The Cisco IMC CLI is a command-line management interface for Cisco UCS C-Series servers. You can launch the Cisco IMC 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.

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

Overview

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.

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.

Command Mode Table

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

Mode Name

EXEC bios advanced

Command to Access top command from any mode

Mode Prompt

# scope bios command from EXEC mode

/bios # scope advanced command from bios mode

/bios/advanced # main server-management boot-device certificate chassis adapter scope main command from bios mode scope server-management command from bios mode

/bios/main #

/bios/server-management # scope boot-device command from bios mode

/bios/boot-device # scope certificate command from

EXEC mode

/certificate #

/chassis # scope chassis command from

EXEC mode

scope adapter index command from chassis mode

/chassis/adapter #

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

Overview

Command Mode Table

Mode Name host-eth-if host-fc-if port-profiles dimm-summary flexflash operational-profiles storageadapter cimc physical-drive virtual-drive firmware import-export log server network ipblocking tech-support fault

Command to Access scope host-eth-if command from adapter mode

Mode Prompt

/chassis/adapter/host-eth-if # scope host-fc-if command from adapter mode

/chassis/adapter/host-fc-if # scope port-profiles command from adapter mode

/chassis/adapter/port-profiles #

/chassis/dimm-summary # scope dimm-summary index command from chassis mode

scope flexflash index command from chassis mode

/chassis/flexflash # scope operational-profile command from flexflash mode

scope storageadapter slot command from chassis mode

/chassis/flexflash/operational-profile

/chassis/storageadapter # scope physical-drive command from storageadapter mode

/chassis/storageadapter/physical-drive

# scope virtual-drive command from storageadapter mode

/chassis/storageadapter/virtual-drive

# scope cimc command from EXEC mode

/cimc #

/cimc/firmware # scope firmware command from cimc mode scope import-export command from cimc mode

/cimc/import-export # scope log command from cimc mode

/cimc/log #

scope server index command from log mode

/cimc/log/server # scope network command from cimc mode

/cimc/network # scope ipblocking command from network mode

/cimc/network/ipblocking # scope tech-support command from cimc mode

/cimc/tech-support # scope fault command from EXEC mode

/fault #

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

Overview

Command Mode Table

Mode Name pef http ipmi kvm ldap role-group power-cap sel sensor snmp trap-destinations v3users sol ssh user user-session vmedia xmlapi

Command to Access scope pef command from fault mode

Mode Prompt

/fault/pef # scope http command from EXEC mode

/http # scope ipmi command from EXEC mode

/ipmi # scope kvm command from EXEC mode

/kvm # scope ldap command from EXEC mode

/ldap # scope role-group command from ldap mode

/ldap/role-group # scope power-cap command from

EXEC mode

/power-cap #

/sel # scope sel command from EXEC mode scope sensor command from

EXEC mode

/sensor # scope snmp command from EXEC mode

/snmp # scope trap-destinations command from snmp mode

/snmp/trap-destinations #

/snmp/v3users # scope v3users command from snmp mode scope sol command from EXEC mode

/sol # scope ssh command from EXEC mode

/ssh #

scope user user-number command from EXEC mode

/user #

scope user-session session-number command from EXEC mode

/user-session #

/vmedia # scope vmedia command from

EXEC mode scope xmlapi command from

EXEC mode

/xmlapi #

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

Overview

Complete a Command

Mode Name dimm-blacklisting reset-ecc

Command to Access scope dimm-blacklisting command from EXEC mode scope reset-ecc command from

EXEC mode

Mode Prompt

/dimm-blacklisting #

/ reset-ecc #

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.

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

Overview

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

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

--name: HDD_01_STATUS hdd-status: present

--name: HDD_02_STATUS hdd-status: present

--name: HDD_03_STATUS hdd-status: present

--name: HDD_04_STATUS hdd-status: present

...

Server /chassis #

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

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

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

Overview

Smart Access: Serial

The Smart Access: Serial allows offline configuration of C-series servers using the command line interface

(CLI) through serial connection. With this setup, you are not required to connect the Cisco IMC to the network in order to access the command line interface.

The serial connection can be accessed using either the KVM dongle (DB9), or the serial port (RJ-45) at the rear of the chassis.

Once you have completed the setup and the BIOS and OS messages are visible on the console, you can view the Cisco IMC CLI by pressing Esc+9 . You are required to authenticate the connection with Cisco IMC user credentials. The default user name is admin and default password is password . You can press Esc+8 to switch back to the BIOS or OS on the same console.

When the session is created, the session is visible on the Web UI sessions tab as a serial connection.

Note Note the following limitations while using the CLI through a serial connection:

• You cannot use the arrow keys to revert to previously executed commands.

• The CLI is not visible when the terminal type is set to either VT100+ or VTUFT8 .

• The smart access feature does not work as expected after an OS boot unless the " console

" property in the grub configuration file of the OS is set to ttyS0 . You must set the " console

" property in the grub configuration file of the OS to ttyS0 for it to work as expected.

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.

Logging In to Cisco IMC

Procedure

Step 1

Step 2

Connect to the console port.

When logging in to an unconfigured system for the first time, use admin as the username and password as the password.

The following situations occur when you login to the CLI for the first time:

• You cannot perform any operation until you change default admin credentials on the Cisco IMC web UI or CLI.

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

Overview

Logging In to Cisco IMC

Note After an upgrade from Cisco IMC version 1.5(x) or 2.0(1) to the latest version, or when you do a factory reset, during first login Cisco IMC prompts for a password change. You cannot choose the word 'password' as your new password. If this creates problems for any scripts you may be running, you could change it to password by logging back into the user management options, but this is

ENTIRELY at your own risk. It is not recommended by Cisco.

Example

The following example shows how to login in to Cisco IMC first time:

Login as # admin admin10.101.255.255's password # password

***********************WARNING*******************

Default credentials were used for login.

Administration passwords needs to be changed for security purpose.

********************************************************************

Enter current password # abcxyz

Re-enter new password # abcxyz

Updating password...

Password updated successfully.

Server #

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

Logging In to Cisco IMC

Overview

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

C H A P T E R

Installing the Server OS

This chapter includes the following sections:

•

OS Installation Methods, on page 13

•

Virtual KVM Console, on page 13

•

PXE Installation Servers, on page 14

•

Booting an Operating System from a USB Port, on page 15

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

For more information on Cisco UCS Server Configuration Utility, see Cisco UCS Server Configuration Utility

Quick Start Guide .

Virtual KVM Console

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

Here are a few major advantages of using Cisco KVM Console:

• The Cisco KVM console provides connection to KVM, SOL, and vMedia whereas the Avocent KVM provides connection only to KVM and vMedia.

• In the KVM Console, the vMedia connection is established at the KVM Launch Manager and is available for all users.

• The KVM console offers you an advanced character replacement options for the unsupported characters while pasting text from the guest to the host.

• The KVM console provides you an ability to store the vMedia mappings on CIMC.

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

Installing the Server OS

Installing an OS Using the KVM Console

Instead of using CD/DVD or floppy drives physically connected to the server, the vKVM console uses virtual media, which are actual disk drives or disk image files that are mapped to virtual CD/DVD or floppy drives.

You can map any of the following to a virtual drive:

• CD/DVD or floppy drive on your computer

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

• USB flash drive on your computer

• CD/DVD or floppy drive on the network

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

• USB flash drive on the network

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

Note The vKVM Console is operated only through the GUI. To launch the vKVM Console, see the instructions in the Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide .

Installing an OS Using the KVM Console

Because the KVM console is operated only through the GUI, you cannot install a server OS using the CLI.

To install an OS using the KVM console, follow the instructions in the "Installing an OS Using the KVM

Console" section of the Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration

Guide .

Note Detailed guides for installing Linux, VMware, and Windows can be found at this URL: http://www.cisco.com/ en/US/products/ps10493/products_installation_and_configuration_guides_list.html

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.

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

Installing the Server OS

Installing an OS Using a PXE Installation Server

Before you begin

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

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

Procedure

Step 1

Step 2

Set the boot order to PXE first.

Reboot the server.

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

What to do next

After the OS installation is complete, reset the LAN boot order to its original setting. Always follow your OS vendors recommended configuration, including software interoperability and driver compatibility. For more information on driver recommendations and installation, follow the Cisco UCS Hardware Compatibility list here: https://ucshcltool.cloudapps.cisco.com/public/

Booting an Operating System from a USB Port

All Cisco UCS C-series servers support booting an operating system from any USB port on the server. However, there are a few guidelines that you must keep in mind, prior to booting an OS from a USB port.

• To maintain the boot order configuration, it is recommended that you use an internal USB port for booting an OS.

• The USB port must be enabled prior to booting an OS from it.

By default, the USB ports are enabled. If you have disabled a USB port, you must enable it prior to booting an OS from it. For information on enabling a disabled USB ports, see topic Enabling or Disabling the Internal USB Port in the server-specific installation and service guide available at the following link: http://www.cisco.com/en/US/products/ps10493/prod_installation_guides_list.html

• After you boot the OS from the USB port, you must set the second-level boot order so that the server boots from that USB source every time.

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

Booting an Operating System from a USB Port

Installing the Server OS

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

C H A P T E R

Managing the Server

This chapter includes the following sections:

•

Toggling the Locator LED, on page 17

•

Toggling the Front Locator LED for the Chassis, on page 18

•

Toggling the Locator LED for a Hard Drive, on page 18

•

Selecting a Time Zone, on page 19

•

Managing the Server Boot Order, on page 22

•

Resetting the Server, on page 36

•

Shutting Down the Server, on page 36

•

Managing Server Power, on page 37

•

Configuring Power Policies, on page 39

•

Configuring Fan Policies, on page 50

•

Configuring DIMM Black Listing, on page 53

•

Configuring BIOS Settings, on page 54

•

Updating Firmware on Server Components, on page 59

•

Viewing Product ID (PID) Catalog Details, on page 60

•

Uploading and Activating a PID Catalog, on page 61

•

Deleting a PID Catalog, on page 63

•

Persistent Memory Module, on page 64

Toggling the Locator LED

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server # scope chassis

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

Purpose

Enters chassis command mode.

Enables or disables the chassis locator LED.

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

Managing the Server

Toggling the Front Locator LED for the Chassis

Step 3

Command or Action

Server /chassis # commit

Purpose

Commits the transaction to the system configuration.

Example

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 Front Locator LED for the Chassis

This option is available only on some UCS C-Series servers.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server # scope chassis

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

Server /chassis # commit

Purpose

Enters chassis command mode.

Enables or disables the chassis locator LED.

Commits the transaction to the system configuration.

Example

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

Server# scope chassis

Server /chassis # set front-locator-led off

Server /chassis *# commit

Server /chassis #

Toggling the Locator LED for a Hard Drive

This action is available only on some UCS C-Series servers.

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

Managing the Server

Selecting a Time Zone

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server # scope chassis

Purpose

Enters chassis command mode.

Server/chassis # scope hdd Enters hard disk drive (HDD) command mode.

Server /chassis/hdd # locateHDD drivenum { 1

| 2 }

Where drivenum is the number of the hard drive whose locator LED you want to set. A value of

1 turns the LED on while a value of 2 turns the

LED off.

Example

This example turns on the locator LED on HDD 2:

Server# scope chassis

Server /chassis # scope hdd

Server /chassis/hdd # locateHDD 2 1

HDD Locate LED Status changed to 1

Server /chassis/hdd # show

Name Status LocateLEDStatus

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

HDD1_STATUS

HDD2_STATUS present present

TurnOFF

TurnON

HDD3_STATUS

HDD4_STATUS absent absent

TurnOFF

Server /chassis/hdd #

Selecting a Time Zone

Selecting a time zone helps you choose a local time zone so that you can view the local time rather than the default machine time. Cisco IMC Web UI and the CLI provide you options to choose and set a time zone of your choice.

Setting the time zone to your local time will apply the time zone variable to all the services that utilize the system timing. This impacts the logging information and is utilized in the following applications of the Cisco

IMC:

• Fault summary and fault history logs

• Cisco IMC log

• rsyslog

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

Managing the Server

Selecting a Time Zone

When you set a local time, the timestamp on the applications that you can view are updated with the local time that you have chosen.

Selecting a Time Zone

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action

Server # scope CIMC

Server /CIMC # timezone-select

Purpose

Enters Cisco IMC command mode.

Displays a list of continents and oceans.

Enter the number corresponding to your continent or ocean.

A list of all the countries or regions of the chosen continent or ocean displays.

Enter the number corresponding to the country or region that you want to set as your time zone.

If a country or a region has more than one time zones, a list of time zones in that country or region displays.

Enter the number corresponding to time zone.

Is the above information OK?

message appears.

Enter 1 .

Continue?[y|N] : prompt appears.

Enter y if you want to set the chosen time zone.

The chosen time zone is set as the time zone for your Cisco IMC server.

Example

This example sets the time zone:

Server# scope CIMC

Server /CIMC # timezone-select

Please identify a location so that time zone rules can be set correctly.

Please select a continent or ocean.

1) Africa

2) Americas

3) Antarctica

4) Arctic Ocean

5) Asia

6) Atlantic Ocean

7) Australia

8) Europe

9) Indian Ocean

10) Pacific Ocean

#? 2

Please select a country whose clocks agree with yours.

1) Anguilla

2) Antigua & Barbuda

3) Argentina

4) Aruba

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

Managing the Server

Selecting a Time Zone

5) Bahamas

6) Barbados

7) Belize

8) Bolivia

9) Brazil

10) Canada

11) Caribbean Netherlands

12) Cayman Islands

13) Chile

14) Colombia

15) Costa Rica

16) Cuba

17) Curacao

18) Dominica

19) Dominican Republic

20) Ecuador

21) El Salvador

22) French Guiana

23) Greenland

24) Grenada

25) Guadeloupe

26) Guatemala

27) Guyana

28) Haiti

29) Honduras

30) Jamaica

31) Martinique

32) Mexico

33) Montserrat

34) Nicaragua

35) Panama

36) Paraguay

37) Peru

38) Puerto Rico

39) St Barthelemy

40) St Kitts & Nevis

41) St Lucia

42) St Maarten (Dutch part)

43) St Martin (French part)

44) St Pierre & Miquelon

45) St Vincent

46) Suriname

47) Trinidad & Tobago

48) Turks & Caicos Is

49) United States

50) Uruguay

51) Venezuela

52) Virgin Islands (UK)

53) Virgin Islands (US)

#? 49

Please select one of the following time zone regions.

1) Eastern Time

2) Eastern Time - Michigan - most locations

3) Eastern Time - Kentucky - Louisville area

4) Eastern Time - Kentucky - Wayne County

5) Eastern Time - Indiana - most locations

6) Eastern Time - Indiana - Daviess, Dubois, Knox & Martin Counties

7) Eastern Time - Indiana - Pulaski County

8) Eastern Time - Indiana - Crawford County

9) Eastern Time - Indiana - Pike County

10) Eastern Time - Indiana - Switzerland County

11) Central Time

12) Central Time - Indiana - Perry County

13) Central Time - Indiana - Starke County

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

Managing the Server

Managing the Server Boot Order

14) Central Time - Michigan - Dickinson, Gogebic, Iron & Menominee Counties

15) Central Time - North Dakota - Oliver County

16) Central Time - North Dakota - Morton County (except Mandan area)

17) Central Time - North Dakota - Mercer County

18) Mountain Time

19) Mountain Time - south Idaho & east Oregon

20) Mountain Standard Time - Arizona (except Navajo)

21) Pacific Time

22) Alaska Time

23) Alaska Time - Alaska panhandle

24) Alaska Time - southeast Alaska panhandle

25) Alaska Time - Alaska panhandle neck

26) Alaska Time - west Alaska

27) Aleutian Islands

28) Metlakatla Time - Annette Island

29) Hawaii

#? 8

The following information has been given:

United States

Eastern Time - Indiana - Crawford County

Is the above information OK?

1) Yes

2) No

#? 1

You have chosen to set timezone settings to:

America/Indiana/Marengo

Continue?[y|N]: y

Timezone has been updated.

The local time now is: Sun Jun 1 02:21:15 2014 EST

Server /CIMC #

Managing the Server Boot Order

Server Boot Order

Using Cisco IMC, you can configure the order in which the server attempts to boot from available boot device types. In the legacy boot order configuration, Cisco IMC allows you to reorder the device types but not the devices within the device types. With the precision boot order configuration, you can have a linear ordering of the devices. In the web UI or CLI you can change the boot order and boot mode, add multiple devices under each device types, rearrange the boot order, set parameters for each device type.

When you change the boot order configuration, Cisco IMC sends the configured boot order to BIOS the next time that server is rebooted. To implement the new boot order, reboot the server after you make the configuration change. The new boot order takes effect on any subsequent reboot. The configured boot order remains until the configuration is changed again in Cisco IMC or in the BIOS setup.

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

Managing the Server

Server Boot Order

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

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

• A user changes the boot order directly through BIOS.

• BIOS appends devices that are seen by the host but are not configured from the user.

Important While upgrading Cisco UCS C220 M5 or C480 M5 servers to release 4.1(1x) under the following conditions:

• if you are upgrading from any release earlier than 4.0(4x)

• if Legacy Boot Mode is enabled and no Cisco IMC Boot Order is configured

• and, if the server is booting from Cisco HWRAID adapter then, you should perform one of the following before upgrading:

• Run XML-API scripts and UCSCFG based scripts provided here.

• Manually configure the intended boot order through Cisco IMC GUI or CLI interfaces.

Note When you create a new policy using the configure boot order feature, BIOS tries to map this new policy to the devices in the system. It displays the actual device name and the policy name to which it is mapped in the

Actual Boot Order area. If BIOS cannot map any device to a particular policy in Cisco IMC, the actual device name is stated as NonPolicyTarget in the Actual Boot Order area.

Note During Cisco IMC 2.0(x) upgrade, the legacy boot order is migrated to the precision boot order. The previous boot order configuration is erased and all device types configured before updating to 2.0 version are converted to corresponding precision boot device types and some dummy devices are created for the same device types.

you can view these devices in the Configured Boot Order area in the web UI. To view these devices in the

CLI, enter show boot-device command. During this the server's actual boot order is retained and it can be viewed under actual boot order option in web UI and CLI.

When you downgrade Cisco IMC prior to 2.0(x) verison the server's last legacy boot order is retained, and the same can be viewed under Actual Boot Order area. For example:

• If you configured the server in a legacy boot order in 2.0(x) version, upon downgrade a legacy boot order configuration is retained.

• If you configured the server in a precision boot order in 2.0(x), upon downgrade the last configured legacy boot order is retained.

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

Managing the Server

Viewing the Boot Device Detail

Important • Boot order configuration prior to 2.0(x) is referred as legacy boot order. If your running version is 2.0(x), then you cannot configure legacy boot order through web UI, but you can configure through CLI and

XML API. In the CLI, you can configure it by using set boot-order HDD,PXE command. Even though, you can configure legacy boot order through CLI or XML API, in the web UI this configured boot order is not displayed.

• Legacy and precision boot order features are mutually exclusive. You can configure either legacy or precision boot order. If you configure legacy boot order, it disables all the precision boot devices configured. If you configure precision boot order, then it erases legacy boot order configuration.

Viewing the Boot Device Detail

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

Step 1

Step 2

Command or Action

Server# scope bios

Server /bios # show boot-device [ detail ].

Purpose

Enters the BIOS command mode.

Displays the detailed information of the boot device.

Example

This example displays the details of the created bootable device:

Server# scope bios

Server /bios # show boot-device

Boot Device Device Type Device State

TestPXE PXE Enabled

Server /bios # show boot-device detail

Device Order

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

TestUSB USB Enabled 1

Boot Device TestUSB:

Device Type: USB

Device State: Enabled

Device Order: 1

Sub Type: HDD

Boot Device TestPXE:

Device Type: PXE

Device State: Enabled

Device Order: 2

Slot Id: L

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

Managing the Server

Configuring the Precision Boot Order

Port Number: 1

Configuring the Precision Boot Order

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

Before you begin

Beginning with release 4.1(3b), Cisco IMC supports HTTP Boot Capability. HTTP Boot is supported in UEFI

Boot Mode only.

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

Procedure

Step 1

Step 2

Command or Action

Server# scope bios

Server /bios # create-boot-device [ device name ] [ device type ].

Purpose

Enters the BIOS command mode.

Creates a bootable device that BIOS chooses to boot. This can be one of the following:

• HDD —Hard disk drive

• PXE —PXE boot

• SAN boot

• iSCSI boot

• SD Card

Note SD card option is available only on some UCS C-Series servers.

• USB

• Virtual Media

• PCHStorage

• UEFISHELL

• HTTP

Step 3

Step 4

Server /bios # scope boot-device created boot device name .

Enters the management of the created bootable devices.

Server /bios /boot-device # set values Specifies the property values for particular bootable device. You can set one or more of the following:

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

Managing the Server

Configuring the Precision Boot Order

Step 5

Command or Action

Server /bios /boot-device # commit

Purpose

• cli— CLI options

• state— Whether the device will be visible by BIOS. By default the device is disabled.

Note If enabled, the device will overwrite the legacy boot order configuration.

• slot— Slot id where the device is plugged in.

• port— Port of the slot in which the device is present.

• LUN— Logical unit in a slot where the device is present.

• sub-type—Sub device type under a certain device type.

• order—The order of the device in the available list of devices.

• macaddress—MAC address of the network ethernet interface

• iptype— IP type.

Enter any one of the required values: IPv4 or IPv6

• ipconfig-type— Type of IP Configuration.

Enter any one of the required values:

DHCP or Static

• uri— URI path where all the OS iso and

EFI files are located.

Commits the transaction to the system configuration.

Example

This example configures the boot order, creates a boot device, set the attributes of the new device and commit the transaction:

Server# scope bios

Server /bios # create boot-device TestPXE PXE

Server /bios # scope boot-device TestPXE

Server /bios /boot-device # set state Enabled

Server /bios /boot-device # set slot L

Server /bios /boot-device # set port 1

Server /bios /boot-device # set order 1

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

Managing the Server

Configuring the Precision Boot Order

Server /bios /boot-device # commit

Enabling boot device will overwrite Legacy Boot Order configuration

Continue?[y|N]y

Server /bios /boot-device # y

Commiting device configuration

Server /bios/boot-device # show detail

BIOS:

BIOS Version: "C240M3.2.0.0.15 (Build Date: 03/16/2014)"

Boot Order: (none)

Boot Override Priority:

FW Update/Recovery Status: None, OK

UEFI Secure Boot: disabled

Configured Boot Mode: None

Actual Boot Mode: Legacy

Last Configured Boot Order Source: CIMC

Server /bios/boot-device # show boot-device detail

Boot Device TestPXE:

Device Type: PXE

Device State: Enabled

Device Order: 1

Slot Id: L

Port Number: 1

This example configures the boot order, creates a HTTP boot device for the IP type DHCP , sets the attributes of the new device and commits the transaction:

Server# scope server 1

Server /server # scope bios

Server /server/bios # create boot-device HTTP-Test HTTP

Server /server/bios # scope boot-device HTTP-Test

Server /server/bios/boot-device # set status enabled

Server /server/bios/boot-device # set port 10

Server /server/server/bios /boot-device # set order 1

Server /server/bios /boot-device # set slot MLOM

Server /server/bios/boot-device # set iptype IPv4

Server /server/bios/boot-device # set macaddress 00:25:B5:00:01:2b

Server /server/bios/boot-device # set ipconfig-type DHCP

Server /server/bios/boot-device # set uri http://www.cloudboot.com:80/EFI/rhel_82_dvd.iso

Server /bios /boot-device # commit

Commiting device configuration

Server /server/bios/boot-device # show detail

BBIOS:

BIOS Version: server-name.2.0.7c.0.071620151216

Backup BIOS Version: server-name.2.0.7c.0.071620151216

Boot Order: (none)

Boot Override Priority:

FW Update/Recovery Status: None, OK

UEFI Secure Boot: Enabled

Last Configured Boot Order Source: CIMC

Server /server/bios/boot-device # show boot-device detail

Boot Device HTTP-Test:

Device Type: HTTP-Test

Device State: Enabled

Device Order: 1

Slot Id: MLOM

Port Number: 10

MAC Address: 00:25:B5:00:01:2b

IP Type: IPv4

IP Config Type: DHCP

URI: http://www.cloudboot.com:80/EFI/rhel_82_dvd.iso

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

Managing the Server

Modifying the Attributes of a Boot Device

This example configures the boot order, creates a HTTP boot device for the IP type Static , sets the attributes of the new device and commits the transaction:

Server# scope server 1

Server /server # scope bios

Server /server/bios # create boot-device HTTP-Test HTTP

Server /server/bios # scope boot-device HTTP-Test

Server /server/bios/boot-device # set status enabled

Server /server/bios/boot-device # set port 10

Server /server/server/bios /boot-device # set order 1

Server /server/bios /boot-device # set slot MLOM

Server /server/bios/boot-device # set macaddress 00:25:B5:00:01:2b

Server /server/bios/boot-device # set ipconfig-type Static

Server /server/bios/boot-device # set iptype IPv6 C240-WZP21360Z1B /bios/boot-device *# set ipaddress 2001:420:5446:2014::330:12

Server /server/bios/boot-device *# set netmask_or_ipv6prefix 64

Server /server/bios/boot-device *# set gateway 2001:420:5446:2014::330:1

Server /server/bios/boot-device *# set dnsserver 2001:420:c0e0:1008::118

Server /server/bios/boot-device *# commit

Server /server/bios/boot-device *# set uri http://cisco.com/a.iso

Server /server/bios/boot-device *# commit

Server /server/bios/boot-device # show detail

Boot Device http_test:

Device Type: HTTP

Device State: Disabled

Device Order: 1

Slot Id: MLOM

Port Number: 10

MAC Address: aa:aa:aa:aa:aa:aa

IP Type: IPv6

IP Config Type: Static

URI: http://cisco.com/a.iso

IP Address: 2001:420:5446:2014::330:12

Netmask/IPV6 Prefix: 64

Gateway: 2001:420:5446:2014::330:1

DNS Server: 2001:420:c0e0:1008::118

Server /server/bios/boot-device #

What to do next

Reboot the server to boot with your new boot order.

Modifying the Attributes of a Boot Device

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

Step 1

Command or Action

Server# scope bios

Purpose

Enters the BIOS command mode.

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

Managing the Server

Modifying the Attributes of a Boot Device

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Command or Action Purpose

Server /bios # scope boot-device created boot device name .

Enters the management of the created bootable devices.

Server /bios /boot-device # set state

{ Enabled | Disabled }.

Enables or disables the device. The default state is disabled.

Note If enabled, the device will overwrite the legacy boot order configuration.

Server /bios /boot-device* # set order { Index

| 1-50 }.

Specifies the order of booting for particular device in the device list. Enter a number between 1 and 50 based on the total number of created device.

Note When you set the boot device order individually, it is not assured that the order appears in the way it was set. So, it is recommended that to set the order for multiple devices in a single execution, use re-arrange-boot-device command.

Server /bios /boot-device* # set port { value |

1-255 }.

Specifies the port of the slot in which the device is present. Enter a number between 1 and 255.

Server /server/bios /boot-device* # set iptype

{ value | IPv4 | IPv6 }.

Specifies the IP type for the device.

Server /server/bios /boot-device* # set macaddress { value }.

Sets the MAC address of the network ethernet interface.

Server /server/bios /boot-device* # set ipconfig-type { value | DHCP | Static }.

Server /server/bios /boot-device* # set uri

{ value }.

Specifies the IP configuration type for the device.

Specifies the URI path where all the OS iso and EFI files are located.

Server /bios /boot-device* # commit Commits the transaction to the system configuration.

Example

This example modifies the attributes of an existing device:

Server# scope bios

Server /bios *# scope boot-device scu-device-hdd

Server /bios/boot-device # set status enabled

Server /bios/boot-device *# set order 2

Server /bios/boot-device *# set port 1

Server /bios/boot-device *# commit

Enabling boot device will overwrite boot order Level 1 configuration

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

Managing the Server

Rearranging Device Boot Order

Continue?[y|N] y

Server /bios/boot-device #

This example modifies the attributes of an existing HTTP boot device:

Server# scope server 1

Server /server # scope bios

Server /server/bios *# scope boot-device http-test

Server /server/bios/boot-device # show detail

Boot Device http-test:

Device Type: HTTP

Device State: Disabled

Device Order: 3

Slot Id: 1

Port Number: 10

MAC Address: 00:25:B5:00:01:2b

IP Type: IPv4

IP Config Type: DHCP

URI: http://www.cloudboot.com:80/EFI/rhel_82_dvd.iso

Server /server/bios/boot-device # set iptype IPv6

Server /server/bios/boot-device *# set slot 34

Server /server/server/bios /boot-device # set order 1

Server /server/bios/boot-device *# set macaddress 00:25:B5:00:01:2c

Server /server/bios/boot-device *# set uri http://www.cloudboot.com:80/dvd.iso

Server /server/bios/boot-device *# commit

Server /server/bios/boot-device # show detail

Boot Device http-test:

Device Type: HTTP

Device State: Disabled

Device Order: 3

Slot Id: 34

Port Number: 10

MAC Address: 00:25:B5:00:01:2c

IP Type: IPv6

IP Config Type: DHCP

URI: http://www.cloudboot.com:80/dvd.iso

Server /server/bios/boot-device #

Rearranging Device 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

Step 1

Command or Action

Server# scope bios

Purpose

Enters the BIOS command mode.

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

Managing the Server

Re-Applying the Boot Order Configuration

Step 2

Command or Action

Server /bios # rearrange boot-device [ device name ]:[ position ].

Purpose

Rearranges the selected boot devices in a single execution.

Example

This example rearranges the selected boot devices:

Server# scope bios

Server /bios # rearrange-boot-device TestPXE:1,TestUSB:2

Server /bios # show boot-device

Boot Device Device Type Device State Device Order

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

TestPXE PXE Disabled 1

TestUSB USB Disabled 2

Server /bios #

Re-Applying the Boot Order Configuration

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

Step 1

Step 2

Command or Action

Server# scope bios

Server /bios # re-apply .

Purpose

Enters the BIOS command mode.

Re-applies the boot order to BIOS, if the last configured boot order source is BIOS..

Example

This example re-applies the boot order to BIOS:

Server# scope bios

Server /bios # re-apply

Server /bios #

What to do next

Reboot the host after reapplying the boot order to BIOS.

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

Managing the Server

Deleting an Existing Boot Device

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

Step 1

Step 2

Command or Action

Server# scope bios

Purpose

Enters the BIOS command mode.

Server /bios # remove-boot-device device name Deletes the particular device from the boot order.

Example

This example deletes the selected device from the device list:

Server# scope bios

Server /bios # remove-boot-device scu-device-hdd

Server /bios #

Overview to UEFI Secure Boot

You can use Unified Extensible Firmware Interface (UEFI) secure boot to ensure that all the EFI drivers, EFI applications, option ROM or operating systems prior to loading and execution are signed and verified for authenticity and integrity, before you load and execute the operating system. You can enable this option using either web UI or CLI. When you enable UEFI secure boot mode, the boot mode is set to UEFI mode and you cannot modify the configured boot mode until the UEFI boot mode is disabled.

Note If you enable UEFI secure boot on a nonsupported OS, on the next reboot, you cannot boot from that particular

OS. If you try to boot from the previous OS, an error is reported and recorded the under system software event in the web UI. You must disable the UEFI secure boot option using Cisco IMC to boot from your previous

OS.

Important Also, if you use an unsupported adapter, an error log event in Cisco IMC SEL is recorded. The error messages is displayed that says:

System Software event: Post sensor, System Firmware error. EFI Load Image Security Violation. [0x5302] was asserted .

UEFI secure boot is supported on the following components:

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

Managing the Server

Components

Supported OS

Broadcom PCI adapters

Intel PCI adapters

QLogic PCI adapters

Fusion-io

LSI

Overview to UEFI Secure Boot

Types

• Windows Server 2019

• Windows Server 2016

• ESX 6.7

• ESX 6.5

• ESXi 7.0

• Linux

• 5709 dual and quad port adapters

• 57712 10GBASE-T adapter

• 57810 CNA

• 57712 SFP port

• i350 quad port adapter

• X520 adapter

• X540 adapter

• LOM

• 8362 dual port adapter

• 2672 dual port adapter

• LSI MegaRAID SAS 9240-8i

• LSI MegaRAID SAS 9220-8i

• LSI MegaRAID SAS 9265CV-8i

• LSI MegaRAID SAS 9285CV-8e

• LSI MegaRAID SAS 9266-8i

• LSI SAS2008-8i mezz

• LSI Nytro card

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

Managing the Server

Enabling UEFI Secure Boot Mode

Procedure

Step 1

Step 2

Command or Action

Server# scope bios

Server/ BIOS # set secure-boot enable | disable

Purpose

Enters the BIOS command mode.

Enables or disables UEFI secure boot.

Note If enabled, the boot mode is set to

UEFI secure boot mode. You cannot modify configure boot mode until

UEFI secure boot mode is disabled.

Note In case of RFD (Reset Factory

Default), you must re-enable UEFI

Secure Boot.

Example

This example enables UEFI secure boot mode and commits the transaction

Server# scope bios

Server /bios # set secure-boot enable

Setting Value : enable

Commit Pending.

Server /bios *# commit

UEFI Secure boot state changed successfully. Execute 'show detail' command to check the current status

Server /bios #

What to do next

Reboot the server to have your configuration boot mode settings take place.

Disabling UEFI Secure Boot

Procedure

Step 1

Step 2

Command or Action

Server# scope bios

Server/ BIOS # set secure-boot enable | disable

Purpose

Enters the BIOS command mode.

Enables or disables UEFI secure boot.

Example

This example disables UEFI secure boot mode and commits the transaction

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

Managing the Server

Viewing the Actual Server Boot Order

Server# scope bios

Server /bios # set secure-boot disable

Setting Value : enable

Commit Pending.

Server /bios *# commit

UEFI Secure boot state changed successfully. Execute 'show detail' command to check the current status

Server /bios #

What to do next

Reboot the server to have your configuration boot mode settings take place.

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 Cisco IMC.

Procedure

Step 1

Step 2

Command or Action

Server# scope bios

Purpose

Enters bios command mode.

Server /bios # show actual-boot-order [ detail ] Displays the boot order actually used by the

BIOS when the server last booted.

Example

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

Server# scope bios

Server /bios # show actual-boot-order

Boot Order Type Boot Device

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

1 CD/DVD CD-ROM

CD/DVD

Network Device (PXE)

Cisco Virtual CD/DVD 1.18

Cisco NIC 23:0.0

Network Device (PXE)

Internal EFI Shell

FDD

MBA v5.0.5

Slot 0100

Slot 0101

Slot 0200

MBA v5.0.5

Slot 0201

Cisco NIC 22:0.0

Internal EFI Shell

Cisco Virtual HDD 1.18

Cisco Virtual Floppy 1.18

Server /bios #

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

Server /bios # show actual-boot-order

Boot Order Boot Device Device Type Boot Policy

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

1 IBA GE Slot 0201 v1398 PXE TestPXE

IBA GE Slot 0200 v1398

IBA GE Slot 0202 v1398

PXE

NonPolicyTarget

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

Managing the Server

Resetting the Server

IBA GE Slot 0203 v1398

"UEFI: Built-in EFI Shell "

Server /bios #

Resetting the Server

PXE

EFI

NonPolicyTarget

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.

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # power hard-reset

Purpose

Enters chassis command mode.

After a prompt to confirm, resets the server.

Example

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

Step 1

Command or Action

Server# scope chassis

Purpose

Enters chassis mode.

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

Managing the Server

Managing Server Power

Step 2

Command or Action

Server /chassis # power shutdown

Example

The following example shuts down the server:

Server# scope chassis

Server /chassis # power shutdown

Managing Server Power

Powering On the Server

Purpose

Shuts down the server.

Note If the server was powered off other than through the Cisco IMC, the server will not become active immediately when powered on. In this case, the server will enter standby mode until the Cisco IMC 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

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # power on

At the prompt, enter y to confirm.

Purpose

Enters the chassis command mode.

Turns on the server.

Example

This example shows how to turn on the server:

Server# scope chassis

Server /chassis # power on

Warning: System is already powered ON, this action is ineffective.

Do you want to continue?[y|N] y

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

Managing the Server

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.

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # power off

Purpose

Enters chassis command mode.

Turns off the server.

Example

This example turns off the server:

Server# scope chassis

Server /chassis # power off

This operation will change the server's power state.

Continue?[y|N]y

Server /chassis # show

Power Serial Number Product Name UUID

----- ------------- ------------- -----------------------------------off Not Specified Not Specified 208F0100020F000000BEA80000DEAD00

Power Cycling the Server

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

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # power cycle

Purpose

Enters chassis command mode.

Power cycles the server.

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

Managing the Server

Configuring Power Policies

Example

This example power cycles the server:

Server# scope chassis

Server /chassis # power cycle

Configuring Power Policies

Power Capping

Important This section is valid only for some UCS C-Series servers.

Power capping determines how server power consumption is actively managed. When you enable power capping option, the system monitors power consumption and maintains the power below the allocated power limit. If the server cannot maintain the power limit or cannot bring the platform power back to the specified power limit within the correction time, power capping performs actions that you specify in the Action field under the Power Profile area.

Once power capping is enabled, you can configure multiple power profiles to either have standard or advanced power profiles with defined attributes. If you choose a standard power profile, you can set the power limit, correction time, corrective-action, suspend period, hard capping, and policy state (if enabled). If you choose an advanced power profile, in addition to the attributes of the standard power profile, you can also set the domain specific power limits, safe throttle level, and ambient temperature based power capping attributes.

Note The following changes are applicable for Cisco UCS C-Series release 2.0(13) and later:

• After upgrading to the 2.0(13) release, power characterization automatically runs during the first host power on. Subsequent characterization runs only if initiated as described in section Run Power

Characterization section.

• Also, when a server is power cycled and there is a change to the CPU or DIMM configurations, power characterization automatically runs on first host boot. For any other hardware change like PCIe adapters,

GPU or HDDs, power characterization does not run. The characterized power range is modified depending on the components present after the host power cycle.

The Run Power Characterization option in the Power Cap Configuration Tab of the Web UI power cycles the host and starts power characterization.

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

Managing the Server

Setting Power Redundancy Policy

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server # scope sensor

Purpose

Enters sensor command.

Server /sensor # scope psu-redundancy-policy Enters psu redundancy policy command.

Server /sensor/psu-redundancy-policy # set

psu-redundancy-policyvalue

Choose one of the following redundancy value that you want to set:

• non-redundant - N, the available PSU output capacity, equals the number of

PSUs installed, where PSU failure or grid failure is not supported.

• N+1 - N, the available PSU output capacity, equals the number of PSUs installed minus 1 (N-1), where the single

PSU failure is supported, but grid failure is not supported.

• grid - N, the available PSU output capacity, equals half the number of PSUs installed (N/2), where N PSU failure or grid failure is supported. This policy implies that the you have connected N number of PSUs to one feed and the other

N number of PSUs to another feed.

Step 4

Step 5

Server /sensor/psu-redundancy-policy*

# commit

(Optional) Server

/sensor/psu-redundancy-policy # show detail

Commits the transaction to the server.

Displays the power redundancy status.

Example

This example shows how to set power redundancy for the server:

Server / # scope sensor

Server /sensor # scope psu-redundancy-policy

Server /sensor/psu-redundancy-policy # set psu-redundancy-policy grid

Server /sensor/psu-redundancy-policy* # commit

Server /sensor/psu-redundancy-policy # show detail

PSU Redundancy Policy: grid

Server /sensor/psu-redundancy-policy #

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

Managing the Server

Enabling Power Characterization

This option is available only on some Cisco UCS C-Series servers.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope power-cap-config

Server /chassis # run-pow-char-at-boot

Server /chassis # commit

Purpose

Enters chassis command mode.

Enters power cap command mode.

Runs the power characterization at boot.

Commits the transaction to the system.

Example

This example shows how to automatically invoke power characterization during a host reboot:

Server# scope chassis

Server /chassis# scope power-cap-config

Server /chassis /power-cap-config # run-pow-char-at-boot

Server /chassis /power-cap-config* # commit

Server /chassis/power-cap-config #

Configuring the Power Cap Policy

This option is available only on some Cisco UCS C-Series servers.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope power-cap-config

Server /chassis /power-cap-config# set pow-cap-enable { yes | no }

Server /chassis /power-cap-config# commit

Purpose

Enters chassis command mode.

Enters power cap command mode.

Enables or disables the capping of power to the server.

Commits the transaction to the system configuration.

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

Managing the Server

Checking the Power Cap Range

Example

This example shows how to enable the power capping policy:

Server# scope chassis

Server /chassis# scope power-cap-config

Server /chassis /power-cap-config # set pow-cap-enable yes

Server /chassis /power-cap-config* # commit

Server /chassis/power-cap-config #

Checking the Power Cap Range

This option is available only on some Cisco UCS C-Series servers.

Before you begin

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

Procedure

Step 1

Command or Action

Chassis power-cap-config # show detail

Purpose

Dislpays details of the power cap range.

Platform Min (Allow-Throttle) - This is the lower power limit for the chassis when CPU throttling is enabled. To use this as the platform minimum, set the allow-throttle field to enabled in the standard or advanced power-profile scope.

Platform Min (Efficient) - This is the lower power limit for the chassis when the CPU throttling is disabled.

CPU Min (Allow-Throttle) - This is the lower power limit for the CPU domain when throttling is enabled. To use this as the CPU minimum, set the allow-throttle field to enabled in the standard or advanced power-profile scope.

CPU Min (Efficient) - This is the lower power limit for the CPU domain when throttling is disabled.

Example

Power Characterization Enabled: yes

Power Capping: yes

Power Characterization Status: Completed

Platform Min (Allow-Throttle)(W): 164

Platform Min (Efficient)(W): 286

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

Managing the Server

Configuring Standard Power Profile

Platform Max (W): 582

Memory Min (W): 2

Memory Max (W): 5

CPU Min (Allow-Throttle)(W): 64

CPU Min (Efficient)(W): 177

CPU Max (W): 330

Configuring Standard Power Profile

This option is available only on some Cisco UCS C-Series servers.

Before you begin

• Power capping must be enabled.

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

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action

Server# scope chassis

Server /chassis # scope power-cap-config

Server /chassis /power-cap-config# set pow-cap-enable { yes | no }

Server /chassis /power-cap-config# scope power-profile standard

Server /chassis /power-cap-config# set allow-throttle yes | no

Server /chassis /power-cap-config#

corr-time value

Server /chassis /power-cap-config# except-action alert | shutdown set set

Purpose

Enters chassis command mode.

Enters power cap command mode.

Enables or disables the power capping capability of the system.

Enters the standard command mode of a power profile

Enables or disables the system to maintain the power limit by forcing the processor to use the throttling state (T-state) and memory throttle.

Sets the correction time in which the platform power should be brought back to the specified power limit before taking the action specified in the Action mode.

The range is from 3 and 600 seconds. The default is 3 seconds.

Specifies the action to be performed if the specified power limit is not maintained within the correction time. This can be one of the following:

• Alert —Logs the event to the Cisco IMC

SEL.

• Shutdown —Gracefully shuts down the host.

• None —No actions are taken.

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

Managing the Server

Configuring Advanced Power Profile Settings

Step 8

Step 9

Step 10

Step 11

Command or Action

Server /chassis /power-cap-config# set hard-cap yes | no

Server /chassis /power-cap-config#

pow-limit value set

Server /chassis /power-cap-config# set susp-pd { h:m-h:m |

|All,Mo,Tu,We,Th,Fr,Sa,Su.

}

Server /chassis /power-cap-config# commit

Purpose

Enables or disables the system to maintain the power consumption below the specified power limit.

Specifies the power limit.

Enter a value within the specified range.

Specifies the time period that the power capping profile is not active.

Commits the transaction to the system.

Example

This example shows how to configure standard power profile:

Server# scope chassis

Server /chassis# scope power-cap-config

Server /chassis /power-cap-config # set pow-cap-enable yes

Server /chassis /power-cap-config* # commit

Server /chassis/power-cap-config # scope power-profile advance

Server /chassis/power-cap-config # set allow-throttle yes

Server /chassis/power-cap-config* # set corr-time 6

Server /chassis/power-cap-config* # set except-action alert

Server /chassis/power-cap-config* # set hard-cap yes

Server /chassis/power-cap-config* # set pow-limit 360

Server /chassis/power-cap-config* # set susp-pd 1:30-2:30|All

Server /chassis/power-cap-config* # commit

Server /chassis/power-cap-config # show detail

Power Cap Config:

Power Characterization Enabled: yes

Power Capping: no

Power Characterization Status: Completed

Platform Min (Allow-Throttle)(W): 164

Platform Min (Efficient)(W): 290

Platform Max (W): 581

Memory Min (W): 2

Memory Max (W): 5

CPU Min (Allow-Throttle)(W): 64

CPU Min (Efficient)(W): 177

CPU Max (W): 330

Configuring Advanced Power Profile Settings

You can configure these settings only on some UCS C-Series servers.

Before you begin

• You must enable power capping.

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

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

Managing the Server

Configuring Advanced Power Profile Settings

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Command or Action

Server # scope chassis

Server /chassis # scope power-cap-config

Server /chassis /power-cap-config # set pow-cap-enable { yes | no }

Purpose

Enters chassis command mode.

Enters power cap command mode.

Enables or disables the power capping capability of the server.

Server /chassis /power-cap-config # commit Commits the transaction to the system.

Server /chassis /power-cap-config # power-profile advanced

Server /chassis

corr-time value scope

/power-cap-config/power-profile # set allow-throttle { yes | no }

/power-cap-config/power-profile # set

Enters the advance command mode of a power profile.

Enables or disables the system to maintain the power limit by forcing the processor to use the throttling state (T-state) and memory throttle.

Sets the maximum time to take corrective actions in order to bring the platform back to the specified power limit before taking the actions specified in the Action mode.

The range is from 3 and 600 seconds. The default is 3 seconds.

Server /chassis

/power-cap-config/power-profile # set

cpu-power-limit value

Server /chassis

/power-cap-config/power-profile # except-action { alert | shutdown } set

Specifies the power limit for the CPU.

Enter power in watts within the range specified.

Specifies the action to be performed if the specified power limit is not maintained within the correction time. This can be one of the following:

• Alert —Reports the event to the Cisco

IMC SEL.

• Shutdown —Gracefully shuts down the host.

• None —No actions are taken.

Server /chassis

/power-cap-config/power-profile # set hard-cap { yes | no }

Server /chassis

/power-cap-config/power-profile # set

mem-pow-limit value

Enables or disables the system to maintain the power consumption below the specified power limit.

Specifies the power limit for the memory.

Enter power in watts within the range specified.

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

Managing the Server

Configuring Advanced Power Profile Settings

Step 12

Step 13

Step 14

Step 15

Step 16

Step 17

Step 18

Command or Action

Server /chassis

/power-cap-config/power-profile # set

fail-safe-timeout value

Purpose

Specifies a safe throttle policy when the power capping functionality is impacted internal faults such as missing power readings for platforms or CPUs.

The range is from 1 and 10 seconds.

Server /chassis

/power-cap-config/power-profile #

plat-safe-Tlvl value set

Server /chassis

/power-cap-config/power-profile # set

plat-temp value

Server /chassis

/power-cap-config/power-profile #

pow-limit value set

Specifies the throttling level for the platform in percentage.

The range is from 0 and 100.

Specifies the inlet temperature sensor.

Enter value in Celsius.

Specifies the power limit.

Enter power in watts within the range specified.

Server /chassis

/power-cap-config/power-profile # set susp-pd

{ h:m-h:m | |All,Mo,Tu,We,Th,Fr,Sa,Su.

}

Specifies the time period that the power capping profile will not be active.

Server

/chassis/power-cap-config/power-profile # set

thermal-power-limit value

Specifies the power limit to be maintained.

Enter power in watts within the range specified.

Server /power-cap-config/power-profile # commit

Commits the transaction to the system configuration.

Example

This example shows how to configure the advance power profile setting:

Server# scope chassis

Server /chassis# scope power-cap-config

Server /chassis /power-cap-config # set pow-cap-enable yes

Server /chassis /power-cap-config* # commit

Server /chassis/power-cap-config # scope power-profile advanced

Server /chassis/power-cap-config/power-profile # set allow-throttle yes

Server /chassis/power-cap-config/power-profile* # set corr-time 6

Server /chassis/power-cap-config/power-profile*# set cpu-power-limit 259

Server /chassis/power-cap-config/power-profile* # set except-action alert

Server /chassis/power-cap-config/power-profile* # set hard-cap yes

Server /chassis/power-cap-config/power-profile* # set mem-pow-limit 259

Server /chassis/power-cap-config/power-profile* # set fail-safe-timeout 10

Server /chassis/power-cap-config/power-profile* # set plat-safe-Tlvl 50

Server /chassis/power-cap-config/power-profile* # set plat-temp 35

Server /chassis/power-cap-config/power-profile* # set pow-limit 360

Server /chassis/power-cap-config/power-profile* # set susp-pd 1:30-2:30|All

Server /chassis/power-cap-config/power-profile* # set thermal-power-limit 354

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

Managing the Server

Resetting the Power Profiles to Defaults

Server /chassis/power-cap-config/power-profile* # commit

Server /chassis/power-cap-config/power-profile #

Resetting the Power Profiles to Defaults

This option is available only on some Cisco UCS C-Series servers.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope power-cap-config

Server /chassis # reset-power-profile-to-defaults

Step 4 Server /chassis # commit

Purpose

Enters chassis command mode.

Enters power cap command mode.

Resets the power profile settings to factory-default values and disables power capping.

Commits the transaction to the system.

Example

This example shows how to reset the power profile to the default settings:

Server# scope chassis

Server /chassis# scope power-cap-config

Server /chassis /power-cap-config # reset-power-profile-to-defaults

Server /chassis /power-cap-config* # commit

Server /chassis/power-cap-config #

Viewing the Power Capping Configuration

This option is available only on some Cisco UCS C-Series servers.

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server # scope chassis

Server /chassis # scope power-cap-config

Purpose

Enters chassis command mode.

Enters power cap configuration command mode.

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

Managing the Server

Viewing the Power Statistics

Step 3

Command or Action Purpose

Server /chassis/power-cap-config # show detail Displays information about the power characterization.

Example

This example shows how to view information about the power cap configuration:

Server # scope chassis

Server/chassis # scope power-cap-config

Server /chassis/power-cap-config # show detail

Power Cap Config:

Power Characterization Enabled: yes

Power Capping: no

Power Characterization Status: Completed

Platform Min (Allow-Throttle)(W): 164

Platform Min (Efficient)(W): 290

Platform Max (W): 581

Memory Min (W): 2

Memory Max (W): 5

CPU Min (Allow-Throttle)(W): 64

CPU Min (Efficient)(W): 177

CPU Max (W): 330

Server /chassis/power-cap-config #

Viewing the Power Statistics

This option is available only on some UCS C-Series servers.

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server # scope chassis

Server /chassis # show power-monitoring

Purpose

Enters chassis command mode.

Displays the power used by the server, CPU, and memory since the last time it was rebooted.

Example

This example shows how to view the power statistics of an individual domain:

Server # scope chassis

Server /chassis # show power-monitoring

Domain Current (W) Minimum (W) Maximum (W) Average (W)

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

Platform 180 160 504 180

CPU 53 33 275 53

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

Managing the Server

Configuring the Power Restore Policy

Memory 2

Server /chassis #

2 6 2

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

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server # Scope CIMC

Purpose

Enters the Cisco IMC command mode.

Server /CIMC # Scope power-restore-policy Enters the power restore policy command mode.

Server /CIMC/power-restore-policy # set policy

{ power-off | power-on | restore-last-state }

Specifies the action to be taken when chassis power is restored. Select one of the following:

• power-off —Server power will remain off until manually turned on. This is the default action.

• power-on —Server power will be turned on when chassis power is restored.

• restore-last-state —Server power will return to the state before chassis power was lost.

When the selected action is power-on , you can select a delay in the restoration of power to the server.

(Optional) Server /CIMC/power-restore-policy

# set delay { fixed | random }

Specifies whether server power will be restored after a fixed or random time. The default is fixed . This command is accepted only if the power restore action is power-on .

(Optional) Server /CIMC/power-restore-policy

# set delay-value delay

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

Server /CIMC/power-restore-policy # commit Commits the transaction to the system configuration.

Example

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

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

Managing the Server

Configuring Fan Policies

Server# scope CIMC

Server /CIMC # Scope power-restore-policy

Server /CIMC/power-restore-policy # set policy power-on

Server /CIMC/power-restore-policy *# commit

Server /CIMC/power-restore-policy # set delay fixed

Server /CIMC/power-restore-policy *# set delay-value 180

Server /CIMC/power-restore-policy *# commit

Server /CIMC/power-restore-policy # show detail

Power Restore Policy:

Power Restore Policy: power-on

Power Delay Type: fixed

Power Delay Value(sec): 180

Server /CIMC/power-restore-policy #

Configuring Fan Policies

Fan Control Policies

Fan Control Policies enable you to control the fan speed to bring down server power consumption and noise levels. Prior to these fan policies, the fan speed increased automatically when the temperature of any server component exceeded the set threshold. To ensure that the fan speeds were low, the threshold temperatures of components are usually set to high values. While this behavior suited most server configurations, it did not address the following situations:

• Maximum CPU performance

For high performance, certain CPUs must be cooled substantially below the set threshold temperature.

This required very high fan speeds which resulted in higher power consumption and increased noise levels.

• Low power consumption

To ensure the lowest power consumption, fans must run very slowly, and in some cases, stop completely on servers that support it. But slow fan speeds resulted in servers overheating. To avoid this situation, it is necessary to run fans at a speed that is moderately faster than the lowest possible speed.

With the introduction of fan policies, you can determine the right fan speed for the server, based on the components in the server. In addition, it allows you to configure the fan speed to address problems related to maximum CPU performance and low power consumption.

Following are the fan policies that you can choose from:

• Balanced —This setting can cool almost any server configuration, but may not be suitable for servers with PCIe cards as these cards overheat easily.

• Low Power —This setting is ideal for minimal configuration servers that do not contain any PCIe cards.

• High Power —This policy is ideal for servers that contain PCIe cards that overheat easily and have high temperatures.

• Maximum Power —This setting can be used for server configurations that required extremely high fan speeds. This policy is ideal for servers that contain PCIe cards that overheat easily and have very high temperatures.

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

Managing the Server

Configuring a Fan Policy

• Acoustic —This setting can be used for configuring the fan noise level, thereby enabling noise reduction in the servers.

Application of this policy might result in performance throttling impacting system performance. If excessive thermal or performance events are recorded in the event logs, select a standard fan control policy like Low Power , which is a non-disruptive change.

Note This option is available only on Cisco UCS C220 M5, C240 SD M5, C240 M5,

C220 M6, C240 M6, C245 M6 and C225 M6 servers. For these servers, Acoustic is the default fan policy.

For other servers, default fan policy depends on the server configuration and the number of PCIe cards present in the server.

Note For Cisco UCS M5 servers, although you set a fan policy in Cisco IMC, the actual speed that the fan runs at is determined by the configuration requirements of the server. PCIe cards are tagged with minimum fan speed depending on thermal requirements. If the server is equipped with these PCIe cards, you cannot configure the fan policy, which go below the tagged requirement.

The Configuration Status displays the status of the configured fan policy in Cisco UCS M5 servers. This can be one of the following:

• SUCCESS —The selected fan policy matches the actual fan speed that runs on the server.

• PENDING —The configured fan policy is not in effect yet. This can be due to one of the following:

• The server is powered off

• The BIOS POST is not complete

• FAN POLICY OVERRIDE—Overrides the specified fan speed with the actual speed determined by the configuration requirements of the server.

Configuring a Fan Policy

The fan policy determines the cooling requirements for your server. Prior to setting the fan policy, you must determine if your server includes PCIe cards that overheat easily.

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # scope fan-policy

Purpose

Enters the chassis command mode.

Enters the fan policy command mode.

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

Managing the Server

Configuring a Fan Policy

Step 3

Command or Action

Server /chassis/fan-policy # set fan-policy

Purpose

Sets the fan policy for the server. It can be one of the following:

• Balanced —This setting can cool almost any server configuration, but may not be suitable for servers with PCIe cards as these cards overheat easily.

• Low Power —This setting is ideal for minimal configuration servers that do not contain any PCIe cards.

• High Power —This policy is ideal for servers that contain PCIe cards that overheat easily and have high temperatures.

• Acoustic —This setting can be used for configuring the fan noise level, thereby enabling noise reduction in the servers.

Note This option is available only on

Cisco UCS C220 M5, C240 SD

M5, C240 M5, C220 M6, C240

M6, C245 M6 and C225 M6 servers. For these servers,

Acoustic is the default fan policy.

For other servers, default fan policy depends on the server configuration and the number of PCIe cards present in the server.

Step 4 Server /chassis/fan-policy # set

aggressive-coolingno\yes

Use this option to enable aggressive cooling.

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

Managing the Server

Configuring DIMM Black Listing

Step 5

Command or Action

Server /chassis/fan-policy # commit

Purpose

Commits the changes to the server.

Example

This example shows how to set the fan policy to maximum power for a server: server # scope chassis server /chassis # scope fan-policy server /chassis/fan-policy # set fan-policy maximum-power server /chassis/fan-policy # set aggressive-cooling yes server /chassis/fan-policy* # commit server /chassis/fan-policy # show detail

Fan Policy: maximum-power

Applied Fan Policy: Max Power

Configuration Status: SUCCESS server /chassis/fan-policy #

Configuring DIMM Black Listing

DIMM Black Listing

In Cisco IMC, the state of the Dual In-line Memory Module (DIMM) is based on SEL event records. A DIMM is marked bad if the BIOS encounters a non-correctable memory error or correctable memory error with 16000 error counts during memory test execution during BIOS post. If a DIMM is marked bad, it is considered a non-functional device.

If you enable DIMM blacklisting, Cisco IMC monitors the memory test execution messages and blacklists any DIMM that encounters memory errors at any given point of time in the DIMM SPD data. This allows the host to map out those DIMMs.

DIMMs are mapped out or blacklisted only when Uncorrectable errors occur. When a DIMM gets blacklisted, other DIMMs in the same channel are ignored or disabled, which means that the DIMM is no longer considered bad.

Note DIMMs do not get mapped out or blacklisted for 16000 Correctable errors.

Enabling DIMM Black Listing

Before you begin

You must be logged in as an administrator.

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

Managing the Server

Configuring BIOS Settings

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope dimm-blacklisting /

Purpose

Enters the DIMM blacklisting mode.

Server /dimm-blacklisting # set enabled { yes

| no }

Enables or disables DIMM blacklisting.

Server /dimm-blacklisting* # commit Commits the transaction to the system configuration.

Example

The following example shows how to enable DIMM blacklisting:

Server# scope dimm-blacklisting

Server /dimm-blacklisting # set enabled yes

Server /dimm-blacklisting* # commit

Server /dimm-blacklisting #

Server /dimm-blacklisting # show detail

DIMM Blacklisting:

Enabled: yes

Configuring BIOS Settings

Viewing BIOS Status

Procedure

Step 1

Step 2

Command or Action

Server# scope bios

Server /bios # show detail

Purpose

Enters the BIOS command mode.

Displays details of the BIOS status.

The BIOS status information contains the following fields:

Name

BIOS Version

Description

The version string of the running BIOS.

Boot Order

Boot Override Priority

FW Update/Recovery Status

UEFI Secure Boot

The legacy boot order of bootable target types that the server will attempt to use.

This can be None, or HV.

The status of any pending firmware update or recovery action.

Enables or Disables UEFI secure boot.

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

Managing the Server

Configuring BIOS Settings

Name

Configured Boot Mode

Actual Boot Mode

Last Configured Boot Order Source

Description

The boot mode in which h BIOS will try to boot the devices.

The actual boot mode in which BIOS booted the devices.

The last configured boot order source by BIOS.

Configuring BIOS Settings

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope bios

Server /bios # scope input-output

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Configure the BIOS settings.

Server /bios/input-output #

Server /bios # exit scope memory

Configure the BIOS settings.

Server /bios/memory # commit commit

Purpose

Enters the BIOS command mode.

Enters the input and output settings command mode.

For descriptions and information about the options for each BIOS setting, see the following topic:

I/O Tab, on page 464

Commits the transaction to the system configuration.

Changes are applied on the next server reboot.

If server power is on, you are prompted to choose whether to reboot now.

Returns to the the BIOS command mode.

Enters the memory settings command mode.

For descriptions and information about the options for each BIOS setting, see the following topic:

Memory Tab, on page 484

Commits the transaction to the system configuration.

Changes are applied on the next server reboot.

If server power is on, you are prompted to choose whether to reboot now.

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

Managing the Server

Configuring BIOS Settings

Step 9

Step 10

Step 11

Step 12

Step 13

Step 14

Step 15

Step 16

Step 17

Step 18

Step 19

Step 20

Step 21

Command or Action

Server /bios/memory # exit

Purpose

Returns to the the BIOS command mode.

Server /bios # scope power-or-performance Enters the power or performance settings command mode.

Configure the BIOS settings.

For descriptions and information about the options for each BIOS setting, see the following topic:

Power/Performance Tab, on page 490

Server /bios/power-or-performance # commit Commits the transaction to the system configuration.

Changes are applied on the next server reboot.

If server power is on, you are prompted to choose whether to reboot now.

Server /bios/power-or-performance # exit

Server /bios # scope processor

Configure the BIOS settings.

Server /bios/processor # commit

Returns to the the BIOS command mode.

Enters the processor settings command mode.

For descriptions and information about the options for each BIOS setting, see the following topic:

Processor Tab, on page 476

Commits the transaction to the system configuration.

Changes are applied on the next server reboot.

If server power is on, you are prompted to choose whether to reboot now.

Server /bios/processor # exit

Server /bios # scope security

Configure the BIOS settings.

Server /bios/security #

Server /bios/security # commit exit

Returns to the the BIOS command mode.

Enters the security settings command mode.

For descriptions and information about the options for each BIOS setting, see the following topic:

Security Tab, on page 475

Commits the transaction to the system configuration.

Changes are applied on the next server reboot.

If server power is on, you are prompted to choose whether to reboot now.

Returns to the the BIOS command mode.

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

Managing the Server

Restoring BIOS Defaults

Step 22

Step 23

Step 24

Command or Action

Server /bios # scope server-management

Configure the BIOS settings.

Server /bios/server-management # commit

Purpose

Enters the server management settings command mode.

For descriptions and information about the options for each BIOS setting, see the following topic:

Server Management Tab, on page 471

Commits the transaction to the system configuration.

Changes are applied on the next server reboot.

If server power is on, you are prompted to choose whether to reboot now.

Example

This example configures the BIOS to enable the USB legacy support and commits the transaction:

Server# scope bios

Server /bios # scope input-output

Server /bios/input-output # set UsbLegacySupport enabled

Server /bios/input-output *# 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/input-output #

Restoring BIOS Defaults

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope bios

Server /bios # bios-setup-default

Purpose

Enters the BIOS command mode.

Restores BIOS default settings. This command initiates a reboot.

Example

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.

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

Managing the Server

Entering BIOS Setup

All your configuration will be lost.

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

Continue?[y|N] y

Entering BIOS Setup

Before you begin

• The server must be powered on.

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

Procedure

Step 1

Step 2

Command or Action

Server# scope bios

Server /bios # enter-bios-setup

Purpose

Enters the BIOS command mode.

Enters BIOS setup on reboot.

Example

This example enables you to enter BIOS setup:

Server# scope bios

Server /bios # enter-bios-setup

This operation will enable Enter BIOS Setup option.

Host must be rebooted for this option to be enabled.

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.

Procedure

Step 1

Command or Action

Server# scope bios

Purpose

Enters the BIOS command mode.

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

Managing the Server

Updating Firmware on Server Components

Step 2

Command or Action

Server /bios # restore-mfg-defaults

Purpose

Restores the set up tokens to the manufacturing default values.

Example

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 #

Updating Firmware on Server Components

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.

Server must be powered off.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope firmware

Server /chassis/firmware # show detail

Server /chassis/firmware # update-all

Purpose

Enters chassis command mode.

Enters firmware command mode.

Displays the firmware update required on some components message.

Updates the firmware on the server components.

Example

This example resets the server:

Server# scope chassis

Server /chassis # scope firmware

Server /chassis / firmware # show detail

Firmware update required on some components, please run update-all (under chassis/firmware scope).

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

Managing the Server

Viewing Product ID (PID) Catalog Details

Server /chassis / firmware # update-all

Viewing Product ID (PID) Catalog Details

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server # scope chassis

Server /chassis # show cpu-pid

Server /chassis # show dimm-pid

Server /chassis # show pciadapter-pid

Server /chassis # show hdd-pid

Purpose

Enters chassis command mode.

Displays the CPU PID details.

Displays the memory PID details.

Displays the PCI adapters PID details.

Displays the HDD PID details.

Example

This example shows how to create view PID details

Server # scope chassis

Viewing CPU PID details

Server /chassis # show cpu-pid

Socket Product ID Model

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

CPU1 UCS-CPU-E52660B Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.2...

CPU2 UCS-CPU-E52660B

Viewing memory PID details

Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.2...

Server /chassis # show dimm-pid

Name Product ID Vendor ID Capacity Speed

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

DIMM_A1

DIMM_A2

DIMM_B1

DIMM_B2

DIMM_C1

UNKNOWN

UCS-MR-1X162RZ-A

0xCE00

Failed

Ignore... NA

16384 MB

1866

DIMM_C2

DIMM_D1

DIMM_D2

DIMM_E1

DIMM_E2

UCS-MR-1X162RZ-A

DIMM_F1

DIMM_F2

DIMM_G1

UCS-MR-1X162RZ-A

DIMM_G2

DIMM_H1

UCS-MR-1X162RZ-A

DIMM_H2 UCS-MR-1X162RZ-A

Viewing PCI adapters PID details

Server /chassis # show pciadapter-pid

0xCE00

16384 MB

1866

16384 MB 1866

Slot Product ID Vendor ID Device ID SubVendor ID SubDevice ID

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

1 UCSC-MLOM-CSC-02

Viewing HDD PID details

0x1137 0x0042 0x1137 0x012e

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

Managing the Server

Uploading and Activating a PID Catalog

Server /chassis # show hdd-pid

Disk Controller Product ID Vendor Model

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

1 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400

SLOT-MEZZ UCS-C3X60-HD4TB

SLOT-MEZZ UCSC-C3X60-HD4TB

SEAGATE

TOSHIBA

ST4000NM0023

MG03SCA400

SLOT-MEZZ

UCSC-C3X60-HD4TB

TOSHIBA

MG03SCA400

9 SLOT-MEZZ UCSC-C3X60-HD4TB

10 SLOT-MEZZ UCSC-C3X60-HD4TB

11 SLOT-MEZZ UCSC-C3X60-HD4TB

12 SLOT-MEZZ UCSC-C3X60-HD4TB

13 SLOT-MEZZ UCSC-C3X60-HD4TB

14 SLOT-MEZZ UCSC-C3X60-HD4TB

15 SLOT-MEZZ UCS-C3X60-HD4TB

16 SLOT-MEZZ UCS-C3X60-HD4TB

19 SLOT-MEZZ UCSC-C3X60-HD4TB

28 SLOT-MEZZ UCSC-C3X60-HD4TB

54 SLOT-MEZZ UCSC-C3X60-HD6TB

55 SLOT-MEZZ UCSC-C3X60-HD6TB

56 SLOT-MEZZ UCSC-C3X60-HD4TB

57 SLOT-MEZZ UCS-HD4T7KS3-E

58 SLOT-MEZZ UCS-HD4T7KS3-E

59 SLOT-MEZZ UCS-HD4T7KS3-E

60 SLOT-MEZZ UCS-HD4T7KS3-E

TOSHIBA

SEAGATE

TOSHIBA

SEAGATE

TOSHIBA

MG03SCA400

ST4000NM0023

MG03SCA400

ST6000NM0014

MG03SCA400

WD4001FYY...

Server /chassis #

Uploading and Activating a PID Catalog

Caution BMC reboots automatically once a PID catalog is activated.

You must reboot the server after activating a PID catalog.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server# /chassis scope pid-catalog

Purpose

Enters the chassis command mode.

Enters the PID catalog command mode.

Server /chassis/pid-catalog #

upload-pid-catalog remote-protocol IP Address

PID Catalog file

Specifies the protocol to connect to the remote server. It can be one of the following types:

• TFTP

• FTP

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

Managing the Server

Uploading and Activating a PID Catalog

Step 4

Step 5

Step 6

Command or Action Purpose

• SFTP

• SCP

• HTTP

Note The Cisco UCS C-Series server now supports fingerprint confirmation of the server when you update firmware through a remote server. This option is available only if you choose SCP or SFTP as the remote server type.

If you chose SCP or SFTP as the remote server type while performing this action, a prompt with the message Server (RSA) key fingerprint is <server_finger_print

_ID> Do you wish to continue?

Click y or n depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

(Optional) Server# /chassis/pid-catalog show detail

Server# /chassis/pid-catalog activate

Displays the status of the upload.

Activates the uploaded PID catalog.

Server# /chassis/pid-catalog show detail Displays the status of the activation.

Example

This example uploads and activates the PID catalog:

Server # scope chassis

Server /chassis # scope pid-catalog

Uploading PID Catalog

Server /chassis/pid-catalog # upload-pid-catalog tftp 10.10.10.10 pid-ctlg-2_0_12_78_01.tar.gz

upload-pid-catalog initialized.

Please check the status using "show detail".

Server /chassis/pid-catalog #

Server /chassis/pid-catalog # show detail

Upload Status: Upload Successful

Activation Status: Please Activate Catalog

Current Activated Version: N/A

Activating the uploaded PID catalog

Server /chassis/pid-catalog # activate

Successfully activated PID catalog

Server /chassis/pid-catalog # show detail

Upload Status:

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

Managing the Server

Deleting a PID Catalog

Activation Status: Activation Successful

Current Activated Version: 2.0(12.78).01

Server /chassis/pid-catalog #

Deleting a PID Catalog

Caution BMC reboots automatically once a PID catalog is deleted.

You must reboot the server after deleting a PID catalog.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server# /chassis scopepid-catalog

Server /chassis/pid-catalog # delete

Purpose

Enters the chassis command mode.

Enters the PID catalog command mode.

Enter y at the confirmation prompt to delete the

PID catalog.

Note You can delete a PID catalog only if it has been previously updated and activated.

Step 4 (Optional) Server# /chassis/pid-catalog show detail

Displays the status of the PID catalog.

Example

This example uploads and activates the PID catalog:

Server # scope chassis

Server /chassis # scope pid-catalog

Server /chassis/pid-catalog # delete

CIMC will be automatically rebooted after successful deletion of the uploaded catalog file.

Once this is complete, a host reboot will be required for the catalog changes to be reflected in the BIOS and host Operating System Continue?[y|N] y

Server /chassis/pid-catalog # show detail

PID Catalog:

Upload Status: N/A

Activation Status: N/A

Current Activated Version: 4.1(0.41)

Server /chassis/pid-catalog #

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

Managing the Server

Persistent Memory Module

Persistent Memory Modules

Cisco UCS C-Series Release 4.0(4) introduces support for the Intel

Optane

™

Data Center persistent memory modules on the UCS M5 servers that are based on the Second Generation Intel

Xeon

These persistent memory modules can be used only with the Second Generation Intel

Scalable processors.

Xeon Scalable processors.

Persistent memory modules are non-volatile memory modules that bring together the low latency of memory and the persistence of storage. Data stored in persistent memory modules can be accessed quickly compared to other storage devices, and is retained across power cycles.

For detailed information about configuring persistent memory modules, see the Cisco UCS: Configuring and

Managing Intel ® Optane ™ Data Center Persistent Memory Modules Guide.

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

Viewing Server Properties

C H A P T E R

This chapter includes the following sections:

•

Viewing Server Properties, on page 65

•

Viewing System Information, on page 66

•

Viewing a Server Utilization, on page 66

•

Viewing Cisco IMC Properties, on page 67

•

Viewing CPU Properties, on page 68

•

Viewing Memory Properties, on page 68

•

Viewing Power Supply Properties, on page 70

•

Viewing Storage Properties, on page 70

•

Viewing PCI Adapter Properties, on page 76

•

Viewing Network Related Properties, on page 77

•

Viewing TPM Properties, on page 78

•

Enabling Dual Enclosure in Storage Controllers, on page 78

Viewing Server Properties

Procedure

Step 1

Command or Action

Server# show chassis [ detail ]

Purpose

Displays server properties.

Example

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: This shows the chassis details.

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

Viewing Server Properties

Viewing System Information

Server#

This example displays server properties for C3160 servers:

Server# show chassis detail

Chassis:

Power: on

Serial Number: FCH1821JAVL

Product Name: UCS C3160

PID : UCSC-C3X60-SVRNB

UUID: 84312F76-75F0-4BD1-9167-28B74EBB444C

Locator LED: off

Front Panel Locator LED: off

Description: This shows the chassis details

Server#

Viewing System Information

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show sku-details

Purpose

Enters the chassis command mode.

Displays the system information.

Example

This example shows how to view system details:

Server# scope chassis

Server /chassis # show sku-details

SAS Expander: Not-Present

HDD: 10-SFF_drive_back_plane

Riser1: (1 Slot x16)

Riser2: (1 Slot x16)

M.2 SATA/NVMe: Not-Present

M.2 SD Card Controller: Not-Present

CPU1 PKG-ID: Non-MCP

CPU2 PKG-ID: Non-MCP

Intrusion Sensor: Not-Equipped

Server /chassis #

Viewing a Server Utilization

You can view a server utilization only on some UCS C-Series servers.

Procedure

Step 1

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

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

Viewing Server Properties

Viewing Cisco IMC Properties

Step 2

Command or Action

Server /chassis # show cups-utilization

Purpose

Displays the server utilization value on all the available CPUs.

Note These utilization values are reported as a percentage of the total hardware bandwidth. These values may not match with the values being displayed by the host based resource monitoring software.

Example

This example shows how to view the server utilization value:

Server# scope chassis

Server /chassis # show cups-utilization

CPU Utilization (%) Memory Utilization (%) I/O Utilization (%) Overall Utilization (%)

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

100 69 0 86

Server /chassis #

Viewing Cisco IMC Properties

Note Cisco IMC 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

Step 1

Command or Action

Server# show cimc [ detail ]

Purpose

Displays Cisco IMC properties.

Example

This example displays Cisco IMC properties:

Server# show cimc detail

Cisco IMC:

Firmware Version: 2.0(8.122)

Current Time: Wed Dec 9 23:14:28 2015

Boot-loader Version: 2.0(8.122).36

Local Time: Wed Dec 9 23:14:28 2015 UTC +0000

Timezone: UTC

Reset Reason: graceful-reboot (This provides the last Cisco IMC reboot reason.)

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

Viewing Server Properties

Viewing CPU Properties

Server#

Viewing CPU Properties

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show cpu [ detail ]

Purpose

Enters chassis command mode.

Displays CPU properties.

Example

This example displays CPU properties:

Server# scope chassis

Server /chassis # show cpu

Name Cores Version

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

CPU1

CPU2

Intel(R) Xeon(R) CPU

E5520

@ 2.27GHz

Server /chassis #

Viewing Memory Properties

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # show dimm [ detail ]

Server /chassis # show dimm-summary

Purpose

Enters chassis command mode.

Displays memory properties.

Displays DIMM summary information.

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

Viewing Server Properties

Viewing Memory Properties

Example

This example displays memory properties:

Server# scope chassis

Server /chassis # show dimm

Name Capacity Channel Speed (MHz) Channel Type

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

DIMM_A1

DIMM_A2

2048 MB

1067

Other

DIMM_B1

DIMM_B2

DIMM_C1

DIMM_C2

DIMM_D1

DIMM_D2

DIMM_E1

DIMM_E2

DIMM_F1

DIMM_F2

2048 MB

Not Installed Unknown

2048 MB

1067

Not Installed Unknown

Other

Server /chassis #

This example displays detailed information about memory properties:

Server# scope chassis

Server /chassis # show dimm detail

Name DIMM_A1:

Capacity: 2048 MB

Channel Speed (MHz): 1067

Channel Type: Other

Memory Type Detail: Synchronous

Bank Locator: NODE 0 CHANNEL 0 DIMM 0

Visibility: Yes

Operability: Operable

Manufacturer: 0x802C

Part Number: 18JSF25672PY-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

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 #

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

Viewing Server Properties

Viewing Power Supply Properties

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show psu [ detail ]

Purpose

Enters chassis command mode.

Displays power supply properties.

Example

This example displays power supply properties:

Server# scope chassis

Server /chassis # show psu

Name In. Power (Watts) Out. Power (Watts) Firmware Status

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

PSU1

PSU2

650

R0E

Present

Server /chassis #

Note Input Power and Maximum Output Power options are available only for some C-Series servers.

Viewing Storage Properties

Viewing Storage Adapter Properties

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # show storageadapter [ slot ]

[ detail ]

Displays installed storage cards.

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

Viewing Server Properties

Viewing Storage Adapter Properties

Step 8

Step 9

Step 10

Step 11

Step 12

Step 13

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action Purpose

Note This command displays all

MegaRAID controllers on the server that can be managed through

Cisco IMC. If an installed controller or storage device is not displayed, then it cannot be managed through

Cisco IMC.

Server /chassis # scope storageadapter slot Enters command mode for an installed storage card.

Server /chassis/storageadapter # show bbu

[ detail ]

Server /chassis/storageadapter # show capabilites [ detail ]

Server /chassis/storageadapter # show error-counters [ detail ]

Server /chassis/storageadapter # show firmware-versions [ detail ]

Displays battery backup unit information for the storage card.

Displays RAID levels supported by the storage card.

Displays number of errors seen by the storage card.

Displays firmware version information for the storage card.

Server /chassis/storageadapter # hw-config mfg-data [

[ detail detail ]

]

Server /chassis/storageadapter # show show

Displays hardware information for the storage card.

Displays manufacturer data for the storage card.

Server /chassis/storageadapter # show pci-info

[ detail ]

Displays adapter PCI information for the storage card.

Server /chassis/storageadapter # show running-firmware-images [ detail ]

Displays running firmware information for the storage card.

Server /chassis/storageadapter # show settings

[ detail ]

Displays adapter firmware settings for the storage card.

Server /chassis/storageadapter # show startup-firmware-images [ detail ]

Displays firmware images to be activated on startup for the storage card.

Example

This example displays storage properties:

Server# scope chassis

Server /chassis # show storageadapter

PCI Slot Product Name Serial Number Firmware Package Build

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

SAS LSI MegaRAID SAS 9260-8i SV93404392 12.12.0-0038

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

Viewing Server Properties

Viewing the Flexible Flash Controller Properties

Product ID Battery Status Cache Memory Size

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

LSI Logic fully charged 0 MB

Server /chassis #

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

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # show bbu

Controller Battery Type Battery Present Voltage Current Charge Charging State

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

SAS iBBU true 4.051 V 0.000 A 100% fully charged

Server /chassis/storageadapter #

Viewing the Flexible Flash Controller Properties

Before you begin

• Cisco Flexible Flash must be supported by your platform.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Required: Server /chassis # show flexflash

[ detail ]

Required: Server /chassis # scope flexflash index

Server /chassis/flexflash # show operational-profile [ detail ]

Purpose

Enters the chassis command mode.

(Optional) Displays the available Cisco Flexible

Flash controllers.

Enters the Cisco Flexible Flash controller command mode for the specified controller. At this time, the only permissible index value is

FlexFlash-0 .

Displays the operational profile properties.

Example

This example displays the properties of the flash controller:

Server# scope chassis

Server /chassis # show flexflash

Controller Product Name Has Error Firmware Version Vendor Internal State

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

FlexFlash-0 Cisco FlexFlash No 1.2 build 247 Cypress Connected

Server /chassis # scope flexflash FlexFlash-0

Server /chassis # show operational-profile

Primary Member Slot I/O Error Threshold Host Accessible VDs

-------------------- -------------------- -------------------slot1 100 SCU Drivers

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

Viewing Server Properties

Viewing Physical Drive Properties

Server /chassis/flexflash #

Viewing Physical Drive Properties

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # show physical-drive [ drive-number ] [ detail ]

Server /chassis/storageadapter # show physical-drive-count [ detail ]

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Displays physical drive information for the storage card.

Displays the number of physical drives on the storage card.

Server /chassis/storageadapter # scope

physical-drive drive-number

Enters command mode for the specified physical drive.

Server /chassis/storageadapter/physical-drive

# show general [ detail ]

Displays general information about the specified physical drive.

Server /chassis/storageadapter/physical-drive

# show inquiry-data [ detail ]

Displays inquiry data about the specified physical drive.

Server /chassis/storageadapter/physical-drive

# show status [ detail ]

Displays status information about the specified physical drive.

Example

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

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

Viewing Server Properties

Viewing Virtual Drive Properties

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:

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

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # virtual-drive [ drive-number ] [ show detail ]

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Displays virtual drive information for the storage card.

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

Viewing Server Properties

Viewing Nvidia GPU Card Information

Step 4

Step 5

Step 6

Command or Action

Server /chassis/storageadapter # show virtual-drive-count [ detail ]

Server /chassis/storageadapter #

virtual-drive drive-number scope

Purpose

Displays the number of virtual drives configured on the storage card.

Enters command mode for the specified virtual drive.

Server /chassis/storageadapter/virtual-drive # show physical-drive [ detail ]

Displays physical drive information about the specified virtual drive.

Example

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

Virtual Drive Status Name

Size RAID Level

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

0 Optimal SLES1SP1beta5 30720 MB RAID 0

1 Optimal RHEL5.5

30720 MB RAID 0

Optimal

W2K8R2_DC

VD_3

30720 MB RAID 0

Optimal

ESX4.0u2

VMs

RHEL6-35GB

OS_Ins_Test_DR

30720 MB

285568 MB

35840 MB

158720 MB

285568 MB

RAID 0

RAID 1

Server /chassis/storageadapter #

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

Server# scope chassis

Server /chassis # scope storageadapter SAS

Server /chassis/storageadapter # scope virtual-drive 1

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

Span Physical Drive Status Starting Block Number Of Blocks

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

0 12 online 62914560 62914560

Server /chassis/storageadapter/virtual-drive #

Viewing Nvidia GPU Card Information

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

Before you begin

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

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

Viewing Server Properties

Viewing PCI Adapter Properties

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show gpu

Step 3 Server /chassis # scope gpu slot-number

Step 4 Server /chassis/gpu # show gpu-list

Purpose

Enters the chassis command mode.

Displays the available Nvidia GPU cards on the system.

Enters the GPU card command mode. Specify the slot number of the GPU card.

Displays temperature information on the GPU cards.

Example

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

Server # scope chassis

Server /chassis # show gpu

Slot

----

Product Name

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

Nvidia GRID K2 @ BD

Num of GPUs

-----------

Server /chassis # scope gpu 5

Server /chassis/gpu # show gpu-list

GPU ID

------

Temperature

-----------

Server /chassis/gpu #

Viewing PCI Adapter Properties

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show pci-adapter [ detail ]

Purpose

Enters the chassis command mode.

Displays PCI adapter properties.

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

Viewing Server Properties

Viewing Network Related Properties

Example

This example displays PCI adapter properties:

Server# scope chassis

Server /chassis # show pci-adapter

Slot Vendor ID Device ID SubVendor ID SubDevice ID Firmware Version Product Name

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

L 0x8086 0x1521 0x1137 0x008b 0x80000AA5... Intel(R) I350 1 Gbps N...

0x19a2

0x10de

0x14e4

0x0710

0x118f

0x1639

0x10df

0x10de

0x14e4

0xe702

0x097f

0x1639

4.6.142.10

N/A

Emulex OCe11102-FX 2 p...

Nvidia TESLA K10 P2055...

Broadcom 5709 1 Gbps 2...

0x10de

0x1000

0x0ff2

0x0073

0x10de

0x1137

0x1012

0x00b1

N/A

Nvidia GRID K1 P2401-502

Cisco UCSC RAID SAS 20…

Option ROM Status

----------

Loaded

Not-Loaded

Loaded

Server /chassis #

Note Option ROM Status is applicable only for legacy boot mode and not for UEFI boot mode.

Viewing Network Related Properties

Viewing LOM Properties

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope network-adapter slot

Enters the specific network adapter command mode.

Server /chassis/network-adapter # show mac-list [ detail ]

Displays the MAC addresses of the LOM ports.

Example

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

Server# scope chassis

Server /chassis # scope network-adapter L

Server /chassis/network-adapter # show mac-list

Interface ID MAC Address

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

Viewing Server Properties

Viewing TPM Properties

-------------------------------eth0 010000002000 eth1 010000002000

Server /chassis/network-adapter #

Viewing TPM Properties

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show tpm-inventory

Purpose

Enters the chassis command mode.

Displays the TPM properties.

Example

This example displays the TPM properties:

Server# scope chassis

Server /chassis # show tpm-inventory

Version Presence Enabled-Status Active-Status Ownership Revision Model

Vendor Serial

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

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

A equipped disabled

Inc FCHXXXXXXXX deactivated unowned 1 UCSX-TPMX-00X ABC

Server /chassis #

Enabling Dual Enclosure in Storage Controllers

This feature is supported only on the server nodes having UCS S3260 12G Dual Pass-Through Controller

(UCS-S3260-DHBA). Using this feature, you can select a SAS expander in the Dynamic Storage tab and enable dual enclosure support on the SAS expander, based on your requirements.

Before you begin

• Ensure that the server is powered off.

Procedure

Step 1 Server# scope chassis

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

Viewing Server Properties

Enabling Dual Enclosure in Storage Controllers

Step 2

Step 3

Step 4

Step 5

Enters the chassis command mode.

Server /chassis # dynamic-storage

Enters the dynamic storage command mode.

Server /chassis/dynamic-storage # show expander-hw-detail

Displays the list of SAS expander hardware details:

• Expander ID

• Hardware revision

• SAS Address

• Enclosure ID of the SAS Expander

Server /chassis/dynamic-storage # set-dual-enclosure

Enable dual enclosure support. And select yes to set different enclosure ID for each SAS expander.

Server /chassis/dynamic-storage # show expander-hw-detail

Displays the list of SAS expander hardware details. Note the enclosure IDs for each SAS expander after enabling dual enclosure support.

Example

This example sets dual enclosure support in the SAS expanders:

Server # scope chassis

Server /chassis # scope dynamic-storage

Server /chassis # show expander-hw-detail

Name Id ExpanderHwRev SasAddress EnclosureId

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

SASEXP1

Name

ExpanderHwRev

52cd02db305cba00

SasAddress

52cd02db305cb000

EnclosureId

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

SASEXP2 2 2 52cd02db305ccb00 52cd02db305cb000

Server /chassis/dynamic-storage # set-dual-enclosure

Do you want to set different enclosure id to SAS Expanders?

Enter 'yes' --> to set different enclosure id

Enter 'no' --> to set same enclosure id

Enter your option 'yes/no' to continue-->yes

This dual enclosure feature should be applied only when the server nodes has UCS-S3260-DHBA adaptor and single path is zoned for each drives.

make sure both server blades are powered off.

Do you want to continue? Enter 'yes' to continue-->yes set-dual-enclosure operation success

Server /chassis # show expander-hw-detail

Name Id ExpanderHwRev SasAddress EnclosureId

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

SASEXP1 1 2 52cd02db305cba00 52cd02db305cb000

Name Id ExpanderHwRev SasAddress EnclosureId

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

SASEXP2 2 2 52cd02db305ccb00 52cd02db305cb100

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

Enabling Dual Enclosure in Storage Controllers

Viewing Server Properties

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

C H A P T E R

Viewing Sensors

This chapter includes the following sections:

•

Viewing Power Supply Sensors, on page 81

•

Viewing Fan Sensors, on page 82

•

Viewing Temperature Sensors, on page 83

•

Viewing Voltage Sensors, on page 84

•

Viewing Current Sensors, on page 85

•

Viewing Storage Sensors, on page 85

•

Setting Dynamic Front Panel Temperature Threshold, on page 86

Viewing Power Supply Sensors

Procedure

Step 1

Step 2

Command or Action

Server# scope sensor

Server /sensor # show psu

Step 3 Server /sensor # show psu-redundancy

Purpose

Enters sensor command mode.

Displays power supply sensor statistics for the server.

Displays power supply redundancy sensor status for the server.

Example

This example displays power supply sensor statistics:

Server# scope sensor

Server /sensor # show psu

Name

Failure

Sensor Status

Normal

Reading

102

Units

Watts

Min. Warning Max. Warning

N/A 882

Min. Failure

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

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

N/A

Max.

SU1_PIN

1098

PSU2_PIN Normal 96 Watts N/A 882 N/A

1098

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

Viewing Sensors

Viewing Fan Sensors

PSU3_PIN

1098

PSU4_PIN

1098

PSU1_POUT

996

PSU2_POUT

996

PSU3_POUT

996

PSU4_POUT

996

POWER_USAGE

2674

PSU1_DC_OK

PSU2_DC_OK

PSU3_DC_OK

PSU4_DC_OK

PSU1_AC_OK

PSU2_AC_OK

PSU3_AC_OK

PSU4_AC_OK

Normal

102

406 good good good

Watts

N/A

Normal

Normal good good good good good

PSU1_STATUS

PSU2_STATUS

PSU3_STATUS

PSU4_STATUS

Normal

Normal present present present present

Server /sensor # show psu-redundancy

Name Reading Sensor Status

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

PS_RDNDNT_MODE full Normal

Server /sensor #

882

798

N/A

Viewing Fan Sensors

Procedure

Step 1

Step 2

Command or Action

Server# scope sensor

Server /sensor # show fan [ detail ]

N/A

Purpose

Enters sensor command mode.

Displays fan sensor statistics for the server.

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

Viewing Sensors

Viewing Temperature Sensors

Example

This example displays fan sensor statistics:

Server# scope sensor

Server /sensor # show fan

Name

Max. Failure

Sensor Status Reading Units Min. Warning Max. Warning Min. Failure

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

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

5160 RPM 1118 N/A 946 PSU1_FAN_SPEED Normal

N/A

PSU2_FAN_SPEED Normal 6106 RPM 1118 N/A 946

N/A

PSU3_FAN_SPEED Normal

N/A

PSU4_FAN_SPEED Normal

N/A

FAN1_SPEED

N/A

Normal

Normal FAN2_SPEED

N/A

FAN3_SPEED

N/A

FAN4_SPEED

Normal

5762

4988

6600

6660

6600

6660

RPM

1118

2040

N/A

946

1800

N/A

FAN5_SPEED

N/A

FAN6_SPEED

N/A

FAN7_SPEED

N/A

FAN8_SPEED

N/A

Server /sensor #

Normal

6660

RPM

2040

N/A

1800

Viewing Temperature Sensors

Procedure

Step 1

Step 2

Command or Action

Server# scope sensor

Server /sensor # show temperature [ detail ]

Purpose

Enters sensor command mode.

Displays temperature sensor statistics for the server.

Example

This example displays temperature sensor statistics:

Server# scope sensor

Server /sensor # show temperature

Name Sensor Status Reading Units Min. Warning Max. Warning

Min. Failure Max. Failure

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

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

Viewing Sensors

Viewing Voltage Sensors

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

IOH_TEMP_SENS

85.0

N/A

P2_TEMP_SENS

N/A 81.0

P1_TEMP_SENS

N/A 81.0

DDR3_P2_D1_TMP

N/A 95.0

DDR3_P1_A1_TMP

N/A 95.0

FP_AMBIENT_TEMP

N/A 45.0

Normal

Server /sensor #

Viewing Voltage Sensors

Procedure

Step 1

Step 2

Command or Action

Server# scope sensor

Server /sensor # show voltage [ detail ]

32.0

31.0

34.0

20.0

21.0

28.0

N/A

80.0

90.0

40.0

Purpose

Enters sensor command mode.

Displays voltage sensor statistics for the server.

Example

This example displays voltage sensor statistics:

Server# scope sensor

Server /sensor # show voltage

Name

Min. Failure Max. Failure

Sensor Status Reading Units Min. Warning Max. Warning

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

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

P3V_BAT_SCALED

3.088

2.798

P12V_SCALED

11.623

12.331

P5V_SCALED

4.844

PV_VCCP_CPU1

5.157

P3V3_SCALED

3.191

3.381

P5V_STBY_SCALED

5.157

Normal

3.022

12.154

5.036

3.318

5.109

0.950

N/A

0.725

PV_VCCP_CPU2

0.725

1.391

P1V5_DDR3_CPU1

1.450

1.548

P1V5_DDR3_CPU2

1.450

1.548

P1V1_IOH

1.068

P1V8_AUX

1.136

Normal

0.891

1.499

1.087

1.773

N/A

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

Viewing Sensors

Viewing Current Sensors

1.744

1.852

Server /sensor #

Viewing Current Sensors

Procedure

Step 1

Step 2

Command or Action

Server# scope sensor

Server /sensor # show current [ detail ]

Purpose

Enters sensor command mode.

Displays current sensor statistics for the server.

Example

This example displays current sensor statistics:

Server# scope sensor

Server /sensor # show current

Name

Min. Failure Max. Failure

Sensor Status Reading Units Min. Warning Max. Warning

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

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

VR_P2_IMON Normal 16.00

AMP N/A 147.20

164.80

N/A

VR_P1_IMON

N/A 164.80

Normal 27.20

AMP N/A 147.20

Server /sensor #

Viewing Storage Sensors

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show hdd [ detail ]

Purpose

Enters chassis command mode.

Displays storage sensor information.

The displayed fields are described in the following table:

Name

Name column

Description

The name of the storage device.

Status column A brief description of the storage device status.

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

Viewing Sensors

Setting Dynamic Front Panel Temperature Threshold

Name

LED Status column

Description

The current LED color, if any.

To make the physical LED on the storage device blink, select Turn On from the drop-down list. To let the storage device control whether the

LED blinks, select Turn Off .

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

Example

This example displays storage sensor information:

Server# scope chassis

Server /chassis # show hdd

Name Status

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

HDD_01_STATUS present

HDD_02_STATUS

HDD_03_STATUS

HDD_04_STATUS present present present

Server /chassis #

Setting Dynamic Front Panel Temperature Threshold

Before you begin

Procedure

Step 1

Step 2

Step 3

Command or Action server # scope sensor server /sensor # set fp-critical-temp upper critical temperature threshold value server /sensor * # commit

Purpose

Enters sensor command mode

Sets the upper critical temperature threshold.

The valid range is between 8 and 50.

Commits the change in temperature threshold value.

Example

This example shows how to set the dynamic front panel temperature threshold:

Server # scope sensor

Valid value for "fp-critical-temp" is from 8 to 50

Server /sensor # set fp-critical-temp 44

Server /sensor *# commit

Server /sensor # show temperature

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

Viewing Sensors

Setting Dynamic Front Panel Temperature Threshold

Name Sensor Status Reading

Non-Recoverable Min Non-Recoverable Max

Units Critical Min Critical Max

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

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

VIC_SLOT1_TEMP Normal 58.0

C N/A 90.0

95.0

N/A

TEMP_SENS_FRONT

N/A 50.0

Normal 27.0

C N/A 40.0

29.0

C N/A 85.0

DDR4_P1_A1_TMP

N/A

DDR4_P2_G1_TMP

N/A

P1_TEMP_SENS

N/A

P2_TEMP_SENS

Normal

90.0

Normal

90.0

Normal

113.0

Normal

28.0

39.5

N/A

85.0

103.0

N/A

PSU1_TEMP

N/A

PSU2_TEMP

N/A

PCH_TEMP_SENS

N/A

RISER2_INLET_TMP

N/A

RISER1_INLET_TMP

N/A

113.0

Normal

70.0

Normal

70.0

Normal

90.0

Normal

80.0

Normal

27.0

26.0

36.0

37.0

36.0

N/A

65.0

85.0

70.0

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

Setting Dynamic Front Panel Temperature Threshold

Viewing Sensors

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

C H A P T E R

Managing Remote Presence

This chapter includes the following sections:

•

Managing the Virtual KVM, on page 89

•

Configuring Virtual Media, on page 92

•

Managing Serial over LAN, on page 96

Managing the Virtual KVM

Virtual KVM Console

Here are a few major advantages of using Cisco KVM Console:

• The Cisco KVM console provides connection to KVM, SOL, and vMedia whereas the Avocent KVM provides connection only to KVM and vMedia.

• In the KVM Console, the vMedia connection is established at the KVM Launch Manager and is available for all users.

• The KVM console offers you an advanced character replacement options for the unsupported characters while pasting text from the guest to the host.

• The KVM console provides you an ability to store the vMedia mappings on CIMC.

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

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

Managing Remote Presence

Enabling the Virtual KVM

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

• USB flash drive on the network

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

Note The vKVM Console is operated only through the GUI. To launch the vKVM Console, see the instructions in the Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide .

Enabling the Virtual KVM

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope kvm

Server /kvm # set enabled yes

Server /kvm # commit

Server /kvm # show [ detail ]

Purpose

Enters KVM command mode.

Enables the virtual KVM.

Commits the transaction to the system configuration.

(Optional) Displays the virtual KVM configuration.

Example

This example enables the virtual KVM:

Server# scope kvm

Server /kvm # set enabled yes

Server /kvm *# commit

Server /kvm # show

Encryption Enabled Local Video Active Sessions Enabled KVM Port

------------------ ---------------- --------------- ------- -------no yes 0 yes 2068

Server /kvm #

Disabling the Virtual KVM

Before you begin

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

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

Managing Remote Presence

Configuring the Virtual KVM

Procedure

Step 1

Step 2

Command or Action

Server# scope kvm

Server /kvm # set enabled no

Step 3 Server /kvm # commit

Step 4 Server /kvm # show [ detail ]

Purpose

Enters KVM command mode.

Disables the virtual KVM.

Note Disabling the virtual KVM disables access to the virtual media feature, but does not detach the virtual media devices if virtual media is enabled.

Commits the transaction to the system configuration.

(Optional) Displays the virtual KVM configuration.

Example

This example disables the virtual KVM:

Server# scope kvm

Server /kvm # set enabled no

Server /kvm *# commit

Server /kvm # show

Encryption Enabled Local Video Active Sessions Enabled KVM Port

------------------ ---------------- --------------- ------- -------no yes 0 no 2068

Server /kvm #

Configuring the Virtual KVM

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope kvm

Server /kvm # set enabled { yes | no }

Server /kvm # set encrypted { yes | no }

Server /kvm # set kvm-port port

Purpose

Enters KVM command mode.

Enables or disables the virtual KVM.

If encryption is enabled, the server encrypts all video information sent through the KVM.

Specifies the port used for KVM communication.

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

Managing Remote Presence

Configuring Virtual Media

Step 5

Command or Action

Server /kvm # set local-video { yes | no }

Step 6 Server /kvm # set max-sessions sessions

Step 7

Step 8

Server /kvm #

Server /kvm # commit show [ detail ]

Purpose

If local video is yes , the KVM session is also displayed on any monitor attached to the server.

Specifies the maximum number of concurrent

KVM sessions allowed. The sessions argument is an integer between 1 and 4.

Commits the transaction to the system configuration.

(Optional) Displays the virtual KVM configuration.

Example

This example configures the virtual KVM and displays the configuration:

Server# scope kvm

Server /kvm # set enabled yes

Server /kvm *# set encrypted no

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

Step 1

Command or Action

Server# scope vmedia

Purpose

Enters virtual media command mode.

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

Managing Remote Presence

Configuring Virtual Media

Step 2

Step 3

Step 4

Command or Action

Server /vmedia # set enabled { yes | no }

Purpose

Enables or disables virtual media. By default, virtual media is disabled.

Note Disabling virtual media detaches the virtual CD, virtual floppy, and virtual HDD devices from the host.

Server /vmedia # set encryption { yes | no } Enables or disables virtual media encryption.

Server /vmedia # set low-power-usb-enabled

{ yes | no }

Enables or disables low power USB.

Note While mapping an ISO to a server which has a UCS VIC P81E card and the NIC is in Cisco Card mode:

• If the low power USB is enabled, after mapping the ISO and rebooting the host the card resets and ISO mapping is lost.

The virtual drives are not visible on the boot selection menu.

• If the low power USB is disabled, after mapping the

ISO, and rebooting the host and the Cisco IMC, the virtual drivers appear on the boot selection menu as expected.

Step 5

Step 6

Server /vmedia #

Server /vmedia # commit show [ detail ]

Commits the transaction to the system configuration.

(Optional) Displays the virtual media configuration.

Example

This example configures virtual media encryption:

Server# scope vmedia

Server /vmedia # set enabled yes

Server /vmedia *# set encryption yes

Server /vmedia *# set low-power-use-enabled no

Server /vmedia *# commit

Server /vmedia # show detail vMedia Settings:

Encryption Enabled: yes

Enabled: yes

Max Sessions: 1

Active Sessions: 0

Low Power USB Enabled: no

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

Managing Remote Presence

Configuring a Cisco IMC-Mapped vMedia Volume

Server /vmedia #

What to do next

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

Configuring a Cisco IMC-Mapped vMedia Volume

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server # scope vmedia

Server /vmedia # map-cifs { volume-name | remote-share | remote-file-path [ mount options ]

Purpose

Enters the virtual media command mode.

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

• Name of the volume to create

• Remote share including IP address and the exported directory

• Path of the remote file corresponding to the exported directory.

• (Optional) Mapping options

• Username and password to connect to the server

Step 3

Step 4

Server /vmedia # map-nfs { volume-name | remote-share | remote-file-path } [ mount options ]

Maps an NFS file for vMedia. You must specify the following:

• Name of the volume to create

• Remote share including IP address and the exported directory

• Path of the remote file corresponding to the exported directory.

• (Optional) Mapping options

Server /vmedia # map-www { volume-name

| remote-share | remote-file-path [ mount options ]

Maps an HTTPS file for vMedia. You must specify the following:

• Name of the volume to create

• Remote share including IP address and the exported directory

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

Managing Remote Presence

Viewing Cisco IMC-Mapped vMedia Volume Properties

Command or Action Purpose

• Path of the remote file corresponding to the exported directory.

• (Optional) Mapping options

• Username and password to connect to the server

Example

This example shows how to create a CIFS Cisco IMC-mapped vmedia settings:

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 Cisco IMC-Mapped vMedia Volume Properties

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server # scope vmedia

Server /vmedia # show mappings detail

Purpose

Enters the virtual media command mode.

Displays information on all the vmedia mapping that are configured.

Example

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

Server # scope vmedia

Server /vmedia # show mappings

Volume Map-status Drive-type remote-share remote-file

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

Huu

Rhel

OK removable

CD mount-type

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

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

www www

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

Managing Remote Presence

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 Cisco

IMC.

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

Step 1

Step 2

Step 3

Command or Action

Server# scope sol

Server /sol # set enabled { yes | no }

Server /sol # set baud-rate { 9600 | 19200 |

38400 | 57600 | 115200 }

Purpose

Enters SoL command mode.

Enables or disables SoL on this server.

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

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

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

Managing Remote Presence

Configuring Serial Over LAN

Step 4

Step 5

Step 6

Command or Action

(Optional) Server /sol # set comport { com0 | com1

Purpose

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

Note This option is only available on some

C-Series servers. If it is not available, the server always uses

COM port 0 for SoL communication.

You can specify:

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

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

• com1 —SoL communication is routed through COM port 1, an internal port accessible only through SoL.

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

Note Changing the comport setting disconnects any existing SoL sessions.

Server /sol # commit

Server /sol # show [ detail ]

Commits the transaction to the system configuration.

(Optional) Displays the SoL settings.

Example

This example configures SoL:

Server# scope sol

Server /sol # set enabled yes

Server /sol *# set baud-rate 115200

Server /sol *# commit

Server /sol # show

Enabled Baud Rate(bps) Com Port

------- --------------- -------yes 115200 com2

Server /sol # show detail

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

Managing Remote Presence

Launching Serial Over LAN

Serial Over LAN:

Enabled: yes

Baud Rate(bps): 115200

Com Port: com2

Server /sol #

Launching Serial Over LAN

Procedure

Step 1

Command or Action

Server# connect host

Purpose

Opens a serial over LAN (SoL) connection to the redirected server console port. You can enter this command in any command mode.

What to do next

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

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

Managing User Accounts

C H A P T E R

This chapter includes the following sections:

•

Configuring Local Users, on page 99

•

Managing SSH Keys for User Accounts, on page 101

•

Non-IPMI User Mode, on page 106

•

Disabling Strong Password, on page 108

•

Configuring User Authentication Precedence, on page 109

•

Resetting the User Password, on page 109

•

LDAP Servers, on page 110

•

Configuring the LDAP Server, on page 111

•

Configuring LDAP in Cisco IMC, on page 112

•

Configuring LDAP Groups in Cisco IMC, on page 116

•

Configuring Nested Group Search Depth in LDAP Groups, on page 117

•

TACACS+ Authentication, on page 118

•

LDAP Certificates Overview, on page 120

•

Viewing User Sessions, on page 123

•

Terminating a User Session, on page 124

Configuring Local Users

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope user usernumber

Server /user #

Server /user # set enabled { yes | no

set name username

}

Purpose

Enters user command mode for user number usernumber .

Enables or disables the user account on the

Cisco IMC.

Specifies the username for the user.

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

Managing User Accounts

Configuring Local Users

Step 4

Command or Action

Server /user # set password

Step 5 Server /user # set role { readonly | user | admin }

Purpose

You are prompted to enter the password twice.

Note When strong password is enabled, you must follow these guidelines while setting a password:

• The password must have a minimum of 8 and a maximum of 14 characters.

• The password must not contain the User's Name.

• The password must contain characters from three of the following four categories:

• English uppercase characters (A through Z)

• English lowercase characters (a through z)

• Base 10 digits (0 through

• Non-alphabetic characters

(!, @, #, $, %, ^, &, *, -,

_, +, =) when strong password is disabled, you can set a password using characters of your choice

(alphanumeric, special characters, or integers) within the range 1-20.

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

• readonly—This user can view information but cannot make any changes.

• user—This user can do the following:

• View all information

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

• Launch the KVM console and virtual media

• Clear all logs

100

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

Managing User Accounts

Managing SSH Keys for User Accounts

Step 6

Command or Action

Server /user # commit

Purpose

• Toggle the locator LED

• Set the time zone

• Ping an IP address

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

Commits the transaction to the system configuration.

Example

This example configures user 5 as an admin:

Server# scope user 5

Server /user # set enabled yes

Server /user *# set name john

Server /user *# set password

Warning:

Strong Password Policy is enabled!

For CIMC protection your password must meet the following requirements:

The password must have a minimum of 8 and a maximum of 14 characters.

The password must not contain the User's Name.

The password must contain characters from three of the following four categories.

English uppercase characters (A through Z)

English lowercase characters (a through z)

Base 10 digits (0 through 9)

Please enter password:

Please confirm password:

Server /user *# set role readonly

Server /user *# commit

Server /user # show

User Name Role Enabled

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

5 john readonly yes

Managing SSH Keys for User Accounts

Configuring SSH Keys

In the release 4.1.2, Cisco IMC provides SSH RSA key-based authentication in addition to password authentication. SSH keys are a set of public and private RSA key pair, which you can use for authentication.

Public key-based authentication provides enhanced security over password-based authentication.

You must log in as a user with admin privileges to configure the SSH keys for all the users. If you are a non-admin user, you can configure the SSH keys to authenticate and login only to your account. You can

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

101

Managing User Accounts

Adding SSH Keys configure only one SSH RSA key pair, public and private, for your account. The SSH keys must be in .pem

or .pub format.

The Cisco IMC sessions authenticated using public keys will be active even if the password has expired. You can also start new sessions using the public SSH key even after the password has expired.

Account lockout option, available on some C-series servers, does not apply to the accounts that use public key authentication.

Adding SSH Keys

Before you begin

• You must log in as a user with admin privileges to add the SSH keys for all the users.

• If you are a non-admin user, you can add the public key only for your account.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope user user-number

Server /user # show-detail

Server /user # scope ssh-keys

Server /user/ssh-keys # add-key 1 remote

Purpose

Enters the user command mode for a user.

Displays the details of the user account. You can view the number of SSH keys configured for a user in the

SSH Key Count field.

Enters the SSH keys command mode.

Use this option to add the SSH key from a remote server.

Enter the following details: a.

Specify the protocol to connect to the remote server. It can be of the following types:

• TFTP

FTP

SFTP

SCP

HTTP

Note If you choose FTP, SCP or

SFTP, you will be prompted to enter your username and password.

Specify the remote server address.

Specify the remote file path.

Specify your username and password.

102

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

Managing User Accounts

Modifying SSH Keys

Step 5

Step 6

Command or Action Purpose

(Optional) Server /user/ssh-keys # add-key 2 paste

Use this option to add the SSH key by paste method.

Launches a dialog for entering the public SSH key. Copy the SSH key text, paste it into the console when prompted, and type CTRL+D.

(Optional) Server /user/ssh-keys # show-detail Displays the public SSH key that you have added to the account.

Example

This example adds the SSH key from a remote server.

Server# scope user 1

Server /user # scope ssh-keys

Server /user/ssh-keys # add-key 1 remote

Enter the remote Protocol [tftp | ftp | sftp | scp | http]: scp

Enter the remote Server: 10.10.10.10

Enter the remote file Path: /home/xyz/publickey.pem

Server (RSA) key fingerprint is dd:b5:2b:07:ad:c0:30:b2:d5:6a:6a:78:80:85:93:b0

Do you wish to continue? [y/N] y

Username: xyz

Password:

SSH Public key added successfully

Server /user/ssh-keys #

This example adds the SSH key by paste method.

Server# scope user 1

Server /user # scope ssh-keys

Server /user/ssh-keys # add-key 2 paste

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

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDFOK17ZYbMMfGcxGrfxlupMqFyl1ZNIJohPxAStu41

OkItF9VrrhrfF1ZKOpogJinx3s0OcPfGLMSWEQkUq1zGlL8rAESZbi6z36WGFeZ93amJ3nfxDU7JWD9K

HmINixpX5XbbZeKQJvfSTptanmkjTQ8sq2iSMK0HL+G35i8BXmwIBLuEM+SWIEYjLaDAZ6aLKPxxddTr

FxWTP9QpzJAfQGlXXZSYauYb6OMNUxjgqFtB2XCiROZTzcj4n1XQRbzU+56HvHmowcOPhO81Btbun+xv ksTeXbV3e9DVymjQK1qD2yY5h/EJdC0+9wGPyVmaT2bAOu4HbTsz8u4HFkTf

SSH Public key added successfully

Server /user/ssh-keys #

What to do next

Modify or delete the SSH key.

Modifying SSH Keys

Before you begin

• You must log in as a user with admin privileges to modify the SSH keys for all the users.

• If you are a non-admin user, you can modify the public key only for your account.

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

103

Managing User Accounts

Modifying SSH Keys

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope user user-number

Purpose

Enters the user command mode for a user.

Server /user # show-detail Displays the details of the user account. You can view the number of SSH keys configured for a user in the

SSH Key Count field.

Enters the SSH keys command mode.

Server /user # scope ssh-keys

Server /user/ssh-keys # modify-key 1 remote Use this option to add the modified key from a remote server. Enter the following details: a.

Specify the protocol to connect to the remote server. It can be of the following types:

• TFTP

FTP

SFTP

SCP

HTTP

Note If you choose FTP, SCP or

SFTP, you will be prompted to enter your username and password.

Specify the remote server address.

Specify the remote file path.

Specify your username and password.

(Optional) Server /user/ssh-keys # modify-key

2 paste

Use this option to add the modified SSH key by paste method.

Launches a dialog for entering the updated public SSH key. Copy the SSH key text, paste it into the console when prompted, and type

CTRL+D.

(Optional) Server /user/ssh-keys # show-detail Displays the updated public SSH key that you modified in the account.

Example

This example adds the modified SSH key from a remote server.

104

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

Managing User Accounts

Deleting SSH Keys

Server# scope user 1

Server /user # scope ssh-keys

Server /user/ssh-keys # modify-key 1 remote

Enter the remote Protocol [tftp | ftp | sftp | scp | http]: scp

Enter the remote Server: 10.10.10.10

Enter the remote file Path: /home/xyz/publickey.pem

Server (RSA) key fingerprint is dd:b5:2b:07:ad:c0:30:b2:d5:6a:6a:78:80:85:93:b0

Do you wish to continue? [y/N] y

Username: xyz

Password:

SSH Public key modified successfully

Server /user/ssh-keys #

This example adds the modified SSH key by paste method.

Server# scope user 1

Server /user # scope ssh-keys

Server /user/ssh-keys # modify-key 2 paste

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

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDFOK17ZYbMMfGcxGrfxlupMqFyl1ZNIJohPxAStu41

OkItF9VrrhrfF1ZKOpogJinx3s0OcPfGLMSWEQkUq1zGlL8rAESZbi6z36WGFeZ93amJ3nfxDU7JWD9K

HmINixpX5XbbZeKQJvfSTptanmkjTQ8sq2iSMK0HL+G35i8BXmwIBLuEM+SWIEYjLaDAZ6aLKPxxddTr

FxWTP9QpzJAfQGlXXZSYauYb6OMNUxjgqFtB2XCiROZTzcj4n1XQRbzU+56HvHmowcOPhO81Btbun+xv ksTeXbV3e9DVymjQK1qD2yY5h/EJdC0+9wGPyVmaT2bAOu4HbTsz8u4HFkTf

SSH Public key modified successfully

Server /user/ssh-keys #

What to do next

Delete the SSH key.

Deleting SSH Keys

Before you begin

• You must log in as a user with admin privileges to delete the SSH keys for all the users.

• If you are a non-admin user, you can delete the public key only for your account.

Procedure

Step 1

Step 2

Command or Action

Server # scope user user-number

Server /user # show-detail

Step 3

Step 4

Server /user # scope ssh-keys

Server /user/ssh-keys # delete-key 1

Step 5 Enter y to confirm the deletion.

Purpose

Enters the user command mode for a user.

Displays the details of the user account. The field

SSH Key Count displays the number of

SSH keys that are configured for the user.

Enters the SSH keys command mode.

A prompt with the message

Do you wish to continue? [y/N] is displayed.

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

105

Managing User Accounts

Non-IPMI User Mode

Step 6

Command or Action Purpose

(Optional) Server /user/ssh-keys # show-detail Displays the updated user details and SSH key count.

Example

This example deletes the SSH key.

Server# scope user 1

Server /user # scope ssh-keys

Server /user/ssh-keys # delete-key 1

This operation will delete the SSH key ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDFOK17ZYbMMfGcxGrfxlupMqFyl1ZNIJohPxAStu41

OkItF9VrrhrfF1ZKOpogJinx3s0OcPfGLMSWEQkUq1zGlL8rAESZbi6z36WGFeZ93amJ3nfxDU7JWD9K

HmINixpX5XbbZeKQJvfSTptanmkjTQ8sq2iSMK0HL+G35i8BXmwIBLuEM+SWIEYjLaDAZ6aLKPxxddTr

FxWTP9QpzJAfQGlXXZSYauYb6OMNUxjgqFtB2XCiROZTzcj4n1XQRbzU+56HvHmowcOPhO81Btbun+xv ksTeXbV3e9DVymjQK1qD2yY5h/EJdC0+9wGPyVmaT2bAOu4HbTsz8u4HFkTf

Do you wish to continue? [y/N]y

SSH Public key deleted successfully

Server /user/ssh-keys #

Non-IPMI User Mode

Release 4.1 introduces a new user configuration option called User Mode that allows you to switch between

IPMI and non-IPMI user modes. Introduction of the non-IPMI user mode provides enhanced password security for users and security enhancements to the BMC database that were restricted in earlier releases due to the constraints posed by the IPMI 2.0 standards. Non-IPMI user mode allows you to use 127 characters to set user passwords whereas users in IPMI mode are restricted to a password length of 20 characters. Non-IPMI user mode enables you to set stronger passwords for users configured in this mode.

You must consider the following configuration changes that occur while switching between user modes, when you:

• Switch to the non-IPMI mode, IPMI over LAN will not be supported.

• Switch from the non-IPMI to IPMI mode, deletes all the local users and reverts user credentials to default username and password. On subsequent login, you will be prompted to change the password.

User data is not affected when you switch from IPMI to non-IPMI mode.

• Downgrade the firmware to a versions lower than 4.1 and if the user mode is non-IPMI, deletes all the local users and reverts user credentials to default username and password. On subsequent login, you will be prompted to change the default password.

Note When you reset to factory defaults, the user mode reverts to IPMI mode.

106

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

Managing User Accounts

Switching User Mode from IPMI to Non-IPMI

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope user-policy

Purpose

Enters user policy command mode.

Server /user-policy # scope user-mode Enters user mode command mode.

Server /user-policy/user-mode # set user-mode non-ipmi

Enter y at the confirmation prompt to switch to

Non-IPMI user mode.

Server /user-policy/user-mode * # commit Commits the transaction to the system configuration.

Server /user-policy/user-mode # show detail Displays the user mode.

Example

This example shows how to disable strong password:

Server# scope user-policy

Server /user-policy # scope user-mode

Server /user-policy/user-mode # set user-mode non-ipmi

Server /user-policy/user-mode *# commit

Warning: This will enable NON-IPMI based user mode.

Converting to Non-IPMI User Mode disables IPMI Services and removes IPMI user support.

SSH, KVM, Webserver, XMAPI and Redfish sessions will be disconnected.

Do you wish to continue? [y/N] y

Connection to 10.10.10.10 closed by remote host.

Connection to 10.10.10.10 closed.

Server /user-policy/user-mode # show detail

User Mode:

User mode for IPMI accessibility: non-ipmi

Server /user-policy/user-mode #

Switching User Mode from Non-IPMI to IPMI

Before you begin

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

Procedure

Step 1

Command or Action

Server# scope user-policy

Purpose

Enters user policy command mode.

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

107

Managing User Accounts

Disabling Strong Password

Step 2

Step 3

Step 4

Step 5

Command or Action

Server /user-policy # scope user-mode

Purpose

Enters user mode command mode.

Server /user-policy/user-mode # set user-mode ipmi

Enter y at the confirmation prompt to switch to

IPMI user mode.

Note Switching to IPMI user mode deletes all the UCS users and reverts to default username and password.

Server /user-policy/user-mode * # commit Commits the transaction to the system configuration.

Server /user-policy/user-mode # show detail Displays the user mode.

Example

This example shows how to disable strong password:

Server# scope user-policy

Server /user-policy # scope user-mode

Server /user-policy/user-mode # set user-mode ipmi

Server /user-policy/user-mode *# commit

Warning: This will enable IPMI based user mode.

Converting to IPMI User Mode deletes all UCS users and reverts to default userid/password.

SSH, KVM, Webserver, XMAPI and Redfish sessions will be disconnected.

Do you wish to continue? [y/N] y

Connection to 10.10.10.10 closed by remote host.

Connection to 10.10.10.10 closed.

Server /user-policy/user-mode # show detail

User Mode:

User mode for IPMI accessibility: ipmi

Server /user-policy/user-mode #

Disabling Strong Password

The Cisco IMC now implements a strong password policy wherein you are required to follow guidelines and set a strong password when you first log on to the server for the first time. The Cisco IMC CLI provides you option which allows you to disable the strong password policy and set a password of your choice by ignoring the guidelines. Once you disable the strong password, an Enable Strong Password button is displayed. By default, the strong password policy is enabled.

Before you begin

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

Procedure

Step 1

Command or Action

Server# scope user-policy

Purpose

Enters user policy command mode.

108

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

Managing User Accounts

Configuring User Authentication Precedence

Step 2

Step 3

Command or Action

Server /user-policy # set password-policy

{ enabled | disabled }

Server /user-policy # commit

Purpose

At the confirmation prompt, enter y to complete the action or n to cancel the action. Enables or disables the strong password.

Commits the transaction to the system configuration.

Example

This example shows how to disable strong password:

Server# scope user-policy

Server /user-policy # set password-policy disabled

Warning: Strong password policy is being disabled.

Do you wish to continue? [y/N] y

Server /user-policy *# commit

Server /user-policy #

Configuring User Authentication Precedence

Procedure

Step 1

Step 2

Step 3

Command or Action

Server # scope user-policy

Server/user-policy # set

authentication-precedence User Database name

Server/user-policy # commit

Purpose

Enters the TACACS+ command mode.

Enter comma delimited list of user database.

Example

Server # scope user-policy

Server /user-policy # set authentication-precedence DB1,DB2

Server /user-policy* # commit

Resetting the User Password

You can use the change password option to change your password.

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

109

Managing User Accounts

LDAP Servers

Note • This option is not available when you login as an admin, you can only change the password of the configured users with read-only user privileges.

• When you change your password you will be logged out of Cisco IMC.

Procedure

Step 1

Step 2

Command or Action

Server # scope user user ID

Server /chassis/user # set password

Step 3 Server /chassis/user * # commit

Purpose

Enters the chosen user command mode.

Read the password requirements instructions and enter the current password, new password and confirm the password at the respective prompts.

Commits the transaction to the system configuration.

Example

This example shows how to change the password of a configured user:

Server # scope user 2

Server /chassis/user # set password

Warning:

Strong Password Policy is enabled!

For CIMC protection your password must meet the following requirements:

The password must have a minimum of 8 and a maximum of 20 characters.

The password must not contain the User's Name.

The password must contain characters from three of the following four categories.

English uppercase characters (A through Z)

English lowercase characters (a through z)

Base 10 digits (0 through 9)

Non-alphabetic characters (!, @, #, $, %, ^, &, *, -, _, +, =)

Please enter current password: Testabcd1

Please enter password: Testabcd2

Please confirm password: Testabcd2

Server /chassis/user * # commit

Server /chassis/user #

LDAP Servers

Cisco IMC supports directory services that organize information in a directory, and manage access to this information. Cisco IMC supports Lightweight Directory Access Protocol (LDAP), which stores and maintains directory information in a network. In addition, Cisco IMC supports Microsoft Active Directory (AD). 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 Cisco IMC utilizes the Kerberos-based authentication service of LDAP.

110

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

Managing User Accounts

Configuring the LDAP Server

When LDAP is enabled in the Cisco IMC, user authentication and role authorization is performed by the

LDAP server for user accounts not found in the local user database. The LDAP user authentication format is [email protected].

By enabling encryption in the configuration of Active Directory on the server, you can require the server to encrypt data sent to the LDAP server.

Configuring the LDAP Server

The Cisco IMC can be configured to use LDAP for user authentication and authorization. To use LDAP, configure users with an attribute that holds the user role and locale information for the Cisco IMC. You can use an existing LDAP attribute that is mapped to the Cisco IMC user roles and locales or you can modify the

LDAP schema to add a new custom attribute, such as the CiscoAVPair attribute, which has an attribute ID of 1.3.6.1.4.1.9.287247.1.

Important For more information about altering the schema, see the article at http://technet.microsoft.com/en-us/library/bb727064.aspx

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

If you are using Group Authorization on the Cisco IMC LDAP configuration, then you can skip Steps 1-4 and perform the steps listed in the Configuring LDAP Settings and Group Authorization in Cisco IMC section.

The following steps must be performed on the LDAP server.

Procedure

Step 1

Step 2

Step 3

Ensure that the LDAP schema snap-in is installed.

Using the schema snap-in, add a new attribute with the following properties:

Properties Value

Common Name

LDAP Display Name

Unique X500 Object ID

Description

Syntax

CiscoAVPair

1.3.6.1.4.1.9.287247.1

CiscoAVPair

Case Sensitive String

Add the CiscoAVPair attribute to the user class using the 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 .

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

111

Managing User Accounts

Configuring LDAP in Cisco IMC

Step 4 c) Type C to select the CiscoAVPair attribute.

d) Click OK .

Add the following user role values to the CiscoAVPair attribute, for the users that you want to have access to Cisco IMC:

Role CiscoAVPair Attribute Value admin shell:roles="admin" user read-only shell:roles="user" shell:roles="read-only"

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

What to do next

Use the Cisco IMC to configure the LDAP server.

Configuring LDAP in Cisco IMC

Configure LDAP in Cisco IMC when you want to use an LDAP 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

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope ldap

Server /ldap # set enabled { yes | no }

Purpose

Enters the LDAP command mode.

Enables or disables LDAP security. When enabled, user authentication and role authorization is performed by LDAP for user accounts not found in the local user database.

Server /ldap # set domainLDAP domain name Specifies an LDAP domain name.

Server /ldap # set timeout seconds

Server /ldap # set base-dn domain-name

Specifies the number of seconds the Cisco IMC waits until the LDAP search operation times out. The value must be between 0 and 1800 seconds.

Specifies the Base DN that is searched on the

LDAP server.

112

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

Managing User Accounts

Configuring LDAP in Cisco IMC

Step 6

Step 7

Step 8

Step 9

Command or Action

Server /ldap # set attribute name

Purpose

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

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

1.3.6.1.4.1.9.287247.1

Note If you do not specify this property, user access is denied.

Server /ldap # set filter-attribute Specifies the account name attribute. If Active

Directory is used, then specify sAMAccountName for this field.

Enters the secure LDAP mode.

Server /ldap # scope secure

Enable secure LDAP and either download the certificate remotely or paste the certificate.

Perform one of the following: a.

Server /ldap # secure-ldap disabled|enabled paste tftp | ftp | sftp | scp

| http

Prompts you to paste the certificate content.

Paste the certificate content and press

CTRL+D .

Confirmation prompt appears.

At the confirmation prompt, enter y .

This begins the download of the LDAP

CA certificate.

OR a.

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

113

Managing User Accounts

Configuring LDAP in Cisco IMC

Step 10

Step 11

Command or Action

Server /ldap #

Server /ldap # commit show [ detail ]

Purpose

Note The Cisco UCS C-Series server now supports fingerprint confirmation of the server when you update firmware through a remote server. This option is available only if you choose

SCP or SFTP as the remote server type.

If you chose SCP or SFTP as the remote server type while performing this action, a prompt with the message Server

(RSA) key fingerprint is

<server_finger_print _ID> Do you wish to continue? Click y or n depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

At the confirmation prompt, enter y .

This begins the download of the LDAP

CA certificate.

Commits the transaction to the system configuration.

(Optional) Displays the LDAP configuration.

Example

This example configures LDAP using remote download option:

Server# scope ldap

Server /ldap # set enabled yes

Server /ldap *# set domain sample-domain

Server /ldap *# set timeout 60

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

Server /ldap *# set attribute CiscoAVPair

Server /ldap *# set filter-attribute sAMAccountName

Server /ldap *# scope secure

Server /ldap/secure *# secure-ldap enabled remote ftp xx.xx.xx.xx filename

% Total % Received % Xferd Average Speed Time Time Time Current

100 1282 100 1282

Dload Upload Total Spent

1247

1239

0:00:01

You are going to overwrite the LDAP CA Certificate.

Left

0:00:01 --:--:--

Speed

1635

1239

114

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

Managing User Accounts

Configuring LDAP in Cisco IMC

Are you sure you want to proceed and overwrite the LDAP CA Certificate? [y|N] y

LDAP CA Certificate is downloaded successfully

Server /ldap/secure *# commit

Server /ldap # exit

Server /ldap # show detail

LDAP Settings:

Enabled: yes

Domain: sample-domain

BaseDN: example.com

Timeout: 60

Filter-Attribute: sAMAccountName

Server /ldap #

This example configures secure LDAP using paste certificate option:

Server# scope ldap

Server /ldap # set enabled yes

Server /ldap *# set domain sample-domain

Server /ldap *# set timeout 60

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

Server /ldap *# set attribute CiscoAVPair

Server /ldap *# set filter-attribute sAMAccountName

Server /ldap *# scope secure

Server /ldap/secure *# secure-ldap enabled ftp paste

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

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

MIIDdzCCAl+gAwIBAgIQV06yJcJPAYNO8Cp+FYQttjANBgkqhkiG9w0BAQsFADBO

MRIwEAYKCZImiZPyLGQBGRYCaW4xGzAZBgoJkiaJk/IsZAEZFgs0T0JKUkEySkhC

UTEbMBkGA1UEAxMSV0lOLTRPQkpSQTJKSEJRLUNBMB4XDTE2MDIyNTE3MDczNloX

DTIxMDIyNTE3MTczM1owTjESMBAGCgmSJomT8ixkARkWAmluMRswGQYKCZImiZPy

LGQBGRYLNE9CSlJBMkpIQlExGzAZBgNVBAMTEldJTi00T0JKUkEySkhCUS1DQTCC

ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMM2cdgmrPTkZe4K2zI+EbeZ mfQnjfiUz8OIY97w8lC/2S4qK46T+fnX13rXe8vvVHAO5wgPDVQTGS4nlF46A6Ba

FK+krKcIgFrQB1gnF74qs/ln1YtKHNBjrvg5KyeWFrA7So6Mi2XEw8w/zMPL0d8T b+LM1YnhnuXA9G8gVCJ/iUhXfMpB20L8sv30Mek7bw8x2cxJYTuJAviVIrjSwU5j fO3WKttRuyFpeOIi00weklpF0+8D3Z9mBinoTbL2pl0U32am6wTI+8WmtJ+8W68v jH4Y8YBY/kzMHdpwjpdZkC5pE9BcM0rL9xKoIu6X0kSNEssoGnepFyNaH3t8vnMC

AwEAAaNRME8wCwYDVR0PBAQDAgGGMA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYE

FBAUulHTAWBT1OBz8IgAEzXsfcCsMBAGCSsGAQQBgjcVAQQDAgEAMA0GCSqGSIb3

DQEBCwUAA4IBAQAzUMZr+0r1dWkVfFNBd7lu8tQbAEJf/A7PIKnJGNoUq8moAGs4 pMndoxdpNGZhYCWDWX3GWdeF1HqZHhb38gGQ9ylu0pIK7tgQufZmeCBH6T7Tzq/w

Dq+TMFGIjXF84xW3N665y4ePgUcUI7e/6aBGcGkGeUYodBPtExe28tQyeuYwD4Zj nLuZKkT+I4PAYygVCqxDGsvfRHDpGneb3R+GeonOf4ED/0tn5PLSL9khb9qkHu/V dO3/HmKVzUhloTDBuAMq/wES2WZAWhGr3hBc4nWQNjZWEMOKDpYZVK/GhBmNF+xi eRcFqgh64oEmH9qAp0caGS1e7UyYaN+LtPRe

-----END CERTIFICATE-----

CTRL+D

You are going to overwrite the LDAP CA Certificate.

Are you sure you want to proceed and overwrite the LDAP CA Certificate? [y|N] y

Server /ldap/secure *# commit

Server /ldap # exit

Server /ldap # show detail

LDAP Settings:

Enabled: yes

Domain: sample-domain

BaseDN: example.com

Timeout: 60

Filter-Attribute: sAMAccountName

Server /ldap #

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

115

Managing User Accounts

Configuring LDAP Groups in Cisco IMC

What to do next

If you want to use LDAP groups for group authorization, see Configuring LDAP Groups in Cisco IMC .

Configuring LDAP Groups in Cisco IMC

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 Cisco IMC 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.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action

Server# scope ldap

Server /ldap# scope ldap-group-rule

Purpose

Enters the LDAP command mode for AD configuration.

Enters the LDAP group rules command mode for AD configuration.

Server /ldap/ldap-group-rule # set group-auth

{ yes | no }

Enables or disables LDAP group authorization.

Server /ldap # scope role-group index Selects one of the available group profiles for configuration, where index is a number between

1 and 28.

Server /ldap/role-group # set name group-name Specifies the name of the group in the AD database that is authorized to access the server.

Server /ldap/role-group # set domain domain-name

Specifies the AD domain the group must reside in.

Server /ldap/role-group # set role { admin | user

| readonly }

Specifies the permission level (role) assigned to all users in this AD group. This can be one of the following:

• admin —The user can perform all actions available.

• user —The user can perform the following tasks:

• View all information

116

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

Managing User Accounts

Configuring Nested Group Search Depth in LDAP Groups

Command or Action

Step 8 Server /ldap/role-group # commit

Purpose

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

• Launch the KVM console and virtual media

• Clear all logs

• Toggle the locator LED

• readonly —The user can view information but cannot make any changes.

Commits the transaction to the system configuration.

Example

This example shows how to configure LDAP group authorization:

Server# scope ldap

Server /ldap # scope ldap-group-rule

Server /ldap/ldap-group-rule # set group-auth yes

Server /ldap *# scope role-group 5

Server /ldap/role-group # set name Training

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

Server /ldap/role-group* # set role readonly

Server /ldap/role-group* # commit ucs-c250-M2 /ldap # show role-group

Group Group Name

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

Domain Name Assigned Role

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

(n/a)

Training

(n/a)

(n/a) example.com

admin user readonly

(n/a) readonly

Server /ldap/role-group #

Configuring Nested Group Search Depth in LDAP Groups

You can search for an LDAP group nested within another defined group in an LDAP group map.

• 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 4.2

117

Managing User Accounts

TACACS+ Authentication

Procedure

Step 1

Command or Action

Server# scope ldap

Step 2 Server /ldap# scope ldap-group-rule

Step 3

Step 4

Server /ldap/ldap-group-rule # set

group-search-depth value

Server /ldap/role-group-rule # commit

Purpose

Enters the LDAP command mode for AD configuration.

Enters the LDAP group rules command mode for AD configuration.

Enables search for a nested LDAP group.

Commits the transaction to the system configuration.

Example

This example shows how to search for run a search for an LDAP group nested within another defined group.

Server# scope ldap

Server /ldap # scope ldap-group-rule

Server /ldap/ldap-group-rule # set group-search-depth 10

Server /ldap/role-group-rule* # commit

Server /ldap/role-group-rule # show detail

Group rules for LDAP:

Group search attribute: memberOf

Enable Group Authorization: yes

Nested group search depth: 10

Server/ldap/ldap-group-rule #

TACACS+ Authentication

Beginning with 4.1(3b) release, Cisco IMC supports Terminal Access Controller Access-Control System Plus

(TACACS+) user authentication. Cisco IMC supports up to six TACACS+ remote servers. Once a user is successfully authenticated, the username is appended with (TACACS+) . This is also displayed in the Cisco

IMC interfaces.

Refer

Enabling TACACS+ Authentication, on page 119

to enable TACACS+ Authentication. Cisco IMC also supports user authentication precedence in case TACACS+ remote servers are inaccessible. User authentication precedence can be configured using

Configuring User Authentication Precedence, on page 109 .

TACACS+ Server Configuration

Privilege level of a user is calculated based on the cisco-av-pair value configured for that user. A cisco-av-pair should be created on the TACACS+ server. Users cannot use any existing TACACS+ attributes.

Following three syntax are supported for the cisco-av-pair attribute:

• For admin privilege: cisco-av-pair=shell:roles=”admin”

• For user privilege: cisco-av-pair=shell:roles=”user”

118

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

Managing User Accounts

Enabling TACACS+ Authentication

• For read-only privilege: cisco-av-pair=shell:roles=”read-only”

More roles, if required, can be added by using comma as a separator.

Note If cisco-av-pair is not configured on the TACACS+ server, then a user with that server has read-only privilege.

Enabling TACACS+ Authentication

Before you begin

Before configuring Terminal Access Controller Access-Control System (TACACS+) based user authentication, ensure that privilege level of a user is configured on TACACS+ server based on the cisco-av-pair value.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope tacacs+

Server/tacacs+ # set enabled yes|no

Server/tacacs+ # set

fallback-only-on-no-connectivity yes|no

Purpose

Enters the TACACS+ command mode.

If you are enabling fallback-only-on-no-connectivity , enter Y to confirm.

Server/tacacs+ # set timeout timeout duration in seconds

Enter a value between 5 to 30.

Server/tacacs+ # restore If you wish to restore TACACS+ configuration to default in case of time out, enter yes to confirm.

Server/tacacs+ # commit Saves the changes in the system.

Example

Server # scope tacacs+

Server /tacacs+ # set enabled yes

Server /tacacs+ # set fallback-only-on-no-connectivity yes

Warning: If TACACS+ and fallback option is enabled, then the fallback to the next precedence database happens only when CIMC is not able to connect to any of the configured TACACS+ servers.

Do you wish to continue? [y/N] y

Server /tacacs+ # set timeout 5

Server /tacacs+ # restore

Are you sure you want to restore TACACS+ configuration to defaults?

Please enter 'yes' to confirm: yes

Restored TACSCS+ default configuration.

Server /tacacs+ # commit

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

119

Managing User Accounts

Configuring TACACS+ Remote Server Settings

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server#

Server# scope tacacs+

scope tacacs-serverServer Number

Purpose

Enters the TACACS+ command mode.

Enters the TACACS server command mode.

Server/tacacs+/tacacs-server # set tacacs-port

Port Number

Enter a value between 1 and 65535.

Server/tacacs+/tacacs-server # set tacacs-key

Server Key

Enter the same key configured on the remote

TACACS+ server.

Server/tacacs+/tacacs-server # set

tacacs-server Server IP Address

Enter remote TACACS+ server IP address.

Server/tacacs+/tacacs-server # restore If you wish to restore TACACS+ configuration to default in case of time out, enter yes to confirm.

Example

Server # scope tacacs+

Server # scope tacacs-server 1

Server /tacacs+/tacacs-server # set tacacs-port 6

Server /tacacs+/tacacs-server # set tacacs-key xxx

Server /tacacs+/tacacs-server # set tacacs-server xx.xx.xx.xx

Server /tacacs+/tacacs-server # restore

Are you sure you want to restore TACACS+ configuration to defaults?

Please enter 'yes' to confirm: yes

Restored TACSCS+ default configuration.

Server /tacacs+/tacacs-server # commit

LDAP Certificates Overview

Cisco C-series servers allow an LDAP client to validate a directory server certificate against an installed CA certificate or chained CA certificate during an LDAP binding step. This feature is introduced in the event where anyone can duplicate a directory server for user authentication and cause a security breach due to the inability to enter a trusted point or chained certificate into the Cisco IMC for remote user authentication.

An LDAP client needs a new configuration option to validate the directory server certificate during the encrypted TLS/SSL communication.

120

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

Managing User Accounts

Exporting LDAP CA Certificate

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope ldap

Server# /ldap scope binding-certificate

Server /ldap/binding-certificate #

export-ca-certificate remote-protocol IP

Adderss LDAP CA Certificate file

Purpose

Enters the LDAP command mode.

Enters the LDAP CA certificate binding command mode.

Specifies the protocol to connect to the remote server. It can be of the following types:

• TFTP

• FTP

• SFTP

• SCP

• HTTP

If you chose SCP or SFTP as the remote server type while performing this action, a prompt with the message Server (RSA) key fingerprint is <server_finger_print

_ID> Do you wish to continue?

Click y or n depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

Initiates the export of the certificate.

Example

This example exports the LDAP certificate:

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

121

Managing User Accounts

Testing LDAP Binding

Server # scope ldap

Server /ldap # scope binding-certificate

Server /ldap/binding-certificate # export-ca-certificate tftp 172.22.141.66 test.csv

Initiating Export

% Total % Received % Xferd Average Speed Time Time

Dload Upload Total Spent

Time Current

Left Speed

100 1262

100

1262

1244

1237

LDAP CA Certificate is exported successfully

0:00:01

0:00:01 --:--:--

1653

1237

Server /ldap/binding-certificate #

Testing LDAP Binding

Before you begin

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

Note If you checked the Enable Encryption and the Enable Binding CA Certificate check boxes, enter the fully qualified domain name (FQDN) of the LDAP server in the LDAP Server field. To resolve the FQDN of the

LDAP server, configure the preferred DNS of Cisco IMC network with the appropriate DNS IP address.

Procedure

Step 1

Step 2

Command or Action

Server# scope ldap

Server# /ldap scope binding-certificate

Step 3

Step 4

Server /ldap/binding-certificate #

test-ldap-binding username

Enter the corresponding password.

Purpose

Enters the LDAP command mode.

Enters the LDAP CA certificate binding command mode.

Password prompt appears.

Authenticates the user.

Example

This example tests the LDAP user binding:

Server # scope ldap

Server /ldap # scope binding-certificate

Server /ldap/binding-certificate # test-ldap-binding user

Password: diagldapbinding: Authenticated by LDAP

User user authenticated successfully.

Server /ldap/binding-certificate #

122

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

Managing User Accounts

Deleting LDAP CA Certificate

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope ldap

Server# /ldap scope binding-certificate

Server /ldap/binding-certificate # delete-ca-certificate

At the confirmation prompt, enter y .

Purpose

Enters the LDAP command mode.

Enters the LDAP CA certificate binding command mode.

Confirmation prompt appears.

This deletes the LDAP CA certificate.

Example

This example deletes the LDAP certificate:

Server # scope ldap

Server /ldap # scope binding-certificate

Server /ldap/binding-certificate # delete-ca-certificate

You are going to delete the LDAP CA Certificate.

Are you sure you want to proceed and delete the LDAP CA Certificate? [y|N] y

LDAP CA Certificate is deleted successfully

Server /ldap/binding-certificate #

Viewing User Sessions

Procedure

Step 1

Command or Action

Server# show user-session

Purpose

Displays information about current user sessions.

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

Name

Session ID column

BMC Session ID

Description

The unique identifier for the session.

The identifier for the BMC session.

User Name column The username for the user.

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

123

Managing User Accounts

Terminating a User Session

Name

IP Address

Action column

Session Type column column

Description

The IP address from which the user accessed the server. If this is a serial connection, it displays N/A .

The type of session the user chose to access the server. This can be one of the following:

• webgui — indicates the user is connected to the server using the web UI.

• CLI — indicates the user is connected to the server using CLI.

• serial — indicates the user is connected to the server using the serial port.

This column displays N/A when the SOL is enabled and Terminate when the SOL is disabled. You can terminate a session by clicking

Terminate on the web UI.

Example

This example displays information about current user sessions:

Server# show user-session

ID Name IP Address Type Killable

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

15 admin 10.20.30.138

CLI yes

Server /user #

Terminating a User Session

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# show user-session

Server /user-session # session-number

Server /user-session # scope user-session terminate

Purpose

Displays information about current user sessions. The user session to be terminated must be eligible to be terminated (killable) and must not be your own session.

Enters user session command mode for the numbered user session that you want to terminate.

Terminates the user session.

124

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

Managing User Accounts

Example

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

Server# show user-session

ID Name IP Address Type Killable

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

15 admin admin

10.20.41.234

10.20.30.138

Server# scope user-session 15

CLI

CLI yes yes

Server /user-session # terminate

User session 15 terminated.

Server /user-session #

Terminating a User Session

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

125

Terminating a User Session

Managing User Accounts

126

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

C H A P T E R

Configuring Network-Related Settings

This chapter includes the following sections:

•

Server NIC Configuration, on page 127

•

Common Properties Configuration, on page 136

•

Configuring IPv4, on page 138

•

Configuring IPv6, on page 140

•

Configuring ICMP, on page 143

•

Configuring the Server VLAN, on page 144

•

Connecting to a Port Profile, on page 146

•

Network Interface Configuration, on page 147

•

Network Security Configuration, on page 149

•

Network Time Protocol Configuration, on page 151

•

Pinging an IP address, on page 152

Server NIC Configuration

Server NICs

NIC Mode

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

• Dedicated —The management port that is used to access the Cisco IMC.

• Cisco Card —Any port on the adapter card that can be used to access the Cisco IMC. The Cisco adapter card has to be installed in a slot with Network the Communications Services Interface protocol support

(NCSI).

• Shared LOM —Any LOM (LAN on Motherboard) port that can be used to access Cisco IMC.

• Shared LOM Extended —Any LOM port or adapter card port that can be used to access Cisco IMC.

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 4.2

127

Configuring Network-Related Settings

Server NICs

Note Shared LOM and Shared LOM Extended ports are available only on some

C-series servers.

Note For other UCS C-Series M4, M5, C220 M6, and C240 M6 servers, the NIC mode is set to Shared LOM Extended by default.

• Shared OCP —The OCP adapter card LOM ports are used to access Cisco IMC. You must select either the Active-Active or Active-standby NIC redundancy setting in the following step.

• Shared OCP Extended —In this NIC mode, DHCP replies are returned to both the OCP adapter card

LOM ports and the Cisco virtual interface card (VIC) ports. If the system determines that the Cisco VIC connection is not getting its IP address from a Cisco UCS Manager system because the server is in standalone mode, further DHCP requests from the Cisco VIC are disabled.

Note Shared OCP and Shared OCP Extended ports are available only on Cisco UCS

C225 M6 and C245 M6 servers.

Default NIC Mode Setting :

• For UCS C-Series C125 M5 servers and S3260 servers, the NIC Mode is set to Cisco Card by default.

For UCS C-Series C225 M6 and C245 M6 servers:

• if the server has a Cisco VIC card with OCP card, then the default NIC mode is Shared OCP Extended and NIC Redundancy is set to active-active .

• if the server has VIC card populated in NCSI supported slots and no OCP card, then the default NIC mode is Cisco Card .

• if the server does not have any VIC card and OCP card, the default NIC mode is Dedicated and NIC

Redundancy is set to None .

NIC Redundancy

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

• active-active —If supported, all ports that are associated with the configured NIC mode operate simultaneously. This feature increases throughput and provides multiple paths to the Cisco IMC.

• active-standby —If a port that is associated with the configured NIC mode fails, traffic fails over to one of the other ports associated with the NIC mode.

Note If you choose this option, make sure that 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.

128

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

Configuring Network-Related Settings

Server NICs

• None —In Dedicated mode, NIC redundancy is set to None .

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

VIC Slots

The VIC slot that can be used for management functions in Cisco card mode.

For C240 M6 and C245 M6, VIC slot options are as follows:

• Riser 1 —Slot 1 and Slot 2

• Riser 2 —Slot 4 and Slot 5

• mLOM

Note For C240 M6 and C245 M6, after resetting to factory default settings, the slot precedence is as follows:

mLOM

Riser 1 - Slot 2; and Riser 2 - Slot 5

Riser 1 - Slot 1; and Riser 2- Slot 4

For C220 M6 and C225 M6, VIC slot options are as follows:

• Riser 1 —Slot 1 is selected.

• Riser 3 —Slot 3 is selected.

• mLOM

Note For C220 M6 and C225 M6, after resetting to factory default settings, the slot precedence is as follows:

mLOM

Riser 1 - Slot 1

Riser 3 - Slot 3

For C125 M5, VIC slot option is Riser 2 .

For C220 M4, C220 M5 and C240 M5 servers, VIC slot options are as follows:

• Riser 1 —Slot 1 is selected.

• Riser 2 —Slot 2 is selected.

• FLEX LOM —Slot 3 (MLOM) is selected.

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

129

Configuring Network-Related Settings

Configuring Server NICs

For C240 M4 servers, VIC slot options are as follows:

• Riser 1 —Slot 2 is the primary slot, but you can also use slot 1.

• Riser 2 —Slot 5 is the primary slot, but you can also use slot 4.

• FLEX LOM —Slot 7 (MLOM) is selected.

For C480 M5 ML servers, Cisco card mode slot is Slot 11 and Slot 12.

The following options are available only on some UCS C-Series servers:

• 4

• 5

• 9

• 10

Note This option is available only on some UCS C-Series servers.

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

Step 1

Step 2

Step 3

Command or Action

Server# scope cimc

Server /cimc # scope network

Purpose

Enters the Cisco IMC command mode.

Enters the Cisco IMC network command mode.

Server /cimc/network # set mode { dedicated

| shared_lom | shared_lom_10g | shipping | cisco_card | share_lom_ext | shared_ocp | shared_ocp_ext }

Sets the NIC mode to one of the following:

• Dedicated —The management port that is used to access the Cisco IMC.

• Cisco Card —Any port on the adapter card that can be used to access Cisco IMC. The

Cisco adapter card has to be installed in a slot with Network the Communications

Services Interface protocol support

(NCSI).

• Shared LOM —Any LOM (LAN on

Motherboard) port that can be used to access Cisco IMC.

130

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

Configuring Network-Related Settings

Command or Action

Configuring Server NICs

Purpose

• Shared LOM Extended —Any LOM port or adapter card port that can be used to access Cisco IMC. The Cisco adapter card has to be installed in a slot with NCSI support.

Note Shared LOM and Shared

LOM Extended ports are available only on some C-series servers.

Note For other UCS C-Series M4,

M5, C220 M6, and C240 M6 servers, the NIC mode is set to

Shared LOM Extended by default.

• Shared OCP —The OCP adapter card

LOM ports are used to access Cisco IMC.

You must select either the Active-Active or Active-standby NIC redundancy setting in the following step.

• Shared OCP Extended —In this NIC mode, DHCP replies are returned to both the OCP adapter card LOM ports and the

Cisco virtual interface card (VIC) ports. If the system determines that the Cisco VIC connection is not getting its IP address from a Cisco UCS Manager system because the server is in standalone mode, further DHCP requests from the Cisco VIC are disabled.

Note Shared OCP and Shared OCP

Extended ports are available only on Cisco UCS C225 M6 and C245 M6 servers.

Default NIC Mode Setting :

• For UCS C-Series C125 M5 servers and

S3260 servers, the NIC Mode is set to

Cisco Card by default.

• For UCS C-Series C225 M6 and C245 M6 servers:

• if the server has a Cisco VIC card with OCP card, then the default NIC mode is Shared OCP Extended and

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

131

Configuring Network-Related Settings

Configuring Server NICs

Command or Action Purpose

NIC Redundancy is set to active-active .

• if the server has VIC card populated in NCSI supported slots and no OCP card, then the default NIC mode is

Cisco Card .

• if the server does not have any VIC card and OCP card, the default NIC mode is Dedicated and NIC

Redundancy is set to None .

Step 4 Server /cimc/network # set vic-slot { none | riser1 | riser2 | mlom }

VIC slot can be set to Cisco cards available in

MLOM or supported Risers.

For C240 M6 and C245 M6, VIC slot options are as follows:

• Riser 1 —Slot 1 and Slot 2

• Riser 2 —Slot 4 and Slot 5

• mLOM

Note For C240 M6 and C245 M6, after resetting to factory default settings, the slot precedence is as follows: a.

mLOM b.

Riser 1 - Slot 2; and Riser 2 -

Slot 5 c.

Riser 1 - Slot 1; and Riser 2-

Slot 4

For C220 M6 and C225 M6, VIC slot options are as follows:

• Riser 1 —Slot 1 is selected.

• Riser 3 —Slot 3 is selected.

• mLOM

Note For C220 M6 and C225 M6, after resetting to factory default settings, the slot precedence is as follows: a.

mLOM b.

Riser 1 - Slot 1 c.

Riser 3 - Slot 3

132

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

Configuring Network-Related Settings

Command or Action

Configuring Server NICs

Purpose

For C125 M5, VIC slot option is Riser 2 .

For C220 M4, C220 M5 and C240 M5 servers,

VIC slot options are as follows:

• Riser 1 —Slot 1 is selected.

• Riser 2 —Slot 2 is selected.

• FLEX LOM —Slot 3 (MLOM) is selected.

For C240 SD M5 servers, VIC slot options are as follows:

• For servers with PCIe Riser 1 and 2B combination:

• If you select Riser1, you must install the VIC in slot 2.

• If you select Riser2, you must install the VIC in slot 5.

• For servers with PCIe Riser 1C and 2E combination:

• If you select Riser1, you must install the VIC in slot 1.

• If you select Riser2, you must install the VIC in slot 2.

• If you select Flex-LOM, you must install an mLOM-style VIC in the mLOM slot.

For C480 M5 ML servers, Cisco card mode slot is Slot 11 and Slot 12.

The following options are available only on some UCS C-Series servers:

• 4

• 5

• 9

• 10

For C240 M4 servers, VIC slot options are as follows:

• Riser 1 —Slot 2 is the primary slot, but you can also use slot 1.

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

133

Configuring Network-Related Settings

Configuring Server NICs

Step 5

Step 6

Step 7

Command or Action Purpose

• Riser 2 —Slot 5 is the primary slot, but you can also use slot 4.

• FLEX LOM —Slot 7 (MLOM) is selected.

Important VIC slot is applicable for Cisco cards and on some UCS C-Series servers only.

Server /cimc/network # set redundancy { none

| active-active | active-standby }

Sets the NIC redundancy mode when the NIC mode is Shared LOM. The redundancy mode can be one of the following:

• none —The LOM Ethernet ports operate independently and do not fail over if there is a problem.

• active-active —If supported, all LOM

Ethernet ports are utilized.

• active-standby —If one LOM Ethernet port fails, traffic fails over to another LOM port.

Server /cimc/network # commit

At the prompt, enter y to confirm.

Commits the transaction to the system configuration.

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

Configures the server NIC.

Example

This example configures the Cisco IMC network interface: scope cimc

Server /cimc # scope network

Server /cimc/network # set mode cisco_card

Server /cimc/network # set vic-slot <mlom>

Server /cimc/network *# set redundancy <active-active>

Server /cimc/network *# commit

Changes to the network settings will be applied immediately.

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

Do you wish to continue? [y/N] y

Server /cimc/network #

134

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

Configuring Network-Related Settings

Cisco VIC mLOM and OCP Card Replacement Considerations

In Cisco UCS C225 M6 and C245 M6 servers, Cisco IMC network connection may be lost in the following situations, while replacing Cisco VIC mLOM and OCP cards:

• If OCP card is replaced by Cisco VIC card in MLOM Slot and the NIC mode is set to Shared OCP or

Shared OCP Extended .

• If Cisco VIC Card in MLOM Slot is replaced by OCP Card and NIC mode is set to Cisco-card MLOM .

Follow these recommendations while replacing Cisco VIC mLOM or OCP cards in Cisco UCS C225 M6 or

C245 M6 servers to avoid loss of connectivity:

• Before replacing the card, configure any of the NIC modes that has network connected, other than Cisco card MLOM , Shared OCP , or Shared OCP Extended . After replacing the card, configure the appropriate NIC mode.

To set the NIC mode, refer Server NIC Configuration section in Configuration Guides for your Cisco

IMC release.

• Or, after replacing the card, configure the appropriate NIC mode using Cisco IMC Configuration Utility/F8.

Refer Connecting to the Server Locally For Setup section in Install and Upgrade Guides for your server.

• Or, after replacing the card, perform factory default settings using Cisco IMC Configuration Utility/F8 then perform the following steps:

Once the server is rebooted, boot the system to Cisco IMC Configuration Utility/F8 then change the default password.

Configure the appropriate NIC mode settings.

Table 2: Factory Default Settings

VIC in mLOM slot

Yes

Intel OCP 3.0 NIC in mLOM Slot

VIC in Riser Slot

No No

Yes

Dedicated

Management Port

Yes

NIC Mode for CIMC

Access

Cisco Card mode with the card in mLOM Slot

Shared OCP

Extended

Shared OCP

Extended

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

135

Configuring Network-Related Settings

Common Properties Configuration

VIC in mLOM slot

Intel OCP 3.0 NIC in mLOM Slot

VIC in Riser Slot

No Yes

No No No

Dedicated

Management Port

Yes

NIC Mode for CIMC

Access

Cisco Card with

VIC SLOT based on precedence:

For C225 M6:

Riser 1 - Slot 1

Riser 3 - Slot 3

For C245 M6:

Riser 1 - Slot 2

Riser 2 - Slot 5

Riser 1 - Slot 1

Riser 2 - Slot 4

Yes Dedicated

Common Properties Configuration

Overview to Common Properties Configuration

Hostname

The Dynamic Host Configuration Protocol (DHCP) enhancement is available with the addition of the hostname to the DHCP packet, which can either be interpreted or displayed at the DHCP server side. The hostname, which is now added to the options field of the DHCP packet, sent in the DHCP DISCOVER packet that was initially sent to the DHCP server.

The default hostname of the server is changed from ucs-c2XX to CXXX-YYYYYY, where XXX is the model number and YYYYYY is the serial number of the server. This unique string acts as a client identifier, allows you to track and map the IP addresses that are leased out to Cisco IMC from the DHCP server. The default serial number is provided by the manufacturer as a sticker or label on the server to help you identify the server.

Dynamic DNS

Dynamic DNS (DDNS) is used to add or update the resource records on the DNS server from Cisco IMC.

You can enable Dynamic DNS by using either the web UI or CLI. When you enable the DDNS option, the

DDNS service records the current hostname, domain name, and the management IP address and updates the resource records in the DNS server from Cisco IMC.

136

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

Configuring Network-Related Settings

Configuring Common Properties

Note The DDNS server deletes the prior resource records (if any) and adds the new resource records to the DNS server if any one of the following DNS configuration is changed:

• Hostname

• Domain name in the LDAP settings

• When DDNS and DHCP are enabled, if the DHCP gets a new IP address or DNS IP or domain name due to a change in a network or a subnet.

• When DHCP is disabled and if you set the static IP address by using CLI or web UI.

• When you enter the dns-use-dhcp command.

Dynamic DNS Update Domain — You can specify the domain. The domain could be either main domain or any sub-domain. This domain name is appended to the hostname of the Cisco IMC for the DDNS update.

Configuring Common Properties

Use common properties to describe your server.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set hostname host-name

(Optional) Server /cimc/network # set ddns-enabled

(Optional) Server /cimc/network # set

ddns-update-domain value

Purpose

Enters Cisco IMC command mode.

Enters Cisco IMC network command mode.

Specifies the name of the host.

When you modify the hostname, you are prompted to confirm whether you want to create a new self-signed certificate with Common

Name (CN) as the new hostname.

If you enter y at the prompt, a new self-signed certificate is created with CN as the new hostname.

If you enter n at the prompt, only the hostname is changed and no certificate will be generated.

Enables the DDNS service for Cisco IMC

Updates the selected domain or its subdomain.

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

137

Configuring Network-Related Settings

Configuring IPv4

Step 6

Command or Action

Server /cimc/network # commit

Step 7 At the prompt, enter y to confirm.

Purpose

Commits the transaction to the system configuration.

Configures common properties.

Example

This example shows how to configure the common properties:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set hostname Server

Create new certificate with CN as new hostname? [y|N] y

New certificate will be generated on committing changes.

All HTTPS and SSH sessions will be disconnected.

Server /cimc/network # set ddns-enabled

Server /cimc/network # set ddns-update-domain 1.2.3.4

Server /cimc/network *# commit

Changes to the network settings will be applied immediately.

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

Do you wish to continue? [y/N] y

Server /cimc/network #

What to do next

Changes to the network are applied immediately. You might lose connectivity to Cisco IMC and have to log in again. Because of the new SSH session created, you may be prompted to confirm the host key.

Configuring IPv4

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope cimc

Server /cimc # scope network

Purpose

Enters the Cisco IMC command mode.

Enters the Cisco IMC network command mode.

138

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

Configuring Network-Related Settings

Configuring IPv4

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12

Command or Action

Server /cimc/network # set dhcp-enabled

{ yes | no }

Purpose

Selects whether the Cisco IMC uses DHCP.

Note If DHCP is enabled, we recommend that the DHCP server be configured to reserve a single IP address for the Cisco IMC. If the Cisco IMC is reachable through multiple ports on the server, the single IP address must be reserved for the full range of MAC addresses of those ports.

Server /cimc/network # set v4-addr ipv4-address

Server /cimc/network # set v4-netmask ipv4-netmask

Specifies the IP address for the Cisco IMC.

Specifies the subnet mask for the IP address.

Server /cimc/network # set v4-gateway gateway-ipv4-address

Specifies the gateway for the IP address.

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

| no }

Selects whether the Cisco IMC retrieves the

DNS server addresses from DHCP.

Server /cimc/network #

Server /cimc/network # set

preferred-dns-server dns1-ipv4-address set

alternate-dns-server dns2-ipv4-address

Server /cimc/network # commit

Specifies the IP address of the primary DNS server.

Specifies the IP address of the secondary DNS server.

At the prompt, enter y

Server /cimc/network # to confirm.

show [ detail ]

Commits the transaction to the system configuration.

Configures IPv4.

(Optional) Displays the IPv4 network settings.

Example

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

Changes to the network settings will be applied immediately.

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

Do you wish to continue? [y/N] y

Server /cimc/network # show detail

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

139

Configuring Network-Related Settings

Configuring IPv6

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

IPv6 Enabled: no

IPv6 Address: ::

IPv6 Prefix: 64

IPv6 Gateway: ::

IPv6 Link Local: ::

IPv6 SLAAC Address: ::

IPV6 DHCP Enabled: no

IPV6 Obtain DNS Server by DHCP: no

IPV6 Preferred DNS: ::

IPV6 Alternate DNS: ::

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Port Profile:

Hostname: C240-FCH1938V17L

MAC Address: E4:AA:5D:AD:19:81

NIC Mode: shared_lom_ext

NIC Redundancy: active-active

VIC Slot: riser1

Auto Negotiate: no

Admin Network Speed: NA

Admin Duplex: NA

Operational Network Speed: NA

Operational Duplex: NA

Server /cimc/network #

Configuring IPv6

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope cimc

Purpose

Enters the Cisco IMC command mode.

Server /cimc # scope network Enters the Cisco IMC network command mode.

Server /cimc/network # set v6-enabled { yes

| no }

Enables IPv6.

140

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

Configuring Network-Related Settings

Configuring IPv6

Step 5

Step 6

Step 7

Step 8

Step 4

Step 9

Step 10

Step 11

Step 12

Step 13

Command or Action Purpose

Server /cimc/network # set v6-dhcp-enabled

{ yes | no }

Selects whether the Cisco IMC uses DHCP.

Note If DHCP is enabled, we recommend that the DHCP server be configured to reserve a single IPv6 address for the Cisco IMC. If the Cisco IMC is reachable through multiple ports on the server, the single IPv6 address must be reserved for the full range of MAC addresses of those ports.

Server /cimc/network # set v6-addr ipv6-address

Server /cimc/network # set v6-prefix ipv6-prefix-length

Specifies the IP address for the Cisco IMC.

Specifies the prefix length for the IP address.

Server /cimc/network # set v6-gateway gateway-ipv6-address

Specifies the gateway for the IP address.

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

{ yes | no }

Selects whether the Cisco IMC retrieves the

DNS server addresses from DHCP.

Note You can use this option only when

DHCP enabled.

Server /cimc/network # set

v6-preferred-dns-server dns1-ipv6-address

Specifies the IP address of the primary DNS server.

Server /cimc/network # set

v6-alternate-dns-server dns2-ipv6-address

Server /cimc/network # commit

Specifies the IP address of the secondary DNS server.

Commits the transaction to the system configuration.

At the prompt, enter y to confirm.

Server /cimc/network # show [ detail ]

Configures IPv6.

(Optional) Displays the IPv6 network settings.

Example

This example enables static IPv6 and displays the IPv6 network settings:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set v6-enabled yes

Server /cimc/network *# set v6-addr 2010:201::279

Server /cimc/network *# set v6-gateway 2010:201::1

Server /cimc/network *# set v6-prefix 64

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

Server /cimc/network *# set v6-preferred-dns-server 2010:201::100

Server /cimc/network *# set v6-alternate-dns-server 2010:201::101

Changes to the network settings will be applied immediately.

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

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

141

Configuring Network-Related Settings

Configuring IPv6

Server /cimc/network *# commit

Changes to the network settings will be applied immediately.

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

Do you wish to continue? [y/N] y

Server /cimc/network # show detail

Network Setting:

IPv4 Enabled: yes

IPv4 Address: 10.106.145.76

IPv4 Netmask: 255.255.255.0

IPv4 Gateway: 10.106.145.1

DHCP Enabled: yes

DDNS Enabled: yes

DDNS Update Domain: example.com

Obtain DNS Server by DHCP: no

Preferred DNS: 171.70.168.183

Alternate DNS: 0.0.0.0

IPv6 Enabled: yes

IPv6 Address: 2010:201::279

IPv6 Prefix: 64

IPv6 Gateway: 2010:201::1

IPv6 Link Local: fe80::523d:e5ff:fe9d:395d

IPv6 SLAAC Address: 2010:201::523d:e5ff:fe9d:395d

IPV6 DHCP Enabled: no

IPV6 Obtain DNS Server by DHCP: no

IPV6 Preferred DNS: 2010:201::100

IPV6 Alternate DNS: 2010:201::101

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Port Profile:

Hostname: CIMC_C220

MAC Address: 50:3D:E5:9D:39:5C

NIC Mode: dedicated

NIC Redundancy: none

Network Speed: 100Mbps

Duplex: full

Auto Negotiate: no

Admin Network Speed: NA

Admin Duplex: NA

Operational Network Speed: NA

Operational Duplex: NA

Server /cimc/network #

This example enables DHCP for IPv6 and displays the IPv6 network settings:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set v6-enabled yes

Server /cimc/network *# set v6-dhcp-enabled yes

Changes to the network settings will be applied immediately.

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

Server /cimc/network *# commit

Changes to the network settings will be applied immediately.

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

Do you wish to continue? [y/N] y

Server /cimc/network # show detail

Network Setting:

IPv4 Enabled: yes

IPv4 Address: 10.106.145.76

IPv4 Netmask: 255.255.255.0

IPv4 Gateway: 10.106.145.1

DHCP Enabled: yes

DDNS Enabled: yes

142

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

Configuring Network-Related Settings

Configuring ICMP

DDNS Update Domain: example.com

Obtain DNS Server by DHCP: no

Preferred DNS: 171.70.168.183

Alternate DNS: 0.0.0.0

IPv6 Enabled: yes

IPv6 Address: 2010:201::253

IPv6 Prefix: 64

IPv6 Gateway: fe80::222:dff:fec2:8000

IPv6 Link Local: fe80::523d:e5ff:fe9d:395d

IPv6 SLAAC Address: 2010:201::523d:e5ff:fe9d:395d

IPV6 DHCP Enabled: yes

IPV6 Obtain DNS Server by DHCP: no

IPV6 Preferred DNS: ::

IPV6 Alternate DNS: ::

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Port Profile:

Hostname: CIMC_C220

MAC Address: 50:3D:E5:9D:39:5C

NIC Mode: dedicated

NIC Redundancy: none

Network Speed: 100Mbps

Duplex: full

Auto Negotiate: no

Admin Network Speed: NA

Admin Duplex: NA

Operational Network Speed: NA

Operational Duplex: NA

Server /cimc/network #

Configuring ICMP

In the release 4.1(3b), Cisco IMC allows you to enable or disable processing of incoming ICMP redirect and destination unreachable packets on BMC.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope cimc

Server /cimc # scope network

Purpose

Enters the Cisco IMC command mode.

Enters the Cisco IMC network command mode.

Server /cimc/network # scope icmp-configuration

Server /cimc/network/icmp-configuration # show-detail

Enters the ICMP configuration mode.

Displays the ICMP configuration settings.

Server /cimc/network/icmp-configuration # set destination-unreachable-enabled yes

Enables the Destination Unreachable configuration setting in ICMP.

Server /cimc/network/icmp-configuration # set redirect-enabled yes

Enables the redirect configuration setting in

ICMP.

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

143

Configuring Network-Related Settings

Configuring the Server VLAN

Step 7

Step 8

Command or Action

Server /cimc/network/icmp-configuration # commit

Server /cimc/network/icmp-configuration # show-detail

Purpose

Commits the transaction to the system configuration.

Displays the updated ICMP configuration settings.

Example

This example shows how to configure the ICMP configuration settings:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # scope icmp-configuration

Server /network/icmp-configuration # show detail

ICMP Settings:

Destination Unreachable Enabled: no

Redirect Enabled: no

Server /cimc/network/icmp-configuration # set destination-unreachable-enabled yes

Server /cimc/network/icmp-configuration # set redirect yes

Server /cimc/network/icmp-configuration # commit

Server /cimc/network/icmp-configuration # show detail

ICMP Settings:

Destination Unreachable Enabled: yes

Redirect Enabled: yes

Server /cimc/network/icmp-configuration #

Configuring the Server VLAN

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope cimc

Purpose

Enters the Cisco IMC command mode.

Server /cimc # scope network Enters the Cisco IMC network command mode.

Server /cimc/network # set vlan-enabled { yes

| no }

Selects whether the Cisco IMC is connected to a VLAN.

Specifies the VLAN number.

Server /cimc/network # set vlan-id id

Server /cimc/network # set vlan-priority priority

Server /cimc/network # commit

Specifies the priority of this system on the

VLAN.

Commits the transaction to the system configuration.

144

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

Configuring Network-Related Settings

Configuring the Server VLAN

Step 7

Step 8

Command or Action

At the prompt, enter y to confirm.

Server /cimc/network # show [ detail ]

Purpose

Configures the server LAN.

(Optional) Displays the network settings.

Example

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

Changes to the network settings will be applied immediately.

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

Do you wish to continue? [y/N] y

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

IPv6 Enabled: no

IPv6 Address: ::

IPv6 Prefix: 64

IPv6 Gateway: ::

IPv6 Link Local: ::

IPv6 SLAAC Address: ::

IPV6 DHCP Enabled: no

IPV6 Obtain DNS Server by DHCP: no

IPV6 Preferred DNS: ::

IPV6 Alternate DNS: ::

VLAN Enabled: yes

VLAN ID: 10

VLAN Priority: 32

Port Profile:

Hostname: C240-FCH1938V17L

MAC Address: E4:AA:5D:AD:19:81

NIC Mode: shared_lom_ext

NIC Redundancy: active-active

VIC Slot: riser1

Auto Negotiate: no

Admin Network Speed: NA

Admin Duplex: NA

Operational Network Speed: NA

Operational Duplex: NA

Server /cimc/network #

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

145

Configuring Network-Related Settings

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.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set port-profile port_profile_name

Purpose

Enters the Cisco IMC command mode.

Enters the Cisco IMC network command mode.

Specifies the port profile Cisco IMC should use to configure the management interface, the virtual Ethernet, and the VIF on supported adapter cards such as the Cisco UCS VIC 1225

Virtual Interface Card.

Enter up to 80 alphanumeric characters. You cannot use spaces or other special characters except for - (hyphen) and _ (underscore). In addition, the port profile name cannot begin with a hyphen.

Note The port profile must be defined on the switch to which this server is connected.

Step 4

Step 5

Step 6

Server /cimc/network # commit

At the prompt, enter y to confirm.

(Optional) Server /cimc/network # show

[ detail ]

Commits the transaction to the system configuration.

Connects to a port profile.

Displays the network settings.

Example

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

146

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

Configuring Network-Related Settings

Network Interface Configuration

Changes to the network settings will be applied immediately.

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

Do you wish to continue? [y/N] y

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

IPv6 Enabled: no

IPv6 Address: ::

IPv6 Prefix: 64

IPv6 Gateway: ::

IPv6 Link Local: ::

IPv6 SLAAC Address: ::

IPV6 DHCP Enabled: no

IPV6 Obtain DNS Server by DHCP: no

IPV6 Preferred DNS: ::

IPV6 Alternate DNS: ::

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Port Profile: abcde12345

Hostname: C240-FCH1938V17L

MAC Address: E4:AA:5D:AD:19:81

NIC Mode: shared_lom_ext

NIC Redundancy: active-active

VIC Slot: riser1

Auto Negotiate: no

Admin Network Speed: NA

Admin Duplex: NA

Operational Network Speed: NA

Operational Duplex: NA

Server /cimc/network #

Network Interface Configuration

Overview to Network Interface Configuration

This support is added to configure network speed and duplex mode for the Cisco IMC management port. Auto

Negotiation mode can be set for dedicated mode only. When auto negotiation is enabled the network port speed and duplex settings are ignored by the system and Cisco IMC retains the speed at which the switch is configured. When auto negotiation is disabled, you can configure the network port speed (10 Mbps, 100 Mbps, or 1 Gbps) and set the duplex value at either full or half.

Port Properties can be managed in the following two modes:

• Admin Mode —You can configure the network speed and duplex values by disabling the Auto Negotiation option. The default value of the network speed in the admin mode is 100 Mbps and the duplex mode is set to Full. Before changing the network speed ensure that the switch you connected to has the same port speed.

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

147

Configuring Network-Related Settings

Configuring Interface Properties

• Operation Mode —Displays the operation network port speed and duplex values. If you enabled auto negotiation mode, the network port speed and duplex details of the switch are displayed. If unchecked, the network port speed and duplex values that you set at the Admin Mode are displayed.

When you reset Cisco IMC 1.5(x), 2.0(1), and 2.0(3) versions to factory defaults, Shared LOM mode is configured by default.

Configuring Interface Properties

The settings on the switch must match with the Cisco IMC settings to avoid any speed or duplex mismatch.

Important This action is available only on some UCS C-Series servers.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server # scope cimc

Purpose

Enters the Cisco IMC command mode.

Server/cimc # scope network

Server/cimc/network* # set mode dedicated

Enters the network command mode.

Enters dedicated command mode.

Server/cimc/network # set auto-negotiate { yes

| no }

Enables or disables auto negotiation command mode.

• If you enter yes , the network port speed and duplex settings are ignored by the system and Cisco IMC retains the speed at which the switch is configured.

• If you enter no , you can configure the network port speed and duplex values.

Server/cimc/network # set net-speed { 10 Mbps

| 100 Mbps | 1 Gbps }

Sets specified network port speed.

Note This option is available only if auto-negotiate is set to no . Before changing the port speed, ensure that the switch you connected to has the same port speed. When auto-negotiate is set to yes , by default the network port speed is set to 100 Mbps.

Server/cimc/network* # set duplex { full | half } Sets specified duplex mode type. By default, the duplex mode is set to Full .

Note For network speed of 1 Gbps, only full duplex mode is allowed.

148

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

Configuring Network-Related Settings

Network Security Configuration

Step 7

Command or Action

Server/cimc/network* # commit

Purpose

Commits the transaction to the system.

Example

This example shows how to configure the interface properties and commit the transaction:

Server # scope cimc

Server/cimc # scope network

Server/cimc/network* # set mode dedicated

Server/cimc/network # set auto-negotiate no

Warning: You have chosen to set auto-negotiate to no

Please set speed and duplex

If not set then a default speed of 100Mbps and duplex full will be applied

Server/cimc/network* # commit

Server/cimc/network* # set net-speed 100 Mbps

Server/cimc/network # set duplex full

Server/cimc/network* # commit

Changes to the network settings will be applied immediately.

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

Do you wish to continue? [y/N] y

Server/cimc/network #

Network Security Configuration

Network Security

The Cisco IMC 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. Cisco IMC 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

Step 1

Step 2

Command or Action

Server# scope cimc

Server /cimc # scope network

Purpose

Enters the Cisco IMC command mode.

Enters the Cisco IMC network command mode.

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

149

Configuring Network-Related Settings

Configuring Network Security

Step 8

Step 9

Step 10

Step 11

Step 12

Step 3

Step 4

Step 5

Step 6

Step 7

Step 13

Command or Action

Server /cimc/network # scope ipblocking

Server /cimc/network/ipblocking # set enabled { yes | no }

Server /cimc/network/ipblocking # set

fail-count fail-count

Purpose

Enters the IP blocking command mode.

Enables or disables IP blocking.

Server /cimc/network/ipblocking #

fail-window fail-seconds

Server /cimc/network/ipblocking #

penalty-time penalty-seconds set set

Sets the number of times a user can attempt to log in unsuccessfully before the system locks that user out for a specified length of time.

The number of unsuccessful login attempts must occur within the time frame specified in the IP Blocking Fail Window field.

Enter an integer between 3 and 10.

Sets the length of time, in seconds, in which the unsuccessful login attempts must occur in order for the user to be locked out.

Enter an integer between 60 and 120.

Sets the number of seconds the user remains locked out if they exceed the maximum number of login attempts within the specified time window.

Enter an integer between 300 and 900.

Server /cimc/network/ipblocking # commit Commits the transaction to the system configuration.

Server /cimc/network/ipblocking # exit Exits the IP blocking to the network command mode.

Enters the IP filtering command mode.

Server /cimc/network # scope ipfiltering

Server /cimc/network/ipfiltering # set enabled

{ yes | no }

Enables or disables IP filtering. At the prompt enter y to enable IP filtering.

Server /cimc/network/ipfiltering # set filter-1

IPv4 or IPv6 address or a range of IP addresses

You can set four IP filters. You can assign an

IPv4 or IPv6 IP address or a range of IP addresses.

Server /cimc/network/ipfiltering # commit Commits the transaction to the system configuration.

Example

This example configures network security:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # scope ipblocking

Server /cimc/network/ipblocking # set enabled yes

150

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

Configuring Network-Related Settings

Network Time Protocol Configuration

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 # exit

Server /cimc/network # scope ipfiltering

Server /cimc/network/ipfiltering # set enabled yes

This will enable IP Filtering

Do you wish to continue? [y/N] y

Server /cimc/network/ipfiltering *# set filter-1 1.1.1.1-255.255.255.255

set filter-2 10.10.10.10

set filter-3 2001:xxx::-2xxx:xx8::0001 set filter-4

2001:xxx::-2xxx:xx8::0001-2001:xxx::-2xxx:xx8::0020

Server /cimc/network/ipfiltering *# commit

Changes to the ipfiltering will be applied immediately.

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

Do you wish to continue? [y/N] Y

Network Time Protocol Configuration

Configuring Network Time Protocol Settings

By default, when Cisco IMC is reset, it synchronizes the time with the host. With the introduction of the NTP service, you can configure Cisco IMC to synchronize the time with an NTP server. The NTP server does not run in Cisco IMC 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, Cisco IMC synchronizes the time with the configured NTP server. The

NTP service can be modified only through Cisco IMC.

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

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # scope ntp

Server /cimc/network/ntp # set enabled yes

Server /cimc/network/ntp* # commit

Purpose

Enters the Cisco IMC command mode.

Enters network command mode.

Enters NTP service command mode.

Enables the NTP service on the server.

Commits the transaction.

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

151

Configuring Network-Related Settings

Pinging an IP address

Step 6

Step 7

Step 8

Step 9

Step 10

Command or Action

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

10.120.33.44

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

10.120.34.45

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

10.120.35.46

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

10.120.36.48

Server /cimc/network/ntp # commit

Purpose

Specifies the IP/DNS address of one of the four servers that act as an NTP server or the time source server.

Commits the transaction.

Example

This example shows how to configure the NTP service:

Server # scope cimc

Server /cimc # scope network

Server /cimc/network # scope ntp

Server /cimc/network/ntp # set enabled yes

Warning: IPMI Set SEL Time Command will be disabled if NTP is enabled.

Do you wish to continue? [y|N] y

Server /cimc/network/ntp* # commit

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

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

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

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

Server /cimc/network/ntp* # commit

Server /cimc/network/ntp #

Pinging an IP address

Ping an IP address when you want to validate network connectivity with the IP address in the Cisco IMC.

Before you begin

You must log in as a user with administration privileges to ping an IP address.

Procedure

Step 1

Command or Action

Server# scope cimc

Purpose

Enters the CIMC command mode.

152

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

Configuring Network-Related Settings

Pinging an IP address

Step 2

Step 3

Command or Action

Server /cimc # scope network

Server /cimc /network# ping IP address |

retriesnumber | timeoutseconds

Step 4

Step 5

Server /cimc/network #

At the prompt, enter y commit to confirm.

Purpose

Enters the CIMC network command mode.

Pings the IP address or host name for a specified number of times until timeout.

• IP address/hostname - The IP address or the host name of the server.

• Number of retries - The number of times the system tries to connect to the server.

Default value is 3. Valid range is from 1 to 10.

• Timeout - The number of seconds the system waits before it stops pinging.

Default maximum value is 20 seconds.

Valid range is from 1 to 20 seconds.

Commits the transaction to the system configuration.

Pings the IP address.

Example

This example pings an IP address:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # ping 10.10.10.10

Server /cimc/network *# commit

Changes to the network settings will be applied immediately.

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

Do you wish to continue? [y/N] y

Server /cimc/network #

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

153

Pinging an IP address

Configuring Network-Related Settings

154

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

C H A P T E R

Managing Network Adapters

This chapter includes the following sections:

•

Overview of the Cisco UCS C-Series Network Adapters, on page 155

•

Viewing Network Adapter Properties, on page 157

•

Configuring Network Adapter Properties, on page 158

•

Managing vHBAs, on page 161

•

Managing vNICs, on page 175

•

Backing Up and Restoring the Adapter Configuration, on page 202

•

Managing Adapter Firmware, on page 205

•

Resetting the Adapter, on page 207

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 VIC 1225 Virtual Interface Card

• Cisco UCS VIC 1227T Virtual Interface Card

• Cisco UCS VIC 1385 Virtual Interface Card

• Cisco UCS VIC 1387 Virtual Interface Card

• Cisco UCS VIC 1455 Virtual Interface Card

• Cisco UCS VIC 1457 Virtual Interface Card

• Cisco UCS VIC 1495 Virtual Interface Card

• Cisco UCS VIC 1497 Virtual Interface Card

• Cisco UCS VIC 1467 Virtual Interface Card

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

155

Managing Network Adapters

Overview of the Cisco UCS C-Series Network Adapters

• Cisco UCS VIC 1477 Virtual Interface Card

Note You must have same generation VIC cards on a server. For example, you cannot have a combination of 3rd generation and 4th generation VIC cards on a single server.

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 VIC 1225 Virtual Interface Card

The Cisco UCS VIC 1225 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.

Cisco UCS VIC 1385 Virtual Interface Card

The Cisco UCS VIC 1385 Virtual Interface Cardis a dual-port Enhanced Quad Small Form-Factor Pluggable

(QSFP) 40 Gigabit Ethernet and Fibre Channel over Ethernet (FCoE)-capable half-height PCI Express (PCIe) card designed exclusively for Cisco UCS C-Series Rack Servers. It incorporates Cisco’s next-generation converged network adapter (CNA) technology, with a comprehensive feature set, providing investment protection for future feature software releases.

Cisco UCS VIC 1227T Virtual Interface Card

The Cisco UCS VIC 1227T Virtual Interface Card is a dual-port 10GBASE-T (RJ-45) 10-Gbps Ethernet and

Fibre Channel over Ethernet (FCoE)–capable PCI Express (PCIe) modular LAN-on-motherboard (mLOM) adapter designed exclusively for Cisco UCS C-Series Rack Servers. New to Cisco rack servers, the mLOM slot can be used to install a Cisco VIC without consuming a PCIe slot, which provides greater I/O expandability.

It incorporates next-generation converged network adapter (CNA) technology from Cisco, providing Fibre

Channel connectivity over low-cost twisted pair cabling with a bit error rate (BER) of 10 to 15 up to 30 meters and investment protection for future feature releases.

Cisco UCS VIC 1387 Virtual Interface Card

The Cisco UCS VIC 1387 Virtual Interface Card is a dual-port Enhanced Quad Small Form-Factor Pluggable

Cisco UCS VIC 1455 Virtual Interface Card

The Cisco UCS VIC 1455 is a quad-port Small Form-Factor Pluggable (SFP28) half-height PCIe card designed for M5 generation of Cisco UCS C-Series rack servers. The card supports 10/25-Gbps Ethernet or FCoE. It incorporates Cisco’s next-generation CNA technology and offers a comprehensive feature set, providing investment protection for future feature software releases. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs and HBAs.

156

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

Managing Network Adapters

Viewing Network Adapter Properties

Cisco UCS VIC 1457 Virtual Interface Card

The Cisco UCS VIC 1457 is a quad-port Small Form-Factor Pluggable (SFP28) mLOM card designed for

M5 generation of Cisco UCS C-Series rack servers. The card supports 10/25-Gbps Ethernet or FCoE. It incorporates Cisco’s next-generation CNA technology and offers a comprehensive feature set, providing investment protection for future feature software releases. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs and HBAs.

Cisco UCS VIC 1495 Virtual Interface Card

The Cisco UCS VIC 1495 is a dual-port Small Form-Factor (QSFP28) PCIe card designed for the M5 generation of Cisco UCS C-Series Rack Servers. The card supports 40/100-Gbps Ethernet and FCoE. The card can present

PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs and HBAs.

Cisco UCS VIC 1497 Virtual Interface Card

The Cisco VIC 1497 is a dual-port Small Form-Factor (QSFP28) mLOM card designed for the M5 generation of Cisco UCS C-Series Rack Servers. The card supports 40/100-Gbps Ethernet and FCoE. The card can present

PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs and HBAs.

Cisco UCS VIC 1467 Virtual Interface Card

The Cisco UCS VIC 1467 is a quad-port Small Form-Factor Pluggable (SFP28) mLOM card designed for the M6 generation of Cisco UCS C-Series Rack Servers. The card supports 10/25-Gbps Ethernet or FCoE.

The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as either NICs or HBA.

Cisco UCS VIC 1477 Virtual Interface Card

The Cisco VIC 1477 is a dual-port Quad Small Form-Factor (QSFP28) mLOM card designed for the M6 generation of Cisco UCS C-Series Rack Servers. The card supports 40/100-Gbps Ethernet or FCoE. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs or HBAs.

Viewing Network Adapter Properties

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # show adapter [ index ] [ detail ] Displays adapter properties. To display the properties of a single adapter, specify the PCI slot number as the index argument.

Example

• This example displays the properties of adapter:

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

157

Managing Network Adapters

Configuring Network Adapter Properties

Server# scope chassis

Server /chassis # show adapter

PCI Slot Product Name Serial Number Product ID Vendor

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

11 UCS VIC 1455 FCH233770S8 UCSC-PCIE-C... Cisco Systems Inc

Server /chassis # show adapter detail

PCI Slot 11:

Product Name: UCS VIC 1455

Serial Number: FCH233770S8

Product ID: UCSC-PCIE-C25Q-04

Adapter Hardware Revision: 5

Current FW Version: 5.1(1.64)

VNTAG: Disabled

FIP: Enabled

LLDP: Enabled

PORT CHANNEL: Enabled

Configuration Pending: no

Cisco IMC Management Enabled: no

VID: V04

Vendor: Cisco Systems Inc

Description:

Bootloader Version: 5.0(3c)

FW Image 1 Version: 5.1(1.64)

FW Image 1 State: RUNNING ACTIVATED

FW Image 2 Version: 5.1(1.59)

FW Image 2 State: BACKUP INACTIVATED

FW Update Status: Fwupdate never issued

FW Update Error: No error

FW Update Stage: No operation (0%)

FW Update Overall Progress: 0%

Server /chassis #

Configuring Network Adapter Properties

Before you begin

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

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show adapter

Step 3 Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

(Optional) Displays the available adapter devices.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

158

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

Managing Network Adapters

Configuring Network Adapter Properties

Step 4

Command or Action Purpose

Server /chassis/adapter # set fip-mode { disable

| enable }

Enables or disables FCoE Initialization Protocol

(FIP) on the adapter card. FIP is enabled by default.

Note • We recommend that you disable this option only when explicitly directed to do so by a technical support representative.

Step 5

Step 6

Step 7

Server /chassis/adapter # set lldp { disable | enable }

Note For LLDP change to be effective, it is required that you reboot the server.

In case of S3260 chassis with two nodes, ensure to reboot the secondary node after making LLDP changes in the primary node.

Enables or disables Link Layer Discovery

Protocol (LLDP) on the adapter card. LLDP is enabled by default.

Note We recommend that you do not disable LLDP option, as it disables all the Data Center Bridging

Capability Exchange protocol

(DCBX) functionality.

Server /chassis/adapter # set vntag-mode

{ disabled | enabled }

Server /chassis/adapter # disabled set portchannel

Enables or disables VNTAG on the adapter card. VNTAG is disabled by default.

Note

If VNTAG mode is enabled:

• vNICs and vHBAs can be assigned to a specific channel.

• vNICs and vHBAs can be associated to a port profile.

• vNICs can fail over to another vNIC if there are communication problems.

Allows you to enable or disable the port channel. When you disable port channel, four vNICs and vHBAs are available for use on the adapter.

When Port channel is enabled:

• Only two vNICs and vHBAs are available for use.

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

159

Managing Network Adapters

Configuring Network Adapter Properties

Step 8

Command or Action

Server /chassis/adapter* # commit

Purpose

• Port 0 and 1 are bundled as one port channel and Port 2 and 3 are bundled as the other port channel.

Note • This option is enabled by default on Cisco UCS VIC

1455 and 1457.

• When you change the port channel configuration, all the previously created vNICs and vHBAs will be deleted and the configuration will be restored to factory defaults.

• VNTAG mode is supported only in the port-channel mode.

Commits the transaction to the system configuration.

Example

This example configures the properties of adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # set fip-mode enable

Server /chassis/adapter *# set vntag-mode enabled

Server /chassis/adapter* # set portchannel disabled

Server /chassis/adapter *# commit

Warning: Enabling VNTAG mode

All the vnic configuration will be reset to factory defaults

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

Server /chassis/adapter # show detail

PCI Slot 1:

Product Name: UCS VIC xxxx

Serial Number: FCHXXXXXZV4

Product ID: UCSC-PCIE-xxx-04

Adapter Hardware Revision: 3

Current FW Version: x.0(0.345)

VNTAG: Enabled

FIP: Enabled

LLDP: Enabled

PORT CHANNEL: Disabled

Configuration Pending: no

Cisco IMC Management Enabled: no

VID: V00

Vendor: Cisco Systems Inc

Description:

Bootloader Version: xxx

FW Image 1 Version: x.0(0.345)

FW Image 1 State: RUNNING ACTIVATED

FW Image 2 Version: gafskl-dev-170717-1500-orosz-ET

FW Image 2 State: BACKUP INACTIVATED

160

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

Managing Network Adapters

Managing vHBAs

FW Update Status: Fwupdate never issued

FW Update Error: No error

FW Update Stage: No operation (0%)

FW Update Overall Progress: 0%

Server /chassis/adapter #

Managing vHBAs

Guidelines for Managing vHBAs

When managing vHBAs, consider the following guidelines and restrictions:

• The Cisco UCS Virtual Interface Cards provide two vHBAs and two vNICs by default. You can create up to 14 additional vHBAs or vNICs on these adapter cards.

The Cisco UCS 1455, 1457, and 1467 Virtual Interface Cards, in non-port channel mode, provide four vHBAs and four vNICs by default. You can create up to 10 additional vHBAs or vNICs on these adapter cards in VNTAG mode.

Note If VNTAG mode is enabled for the adapter, you must assign a channel number to a vHBA when you create it.

• When using the Cisco UCS Virtual Interface Cards in an FCoE application, you must associate the vHBA with the FCoE VLAN. Follow the instructions in the Modifying vHBA Properties section to assign the

VLAN.

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

Viewing vHBA Properties

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

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

| fc1 | name ] [ detail ]

Displays properties of a single vHBA, if specified, or all vHBAs.

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

161

Managing Network Adapters

Modifying vHBA Properties

Example

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

Server# scope chassis

Server /chassis # scope adapter 1

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

Name World Wide Port Name FC SAN Boot Uplink Port

-------- ------------------------ ----------- ----------fc0 fc1

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

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

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

Name fc0:

World Wide Node Name: 10:00:70:0F:6A:C0:97:43

World Wide Port Name: 20:00:70:0F:6A:C0:97:43

FC SAN Boot: disabled

FC Type: fc-initiator

Persistent LUN Binding: disabled

Uplink Port: 0

PCI Link: 0

MAC Address: 70:0F:6A:C0:97:43

CoS: 3

VLAN: NONE

Rate Limiting: OFF

PCIe Device Order: 2

EDTOV: 2000

RATOV: 10000

Maximum Data Field Size: 2112

Channel Number: N/A

Port Profile: N/A

Server /chassis/adapter #

Modifying vHBA Properties

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show adapter

Step 3 Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

(Optional) Displays the available adapter devices.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

162

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

Managing Network Adapters

Modifying vHBA Properties

Step 7

Step 8

Step 9

Step 10

Step 4

Step 5

Step 6

Step 11

Step 12

Step 13

Step 14

Command or Action Purpose

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

| fc1 | name }

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

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

Specifies a unique World Wide Node Name

(WWNN) for the adapter in the form hh:hh:hh:hh:hh:hh:hh:hh.

Unless specified by this command, the WWNN is generated automatically by the system.

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

Specifies a unique World Wide Port Name

(WWPN) for the adapter in the form hh:hh:hh:hh:hh:hh:hh:hh.

Unless specified by this command, the WWPN is generated automatically by the system.

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

{ disable | enable } set boot

Server /chassis/adapter/host-fc-if # set persistent-lun-binding { disable | enable }

Enables or disables FC SAN boot. The default is disable.

Enables or disables persistent LUN binding.

The default is disable.

Specifies a MAC address for the vHBA.

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

mac-addr mac-addr

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

{ none | vlan-id }

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

Specifies the default VLAN for this vHBA.

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

Specifies the class of service (CoS) value to be marked on received packets unless the vHBA is configured to trust host CoS. Valid

CoS values are 0 to 6; the default is 0. Higher values indicate more important traffic.

This setting is not functional in NIV mode.

Server /chassis/adapter/host-fc-if # set rate-limit { off | rate }

Specifies a maximum data rate for the vHBA.

The range is 1 to 100000 Mbps; the default is off.

This setting is not functional in NIV mode.

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

{ any | 0-99 }

Specifies the relative order of this device for

PCIe bus device number assignment; the default is any.

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

error-detect-timeout msec

Specifies the error detect timeout value

(EDTOV), the number of milliseconds to wait before the system assumes that an error has occurred. The range is 1000 to 100000; the default is 2000 milliseconds.

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

163

Managing Network Adapters

Modifying vHBA Properties

Step 15

Step 16

Step 17

Step 18

Step 19

Step 20

Command or Action

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

resource-allocation-timeout msec

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

max-data-field-size size

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

channel-number channel number set set

Purpose

Specifies the resource allocation timeout value

(RATOV), the number of milliseconds to wait before the system assumes that a resource cannot be properly allocated. The range is 5000 to 100000; the default is 10000 milliseconds.

Specifies the maximum size of the Fibre

Channel frame payload (in bytes) that the vHBA supports. The range is 1 to 2112; the default is 2112 bytes.

The channel number that will be assigned to this vHBA. Enter an integer between 1 and

1,000.

Note VNTAG mode is required for this option.

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

0|1

The link through which vNICs can be connected. These are the following values:

• 0 — The first cross-edged link where the vNIC is placed.

• 1 — The second cross-edged link where the vNIC is placed.

Note This option is available only on some Cisco UCS C-Series servers.

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

Port number

The uplink port associated with the vHBA.

Note This value cannot be changed for the system-defined vHBAs fc0 and fc1.

Server /chassis/adapter/host-fc-if # set vhba-type fc-initiator|fc-target|fc-nvme-initiator|fc-nvme-target

The vHBA type used in this policy. vHBAs supporting FC and FC-NVMe can now be created on the same adapter. The vHBA type used in this policy can be one of the following:

• fc-initiator—Legacy SCSI FC vHBA initiator

• fc-target—vHBA that supports SCSI FC target functionality

Note This option is available as a

Tech Preview.

164

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

Managing Network Adapters

Modifying vHBA Properties

Step 21

Step 22

Step 23

Step 24

Step 25

Step 26

Step 27

Step 28

Command or Action Purpose

• fc-nvme-initiator—vHBA that is an FC

NVME initiator, which discovers FC

NVME targets and connects to them.

• fc-nvme-target—vHBA that acts as an

FC NVME target and provides connectivity to the NVME storage.

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

Enters the Fibre Channel error recovery command mode.

Server

/chassis/adapter/host-fc-if/error-recovery # set fcp-error-recovery { disable | enable }

Enables or disables FCP Error Recovery. The default is disable.

Server

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

link-down-timeout msec

Specifies the link down timeout value, the number of milliseconds the uplink port should be offline before it informs the system that the uplink port is down and fabric connectivity has been lost. The range is 0 to 240000; the default is 30000 milliseconds.

Server

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

port-down-io-retry-count count

Specifies the port down I/O retries value, the number of times an I/O request to a port is returned because the port is busy before the system decides the port is unavailable. The range is 0 to 255; the default is 8 retries.

Server

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

port-down-timeout msec

Specifies the port down timeout value, the number of milliseconds a remote Fibre

Channel port should be offline before informing the SCSI upper layer that the port is unavailable. The range is 0 to 240000; the default is 10000 milliseconds.

Server

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

Exits to the host Fibre Channel interface command mode.

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

Server /chassis/adapter/host-fc-if/interrupt # set interrupt-mode { intx | msi | msix }

Enters the interrupt command mode.

Specifies the Fibre Channel interrupt mode.

The modes are as follows:

• intx —Line-based interrupt (INTx)

• msi —Message-Signaled Interrupt (MSI)

• msix —Message Signaled Interrupts with the optional extension (MSIx). This is the recommended and default option.

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

165

Managing Network Adapters

Modifying vHBA Properties

Step 29

Step 30

Step 31

Step 32

Step 33

Step 34

Step 35

Step 36

Step 37

Step 38

Step 39

Step 40

Command or Action

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

Purpose

Exits to the host Fibre Channel interface command mode.

Server /chassis/adapter/host-fc-if # scope port Enters the Fibre Channel port command mode.

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

outstanding-io-count count

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

max-target-luns count set

Specifies the I/O throttle count, the number of

I/O operations that can be pending in the vHBA at one time. The range is 1 to 1024; the default is 512 operations.

Specifies the maximum logical unit numbers

(LUNs) per target, the maximum number of

LUNs that the driver will discover. This is usually an operating system platform limitation. The range is 1 to 1024; the default is 256 LUNs.

Server /chassis/adapter/host-fc-if/port # exit Exits to the host Fibre Channel interface command mode.

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

Enters the Fibre Channel fabric login command mode.

Server /chassis/adapter/host-fc-if/port-f-logi # set flogi-retries { infinite | count }

Specifies the fabric login (FLOGI) retries value, the number of times that the system tries to log in to the fabric after the first failure.

Enter a number between 0 and 4294967295 or enter infinite ; the default is infinite retries.

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

set flogi-timeout msec

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

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

Exits to the host Fibre Channel interface command mode.

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

Enters the Fibre Channel port login command mode.

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

# set plogi-retries count

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

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

# set plogi-timeout msec

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

166

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

Managing Network Adapters

Modifying vHBA Properties

Step 41

Step 42

Step 43

Step 44

Step 45

Step 46

Step 47

Step 48

Step 49

Step 50

Command or Action

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

# exit

Purpose

Exits to the host Fibre Channel interface command mode.

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

Enters the SCSI I/O command mode.

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

cdb-wq-count count

The number of command descriptor block

(CDB) transmit queue resources to allocate.

For Cisco UCS VIC 14xx series adapters, enter an integer between 1 and 64. For any other

VIC adapter, enter an integer between 1 and

245.

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

cdb-wq-ring-size size

The number of descriptors in the command descriptor block (CDB) transmit queue. The range is 64 to 512; the default is 512.

Server /chassis/adapter/host-fc-if/scsi-io # exit Exits to the host Fibre Channel interface command mode.

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

Enters the Fibre Channel transmit queue command mode.

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

# set fc-wq-ring-size size

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

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

# exit

Exits to the host Fibre Channel interface command mode.

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

Enters the Fibre Channel receive queue command mode.

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

# set fc-rq-ring-size size

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

Step 51

Step 52

Step 53

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

# exit

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

Exits to the host Fibre Channel interface command mode.

Commits the transaction to the system configuration.

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

Example

This example configures the properties of a vHBA (only few options are shown):

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

167

Managing Network Adapters

Creating a vHBA

Server# scope chassis

Server /chassis # show adapter

PCI Slot Product Name Serial Number Product ID Vendor

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

1 UCS VIC P81E QCI1417A0QK N2XX-ACPCI01 Cisco Systems Inc

Server /chassis # scope adapter 1

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

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.

Note Additional vHBAs can be created only in VNTAG mode.

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

Step 3

Step 4

Step 5

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

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

channel-number number

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

Creates a vHBA and enters the host Fibre

Channel interface command mode. The name argument can be up to 32 ASCII characters.

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

Commits the transaction to the system configuration.

168

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

Managing Network Adapters

Deleting a vHBA

Command or Action Purpose

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

Example

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 162

Deleting a vHBA

Before you begin

You cannot delete the default vHBAs.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

Server /chassis/adapter # delete host-fc-if name Deletes the specified vHBA.

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

Server /chassis/adapter # commit Commits the transaction to the system configuration.

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

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

169

Managing Network Adapters vHBA Boot Table

Example

This example deletes a vHBA on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

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

Server /chassis/adapter *# commit

Server /chassis/adapter # vHBA Boot Table

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

Viewing the Boot Table

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

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

| fc1 | name }

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

Server /chassis/adapter/host-fc-if # show boot Displays the boot table of the Fibre Channel interface.

Example

This example displays the boot table for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 1

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

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

Boot Table Entry Boot Target WWPN Boot LUN ID

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

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

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

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

170

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

Managing Network Adapters

Creating a Boot Table Entry

You can create up to four boot table entries.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

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

| fc1 | name }

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

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

create-boot-entry wwpn lun-id

Creates a boot table entry.

• wwpn — The World Wide Port Name

(WWPN) for the boot target in the form hh:hh:hh:hh:hh:hh:hh:hh.

• lun-id —The LUN ID of the boot LUN.

The range is 0 to 255.

Server /chassis/adapter/host-fc-if # commit Commits the transaction to the system configuration.

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

Example

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 #

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

171

Managing Network Adapters

Deleting a Boot Table Entry

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

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

| fc1 | name }

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

Server /chassis/adapter/host-fc-if # show boot Displays the boot table. From the Boot Table

Entry field, locate the number of the entry to be deleted.

Server /chassis/adapter/host-fc-if # delete boot entry

Deletes the boot table entry at the specified position in the table. The range of entry is 0 to 3. The change will take effect upon the next server reset.

Server /chassis/adapter/host-fc-if # commit Commits the transaction to the system configuration.

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

Example

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

Server# scope chassis

Server /chassis # scope adapter 1

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

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

Boot Table Entry Boot Target WWPN Boot LUN ID

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

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

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

Server /chassis/adapter/host-fc-if # delete boot 1

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 # show boot

Boot Table Entry Boot Target WWPN Boot LUN ID

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

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

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

172

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

Managing Network Adapters vHBA Persistent Binding

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.

Enabling Persistent Binding

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

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

| fc1 | name }

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

Server /chassis/adapter/host-fc-if # scope perbi Enters the persistent binding command mode for the vHBA.

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

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

Enables persistent binding for the vHBA.

Commits the transaction to the system configuration.

Example

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 #

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

173

Managing Network Adapters

Disabling Persistent Binding

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

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

| fc1 | name }

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

Server /chassis/adapter/host-fc-if # scope perbi Enters the persistent binding command mode for the vHBA.

Disables persistent binding for the vHBA.

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

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

Commits the transaction to the system configuration.

Example

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

Step 1

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

174

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

Managing Network Adapters

Managing vNICs

Step 2

Step 3

Step 4

Step 5

Command or Action

Server /chassis # scope adapter index

Purpose

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

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

| fc1 | name }

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

Server /chassis/adapter/host-fc-if # scope perbi Enters the persistent binding command mode for the vHBA.

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

Rebuilds the persistent binding table for the vHBA.

Example

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 Virtual Interface Cards provide two vHBAs and two vNICs by default. You can create up to 14 additional vHBAs or vNICs on these adapter cards.

Additional vHBAs can be created using VNTAG mode.

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

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

175

Managing Network Adapters

Viewing vNIC Properties

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

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

| eth1 | name ] [ detail ]

Displays properties of a single vNIC, if specified, or all vNICs.

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

[ detail ]

Displays the external ethernet interfaces' details.

Example

Following examples display the brief properties of all vNICs and the detailed properties of eth0 and the external interfaces:

Note These examples may show features available only with certain releases.

Server# scope chassis

Server /chassis # scope adapter 1

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

Name MTU Uplink Port MAC Address CoS VLAN PXE Boot iSCSI Boot usNIC

----- ----- ---------------------- -------------- --------------- -----eth0 1500 0 eth1 1500 1 srg 1500 0 hhh 1500 0

74:A2:E6:28:C6:AE N/A N/A disabled disabled 0

74:A2:E6:28:C6:AF N/A N/A disabled disabled 0

74:A2:E6:28:C6:B2 N/A N/A disabled disabled 64

74:A2:E6:28:C6:B3 N/A N/A disabled disabled 0

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

Name eth0:

MTU: 1500

Uplink Port: 0

MAC Address: B0:8B:CF:4C:ED:FF

CoS: 0

Trust Host CoS: disabled

PCI Link: 0

PCI Order: 0

VLAN: NONE

VLAN Mode: TRUNK

Rate Limiting: OFF

PXE Boot: disabled iSCSI Boot: disabled usNIC: 0

Channel Number: N/A

176

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

Managing Network Adapters

Viewing vNIC Properties

Port Profile: N/A

Uplink Failover: N/A

Uplink Failback Timeout: N/A aRFS: disabled

VMQ: disabled

NVGRE: disabled

VXLAN: disabled

CDN Name: VIC-MLOM-eth0

RoCE Version1: disabled

RoCE Version2: disabled

RDMA Queue Pairs: 0

RDMA Memory Regions: 0

RDMA Resource Groups: 0

RDMA COS: 0

Multi Queue: disabled

No of subVnics:

Multi Queue Transmit Queue Count:

Multi Queue Receive Queue Count:

Multi Que Completion Queue Count:

Multi Queue RoCE Version1:

Multi Queue RoCE Version2:

Multi Queue RDMA Queue Pairs:

Multi Queue RDMA Memory Regions:

Multi Queue RDMA Resource Groups:

Multi Queue RDMA COS:

Advanced Filters: disabled

Geneve Offload: disabled

Server# scope chassis

Server /chassis # scope adapter 1

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

Port MAC Address Link State Encap.. Mode Admin Speed Oper..Speed

Link Training

Connector Present Connector Supported

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

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

0 74:A2:E6:28:C6:A2 Link CE 40Gbps 40Gbps N/A

Yes

74:A2:E6:28:C6:A3 Link

Yes

CE 40Gbps 40Gbps N/A

Server /chassis/adapter # show ext-eth-if detail

C220-FCH1834V23X /chassis/adapter # show ext-eth-if detail

Port 0:

MAC Address: 74:A2:E6:28:C6:A2

Link State: Link

Encapsulation Mode: CE

Admin Speed: 40Gbps

Operating Speed: 40Gbps

Link Training: N/A

Connector Present: Yes

Connector Supported: Yes

Connector Type: QSFP_XCVR_CR4

Connector Vendor: CISCO

Connector Part Number: 2231254-3

Connector Part Revision: B

Port 1:

MAC Address: 74:A2:E6:28:C6:A3

Link State: Link

Encapsulation Mode: CE

Admin Speed: 40Gbps

Operating Speed: 40Gbps

Link Training: N/A

Connector Present: Yes

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

177

Managing Network Adapters

Modifying vNIC Properties

Connector Supported: Yes

Connector Type: QSFP_XCVR_CR4

Connector Vendor: CISCO

Connector Part Number: 2231254-3

Connector Part Revision: B

Server /chassis/adapter #

Modifying vNIC Properties

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show adapter

Step 3 Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

(Optional) Displays the available adapter devices.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

Step 4

Step 5

Step 6

Step 7

Step 8

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

{ eth0 | eth1 | name }

Enters the host Ethernet interface command mode for the specified vNIC.

Server /chassis/adapter/host-eth-if # set mtu mtu-value

Specifies the maximum transmission unit

(MTU) or packet size that the vNIC accepts.

Valid MTU values are 1500 to 9000 bytes; the default is 1500.

Server /chassis/adapter/host-eth-if # set uplink { 0 | 1 }

Specifies the uplink port associated with this vNIC. All traffic for this vNIC goes through this uplink port.

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

mac-addr mac-addr

Server /chassis/adapter/host-eth-if # set cos cos-value

Specifies a MAC address for the vNIC in the form hh:hh:hh:hh:hh:hh or hhhh:hhhh:hhhh.

Specifies the class of service (CoS) value to be marked on received packets unless the vNIC is configured to trust host CoS. Valid CoS values are 0 to 6; the default is 0. Higher values indicate more important traffic.

178

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

Managing Network Adapters

Modifying vNIC Properties

Step 9

Step 10

Step 11

Step 12

Command or Action Purpose

Note • You must set the COS value to 5 for the RDMA enabled interfaces.

• If NIV is enabled, this setting is determined by the switch, and the command is ignored.

Server /chassis/adapter/host-eth-if # trust-host-cos { disable | enable } set

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

{ any | 0-99 }

Specifies the relative order of this device for

PCI bus device number assignment; the default is any.

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

{ none | vlan-id }

Specifies the default VLAN for this vNIC.

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

Note If NIV is enabled, this setting is determined by the switch, and the command is ignored.

Server /chassis/adapter/host-eth-if # set vlan-mode { access | trunk }

Specifies whether the vNIC will trust host CoS or will remark packets. The behavior is as follows:

• disable —Received packets are remarked with the configured CoS. This is the default.

• enable —The existing CoS value of received packets (host CoS) is preserved.

Specifies the VLAN mode for the vNIC. The modes are as follows:

• access —The vNIC belongs to only one

VLAN. When the VLAN is set to access mode, any frame received from the specified default VLAN (1-4094) that is received from the switch with a TAG removes that TAG when it is sent to the host OS through the vNIC.

• trunk —The vNIC can belong to more than one VLAN. This is the default.

Note If NIV is enabled, this setting is determined by the switch, and the command is ignored.

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

179

Managing Network Adapters

Modifying vNIC Properties

Step 13

Step 14

Step 15

Step 16

Step 17

Command or Action

Server /chassis/adapter/host-eth-if # set rate-limit { off | rate }

Purpose

Specifies a maximum data rate for the vNIC.

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

For VIC 13xx controllers, you can enter an integer between 1 and 40,000.

For VIC 1455 and 1457 controllers:

• If the adapter is connected to 25 Gbps link on a switch, then you can enter an integer between 1 to 25,000 Mbps.

• If the adapter is connected to 10 Gbps link on a switch, then you can enter an integer between 1 to 10,000 Mbps.

For VIC 1495 and 1497 controllers:

• If the adapter is connected to 40 Gbps link on a switch, then you can enter an integer between 1 to 40,000 Mbps.

• If the adapter is connected to 100 Gbps link on a switch, then you can enter an integer between 1 to 100,000 Mbps.

Note If NIV is enabled, this setting is determined by the switch, and the command is ignored.

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

{ disable | enable }

Specifies whether the vNIC can be used to perform a PXE boot. Default value is set to disable for the default vNICs and user-created vNICs.

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

channel-number number

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

port-profile name set

If NIV mode is enabled for the adapter, select the channel number that will be assigned to this vNIC. The range is 1 to 1000.

If NIV mode is enabled for the adapter, select the port profile that should be associated with the vNIC.

Note The name must be a port profile defined on the switch to which this server is connected.

Server /chassis/adapter/host-eth-if # set uplink-failover { disable | enable }

If NIV mode is enabled for the adapter, enable this setting if traffic on this vNIC should fail over to the secondary interface if there are communication problems.

180

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

Managing Network Adapters

Modifying vNIC Properties

Step 18

Step 19

Step 20

Command or Action

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

uplink-failback-timeout seconds

Purpose

After a vNIC has started using its secondary interface, this setting controls how long the primary interface must be available before the system resumes using the primary interface for the vNIC.

Enter a number of seconds between 0 and 600.

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

{ disabled | enabled }

Enables or disables Virtual Machine Queue

(VMQ) for this adapter.

Note • Ensure that VMQ is not enabled when SR-IOV is enabled on the adapter.

• This option is available only on some Cisco UCS C-Series servers with 1495 or 1497 adapters.

Server /chassis/adapter/host-eth-if # set multi-queue { disabled | enabled }

Enables or disables the multi queue option for this adapter and allows you to set the following multi queue parameters:

• mq-rq-count —The number of receive queue resources to allocate. Enter an integer between 1 and 1000.

• mq-wq-count —The number of transmit queue resources to allocate. Enter an integer between 1 and 1000.

• mq-cq-count —The number of completion queue resources to allocate.

In general, the number of completion queue resources you should allocate is equal to the number of transmit queue resources plus the number of receive queue resources. Enter an integer between

1 and 2000.

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

181

Managing Network Adapters

Modifying vNIC Properties

Step 21

Step 22

Command or Action Purpose

Note • Multi queue is supported only on C-Series servers with 14xx adapters.

• VMQ must be in enabled state to enable this option.

• When you enable this option on one of the vNICs, configuring only VMQ

(without choosing multi-queue) on other vNICs is not supported.

• When this option is enabled usNIC configuration will be disabled.

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

{ disable | enable }

Enables or disables Accelerated Receive Flow steering (aRFS) for this adapter.

Server /chassis/adapter/host-eth-if # set geneve { disable | enable }

Beginning with release 4.1(2a), Cisco IMC supports Generic Network Virtualization

Encapsulation (Geneve) Offload feature with

Cisco VIC 14xx series adapters in ESX 7.0

(NSX-T 3.0) and ESX 6.7U3(NSX-T 2.5) OS.

Geneve is a tunnel encapsulation functionality for network traffic. Enable this feature if you want to enable Geneve Offload encapsulation in Cisco VIC 14xx series adapters.

Disable this feature to disable Geneve Offload, in order to prevent non-encapsulated UDP packets whose destination port numbers match with the Geneve destination port from being treated as tunneled packets.

If you enable Geneve Offload feature, then

Cisco recommends the following settings:

• Transmit Queue Count—1

• Transmit Queue Ring Size—4096

• Receive Queue Count—8

• Receive Queue Ring Size—4096

• Completion Queue Count—9

• Interrupt Count—11

182

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

Managing Network Adapters

Modifying vNIC Properties

Step 23

Step 24

Step 25

Step 26

Step 27

Command or Action Purpose

Note You cannot enable the following when Geneve Offload is enabled:

• RDMA on the same vNIC

• usNIC on the same vNIC

• Non-Port Channel Mode

• aRFS

• Advanced Filters

• NetQueue

Outer IPV6 is not supported with GENEVE

Offload feature.

Downgrade Limitation —If Geneve Offload is enabled, you cannot downgrade to any release earlier than 4.1(2a).

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

Enters the interrupt command mode.

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

set interrupt-count count

Specifies the number of interrupt resources.

The range is 1 to 514; the default is 8. In general, you should allocate one interrupt resource for each completion queue.

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

set coalescing-time usec

The time to wait between interrupts or the idle period that must be encountered before an interrupt is sent.

The range is 1 to 65535 microseconds; the default is 125. To turn off coalescing, enter 0

(zero).

Server /chassis/adapter/host-eth-if/interrupt # set coalescing-type { idle | min }

The coalescing types are as follows:

• idle —The system does not send an interrupt until there is a period of no activity lasting as least as long as the time specified in the coalescing time configuration.

• min —The system waits for the time specified in the coalescing time configuration before sending another interrupt event. This is the default.

Server /chassis/adapter/host-eth-if/interrupt # set interrupt-mode { intx | msi | msix }

Specifies the Ethernet interrupt mode. The modes are as follows:

• intx —Line-based interrupt (PCI INTx)

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

183

Managing Network Adapters

Modifying vNIC Properties

Step 28

Step 29

Step 30

Step 31

Step 32

Step 33

Step 34

Step 35

Step 36

Step 37

Step 38

Step 39

Step 40

Command or Action Purpose

• msi —Message-Signaled Interrupt (MSI)

• msix —Message Signaled Interrupts with the optional extension (MSI-X). This is the recommended and default option.

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

Exits to the host Ethernet interface command mode.

Server /chassis/adapter/host-eth-if # scope recv-queue

Enters receive queue command mode.

Server /chassis/adapter/host-eth-if/recv-queue

# set rq-count count

The number of receive queue resources to allocate. The range is 1 to 256; the default is

Server /chassis/adapter/host-eth-if/recv-queue

# set rq-ring-size size

The number of descriptors in the receive queue. The range is 64 to 4094; the default is

512.

Server /chassis/adapter/host-eth-if/recv-queue

# exit

Exits to the host Ethernet interface command mode.

Server /chassis/adapter/host-eth-if # scope trans-queue

Enters transmit queue command mode.

Server /chassis/adapter/host-eth-if/trans-queue

# set wq-count count

The number of transmit queue resources to allocate. The range is 1 to 256; the default is

Server /chassis/adapter/host-eth-if/trans-queue

# set wq-ring-size size

The number of descriptors in the transmit queue. The range is 64 to 4094; the default is

256.

Server /chassis/adapter/host-eth-if/trans-queue

# exit

Exits to the host Ethernet interface command mode.

Server /chassis/adapter/host-eth-if # scope comp-queue

Enters completion queue command mode.

Server /chassis/adapter/host-eth-if/comp-queue

# set cq-count count

The number of completion queue resources to allocate. The range is 1 to 512; the default is

In general, the number of completion queues equals the number of transmit queues plus the number of receive queues.

Server /chassis/adapter/host-eth-if/comp-queue

# exit

Exits to the host Ethernet interface command mode.

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

rdma_mr number

Sets the number of memory regions to be used per adapter. The values range from 4096 to

524288.

184

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

Managing Network Adapters

Modifying vNIC Properties

Step 41

Step 42

Step 43

Step 44

Step 45

Step 46

Command or Action

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

rdma_qp number

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

rdma_resgrp number set

Purpose

Sets the number of queue pairs to be used per adapter. The values range from 1-8192 queue pairs.

Sets the number of resource groups to be used.

The values range from 1-128 resource groups.

Note After committing the RoCE details, you are required to reboot the server for the changes to take place.

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

Enters TCP offload command mode.

Server /chassis/adapter/host-eth-if/offload # set tcp-segment-offload { disable | enable }

Enables or disables TCP Segmentation Offload as follows:

• disable —The CPU segments large TCP packets.

• enable —The CPU sends large TCP packets to the hardware to be segmented.

This option may reduce CPU overhead and increase throughput rate. This is the default.

Note This option is also known as Large

Send Offload (LSO).

Server /chassis/adapter/host-eth-if/offload # set tcp-rx-checksum-offload { disable | enable }

Enables or disables TCP Receive Offload

Checksum Validation as follows:

• disable —The CPU validates all packet checksums.

• enable —The CPU sends all packet checksums to the hardware for validation.

This option may reduce CPU overhead.

This is the default.

Server /chassis/adapter/host-eth-if/offload # set tcp-tx-checksum-offload { disable | enable }

Enables or disables TCP Transmit Offload

Checksum Validation as follows:

• disable —The CPU validates all packet checksums.

• enable —The CPU sends all packet checksums to the hardware for validation.

This option may reduce CPU overhead.

This is the default.

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

185

Managing Network Adapters

Modifying vNIC Properties

Step 51

Step 52

Step 53

Step 54

Step 55

Step 56

Step 57

Step 58

Step 47

Step 48

Step 49

Step 50

Command or Action

Server /chassis/adapter/host-eth-if/offload # set tcp-large-receive-offload { disable | enable }

Purpose

Enables or disables TCP Large Packet Receive

Offload as follows:

• disable —The CPU processes all large packets.

• enable —The hardware reassembles all segmented packets before sending them to the CPU. This option may reduce CPU utilization and increase inbound throughput. This is the default.

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

Exits to the host Ethernet interface command mode.

Server /chassis/adapter/host-eth-if # scope rss Enters Receive-side Scaling (RSS) command mode.

Server /chassis/adapter/host-eth-if/rss # set rss { disable | enable }

Enables or disables RSS, which allows the efficient distribution of network receive processing across multiple CPUs in multiprocessor systems. The default is enable for the two default vNICs, and disable for user-created vNICs.

Server /chassis/adapter/host-eth-if/rss # rss-hash-ipv4 { disable | enable }

Server /chassis/adapter/host-eth-if/rss # rss-hash-tcp-ipv4 { disable | enable }

Server /chassis/adapter/host-eth-if/rss # set rss-hash-ipv6 { disable | enable }

Server /chassis/adapter/host-eth-if/rss # set rss-hash-tcp-ipv6 { disable | enable }

Server /chassis/adapter/host-eth-if/rss # rss-hash-ipv6-ex { disable rss-hash-tcp-ipv6-ex {

| enable disable |

}

Server /chassis/adapter/host-eth-if/rss # enable set set set set

}

Enables or disables IPv4 RSS. The default is enable.

Enables or disables TCP/IPv4 RSS. The default is enable.

Enables or disables IPv6 RSS. The default is enable.

Enables or disables TCP/IPv6 RSS. The default is enable.

Enables or disables IPv6 Extension RSS. The default is disable.

Enables or disables TCP/IPv6 Extension RSS.

The default is disable.

Server /chassis/adapter/host-eth-if/rss # exit Exits to the host Ethernet interface command mode.

Server /chassis/adapter/host-eth-if # commit Commits the transaction to the system configuration.

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

186

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

Managing Network Adapters

Enabling or Disabling Link Training on External Ethernet Interfaces

Example

This example configures the properties of a vNIC:

Server# scope chassis

Server /chassis # show adapter

PCI Slot Product Name Serial Number Product ID Vendor

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

1 UCS VIC P81E QCI1417A0QK N2XX-ACPCI01 Cisco Systems Inc

Server /chassis # scope adapter 1

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

Server /chassis/adapter/host-eth-if # set uplink 1

Server /chassis/adapter/host-eth-if # set vmq enabled

Server /chassis/adapter/host-eth-if # set multi-queue enabled

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

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

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

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

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

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

What to do next

Reboot the server to apply the changes.

Enabling or Disabling Link Training on External Ethernet Interfaces

Link training for the port profile on the external ethernet interfaces of the specified vNIC can be enabled or disabled.

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show adapter

Step 3 Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

(Optional) Displays the available adapter devices.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

Step 4 Server /chassis / adapter # scope ext-eth-if 0 |

1 name

Enters the external ethernet interface command mode for the specified vNIC.

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

187

Managing Network Adapters

Setting Admin FEC Mode on External Ethernet Interfaces

Step 5

Step 6

Command or Action

Server /chassis / adapter / ext-eth-if # set link-training on | off

Purpose

Enables or disables the link training for the specified vNIC.

Server /chassis / adapter / ext-eth-if * # commit Commits the transaction to the system configuration.

Example

This example shows how to enable or disable link training on the external ethernet interface.

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope ext-eth-if 1

Server /chassis/adapter/ext-eth-if # set link-training on

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

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

Do you wish to continue? [y/N] y

Port 1:

MAC Address: 74:A2:E6:28:C6:A3

Link State: Link

Encapsulation Mode: CE

Admin Speed: 40Gbps

Operating Speed: -

Link Training: N/A

Connector Present: Yes

Connector Supported: Yes

Connector Type: QSFP_XCVR_CR4

Connector Vendor: CISCO

Connector Part Number: 2231254-3

Connector Part Revision: B

Server /chassis/adapter/ext-eth-if

Setting Admin FEC Mode on External Ethernet Interfaces

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # show adapter

Step 3 Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

(Optional) Displays the available adapter devices.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

188

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

Managing Network Adapters

Setting Admin FEC Mode on External Ethernet Interfaces

Step 4

Step 5

Command or Action Purpose

Server /chassis / adapter # scope ext-eth-if { 0

| 1 name }

Enters the external ethernet interface command mode for the specified vNIC.

Server /chassis / adapter / ext-eth-if # set admin-fec-mode { cl74 | cl91 | off }

Sets the admin FEC mode. The default value is cl91 .

Note • FEC mode is applicable only for 25G and 100G link speed.

On the 14xx adapters, the

Operating FEC mode on the adapter and the switch must match in order to achieve link between devices.

• In order to achieve a successful

BER the Operating FEC value needs to meet or exceed the minimum FEC requirement for the transceiver or cable PID in use.

The minimum FEC requirement is dependent on the link speed and specific PID.

Note For 25G refer Cisco 25GBASE

SFP28 Modules Data Sheet .

Table 3: For 25G

PID Min. FEC Optional

Higher FEC

NA SFP-25G-SR-S cl91

(RS-FEC)

SFP-10/25G

-CSR-S

Off -

30M/50M on

OM3/4 cl74 (FC-FEC,

Base-R FEC)

(at 25G) cl91

(RS-FEC) cl74 -

70M/100M on

OM3/4 cl91

(RS-FEC) cl91 -

300M/400M on OM3/4

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

189

Setting Admin FEC Mode on External Ethernet Interfaces

Command or Action

Managing Network Adapters

Purpose

PID

SFP-H25G

-CU1M/2M

Min. FEC

Off

Optional

Higher FEC cl74 (FC-FEC,

Base-R FEC) cl91

(RS-FEC) cl74 (FC-FEC,

Base-R FEC) cl91

(RS-FEC)

SFP-H25G

-CU3M

SFP-H25G-

CU4M/5M

SFP-25G-

AOC1M

/2M/3M

/5M/7M

/10M cl91

(RS-FEC)

NA cl74 (FC-FEC,

Base-R FEC) cl91

(RS-FEC)

For 100G:

All PIDs with the following exceptions require cl91 (RS-FEC):

• QSFP-40/100-SRBD at 100G requires

Operating FEC Off

• QSFP-100G-LR4-S requires Operational

FEC Off

For these two PIDs the Operating FEC is forced to Off regardless of the Admin FEC value.

For the 100G cables with the QSFP connector to the Nexus Switch and the SFP28 connector to VIC 14XX 25G adapters:

PID Min. FEC Optional

Higher FEC

QSFP

-4SFP25G

-CU1M/2M

Off cl74 (FC-FEC,

Base-R FEC) cl91

(RS-FEC)

190

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

Managing Network Adapters

Setting Admin FEC Mode on External Ethernet Interfaces

Step 6

Command or Action Purpose

PID

QSFP

-4SFP25G

-CU3M

Min. FEC cl74 (FC-FEC,

Base-R FEC)

Optional

Higher FEC cl91

(RS-FEC)

Operating FEC Mode —

For 14xx adapters the Operating FEC Mode is set to the Admin FEC Mode value. The only exceptions are QSFP-40/100-SRBD and

QSFP-100G-LR4-S as described in Admin

FEC Mode .

Note • For 25G interfaces on Nexus

NXOS Switches with Admin

FEC value set to Auto , the default value for Operating

FEC is cl74 (FC-FEC).

• For 100G interfaces on Nexus

Switches with the Admin FEC value set to Auto , the default value for Operating FEC is cl91

(RS-FEC).

The exceptions are

QSFP-40/100-SRBD and

QSFP-100G-LR4-S. The

Operating FEC is forced to Off , regardless of the Admin FEC value.

Refer to the Admin FEC Mode description for a successful connection with 14xx adapter.

Server /chassis / adapter / ext-eth-if * # commit At the prompt, select y . Commits the transaction to the system configuration.

Example

This example shows how to set the admin FEC mode on the external ethernet interface.

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope ext-eth-if 1

Server /chassis/adapter/ext-eth-if # set admin-fec-mode cl74

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

Changes to the network settings will be applied immediately.

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

191

Managing Network Adapters

Creating a vNIC

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

Do you wish to continue? [y/N] y

Port 1:

MAC Address: 00:5D:73:1C:6C:58

Link State: LinkDown

Encapsulation Mode: CE

Admin Speed: Auto

Operating Speed: -

Link Training: N/A

Admin FEC Mode: cl74

Operating FEC Mode: Off

Connector Present: NO

Connector Supported: N/A

Connector Type: N/A

Connector Vendor: N/A

Connector Part Number: N/A

Connector Part Revision: N/A

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

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.

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

Step 3

Step 4

Step 5

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

(Optional) Server /chassis/adapter/host-eth-if #

set channel-number number

If NIV mode is enabled for the adapter, you must assign a channel number to this vNIC. The range is 1 to 1000.

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

Creates a vNIC and enters the host Ethernet interface command mode. The name argument can be up to 32 ASCII characters.

Commits the transaction to the system configuration.

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

192

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

Managing Network Adapters

Deleting a vNIC

Example

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

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

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

Server /chassis/adapter # commit

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

Deletes the specified vNIC.

Note You cannot delete either of the two default vNICs, eth0 or eth1.

Commits the transaction to the system configuration.

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

Example

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 #

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

193

Managing Network Adapters

Creating Cisco usNIC Using the Cisco IMC CLI

Note Even though several properties are listed for Cisco usNIC in the usNIC properties dialog box, you must configure only the following properties because the other properties are not currently being used.

• cq-count

• rq-count

• tq-count

• usnic-count

Before you begin

You must log in to the Cisco IMC CLI with administrator privileges to perform this task.

Procedure

Step 1

Step 2

Command or Action server# scope chassis server/chassis# scope adapter index

Purpose

Enters chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note Make sure that the server is powered on before you attempt to view or change adapter settings. To view the index of the adapters configured on you server, use the show adapter command.

Step 3

Step 4 server/chassis/adapter# scope host-eth-if { eth0

| eth1 }

Enters the command mode for the vNIC.

Specify the Ethernet ID based on the number of vNICs that you have configured in your environment. For example, specify eth0 if you configured only one vNIC.

server/chassis/adapter/host-eth-if# create usnic-config 0

Creates a usNIC config and enters its command mode. Make sure that you always set the index value to 0.

194

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

Managing Network Adapters

Creating Cisco usNIC Using the Cisco IMC CLI

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Command or Action Purpose

Note To create a Cisco usNIC for the first time for a given vNIC using the

Cisco IMC CLI, you must first create a usnic-config .

Subsequently, you only need to scope into the usnic-config and modify the properties for Cisco usNIC. For more information about modifying Cisco usNIC properties, see

Modifying a Cisco usNIC value using the Cisco IMC CLI, on page

197

server/chassis/adapter/host-eth-if/usnic-config#

set cq-count count

Specifies the number of completion queue resources to allocate. We recommend that you set this value to 6.

The number of completion queues equals the number of transmit queues plus the number of receive queues.

server/chassis/adapter/host-eth-if/usnic-config#

set rq-count count

Specifies the number of receive queue resources to allocate. We recommend that you set this value to 6.

server/chassis/adapter/host-eth-if/usnic-config#

set tq-count count

Specifies the number of transmit queue resources to allocate. We recommend that you set this value to 6.

server/chassis/adapter/host-eth-if/usnic-config#

set usnic-count number of usNICs .

Specifies the number of Cisco usNICs to create. Each MPI process that is running on the server requires a dedicated Cisco usNIC.

Therefore, you might need to create up to 64

Cisco usNICs to sustain 64 MPI processes running simultaneously. We recommend that you create at least as many Cisco usNICs, per

Cisco usNIC-enabled vNIC, as the number of physical cores on your server. For example, if you have 8 physical cores on your server, create 8 Cisco usNICs.

server/chassis/adapter/host-eth-if

/usnic-config# commit

Commits the transaction to the system configuration.

Note The changes take effect when the server is rebooted.

server/chassis/adapter/host-eth-if/usnic-config# exit

Exits to host Ethernet interface command mode.

server/chassis/adapter/host-eth-if# exit Exits to adapter interface command mode.

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

195

Managing Network Adapters

Creating Cisco usNIC Using the Cisco IMC CLI

Step 12

Step 13

Step 14

Step 15

Step 16

Step 17

Step 18

Step 19

Command or Action server/chassis/adapter# server/chassis# server# server/bios# exit scope bios exit scope advanced

Purpose

Exits to chassis interface command mode.

Exits to server interface command mode.

Enters Bios command mode.

Enters the advanced settings of BIOS command mode.

server/bios/advanced# set IntelVTD Enabled Enables the Intel Virtualization Technology.

server/bios/advanced# set ATS Enabled Enables the Intel VT-d Address Translation

Services (ATS) support for the processor.

server/bios/advanced# set CoherencySupport

Enabled

Enables Intel VT-d coherency support for the processor.

server /bios/advanced# commit Commits the transaction to the system configuration.

Note The changes take effect when the server is rebooted.

Example

This example shows how to configure Cisco usNIC properties:

Server # scope chassis server /chassis # show adapter server /chassis # scope adapter 2 server /chassis/adapter # scope host-eth-if eth0 server /chassis/adapter/host-eth-if # create usnic-config 0 server /chassis/adapter/host-eth-if/usnic-config *# set usnic-count 64 server /chassis/adapter/host-eth-if/usnic-config *# set cq-count 6 server /chassis/adapter/host-eth-if/usnic-config *# set rq-count 6 server /chassis/adapter/host-eth-if/usnic-config *# set tq-count 6 server /chassis/adapter/host-eth-if/usnic-config *# commit

Committed settings will take effect upon the next server reset server /chassis/adapter/host-eth-if/usnic-config # exit server /chassis/adapter/host-eth-if # exit server /chassis/adapter # exit server /chassis # exit server # exit server# scope bios server /bios # scope advanced server /bios/advanced # set IntelVTD Enabled server /bios/advanced *# set ATS Enabled* server /bios/advanced *# set CoherencySupport Enabled server /bios/advanced *# commit

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

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

A system reboot has been initiated.

196

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

Managing Network Adapters

Modifying a Cisco usNIC value using the Cisco IMC CLI

Before you begin

You must log in to the Cisco IMC GUI with administrator privileges to perform this task.

Procedure

Step 1

Step 2

Command or Action server# scope chassis server/chassis# scope adapter index

Purpose

Enters chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note Make sure that the server is powered on before you attempt to view or change adapter settings. To view the index of the adapters configured on you server, use the show adapter command.

Step 3

Step 4

Step 5

Step 6

Step 7 server/chassis/adapter# scope host-eth-if { eth0

| eth1 }

Enters the command mode for the vNIC.

Specify the Ethernet ID based on the number of vNICs that you have configured in your environment. For example, specify eth0 if you configured only one vNIC.

server/chassis/adapter/host-eth-if# scope usnic-config 0

Enters the command mode for the usNIC.

Make sure that you always set the index value as 0 to configure a Cisco usNIC.

server/chassis/adapter/host-eth-if/usnic-config#

set usnic-count number of usNICs .

Specifies the number of Cisco usNICs to create. Each MPI process running on the server requires a dedicated Cisco usNIC. Therefore, you might need to create up to 64 Cisco usNIC to sustain 64 MPI processes running simultaneously. We recommend that you create at least as many Cisco usNIC, per Cisco usNIC-enabled vNIC, as the number of physical cores on your server. For example, if you have 8 physical cores on your server, create 8 usNICs.

server /chassis/adapter/host-eth-if

/usnic-config# commit

Commits the transaction to the system configuration.

Note The changes take effect when the server is rebooted.

server/chassis/adapter/host-eth-if/usnic-config# exit

Exits to host Ethernet interface command mode.

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

197

Managing Network Adapters

Viewing usNIC Properties

Step 8

Step 9

Step 10

Command or Action server/chassis/adapter/host-eth-if# exit server/chassis/adapter# exit server/chassis# exit

Purpose

Exits to adapter interface command mode.

Exits to chassis interface command mode.

Exits to server interface command mode.

Example

This example shows how to configure Cisco usNIC properties: server # scope chassis server /chassis # show adapter server /chassis # scope adapter 2 server /chassis/adapter # scope host-eth-if eth0 server /chassis/adapter/host-eth-if # scope usnic-config 0 server /chassis/adapter/host-eth-if/usnic-config # set usnic-count 32 server /chassis/adapter/host-eth-if/usnic-config # commit

Viewing usNIC Properties

Before you begin

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

usNIC must be configured on a vNIC.

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

Step 3

Step 4

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

{ eth0 | eth1 | name }

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

usnic-config index

Enters the host Ethernet interface command mode for the specified vNIC.

Displays the usNIC properties for a vNIC.

198

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

Managing Network Adapters

Deleting Cisco usNIC from a vNIC

Example

This example displays the usNIC properties 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 # show usnic-config 0

Idx usNIC Count TQ Count RQ Count CQ Count TQ Ring Size RQ Ring Size Interrupt Count

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

0 113 2 2 4

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

256 512 4

Deleting Cisco usNIC from a vNIC

Before you begin

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

Procedure

Step 1

Step 2

Command or Action server# scope chassis server/chassis# scope adapter index

Purpose

Enters chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note Make sure that the server is powered on before you attempt to view or change adapter settings. To view the index of the adapters configured on you server, use the show adapter command.

Step 3

Step 4

Step 5 server/chassis/adapter# scope host-eth-if { eth0

| eth1 }

Enters the command mode for the vNIC.

Specify the Ethernet ID based on the number of vNICs that you have configured in your environment. For example, specify eth0 if you configured only one vNIC.

Server/chassis/adapter/host-eth-if# usnic-config 0 delete

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

Deletes the Cisco usNIC configuration for the vNIC.

Commits the transaction to the system configuration

Note The changes take effect when the server is rebooted.

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

199

Managing Network Adapters

Configuring iSCSI Boot Capability

Example

This example shows how to delete the Cisco usNIC configuration for a vNIC: server # scope chassis server/chassis # show adapter server/chassis # scope adapter 1 server/chassis/adapter # scope host-eth-if eth0 server/chassis/adapter/host-eth-if # delete usnic-config 0 server/chassis/host-eth-if/iscsi-boot *# commit

New host-eth-if settings will take effect upon the next adapter reboot server/chassis/host-eth-if/usnic-config #

Configuring iSCSI Boot Capability

Configuring iSCSI Boot Capability for vNICs

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.

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

200

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

Managing Network Adapters

Deleting an iSCSI Boot Configuration for a vNIC

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Command or Action

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

{ eth0 | eth1 | name }

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

iscsi-boot index

Purpose

Enters the host Ethernet interface command mode for the specified vNIC.

Creates the iSCSI boot index for the vNIC. At this moment, only 0 is allowed as the index.

Server /chassis/adapter/host-eth-if/iscsi-boot*

# create iscsi-target index

Creates an iSCSI target for the vNIC. The value can either be 0 or 1.

Server /chassis/adapter/host-eth-if/iscsi-boot*

# set dhcp-net-settings enabled

Enables the DHCP network settings for the iSCSI boot.

Server /chassis/adapter/host-eth-if/iscsi-boot*

# set initiator-name string

Sets the initiator name. It cannot be more than

223 characters.

Server /chassis/adapter/host-eth-if/iscsi-boot*

# set dhcp-iscsi-settings enabled

Enables the DHCP iSCSI settings.

Server /chassis/adapter/host-eth-if/iscsi-boot*

# commit

Commits the transaction to the system configuration.

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

Example

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 #

Deleting an iSCSI Boot Configuration for a vNIC

Before you begin

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

Procedure

Step 1

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

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

201

Managing Network Adapters

Backing Up and Restoring the Adapter Configuration

Step 2

Step 3

Step 4

Step 5

Command or Action

Server /chassis # scope adapter index

Purpose

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

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

{ eth0 | eth1 | name }

Enters the host Ethernet interface command mode for the specified vNIC.

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

Deletes the iSCSI boot capability for the vNIC.

Server /chassis/adapter/host-eth-if* # commit Commits the transaction to the system configuration

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

Example

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 #

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.

202

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

Managing Network Adapters

Exporting the Adapter Configuration

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

Server /chassis/adapter # export-vnic protocol remote server IP address

Starts the export operation. The adapter configuration file will be stored at the specified path and filename on the remote server at the specified IP address. The protocol can be one of the following:

• TFTP

• FTP

• SFTP

• SCP

• HTTP

If you chose SCP or SFTP as the remote server type while performing this action, a prompt with the message Server (RSA) key fingerprint is <server_finger_print

_ID> Do you wish to continue?

Click y or n depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

Example

This example exports the configuration of adapter 1:

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

203

Managing Network Adapters

Importing the Adapter Configuration

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # export-vnic ftp 192.0.20.34 //test/dnld-ucs-k9-bundle.1.0.2h.bin

Server /chassis/adapter #

Importing the Adapter Configuration

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

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # scope adapter index

Purpose

Enters the chassis command mode.

Enters the command mode for the adapter card at the PCI slot number specified by index .

Note The server must be powered on before you can view or change adapter settings.

Step 3 Server /chassis/adapter # import-vnic tftp-ip-address path-and-filename

Starts the import operation. The adapter downloads the configuration file from the specified path on the TFTP server at the specified IP address. The configuration will be installed during the next server reboot.

Example

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.

204

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

Managing Network Adapters

Restoring Adapter Defaults

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # adapter-reset-defaults index Restores factory default settings for the adapter at the PCI slot number specified by the index argument.

Note Resetting the adapter to default settings sets the port speed to 4 X 10

Gbps. Choose 40 Gbps as the port speed only if you are using a 40

Gbps switch.

Example

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 #

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 Cisco IMC 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 Cisco IMC. You can install this firmware using the Host Upgrade Utility.

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

205

Managing Network Adapters

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

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # update-adapter-fw tftp-ip-address path-and-filename { activate | no-activate } [ pci-slot ] [ pci-slot ]

(Optional) Server /chassis # recover-adapter-update [ pci-slot ] [ pci-slot ]

Downloads the specified adapter firmware file from the TFTP server, then installs the firmware as the backup image on one or two specified adapters or, if no adapter is specified, on all adapters. If the activate keyword is specified, the new firmware is activated after installation.

Clears an incomplete firmware update condition on one or two specified adapters or, if no adapter is specified, on all adapters.

Example

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 #

What to do next

To activate the new firmware, see

Activating Adapter Firmware, on page 207

206

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

Managing Network Adapters

Activating Adapter Firmware

Important While the activation is in progress, do not:

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

• Reboot or reset Cisco IMC.

• 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

Step 1

Step 2

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # activate-adapter-fw pci-slot

{ 1 | 2 }

Activates adapter firmware image 1 or 2 on the adapter in the specified PCI slot.

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

Example

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 4.2

207

Managing Network Adapters

Resetting the Adapter

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server/chassis # adapter-reset index

Purpose

Enters the chassis command mode.

Resets the adapter at the PCI slot number specified by the index argument.

Note Resetting the adapter also resets the host.

Example

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 #

208

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

C H A P T E R

Managing Storage Adapters

This chapter includes the following sections:

•

Creating Virtual Drives from Unused Physical Drives, on page 210

•

Creating Virtual Drive from an Existing Drive Group, on page 212

•

Setting a Virtual Drive as Transport Ready, on page 215

•

Clearing a Virtual Drive as Transport Ready, on page 216

•

Setting Physical Drive Status Auto Config Mode, on page 217

•

Importing Foreign Configuration, on page 219

•

Unlocking Foreign Configuration Drives, on page 219

•

Clearing Foreign Configuration, on page 220

•

Enabling JBOD, on page 221

•

Disabling JBOD, on page 222

•

Clearing a Boot Drive, on page 223

•

Enabling Security on a JBOD, on page 223

•

Clearing a Secure Physical Drive, on page 224

•

Clearing a Secure SED Foreign Configuration Physical Drive , on page 225

•

Retrieving Storage Firmware Logs for a Controller, on page 226

•

Self Encrypting Drives (Full Disk Encryption), on page 227

•

Deleting a Virtual Drive, on page 233

•

Initializing a Virtual Drive, on page 234

•

Set as Boot Drive, on page 235

•

Editing a Virtual Drive, on page 236

•

Securing a Virtual Drive, on page 237

•

Modifying Attributes of a Virtual Drive, on page 238

•

Making a Dedicated Hot Spare, on page 239

•

Making a Global Hot Spare, on page 239

•

Preparing a Drive for Removal, on page 240

•

Toggling Physical Drive Status, on page 241

•

Setting a Physical Drive as a Controller Boot Drive, on page 242

•

Removing a Drive from Hot Spare Pools, on page 243

•

Undo Preparing a Drive for Removal, on page 244

•

Enabling Auto Learn Cycles for the Battery Backup Unit, on page 245

•

Disabling Auto Learn Cycles for the Battery Backup Unit, on page 245

•

Starting a Learn Cycle for a Battery Backup Unit, on page 246

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

209

Managing Storage Adapters

Creating Virtual Drives from Unused Physical Drives

•

Toggling the Locator LED for a Physical Drive, on page 247

•

Viewing Storage Controller Logs, on page 247

•

Viewing NVMe Controller Details, on page 248

•

Viewing NVMe Physical Drive Details, on page 249

•

Viewing SIOC NVMe Drive Details , on page 250

•

Viewing PCI Switch Details, on page 251

•

Viewing Details of a Particular PCI Switch, on page 253

•

Managing the Flexible Flash Controller, on page 254

•

Managing the FlexUtil Controller, on page 266

•

Cisco Boot Optimized M.2 Raid Controller, on page 279

•

Cisco FlexMMC, on page 284

Creating Virtual Drives from Unused Physical Drives

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # virtual-drive create

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

At this point, you are prompted to enter information corresponding to the RAID level, the physical drives to be used, the size, enabling full disk encryption of the drive and the write policy for the new virtual drive. Enter the appropriate information at each prompt.

When you have finished specifying the virtual drive information, you are prompted to confirm that the information is correct. Enter y (yes) to confirm, or n (no) to cancel the operation.

Note Enabling full disk encryption secures the drive.

Step 4 Server /chassis/storageadapter # virtual-drive show Displays the existing virtual drives.

Example

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

210

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

Managing Storage Adapters

Creating Virtual Drives from 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, 10, 50 --> 1

Please choose from the following 10 unused physical drives:

ID Size(MB) Model Interface Type

1 571776

2 571776

SEAGATE

SAS

HDD

4 571776

5 428672

6 571776

7 571776

8 571776

9 428672

10 571776

11 953344

SEAGATE

SAS

HDD

Specify physical disks for span 0:

Enter comma-separated PDs from above list--> 1,2

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' --> 10 GB

Optional attribute: stripsize: defaults to 64K Bytes

0: 8K Bytes

1: 16K Bytes

2: 32K Bytes

3: 64K Bytes

4: 128K Bytes

5: 256K Bytes

6: 512K Bytes

7: 1024K Bytes

Choose number from above options or hit return to pick default--> 2 stripsize will be set to 32K Bytes (6 and 'strip-size\:32k')

Disk Cache Policy: defaults to Unchanged

0: Unchanged

1: Enabled

2: Disabled

Choose number from above options or hit return to pick default--> 0

Disk Cache Policy will be set to Unchanged (0 and 'disk-cache-policy\:unchanged'

)

Read Policy: defaults to No Read Ahead

0: No Read Ahead

1: Always

Choose number from above options or hit return to pick default--> 0

Read Policy will be set to No Read Ahead (0 and 'read-policy\:no-read-ahead')

Write Policy: defaults to Write Through

0: Write Through

1: Write Back Good BBU

2: Always Write Back

Choose number from above options or hit return to pick default--> 0

Write Policy will be set to Write Through (0 and 'write-policy\:write-through')

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

211

Managing Storage Adapters

Creating Virtual Drive from an Existing Drive Group

IO Policy: defaults to Direct I/O

0: Direct I/O

1: Cached I/O

Choose number from above options or hit return to pick default--> 0

IO Policy will be set to Direct I/O (0 and 'io-policy\:direct-io')

Access Policy: defaults to Read Write

0: Read Write

1: Read Only

2: Blocked

Choose number from above options or hit return to pick default--> 0

Access Policy will be set to Read Write (0 and 'access-policy\:read-write')

Enable SED security on virtual drive (and underlying drive group)?

Enter y or n--> y

Virtual drive and drive group will be secured

New virtual drive will have the following characteristics:

- Spans: '[1.2]'

- RAID level: '1'

- Name: 'test_v_drive'

- Size: 10 GB

- stripsize: 32K Bytes

- Disk Cache Policy: Unchanged

- Read Policy: No Read Ahead

- Write Policy: Write Through

- IO Policy: Direct I/O

- Access Policy: Read Write

- Encryption: FDE

OK? (y or n)--> y

Server /chassis/storageadapter # show virtual-drive

Virtual Drive Health Status Name

0 false

Size RAID Level

Boot Drive

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

----------

Good Optimal 150528 MB RAID 0

Good Optimal 20480 MB RAID 0 1 true

2 false

Good

Optimal

Optimal test_v_drive

114140 MB

10000 MB

RAID 0

RAID 1 false

4 false

Good Optimal new_from_test 500 MB RAID 1

Server /chassis/storageadapter #

Creating Virtual Drive from an Existing Drive Group

Before you begin

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

212

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

Managing Storage Adapters

Creating Virtual Drive from an Existing Drive Group

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # carve-virtual-drive

Server /chassis/storageadapter # virtual-drive show

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

At this point, you are prompted to enter information corresponding to the virtual drives to be used, and the size and the write policy for the new virtual drive. Enter the appropriate information at each prompt.

When you have finished specifying the virtual drive information, you are prompted to confirm that the information is correct. Enter y (yes) to confirm, or n (no) to cancel the operation.

Displays the existing virtual drives.

Example

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 # carve-virtual-drive

< Fetching virtual drives...>

ID Name RL VDSize MaxPossibleSize PD(s)

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

0 RAID0_12 0 100 MB Unknown 1,2

Please choose from the above list the virtual drive number whose space the new virtual drive will share--> 0

New virtual drive will share space with VD 0

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

Please enter Virtual Drive size in MB, GB, or TB (maximum: Unknown)

Example format: '400 GB' --> 10 GB

Optional attributes: stripsize: defaults to 64K Bytes

0: 8K Bytes

1: 16K Bytes

2: 32K Bytes

3: 64K Bytes

4: 128K Bytes

5: 256K Bytes

6: 512K Bytes

7: 1024K Bytes

Choose number from above options or hit return to pick default--> 0 stripsize will be set to 8K Bytes (4 and 'strip-size\:8k')

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

213

Managing Storage Adapters

Creating Virtual Drive from an Existing Drive Group

Disk Cache Policy: defaults to Unchanged

0: Unchanged

1: Enabled

2: Disabled

Choose number from above options or hit return to pick default--> 0

Disk Cache Policy will be set to Unchanged (0 and 'disk-cache-policy\:unchanged')

Read Policy: defaults to No Read Ahead

0: No Read Ahead

1: Always

Choose number from above options or hit return to pick default--> 0

Read Policy will be set to No Read Ahead (0 and 'read-policy\:no-read-ahead')

Write Policy: defaults to Write Through

0: Write Through

1: Write Back Good BBU

2: Always Write Back

Choose number from above options or hit return to pick default--> 0

Write Policy will be set to Write Through (0 and 'write-policy\:write-through')

IO Policy: defaults to Direct I/O

0: Direct I/O

1: Cached I/O

Choose number from above options or hit return to pick default--> 0

IO Policy will be set to Direct I/O (0 and 'io-policy\:direct-io')

Access Policy: defaults to Read Write

0: Read Write

1: Read Only

2: Blocked

Choose number from above options or hit return to pick default--> 0

Access Policy will be set to Read Write (0 and 'access-policy\:read-write')

New virtual drive will have the following characteristics:

- It will share space with virtual drive 0

- Name: 'amit'

- Size: 10 GB

- stripsize: 8K Bytes

- Disk Cache Policy: Unchanged

- Read Policy: No Read Ahead

- Write Policy: Write Through

- IO Policy: Direct I/O

- Access Policy: Read Write

OK? (y or n)--> y

Server /chassis/storageadapter # show virtual-drive

Virtual Drive Health

Boot Drive

Status Name Size RAID Level

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

----------

0 Good Optimal 150528 MB RAID 0 false

1 true

2 false

3 false

4 false

Good

Optimal

Optimal test_v_drive new_from_test

20480 MB

114140 MB

10000 MB

500 MB

RAID 0

RAID 1

Server /chassis/storageadapter #

214

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

Managing Storage Adapters

Setting a Virtual Drive as Transport Ready

Before you begin

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

• The virtual drive must be in optimal state to enable transport ready.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server # scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot ID Enters the command mode for an installed storage card.

Server /chassis/storageadapter # scope

virtual-drive drive-number

Enters the command mode for the specified virtual drive.

Server /chassis/storageadapter/virtual-drive #

set-transport-ready {include-all | exclude-all

| include-dhsp}

Sets the virtual drive to transport ready and assigns the chosen properties.

Enter the initialization type using which you can set the selected virtual drive as transport ready. This can be one of the following:

• exlude-all — Excludes all the dedicated hot spare drives.

• include-all — Includes any exclusively available or shared dedicated hot spare drives.

• include-dhsp — Includes exclusive dedicated hot spare drives.

When you are prompted to confirm the action.

Enter y to confirm.

Note When you set a virtual drive to transport ready all the physical drives associated with it are displayed as Ready to remove.

(Optional) Server

/chassis/storageadapter/virtual-drive # show detail

Display the virtual drive properties with the change.

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

215

Managing Storage Adapters

Clearing a Virtual Drive as Transport Ready

Example

This example shows how to set virtual drive 5 to transport ready:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-HBA

Server /chassis/storageadapter # scope virtual-drive 5

Server /chassis/storageadapter/virtual-drive # set-transport-ready exclude-all

Since they belong to same drive group, all these virtual drives will be set to Transport

Ready - 0

Are you sure you want to proceed?[y|N] y

Server /chassis/storageadapter/virtual-drive # show detail

Virtual Drive 0:

Health: Good

Status: Optimal

Visibility : Visible

Name: RAID0_124_RHEL

Size: 2858160 MB

Physical Drives: 1, 2, 4

RAID Level: RAID 0

Boot Drive: false

FDE Capable: 0

FDE Enabled: 0

Target ID: 0

Strip Size: 64 KB

Drives Per Span: 3

Span Depth: 1

Access Policy: Transport Ready

Cache Policy: Direct

Read Ahead Policy: None

Requested Write Cache Policy: Write Through

Current Write Cache Policy: Write Through

Disk Cache Policy: Unchanged

Auto Snapshot: false

Auto Delete Oldest: true

Allow Background Init: true

Server /chassis/storageadapter/virtual-drive #

Clearing a Virtual Drive as Transport Ready

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server # scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot ID Enters the command mode for an installed storage card.

Server /chassis/storageadapter # scope

virtual-drive drive-number

Enters the command mode for the specified virtual drive.

216

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

Managing Storage Adapters

Setting Physical Drive Status Auto Config Mode

Step 4

Step 5

Command or Action

Server /chassis/storageadapter/virtual-drive # clear-transport-ready

Purpose

This reverts the selected transport ready virtual drive to its original status.

When you are prompted to confirm the action.

Enter y to confirm.

(Optional) Server

/chassis/storageadapter/virtual-drive # show detail

Display the virtual drive properties with the change.

Example

This example shows how to revert the selected transport ready virtual drive to its original state:

Server # scope chassis

Server /chassis # scope server 1

Server /chassis # scope storageadapter SLOT-HBA

Server /chassis/storageadapter # scope virtual-drive 5

Server /chassis/storageadapter/virtual-drive # clear-transport-ready

Since they belong to same drive group, all these virtual drives will be moved out of Transport

Ready - 0

Are you sure you want to proceed?[y|N] y

Server /chassis/storageadapter/virtual-drive # show detail

Virtual Drive 0:

Health: Good

Status: Optimal

Visibility : Visible

Name: RAID0_124_RHEL

Size: 2858160 MB

Physical Drives: 1, 2, 4

RAID Level: RAID 0

Boot Drive: false

FDE Capable: 0

FDE Enabled: 0

Target ID: 0

Strip Size: 64 KB

Drives Per Span: 3

Span Depth: 1

Access Policy: Read-Write

Cache Policy: Direct

Read Ahead Policy: None

Requested Write Cache Policy: Write Through

Current Write Cache Policy: Write Through

Disk Cache Policy: Unchanged

Auto Snapshot: false

Auto Delete Oldest: true

Allow Background Init: true

Server /chassis/storageadapter/virtual-drive #

Setting Physical Drive Status Auto Config Mode

The following procedure explains how to set physical drive status auto config mode in the controller.

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

217

Managing Storage Adapters

Setting Physical Drive Status Auto Config Mode

Before you begin

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

Note You can set physical drive status auto config mode only on some UCS C-Series servers.

Procedure

Step 1

Step 2

Step 3

Server# scope chassis

Enters the chassis command mode.

Server /chassis# scope storageadapter

Enters the command mode for the storage adapter.

Server /chassis/storageadapter# set-auto-cfg-option unconfigured-good

The following message is displayed:

Are you sure you want to change auto config option?

Enter 'yes' to confirm -> yes

At the confirmation prompt, enter yes. Enables unconfigured-good mode. This is the default option.

Name

Physical Drive Status Auto

Config Mode options

Description

This can be one of the following:

• unconfigured-good - The default option. Select this option if you are using the server for RAID volume and mixed JBOD.

• raid-0-writeback - Select this option if you are using the server for per drive R0 WB.

• jbod - Select this option if you are using the server for JBOD only.

Note All the status of the unused physical drives changes when you select the appropriate option in the

Auto Config mode.

Example

This example set the physical drive status auto config mode to unconfigured-good .

Server# scope chassis

Server /chassis # scope storageadapter

Server /chassis/storageadapter # set-auto-cfg-option unconfigured-good

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter #

218

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

Managing Storage Adapters

Importing Foreign Configuration

When one or more physical drives that have previously been configured with a different controller are inserted into a server, they are identified as foreign configurations. You can import these foreign configurations to a controller.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # import-foreign-config

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

You are prompted to confirm the action. Enter yes to confirm.

Note If you do not enter aborted.

yes , the action is

Example

This example shows how to import all foreign configurations on the MegaRAID controller in slot

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # import-foreign-config

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

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter #

Unlocking Foreign Configuration Drives

When a set of physical drives hosting a secured drive group are inserted into a different server or controller

(or the same controller but whose security-key has been changed while they were not present), they become foreign configurations. Since they are secured, these foreign configurations must be unlocked before they can be imported. The following procedure explains how to unlock a foreign configuration drive:

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 4.2

219

Managing Storage Adapters

Clearing Foreign Configuration

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

At the prompt, enter the security key and enter yes at the confirmation prompt.

Server /chassis/storageadapter # unlock-foreign-configuration

(Optional) Server /chassis/storageadapter # scope physical-drive 2

Enters the physical drive command mode.

(Optional) Server

/chassis/storageadapter/physicsl-drive # show detail

Displays the status of the unlocked foreign drive.

Example

This example shows how to unlock a foreign configuration drive:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # unlock-foreign-configuration

Please enter the security key to unlock the foreign configuration -> testSecurityKey

Server /chassis/storageadapter # import-foreign-config

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

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter # scope physical-drive 2

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

Physical Drive Number 2:

Controller: SLOT-HBA

Health: Good

Status: Online

FDE Capable: 1

FDE Enabled: 1

FDE Secured: 1

FDE Locked: 0

FDE locked foreign config: 0

Server /chassis/storageadapter/physical-drive #

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.

220

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

Managing Storage Adapters

Enabling JBOD

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # clear-foreign-config

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

You are prompted to confirm the action. Enter yes to confirm.

Note If you do not enter aborted.

yes , the action is

Example

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 #

Enabling JBOD

Note You can enable Just a Bunch of Disks (JBOD) only on some UCS C-Series servers.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis /storageadapter # enable-jbod-mode

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Enables the JBOD Mode for the selected controller

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

221

Managing Storage Adapters

Disabling JBOD

Example

This example enables the JBOD mode for the selected controller:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # enable-jbod-mode

Are you sure you want to enable JBOD mode?

Enter 'yes' to confirm -> yes

Server/chassis/storageadapter # show settings

PCI Slot SLOT-3:

Info Valid: Yes

Enable JBOD Mode: true

Disabling JBOD

Note This option is available only on some UCS C-Series servers.

Before you begin

JBOD mode must be enabled for the selected controller.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis /storageadapter # disable-jbod-mode

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Disables the JBOD Mode for the selected controller

Example

This example disables the JBOD mode for the selected controller:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # disable-jbod-mode

Are you sure you want to disable JBOD mode?

Enter 'yes' to confirm -> yes

Server/chassis/storageadapter # show settings

PCI Slot SLOT-3:

Info Valid: Yes

Enable JBOD Mode: false

222

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

Managing Storage Adapters

Clearing a Boot Drive

Important This task clears the boot drive configuration on the controller. This action cannot be reverted.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # clear-boot-drive

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

You are prompted to confirm the action. Enter yes to confirm.

Note If you do not enter aborted.

yes , the action is

Example

This example shows how to clear the boot drive configuration on the MegaRAID controller in slot

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # clear-boot-drive

Are you sure you want to clear the controller's boot drive?

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter #

Enabling Security on a JBOD you can enable security on a physical drive only if it is a JBOD. The following procedure explains how to enable security on a JBOD:

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 4.2

223

Managing Storage Adapters

Clearing a Secure Physical Drive

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Server /chassis/storageadapter # scope physical-drive 2

Server /chassis/storageadapter # enable-security-on-jbod

Enters the physical drive command mode.

At the confirmation prompt, enter yes .

Enables security on the JBOD.

(Optional) Server

/chassis/storageadapter/physicsl-drive # show detail

Displays details of the physical drive.

Example

This example shows how to enable security on a JBOD:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3 savbu-stordev-dn1-2-cimc /chassis/storageadapter # scope physical-drive 2 server /chassis/storageadapter/physical-drive # enable-security-on-jbod

Are you sure you want to enable security on this JBOD?

NOTE: this is not reversible!

Enter 'yes' to confirm -> yes server /chassis/storageadapter/physical-drive # show detail

Physical Drive Number 2:

Status: JBOD

FDE Capable: 1

FDE Enabled: 1

FDE Secured: 1 server /chassis/storageadapter/physical-drive #

Clearing a Secure Physical Drive

Clearing a secure drive converts an FDE drive from secured to unsecured. The Physical drive status must be

Unconfigured good to perform this action. This erases the data on the physical drive. The following procedure explains how to clear a secure SED physical drive:

Before you begin

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

224

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

Managing Storage Adapters

Clearing a Secure SED Foreign Configuration Physical Drive

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Server /chassis/storageadapter # scope physical-drive 2

Enters the physical drive command mode.

Server /chassis/storageadapter/physicsl-drive # clear-secure-drive

At the confirmation prompt, enter yes .

This clears the secure SED physical drive and all the data will be lost.

(Optional) Server

/chassis/storageadapter/physicsl-drive # show detail

Displays the physical drive details.

Example

This example shows how to clear an SED foreign configuration physical drive:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 2

Server /chassis/storageadapter/physical-drive # clear-secure-drive

Are you sure you want to erase all data from this physical drive?

NOTE: this is not reversible!

ALL DATA WILL BE LOST!!

Enter 'yes' to confirm -> yes

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

Physical Drive Number 2:

Controller: SLOT-HBA

Health: Good

Status: Unconfigured Good

FDE Capable: 1

FDE Enabled: 0

FDE Secured: 0

Server /chassis/storageadapter/physical-drive #

Clearing a Secure SED Foreign Configuration Physical Drive

Coverts a locked foreign configuration Full Disk Encryption drive to a unsecured and unlocked drive. This erases the data on the physical drive. The following procedure explains how to clear a secure SED foreign configuration physical drive:

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 4.2

225

Managing Storage Adapters

Retrieving Storage Firmware Logs for a Controller

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Server /chassis/storageadapter # scope physical-drive 2

Enters the physical drive command mode.

Server /chassis/storageadapter/physicsl-drive # clear-secure-foreign-config-drive

At the confirmation prompt, enter yes .

This clears the secure SED foreign configuration physical drive and all the data will be lost.

(Optional) Server

/chassis/storageadapter/physicsl-drive # show detail

Displays the physical drive details.

Example

This example shows how to clear an SED foreign configuration physical drive:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 2

Server /chassis/storageadapter/physical-drive # clear-secure-foreign-config-drive

Are you sure you want to erase all data from this foreign-configuration physical drive?

NOTE: this is not reversible!

ALL DATA WILL BE LOST!!

Enter 'yes' to confirm -> yes

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

Physical Drive Number 2:

Controller: SLOT-HBA

Health: Good

Status: Unconfigured Good

FDE Capable: 1

FDE Enabled: 0

FDE Secured: 0

FDE Locked: 0

FDE Locked Foreign Config: 0

Server /chassis/storageadapter/physical-drive #

Retrieving Storage Firmware Logs for a Controller

This task retrieves the Storage Firmware Logs for the controller and places it in the /var/log location. This ensures that this log data is available when Technical Support Data is requested.

Before you begin

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

226

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

Managing Storage Adapters

Self Encrypting Drives (Full Disk Encryption)

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Server /chassis/storageadapter # get-storage-fw-log

Server /chassis/storageadapter # show detail Displays the status of the retrieval process.

Important Retrieving Storage Firmware Logs for a controller could take up to 2-4 minutes. Until this process is complete, do not initiate exporting technical support data.

Example

This example shows how to retrieve Storage Firmware Logs for a MegaRAID controller in slot 3:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # get-storage-fw-log

Server /chassis/storageadapter # show detail

PCI Slot SLOT-3:

TTY Log Status: In progress (8192 bytes fetched)

Server /chassis/storageadapter # show detail

PCI Slot SLOT-3:

TTY Log Status: In progress (90112 bytes fetched)

Server /chassis/storageadapter # show detail

PCI Slot SLOT-3:

TTY Log Status: Complete (172032 bytes fetched)

Self Encrypting Drives (Full Disk Encryption)

Cisco IMC supports self encrypting drives (SED). A special hardware in the drives encrypts incoming data and decrypts outgoing data in real-time. This feature is also called Full Disk Encryption (FDE).

The data on the drive is encrypted on its way into the drive and decrypted on its way out. However, if you lock the drive, no security key is required to retrieve the data.

When a drive is locked, an encryption key is created and stored internally. All data stored on this drive is encrypted using that key, and stored in encrypted form. Once you store the data in this manner, a security key is required in order to un-encrypt and fetch the data from the drive. Unlocking a drive deletes that encryption key and renders the stored data unusable. This is called a Secure Erase. The FDE comprises a key ID and a security key.

The FDE feature supports the following operations:

• Enable and disable security on a controller

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

227

Managing Storage Adapters

Enabling Drive Security on a Controller

• Create a secure virtual drive

• Secure a non-secure drive group

• Unlock foreign configuration drives

• Enable security on a physical drive (JBOD)

• Clear secure SED drives

• Clear secure foreign configuration

Scenarios to consider While Configuring Controller Security in a Dual or Multiple Controllers

Environment

Note Dual or Multiple controllers connectivity is available only on some servers.

Controller security can be enabled, disabled, or modified independently. However, local and remote key management applies to all the controllers on the server. Therefore security action involving switching the key management modes must be performed with caution. In a scenario where both controllers are secure, and you decide to move one of the controllers to a different mode, you need to perform the same operation on the other controller as well.

Consider the following two scenarios:

• Scenario 1—Key management is set to remote; both controllers are secure and use remote key management. If you now wish to switch to local key management, switch the key management for each controller and disable remote key management.

• Scenario 2—Key management is set to local; both controllers are secure and use local key management.

If you now wish to switch to remote key management, enable remote key management and switch the key management for each controller.

If you do not modify the controller security method on any one of the controllers, it renders the secure key management in an unsupported configuration state.

Enabling Drive Security on a Controller

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # enable-controller-security

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

At this point, you are prompted to enter a security key, you can either enter a security key

228

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

Managing Storage Adapters

Disabling Drive Security on a Controller

Step 4

Command or Action

Server /chassis/storageadapter # show detail

Purpose of your choice or you can use the suggested security key. If you choose to assign a security key of your choice, enter the security key at the prompt.

Depending on whether you want to use the suggested security key or a security key of your choice, enter y (yes) to confirm, or n (no) to cancel the operation at the appropriate prompt.

Displays the storage drive details.

Example

The following example shows how to enable security on a controller:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # enable-controller-security

Use generated key-id 'UCSC-MRAID12G_FHH18250010_1d85dcd3'?

(y or n)--> y

Use suggested security-key '6ICsmuX@oVB7e9wXt79qsTgp6ICsmuX@'?

(y or n)--> n

Enter security-key --> testSecurityKey

Will use security-key ' testSecurityKey '

Server /chassis/storageadapter show detail

PCI Slot SLOT-HBA:

Controller is Secured: 1

Server /chassis/storageadapter #

Disabling Drive Security on a Controller

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # disable-controller-security

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

A confirmation prompt appears.

At the confirmation prompt, enter yes to confirm, or n (no) to cancel the operation.

Another prompt to enter the security key appears. Enter the security key.

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

229

Managing Storage Adapters

Modifying Controller Security Settings

Step 4

Command or Action

Server /chassis/storageadapter # show detail

Purpose

This disables the controller security.

Displays the storage drive details.

Example

The following example shows how to disable security on a controller:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # disable-controller-security

Note: this operation will fail if any secured drives are present.

Are you sure you want to disable security on this controller?

Enter 'yes' to confirm -> yes

Please enter the controller's security-key -> testSecurityKey savbu-stordev-dn1-2-cimc /chassis/storageadapter # show detail

PCI Slot SLOT-HBA:

Controller is Secured: 0

Server /chassis/storageadapter #

Modifying Controller Security Settings

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # modify-controller-security

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

At this point, you are prompted to enter the current security key, option to choose whether you want to reset the key-id and the new security key. Enter the appropriate information.

At the confirmation prompt, enter y (yes) to confirm, or n (no) to cancel the operation.

Example

The following example shows how to modify the security settings of a controller:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # modify-controller-security

230

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

Managing Storage Adapters

Verifying the Security Key Authenticity

Please enter current security-key --> testSecurityKey

Keep current key-id 'UCSC-MRAID12G_FHH18250010_1d85dcd3'? (y or n)--> n

Enter new key-id: NewKeyId

Will change key-id to 'NewKeyId'

Keep current security-key? (y or n)--> y

Server /chassis/storageadapter #

Verifying the Security Key Authenticity

If you are not sure about the security key, you can use this procedure to verify whether the security key that you provide matches the controller security key.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # verify-controller-security-key

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

At the prompt, enter the security key and press

Enter.

If you enter a security key that does not match the controller security key, a verification failure message appears.

Example

The following example shows how to verify the security key of a controller:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # verify-controller-security-key

Please enter the security key to verify -> WrongSecurityKey verify-controller-security-key failed.

Error: "r-type: RAID controller: SLOT-HBA command-status: Lock key from backup failed verification" savbu-stordev-dn1-2-cimc /chassis/storageadapter # savbu-stordev-dn1-2-cimc /chassis/storageadapter # verify-controller-security-key

Please enter the security key to verify -> testSecurityKey

Server /chassis/storageadapter #

Switching Controller Security From Remote to Local Key Management

This task allows you to switch controller security from local management to remote management, and from remote to local management.

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

231

Managing Storage Adapters

Switching Controller Security From Local to Remote Key Management

Before you begin

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

• KMIP must be enabled.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server # scope chassis

Purpose

Enters chassis command mode.

Server /chassis # scope storageadapter Slot-ID Enters storage adapter command mode.

Server /chassis/storageadapter # switch-to-local-key-mgmt

Enter

Note y at the confirmation prompt.

If you have multiple controller you must switch the security on those as well.

Server /chassis/server/storageadapter # key id Enter the new key ID at the prompt. Switches to local key management.

Example

The following example shows how to switch controller security from remote to local key management:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-HBA 1

Server /chassis/storageadapter # switch-to-local-key-mgmt

Executing this command will require you to disable remote key management once switch is complete.

Do you want to continue(y or n)?

Proceeding to switch to local key management.

Enter new security-key: test

Will change security-key to 'test'

Switch to local key management complete on controller in SLOT-HBA.

***Remote key management needs to be disabled***

Please disable remote key management.

Server /chassis/server/storageadapter #

What to do next

After you switch from Remote to Local Key Management, ensure that you disable KMIP secure key management.

Switching Controller Security From Local to Remote Key Management

This task allows you to switch controller security from local management to remote management, and from remote to local management.

Before you begin

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

232

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

Managing Storage Adapters

Deleting a Virtual Drive

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server # scope chassis

Purpose

Enters chassis command mode.

Server /chassis # scope storageadapter Slot-ID Enters storage adapter command mode.

Server /chassis/storageadapter # switch-to-remote-key-mgmt

Server /chassis/storageadapter # security id

Enter y at the confirmation prompt.

Enter the security key at the prompt. Switches to remote key management.

Example

The following example shows how to switch controller security from local to remote key management:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-HBA 1

Server /chassis/server/storageadapter # switch-to-remote-key-mgmt

Changing the security key requires existing security key.

Please enter current security-key --> test

Switch to remote key management complete on controller in SLOT-HBA.

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

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Server /chassis/storageadapter # scope

virtual-drive drive-number

Enters command mode for the specified virtual drive.

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

You are prompted to confirm the action. Enter yes to confirm.

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

233

Managing Storage Adapters

Initializing a Virtual Drive

Command or Action Purpose

Note If you do not enter yes , the action is aborted.

Example

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

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

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # scope

virtual-drive drive-number

Enters command mode for an installed storage card.

Enters command mode for the specified virtual drive.

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

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

Initializes the specified virtual drive.

(Optional) Cancels the initialization of the specified virtual drive.

Server /chassis/storageadapter/physical-drive

# get-operation-status

Displays the status of the task that is in progress on the drive.

Example

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

234

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

Managing Storage Adapters

Set as Boot Drive

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 #

Set as Boot Drive

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # scope

virtual-drive drive-number

Enters command mode for an installed storage card.

Enters command mode for the specified virtual drive.

Server /chassis/storageadapter # set-boot-drive Specifies the controller to boot from this virtual drive.

Example

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

Server /chassis/storageadapter/virtual-drive # set-boot-drive

Are you sure you want to set virtual drive 3 as the boot drive?

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter/virtual-drive #

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

235

Managing Storage Adapters

Editing a Virtual Drive

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot

Server chassis /storageadapter # scope

virtual-drive drive number

Enters command mode for an installed storage card.

Enters command mode for the specified virtual drive.

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

Prompts you to select a different current policy.

Server chassis /storageadapter /virtual-drive#

set raid-level value

Specifies the RAID level for the specified virtual drive.

Server chassis /storageadapter /virtual-drive#

set physical-drive value

Specifies the physical drive for the specified virtual drive.

Example

This example shows to edit a virtual drive:

Server# scope chassis

Server /chassis # scope storageadapter slot-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive # set raid-level 1

Server /chassis/storageadapter/virtual-drive *# physical-drive 1

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

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

Current write policy: Write Back Good BBU

0: Write Through

1: Write Back Good BBU

2: Always Write Back

Choose number from above options--> 0

The following attribute will be modified:

- Write Policy: Write Through

OK? (y or n)--> y

Server /chassis/storageadapter/virtual-drive #

236

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

Managing Storage Adapters

Securing a Virtual Drive

Important This task secures all the VDs in an existing drive group, where virtual-drive is the target ID of a virtual drive in the drive group.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Server /chassis/storageadapter # scope

virtual-drive drive-number

Enters command mode for the specified virtual drive.

Server /chassis/storageadapter/virtual-drive # secure-drive-group

You are prompted to confirm the action. Enter yes to confirm.

Note If you do not enter aborted.

yes , the action is

Example

This example shows how to secure the virtual drive group.

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive # secure-drive-group

This will enable security for virtual drive 16, and all virtual drives sharing this drive group.

It is not reversible.

Are you quite certain you want to do this?

Enter 'yes' to confirm -> yes server /chassis/storageadapter/virtual-drive # show detail

Virtual Drive 16:

FDE Capable: 1

FDE Enabled: 1

server /chassis/storageadapter/virtual-drive #

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

237

Managing Storage Adapters

Modifying Attributes of a Virtual Drive

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot Enters command mode for an installed storage card.

Server /chassis/storageadapter # scope

virtual-drive 3

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

Enters the command mode for the virtual drive.

Prompts you to select a different current policy.

Example

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 #

238

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

Managing Storage Adapters

Making a Dedicated Hot Spare

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # scope

physical-drive drive-number

Enters command mode for an installed storage card.

Enters command mode for the specified physical drive.

Server /chassis/storageadapter/physical-drive

# make-dedicated-hot-spare

You are prompted to choose a virtual drive for which the dedicated hot spare is being created.

Example

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

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.

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

239

Managing Storage Adapters

Preparing a Drive for Removal

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Server /chassis/storageadapter # scope

physical-drive drive-number

Enters command mode for an installed storage card.

Enters command mode for the specified physical drive.

Server /chassis/storageadapter/physical-drive

# make-global-hot-spare

Server /chassis/storageadapter/physical-drive

# get-operation-status

Displays the status of the task that is in progress on the drive.

Example

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.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # scope

physical-drive drive-number

Server /chassis/storageadapter/physical-drive

# prepare-for-removal

Enters command mode for an installed storage card.

Enters command mode for the specified physical drive.

240

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

Managing Storage Adapters

Toggling Physical Drive Status

Example

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 #

Toggling Physical Drive Status

Before you begin

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

• The controller must support the JBOD mode and the JBOD mode must be enabled.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Server /chassis/storageadapter # scope physical-drive 4

Server /chassis/storageadapter/physical-drive

# make-unconfigured-good

Enters command mode for the physical drive.

Modifies the status of the drive to Unconfigured good.

Server /chassis/storageadapter/physical-drive

# make-jbod

Enables the JBOD mode on the physical drive.

Example

This example shows how to toggle between the status of the physical drive:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 4

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

Physical Drive Number 4:

Controller: SLOT-4

Health: Good

Status: JBOD

Boot Drive: true

Manufacturer: ATA

Model: ST500NM0011

Predictive Failure Count: 0

Drive Firmware: CC02

Coerced Size: 476416 MB

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

241

Managing Storage Adapters

Setting a Physical Drive as a Controller Boot Drive

Type: HDD

Server /chassis/storageadapter/physical-drive # make-unconfigured-good

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

Physical Drive Number 4:

Controller: SLOT-4

Health: Good

Status: Unconfigured Good

Boot Drive: true

Manufacturer: ATA

Model: ST500NM0011

Predictive Failure Count: 0

Drive Firmware: CC02

Coerced Size: 476416 MB

Type: HDD

Server /chassis/storageadapter/physical-drive # make-jbod

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

Physical Drive Number 4:

Controller: SLOT-4

Health: Good

Status: JBOD

Boot Drive: true

Manufacturer: ATA

Model: ST500NM0011

Predictive Failure Count: 0

Drive Firmware: CC02

Coerced Size: 476416 MB

Type: HDD

Setting a Physical Drive as a Controller Boot Drive

Before you begin

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

• The controller must support the JBOD mode and the JBOD mode must be enabled.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Server /chassis/storageadapter # scope physical-drive 4

Server /chassis/storageadapter/physical-drive

# set-boot-drive

Enters command mode for the physical drive.

You are prompted to confirm the action. Enter yes to confirm.

Note If you do not enter yes , the action is aborted.

242

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

Managing Storage Adapters

Removing a Drive from Hot Spare Pools

Example

This example shows how to set a physical drive as a boot drive for a controller:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # show detail

PCI Slot SLOT-4:

Health: Good

Controller Status: Optimal

ROC Temperature: Not Supported

Product Name: MegaRAID 9240-8i (RAID 0,1,10,5)

Serial Number: SP23807413

Firmware Package Build: 20.11.1-0159

Product ID: LSI Logic

Battery Status: no battery

Cache Memory Size: 0 MB

Boot Drive: none

Boot Drive is PD: false

TTY Log Status: Not Downloaded

Server /chassis/storageadapter # scope physical-drive 4

Server /chassis/storageadapter/physical-drive # set-boot-drive

Are you sure you want to set physical drive 4 as the boot drive?

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter/physical-drive # exit

Server /chassis/storageadapter # show detail

PCI Slot SLOT-4:

Health: Good

Controller Status: Optimal

ROC Temperature: Not Supported

Product Name: MegaRAID 9240-8i (RAID 0,1,10,5)

Serial Number: SP23807413

Firmware Package Build: 20.11.1-0159

Product ID: LSI Logic

Battery Status: no battery

Cache Memory Size: 0 MB

Boot Drive: 4

Boot Drive is PD: true

TTY Log Status: Not Downloaded

Removing a Drive from Hot Spare Pools

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

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

243

Managing Storage Adapters

Undo Preparing a Drive for Removal

Step 3

Step 4

Command or Action

Server /chassis/storageadapter # scope

physical-drive drive-number

Purpose

Enters command mode for the specified physical drive.

Server /chassis/storageadapter/physical-drive

# remove-hot-spare

Removes a drive from the host spare pool.

Example

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 #

Undo Preparing a Drive for Removal

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # scope

physical-drive drive-number

Server /chassis/storageadapter/physical-drive

# undo-prepare-for-removal

Enters command mode for an installed storage card.

Enters command mode for the specified physical drive.

Example

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 #

244

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

Managing Storage Adapters

Enabling Auto Learn Cycles for the Battery Backup Unit

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter #

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

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Enter the battery backup unit command mode.

Enables the battery auto-learn cycles

Example

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

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # scope bbu

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Enter the battery backup unit command mode.

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

245

Managing Storage Adapters

Starting a Learn Cycle for a Battery Backup Unit

Step 4

Command or Action

Server /chassis/storageadapter # disable-auto-learn

Purpose

Disables the battery auto-learn cycles

Example

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.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter #

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

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Enter the battery backup unit command mode.

Starts the learn cycle for the battery.

Example

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 #

246

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

Managing Storage Adapters

Toggling the Locator LED for a Physical Drive

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # scope storageadapter slot Enters command mode for an installed storage card.

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive

# locator-led { on | off }

Enters the physical drive command mode.

Enables or disables the physical drive locator

LED.

Example

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 #

Viewing Storage Controller Logs

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter slot

Server /chassis/storageadapter # show log

Purpose

Enters the chassis command mode.

Enters command mode for an installed storage card.

Displays the storage controller logs.

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

247

Managing Storage Adapters

Viewing NVMe Controller Details

Example

This example shows how to display storage controller logs:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # show log

Time Severity

-----------

Fri March 1 09:52:19 2013 Warning

Fri March 1 07:50:19 2013 Info

Fri March 1 07:48:19 2013 Info

Fri March 1 07:47:19 2013 Info

Fri March 1 07:45:19 2013 Info

Server /chassis/storageadapter #

Description

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

Predictive Failure

Battery charge complete

Battery charge started

Battery relearn complete

Battery is discharging

Battery relearn started

Viewing NVMe Controller Details

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis # show nvmeadapter

Server /chassis/nvmeadapter # scope

nvmeadapter NVMe Adapter Name

Server /chassis/nvmeadapter # show detail

Purpose

Enters the chassis command mode.

Displays the available NVMe adapters.

Enters the chosen NVMe adapter command mode.

Displays the NVMe controller details.

Example

This example shows how to view the controller information:

Server# scope chassis

Server /chassis # show nvmeadapter

PCI Slot

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

NVMe-direct-U.2-drives

PCIe-Switch

Server /chassis # scope nvmeadapter PCIe-Switch

Server /chassis/nvmeadapter # show detail

PCI Slot: PCIe-Switch

Health: Good

Drive Count: 8

Vendor ID: MICROSEM

Product ID: PFX 48XG3

Component ID: 8533

Product Revision: RevB

P2P Vendor ID: f811

P2P Device ID: efbe

248

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

Managing Storage Adapters

Viewing NVMe Physical Drive Details

Running Firmware Version: 1.8.0.58-24b1

Pending Firmware Version: 1.8.0.58

Switch temperature: 49 degrees C

Switch status: Optimal

Link Status: Optimal

Server /chassis/nvmeadapter #

Viewing NVMe Physical Drive Details

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope chassis

Server /chassis # show nvmeadapter

Server /chassis/nvmeadapter # scope

nvmeadapter NVMe Adapter Name

Purpose

Enters the chassis command mode.

Displays the available NVMe adapters.

Enters the chosen NVMe adapter command mode.

Server /chassis/nvmeadapter # show nvme-physical-drive

Server /chassis/nvmeadapter # scope

nvme-physical-drive Physical Drive Number

Displays the available physical drives.

Enters the chosen physical drive command mode.

Server

/chassis/nvmeadapter/nvme-physical-drive # show detail

Displays the NVMe physical drive details.

Example

This example shows how to view the physical drive information:

Server# scope chassis

Server /chassis # scope nvmeadapter NVMe-direct-U.2-drives

Server /chassis/nvmeadapter # show nvme-physical-drive

Physical Drive Number Product Name Manufacturer Serial Number Temperature % Drive Life Used

Performance Level LED Fault status % Power on Hours

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

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

REAR-NVME-1 Ci... HGST

Healthy. Driv... 2

SDM00000E5EC 48 degre... 3 100

100 REAR-NVME-2

Healthy

Ci... HGST

SDM00000DC90 47 degre... 2

Server /chassis/nvmeadapter # scope nvme-physical-drive REAR-NVME-1

Server /chassis/nvmeadapter/nvme-physical-drive # show detail

Physical Drive Number REAR-NVME-1:

Product Name: Cisco UCS (SN200) 2.5 inch 800 GB NVMe based PCIe SSD

Manufacturer: HGST

Serial Number: SDM00000E5EC

Temperature: 48 degrees C

% Drive Life Used: 3

Performance Level: 100

LED Fault status: Healthy. Drive is overused based on current write pattern

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

249

Managing Storage Adapters

Viewing SIOC NVMe Drive Details

% Power on Hours: 2

Firmware Revision:

PCI Slot: REAR-NVME-1

Managed Id: 10

Controller Type: NVME-SFF

Controller Temperature: 48 degrees C

Fault State: 0

Throttle Start Temperature: 70 degrees C

Shutdown Temperature: 75 degrees C

Server /chassis/nvmeadapter/nvme-physical-drive #

Viewing SIOC NVMe Drive Details

You must scope to a particular CMC to view the NVMe drives in SIOC associated with that CMC.

Note This feature is available only on some S-Series servers.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server # scope chassis

Server /chassis # scope cmc [1 | 2]

Server /chassis/CMC # scope nvmeadapter adapter name

Server /chassis/CMC/nvmeadapter # show nvme-physical-drive detail

Purpose

Enters the chassis command mode.

Enters the CMC command mode.

Enters the NVMe adapter command mode.

Displays the SIOC NVMe physical drive details.

Example

This example shows how to view SIOC NVMe drive details:

Server # scope chassis

Server /chassis # scope cmc

Server /chassis/cmc # show detail

Firmware Image Information:

ID: 1

Name: CMC1

SIOC PID: UCS-S3260-PCISIOC

Serial Number: FCH21277K8T

Update Stage: ERROR

Update Progress: OS_ERROR

Current FW Version: 4.0(0.166)

FW Image 1 Version: 0.0(4.r17601)

FW Image 1 State: BACKUP INACTIVATED

FW Image 2 Version: 4.0(0.166)

FW Image 2 State: RUNNING ACTIVATED

Reset Reason: ac-cycle

Secure Boot: ENABLED

Server /chassis # scope cmc 1

250

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

Managing Storage Adapters

Viewing PCI Switch Details

Server /chassis/cmc # scope nvmeadapter NVMe-direct-U.2-drives

Server /chassis/cmc/nvmeadapter # show nvme-physical-drive detail

Physical Drive Number SIOCNVMe1 :

Product Name: Cisco 2.5 inch 1TB Intel P4501 NVMe Med. Perf. Value Endurance

Manufacturer: Intel

Serial Number: PHLF7303008G1P0KGN

Temperature: 39 degrees C

% Drive Life Used: 1

Performance Level: 100

LED Fault status: Healthy

Drive Status: Optimal

% Power on Hours: 8

Firmware Version: QDV1CP03

PCI Slot: SIOCNVMe1

Managed Id: 1

Controller Type: NVME-SFF

Controller Temperature: 39

Throttle State: 0

Throttle Start Temperature: 70

Shutdown Temperature: 80

Physical Drive Number SIOCNVMe2 :

Product Name: Cisco 2.5 inch 500GB Intel P4501 NVMe Med. Perf. Value Endurance

Manufacturer: Intel

Serial Number: PHLF73440068500JGN

Temperature: 39 degrees C

% Drive Life Used: 1

Performance Level: 100

LED Fault status: Healthy

Drive Status: Optimal

% Power on Hours: 7

Firmware Version: QDV1CP03

PCI Slot: SIOCNVMe2

Managed Id: 2

Controller Type: NVME-SFF

Controller Temperature: 39

Throttle State: 0

Throttle Start Temperature: 70

Shutdown Temperature: 80

Server /chassis/cmc/nvmeadapter #

Viewing PCI Switch Details

This feature is available only on some C-Series servers.

Procedure

Step 1

Step 2

Command or Action

Server # scope chassis

Server /chassis # show pci-switch

Step 3 Server /chassis # show pci-switch detail

Purpose

Enters the chassis command mode.

Displays the list of PCI switches available in the system.

Displays the details of the PCI switches available in the system.

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

251

Viewing PCI Switch Details

Example

This example shows how to view PCI Switch details:

Server # scope chassis

Server /chassis # show pci-switch

Slot-ID Product Name Manufacturer

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

PCI-Switch-1

PCI-Switch-2

PEX 8764

PLX

PCI-Switch-3

PCI-Switch-4

PEX 8764

Server /chassis # show pci-switch detail

PCI SWITCH:

Slot-ID: PCI-Switch-1

Product Name: PEX 8764

Product Revision: 0xab

Manufacturer: PLX

Device Id: 0x8764

Vendor Id: 0x10b5

Sub Device Id: 0x8764

Sub Vendor Id: 0x10b5

Temperature: 43

Composite Health: Good

Adapter Count: 3

PCI SWITCH:

Slot-ID: PCI-Switch-2

Product Name: PEX 8764

Product Revision: 0xab

Manufacturer: PLX

Device Id: 0x8764

Vendor Id: 0x10b5

Sub Device Id: 0x8764

Sub Vendor Id: 0x10b5

Temperature: 43

Composite Health: Good

Adapter Count: 3

PCI SWITCH:

Slot-ID: PCI-Switch-3

Product Name: PEX 8764

Product Revision: 0xab

Manufacturer: PLX

Device Id: 0x8764

Vendor Id: 0x10b5

Sub Device Id: 0x8764

Sub Vendor Id: 0x10b5

Temperature: 42

Composite Health: Good

Adapter Count: 3

PCI SWITCH:

Slot-ID: PCI-Switch-4

Product Name: PEX 8764

Product Revision: 0xab

Manufacturer: PLX

Device Id: 0x8764

Vendor Id: 0x10b5

Sub Device Id: 0x8764

Sub Vendor Id: 0x10b5

Temperature: 43

Composite Health: Degraded

Adapter Count: 3

C480-FCH2213WH02 /chassis #

Server /chassis/ #

252

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

Managing Storage Adapters

Viewing Details of a Particular PCI Switch

This feature is available only on some C-Series servers.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server # scope chassis

Purpose

Enters the chassis command mode.

Server /chassis # show pci-switch Displays the list of PCI switches available in the system.

Server /chassis # scope pci-switch PCI-Switch

Number

Enters the PCI switch command mode of the chosen switch.

Server /chassis/pci-switch # show detail Displays the details of the PCI switch.

Server /chassis/pci-switch # show adapter-list Displays the details of the adapters present on the PCI switch.

Example

This example shows how to view details of a particular PCI Switch:

Server # scope chassis

Server /chassis # show pci-switch

Slot-ID Product Name Manufacturer

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

PCI-Switch-1

PCI-Switch-2

PCI-Switch-3

PEX 8764

PLX

PCI-Switch-4 PEX 8764

Server /chassis # scope pci-switch PCI-Switch-1

PLX

Server /chassis/pci-switch show detail

PCI SWITCH:

Slot-ID: PCI-Switch-1

Product Name: PEX 8764

Product Revision: 0xab

Manufacturer: PLX

Device Id: 0x8764

Vendor Id: 0x10b5

Sub Device Id: 0x8764

Sub Vendor Id: 0x10b5

Temperature: 43

Composite Health: Good

Adapter Count: 3

Server /chassis/pci-switch # show adapter-list

Slot Link Status Link Speed Link Width

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

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

GPU-3

GPU-4

12 up up up

Server /chassis/pci-switch #

8.0

Status

Good

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

253

Managing Storage Adapters

Managing the Flexible Flash Controller

Cisco Flexible Flash

On the M5 servers, Flexible Flash Controller is inserted into the mini storage module socket. The mini storage socket is inserted into the M.2 slot on the motherboard. M.2 slot also supports SATA M.2 SSD slots.

Note M.2 slot does not support NVMe in this release.

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 Cisco IMC as a single hypervisor (HV) partition configuration. Prior versions had four virtual USB drives. Three were preloaded with Cisco UCS Server Configuration Utility, Cisco drivers and Cisco Host Upgrade Utility, and the fourth as user-installed hypervisor. A single HV partition configuration is also created when you upgrade to the latest version of Cisco IMC or downgrade to the prior version, and reset the configuration.

For more information about installing and configuring the M.2 drives, see the Storage Controller

Considerations (Embbeded SATA RAID Requirements) and Replacing an M.2 SSD in a Mini-Storage

Carrier For M.2

sections in the Cisco UCS Server Installation and Service Guide for the C240 M5 servers at this URL: https://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-c-series-rack-servers/ products-installation-guides-list.html

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

Card Management Feature in the Cisco Flexible Flash Controller

The Cisco Flexible Flash controller supports management of both single and two SD cards as a RAID-1 pair.

With the introduction of card management, you can perform the following tasks:

Note • If you want to upgrade from version 1.4(5e) to 1.5(4) or higher versions, you must first upgrade to version1.5(2) and then upgrade to a higher version of Cisco IMC.

• Reset the Cisco Flexible Flash controller to load the latest Flex Flash firmware after every Cisco IMC firmware upgrade.

Action

Reset Cisco Flex Flash

Reset Partition Defaults

Description

Allows you to reset the controller.

Allows you to reset the configuration in the selected slot to the default configuration.

254

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

Managing Storage Adapters

Upgrading from Single Card to Dual Card Mirroring with FlexFlash

Action

Synchronize Card Configuration

Configure Operational Profile

Description

Allows you to retain the configuration for an SD card that supports firmware version 253 and later.

Allows you to configure the SD cards on the selected

Cisco Flexible Flash controller.

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.

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

Flash controller:

Scenario

Single card

Behavior

RAID partitions are enumerated if the card is healthy, and if the mode is either Primary or

Secondary-active .

Dual paired cards

Dual unpaired cards

RAID partitions are enumerated if one of the cards is healthy.

When only one card is healthy, all read/write operations occur on this healthy card. You must use

UCS SCU to synchronize the two RAID partitions.

If this scenario is detected when the server is restarting, then neither one of the RAID partitions is enumerated.

If this scenario is detected when the server is running, when a user connects a new SD card, then the cards are not managed by the Cisco Flexible Flash controller. This does not affect the host enumeration.

You must pair the cards to manage them. You can pair the cards using the Reset Partition Defaults or

Synchronize Card Configuration options.

Upgrading from Single Card to Dual Card Mirroring with FlexFlash

You can upgrade from a single card mirroring to dual card mirroring with FlexFlash in one of the following methods:

• Add an empty FlexFlash card to the server, and then upgrade its firmware to the latest version.

• Upgrade the FlexFlash firmware to the latest version and then add an empty card to the server.

Prior to using either of these methods, you must keep in mind the following guidelines:

• To create RAID1 mirroring, the empty card that you want to add to the server must be of the exact size of the card that is already in the server. Identical card size is a must to set up RAID1 mirroring.

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

255

Managing Storage Adapters

Configuring the Flexible Flash Controller Properties for C220 M5 and C240 M5 Servers

• Ensure that the card with valid data in the Hypervisor partition is marked as the primary healthy card.

You can determine this state either in the Cisco IMC GUI or from the Cisco IMC CLI. To mark the state of the card as primary healthy, you can either use the Reset Configuration option in the Cisco IMC GUI or run the reset-config command in the Cisco IMC CLI. When you reset the configuration of a particular card, the secondary card is marked as secondary active unhealthy.

• In a Degraded RAID health state all read-write transactions are done on the healthy card. In this scenario, data mirroring does not occur. Data mirroring occurs only in the Healthy RAID state.

• Data mirroring is only applicable to RAID partitions. In the C-series servers, only Hypervisor partitions operate in the RAID mode.

• If you have not configured SD cards for use with prior versions, then upgrading to the latest version loads the latest 253 firmware and enumerates all four partitions to the host.

While upgrading versions of the FlexFlash, you may see the following error message:

Unable to communicate with Flexible Flash controller: operation ffCardsGet, status

CY_AS_ERROR_INVALID_RESPONSE”

In addition, the card status may be shown as missing . This error occurs because you accidently switched to an alternate release or a prior version, such as 1.4(x). In this scenario, you can either revert to the latest version, or you can switch back to the FlexFlash 1.4(x) configuration. If you choose to revert to the latest Cisco IMC version, then the Cisco FlexFlash configuration remains intact. If you choose to switch back to the prior version configuration, you must reset the Flexflash configuration. In this scenario, you must be aware of the following:

• If multiple cards are present, and you revert to a prior version, then the second card cannot be discovered or managed.

• If the card type is SD253, then you must run the reset-config command twice from the Cisco IMC CLI

- once to reload the old firmware on the controller and to migrate SD253 to SD247 type, and the second time to start the enumeration.

Configuring the Flexible Flash Controller Properties for C220 M5 and C240 M5

Servers

Before you begin

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

• Cisco Flexible Flash must be supported by your platform.

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexflash

Purpose

Enters the chassis command mode.

Enters the Cisco Flexible Flash controller command mode for the specified controller.

256

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

Managing Storage Adapters

Configuring the Flexible Flash Controller Properties for C220 M5 and C240 M5 Servers

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action

Server /chassis/flexflash # scope operational-profile

Purpose

Enters the operational profile command mode.

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

Specifies the number of read errors that are permitted while accessing the Cisco Flexible

Flash card in slot 1. If the number of errors exceeds this threshold, the Cisco Flexible Flash card is disabled and you must reset it manually before Cisco IMC attempts to access it again.

To specify a read error threshold, enter an integer between 1 and 255. To specify that the card should never be disabled regardless of the number of errors encountered, enter 0 (zero).

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

Specifies the number of read errors that are permitted while accessing the Cisco Flexible

Flash card in slot 2. If the number of errors exceeds this threshold, the Cisco Flexible Flash card is disabled and you must reset it manually before Cisco IMC attempts to access it again.

To specify a read error threshold, enter an integer between 1 and 255. To specify that the card should never be disabled regardless of the number of errors encountered, enter 0 (zero).

Server /chassis/flexflash/operational-profile # set write-error-count-slot2-threshold threshold

Specifies the number of write errors that are permitted while accessing the Cisco Flexible

Flash card in slot 2. If the number of errors exceeds this threshold, the Cisco Flexible Flash card is disabled and you must reset it manually before Cisco IMC attempts to access it again.

To specify a write error threshold, enter an integer between 1 and 255. To specify that the card should never be disabled regardless of the number of errors encountered, enter 0 (zero).

Server /chassis/flexflash/operational-profile # commit

Commits the transaction to the system configuration.

Example

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

Server# scope chassis

Server /chassis # scope flexflash FlexFlash-0

Server /chassis/flexflash # scope operational-profile

Server /chassis/flexflash/operational-profile # set read-err-count-slot1-threshold 9

Server /chassis/flexflash/operational-profile *# set read-err-count-slot2-threshold 10

Server /chassis/flexflash/operational-profile *# set write-err-count-slot1-threshold 11

Server /chassis/flexflash/operational-profile *# set write-err-count-slot2-threshold 12

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

257

Managing Storage Adapters

Resetting the Flexible Flash Controller

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

Server /chassis/flexflash/operational-profile # show detail

FlexFlash Operational Profile:

Firmware Operating Mode: util

SLOT1 Read Error Threshold: 9

SLOT1 Write Error Threshold: 11

SLOT2 Read Error Threshold: 10

SLOT2 Write Error Threshold: 12

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

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexflash index

Server /chassis/flexflash # reset

Purpose

Enters the chassis command mode.

Enters the Cisco Flexible Flash controller command mode for the specified controller. At this time, the only permissible index value is

FlexFlash-0 .

Resets the Cisco Flexible Flash controller.

Example

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 #

258

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

Managing Storage Adapters

Configuring the Flexible Flash Controller Cards in Mirror Mode

Configuring controller cards in mirror mode:

Before you begin

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

• Cisco Flexible Flash must be supported by your platform.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexflash

Purpose

Enters the chassis command mode.

Enters the Cisco Flexible Flash controller command mode for the specified controller.

Server /chassis/flexflash # configure-cards-mirror SLOT-1 .

Enter y at the Enable auto sync(by default auto sync is disabled)?[y|N] prompt.

Configures SLOT-1 as healthy primary.

Sync the card on slot 1 with the card on slot 2.

Enter y at the Set Mirror Partition

Name(Default name is Hypervisor)?[y|N] prompt.

Enables you to set the name of the mirror partition.

Enter the name of the mirror partition at the

Enter Partition Name Mirror Partition Name

:Hypervisor prompt.

Sets the name of the mirror partition.

Enter y at the Set Virtual Drive as non-removable (Default is removable)?[y|N] prompt.

Enables you to set the VD as non-removable.

The following message displays:

This action will mark the SLOT-1 as healthy primary slot and SLOT-2 (if card existing) as unhealthy secondary.

This operation may disturb the host connectivity as well.

Enter y at the Continue?[y|N]y prompt.

Configures the cards in Mirror mode and sets the card in SLOT-1 as primary healthy and

SLOT-2 (if card existing) as unhealthy secondary.

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

259

Managing Storage Adapters

Configuring the Flexible Flash Controller Cards in Mirror Mode

Step 9

Command or Action

(Optional) Server /chassis/flexflash # show physical-drive

Purpose

Displays the status of the configured cards.

Note •

• If the cards are configured in auto sync mode and if a card goes out of sync, then syncing from a good card starts automatically.

• If the server is running with one auto mirror healthy card and if a new card is inserted then the metadata is automatically created on the new card and data syncing starts from auto mirror configured card to the new paired card.

Example

This example shows how to configure the controller cards in mirror mode:

Server# scope chassis

Server /chassis # scope flexflash

Server /chassis/flexflash # configure-cards-mirror SLOT-1

Enable auto sync(by default auto sync is disabled)?[y|N] y

Set Mirror Partition Name(Default name is Hypervisor)?[y|N] y

Enter Partition Name Mirror Partition Name : HV

Set Virtual Drive as non-removable (Default is removable)?[y|N] y

This action will mark the SLOT-1 as healthy primary slot and SLOT-2 (if card existing) as unhealthy secondary.

This operation may disturb the host connectivity as well.

Continue?[y|N] y

Server /chassis/flexflash # show detail

Controller FlexFlash-0:

Product Name: Cisco FlexFlash

Controller HW: FX3S

Vendor: Cypress

Firmware Version: 1.3.2 build 159

Firmware Operating Mode: mirror

Firmware Configured Mode: mirror

Has Error: No

Error Description:

Internal State: Disconnected

Controller Status: OK

Cards Manageable: Yes

Startup Firmware Version: 1.3.2 build 159

Server /chassis/flexflash # show physical-drive

Physical Drive Status Controller Card Type

SLOT-1

SLOT-2

Card mode Health

Mode

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

----------

Sync present FlexFlash-0 FX3S configured mirror-primary healthy auto present FlexFlash-0 FX3S configured mirror-secondary unhealthy auto

260

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

Managing Storage Adapters

Enabling Virtual Drives

Server /chassis/flexflash #

Enabling Virtual Drives

Before you begin

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

• Cisco Flexible Flash must be supported by your platform.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexflash

Required: Server /chassis/ flexflash # scope virtual-drive

Server /chassis/flexflash/virtual-drive #

enable-vds "SCU HUU dlfd"

Purpose

Enters the chassis command mode.

Enters the Cisco Flexible Flash controller command mode for the specified controller.

Enters the virtual drive command mode for the specified controller.

Enables the virtual drives to the host.

Example

This example shows how to enable the virtual drives to the host:

Server# scope chassis

Server /chassis # scope flexflash

Server /chassis/flexflash # scope virtual-drive

Server /chassis/flexflash/virtual-drive # enable-vds "SCU HUU dlfd"

Server /chassis/flexflash/virtual-drive # show detail

Virtual Drive SCU:

VD ID: 1

Size: 2560 MB

VD Scope: Non-Raid

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Connected

Operation in progress: NA

Last Operation completion status: none

Virtual Drive HUU:

VD ID: 2

Size: 1536 MB

VD Scope: Non-Raid

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Connected

Operation in progress: NA

Last Operation completion status: none

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

261

Managing Storage Adapters

Erasing Virtual Drives

Virtual Drive Drivers:

VD ID: 3

Size: 8192 MB

VD Scope: Non-Raid

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Not-Connected

Operation in progress: NA

Last Operation completion status: none

Virtual Drive dlfd:

VD ID: 4

Size: 9952 MB

VD Scope: Non-Raid

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Connected

Operation in progress: NA

Last Operation completion status: none

Virtual Drive dfdff:

VD ID: 5

Size: 30432 MB

VD Scope: Non-Raid

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Not-Connected

Operation in progress: NA

Last Operation completion status: none

Server /chassis/flexflash/virtual-drive #

Erasing Virtual Drives

Before you begin

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

• Cisco Flexible Flash must be supported by your platform.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexflash

Required: Server /chassis/ flexflash # scope virtual-drive

Server /chassis/flexflash/virtual-drive # erase-vds "SCU HUU"

Purpose

Enters the chassis command mode.

Enters the Cisco Flexible Flash controller command mode for the specified controller.

Enters the virtual drive command mode for the specified controller.

Initiates erasing FAT32.

262

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

Managing Storage Adapters

Example

This example shows how to erase data on the virtual drives:

Server# scope chassis

Server /chassis # scope flexflash

Server /chassis/flexflash # scope virtual-drive

Server /chassis/flexflash/virtual-drive # erase-vds "SCU HUU"

Server /chassis/flexflash/virtual-drive # show detail

Virtual Drive SCU:

VD ID: 1

Size: 2560 MB

VD Scope: Non-Raid

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Not-Connected

Operation in progress: Erasing

Last Operation completion status: none

Virtual Drive HUU:

VD ID: 2

Size: 1536 MB

VD Scope: Non-Raid

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Connected

Operation in progress: Erase-Pending

Last Operation completion status: none

Virtual Drive Drivers:

VD ID: 3

Size: 8192 MB

VD Scope: Non-Raid

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Not-Connected

Operation in progress: NA

Last Operation completion status: none

Virtual Drive dlfd:

Server /chassis/flexflash/virtual-drive #

Syncing Virtual Drives

Before you begin

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

• Cisco Flexible Flash must be supported by your platform.

• The cards must be configured in manual mirror mode.

Syncing Virtual Drives

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

263

Managing Storage Adapters

Syncing Virtual Drives

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexflash

Required: Server /chassis/ flexflash # scope virtual-drive

Server /chassis/flexflash/virtual-drive #

sync-vds Hypervisor

Purpose

Enters the chassis command mode.

Enters the Cisco Flexible Flash controller command mode for the specified controller.

Enters the virtual drive command mode for the specified controller.

Syncs the virtual drives.

Note • If the cards are configured in auto sync mode and if a card goes out of sync, then syncing from a good card starts automatically.

Example

This example shows how to sync the virtual drives:

Server# scope chassis

Server /chassis # scope flexflash

Server /chassis/flexflash # scope virtual-drive

Server /chassis/flexflash/virtual-drive # sync-vds Hypervisor

Server /chassis/flexflash/virtual-drive # show detail

Virtual Drive Hypervisor:

VD ID: 1

Size: 30432 MB

VD Scope: Raid

VD Status: Degraded

VD Type: Removable

Read/Write: R/W

Host Accessible: Not-Connected

Operation in progress: Syncing(Manual)10% done

Last Operation completion status: none

Server /chassis/flexflash/virtual-drive #

264

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

Managing Storage Adapters

Viewing FlexFlash Logs

Before you begin

Cisco Flexible Flash must be supported by your platform.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexflash index

Server /chassis/flexflash # show logs

Purpose

Enters the chassis command mode.

Enters the Cisco Flexible Flash controller command mode.

Displays the Flexible Flash controller logs.

Example

An example of the Flexible Flash Controller logs.

Server # scope chassis

Server /chassis # scope chassis flexflash FlexFlash-0

Server /chassis/flexflash # show logs

TimeStamp

---------

2017 July 10 07:16:17 UTC enable=1, 3.0 mode=1"

Severity

–------warning

Description

-----------

"CYWB_LOG: CYWB: USB connection status, 3.0

warning "CYWB_LOG: CYWB: USB connection status, 3.0

2017 July 10 07:46:05 UTC enable=1, 3.0 mode=1"

2017 July 10 07:46:05 UTC event, data=1"

2017 July 10 07:45:07 UTC event, data=0"

2017 July 10 07:45:06 UTC warning warning warning

"CYWB_LOG: CYWB FWLOG (usbapp): USB HSChirp

"CYWB_LOG: CYWB FWLOG (usbapp): USB Suspend

"CYWB_LOG: CYWB FWLOG (usbapp): USB VbusValid event, data=0"

2017 July 10 07:44:23 UTC usb_state=4 ctrl_reg=0" warning

2017 July 10 07:44:23 UTC info disks: S0=0 S1=0 RAID=0 TOTAL=0" info 2017 July 10 07:44:23 UTC port=0 unit=0 usage=0"

2017 July 10 07:44:23 UTC info

"CYWB_LOG: CYWB FWLOG (usb): connect done,

"cywb_blkdev_create_disks: Finished changing

"cywbblkdev_blk_put: disk=cd3ad400 queue=cd3bd360

"cywb_blkdev_create_disks: S2 unit 0 has become unavailable"

2017 July 10 07:44:23 UTC info on port0 and 0 partitions on port 1"

2017 July 10 07:44:23 UTC

2017 July 10 07:44:23 UTC callback"

2017 July 10 07:44:23 UTC info "cywbblkdev: Added disk=cd3ad400 queue=cd3bd360 port=0 unit=0"

2017 July 10 07:44:23 UTC info "cywbblkdev: Registered block device cydiskraida with capacity 124727295 (major=254, minor=0)"

2017 July 10 07:44:23 UTC

2017 July 10 07:44:23 UTC port=0 unit=0 usage=1"

2017 July 10 07:44:23 UTC

2017 July 10 07:44:23 UTC info info info info info warning

"CYWB_LOG: Found 0 RAID partitions, 0 partitions cywb_blkdev_create_disks called

"cywb_blkdev_create_disks: Scheduling driver cywbblkdev_blk_release exit

"cywbblkdev_blk_put: disk=cd3ad400 queue=cd3bd360 cywbblkdev_blk_release entry

"CYWB_LOG: CyWb: Disk on port0, unit0 is busy,

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

265

Managing Storage Adapters

Managing the FlexUtil Controller waiting"

2017 July 10 07:44:23 UTC warning

2017 July 10 07:44:23 UTC

2017 July 10 07:44:23 UTC info info info info

2017 July 10 07:44:23 UTC info disks: S0=0 S1=0 RAID=1 TOTAL=1"

"CYWB_LOG: CYWB: No device found on storage port cywbblkdev_revalidate_disk called cywbblkdev_blk_open exit cywbblkdev_media_changed called cywbblkdev_blk_open entry

"cywb_blkdev_create_disks: Finished changing

Managing the FlexUtil Controller

The C-Series M5 Rack-Mount servers support microSD memory card for storage of server software tools and utilities. Riser 1 has this microSD memory card slot. Cisco FlexUtil supports only 32GB microSD card.

The following user visible partitions are present on the microSD card:

• Server Configuration Utility (SCU) – 1.25 GB

• Diagnostics – 0.25 GB

• Host Update Utility (HUU) – 1.5 GB

• Drivers – 8 GB

• User

Note The number of partitions and size of each partition on microSD is fixed.

At any time, two partitions can be mapped onto the host. These partitions (except the user partition ) can also be updated through a CIFS or NFS share. A second level BIOS boot order support is also available for all the bootable partitions.

Note User partition must be used only for storage. This partition does not support OS installations.

Configuring FlexUtil Operational Profiles

Before you begin

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

• Cisco FlexUtil must be supported by your platform.

Procedure

Step 1

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

266

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

Managing Storage Adapters

Resetting FlexUtil Card Configuration

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Required: Server /chassis # scope flexutil

Purpose

Enters the FlexUtil controller command mode.

Required: Server /chassis/flexutil # scope operational-profile

Enters the operational profile command mode.

Server /chassis/flexutil/operational-profile # set

read-err-count-threshold count

Sets the read error threshold count.

Note Zero value for threshold will be treated as special case, cards will not be marked unhealthy if error count crosses zero threshold.

Server /chassis/flexutil/operational-profile* #

set write-err-count-threshold count

Sets the write error threshold count.

Note Zero value for threshold will be treated as special case, cards will not be marked unhealthy if error count crosses zero threshold.

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

Commits the transaction to the system.

Example

This example shows how to configure the FlexUtil operational profile:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # scope operational-profile

Server /chassis/flexutil/operational-profile # set read-err-count-threshold 49

Server /chassis/flexutil/operational-profile* # set write-err-count-threshold 49

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

Server /chassis/flexutilServer /chassis/flexutil/operational-profile

Resetting FlexUtil Card Configuration

Before you begin

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

• Cisco FlexUtil must be supported by your platform.

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexutil

Purpose

Enters the chassis command mode.

Enters the FlexUtil controller command mode.

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

267

Managing Storage Adapters

Viewing FlexUtil Properties

Step 3

Command or Action

Server /chassis/flexutil # reset-card-config

Purpose

At the confirmation prompt enter y . Resets the

FlexUtil card configuration.

Example

This example shows how to reset the FlexUtil card configuration:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # reset-card-config

This operation will wipe all the data on the card.

Any VD connected to host (except UserPartition) will be disconnected from host.

This task will take few minutes to complete.

Do you want to continue?[y|N] y

Server /chassis/flexutil #

Viewing FlexUtil Properties

Before you begin

Cisco FlexUtil must be supported by your platform.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexutil

Server /chassis/flexutil # show detail

Purpose

Enters the chassis command mode.

Enters the FlexUtil controller command mode.

Displays the FlexUtil controller properties.

Example

This example displays the FlexUtil controller properties:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # show detail

Controller Flexutil:

Product Name: Cisco Flexutil

Internal State: Connected

Controller Status: OK

Physical Drive Count: 1

Virtual Drive Count: 5

Server /chassis/flexutil #

268

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

Managing Storage Adapters

Viewing FlexUtil Physical Drives Details

Before you begin

Cisco FlexUtil must be supported by your platform.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Required: Server /chassis # scope flexutil Enters the FlexUtil controller command mode.

Server /chassis/flexutil # show physical-drive detail

Displays the FlexUtil physical drives properties.

Example

This example displays the FlexUtil physical drives properties:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # show physical-drive detail

Physical Drive microSD:

Status: present

Controller: Flexutil

Health: healthy

Capacity: 30624 MB

Write Enabled: true

Read Error Count: 0

Read Error Threshold: 49

Write Error Count: 0

Write Error Threshold : 49

Product Name: SD32G

Product Revision: 3.0

Serial#: 0x1cafb

Manufacturer Id: 39

OEM Id: PH

Manufacturing Date : 12/2016

Block Size: 512 bytes

Partition Count: 5

Drives Enabled: SCU Diagnostics HUU Drivers UserPartition

Server /chassis/flexutil #

Viewing FlexUtil Virtual Drives Details

Before you begin

Cisco FlexUtil must be supported by your platform.

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

269

Managing Storage Adapters

Viewing FlexUtil Virtual Drives Details

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexutil

Required: Server /chassis/flexutil # scope virtual-drive

Server /chassis/flexutil/virtual-drive # show detail

Purpose

Enters the chassis command mode.

Enters the FlexUtil controller command mode.

Enters the virtual drive command mode.

Displays the FlexUtil physical drives properties.

Example

This example displays the FlexUtil physical drives properties:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # scope virtual-drive

Server /chassis/flexutil/virtual-drive # show detail

Virtual Drive SCU:

ID: 1

LUN ID: NA

Size: 1280 MB

VD Scope: Non-RAID

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Not-Connected

Operation in progress: NA

Last Operation completion status: none

Virtual Drive Diagnostics:

ID: 2

LUN ID: 0

Size: 256 MB

VD Scope: Non-RAID

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Connected

Operation in progress: NA

Last Operation completion status: none

Virtual Drive HUU:

ID: 3

LUN ID: NA

Size: 1536 MB

VD Scope: Non-RAID

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Not-Connected

Operation in progress: NA

Last Operation completion status: none

Virtual Drive Drivers:

ID: 4

LUN ID: NA

Size: 8192 MB

VD Scope: Non-RAID

VD Status: Healthy

270

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

Managing Storage Adapters

Adding an Image to a FlexUtil Virtual Drive

VD Type: Removable

Read/Write: R/W

Host Accessible: Not-Connected

Operation in progress: NA

Last Operation completion status: none

Virtual Drive UserPartition:

ID: 5

LUN ID: NA

Size: 11159 MB

VD Scope: Non-RAID

VD Status: Healthy

VD Type: Removable

Read/Write: R/W

Host Accessible: Not-Connected

Operation in progress: NA

Last Operation completion status: none

Server /chassis/flexutil/virtual-drive #

Adding an Image to a FlexUtil Virtual Drive

Before you begin

• Log in with admin privileges to perform this task.

• Cisco FlexUtil must be supported by your platform.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action server # scope chassis

Purpose

Enters chassis command mode.

Required: Server /chassis # scope flexutil

Required: Server /chassis/flexutil # scope vd-image-configs

Enters the FlexUtil controller command mode.

Enters the virtual drive image configuration command mode.

Server /chassis/flexutil/vd-image-configs # vd-image-cifs { virtual-drive-name remote-share remote-file-path [ mount options ]

Maps a CIFS file for the FlexUtil virtual drive.

You must specify the following:

• Name of the virtual drive

• Remote share including IP address (IPv4 or IPv6 address) and the exported directory

• Path of the remote file corresponding to the exported directory.

• (Optional) Mapping options

• Username and password to connect to the server

Server /chassis/flexutil/vd-image-configs # vd-image-nfs { virtual-drive-name remote-share remote-file-path [ mount options ]

Maps an NFS file for the FlexUtil virtual drive.

You must specify the following:

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

271

Managing Storage Adapters

Adding an Image to a FlexUtil Virtual Drive

Step 6

Step 7

Command or Action

Server /chassis/flexutil/vd-image-configs # vd-image-www { virtual-drive-name | remote-share | remote-file-path [ mount options ]

Server /chassis/flexutil/vd-image-configs # show detail

Purpose

• Name of the virtual drive

• Remote share including IP address (IPv4 or IPv6 address)

• Path of the remote file

• (Optional) Mapping options

Maps an HTTPS file to the virtual drive. You must specify the following:

• Name of the virtual drive to map

• Remote share including IP address and the exported directory

• Path of the remote file corresponding to the exported directory.

• (Optional) Mapping options

• Username and password to connect to the server

Displays the FlexUtil virtual drive image details.

Example

This example shows how to map an image to a FlexUtil virtual drive:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # scope vd-image-configs

Server /chassis/flexutil/vd-image-configs # vd-image-nfs HUU 10.10.10.10:/nfsdata ucs-c240m5-huu-3.1.0.182.iso

Server /chassis/flexutil/vd-image-configs # show detail

Virtual drive: SCU mount-type: nfs remote-share: 10.10.10.10:/nfsshare remote-file: ucs-cxx-scu-4.0.12.3.iso

mount-options: 'nolock,noexec,noac,soft,timeo=60,retry=2,rsize=3072,wsize=3072'

Virtual drive: Diagnostics mount-type: nfs remote-share: 10.10.10.10:/nfsshare remote-file: ucs-cxx-diag.5.0.1a.iso

mount-options: 'nolock,noexec,noac,soft,timeo=60,retry=2,rsize=3072,wsize=3072'

Virtual drive: HUU mount-type: nfs remote-share: 10.10.10.10:/nfsdata remote-file: ucs-c240m5-huu-3.1.0.182.iso

mount-options: "nolock,noexec,noac,soft,timeo=60,retry=2,rsize=3072,wsize=3072"

Virtual-drive: Drivers

272

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

Managing Storage Adapters

Updating a FlexUtil Virtual Drive mount-type: None remote-share: None remote-file: None mount-options: None

Server /chassis/flexutil/vd-image-configs #

Updating a FlexUtil Virtual Drive

Before you begin

• You must be logged in with admin privileges to perform this task.

• Cisco FlexUtil must be supported by your platform.

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Procedure

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexutil

Purpose

Enters the chassis command mode.

Enters the FlexUtil controller command mode.

Required: Server /chassis/flexutil # scope virtual-drive

Server /chassis/flexutil/virtual-drive #

update-vds virtual-drive

Enters the virtual drive command mode.

Updates the chosen virtual drive.

(Optional) Server /chassis/flexutil/virtual-drive

# update-vds-cancel

Cancels an ongoing virtual drive update.

Server /chassis/flexutil/virtual-drive # show detail

Displays the FlexUtil virtual drive image details.

Example

This example shows how to updates a FlexUtil virtual drive:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # scope virtual-drive

Server /chassis/flexutil/virtual-drive # update-vds HUU

Server /chassis/flexutil/virtual-drive # show detail

Virtual-drive: SCU partition-id: 1 lun-id: NA size: 1280 MB partition-scope: Non-RAID partition-status: Healthy partition-type: Removable writable: R/W host-accessible: Not-Connected operation-in-progress: NA operation-completion-status: none

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

273

Enabling FlexUtil Virtual Drive

Virtual-drive: Diagnostics partition-id: 2 lun-id: NA size: 256 MB partition-scope: Non-RAID partition-status: Healthy partition-type: Removable writable: R/W host-accessible: Not-Connected operation-in-progress: NA operation-completion-status: none

Virtual-drive: HUU partition-id: 3 lun-id: NA size: 1536 MB partition-scope: Non-RAID partition-status: Healthy partition-type: Removable writable: R/W host-accessible: Not-Connected operation-in-progress: Updating operation-completion-status: none

Virtual-drive: Drivers partition-id: 4 lun-id: NA size: 8192 MB partition-scope: Non-RAID partition-status: Healthy partition-type: Removable writable: R/W host-accessible: Not-Connected operation-in-progress: NA operation-completion-status: none

Virtual drive: UserPartition partition-id: 5 lun-id: NA size: 11159 MB partition-scope: Non-RAID partition-status: Healthy partition-type: Removable writable: R/W host-accessible: Not-Connected operation-in-progress: NA operation-completion-status: none

Server /chassis/flexutil/virtual-drive #

Enabling FlexUtil Virtual Drive

Before you begin

• You must be logged in with admin privileges to perform this task.

• Cisco FlexUtil must be supported by your platform.

• Update the virtual drive image before maping the drive to a host.

Managing Storage Adapters

274

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

Managing Storage Adapters

Mapping an Image to a Virtual Drive

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexutil

Required: Server /chassis/flexutil # scope virtual-drive

Server /chassis/flexutil/virtual-drive #

enable-vds virtual-drive

Server /chassis/flexutil/virtual-drive # show detail

Purpose

Enters the chassis command mode.

Enters the FlexUtil controller command mode.

Enters the virtual drive command mode.

Maps the virtual drive to host.

Displays the FlexUtil virtual drive image details.

Example

This example shows how to map a virtual drive image to a host:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # scope virtual-drive

Server /chassis/flexutil/virtual-drive # enable-vds HUU

Server /chassis/flexutil/virtual-drive # show detail

Virtual Drive ID LUN ID Size VD Status Host Accessible Operation in

Operation progress completion status

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

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

SCU 1 NA 1280 MB Healthy Not-Connected NA none

Diagnostics

Update-Success

2 0 256 MB Healthy Connected NA

HUU

Update-Success

Drivers

3 1 1536 MB Healthy

4 NA 8192 MB Healthy

UserPartition 5 NA 11159 MB Healthy

Server /chassis/flexutil/vd-image-configs #

Connected

Not-Connected

Last none none

Mapping an Image to a Virtual Drive

Before you begin

• You must be logged in with admin privileges to perform this task.

• Cisco FlexUtil must be supported by your platform.

Procedure

Step 1

Step 2

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexutil

Purpose

Enters the chassis command mode.

Enters the FlexUtil controller command mode.

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

275

Managing Storage Adapters

Unmapping an Image From a Virtual Drive

Step 3

Step 4

Step 5

Command or Action

Required: Server /chassis/flexutil # scope vd-image-configs

Purpose

Enters the virtual drive image configuration command mode.

Required: /chassis/flexutil/vd-image-configs #

vd-image-nfs HUU nfs/cifs share IP and path

ISO image file

Specify the IP and the path of the nfs/cifs share, and the ISO image file.

/chassis/flexutil/vd-image-configs # show detail

Displays the FlexUtil virtual drive image details.

Example

This example shows how to add an image to a FlexUtil virtual drive:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # scope vd-image-configs

Server /chassis/flexutil/vd-image-configs # vd-image-nfs HUU 10.127.54.176:/nfsdata ucs-c240m5-huu-3.1.0.182.iso

Server /chassis/flexutil/vd-image-configs # show detail virtual-drive: SCU mount-type: nfs remote-share: 10.104.236.81:/nfsshare remote-file: ucs-cxx-scu-4.0.12.3.iso

mount-options: 'nolock,noexec,noac,soft,timeo=60,retry=2,rsize=3072,wsize=3072' virtual-drive: Diagnostics mount-type: nfs remote-share: 10.104.236.81:/nfsshare remote-file: ucs-cxx-diag.5.0.1a.iso

mount-options: 'nolock,noexec,noac,soft,timeo=60,retry=2,rsize=3072,wsize=3072' virtual-drive: HUU mount-type: nfs remote-share: 10.127.54.176:/nfsdata remote-file: ucs-c240m5-huu-3.1.0.182.iso

mount-options: "nolock,noexec,noac,soft,timeo=60,retry=2,rsize=3072,wsize=3072" virtual-drive: Drivers mount-type: None remote-share: None remote-file: None mount-options: None

Server /chassis/flexutil/vd-image-configs

Unmapping an Image From a Virtual Drive

Before you begin

• You must be logged in with admin privileges to perform this task.

276

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

Managing Storage Adapters

Unmapping an Image From a Virtual Drive

• Cisco FlexUtil must be supported by your platform.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexutil

Required: Server /chassis/flexutil # scope vd-image-configs

Server /chassis/flexutil/vd-image-configs #

unmap virtual-drive

Server /chassis/flexutil/vd-image-configs # show detail

Purpose

Enters the chassis command mode.

Enters the FlexUtil controller command mode.

Enters the virtual drive image configuration command mode.

Unmaps the chosen virtual drive image.

Displays the FlexUtil virtual drive image details.

Example

This example shows how to unmap a FlexUtil virtual drive:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # scope vd-image-configs

Server /chassis/flexutil/vd-image-configs # unmap HUU

Server /chassis/flexutil/vd-image-configs # show detail

Virtual drive: SCU mount-type: nfs remote-share: 10.10.10.10:/nfsshare remote-file: ucs-cxx-scu-4.0.12.3.iso

mount-options: 'nolock,noexec,noac,soft,timeo=60,retry=2,rsize=3072,wsize=3072'

Virtual drive: Diagnostics mount-type: nfs remote-share: 10.10.10.10:/nfsshare remote-file: ucs-cxx-diag.5.0.1a.iso

mount-options: 'nolock,noexec,noac,soft,timeo=60,retry=2,rsize=3072,wsize=3072'

Virtual drive: HUU mount-type: None remote-share: None remote-file: None mount-options: None

Virtual-drive: Drivers mount-type: None remote-share: None remote-file: None mount-options: None

Server /chassis/flexutil/vd-image-configs #

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

277

Managing Storage Adapters

Erasing an Image on a Virtual Drive

Before you begin

• You must be logged in with admin privileges to perform this task.

• Cisco FlexUtil must be supported by your platform.

Step 1

Step 2

Step 3

Step 4

Step 5

Procedure

Command or Action

Server# scope chassis

Required: Server /chassis # scope flexutil

Purpose

Enters the chassis command mode.

Enters the FlexUtil controller command mode.

Required: Server /chassis/flexutil # scope virtual-drive

Enters the virtual drive command mode.

Server /chassis/flexutil/virtual-drive # erase-vds virtual-drive

Erases a virtual drive image.

Server /chassis/flexutil/virtual-drive # show detail

Displays the FlexUtil virtual drive image details.

Example

This example shows how to erase a virtual drive image:

Server# scope chassis

Server /chassis # scope flexutil

Server /chassis/flexutil # scope virtual-drive

Server /chassis/flexutil/virtual-drive # erase-vds SCU

This operation will erase data on the VD

Continue?[y|N] y

Server /chassis/flexutil/virtual-drive # show detail

Virtual Drive ID

Operation

LUN ID Size VD Status progress completion status

Host Accessible Operation in

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

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

SCU

Diagnostics

Update-Success

1280 MB

256 MB

Healthy

Not-Connected

Connected

Erasing

Connected NA HUU

Update-Success

3 1 1536 MB Healthy

Drivers 4

UserPartition 5

8192 MB Healthy

11159 MB Healthy

C220-WZP210606A7 /chassis/flexutil/virtual-drive #

Not-Connected

Last none none none

278

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

Managing Storage Adapters

Cisco Boot Optimized M.2 Raid Controller

Viewing Cisco Boot Optimized M.2 Raid Controller Details

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis #

MSTOR-RAID scope storageadapter

Purpose

Enters the chassis command mode.

Enters the Cisco Boot Optimized M.2 raid controller command mode.

Server /chassis/storageadapter # show detail Displays the Cisco Boot Optimized M.2 raid controller details.

Example

This example shows how to view the controller information:

Server# scope chassis

Server /chassis # show storageadapter MSTOR-RAID

Server /chassis/storageadapter # show detail

PCI Slot MSTOR-RAID:

Health: Good

Controller Status: Optimal

Product Name: Cisco Boot optimized M.2 Raid controller

Serial Number: FCH222877A7

Firmware Package Build: 2.3.17.1009

Product ID: Marvell

Flash Memory Size: 2 MB

Product PID: UCS-M2-HWRAID

Server /chassis/storageadapter #

Viewing Cisco Boot Optimized M.2 Raid Controller Physical Drive Details

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis #

MSTOR-RAID scope storageadapter

Purpose

Enters the chassis command mode.

Enters the Cisco Boot Optimized M.2 raid controller command mode.

Server /chassis/storageadapter # scope

physical-drive Physical Drive Number

Server /chassis/storageadapter/physical-drive

# show general

Enters the physical drive command mode.

Displays the general physical drive information.

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

279

Managing Storage Adapters

Viewing Cisco Boot Optimized M.2 Raid Controller Physical Drive Details

Step 5

Step 6

Step 7

Command or Action

Server /chassis/storageadapter/physical-drive

# show detail

Server /chassis/storageadapter/physical-drive

# show inquiry-data

Server /chassis/storageadapter/physical-drive

# show status

Purpose

Displays the physical drive details.

Displays the physical drive serial number.

Displays the health status of the physical drive.

Example

This example shows how to view the physical drive information:

Server# scope chassis

Server /chassis # show storageadapter MSTOR-RAID

Server /chassis/storageadapter # scope physical-drive 253

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

PCI Slot MSTOR-RAID:

Health: Good

Controller Status: Optimal

Product Name: Cisco Boot optimized M.2 Raid controller

Serial Number: FCH222877A7

Firmware Package Build: 2.3.17.1009

Product ID: Marvell

Flash Memory Size: 2 MB

Product PID: UCS-M2-HWRAID

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

Physical Drive Number 253:

Controller: MSTOR-RAID

Info Valid: Yes

Info Invalid Cause:

Drive Number: 253

Health: Good

Status: Online

Manufacturer: ATA

Model: Micron_5100_MTFDDAV240TCB

Drive Firmware: D0MU054

Type: SSD

Block Size: 512

Physical Block Size: 512

Negotiated Link Speed: 6.0 Gb/s

State: online

Operating Temperature: 32

Enclosure Association: Direct Attached

Interface Type: SATA

Block Count: 468862127

Raw Size: 228936 MB

Non Coerced Size: 228936 MB

Coerced Size: 228936 MB

Power State: active

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

Physical Drive Number 253:

Controller: MSTOR-RAID

Info Valid: Yes

Info Invalid Cause:

Vendor: ATA

Product ID: Micron_5100_MTFDDAV240TCB

Drive Firmware: D0MU054

Drive Serial Number: 18201CB94A2C

280

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

Managing Storage Adapters

Viewing Cisco Boot Optimized M.2 Raid Controller Virtual Drive Details

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

Physical Drive Number 253:

Controller: MSTOR-RAID

Info Valid: Yes

Info Invalid Cause:

State: online

Online: true

Fault: false

Server /chassis/storageadapter/physical-drive #

Viewing Cisco Boot Optimized M.2 Raid Controller Virtual Drive Details

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope chassis

Server /chassis #

MSTOR-RAID scope storageadapter

Purpose

Enters the chassis command mode.

Enters the Cisco Boot Optimized M.2 raid controller command mode.

Server /chassis/storageadapter # scope

virtual-drive Virtual Drive Number

Server /chassis/storageadapter/virtual-drive # show detail

Server /chassis/storageadapter/virtual-drive # show lrop-info

Enters the virtual drive command mode.

Displays the virtual drive information.

Displays the status of the virtual drive rebuild.

Example

This example shows how to view the virtual drive information:

Server# scope chassis

Server /chassis # show storageadapter MSTOR-RAID

Server /chassis/storageadapter # scope virtual-drive 0

Server /chassis/storageadapter/virtual-drive # show detail

Virtual Drive 0:

Health: Good

Status : Optimal

Name: test

Size: 228872 MB

Physical Drives: 253, 254

RAID Level: RAID 1

Target ID: 0

Strip Size: 32 KB

Server /chassis/storageadapter/virtual-drive # show detail

LROP:

LROP In Progress: false

Current Long-Running Op: No operation in progress

Percent Complete: 0

Server /chassis/storageadapter/virtual-drive #

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

281

Managing Storage Adapters

Creating a Cisco Boot Optimized M.2 Raid Controller Virtual Drive

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter

MSTOR-RAID

Server /chassis/storageadapter # create-virtual-drive

Purpose

Enters the chassis command mode.

Enters the Cisco Boot Optimized M.2 raid controller command mode.

Enters the virtual drive name and the stripsize at the respective prompts. This creates the virtual drive.

Example

This example shows how to create a virtual drive:

Server# scope chassis

Server /chassis # show storageadapter MSTOR-RAID

Server /chassis/storageadapter # create-virtual-drive

Please enter Virtual Drive name (15 characters maximum, hit return to skip name)--> test

Unused physical drives available 2:

ID Size(MB) Model

253 228936 ATA

254 915715 ATA

Interface Type

SATA SSD

PD sizes NOT equal. NOT Assigning VD_size for RAID1

Optional attribute: stripsize: defaults to 64K Bytes

0: 32K Bytes

1: 64K Bytes

Choose number from above options or hit return to pick default--> 0 stripsize will be set to 32K Bytes (4 and 'strip-size\:32k')

New virtual drive will have the following characteristics:

- RAID level: '1'

- Name: 'test'

- stripsize: 32K Bytes

OK? (y or n)--> y

Server /chassis/storageadapter #

Deleting a Cisco Boot Optimized M.2 Raid Controller Virtual Drive

Procedure

Step 1

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

282

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

Managing Storage Adapters

Importing Cisco Boot Optimized M.2 Raid Controller Foreign Configuration

Step 2

Step 3

Command or Action

Server /chassis # scope storageadapter

MSTOR-RAID

Server /chassis/storageadapter # delete-virtual-drive

Purpose

Enters the Cisco Boot Optimized M.2 raid controller command mode.

Enters yes at the confirmation prompts. This deletes the virtual drive.

Example

This example shows how to delete a virtual drive:

Server# scope chassis

Server /chassis # show storageadapter MSTOR-RAID

Server /chassis/storageadapter # delete-virtual-drive

Are you sure you want to delete virtual drive 0?

All data on the drive will be lost.

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter #

Importing Cisco Boot Optimized M.2 Raid Controller Foreign Configuration

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter

MSTOR-RAID

Server /chassis/storageadapter # import-foreign-config

Purpose

Enters the chassis command mode.

Enters the Cisco Boot Optimized M.2 raid controller command mode.

Enter yes at the confirmation prompt to import the controller configuration.

Example

This example shows how to import the controller configuration:

Server# scope chassis

Server /chassis # show storageadapter MSTOR-RAID

Server /chassis/storageadapter # import-foreign-config

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

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter #

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

283

Managing Storage Adapters

Clearing Cisco Boot Optimized M.2 Raid Controller Foreign Configuration

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis # scope storageadapter

MSTOR-RAID

Server /chassis/storageadapter # clear-foreign-config

Purpose

Enters the chassis command mode.

Enters the Cisco Boot Optimized M.2 raid controller command mode.

Enter yes at the confirmation prompt to clear the controller configuration.

Example

This example shows how to clear the controller configuration:

Server# scope chassis

Server /chassis # show storageadapter MSTOR-RAID

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 #

Cisco FlexMMC

Viewing Cisco FlexMMC Details

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server/chassis # Scope flexmmc

Server/chassis/flexmmc # show detail

Purpose

Enters the chassis command mode.

Enters the FlexMMC mode.

Displays the FlexMMC details.

Example

This example shows how to view the controller information:

Server# scope chassis

Server /chassis # scope flexmmc

Server /chassis/flexmmc # show detail

Cisco FlexMMC Storage:

Total Memory For IMC Utilities: 2048 MB

Available Memory For IMC Utilities: 1970 MB

284

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

Managing Storage Adapters

Uploading New Image File

Total Memory For User Files: 6144 MB

Available Memory For User Files: 6144 MB

Uploading New Image File

Before you begin

Ensure that there are no file upload in progress. You can upload only one image file at any time. To upload a new file, you should first un-map and delete the existing file.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server/chassis # scope flexmmc

Server/chassis/flexmmc # download-file location mount_type serverip/remote_share remote_file option_string

Purpose

Enters the chassis command mode.

Enters the FlexMMC mode.

Uploads the image file for mapping.

Example

This example shows how to upload an image file:

Server# scope chassis

Server /chassis # scope flexmmc

Server /chassis/flexmmc # download-file file location

Deleting an Image File

Before you begin

Ensure that:

• there are no file uploads in progress. You cannot delete a file for which the upload is in progress.

• there are no files mapped. You cannot delete a file which is already mapped. You should first un-map the file before deleting the file.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server/chassis # scope flexmmc

Server/chassis/flexmmc # delete-file file_ID

Purpose

Enters the chassis command mode.

Enters the FlexMMC mode.

Deletes the image file.

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

285

Managing Storage Adapters

Mapping an Image

Example

This example shows how to delete an image file:

Server# scope chassis

Server /chassis # scope flexmmc

Server /chassis/flexmmc # delete-file file ID

Mapping an Image

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server/chassis # scope flexmmc

Purpose

Enters the chassis command mode.

Enters the FlexMMC mode.

Server/chassis/flexmmc # scope flexmmc-file file_ID

Selects the file to be mapped.

Server/chassis/flexmmc/flexmmc-file # map

Example

This examples shows how to map an already uploaded image file.

Server# scope chassis

Server /chassis # scope flexmmc

Server /chassis/flexmmc # scope flexmmc-file file ID

Server /chassis/flexmmc/flexmmc-file # map

Resetting FlexMMC to Default Settings

Perform this procedure to reset FlexMMC to default Cisco IMC settings.

Note Performing this procedure deletes all the uploaded images.

Before you begin

Ensure that:

• there are no file uploads in progress. You cannot reset FlexMMC to default settings while a file upload is in progress.

• there are no files mapped. You cannot reset FlexMMC if a file is already mapped. You should first un-map the file before resetting FlexMMC.

286

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

Managing Storage Adapters

Resetting FlexMMC to Default Settings

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server/chassis # scope flexmmc

Server/chassis/flexmmc # reset-to-default

Enter yes to confirm.

Purpose

Enters the chassis command mode.

Enters the FlexMMC mode.

Resets FlexMMC to default settings.

Example

This example shows how to reset FlexMMC to default settings:

Server# scope chassis

Server /chassis # scope flexmmc

Server /chassis/flexmmc # reset-to-default

Are you sure you want to reset the Cisco FlexMMC to default? All the files will be deleted/wiped

Please enter 'yes' to confirm: yes

Server /chassis/flexmmc

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

287

Resetting FlexMMC to Default Settings

Managing Storage Adapters

288

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

C H A P T E R

Configuring Communication Services

This chapter includes the following sections:

•

Configuring HTTP, on page 289

•

Configuring SSH, on page 291

•

Configuring XML API, on page 292

•

Configuring IPMI, on page 293

•

Configuring SNMP, on page 295

Configuring HTTP

Beginning with release 4.1(2b), Cisco IMC supports separate HTTPS and HTTP communication services.

You can disable only HTTP services using this functionality.

This functionality is supported only on the following servers:

• Cisco UCS C220 M5

• Cisco UCS C240 M5

• Cisco UCS C480 M5

• Cisco UCS C480 ML M5

• Cisco UCS C240 SD M5

• Cisco UCS C125 M5

• Cisco UCS S3260 M4/M5

Note If Redirect HTTP to HTTPS Enabled was disabled in any release earlier than 4.1(2b), then after upgrading to release 4.1(2b) or later, HTTP Enabled value is set to Disabled by the system.

Before you begin

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

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

289

Configuring HTTP

Configuring Communication Services

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Command or Action

Server# scope http

Server /http # set https-enabled { yes | no }

Server /http #

Server /http # set http-enabled commit

{ yes

set http-port number

set https-port number set http-redirect { yes

set timeout seconds

| no no

}

Purpose

Enters the HTTP command mode.

Enables the HTTPS services or disables both

HTTPS and HTTP services on Cisco IMC.

Enables or disables HTTP services on the Cisco

IMC.

Sets the port to use for HTTP communication.

The default is 80.

Sets the port to use for HTTPS communication.

The default is 443.

Note This option is applicable only when

HTTP is enabled.

Enables or disables the redirection of an HTTP request to HTTPS.

Sets the number of seconds to wait between

HTTP requests before the Cisco IMC times out and terminates the session.

Enter an integer between 60 and 10,800. The default is 1,800 seconds.

Commits the transaction to the system configuration.

Example

This example configures HTTP for the Cisco IMC:

Server# scope http

Server /http # set https-enabled yes

Server /http # set http-enabled yes

Server /http *# set http-port 80

Server /http *# set https-port 443

Server /http *# set http-redirect yes

Server /http *# set timeout 1800

Server /http *# commit

Server /http # show

HTTP Port HTTPS Port Timeout Active Sessions HTTPS Enabled HTTP Redirected HT

TP Enabled

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

--------

80 443 1800 0 yes yes yes

Server /http #

290

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

Configuring Communication Services

Configuring SSH

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

Server# scope ssh

Server /ssh # set enabled { yes | no }

Server /ssh # set ssh-port number

Server /ssh #

set timeout seconds commit show [ detail ]

Purpose

Enters the SSH command mode.

Enables or disables SSH on the Cisco IMC.

Sets the port to use for secure shell access. The default is 22.

Sets the number of seconds to wait before the system considers an SSH request to have timed out.

Enter an integer between 60 and 10,800. The default is 300 seconds.

Commits the transaction to the system configuration.

(Optional) Displays the SSH configuration.

Example

This example configures SSH for the Cisco IMC:

Server# scope ssh

Server /ssh # set enabled yes

Server /ssh *# set ssh-port 22

Server /ssh *# set timeout 600

Server /ssh *# commit

Server /ssh # show

SSH Port Timeout Active Sessions Enabled

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

22 600 1 yes

Server /ssh #

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

291

Configuring Communication Services

Configuring XML API

XML API for Cisco IMC

The Cisco Cisco IMC XML application programming interface (API) is a programmatic interface to Cisco

IMC 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 Cisco IMC 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

Step 1

Step 2

Step 3

Command or Action

Server# scope xmlapi

Server /xmlapi # set enabled { yes | no }

Server /xmlapi # commit

Purpose

Enters XML API command mode.

Enables or disables XML API control of Cisco

IMC.

Commits the transaction to the system configuration.

Example

This example enables XML API control of Cisco IMC 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 #

292

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

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 Cisco IMC with IPMI messages.

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope ipmi

Server /ipmi # set enabled { yes | no }

Purpose

Enters the IPMI command mode.

Enables or disables IPMI access on this server.

Server /ipmi # set privilege-level { readonly | user | admin }

Specifies the highest privilege level that can be assigned to an IPMI session on this server. This can be:

• readonly — IPMI users can view information but cannot make any changes.

If you select this option, IPMI users with the "Administrator", "Operator", or "User" user roles can only create read-only IPMI sessions, regardless of their other IPMI privileges.

• user — IPMI users can perform some functions but cannot perform administrative tasks. If you select this option, IPMI users with the

"Administrator" or "Operator" user role can create user and read-only sessions on this server.

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

293

Configuring Communication Services

Configuring IPMI over LAN

Step 4

Step 5

Step 6

Command or Action

Server /ipmi #

set encryption-key key commit randomise-key

Purpose

• admin — IPMI users can perform all available actions. If you select this option,

IPMI users with the "Administrator" user role can create admin, user, and read-only sessions on this server.

Sets the IPMI encryption key to use for IPMI communications. The key value must be 40 hexadecimal numbers.

Commits the transaction to the system configuration.

Sets the IPMI encryption key to a random value.

Note You can perform the Step 6 action instead of Steps 4 and 5.

Sets the IPMI encryption key to a random value.

Step 7 At the prompt, enter y to randomize the encryption key.

Example

This example configures IPMI over LAN for the Cisco IMC:

Server# scope ipmi

Server /ipmi # set enabled yes

Server /ipmi *# set privilege-level admin

Server /ipmi *# set encryption-key abcdef01234567890abcdef01234567890abcdef

Server /ipmi *# commit

Server /ipmi *# show

Enabled Encryption Key Privilege Level Limit

------- ---------------------------------------- --------------------yes ABCDEF01234567890ABCDEF01234567890ABCDEF admin

Server /ipmi # randomise-key

This operation will change the IPMI Encryption Key to a random value

Continue?[y|N] y

Setting IPMI Encryption Key to a random value...

Server /ipmi # show

Enabled Encryption Key Privilege Level Limit

------- ---------------------------------------- --------------------yes abcdef01234567890abcdef01234567890abcdef admin

Server /ipmi #

294

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

Configuring Communication Services

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 Cisco IMC, see the MIB Quick

Reference for Cisco UCS at this URL: http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/mib/ b-series/b_UCS_MIBRef.html

Beginning with release 4.1(3b), Cisco IMC introduces enhanced authentication protocol for SNMP v3 version.

SNMP v3 users cannot be added with DES security protocol.

Cisco IMC GUI displays a warning when you select an existing v3 version with unsupported security level, authentication type, or privacy type. You may select and modify the user details.

Configuring SNMP Properties

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope snmp

Server /snmp # set enabled { yes | no }

Purpose

Enters SNMP command mode.

Enables or disables SNMP.

Note SNMP must be enabled and saved before additional SNMP configuration commands are accepted.

Step 3

Step 4

Step 5

Server /snmp # commit Commits the transaction to the system configuration.

Server /snmp # set enable-serial-num { yes | no }

Prefixes the traps with the serial number of the server.

Server /snmp # set snmp-port port number Sets the port number on which the SNMP agent runs. You can choose a number within the range 1 to 65535. The default port number is 161.

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

295

Configuring Communication Services

Configuring SNMP Properties

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Command or Action Purpose

Note The port numbers that are reserved for system calls, such as

22,23,80,123,443,623,389,636,3268,3269 and 2068, cannot be used as an SNMP port.

Server /snmp # set community-str community Specifies the default SNMP v1 or v2c community name that Cisco IMC includes on any trap messages it sends to the SNMP host.

The name can be up to 18 characters.

Server /snmp # set community-access

Server /snmp #

Server /snmp # set trap-community-str

set sys-contact contact

set sys-location location

This can be one of the following : Disabled,

Limited, or Full.

Specifies the SNMP community group to which trap information should be sent. The name can be up to 18 characters

Specifies the system contact person responsible for the SNMP implementation. The contact information can be up to 254 characters, such as an email address or a name and telephone number. To enter a value that contains spaces, you must enclose the entry with quotation marks.

Specifies the location of the host on which the

SNMP agent (server) runs. The location information can be up to 254 characters. To enter a value that contains spaces, you must enclose the entry with quotation marks.

Server /snmp # commit Commits the transaction to the system configuration.

Example

This example configures the SNMP properties and commits the transaction:

Server# scope snmp

Server /snmp # set enabled yes

Server /snmp *# commit

Server /snmp *# set enable-serial-num yes

Server /snmp *# set snmp-port 20000

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 <[email protected]> +1-408-555-1212"

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

Server /snmp *# commit

Server /snmp # show detail

SNMP Settings:

SNMP Port: 20000

296

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

Configuring Communication Services

Configuring SNMP Trap Settings

System Contact: User Name <[email protected]> +1-408-555-1212

System Location: San Jose, California

SNMP Community: cimcpublic

SNMP Trap Community: public

SNMP Community access: Full

Enabled: yes

Serial Number Enabled: yes

Server /snmp #

What to do next

Configure SNMP trap settings as described in

Configuring SNMP Trap Settings, on page 297 .

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

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope snmp

Purpose

Enters the SNMP command mode.

Server /snmp # scope trap-destinations number Enters the SNMP trap destination command mode for the specified destination. Four SNMP trap destinations are available. The destination number is an integer between 1 and 15.

Server /snmp/trap-destinations # set enabled

{ yes | no }

Enables or disables the SNMP trap destination.

Server /snmp/trap-destinations # set version {

| 2 | 3 }

Specify the desired SNMP version of the trap message.

Note SNMPv3 traps will be delivered only to locations where the SNMPv3 user and key values are configured correctly.

Server /snmp/trap-destinations # set type { trap

| inform }

Specifies whether SNMP notification messages are sent as simple traps or as inform requests requiring acknowledgment by the receiver.

Note The inform option can be chosen only for V2 users.

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

297

Configuring Communication Services

Configuring SNMP Trap Settings

Step 6

Step 7

Step 8

Step 9

Command or Action Purpose

Server /snmp/trap-destinations # set user user Note While Configuring SNMP v3 version, you cannot use SNMP users with Encryption Method set as DES .

Server /snmp/trap-destination # set trap-addr trap destination address

Specifies the trap destination address to which the trap information is sent. You can set an IPv4 or IPv6 address or a domain name as the trap destination.

Note When IPv6 is enabled, the SNMP

Trap destination source address can either be the SLAAC IPv6 address

(if available) or a user assigned IPv6 address. Both these are valid SNMP

IPv6 destination addresses that uniquely identify the server.

Server /snmp/trap-destinations # set trap-port trap destination port

Sets the port number the server uses to communicate with the trap destination. You can choose a number within the range 1 to 65535.

Server /snmp/trap-destination # commit Commits the transaction to the system configuration.

Example

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 trap-addr www.cisco.com

Server /snmp/trap-destination *# set trap-port 10000

Server /snmp/trap-destination *# commit

Server /snmp/trap-destination # show detail

Trap Destination 1:

Enabled: yes

SNMP version: 2

Trap type: inform

SNMP user: user1

Trap Address: www.cisco.com

Trap Port: 10000

Delete Trap: no

Server /snmp/trap-destination #

298

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

Configuring Communication Services

Sending a Test SNMP Trap Message

Before you begin

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

Procedure

Step 1

Step 2

Command or Action

Server# scope snmp

Server /snmp # send-test-trap

Purpose

Enters the SNMP command mode.

Sends an SNMP test trap to the configured

SNMP trap destination that are enabled.

Note The trap must be configured and enabled in order to send a test message.

Example

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

Server# scope snmp

Server /snmp # send-test-trap

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

Step 1

Step 2

Step 3

Command or Action

Server# scope snmp

Purpose

Enters the SNMP command mode.

Server /snmp # scope v3users number Enters the SNMPv3 users command mode for the specified user number.

Server /snmp/v3users # set v3add { yes | no } Adds or deletes an SNMPv3 user. This can be one of the following:

• yes —This user is enabled as an SNMPv3 user and is allowed to access the SNMP

OID tree.

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

299

Configuring Communication Services

Configuring SNMPv3 Users

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Command or Action Purpose

Note The security name and security level must also be configured at this time or the user addition will fail.

• no —This user configuration is deleted.

Server /snmp/v3users # set v3security-name security-name

Enter an SNMP username for this user.

Server /snmp/v3users # set v3security-level

{ noauthnopriv | authnopriv | authpriv }

Select a security level for this user. This can be one of the following:

• noauthnopriv —The user does not require an authorization or privacy password.

• authnopriv —The user requires an authorization password but not a privacy password. If you select this option, you must configure an authentication key.

• authpriv —The user requires both an authorization password and a privacy password. If you select this option, you must configure an authentication key and a private encryption key.

Note For a v3 version, only authnopriv and authpriv security levels are available.

Server /snmp/v3users # set v3proto { MD5 |

SHA }

Note For a v3 version, only SHA authentication methods are available.

Select an authentication protocol for this user.

Enter an authorization password for this user.

Server /snmp/v3users # set v3auth-key auth-key

Server /snmp/v3users # set v3priv-proto

{ DES | AES }

Note For a v3 version, only AES option is available.

Select an encryption protocol for this user.

Server /snmp/v3users # set v3priv-auth-key priv-auth-key

Enter a private encryption key (privacy password) for this user.

Server /snmp/v3users # commit Commits the transaction to the system configuration.

300

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

Configuring Communication Services

Configuring SNMPv3 Users

Example

This example configures SNMPv3 user number 2 and commits the transaction:

Server# scope snmp

Server /snmp # scope v3users 2

Server /snmp/v3users # set v3add yes

Server /snmp/v3users *# set v3security-name ucsSNMPV3user

Server /snmp/v3users *# set v3security-level authpriv

Server /snmp/v3users *# set v3proto SHA

Server /snmp/v3users *# set v3auth-key

Please enter v3auth-key: ex4mp1ek3y

Please confirm v3auth-key: ex4mp1ek3y

Server /snmp/v3users *# set v3priv-proto AES

Server /snmp/v3users *# set v3priv-auth-key

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 4.2

301

Configuring SNMPv3 Users

Configuring Communication Services

302

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

C H A P T E R

Managing Certificates and Server Security

This chapter includes the following sections:

•

Managing the Server Certificate, on page 303

•

Managing the External Certificate, on page 309

•

SPDM Security - MCTP SPDM, on page 313

•

Key Management Interoperability Protocol, on page 320

•

FIPS 140-2 Compliance in Cisco IMC, on page 336

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 Cisco IMC 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. The generated certificate key length is 2048 bits.

Note Before performing any of the following tasks in this chapter, ensure that the Cisco IMC time is set to the current time.

Procedure

Step 1

Step 2

Step 3

Generate the CSR from Cisco IMC.

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.

Upload the new certificate to Cisco IMC.

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

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

303

Managing Certificates and Server Security

Generating a Certificate Signing Request

You can either generate a self-signed certificate manually using the generate-csr command, or automatically when you change the hostname. For information on changing the hostname and auto generation of the self-signed certificate, see the Configuring Common Properties section.

To manually generate a certificate signing request, follow these steps:

Before you begin

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

• Ensure that the Cisco IMC time is set to the current time.

Procedure

Step 1

Step 2

Command or Action

Server# scope certificate

Server /certificate # generate-csr

Purpose

Enters the certificate command mode.

Launches a dialog for the generation of a certificate signing request (CSR).

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

Name

Common Name field

Description

The fully qualified name of the Cisco IMC.

By default the CN of the servers appears in CXXX-YYYYYY format, where XXX is the model number and YYYYYY is the serial number of the server.

When you upgrade to latest version, CN is retained as is.

Organization Name

Organization Unit

Locality field field field

The organization requesting the certificate.

The organizational unit.

The city or town in which the company requesting the certificate is headquartered.

State Name field

Country Code

Email field drop-down list

The state or province in which the company requesting the certificate is headquartered.

The country in which the company resides.

The email contact at the company.

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

304

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

Managing Certificates and Server Security

Generating a Certificate Signing Request

Example

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: [email protected]

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 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 Cisco IMC 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.

• Ensure that the certificate is of type Server .

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

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

305

Managing Certificates and Server Security

Creating an Untrusted CA-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 Cisco IMC.

Before you begin

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

• Ensure that the Cisco IMC time is set to the current time.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

openssl genrsa -out CA_keyfilename keysize

Example:

# openssl genrsa -out ca.key 2048

Purpose

This command generates an RSA private key that will be used by the CA.

Note To allow the CA to access the key without user input, do not use the

-des3 option for this command.

The specified file name contains an RSA key of the specified key size.

openssl req -new -x509 -days numdays -key

CA_keyfilename -out CA_certfilename

Example:

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

This command generates a new self-signed certificate for the CA using the specified key.

The certificate is valid for the specified period.

The command prompts the user for additional certificate information.

The certificate server is an active CA.

echo "nsCertType = server" > openssl.conf

Example:

# echo "nsCertType = server" > openssl.conf

This command adds a line to the OpenSSL configuration file to designate the certificate as a server-only certificate. This designation is a defense against a man-in-the-middle attack, in which an authorized client attempts to impersonate the server.

The OpenSSL configuration file openssl.conf

contains the statement "nsCertType = server".

openssl x509 -req -days numdays -in

CSR_filename -CA CA_certfilename -set_serial

04 -CAkey CA_keyfilename -out

server_certfilename -extfile openssl.conf

This command directs the CA to use your CSR file to generate a server certificate.

Your server certificate is contained in the output file.

306

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

Managing Certificates and Server Security

Creating an Untrusted CA-Signed Certificate

Step 5

Step 6

Command or Action

Example:

# openssl x509 -req -days 365 -in csr.txt

-CA ca.crt -set_serial 04

-CAkey ca.key -out myserver05.crt

-extfile openssl.conf

Purpose openssl x509 -noout -text -purpose -in <cert file>

Verifies if the generated certificate is of type

Server .

Example: openssl x509 -noout -text -purpose -in

Note If the values of the fields Server

SSL and Netscape SSL server are not yes, ensure that openssl.conf is configured to generate certificates of type server.

(Optional) If the generated certificate does not have the correct validity dates, ensure the Cisco

IMC time is set to the current time, and regenerate the certificate by repeating steps 1 through 5.

Certificate with the correct validity dates is created.

Example

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 2048

Generating RSA private key, 2048 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,

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 []: [email protected]

# 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/[email protected]

Getting CA Private Key

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

307

Managing Certificates and Server Security

Uploading a Server Certificate

What to do next

Upload the new certificate to the Cisco IMC.

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.

• Ensure that the generated certificate is of type Server .

• The following certificate formats are supported:

• .crt

• .cer

• .pem

Note You must first generate a CSR using the Cisco IMC 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

Step 1

Step 2

Command or Action

Server# scope certificate

Server /certificate # upload

Purpose

Enters the certificate command mode.

Launches a dialog for entering and uploading the new server certificate.

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

Example

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

MIIB/zCCAWgCAQAwgZkxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEVMBMGA1UE

308

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

Managing Certificates and Server Security

Managing the External Certificate

BxMMU2FuIEpvc2UsIENBMRUwEwYDVQQKEwxFeGFtcGxlIEluYy4xEzARBgNVBAsT

ClRlc3QgR3JvdXAxGTAXBgNVBAMTEHRlc3QuZXhhbXBsZS5jb20xHzAdBgkqhkiG

9w0BCQEWEHVzZXJAZXhhbXBsZS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ

AoGBAMZw4nTepNIDhVzb0j7Z2Je4xAG56zmSHRMQeOGHemdh66u2/XAoLx7YCcYU

ZgAMivyCsKgb/6CjQtsofvzxmC/eAehuK3/SINv7wd6Vv2pBt6ZpXgD4VBNKONDl

GMbkPayVlQjbG4MD2dx2+H8EH3LMtdZrgKvPxPTE+bF5wZVNAgMBAAGgJTAjBgkq hkiG9w0BCQcxFhMUQSBjaGFsbGVuZ2UgcGFzc3dvcmQwDQYJKoZIhvcNAQEFBQAD gYEAG61CaJoJaVMhzCl903O6Mg51zq1zXcz75+VFj2I6rH9asckCld3mkOVx5gJU

Ptt5CVQpNgNLdvbDPSsXretysOhqHmp9+CLv8FDuy1CDYfuaLtvlWvfhevskV0j6 mK3Ku+YiORnv6DhxrOoqau8r/hyI/L43l7IPN1HhOi3oha4=

-----END CERTIFICATE-----

<CTRL+D>

Managing the External Certificate

Uploading an External Certificate

Before you begin

• You must log in as a user with admin privileges.

• The certificate file to be uploaded must reside on a locally accessible file system.

• The following certificate formats are supported:

• .crt

• .cer

• .pem

Note • Cisco IMC supports external private key size of 2048 bits and 4096 bits in Cisco UCS C-Series M4 servers.

• Cisco IMC supports external private key size of 2048 bits, 4096 bits and 8192 bits in Cisco UCS C-Series

M5 servers.

Procedure

Step 1

Step 2

Server# scope certificate

Enters Cisco IMC certificate command mode.

Server /certificate # upload-remote-external-certificate remote-protocol server_address path certificate_filename

Specify the protocol to connect to the remote server. It can be of the following types:

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

309

Managing Certificates and Server Security

Uploading an External Certificate

Step 3

• TFTP

• FTP

• SFTP

• SCP

• HTTP

Note If you enter the protocol as FTP, SCP or SFTP, you will be prompted to enter your username and password.

Along with the remote protocol, enter the filepath from where you want to upload the external certificate.

After validating your remote server username and password, uploads the external certificate from the remote server.

(Optional) Server /certificate # upload-paste-external-certificate

This is an additional option to upload the external certificate.

At the prompt, paste the content of the certificate and press

CTRL+D

Note The maximum file size supported for upload:

• Up to 8 KB in Cisco UCS C-Series M5 servers

• Up to 4 KB in Cisco UCS C-Series M4 servers

Example

• This example uploads an external certificate from a remote server:

Server # scope certificate

Server /certificate # upload-remote-external-certificate scp 10.10.10.10

/home/user-xyz/ext-certif.cert

Server (RSA) key fingerprint is dd:b5:2b:07:ad:c0:30:b2:d5:6a:6a:78:80:85:93:b0

Do you wish to continue? [y/N]y

Username: user-xyz

Password:

External Certificate uploaded successfully

Server /certificate #

• This example uploads an external certificate using paste option:

Server # scope certificate

Server /certificate # upload-paste-external-certificate

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

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

MIID8zCCAtugAwIBAgIBBDANBgkqhkiG9w0BAQwFADCBsDELMAkGA1UEBhMCSU4x

EjAQBgNVBAgMCUthcm5hdGFrYTESMBAGA1UEBwwJQmFuZ2Fsb3JlMSQwIgYDVQQK

DBtDaXNjbyBTeXN0ZW1zIEluZGlhIFB2dCBMdGQxGDAWBgNVBAsMD1VDUy1SYWNr

LVNlcnZlcjEWMBQGA1UEAwwNQ2lzY28gU3lzdGVtczEhMB8GCSqGSIb3DQEJARYS c3JpdmF0c3NAY2lzY28uY29tMB4XDTIwMDExMzA4MTM1NVoXDTIxMDExMjA4MTM1

NVowgbExCzAJBgNVBAYTAklOMRIwEAYDVQQIEwlLYXJuYXRha2ExEjAQBgNVBAcT

CUJlbmdhbHVydTEkMCIGA1UEChMbQ2lzY28gU3lzdGVtcyBJbmRpYSBQdnQgTHRk

MRgwFgYDVQQLEw9VQ1MtUmFjay1TZXJ2ZXIxFjAUBgNVBAMTDUNpc2NvIFN5YXRl bXMxIjAgBgkqhkiG9w0BCQEWE3NyaXZhdHNzQGNpc2NvLmNvbm0wggEiMA0GCSqG

310

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

Managing Certificates and Server Security

Uploading an External Private Key

SIb3DQEBAQUAA4IBDwAwggEKAoIBAQC6fcG9QISg6t1fi6U3+czmek2LvfhAxSGd r2g7uMssgdTrBh59TEgZl5azal5zWaZm/1iO69D6/iabyoli8+MiQAtANnKxqWM3

STeih+3U2jOf39lIlZrAMpd4Ag/OtK5OcUtwUHM52ixm/UU61geVPZ5mJpPkzq3T

JNcv6TR90K8v0nEILm1lgoA96y64I9YN3ufSE4gm9VOS/sFughmAyYErsgvgoJpn

SQZUYxwdueBm4XV48QY7Mc7neUVYCNo7TcfBX7DC/N0BHv3hlKhGCCQ+5if63uOh ja8ahdBoIPJqI0h70a92yBK5lv4dxSHexccw2D40kar4CzfVSqx9AgMBAAGjFTAT

MBEGCWCGSAGG+EIBAQQEAwIGQDANBgkqhkiG9w0BAQwFAAOCAQEAXdVTJevqNyI9

DEVibfjGXiKnJ2gEuYr8MdhpDeff/WrsLk7lxhOomVrDZ3iyCX99tNoCIvtOMgNs jOu9OEjNtBulOlgwdQ9ugwp/JToohbD+2JHRK/MgrFpZmewH1oKKDNpOdayR6u9m

SNfvMNBgvxg+cMcbkif0pJU3XHlniPF6UVgj/LJDyBSGrULpnyDwTOq2UEF6g9Dc

6gOgRGYNHn7MRzigPJtyjbJsbxgPQ9C46I3Me9N2sJNaSLSVQhOxW7KonPI6USRs e2iEAYaaCvThGE4HTwOMF9dJ24inU+SKTci1AFq2+V4I3P9v+aH5ao1H9T/p/AUP ho6MuZ+wWg==

-----END CERTIFICATE-----

External Certificate pasted successfully.

Server /certificate #

What to do next

You must upload an external private key and then activate the external certificate.

Uploading an External Private Key

Before you begin

• You must log in as a user with admin privileges to upload an external private key.

Note • Cisco IMC supports external private key size of 2048 bits and 4096 bits in Cisco UCS C-Series M4 servers.

• Cisco IMC supports external private key size of 2048 bits, 4096 bits and 8192 bits in Cisco UCS C-Series

M5 servers.

Procedure

Step 1

Step 2

Step 3

Server# scope certificate

Enters Cisco IMC certificate command mode.

Server /certificate # upload-remote-external-private-key remote-protocol server_address path key_filename

Specify the protocol to connect to the remote server. It can be one of the following:

• SFTP

• SCP

Along with the remote protocol, enter the filepath from where you want to upload the private key. After validating your remote server username and password, uploads the private key from the remote server.

(Optional) Server /certificate # upload-paste-external-private-key

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

311

Uploading an External Private Key

This is an additional option to upload the private key.

At the prompt, paste the content of the private key and press

CTRL+D

Note The maximum file size supported for upload:

• Up to 8 KB in Cisco UCS C-Series M5 servers

• Up to 4 KB in Cisco UCS C-Series M4 servers

Managing Certificates and Server Security

Example

• This example uploads an external private key from a remote server:

Server # scope certificate

Server /certificate # upload-remote-external-private-key scp 10.10.10.10

/home/user-xyz/ext-pvt-key.pem

Server (RSA) key fingerprint is dd:b5:2b:07:ad:c0:30:b2:d5:6a:6a:78:80:85:93:b0

Do you wish to continue? [y/N]y

Username: user-xyz

Password:

External Private Key uploaded successfully

Server /certificate #

• This example uploads an external private key using paste option:

Server # scope certificate

Server /certificate # upload-paste-external-private-key

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

-----BEGIN RSA PRIVATE KEY-----

MIIEoQIBAAKCAQEAun3BvUCEoOrdX4ulN/nM5npNi734QMUhna9oO7jLLIHU6wYe fUxIGZeWs2pec1mmZv9YjuvQ+v4mm8qJYvPjIkALQDZysaljN0k3ooft1Nozn9/Z

SJWawDKXeAIPzrSuTnFLcFBzOdosZv1FOtYHlT2eZiaT5M6t0yTXL+k0fdCvL9Jx

CC5tZYKAPesuuCPWDd7n0hOIJvVTkv7BboIZgMmBK7IL4KCaZ0kGVGMcHbngZuF1 ePEGOzHO53lFWAjaO03HwV+wwvzdAR794ZSoRggkPuYn+t7joY2vGoXQaCDyaiNI e9GvdsgSuZb+HcUh3sXHMNg+NJGq+As31UqsfQIDAQABAoH/MSv3aW8ZiVRkCk1H wvqajCqzR6VPT8SqmGknkpem+pVBDrcOUvtKB3Vwxt3FCaUZuw6YyxZig8t/YpSE pRKpUN6SGNxCYZXIE0u635/3lafy9LSRFhJcO1EbnwjsIhSB4Sz+Nx7/QsHD82PU

XS8R0MfufACv/iSAsKuGEZvru0BWexD1ycojGTDRhGqWZGzsN6ncsbhQ0kItC0Pv

Ycx+9NeKfGwO+P9NwyWwaKW9M4nOyx3/MviMx9QRbNjgxjrdTj+A0aBUEzgdeZOf

WCJ/LlSbHmJ46HYZOILL4KDBbow/c7a1c2JcFWn01m33qNCRWdkb5H+1UZA+el7g

XnxDAoGBALzBdW26GGIZjj42Ayr9PAXFsO8n0MonqVHRlRTvxeuLOvHYdD9HzgkH

CFXA0IGmNk/1RuwEArx6U6ezSP6z7za9B63MskE7t3Vs28/OJg14KptRftGKUIbZ

NRf1o3J7VUf9mYk9u3pc/PJ8oVweFoml/SwRTDvZyUn5WRLq7zJ3AoGBAPztx24M qj0Gcbqa7U5pUM+9bD9eGPxrGranFlDp79eobG+9kva286clp0Yr5XrNsQpx42Q6

RJLBVEwrB03D7X9UIOaAgyiaDbDMbIeAcRqOC9qpLDUXrpMVrdvVhtcPrKS8VAp4 hOle6zYKMShMXDExhH3EHaQ7aVOQRpt5GoGrAoGBAKBX1uE3TK9I9kRyrY4/QFXG

8d62++4+ct9GIlZ+uKq2w4PeVCHNZYDVsIboHDeGcmzJ901WutxRLe8vpbp4L6VY

PsWtNV+k0tu1daS5gim/ArKeMBTgYjerHCcWS5pcmr1k+KBVCIWRqG504L3X8V1M

3BwrNY9CGnP0lW40lK1RAoGASikuIIZ2JA6Pqjdi/WrD1yWjZ7EfgmOlIYk8cd0m

BgXMRbdAMDbUml3f/iNA1hEZqAZctjafhKhLH0o+if641GzGeM+VpYIGIaDO8awn fbHIqASSgb6/4UCqCZtCPizKYkMWITvVPNgn/2BdqYM6RPJP9tBaIJ2K9IWJLm0D

6KECgYB9rmj/8YW7Rz1Isfg7JhK32p7LC+5xSSbpxQc8s/3PftZ5uQnsXXHoZJ0H cfA4mbj4nttyFwX+kuUpQdG/ZhoJ/SDqE5lvzVM4stMRKFEJq8ksld+KGGzLFEkj

OotvpQor5dHHU46IIu9tv5ctrJImMjSM7wro26kW2EE3UzZMYw==

-----END RSA PRIVATE KEY-----

External Private Key pasted successfully.

Server /certificate #

312

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

Managing Certificates and Server Security

Activating the External Certificate

What to do next

You must activate the external certificate.

Activating the External Certificate

• You must log in as a user with admin privileges.

• You can activate the external certificate only after the certificate and private key are uploaded.

• Activating the external certificate replaces the existing certificate and disconnects any active HTTPS or

SSH sessions.

Procedure

Step 1

Step 2

Server# scope certificate

Enters Cisco IMC certificate command mode.

Server /certificate # activate-external-certificate

Activates the uploaded external certificate.

Example

This example activates the uploaded certificate:

Server # scope certificate

Server /certificate # activate-external-certificate

This operation will overwrite the current certificate with the uploaded external certificate.

All HTTPS and SSH sessions will be disconnected.

Continue?[y|N] y

A system reboot has been initiated.

Server /certificate #

SPDM Security - MCTP SPDM

SPDM Security

Cisco M6 Servers might contain mutable components that could provide vectors for attack against a device itself or use of a device to attack another device within the system. To defend against these attacks, SPDM

(Security Protocol and Data Model) specification defines messages, data objects, and sequences for performing message exchanges between devices over a variety of transport and physical media. It orchestrates message exchanges between management controllers and end-point devices over Management Component Transport

Protocol (MCTP).

Message exchanges include authentication of hardware identities accessing the controller. The SPDM enables access to low-level security capabilities and operations by specifying a managed level for device authentication

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

313

Managing Certificates and Server Security

Configuring and Viewing the MCTP SPDM Fault Alert Setting and certificate management. This feature is supported on Cisco UCS C220 and 240 M6 Servers, in Cisco

IMC, Release 4.2(1a).

Endpoint certificates and authorites (Root CA) certificates are listed on all user interfaces on the server. You can also upload the content of one or more external device certificates into Cisco IMC. Using a SPDM policy allows you to change or delete external Root CA certificate or settings as desired. You can also delete or replace the root CA certificate when no longer needed.

A SPDM security policy allows you to specify any one of the three security level settings, as listed below:

• Full Security:

This is the highest MCTP security setting. When you select this setting, a fault is generated when any endpoint authentication failure is detected. A fault will also be generated if any of the endpoints do not support endpoint authentication.

• Partial Security:

When you select this setting, a fault is generated when any endpoint authentication failure is detected.

There will NOT be a fault generated when the endpoint doesn’t support endpoint authentication. This is chosen as the default setting.

• No Security

When you select this setting, no fault will be generated for any failure (endpoint measurement).

Configuring and Viewing the MCTP SPDM Fault Alert Setting

You can configure the MCTP SPDM fault alert setting.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis# scope mctp

Purpose

Enters the chassis command mode.

Enters the MCTP SPDM security command mode.

Server /chassis/mctp# set fault-alert-setting

Partial | Full | Disabled

Configures the MCTP SPDM fault-alert-setting with the chosen value.

This can be one of the following:

• Full - If you select this option, then a fault is generated when there is any endpoint authentication failure.

If you select this option, then a fault is generated when the endpoints do not support endpoint authentication.

• Partial - The default option. If you select this option, then a fault is generated when there is any endpoint authentication failure.

314

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

Managing Certificates and Server Security

Uploading SPDM Root CA Certificates

Command or Action

Step 4 Server /chassis/mctp# show detail

Step 5

Step 6

Step 7

Step 8

(Optional) Server /chassis/mctp# exit

(Optional) Server /chassis# exit

(Optional) Server# scope fault

(Optional) Server /chassis/fault# show fault-entries

Purpose

If you select this option, no fault is generated when the endpoints do not support endpoint authentication.

• Disabled - If you select this option, no fault is generated for endpoint authentication failure.

Displays the configured MCTP SPDM fault alert setting.

Returns to the chassis command mode.

Returns to the server command mode.

Enters the fault command mode.

Displays a log of all the faults.

Note If the device attestation fails, a fault is generated. Run the steps 5 to 8 to view the relevant fault.

Example

This example configures the fault-alert-setting to full .

Server# scope chassis

Server /chassis # scope mctp

Server /chassis/mctp # set fault-alert-setting full

Server /chassis/mctp # show detail

Fault Alert Setting: Full

Uploading SPDM Root CA Certificates

You can upload the SPDM Root CA certificate by remotely uploading the Root CA certificate to the server.

Optionally, you can also upload by pasting the certificate details (

.pem

format only).

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis# scope mctp

Purpose

Enters the chassis command mode.

Enters the MCTP SPDM security command mode.

Server /chassis/mctp#

upload-remote-external-certificate protocol server_address path/certificate_filename

Specify the protocol to connect to the remote server. It can be of the following types:

• TFTP

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

315

Managing Certificates and Server Security

Uploading SPDM Root CA Certificates

Step 4

Step 5

Command or Action Purpose

• FTP

• SFTP

• SCP

• HTTP

Note If you enter the protocol as FTP,

SCP or SFTP, you will be prompted to enter your username and password.

Along with the remote protocol, enter the filepath from where you want to upload the

SPDM Root CA certificate. After validating your remote server username and password, uploads the SPDM Root CA certificate from the remote server.

(Optional) Server /chassis/mctp# show status Displays the certificate upload status.

(Optional) Server /chassis/mctp# upload-paste-external-certificate

This is an additional option to upload the SPDM

Root CA certificate (

.pem

format only).

At the prompt, paste the content of the certificate and press

CTRL+D

Example

• This example uploads an SPDM Root CA certificate from a remote server:

Server# scope chassis

Server /chassis # scope mctp

Server /chassis/mctp# upload-remote-external-certificate scp 10.10.10.10

/home/user-xyz/ext-certif.cert

Server (RSA) key fingerprint is dd:b5:2b:07:ad:c0:30:b2:d5:6a:6a:78:80:85:93:b0

Do you wish to continue? [y/N]y

Username: user-xyz

Password:

External Certificate uploaded successfully

Server /chassis/mctp #

• This example uploads an SPDM Root certificate using paste option (

.pem

format only):

Server# scope chassis

Server /chassis # scope mctp

Server /chassis/mctp# upload-paste-external-certificate

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

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

MIIDfDCCAmSgAwIBAgIQGKy1av1pthU6Y2yv2vrEoTANBgkqhkiG9w0BAQUFADBY

MQswCQYDVQQGEwJVUzEWMBQGA1UEChMNR2VvVHJ1c3QgSW5jLjExMC8GA1UEAxMo

R2VvVHJ1c3QgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNjEx

MjcwMDAwMDBaFw0zNjA3MTYyMzU5NTlaMFgxCzAJBgNVBAYTAlVTMRYwFAYDVQQK

Ew1HZW9UcnVzdCBJbmMuMTEwLwYDVQQDEyhHZW9UcnVzdCBQcmltYXJ5IENlcnRp

ZmljYXRpb24gQXV0aG9yaXR5MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC mO9Y+pyEtzavwt+s0vQQBnBxNQIDAQABo0IwQDAPBgNVHRMBAf8EBTADAQH/MA4G

316

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

Managing Certificates and Server Security

Viewing SPDM Authentication Status and SPDM Certificate Chain

A1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQULNVQQZcVi/CPNmFbSvtr2ZnJM5IwDQYJ

6CePbJC/kRYkRj5KTs4rFtULUh38H2eiAkUxT87z+gOneZ1TatnaYzr4gNfTmeGl

4b7UVXGYNTq+k+qurUKykG/g/CFNNWMziUnWm07Kx+dOCQD32sfvmWKZd7aVIl6K oKv0uHiYyjgZmclynnjNS6yvGaBzEi38wkG6gZHaFloxt/m0cYASSJlyc1pZU8Fj

UjPtp8nSOQJw+uCxQmYpqptR7TBUIhRf2asdweSU8Pj1K/fqynhG1riR/aYNKxoU

AT6A8EKglQdebc3MS6RFjasS6LPeWuWgfOgPIh1a6Vk=

-----END CERTIFICATE-----

External Certificate pasted successfully.

Server /chassis/mctp#

• This example shows the certificate upload progress and status:

Server# /chassis/mctp # show status

MCTP External Certificate Upload Status: NONE

MCTP External Certificate Upload Progress: 0

Viewing SPDM Authentication Status and SPDM Certificate Chain

You can view the SPDM authentication status and the SPDM certificate chain for a particular slot.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Purpose

Enters the chassis command mode.

Server /chassis# scope mctp Enters the MCTP SPDM security command mode.

Displays the SPDM status.

Server /chassis/mctp# spdm-status

Server /chassis/mctp# spdm-cert-chain Slot-ID Displays the SPDM certificate chain for a particular slot.

Example

This example displays the SPDM status, when in progress and on successful completion.

Server# scope chassis

Server /chassis # scope mctp

Server /chassis/mctp # spdm-status

Overall SPDM Status : in progress

Server /chassis/mctp # spdm-cert-chain MRAID

Certificate Chain Information

Error : Failed to get cert chain due to on-going handshake ( Please try after some time)

Server /chassis/mctp # spdm-status

Overall SPDM Status : success

Slot ID Status Name

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

MRAID success N/A

Server /chassis/mctp # spdm-cert-chain MRAID

Certificate Chain Information

Slot ID : MRAID

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

Depth : 0

Subject Country Code (C)

Subject State (ST)

Colorado

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

317

Managing Certificates and Server Security

Viewing the List of Certificates and Certificate Details

Subject City (L)

Subject Organization (O)

: Colorado Springs

: Broadcom Inc.

Subject Organization Unit(OU) : NA

Subject Common Name (CN) : Aero Device

Issuer Country Code (C) : US

Issuer State (ST)

Issuer City (L)

: Colorado

: NA

Issuer Organization (O) : Broadcom Inc.

Issuer Organization Unit(OU) : DCSG

Issuer Common Name (CN) : Aero Model

Valid From

Valid To

: Oct 23 01:01:28 2019 GMT

: Mar 10 01:01:28 2047 GMT

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

Depth : 1

Subject Country Code (C) : US

Subject State (ST)

Subject City (L)

: Colorado

: Colorado Springs

Subject Organization (O) : Broadcom Inc.

Subject Organization Unit(OU) : NA

Subject Common Name (CN) : Aero Model

Issuer Country Code (C)

Issuer State (ST)

: US

: Colorado

Issuer City (L)

Issuer Organization (O)

Colorado Springs

Broadcom Inc.

Issuer Organization Unit(OU) : NA

Issuer Common Name (CN)

Valid From

: NA

: Oct 23 00:36:24 2019 GMT

Valid To : Aug 3 00:36:24 2126 GMT

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

Viewing the List of Certificates and Certificate Details

You can view the list of SPDM Root CA certificates that have been uploaded.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope chassis

Server /chassis# scope mctp

Server /chassis/mctp# cert-list

Server /chassis/mctp# cert-details

Certificate-ID

Purpose

Enters the chassis command mode.

Enters the MCTP SPDM security command mode.

Lists all the certificates.

Lists the details of the SPDM Root CA certificate with the certificate ID 1

The following example shows the certificate ID, common name, issuer organization, and validity of two

Broadcom certificates.

Example

The example below lists all the SDPM Root CA certificates.

318

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

Managing Certificates and Server Security

Deleting Certificates

Server# scope chassis

Server /chassis # scope mctp

Server /chassis/mctp# cert-list

Certificate ID Common Name

Broadcom

Issuer Organization (O)

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

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

Broadcom

Valid To

Apr 8 10:36:14 1101

2021 GMT

1109 Broadcom1 Broadcom Apr 8 10:36:15

2021 GMT

The example below lists all the details of the SPDM Root CA certificate with the certificate ID 1 .

Server# scope chassis

Server /chassis # scope mctp

Server /chassis/mctp# cert-details 1

Certificate Information

Subject Country Code (C)

Subject State (ST)

Subject City (L)

Subject Organization (O)

Colorado

Colorado Springs

Broadcom Inc.

Subject Organization Unit(OU) : NA

Subject Common Name (CN) : NA

Issuer Country Code (C)

Issuer State (ST)

Issuer City (L)

Colorado

Colorado Springs

Issuer Organization (O) : Broadcom Inc.

Issuer Organization Unit(OU) : NA

Issuer Common Name (CN)

Valid From

Valid To

: NA

: Oct 23 00:25:13 2019 GMT

: Apr 29 00:25:13 2129 GMT

Deleting Certificates

You can delete any of the certificates that you have uploaded.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope chassis

Server /chassis# scope mctp

Server /chassis/mctp# delete-certificate

Certificate-id

Purpose

Enters the chassis command mode.

Enters the MCTP SPDM security command mode.

Successfully deletes the uploaded SPDM Root

CA Certificate with the certificate id 1 .

If the certificate id corresponds to any internal certificate, the following message is displayed:

The Certificate ID corresponds to

Internal certificate. Can’t delete

Internal certificates.

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

319

Managing Certificates and Server Security

Key Management Interoperability Protocol

Example

This example deletes any of the chosen uploaded certificates.

Server# scope chassis

Server /chassis # scope mctp

Server /chassis/mctp # delete-certificate

Please provide Certificate ID to delete certificate

Server /chassis/mctp # delete-certificate 1

Successfully deleted the user uploaded MCTP Certificate

Server /chassis/mctp # delete-certificate 11

The Certificate ID corresponds to Internal certificate. Can’t delete Internal certificates.

Key Management Interoperability Protocol

Key Management Interoperability Protocol (KMIP) is a communication protocol that defines message formats to handle keys or classified data on a key management server. KMIP is an open standard and is supported by several vendors. Key management involves multiple interoperable implementations, so a KMIP client works effectively with any KMIP server.

Self-Encrypting Drives(SEDs) contain hardware that encrypts incoming data and decrypts outgoing data in realtime. A drive or media encryption key controls this function. However, the drives need to be locked in order to maintain security. A security key identifier and a security key (key encryption key) help achieve this goal. The key identifier provides a unique ID to the drive.

Different keys have different usage requirements. Currently, the responsibility of managing and tracking local keys lies primarily with the user, which could result in human error. The user needs to remember the different keys and their functions, which could prove to be a challenge. KMIP addresses this area of concern to manage the keys effectively without human involvement.

Enabling or Disabling KMIP

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope kmip

Server/kmip# set enabled { yes | no }

Server/kmip*# commit

(Optional) Server/kmip # show detail

Purpose

Enters the KMIP command mode.

Enables or disables KMIP.

Commits the transaction to the system configuration.

Displays the KMIP status.

320

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

Managing Certificates and Server Security

Creating a Client Private Key and Client Certificate for KMIP Configuration

Example

This example enables KMIP:

Server # scope kmip

Server /kmip # set enabled yes

Server /kmip *# commit

Server /kmip # show detail

Enabled: yes

Server /kmip #

Creating a Client Private Key and Client Certificate for KMIP Configuration

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

Before you begin

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

• Ensure that the Cisco IMC time is set to the current time.

Procedure

Step 1

Step 2

Step 3

Command or Action Purpose

openssl genrsa -out Client_Privatekeyfilename keysize

This command generates a client private key that will be used to generate the client certificate.

Example:

# openssl genrsa –out client_private.pem

2048

The specified file name contains an RSA key of the specified key size.

openssl req -new -x509 -days numdays -key

Client_Privatekeyfilename -out

Client_certfilename

Example:

# openssl req -new -x509 -key client_private.pem -out client.pem -days

365

This command generates a new self-signed client certificate using the client private key obtained from the previous step. The certificate is valid for the specified period. The command prompts the user for additional certificate information.

A new self-signed client certificate is created.

Obtain the KMIP root CA certificate from the

KMIP server.

Refer to the KMIP vendor documentation for details on obtaining the root CA certificate.

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

321

Managing Certificates and Server Security

Downloading a KMIP Client Certificate

What to do next

Upload the new certificate to the Cisco IMC.

Downloading a KMIP Client Certificate

Before you begin

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

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope kmip

Server/kmip #

Server/kmip*# set enabled yes commit

Purpose

Enters the KMIP command mode.

Enables KMIP.

Commits the transaction to the system configuration.

Server/kmip # scope kmip-client-certificate Enters the KMIP client certificate command mode.

Server /kmip/kmip-client-certificate #

download-client-certificate remote-protocol

IP Address KMIP client certificate file

Specifies the protocol to connect to the remote server. It can be of the following types:

• TFTP

• FTP

• SFTP

• SCP

• HTTP

322

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

Managing Certificates and Server Security

Downloading a KMIP Client Certificate

Step 6

Step 7

Command or Action Purpose

If you chose SCP or SFTP as the remote server type while performing this action, a prompt with the message Server (RSA) key fingerprint is <server_finger_print

_ID> Do you wish to continue?

Click y or n depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

At the confirmation prompt, enter y .

This begins the download of the KMIP client certificate.

(Optional) Server /kmip/kmip-client-certificate

# paste-client-certificate

At the prompt, paste the content of the signed certificate and press CTRL+D .

Note You can either use the remote server method from the previous steps or use the paste option to download the client certificate.

Example

This example downloads the KMIP client certificate:

Server # scope kmip

Server /kmip # set enabled yes

Server /kmip *# commit

Server /kmip # scope kmip-client-certificate

Server /kmip/kmip-client-certificate # show detail

KMIP client certificate Available: 1

Download client certificate Status: COMPLETED

Export client certificate Status: NONE

Server /kmip/kmip-client-certificate # download-client-certificate tftp 10.10.10.10

KmipCertificates/ svbu-xx-blr-dn1-13_ClientCert.pem

You are going to overwrite the KMIP client certificate.

Are you sure you want to proceed and overwrite the KMIP client certificate? [y|N] y

KMIP client certificate downloaded successfully

You can either use the remote server method from the previous steps or use the paste option to download the client certificate.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 4.2

323

Managing Certificates and Server Security

Exporting a KMIP Client Certificate

Server /kmip/kmip-client-certificate # paste-client-certificate

Please paste your certificate here, when finished, press CTRL+D .

----BEGIN CERTIFICATE-----

MIIDTzCCAjegAwIBAgIQXuWPdBbyTb5M7/FT8aAjZTANBgkqhkiG9w0BAQUFADA6

MRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZImiZPyLGQBGRYDbmV3MQ4wDAYD

VQQDEwVuZXdDQTAeFw0xNTAzMTIxMTM5MTZaFw0yMDAzMTIxMTQ5MTVaMDoxEzAR

BgoJkiaJk/IsZAEZFgNjb20xEzARBgoJkiaJk/IsZAEZFgNuZXcxDjAMBgNVBAMT

BW5ld0NBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuPSAwHtk0IbM

Cd5tYdCa498bfX5Nfdgnq5zE+cGIOqv0dAkucofC/Y0+m7hne9H12aQ9SqTOK1+L

5IT3PVCczhasI7L7jAa+Oe5AOYw7Nsugw5Bd23n42BTVMMp7xsgr1mVfFoHXbBkQ wiT9DieyImSyGiq5n0/8Iooc0iN5WPMVcHO2ysz76jR8p07xRqgYNCl6cbKAhWfZ oYIwjhpZv0+SXEs8sEJZKDUhWIfOIpnDL7MoZYgl/kymgs/0hsW4L338jy303c7T

TwnG2/7BOMK0YFkEhqcjlkamGP7MKB2T9e/Cug6VkvFSkkim8M1eHx1gEnQxRtAG

YGp1n55iHQIDAQABo1EwTzALBgNVHQ8EBAMCAYYwDwYDVR0TAQH/BAUwAwEB/zAd

BgNVHQ4EFgQUl2F3U7cggzCuvRWliZWg91n5lccwEAYJKwYBBAGCNxUBBAMCAQAw

DQYJKoZIhvcNAQEFBQADggEBAJXoJJDDB3QH0q8VY8G/oC1SkAwyOE1dH0NdxFES tNqQMTaRB2Sb2L/ZzAtfIaZ0Xab9Ig4MqNIMBbHDCwlzhD5gX42GPYWhA/GjRj3O

Q5KcRaEFomxp+twRrJ25ScVSczKJaRonWqKDVL9TwoSuDar3ObiS9ZC0KuBBf0vu dzrJEYY/1zz7WVPZVyevhba3VSt4LW75URTqOKBSuKO+fvGyyNHWvMPFEIEnJAKt

7QmhO2fiWhD8CxaPFIByqkvrJ96no6oBxdEcjm9n1MttF/UJcpypSPH+46mRn5Az

SzgCBftYNjBPLcwbZGJkF/GpPwjd0TclMM08UOdqiTxR7Ts=

-----END CERTIFICATE-----

You are going to overwrite the KMIP Client Certificate.

Are you sure you want to proceed and overwrite the KMIP Client Certificate? [y|N] y

Server /kmip/kmip-client-certificate #

Exporting a KMIP Client Certificate

Before you begin

• You must log in as a user with admin privileges to perform this task.

• You should have downloaded KMIP client certificate before you can export it.

Procedure

Step 1

Step 2

Step 3

Command or Action

Server# scope kmip

Purpose

Enters the KMIP command mode.

Server /kmip # scope kmip-client-certificate Enters the KMIP client certificate command mode.

Server /kmip/kmip-client-certificate #

export-client-certificate remote-protocol IP

Adderss KMIP root CA Certificate file

Specifies the protocol to connect to the remote server. It can be of the following types:

• TFTP

• FTP

• SFTP

• SCP

324

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 4.2

Managing Certificates and Server Security

Deleting a KMIP Client Certificate

Step 4

Command or Action Purpose

• HTTP

If you chose SCP or SFTP as the remote server type while performing this action, a prompt with the message Server (RSA) key fingerprint is <server_finger_print

_ID> Do you wish to continue?

Click y or n depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

Initiates the export of the certificate.

(Optional) Server /kmip/kmip-client-certificate

# show detail

Displays the status of the certificate export.

Example

This example exports the KMIP client certificate:

Server # scope kmip

Server /kmip # scope kmip-client-certificate

Server /kmip/kmip-client-certificate # export-client-certificate ftp 10.10.10.10

/TFTP_DIR/KmipCertificates

/svbu-xx-blr-dn1-13_ClientCert.pem_exported_ftp

Username: username

Password:

KMIP Client Certificate exported successfully

Server /kmip/kmip-client-certificate # show detail

KMIP Client Certificate Available: 1

Download KMIP Client Certificate Status: COMPLETED

Export KMIP Client Certificate Status: COMPLETED

Server /kmip/kmip-client-certificate #

Deleting a KMIP Client Certificate

Before you begin

You must log in as a user with admin privileges to perform this task.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 4.2

325

Managing Certificates and Server Security

Downloading a KMIP Root CA Certificate

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

Server# scope kmip

Purpose

Enters the KMIP command mode.

Server# /kmip scope kmip-client-certificate Enters the KMIP client certificate binding command mode.

Confirmation prompt appears.

Server /kmip/kmip-client-certificate # delete-client-certificate

At the confirmation prompt, enter y .

This deletes the KMIP client certificate.

Example

This example deletes the KMIP client certificate:

Server # scope kmip

Server /kmip # scope kmip-client-certificate

Server /kmip/kmip-client-certificate # delete-client-certificate

You are going to delete the KMIP Client Certificate.

Are you sure you want to proceed and delete the KMIP Client Certificate? [y|N] y

KMIP Client Certificate deleted successfully.

Downloading a KMIP Root CA Certificate

Before you begin

You must log in as a user with admin privileges to perform this task.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

Server# scope kmip

Purpose

Enters the KMIP command mode.

Server/kmip #

Server/kmip * # set enabled yes commit

Enables KMIP.

Commits the transaction to the system configuration.

Server /kmip # scope kmip-root-ca-certificate Enters the KMIP root CA certificate command mode.

Server /kmip/kmip-root-ca-certificate #

download-root-ca-certificate remote-protocol

IP Address KMIP CA Certificate file

Specifies the protocol to connect to the remote server. It can be of the following types:

• TFTP

• FTP

• SFTP

• SCP

326

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 4.2

Managing Certificates and Server Security

Downloading a KMIP Root CA Certificate

Step 6

Step 7

Command or Action Purpose

• HTTP

If you chose SCP or SFTP as the remote server type while performing this action, a prompt with the message Server (RSA) key fingerprint is <server_finger_print

_ID> Do you wish to continue?

Click y or n depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

At the confirmation prompt, enter y .

This begins the download of the KMIP root CA certificate.

(Optional) Server /kmip/kmip-root-ca-certificate

# paste-root-ca-certificate

At the prompt, paste the content of the root CA certificate and press CTRL+D .

Note You can either use the remote server method from the previous steps or use the paste option to download the root CA certificate.

Example

This example downloads the KMIP root CA certificate:

Server # scope kmip

Server /kmip # set enabled yes

Server /kmip *# commit

Server /kmip # scope kmip-root-ca-certificate

Server /kmip/kmip-root-ca-certificate # show detail

KMIP Root CA Certificate Available: 1

Download Root CA Certificate Status: COMPLETED

Export Root CA Certificate Status: NONE

Server /kmip/kmip-root-ca-certificate # download-root-ca-certificate tftp 10.10.10.10

KmipCertificates/ svbu-xx-blr-dn1-13_ServerCert.pem

You are going to overwrite the KMIP Root CA Certificate.

Are you sure you want to proceed and overwrite the KMIP Root CA Certificate? [y|N] y

KMIP Root CA Certificate downloaded successfully

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 4.2

327

Managing Certificates and Server Security

Exporting a KMIP Root CA Certificate

You can either use the remote server method from the previous steps or use the paste option to download the client certificate.

Server /kmip/kmip-root-ca-certificate # paste-root-ca-certificate