Cisco C880 M5 Configuration Manual

Cisco C880 M5 Configuration Guide

December 2017

Americas Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL AR E BELI EV ED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORT H IN T HE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, R ege nts of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM A LL WARRANTIES, EX P RESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES , INCLUDING,WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partners hip relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illus trative purposes only. Any use of actual IP add res s e s in illust ra t ive content is unintentional and coincidental.

Contents

1 Preface ................................................................................................................................................................... 5

1.1

Concept and target groups for this manual .................................................................................................. 5

1.2

Documentation overview ............................................................................................................................... 6

1.3

Notational conventions ................................................................................................................................... 7

2 IPMI ........................................................................................................................................................................ 8

2.1

Technical Background ................................................................................................................................... 8

2.2

IPMI over LAN .............................................................................................................................................. 13

2.3

Supported IPMI OEM Commands .............................................................................................................. 14

2.3.1

SCCI-compliant Power On/Off commands ......................................................................................... 15

2.3.2

SCCI-compliant signaling command ................................................................................................... 19

2.3.3

BIOS-specific commands ..................................................................................................................... 20

2.3.4

iRMC S5-specific commands ............................................................................................................... 22

2.4

Data Center Management Interface ............................................................................................................ 30

2.5

Serial over LAN (SOL) ................................................................................................................................. 30

3 iRMC Configuration ............................................................................................................................................. 32

3.1

Configuration via the iRMC web interface .................................................................................................. 32

3.2

Configuration via Remote Manager ............................................................................................................ 33

3.3

Configuration via text console redirection .................................................................................................. 34

3.4

Configuration via scripting............................................................................................................................ 35

3.5

Configuration via UEFI setup utility ............................................................................................................. 36

3.5.1

Configuring the LAN interface .............................................................................................................. 37

3.5.2

Configuring text console redirection .................................................................................................... 38

3.5.3

Configuring the serial over LAN ........................................................................................................... 40

4 Configuration via Telnet/SSH (Remote Manager) ........................................................................................... 42

4.1

Requirements on the managed server ....................................................................................................... 42

4.2

Required user permissions .......................................................................................................................... 43

4.3

Logging in ...................................................................................................................................................... 46

4.4

Main menu .................................................................................................................................................... 48

4.4.1

System Information menu .................................................................................................................... 49

4.4.2

Power Management menu ................................................................................................................... 50

4.4.3

Enclosure Information menu ............................................................................................................... 51

4.4.3.1

System Eventlog ............................................................................................................................ 52

4.4.3.2

Internal Eventlog ............................................................................................................................ 53

4.4.4

Service processor menu ...................................................................................................................... 54

4.4.5

Console Redirection (EMS/SAC) ......................................................................................................... 55

4.4.6

Shell menu ............................................................................................................................................. 55

4.4.7

Console Logging ................................................................................................................................... 56

4.4.8

Console Logging Run State Menu ...................................................................................................... 57

Contents

5 Configuration via scripting ................................................................................................................................. 58

5.1

REST ............................................................................................................................................................. 58

5.2

Profile Management ..................................................................................................................................... 61

5.2.1

Profiles ................................................................................................................................................... 61

5.2.2

Automatic BIOS parameter backup ..................................................................................................... 62

5.3

Redfish .......................................................................................................................................................... 63

5.4

SCCI .............................................................................................................................................................. 66

5.4.1

iRMC configuration data ....................................................................................................................... 66

5.4.2

SCCI file format ..................................................................................................................................... 67

5.4.2.1

Parameters of SCCI provider-specific commands ..................................................................... 68

5.4.2.2

Restrictions ..................................................................................................................................... 70

5.4.2.3

Export / import of configuration data ........................................................................................... 71

5.4.3

Supported SCCI commands ................................................................................................................. 71

5.4.4

Script Examples .................................................................................................................................... 72

5.4.4.1

cURL examples ............................................................................................................................. 72

5.4.4.2

Visual Basic (VB) script ............................................................................................................... 73

5.4.4.3

Python script .................................................................................................................................. 73

6 Monitoring the iRMC........................................................................................................................................... 75

6.1

Monitoring with SNMP .................................................................................................................................. 75

6.2

iRMC system report ...................................................................................................................................... 77

6.2.1

cURL script for download ..................................................................................................................... 77

6.2.2

Visual Basic script ................................................................................................................................. 78

6.2.3

Information sections ............................................................................................................................. 79

6.2.3.1

Summary section ........................................................................................................................... 80

6.2.3.2

BIOS section .................................................................................................................................. 81

6.2.3.3

Processor section.......................................................................................................................... 81

6.2.3.4

Memory section ............................................................................................................................. 82

6.2.3.5

Fans section .................................................................................................................................. 83

6.2.3.6

Temperature section ..................................................................................................................... 83

6.2.3.7

Power supplies section .................................................................................................................. 84

6.2.3.8

Voltages section ............................................................................................................................ 84

6.2.3.9

IDPROMS section ......................................................................................................................... 84

6.2.3.10

SensorDataRecords section ........................................................................................................ 84

6.2.3.11

PCIDevices section ....................................................................................................................... 85

6.2.3.12

SystemEventLog section .............................................................................................................. 85

6.2.3.13

InternalEventLog section .............................................................................................................. 86

6.2.3.14

BootStatus section ........................................................................................................................ 86

6.2.3.15

ManagementControllers section .................................................................................................. 86

6.2.3.16

Settings section ............................................................................................................................. 87

6.2.3.17

Adapters section ........................................................................................................................... 87

6.2.3.18

Interfaces section .......................................................................................................................... 87

6.2.3.19

Ports section .................................................................................................................................. 87

6.2.3.20

SNMPAgents section .................................................................................................................... 87

1 Preface

Cisco C880 M5 Configuration Guide

1 Preface

The scalable CISCO C880 M5 is an I ntel-based rack server for critical company scenarios, e.g. as database management system for medium or large-sized databases or as a consolidation basis to run an immensely large number of different applications using virtualization technologies.

Thanks to its highly developed hardware and software components, the server offers a high level of data security and availability. These include hot-plug HDD/SSD modules, hot-plug system fans, and also hot-plug power supply units, Prefailure Detection and Analysis (PDA) and Automatic Server Reconfiguration and Restart (ASR&R).

Security functions in the BIOS Setup and on the System Board protect the data on the server against manipulation. Additional security is provided by the lockable rack door.

The server occupies 5 height units (HU) in the rack.

1.1

Concept and target groups for this ma nual

This manual is aimed at system administrators, network administrators, and service staff who have a sound knowledge of hardware and software. It provides basic information on the concepts of the iRMC and deals with the following aspects in detail:

The IPMI chapter comprises the basic principles of the IPMI protocol and the

supported

OEM commands, that can be used within a script.

iRMC Configurati on gi v es a n ov erv i ew of th e v ar io u s po s sibi lities to configur e the

iRMC.

The next chapters describe the configuration of the iRMC in detail using

different

interfaces:

Remote Manager

Several APIs

Monitoring the iRMC comprises the methods of how to monitor the iRMC.

Cisco C880 M5 Configuration Guide

1.2 Documentation overview

1.2

Documentation overview

More information on your CISCO C880 M5 can be found in the following documents: –

Cisco C880 M5 Installation Manual

–

Cisco C880 M5 Configuration Guide

–

Cisco C880 M5 Administration Guide

–

Cisco C880 M5 User Interface Guide

–

Cisco C880 M5 BIOS Setup Guide

Further sources of information:

–

Manual for the monitor

–

Documentation for the boards and drives

–

Operating system documentation

–

Information files in your operating system

Cisco C880 M5 Configuration Guide

1.3 Notational conventions

1.3

Notational conventions

The following notational conventions are used in this manual:

Notational

conventions

Indicates

Indicates various types of risks, namely health risks, risk of data

loss and risk of damage to devices.

Indicates additional relevant information and tips.

Bold

Indicates references to names of interface elements.

monospace

Indicates system output and system elements, for example file

names and paths.

monospace semibold

Indicates statements that are to be entered using the keyboard.

blue continuous

Indicates a link to a related topic.

text

purple

continuous text

Indicates a link to a location you have already visited. <abc>

Indicates variables which must be replaced with real values.

[abc]

Indicates options that can be specified (syntax).

[Key]

Indicates a key on your keyboard. If you need to explicitly enter text

in uppercase, the Shift key is specified, for example [Shift] + [A] for A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols.

Screenshots

The screenshots are to some degree system-dependent and consequently will not necessarily match the output on your system in all the details. The menus and their commands can also contain system-dependent differences.

Cisco C880 M5 Configuration Guide

2 IPMI

2.1

Technical Background

The iRMC makes the BMC (Baseboard Management Controller) functions available over the IPMI interface.

Intelligent Platform Management

The “Intelligent Platform Management” initiative is a response to the increasing complexity of modern server systems. A number of manufacturers have joined this initiative in order to come up with a new solution for monitoring these server systems.

The term “Intelligent Platform Management” expresses the core aspect of this approach to the solution: Functions for monitoring and recovery of systems are implemented directly in the hardware and firmware for platform management.

Objective

The objective was to define a standardized, abstract and message-based interface between the central system controller (Baseboard Management Controller - BMC) and intelligent platform management hardware.

The standardization committees combined the central characteristics of various platform management modules into standardized descriptions.

Definition

The IPMI specification defines: “IPMI is a hardware level interface specification that is ‘management software neutral’

providing monitoring and control functions that can be exposed through standard management software interfaces such as DMI, WMI, CIM, SNMP, etc. As a hardware level interface, it sits at the bottom of a typical management software stack”.

Advantage

The IPMI specifications ensure the independence of functions for inventory, logging, recovery and monitoring of a system by the system processor, BIOS or operating system.

This means that a system can still be involved in platform management when it is shut down and turned off .

IPMI and other management standards IPMI is best used in conjunction with system management software running under the

relevant operating system. Integration of the IPMI functionality into the management functionality offered by a management application and the operating system results in a powerful platform management environment.

Cisco C880 M5 Configuration Guide

2.1 Technical Background

An overview of the relationship between IPMI and the management software stack is shown in the following figure:

Figure 1: IPMI in the management software stack (source: IPMI specification)

IPMI, IPMB and ICMB The IPMI initiative resulted in three central standards:

IPMI: Intelligent Platform Management Interface Specification

describes the higher-level architecture, the current commands, event formats, data packets and properties that are used in IPMI-based systems.

IPMB: Intelligent Platform Management Bus

is an I

C based (write only) bus, which provides a standardized connection

between various modules in a common housing. IPMB can also be used as a standardized interface for remote management modules.

ICMB: Intel l igent Chassis Management Bus

(Not currently implemented in the remote management environment.) provides a standardized interface for exchange of platform management

information and for control across systems. ICMB is designed in such a way that it can be implemented with a device that is connected to the IPMB.

IPMI implementation The core element of an IPMI implementation is the Baseboard Management Controller

(BMC).

Cisco C880 M5 Configuration Guide

2.1 Technical Background

The BMC performs the following tasks:

The BMC organizes the interface between the system management sof t ware

and the

platform management hardware.

It provides autonomous functions for monitoring, event logging and recovery control.

The BMC acts as a gateway between the system management software and IPMB.

IPMI allows platform management to be extended: Additional management controllers can be connected via the IPMB. The IPMB is an I

C based serial bus, which runs between the main modules of the system. It is used for communication with and between the management controllers.

With the support of multiple management controllers, IPMI provides a scalable architecture: A complex server system can use multiple controllers for monitoring different subsystems, e.g. power supplies, hot swap RAID drive modules etc.

In addition, IPMI provides ‘low level’ I

C commands, which can be accessed via a

management controller connected to the IPMB on 'unintelligent' I

C modules that

cannot process IPMI commands. An overview of the fundamental elements of an IPMI implementation is shown in the

following figure:

Cisco C880 M5 Configuration Guide

2.1 Technical Background

Figure 2: IPMI block diagram (source: IPMI specification)

Cisco C880 M5 Configuration Guide

2.1 Technical Background

IPMI and “in-band” and “out-of-band” management In the field of system management, a distinction is made between “in-band” and “out-

of- band” management:

The term “in-band” management is used when the operating system is running

on the

managed server.

The term “out-of-band” mana ge m ent is used when the oper at in g s y ste m i s not

running on the manage d server, for instance if the hardware is faulty.

As different interfaces are available in an environment with IPMI compatible systems, you can manage IPMI compatible systems either “in-band” or “out-of-band”.

Channel concept under IPMI

‘Channels’ provide the mechanisms with which IPMI messages are routed to the BMC via various connection carriers. Up to nine channels can be supported. The system interface and the primary IPMB are fixed. The other seven channels are available for the implementation.

Channels can be either ‘session based’ or ‘sessionless’. The ‘session’ concept has two meanings: It is either a concept for user authentication or a concept for routing multiple IPMI message streams via a single channel.

Examples of ‘session based’ channels are LAN channels or serial/modem channels. Examples of ‘sessionless’ channels are the system interface and the IPMB.

User identifications

For ‘session based’ channels, a user login is necessary. By contrast, the ‘sessionless’ channels have no user authentication.

Under IPMI, the user configuration is channel specific. Thus, users can have different privileges depending on whether they are accessing the BMC via the LAN channel or the serial channel.

Fencing

In high available clusters problems can arise if the node considered failed is not actually failed. If, for any reason, it is not really down and it is still connected to the storage solution, node still tries to communicate and write data.

With two nodes connected to the same storage running, the storage can be easily corrupted, leaving the nodes in an inconsistent state. This is where fencing comes in. With fencing, even when the cluster doesn’t know what is happening on some node, you can make sure that node doesn’t run any or certain important resources.

So fencing refers to the idea of isolating nodes considered down and preventing them from writing anything to the shared storage. The fencing feature on the iRMC can request a shutdown of a remote device, if IPMI fencing is enabled. See the "C880 M5 User Interface" manual for how to enable IPMI fencing.

References

Information about the IPMI standards can be found on the Internet.

Cisco C880 M5 Configuration Guide

2.2 IPMI over LAN

2.2

IPMI over LAN

IPMI-over-LAN is the current name for the specification of the LAN interface in the IPMI standard. This specification stipulates how IPMI messages can be sent to or from the BMC of a managed system - encapsulated in RMCP (Remote Management Control Protocol) data packets. These RMCP data packets are transferred via an Ethernet LAN connection using the UDP (User Datagram Protocol) under IPv4 (Internet Protocol Version 4).

The RMCP protocol has been specified to support the management of system statuses in which the operating system is not running. The RMCP is a simple inquiry/response protocol.

The interface for such a connection is provided on an onboard LAN controller assigned to the BMC.

The interface can only be provided by an on-board LAN controller, not by

an inserted LAN card.

Of the two ports that RCMP uses under UDP, the BMC communicates with the LAN controller via port 623 (primary RMCP Port).

Figure 3: BMC and LAN controller

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

2.3

Supported IPMI O EM Commands

The following OEM-specific IPMI commands are supported by the iRMC S5:

SCCI-compliant Power On/Off commands (SCCI: Server Common Command Interface)

0115 Get Power On Source 0116 Get Power Off Source 011C Set Power Off Inhibit 011D Get Power Off Inhibit 0120 Set Next Power On Time SCCI-compliant signaling commands

1002 Write to System Display

BIOS-specific command

F109 Get BIOS POST State F115 Get CPU Info iRMC S5-specific commands F510 Get System Status

F512 Get EEPROM Version Info F542 Get HDD lightpath status (Component Status Signal Read) F543 Get SEL entry long text F545 Get SEL entry text F5B0 Set Identify LED F5B1 Get Identify LED F5B3 Get Error LED F5E0 Set Configuration Space to Default Values F5F8 Delete User ID

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

The following sections describe the individual OEM-specific IPMI commands. Description format The OEM-specif ic IPMI commands contained in this chapter are described in the

format used by the IPMI standard for describing IPMI commands. The IPMI standard describes the IPMI commands using command tables which

list the input and output parameters for each command. You can find information on the IPMI standards on the Internet.

2.3.1

SCCI-compliant Power On/Off commands

01 15 - Get Power On Source

This command returns the reason for the most recent Power On. The possible reasons are listed below.

Request Data

B8 NetFnlLUN: OEM/Group

01 Cmd : Command Group Communication

1:3

80 28 00 IANA-Enterprise-Number FTS, LS byte first

15 Command specifier

Response Data -

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS byte first

01 Data Length

Power on Source: Cause of last power on

Power on Source

Description

0x00 Software or command 0x01 Power switch (on the front panel or keyboard) 0x02 Automatic restart after an AC power failure 0x03 Clock or timer (hardware RTC or software timer) 0x04 Automatic res tart after fan failure shutdown 0x05 Automatic restart after critical temperature shutdown

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

Power on Source

Description

0x08 Reboot after watchdog timeout 0x09 Remote on (modem RI line, SCSI termination power, LAN, chip card 0x0C Reboot after a CPU error 0x15 Reboot by hardware reset 0x16 Reboot after warm start 0x1A Powered on by a PCI Bus Power Management Event 0x1D Powered on by remote control via remote manager 0x1E Reboot/ r eset by remote control via remote manager 0x24 Automatic Power on/off for VIOM Inventory Boot 0x25 Automatic Power on/off for VIOM Init Boot

01 16 - Get Power Off Source

This command returns the reason for the most recent Power Off. The possible reasons are listed below.

Request Data

B8 NetFnlLUN: OEM/Group

01 Cmd : Command Group Communication

1:3

80 28 00 IANA-Enterprise-Number FTS, LS byte first

16 Command specifier

Response Data -

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS byte first

01 Data length

Power off Source: Caus e of last power off

Power off Source

Description

0x00 Software (SWOFF, SE: power off by command) 0x01 Power switch (on the front panel or keyboard) 0x02 AC power fail 0x03 Clock or timer (hardware RTC or software timer)

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

Power off Source

Description

0x04 Fan failure 0x05 Critical temperatur e 0x08 Final power-off after repeated watchdog timeouts 0x0C Final power-off after repeated CPU errors 0x1D Powered off by remote control via remote manager 0x24 Automatic Power on/off for VIOM Inventory Boot 0x25 Automatic Power on/off for VIOM Init Boot

01 1C - Set Power Off Inhibit

This command sets the Power Off Inhibit flag, which temporarily suppresses any unfounded attempt to power down the server.

If the Power Off Inhibit flag is set, the firmware saves the cause of any attempt to perform a Power Off, Power Cycle or restart of the server, but does not perform the action. The cause of the most recent attempt to perform a Power Off, Power Cycle or restart of the server is always saved at any given time. The stored action is only performed when the Power Off Inhibit flag is reset.

The Power Off Inhibit flag is automatically reset after a power failure or when the reset button is pressed.

The effect of the Power Off Inhibit flag is the same as that of the Dump flag used when creating a main memory dump. In this case, the initiator must set the flag before making the dump and reset it when the dump is complete.

Request Data

B8 NetFn|LUN: OEM/Group

01 Cmd : Command Group Communication

1:3

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

1C Command specifier

00 Object ID

6:7

00 00 Value ID

01 Data length

Power Off Inhibit Flag: 0 no Inhibit, 1 Inhibit

Response Data -

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

01 1D - Get Power Off Inhibit

This command gets the value of the Power Off Inhibit flag. For more information on the Power Off Inhibit flag, refer to the description

of "01 1C - Set Power Off Inhibit".

Request Data

B8 NetFn|LUN: OEM/Group

01 Cmd : Command Group Communication

1:3

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

1D Command specifier

Response Data -

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

01 Response data length

Power Off Inhibit Flag: 0 no Inhibit, 1 Inhibit

01 20 - Set Next Power On Time

This command switches on a system at the given time independent of the stored On/Off times in the configuration space.

The command takes effect only once.

You cancel a Power On time previously set with a 01 20 command by specifying the Power On time “0” in a subsequent 01 20 command.

Request Data

B8 NetFnlLUN: OEM/Group

01 Cmd : Command Group Communication

1:3

80 28 00 IANA-Enterprise-Number FTS, LS byte first

20 Command specifier

00 Object ID

6:7

00 00 Value ID

04 Data length

9:12 Time (LSB first)

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

Response Data -

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS byte first

Time (LSB first)

Time (UNIX-specific format) when the system switches on again. Time is NOT stored in non-volatile memory. Resolution is 1 minute. After the system has switched on, Time is set to 0 internally. If Time == 0, the system is not switched on.

2.3.2

SCCI-compliant signaling command

10 02 - Write to System Display

This command is used to write characters to the LocalView display (if connected).

Request Data

B8 NetFnlLUN: OEM/Group

10 Cmd : Command Group fan test

1:3

80 28 00 IANA-Enterprise-Number FTS, LS byte first

02 Command specifier

Object Index : Line on display to write on.

6:7

Value ID (not used)

Length Number of characters to write, incremented by one. (The string needs not to be null-terminated; characters exceeding the length of a display line are truncated.)

Attribute:

0 = Write string left aligned. 1 = Write string centered.

10:10+n

Characters to write to the display; string needs not to be nullterminated.

Response Data

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS byte first

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

2.3.3

BIOS-specific commands

F1 09 - Get BIOS POST State

This command provides information whether BIOS is in POST.

Request Data -

NetFnlLUN: OEM/Group

Cmd : Command Group BIOS

1:3

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

Command Specifier

Response Data

Complet ion Code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

[7:3] - reserved

[0]

- BIOS POST State : 0 = BIOS is not in POST 1 = BIOS is in POST

[1]

- BIOS Video State: 0 = Video initialization is not yet

done 1 = Video initialization is done

[2]

- Uncorrectable Error Indicators State: 0 = Indicators are not yet cleared

F1 15 - Get CPU Info

This command returns CPU-internal information. The iRMC gets this information from the BIOS during the POST phase.

Request Data

B8 NetFnlLUN: OEM/Group

F1 Cmd : Command Group BIOS

1:3

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

15 Command Specifier

Socket Number (0-based) of the CPU

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

Response Data

Completion Code:

01 = Unpopulated CPU Socket

2:4

80 28 00 IANA-Enterprise-Number FTS, LS Byte first 5:6 CPU ID, LS Byte first 7

Platform ID

Brand ID 9:10 Maximal Core Speed of the CPU [MHz], LS Byte first 11:12 Intel Ultra path Interconnect in Mega Transactions per

second, LS Byte first 13 T-Control Offset 14 T-Diode Offset 15 CPU TJ max 16:17 Record ID CPU Info SDR, LS Byte first 18:19 Record ID Fan Control SDR, LS Byte first 20:21 CPU ID High Word, LS Byte first (optional) (N/A = 0000h) 22:23 Thermal Design Power TDP value with 1/8W granularity,

LS Byte first (optional) (N/A = FFFFh) 24:25 Cache Size (L1) (sum of all L1 caches of socket) Unit

[KB] if MSBit = 0, [MB] if MSBit = 1, LS Byte first (N/A =

FFFFh) 26:27 Cache Size (L2) (sum of all L2 caches of socket) Unit

[KB] if MSBit = 0, [MB] if MSBit = 1, LS Byte first (N/A =

FFFFh) 28:29 Cache Size (L3) (sum of all L3 caches of socket) Unit

[KB] if MSBit = 0, [MB] if MSBit = 1, LS Byte first (N/A =

FFFFh) 30 Maximal Corecount (N/A = FFh)

31 Current Corecount (N/A = FFh) 32 Maximal Threads per Core (N/A = FFh) 33 Current Threads per Core (N/A = FFh) 34:35 CPU Family from SMBIOS (structure 4, offset 6) 36 CPU Manufacturer: 0 = unknown, 1 = INTEL, 2 = AMD

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

2.3.4

iRMC S5-specific commands

F5 10 - Get System Status

This command returns a variety of internal information on the system such as the power state, error status, etc.

Request Data

B8 NetFnlLUN: OEM/Group

F5 Cmd : Command Group Memory

1:3

80 28 00 IANA-Enterprise-Number FTS, LS byte first

10 Command Specifier

5:8

Timestamp

Response Data -

Completion Code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS byte first

System Status

Signaling

Notifications

POST Code

The Timestamp is only relevant for evaluating the Notifications Byte.

System Status Signaling Notifications

Bit 7 - System ON Localize LED SEL Modified (new SEL entry) Bit 6 -

SEL Modified (SEL Cleared)

Bit 5 -

SDR Modified

Bit 4 - SEL entries available

Nonvolatile IPMI variable modified

Bit 3 -

CSS LED ConfigSpace modified Bit 2 - Watchdog active CSS LED Bit 1 - Bit 0 - Post State Global Error LED New Output on LocalView display

F5 12 - Get EEPROM Version Info

This command returns information on the current versions (bootloader, firmware and SDR) stored in the EEPROM(s).

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

Request Data -

B8 NetFnlLUN: OEM/Group

F5 Cmd : Command Group Memory

1:3

80 28 00 IANA-Enterprise-Number FTS, LS byte first

12 Command Specifier

EEPROM# 00=EEPROM 1; 01=EEPROM 2

Response Data -

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS byte first

Status 00=Checksum error runtime FW, 01=OK

Major FW Revision Binary coded

Minor FW Revision BCD coded

8:10

Aux. FW Revision Binary coded (major/minor/res.)

Major FW Revision ASCII coded letter

Major SDRR Revision BCD coded

Minor SDRR Revision BCD coded

SDRR Revision Char. ASCII coded letter

SDRR-ID LSB binary coded

SDRR-ID MSB binary coded

Major Booter Revision Binary coded

Major Booter Revision BCD coded

19:20 Aux. Booter Revision Binary coded (major/minor)

F5 42 - Get HDD lightpath status (Component Status Signal Read)

Light path diagnostics is a system of LEDs on the control panel and on the system board. When an error occurs, LEDs are lit. If the control panel indicates an error, use the descriptions of the LEDs to diagnose the problem and take corrective action.

This command returns information on the state of a hard disk drive (HDD) slot.

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

Request Data

NetFn|LUN: OEM/Group

Cmd : Command Group iRMC

1:3

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

Command specifier

Entity ID (Table 37-12 of IPMI 1.5 Spec.) of Component whose status signal is to be read.

Entity Instance (0-based) of Component whose status signal is to be read.

Sensor Type (Table 36-3 of IPMISpec.) of the sensor which reports the status of the component to which the status signal is associated.

(8) Option (optional)

Bit 7:2 - Reserved Bit 1 :Completion code 0x02 suppressed

Bit 0 - 1 : Retu rn ID string of component status Sensor

Response Data

Completion Code:

01 = Status signal not available 02 = Component not present

2:4

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

Signal Status:

00 = ok 01 = Identify 02 = Prefailure warning

03 = Failure

CSS and Physical LED available:

Bit 6:0 - 0= No physical LED available Bit 6:0 > 00 = Physical LED available, single or multiple color, code Bit 7 = 0: No CSS component Bit 7 = 1: CSS component

(7) Lengt h of ID string of component status sensor

(only present if Bit 0 in requested Byte 8 is set)

(8:m) Length of ID string of component status sensor in ASCII

characters (only present if Bit 0 in requested Byte 8 is set)

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

F5 43 - Get SEL entry long text

This command translates a given SEL entry into long text.

Request Data

B8 NetFn|LUN: OEM/Group

F5 Cmd : Command group iRMC

1:3

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

43 Command specifier

5:6

Record ID of SEL record, LS Byte first 0x0000: get

first

record 0xFFFF: get last record

Offset in response SEL text

MaxResponseDataSize size of converted SEL data

(16:n) in response

(on Pilot-1 designs the max data size is 56 bytes)

Response Data

Completion Code:

2:4

80 28 00 IANA-Enterprise-Number FTS, LS Byte first 5:6 Next Record ID 7:8

Actual Record ID

Record type

10:13

Timestamp

Severity: Bit 7: 0 = No CSS component

1 = CSS component

Bit 6-4: 000 = INFORMATIONAL

001 = MINOR

010 = MAJOR

011 = CRITICAL

1xx = Unknown’

Bit 3-0: reserved, read as 0000

Data length of the whole text 16:n

Converted SEL data requested part

(n = 16 + MaxResponseDataSize - 1)

n + 1

String Terminator trailing '\0' character

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

F5 45 - Get SEL Entry Short Text

This command translates a given System Event Log SEL entry into ASCII text.

Request Data -

B8 NetFnlLUN: OEM/Group

F5 Cmd : Command Group iRMC

1:3

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

45 Command specifier

5:6

Record ID of SDR, LS Byte first

Response Data -

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS Byte first

5:6

Next Record ID

7:8

Actual Record ID

Record type

10:13

Timestamp

Severity: Bit 7: 0 = No CSS component

1 = CSS component

Bit 6-4: 000 = INFORMATIONAL

001 = MINOR

010 = MAJOR

011 = CRITICAL

1xx = Unknown’

Bit 3-0: reserved, read as 0000

Data length without trailing null terminator

16:35

Converted SEL data as ASCII, 20 bytes maximum

n+1

Trailing Null

Cisco C880 M5 Configuration Guide

2.3 Supported IPMI OEM Commands

F5 B0 - Set Identify LED

This command allows you to switch the Identify LED (blue) of the server on and off. In addition, you can set and read the GPIOs that are directly connected to the Identify LED.

You can also switch the Identify LED on and off using the Identify switch

on the server.

Request Data

NetFnlLUN: OEM/Group

Cmd : Command Group BMC

1:3

80 28 00 IANA-Enterprise-Number FTS, LS byte first

Command specifier

Identify LED:

0: Identify LED off 1: Identify LED on 2: Identify LED blinking

Response Data -

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS byte first

F5 B1 - Get Identify LED

This command returns information on the status of the Identify LED (blue) of the server.

Request Data

NetFnlLUN: OEM/Group

Cmd : Command Group BMC

1:3

80 28 00 IANA-Enterprise-Number FTS, LS byte first

Command specifier

Response Data -

Completion code

2:4

80 28 00 IANA-Enterprise-Number FTS, LS byte first

State of Identify LED:

0: Identify LED off 1: Identify LED on 2: Identify LED blinking

+ 60 hidden pages

Cisco C880 M5 Configuration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual