Kontron ME1100 User Manual

Download



USER GUIDE

ME1100

Doc. Rev. 1.3

ME1100 Doc. Rev. 1.3

www.kontron.com // 2



ME1100 - USER GUIDE

Disclaimer

Kontron would like to point out that the information contained in this manual may be subject to alteration, particularly as a result of the constant upgrading of Kontron products. This document does not entail any guarantee on the part of Kontron with respect to technical processes described in the manual or any product characteristics set out in the manual. Kontron assumes no responsibility or liability for the use of the described product(s), conveys no license or title under any patent, copyright or mask work rights to these products and makes no representations or warranties that these products are free from patent, copyright or mask work right infringement unless otherwise specified. Applications that are described in this manual are for illustration purposes only. Kontron makes no representation or warranty that such application will be suitable for the specified use without further testing or modification. Kontron expressly informs the user that this manual only contains a general description of processes and instructions which may not be applicable in every individual case. In cases of doubt, please contact Kontron.

This manual is protected by copyright. All rights are reserved by Kontron. No part of this document may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), without the express written permission of Kontron. Kontron points out that the information contained in this manual is constantly being updated in line with the technical alterations and improvements made by Kontron to the products and thus this manual only reflects the technical status of the products by Kontron at the time of publishing.

Kontron S&T Ag Lise-Meitner-Str. 3-5

86156 Augsburg Germany www.kontron.com

ME1100 Doc. Rev. 1.3

www.kontron.com // 3

Revision History

Revision

Brief Description of Changes

Date of Issue

1.0

Preliminary release

2017-May-02

1.1

Production release

2018-Oct-31

1.2

DC PSU information added

2018-Nov-26

1.3

New information about BIOS updates in section 7

2019-Feb-25

Customer Support

Find Kontron contacts by visiting: http://www.kontron.com/support.

Customer Service

Kontron, a trusted technology innovator and global solutions provider, uses its embedded market strengths to deliver a service portfolio that helps companies break the barriers of traditional product lifecycles. Through proven product expertise and collaborative, expert support, Kontron provides unparalleled peace of mind when it comes to building and maintaining successful products.

including enhanced repair services, an extended warranty, and the

Kontron training academy visit www.kontron.com/support-and-services/services.

Customer Comments

If you have any difficulties using this guide, discover an error, or just want to provide some feedback, please contact Kontron support. Detail any errors you find. We will correct the errors or problems as soon as possible and post the revised user guide on our website.

Thank you.

ME1100 Doc. Rev. 1.3

www.kontron.com // 4

Symbols

The following symbols may be used in this manual

DANGER indicates a hazardous situation which, if not avoided, will result in death or serious injury.

WARNING indicates a hazardous situation which, if not avoided, could result in death or serious injury.

CAUTION indicates a hazardous situation which, if not avoided, may result in minor or moderate injury.

NOTICE indicates a property damage message.

Electric Shock! This symbol and title warn of hazards due to electrical shocks (> 60 V) when touching

products or parts of them. Failure to observe the precautions indicated and/or prescribed by the law may endanger life/health and/or result in damage to material.

Please also refer to the "High-Voltage Safety Instructions" portion below in this section.

ESD Sensitive Device! This symbol and title inform that the electronic boards and their components are sensitive

to static electricity. Care must therefore be taken during all handling operations and inspections of this product in order to ensure product integrity at all times.

HOT Surface! Do NOT touch! Allow to cool before servicing.

This symbol indicates general information about the product and the user manual. This symbol also indicates detail information about the specific product configuration.

This symbol precedes helpful hints and tips for daily use.

ME1100 Doc. Rev. 1.3

www.kontron.com // 5

Table of Contents

Symbols ................................................................................................................................................................................................................ 4

Table of Contents ............................................................................................................................................................................................... 5

List of Tables ........................................................................................................................................................................................................ 6

List of Figures ...................................................................................................................................................................................................... 6

List of Acronyms ................................................................................................................................................................................................. 7

Electrostatic Discharge ................................................................................................................................................................................... 8

Limited Warranty............................................................................................................................................................................................... 8

ME1100 Safety and Regulatory Information ................................................................................................................................ 9

General Safety Warnings and Cautions ................................................................................................................................................ 9

General Power Safety Warnings and Cautions ................................................................................................................................. 9

1.2.1. Elevated Operating Ambient Temperature ...................................................................................................................................... 9

1.2.2. Reduced Air Flow ..................................................................................................................................................................................... 9

1.2.3. Mechanical Loading ................................................................................................................................................................................ 9

1.2.4. Circuit Overloading ................................................................................................................................................................................ 10

1.2.5. DC Power Supply Safety ...................................................................................................................................................................... 10

1.2.6. Reliable Earth-Grounding ................................................................................................................................................................... 10

1.2.7. Regulatory Specifications .................................................................................................................................................................... 11

1.2.8. CE Mark ...................................................................................................................................................................................................... 11

1.2.9. Waste Electrical and Electronic Equipment Directive ................................................................................................................ 11

Shipping Box Contents ...................................................................................................................................................................... 12

Recommended Optional Components ............................................................................................................................................... 12

Product Description ........................................................................................................................................................................... 13

Product Overview ...................................................................................................................................................................................... 13

Block Diagram ............................................................................................................................................................................................ 13

Serial Port Component Access ............................................................................................................................................................. 14

Physical Dimensions ............................................................................................................................................................................... 14

Environmental Specifications .............................................................................................................................................................. 15

Feature Summary ..................................................................................................................................................................................... 16

Server Components ................................................................................................................................................................................. 18

3.7.1. Front Panel ................................................................................................................................................................ ............................... 18

3.7.2. Serial Port Connector Pinout ............................................................................................................................................................. 18

3.7.3. LED and Button Behavior ................................................................................................................................ .................................... 19

3.7.4. Fans and Filter ....................................................................................................................................................................................... 21

3.7.4.1. Cooling and Thermal Management ............................................................................................................................................. 22

3.7.5. Power Supply Unit ................................................................................................................................................................................ 23

3.7.5.1. DC Power Supply Mating Cable Preparation ............................................................................................................................ 23

3.7.6. PCIe Add-in Card ................................................................................................................................................................................... 25

3.7.7. Optional 2.5-in SSD .............................................................................................................................................................................. 28

Typical Power Consumption ................................................................................................................................................................ 30

BMC Access ............................................................................................................................................................................................... 30

PCI Mapping .............................................................................................................................................................................................. 31

MAC Addresses ....................................................................................................................................................................................... 32

Interfaces ................................................................................................................................................................................................. 33

Description of Interface Access Methods ................................................................................................................................. 36

Paths to the Operating System Prompt ........................................................................................................................................... 36

Paths to the ME1100 embedded IPMITOOL shell .......................................................................................................................... 37

Getting Started ................................................................................................................................................................................... 38

ME1100 Doc. Rev. 1.3

www.kontron.com // 6

Connect the Power Supply .................................................................................................................................................................... 38

5.1.1. DC Power Supply .................................................................................................................................................................................... 38

Establish a Serial Console Connection ............................................................................................................................................. 38

Log In to the BMC/FRU0 of the ME1100 ........................................................................................................................................... 39

Configure and Set the IP Address of BMC/FRU0 (Static or DHCP) .......................................................................................... 40

Enable Remote Management Using the IPMI Protocol ............................................................................................................... 40

Verify BMC/FRU0 Network Configuration........................................................................................................................................ 41

Optional Configurations, Monitoring and Operation ............................................................................................................. 42

CPU Power ON, Power OFF and Reset ............................................................................................................................................... 42

Chassis ID Led Control ........................................................................................................................................................................... 43

Boot Order .................................................................................................................................................................................................. 43

OS Installation .......................................................................................................................................................................................... 44

Disable Remote Management Using the IPMI Protocol .............................................................................................................. 45

Disable a BMC LAN Interface ............................................................................................................................................................... 45

Performing Updates ......................................................................................................................................................................... 46

Update the Firmware .............................................................................................................................................................................. 46

Appendix A: Sensor List ................................................................................................................................................................................. 47

Appendix B: IPMI Command List ................................................................................................................................................................. 54

Appendix C: Additional Options to Configure IOL Interfaces ............................................................................................................. 59

Appendix D: User Application Providing Feedback to BMC ................................................................................................................ 61

......................................................................................................................................... 70

List of Tables

Table 1: Safety compliance ............................................................................................................................................................................. 11

Table 2: Electromagnetic compatibility ..................................................................................................................................................... 11

Table 3: Chassis dimensions ......................................................................................................................................................................... 14

Table 4: Environmental tests and standards.......................................................................................................................................... 15

Table 5: Key hardware features .................................................................................................................................................................. 16

Table 6: Key software features ................................................................................................................................................................... 17

Table 7: ID and power LED behavior ........................................................................................................................................................... 19

Table 8: Status LED behavior ....................................................................................................................................................................... 20

Table 9: Reset button behavior ................................................................................................................................................................... 20

Table 10: Management LED behavior ....................................................................................................................................................... 20

Table 11: SFP+ LED behavior ......................................................................................................................................................................... 20

Table 12: Power supply rating ..................................................................................................................................................................... 23

Table 13: DC power supply inlet .................................................................................................................................................................. 23

Table 14: Mating terminals suggested for the DC power supply .................................................................................................... 23

Table 15: PCI mapping ..................................................................................................................................................................................... 31

Table 16: MAC addresses .............................................................................................................................................................................. 32

Table 17: Default IP addresses .................................................................................................................................................................... 33

Table 18: Default usernames and passwords ....................................................................................................................................... 35

Table 19: BMC sensor list .............................................................................................................................................................................. 47

Table 20: Detailed information for Kontron OEM Firmware Info ..................................................................................................... 51

Table 21: Supported and unsupported commands for FRU0 ............................................................................................................ 54

Table 22: Default IP addresses ................................................................................................................................................................... 60

List of Figures

Figure 1: Earth ground lug location ............................................................................................................................................................. 10

Figure 2: WEEE directive logo ........................................................................................................................................................................ 11

Figure 3: ME1100 block diagram .................................................................................................................................................................. 13

ME1100 Doc. Rev. 1.3

www.kontron.com // 7

Figure 4: Serial port component access ................................................................................................................................................... 14

Figure 5: ME1100 front view .......................................................................................................................................................................... 18

Figure 6: Serial port pinout ............................................................................................................................................................................ 18

Figure 7: Server LEDs and Button ................................................................................................................................................................ 19

Figure 8: Hot-swappable fan tray .............................................................................................................................................................. 21

Figure 9: Hot-swappable filter tray ............................................................................................................................................................ 21

Figure 10: Temperature management ...................................................................................................................................................... 22

Figure 11: DC Power Supply Cable Preparation and Connection ...................................................................................................... 24

Figure 12: Rear mounting bracket position for a FH3/4L PCIe add-in card .................................................................................. 25

Figure 13: Rear mounting bracket position for a FHHL PCIe add-in card ...................................................................................... 25

Figure 14: PCIe riser card and front plate adaptor assembly ........................................................................................................... 26

Figure 15: PCIe add-in card installation in ME1100 ............................................................................................................................... 27

Figure 16: Assembled PCIe card .................................................................................................................................................................. 27

Figure 17: 2.5-in SSD installation in a carrier bracket .......................................................................................................................... 28

Figure 18: SSD carrier bracket insertion ................................................................................................................................................... 29

Figure 19: SSD carrier bracket attachment ............................................................................................................................................. 29

Figure 20: Default IP addresses in an ME1100 server ......................................................................................................................... 33

Figure 21: Diagram of interface paths with a serial console connection ...................................................................................... 34

Figure 22: Diagram of interface paths with a management networking connection .............................................................. 35

Figure 23: Default IP addresses in a ME1100 server ............................................................................................................................ 60

List of Acronyms

ACPI

Advanced Configuration & Power Interface

BMC

Baseboard Management Controller

CLI

Command-Line Interface

DHCP

Dynamic Host Configuration Protocol

EMC

Electromagnetic Compatibility

ETSI

European Telecommunications Standards Institute

FH3/4L

Full-height, three-quarter length

FHHL

Full-height, half length

FRU

Field Replaceable Unit

IOL

IPMI Over-LAN

IPMI

Intelligent Platform Management Interface

KCS

Keyboard Controller Style

LPC

Low Pin Count

MAT

Maximum Ambient Temperature

MEC

Mobile Edge Computing

NCSI

Network Communications Services Interface

PCH

Platform Controller Hub

PCIe

PCI-Express

PECI

Platform Environment Control Interface

PXE

Preboot eXecution Environment

RAN

Radio Access Network

RDP

Remote Desktop

SEL

System Event Log

SFP+

Small Form-factor Pluggable that supports data rates up to 10.0 Gbps

SOC

System on a Chip

SOL

Serial Over LAN

SSH

Secure Shell

WEEE

Waste Electrical and Electronic Equipment

ME1100 Doc. Rev. 1.3

www.kontron.com // 8

Electrostatic Discharge

ESD Sensitive Device! ME1100 Mobile Edge servers are sensitive to electrostatic discharge (ESD). Users must take

the appropriate precautions when handling ESD-sensitive devices.

Limited Warranty

Please refer to the full terms and https://www.kontron.com/support-and-services/rma/canada/standard_warranty_policy_canada.pdf.

ME1100 Doc. Rev. 1.3

www.kontron.com // 9

ME1100 Safety and Regulatory Information

Before working with SYMKLOUD products or performing instructions described in this guide or other SYMKLOUD guides, read the safety and warning information in this section. Assembly instructions in this guide must be followed to ensure and maintain compliance with existing product certifications and approvals. Use only the described, regulated components specified in this guide. Use of other products/components will void the CSA certification and other regulatory approvals of the product and will most likely result in non-compliance with product regulations in the region(s) in which the product is sold.

General Safety Warnings and Cautions

To prevent a fire or shock hazard, do not expose this product to rain or moisture. The chassis should not be exposed to dripping or splashing liquids and no objects filled with liquids should be placed on the chassis cover.

General Power Safety Warnings and Cautions

This product usually has more than one power supply cord. Disconnect all power supply cords before servicing to avoid electric shock.

Installation of this product must be performed in accordance with national wiring codes and conform to local regulations.

1.2.1. Elevated Operating Ambient Temperature

If this product is installed in a closed or multi-unit rack assembly, the operating ambient temperature of the rack environment may be greater than the ambient temperature of the room. Therefore, be careful to install the product in an environment that is compatible with the maximum ambient temperature specified by the manufacturer (MAT = 65oC).

1.2.2. Reduced Air Flow

Do not compromise on the amount of air flow required for safe operation when installing this product in a rack (see side clearances in Section 3.3).

1.2.3. Mechanical Loading

Do not load the equipment unevenly when mounting this product in a rack as it may create hazardous conditions.

ME1100 Doc. Rev. 1.3

www.kontron.com // 10

1.2.4. Circuit Overloading

Do not overload the circuits when connecting this product to the supply circuit as this can adversely affect overcurrent protection and supply wiring. Check the supply equipment nameplate ratings for correct use.

1.2.5. DC Power Supply Safety

ME1100 servers equipped with a DC power supply must be installed in a restricted access area. When powered by DC current, this equipment must be protected by a listed branch circuit protector with a maximum 20 A rating. The DC source must be electrically isolated from any hazardous AC source by double or reinforced insulation.

The DC power supply is protected from reverse polarity by internal diodes and will not operate at all if wired incorrectly.

This equipment is designed for the earth grounded conductor (return) in the DC supply circuit to be connected to the earth grounding conductor on the equipment (ground lug).

All of the following conditions must be met:

1. This equipment shall be connected directly to the d.c. supply system earthing electrode conductor or to a

bonding jumper from an earthing terminal bar or bus to which the d.c. supply system earthing electrode conductor is connected.

2. This equipment shall be located in the same immediate area (such as adjacent cabinets) as any other equipment

that has a connection between the earthed conductor of the same d.c. supply circuit and the earthing conductor, and also the point of earthing of the d.c. system. The d.c. system shall not be earthed elsewhere.

3. The d.c. supply source shall be located within the same premises as this equipment.

4. Switching or disconnecting devices shall not be in the earthed circuit conductor between the d.c. source and the

point of the connection of the earthing electrode conductor.

1.2.6. Reliable Earth-Grounding

Always maintain reliable grounding of rack-mounted equipment.

Figure 1: Earth ground lug location

ME1100 Doc. Rev. 1.3

www.kontron.com // 11

1.2.7. Regulatory Specifications

The ME1100 server meets the requirements of the following regulatory tests and standards:

Table 1: Safety compliance

USA/Canada

This product is marked cCSAus

Europe

This product complies with the Low Voltage Directive, 2014/35/EU and EN 60590-1

International

This product has a CB report and certificate to IEC 60950-1

Table 2: Electromagnetic compatibility

USA/Canada

This product meets FCC Part 15/ICES-003 Class A. It is designed to meet GR-1089 and GR-63.

Europe

This product complies with the Electromagnetic Compatibility Directive 2014/30/EU and EN 300 386. The GPS version complies with Radio Equipment Directive 2014/53/EU, EN 301 489-1 and EN 303 413.

International

This product complies with CISPR 32 Class A and CISPR 24.

1.2.8. CE Mark

The CE marking on this product indicates that it is in compliance with the applicable European Union Directives: Low Voltage, EMC, Radio Equipment and RoHS requirements.

1.2.9. Waste Electrical and Electronic Equipment Directive

This product contains electrical or electronic materials. If not disposed of properly, these materials may have potential adverse effects on the environment and human health. The presence of this logo on the product means it should not be disposed of as unsorted waste and must be collected separately.

Dispose of this product according to the appropriate local rules, regulations and laws.

Figure 2: WEEE directive logo

ME1100 Doc. Rev. 1.3

www.kontron.com // 12

Shipping Box Contents

Server

One-page document with a QR code referring to online documentation

Kontron products have a QR code. This code provides the following information: serial number, part number, batch ID, and MAC address.

Recommended Optional Components

RJ45 to DB9 serial adaptor Kontron part number: 1015-9404

Note: The serial console port is compatible with Cisco 72-3383-01

Refer to Section 5/ for basic initial system connection.

ME1100 Doc. Rev. 1.3

www.kontron.com // 13

Product Description

Product Overview

ME1100 is a 1U rackmount, short depth (300mm), Xeon D-1500 server with two 10GbE SFP+ network interfaces, optional SATA storage and a PCIe extension slot. The ME1100 server is designed for Telco Edge virtual infrastructures and could be used with Kubernetes Kontron platforms.

The ME1100 is targeted for high-performance servers used in mobile edge computing (MEC) applications like Radio Access Network (RAN), Artificial Intelligence or Data Caching.

An operating system must be loaded on the CPU engine for the system to be operational.

Kontron products have a QR code. This code will provide the following information: serial number, part number, batch ID, and base MAC address.

To obtain the latest document version or to consult other SYMKLOUD documents, visit the SYMKLOUD portal at Symkloud.com.

Block Diagram

Figure 3: ME1100 block diagram

ME1100 Doc. Rev. 1.3

www.kontron.com // 14

Serial Port Component Access

When connecting to the serial interface, a multiplexing functionality (see Section 3.12) can establish a link with one of the following components:

 Baseboard Management Controller (BMC)  Server (CPU)

Figure 4: Serial port component access

Physical Dimensions

Table 3: Chassis dimensions

Chassis

Measurements (mm [in])

Notes

Depth

300 mm [11.811 in]

Body

Width

Standard 482.6 mm [19 in] rack (including ear brackets)

Body

Height

43.5 mm [1.713 in, 1U] MAX

Body

Front clearance

100 mm [4 in]

Recommended

Side clearance

70 mm [ 2.756 in]

Recommended

Rear clearance

None

Weight

5,5 kg

Configuration: 2x UDIMM memory and 1x M.2

SSD, 4x 2.5in SSD, no PCIe card (packaging included)

ME1100 Doc. Rev. 1.3

www.kontron.com // 15

Environmental Specifications

Table 4: Environmental tests and standards

Environment

Specification

Temperature, operating

0ºC to 65ºC (32ºF to 149ºF) The failure of one fan will not impact operation for at least 4 hours at 65 . Certain limitations may apply. These limitations could be the result of the

operating temperature range of installed configurable components (e.g., SFP+ module, SSD and PCIe card). Kontron recommends using SFP+ and SSD modules with an industrial operating temperature range. Another limitation can result from airflow obstruction caused by fan filter clogging and failure to follow recommended side clearances.

Temperature, non-operating

-40ºC to 70ºC (-40ºF to 158ºF)

Humidity, operating

This product is designed to meet a test profile based on Telcordia GR-63, ETSI EN 300 019-2-3 class 3.1E, 5% to 93% non-condensing at 40ºC.

Humidity, non-operating (Transportation)

This product is designed to meet a test profile based on ETSI EN 300 019-2-2 class

2.3, to 93% (long term), 90% to 100% (short term) at 40 ºC.

Humidity, non-operating (storage)

This product is designed to meet a test profile based on ETSI EN 300 019-2-1 class

1.2, to 93% (long term), condensing to 100% (short term) at 30 ºC.

Altitude/pressure, operating

-60 m to 1,800 m altitude without temperature de-rating Up to 4,000 m altitude with temperature de-rating of 1 degree Celsius per 300 m

above 1,800 m

Altitude/pressure, nonoperating

Up to 4,570 m

Vibration, operating

This product meets operational swept sine vibration Test profile based on GR-63 clause 5.4.2, and ETSI EN 300 019-2-3 class 3.2 5 Hz to 200 Hz at 0.2 g

This product meets operational random vibration Test profile based on ETSI EN 300 019-2-3 class 3.2 5 Hz to 10 Hz at +12 dB/octave (slope up) 10 Hz to 50 Hz at 0.02 m2/s3 (0.0002 g2/Hz) (flat) 50 Hz to 100 Hz at -12 dB/octave (slope down) 30 minutes for each of the three axes

Vibration, non-operating

This product meets transportation and storage swept sine vibration Test profile based on ETSI EN 300 019-2-1 class 1.2 5 Hz to 200 Hz at 0.2 g This product meets transportation and storage random vibration Test profile based on GR-63 clause 5.4.3, and ETSI EN 300 019-2-2 class 2.3 5 Hz to 20 Hz at 1 m2/s3 (0.01 g2/Hz) (flat) 20 Hz to 200 Hz at -3 dB/octave (slope down) 30 minutes for each of the three axes

Shock, operating

This product meets operational shock standards Test profile based on ETSI EN 300 019-2-3 class 3.2 11 ms half sine, 3 g, three shocks in each direction

Shock, non-operating

This product meets transportation and storage half sine shock Test profile based on ETSI EN 300 019-2-2 class 3.2 6 ms half sine, 18 g, 100 shocks in each direction

Drop/free fall

This product meets Bellcore GR-63 section 5.3 Packaged = 1,000 mm, six surfaces, three edges and four corners Unpackaged = 100 mm, two sides and two bottom corners

ME1100 Doc. Rev. 1.3

www.kontron.com // 16

Environment

Specification

Electrostatic discharge

This product meets 8 kV contact, 15 kV air discharge using IEC 61000-4-2 Test Method

RoHS

This product is designed to meet China RoHS Phase 1 (self-declaration and labeling) This product complies with EU directive 2002/96/EC (WEEE) This product complies with RoHS directive 2011/65/EU

Feature Summary

Table 5: Key hardware features

Feature

Description

Hardware platform

High-performance server for mobile edge computing (MEC) 1U height, 300mm deep, 19 inches wide Hot-swappable fan tray and filter

Front access only (motherboard I/O, PSU, PCIe card I/O, fan tray)

I/O

Two 10GbE SFP+ One USB 2.0 One RJ45 10/100/1000Base-T management port One RJ45 serial port One reset button

PCIe add-in card

One optional FH/HL or FH/¾L PCIe x16 card supported (power and thermal restrictions may apply)

The maximum power consumption supported is 50 W Refer to the Hardware Compatibility List available on

Symkloud.com

CPU

Intel® Xeon® D-1500 family processors are supported, including (but not limited to) the following processors:

 Xeon D-1548, 8 Cores @ 2.00GHz, 45W  Xeon D-1567, 12 Cores @ 2.10GHz, 65W  Xeon D-1559, 12 Cores @ 1.50GHz, 45W

SSD

One M.2 SSD option:

 Refer to the Hardware Compatibility List available on

Symkloud.com

Four 2.5-in SSD option:

 Refer to the Hardware Compatibility List available on

Symkloud.com

Memory

DDR4 DIMM with ECC

 Bandwidth up to 2400 MT/s  Two memory channels  One DIMM socket per channel  Refer to the Hardware Compatibility List available on

Symkloud.com

Power supplies

PSU: One -57 VDC to -40 VDC dual input feed

ME1100 Doc. Rev. 1.3

www.kontron.com // 17

Feature

Description

Fans

Hot-swappable fan tray:

 Fan tray contains 3 fans (standard configuration)  Fan tray contains 4 fans when 2.5-in SSD option is

installed Fan filter can be removed independently from the fan tray Fan speed control

Support

Product life cycle support for 3 to 5 years

Table 6: Key software features

Feature

Description

Server management

Integrated BMC this subsystem consists of communication buses, sensors, system BIOS, and server management firmware; it supports standard IPMI features as well as OEM (supplemental) features that are not part of IPMI

IPMI-based system monitor used for server monitoring, diagnostic and configuration

System event log Server power consumption monitoring Server power control Server and component health monitoring Fan speed monitoring Serial Over LAN console access IPMI Over LAN Sensor data record describing all sensors and providing their readings

(analog or discrete) ACPI state synchronization: the BMC tracks ACPI state changes that

are provided by the BIOS BIOS recovery

Operating system

Refer to the Hardware Compatibility List available on Symkloud.com

Thermal management

Platform Environment Control Interface (PECI) for thermal management support

Memory and CPU thermal management

ME1100 Doc. Rev. 1.3

www.kontron.com // 18

Server Components

3.7.1. Front Panel

Figure 5: ME1100 front view

3.7.2. Serial Port Connector Pinout

Figure 6: Serial port pinout

ME1100 Doc. Rev. 1.3

www.kontron.com // 19

3.7.3. LED and Button Behavior

Figure 7: Server LEDs and Button

Table 7: ID and power LED behavior

State

ID1 (blue)

Power (green)

Both power inputs DOWN or out of range for normal operation

OFF

One or both power inputs UP ACPI S5 state

OFF

Powering up ACPI S0 state

OFF

Rapid Blink (2 Hz)

BIOS started POST

OFF

Normal Blink (1 Hz)

BIOS hand over to OS boot loader

OFF

Normal Blink (1 Hz) or ON2

Application started/running OK

OFF

ON2

The ID LED can be made to blink at any time if a (manual) request is sent to the BMC (refer to Section 6.2).

A BIOS optional setting can opt to set the Power LED steady ON after POST (before starting the OS/application), but

the default BIOS setting is to leave that task to the application.

ME1100 Doc. Rev. 1.3

www.kontron.com // 20

Table 8: Status LED behavior

State

Status (amber/red)

No active error notification (normal operation)

OFF

Major alarm active

Amber ON

Critical alarm active (service/maintenance is required)

Red ON

Table 9: Reset button behavior

State

Behavior

Reset button pressed

CPU resets (does not affect the Management Controller)

Table 10: Management LED behavior

State

Management link (left green/yellow)

Management activity (right green)

No link

OFF

1000Base-T link established

Green ON

ON (no activity) Blinking (activity)

10/100Base-TX link established

Yellow ON

ON (no activity) Blinking (activity)

Table 11: SFP+ LED behavior

State

SFP+ (green)

Link established, no activity

ON (Speed 10/1 Gbps)

Activity

Blinking (Speed 10/1 Gbps)

No link

OFF

ME1100 Doc. Rev. 1.3

www.kontron.com // 21

3.7.4. Fans and Filter

The ME1100 server is equipped with a fan tray assembly comprised of fans and a filter. The filter can be pulled out by itself or the entire fan tray assembly (i.e., the fans and the filter) can be pulled out.

 To service the entire fan tray: unfasten the fan screw (see Figure 8).  To service the filter only: unfasten the filter screw (see Figure 9) and clean using oil-free compressed air.

Always replace the fan tray with the equivalent fan tray assembly (part number). Two fan tray kits are available for the ME1100 product. Fan tray with 3 fans (standard) and fan tray with 4 fans when ME1100 is configured with 2.5-in SSD. Using the wrong fan tray may cause thermal issue in the system.

Figure 8: Hot-swappable fan tray

Figure 9: Hot-swappable filter tray

ME1100 Doc. Rev. 1.3

www.kontron.com // 22

3.7.4.1. Cooling and Thermal Management

rated BMC.

The BMC uses information collected from on-board temperature sensors in order to adjust the speed of the fans and regulate the temperature of the platform according to a PID algorithm. The temperature sensors are aggregated to provide an input value to the system temperature PID regulator, which provides a speed command for the fans.

In addition to the sensors read by the BMC, other sensors can be read by a customer application, if available, running under the server Figure 10) and then reported to the BMC. As such, the PCIe add-in card temperature, as well as the M.2 and SFP+ temperatures, can be reported to the BMC by the customer application and considered by the fan speed regulator in its computation for thermal management function.

Refer to Appendix D for details on how a user application running on the CPU could access several data registers exposed by the board management hardware via the LPC interface.

Figure 10: Temperature management

ME1100 Doc. Rev. 1.3

www.kontron.com // 23

3.7.5. Power Supply Unit

Read the power safety warnings in Sections 1.1 and 1.2 before handling the power supply units.

Table 12: Power supply rating

Description

Input voltage range

Power (W)

DC power supply module

-57 to -40 VDC

240

Table 13: DC power supply inlet

Description

Maximum

input

current

PSU receptacle model

Mating terminal description

240W DC power

supply module

input connector

7.5 A

Amphenol (Anytek)

YK6050423000G

Spade or ring terminals, see Table 14

below

The thread of the two chassis ground lugs is M5x0.8.

Installation of this product must be in accordance with national wiring codes and conform to local regulations. Different types of line cord sets may be used for connections to the main supply circuit and must comply with the electrical code requirements of the country of use.

3.7.5.1. DC Power Supply Mating Cable Preparation

Kontron suggests using crimp lugs (ring or spade terminal, straight, isolated, UL94V-0) on the power cables. Connect the appropriate cable to the appropriate polarity.

Read the power safety warnings in Sections 1.1 and 1.2 before handling the power supply units.

Pliers may be used to bend the crimp lugs.

Table 14: Mating terminals suggested for the DC power supply

Terminal type

Wire

gauge

(AWG)

Manufacturer

Manufacturer part number

ME1100 Doc. Rev. 1.3

www.kontron.com // 24

Terminal type

Wire gauge (AWG)

Manufacturer

Manufacturer part number

Insulated spade

14-16

Molex

19131-0023

Insulated ring

10-12

Panduit

EV10-6RB-Q

Kontron suggests the following wire gauges for -48V DC and RTN: 14 AWG or 12 AWG.

Kontron suggests installing the terminals so the wires connected to the -48V DC and RTN terminal blocks go up toward the top of the chassis.

Figure 11: DC Power Supply Cable Preparation and Connection

ME1100 Doc. Rev. 1.3

www.kontron.com // 25

3.7.6. PCIe Add-in Card

A PCIe add-in card can be installed in the server as an option. The PCIe add-in card maximum form factor is fullheight, three-quarter length.

To install a PCIe add-in card:

1. Remove the top cover by unscrewing the 4 screws in the back and sliding the cover off toward the rear.

2. Install the rear mounting bracket as shown in Figure 12 for a FH3/4L PCIe add-in card or as shown in Figure 13 for

a FHHL PCIe add-in card. The figures used to describe the rest of the installation procedure show the bracket in FHHL position.

Figure 12: Rear mounting bracket position for a FH3/4L PCIe add-in card

Figure 13: Rear mounting bracket position for a FHHL PCIe add-in card

ME1100 Doc. Rev. 1.3

www.kontron.com // 26

3. Install the PCIe riser card onto the PCIe add-in card as shown in Figure 14.

4. Mount the front plate adaptor onto the PCIe add- -bracket as shown in Figure 14.

5. Fasten the front plate adaptor screw to the L-bracket (6 lbf·in torque) as shown in Figure 14.

Figure 14: PCIe riser card and front plate adaptor assembly

6. Carefully insert the PCIe card assembly into the server as shown in Figure 15.

7. Fasten the following 6 screws: 2 for the riser card onto the server motherboard (4 lbf·in torque), 2 for the PCIe

add-in card into the rear mounting bracket (4 lbf·in torque) and 2 captive screws into the front plate (4 lbf·in torque), as shown in Figure 15.

ME1100 Doc. Rev. 1.3

www.kontron.com // 27

Figure 15: PCIe add-in card installation in ME1100

Figure 16: Assembled PCIe card

8. Reinstall the top cover by sliding it from back to front, and then fasten the 4 screws (4 lbf·in torque).

ME1100 Doc. Rev. 1.3

www.kontron.com // 28

3.7.7. Optional 2.5-in SSD

Up to four 2.5-in SSDs can be installed in the server as an option. To install 2.5-in SSDs:

1. Remove the top cover by unscrewing the 4 screws in the back and sliding the cover off toward the rear.

2. Fasten each 2.5-in SSD in the SSD carrier bracket using 2 screws as shown in Figure 17. Up to two 2.5-in SSD

modules can be installed in one carrier bracket.

Figure 17: 2.5-in SSD installation in a carrier bracket

3. Slide in one or two SSD carrier brackets containing the 2.5-in SSDs into the SSD rear mounting bracket as shown

in Figure 18 and fasten each carrier bracket with one screw (2 lbf·in torque) as shown in Figure 19.

ME1100 Doc. Rev. 1.3

www.kontron.com // 29

Figure 18: SSD carrier bracket insertion

Figure 19: SSD carrier bracket attachment

4. Reinstall the top cover by sliding it from back to front, and then fasten the 4 screws (4 lbf·in torque).

ME1100 Doc. Rev. 1.3

www.kontron.com // 30

Typical Power Consumption

The power consumption of the following base configuration is 140W:

Components

Quantity

240W DC PSU*

Fans

45W TDP CPU

4GB UDIMM

SATA 32GB M.2 SSD

10G Base-SR SFP+

50W PCIe add-in card

2.5-in SATA SSD

*With the 240W DC PSU, the unit could draw up to 258W of continuous load on -48V feeds. Various options will increase power consumption compared to the base configuration:

Components

Quantity

Additional system power consumption from 140W base configuration

65W TDP CPU

instead of the 45W TDP CPU

22W

32GB RDIMM Instead of the two 4GB UDIMM

2.5-in SATA SSD (comes with 1 additional chassis fan)

1 to 4

23W (fan) + up to 8W per SSD 50W PCIe add-in card

54W

If all the optional components are used and operate at maximum power, the system could exceed its maximum power consumption.

BMC Access

The Board Management Controller monitors and manages the resources and can be accessed via the RJ45 1GbE connection or via the serial port or remotely via the SFP+ network connection (SFP+ port 2 in Figure 5) (the BMC is using NC-SI, sideband traffic, to communicate with the network). A third way to access it is from the CPU, via the KCS interface, using the ipmitool application provided by Kontron.

The BMC implements the IPMI standard for management:

Component

Description

IPMI KCS

The IPMI KCS is the communication channel linking the management controller to the OS of the server.

ME1100 Doc. Rev. 1.3

www.kontron.com // 31

PCI Mapping

Table 15: PCI mapping

Bus:Device. Function

Vendor ID

Device ID

Component

Description

00:00.0

8086

6F00

Host Bridge

Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 (rev 03)

00:01.0

8086

6F02

PCI Bridge

Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 03)

00:02.0

8086

6F04

PCI Bridge

Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 03)

00:02.2

8086

6F06

PCI Bridge

Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 03)

00:03.0

8086

6F08

PCI Bridge

Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 03)

00:05.0

8086

6F28

System Peripheral

Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management (rev 03)

00:05.1

8086

6F29

System Peripheral

Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug (rev 03)

00:05.2

8086

6F2A

System Peripheral

Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors (rev 03)

00:05.4

8086

6F2C

PIC

Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC (rev 03)

00:16.0

8086

8C3A

Communication Controller

Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)

00:16.1

8086

8C3B

Communication Controller

Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #2 (rev 04)

00:1D.0

8086

8C26

USB Controller

Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)

00:1F.0

8086

8C54

ISA Bridge

Intel Corporation C224 Series Chipset Family Server Standard SKU LPC Controller (rev 05)

00:1F.2

8086

8C02

SATA Controller

Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev

05)

00:1F.3

8086

8C22

SMBus

Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)

02:00.0

8086

6F50

System Peripheral

Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 0

02:00.1

8086

6F51

System Peripheral

Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 1

02:00.2

8086

6F52

System Peripheral

Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 2

02:00.3

8086

6F53

System Peripheral

Intel Corporation Xeon Processor D Family

ME1100 Doc. Rev. 1.3

www.kontron.com // 32

Bus:Device. Function

Vendor ID

Device ID

Component

Description

QuickData Technology Register DMA Channel 3

03:00.0

8086

15AC

Ethernet Controller

Intel Corporation Ethernet Connection X552 10GbE

03:00.1

8086

15AC

Ethernet Controller

Intel Corporation Ethernet Connection X552 10GbE

05:00.0

Slot for PCIe Addin Card

Provision for PCIe x16 expansion port

MAC Addresses

Table 16: MAC addresses

Interface description

MAC address

CPU SFP+ 1

MAC_BASE

CPU SFP+ 2

MAC_BASE + 1

FRU0 Management Controller IOL 1 via MGMT port

MAC_BASE + 2

FRU0 Management Controller IOL 2 via SFP+ 2 port

MAC_BASE + 3

To obtain the value of the MAC_BASE, read the QR code label on the face plate or access the FRU0 of the BMC and use command:

ipmitool fru print

The MAC_BASE will be in the Board Extra section.

ME1100 Doc. Rev. 1.3

www.kontron.com // 33

Interfaces

This section describes the default IP addresses and the various interfaces of the platform. For instructions on how to access an interface using a specific path, refer to Section 4/. For the serial console connection or IPMI (local or remote), refer to Section 5/.

The IOL IP addresses of the BMC (IOL1 and IOL2) may be required when remotely accessing internal components from the management interface. The IP addresses of the BMC must be in different subnets in order to avoid potential conflicts. The default IOL IP addresses are set to be static and are shown in the following figure and table.

Figure 20: Default IP addresses in an ME1100 server

Table 17: Default IP addresses

IOL1 FRU0

192.168.0.2, netmask 255.255.255.0

IOL2 FRU0

0.0.0.0

ME1100 Doc. Rev. 1.3

www.kontron.com // 34

Figure 21: Diagram of interface paths with a serial console connection

*Default redirection is set to CPU 1 at system power up. The serial interface of the server includes a multiplexing functionality that can establish a link with each component

through a series of hotkeys (Figure 21).

To access CLI using the Ctrl-gg command:

1. Simultaneously press and hold the Ctrl keys

2. key and keep pressing the Ctrl key

3. While continuing to hold the Ctrl

4. Release both keys

5. key and release it

6. Press the Enter key and release it

To access , Hint: It is preferable to use the Ctrl key located on the left of the keyboard.

ME1100 Doc. Rev. 1.3

www.kontron.com // 35

Figure 22: Diagram of interface paths with a management networking connection

 Terminal emulator software such as PuTTY can be used.  The Kontron ipmitool package can be downloaded from Symkloud.com. Kontron

recommends using the ipmitool package from its website and not the open source version.

 Ensure the protocol is enabled for the interface to be accessed (SSH, SOL, etc.).  An IOL connection allows users to send ipmitool commands over the LAN for

immediate execution by the addressed BMC (FRU0).

Table 18: Default usernames and passwords

Configuration interface

Username and password

Used for access via

Server BMC CLI

admin admin

Serial port IOL

Server CPU serial console (OS)

Installation-specific

Serial port SOL Other (installation-specific)

ME1100 Doc. Rev. 1.3

www.kontron.com // 36

Description of Interface Access Methods

This section describes various access methods to the OS prompt and the management controllers. For a visual representation of the paths, refer to Section 3.12. For the serial console connection, refer to Section 5/.

To configure, monitor and troubleshoot the ME1100 server, several interfaces can be used: OS prompt through the serial port of the server, through the management port of the server, or through the data

ports of the server

BMC ipmitool shell through the serial port of the server, through the management port of the server (RJ45

connector), through SFP+ 2 via NC-SI (located on the right side of the faceplate), or through the KCS using any of the SFP+ ports

Using a serial console connection is the safest way to proceed when making configurations. It is the method recommended by Kontron and described in the Getting Started section.

To access the interfaces via the management connection, the BMC management IP address is required (see Section 3.12).

Paths to the Operating System Prompt

For any type of connection to the server , an operating system has to be installed. Redirection to the serial port must be configured in the OS (e.g., console=ttyS0, 115200n8). If the system delivered has an OS installed by Kontron, then the console redirection will be enabled by default.

Path to the Operating System prompt and the BIOS setup menu

Path

BIOS

Main reasons for use

Prerequisites

Serial Console (Physical connection)

Fail-safe path to access all server components when elements (OS, BMC BIOS, etc.) get misconfigured

Yes

1. Initial configuration

2. No configuration

performed on OS network interfaces

3. No configuration performed on BMCs

 Serial console port

connected and accessible from an external computer

 Serial console tool (e.g.:

PuTTY) installed on the external computer using the following parameters: Speed: 115200 Data bits: 8 Stop bits: 1 Parity: none Flow control: none

SSH/RDP/Customer application protocols (Remote connection)

Ideal path once the initial server configuration has been performed

Yes

1. Preferred method when OS network interfaces are configured and accessible from an external computer

 OS network interfaces

configured and accessible from an external computer

 Service configured and

enabled in the OS

ME1100 Doc. Rev. 1.3

www.kontron.com // 37

Path to the Operating System prompt and the BIOS setup menu

Path

BIOS

Main reasons for use

Prerequisites

Serial Over Lan (SOL) via IPMITOOL (Remote connection)

Yes

1. Unable to establish an SSH session to the OS

2. OS network interfaces are not configured, but network access to the BMC of the ME1100 server is available

 BMC network configured and

accessible

 Kontron version of IPMITOOL

installed on the external computer

 Console redirection enabled

in OS (e.g., 115200, ttyS0) or BIOS

Paths to the ME1100 embedded IPMITOOL shell

Paths to the embedded IPMITOOL shell

Path

Main reasons for use

Prerequisites

Serial Console (Physical access)

Fail-safe path to access all server components; it is independent of configuration

1. Initial configuration

2. No configuration performed

on BMC

 Serial console port connected and

accessible from an external computer

 Serial console tool (e.g.: PUTTY) installed

on the external computer using the following parameters: Speed: 115200 Data bits: 8 Stop bits: 1 Parity: none Flow control: none

IPMI Over Lan (IOL) (Remote request)

Path recommended for automated monitoring/control script once the initial server configuration has been performed

1. Remote server monitoring

2. Remote server control

 BMC network configured and accessible  Kontron version of IPMITOOL installed on

the external computer

SSH (Remote access)

1. BMC network configured and

accessible from an external computer having access to the subnet of the network connected to the management port or from SFP+ 2 (located on the right side of the faceplate)

 BMC network interface configured and

accessible from an external computer

ME1100 Doc. Rev. 1.3

www.kontron.com // 38

Getting Started

Connect the Power Supply

5.1.1. DC Power Supply

1. Connect the chassis ground to one of the

ground lugs located on the faceplate.

2. Connect appropriately rated cables from an external power source to each power supply input on the front of the unit. Connect one or two (for redundancy) inputs labeled as A and B on the faceplate.

a. The return must be

connected to the two leftmost terminal screws.

b. The -48V DC must be

connected to the two rightmost terminal screws. The power supply is reverse polarity protected.

3. The unit will power on as soon as external power is applied.

See Section 3.7.5 Power Supply Unit for related information.

Establish a Serial Console Connection

Use the RJ45 to DB9 adaptor (ordered separately) with a non-crossover Ethernet cable to establish a

and

the RJ45 serial port.

ME1100 Doc. Rev. 1.3

www.kontron.com // 39

Configure a serial console tool (e.g.: PuTTY) with the correct COM-port for your system using the following parameters:

Default credentials are admin/admin.

Multiple methods can be used to configure the management network of the ME1100. The following configuration steps use the serial console multiplexing feature of the platform. Please refer to Appendix C for all available methods.

Set up the access to the BMC by directing the serial connection to it and log in (default set to OS serial console after power on). The default username and password is admin.

COMMAND

PURPOSE

sk9013075860 login: Ctrl+gg 0 ME1100 login: admin Password: admin ipmitool>

Use HOTKEY to redirect serial console multiplexer to the BMC of the server.

To type Ctrl+gg 0 (see Figure 21):

1. Simultaneously press and hold the Ctrl

2. trl key

3. While continuing to hold the Ctrl

4. Release both keys

6. Press the Enter key and release it

To type Ctrl+gg 1 Hint: It is preferable to use the CTRL key located on the left of the keyboard.

The ASCII control code -

ME1100 Doc. Rev. 1.3

www.kontron.com // 40

Configure and Set the IP Address of BMC/FRU0 (Static or DHCP)

Configure and set the IP address, the netmask and the gateway (optional for a static IP) of IOL1 FRU0 (0x20) and IOL2 FRU0. Choose Option 1 for a static IP or Option 2 for a DHCP IP.

The network configuration allows for setting the two LAN ports either on different networks or on the same network. Run de commands listed below (option 1 or option 2).

Option 1 Static IP

COMMAND

PURPOSE

ipmitool> lan set 1 ipsrc static ipmitool> lan set 1 ipaddr 192.168.101.11 ipmitool> lan set 1 netmask 255.255.255.0 ipmitool> lan set 1 defgw ipaddr 192.168.101.254

ipmitool> lan set 2 ipsrc static ipmitool> lan set 2 ipaddr 192.169.102.12 ipmitool> lan set 2 netmask 255.255.255.0 ipmitool> lan set 2 defgw ipaddr 192.169.102.254

Configure IP source to static for IOL1 FRU0. Define static IP address for IOL1 FRU0. Define netmask for IOL1 FRU0. Define default gateway IP address for IOL1 FRU0. Configure IP source to static for IOL2 FRU0. Define static IP address for IOL2 FRU0. Define netmask for IOL2 FRU0. Define default gateway IP address for IOL2 FRU0.

Option 2 Network using DHCP IP

COMMAND

PURPOSE

ipmitool> lan set 1 ipsrc dhcp ipmitool> lan set 2 ipsrc dhcp

Configure IP source to DHCP for IOL1 FRU0. Configure IP source to DHCP for IOL2 FRU0.

Note that, depending on the existing infrastructure, it may take several seconds to gather an IP from the DHCP server.

Enable Remote Management Using the IPMI Protocol

As a security measure, the remote management of the server via the IPMI protocol is disabled by default. To use the IPMI protocol remotely (i.e. via IOL), the BMC has to be instructed to enable this protocol on each interface

required to support it. If the need arises to disable the IPMI access through one of the interfaces, the BMC can be instructed not to respond

to IPMI commands over that interface (refer to Section 6.5 for the appropriate commands).

COMMAND

PURPOSE

ipmitool> lan set 1 access on

ipmitool> lan set 2 access on

Enable the IPMI protocol in IOL1 (which corresponds to the RJ45 connector). Enable the IPMI protocol in IOL2 (which corresponds to SFP+ port 2 in Figure 5).

ME1100 Doc. Rev. 1.3

www.kontron.com // 41

Verify BMC/FRU0 Network Configuration

Check the following configurations: IP address source (static or DHCP), IP address, subnet mask, default gateway IP and 802.1q VLAN ID. The results shown in the table below are for a static IP.

COMMAND

PURPOSE

ipmitool> lan print 1 Access Mode : Enable IP Address Source : Static IP Address : 192.168.101.11 Subnet Mask : 255.255.255.0 MAC Address : 00:a0:a5:00:00:01 IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10 Default Gateway IP : 192.168.101.254 Default Gateway MAC : 00:00:00:00:00:00

802.1q VLAN ID : 4093

802.1q VLAN Priority : 0 HPM.2 Draft Capabilities: Supported Hostname (OEM) :

ipmitool> lan print 2 Access Mode : Enable IP Address Source : Static IP Address : 192.169.102.12 Subnet Mask : 255.255.255.0 MAC Address : 00:a0:a5:00:00:02 IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10 Default Gateway IP : 192.169.102.254 Default Gateway MAC : 00:00:00:00:00:00

802.1q VLAN ID : 4093

802.1q VLAN Priority : 0 HPM.2 Draft Capabilities: Supported Hostname (OEM) :

Display the current network configuration for IOL1 FRU0.

Display the current network configuration for IOL2 FRU0.

ME1100 Doc. Rev. 1.3

www.kontron.com // 42

Optional Configurations, Monitoring and Operation

The following conventions are used in the sections below:

CONVENTION

PURPOSE

< > in blue

Elements between < > in blue are variables. The value shown is an example or an indication of what to enter.

()

Items between () show a value range for the variable spelled out, e.g. <Switch No. (1-2)> means the switch number is to be entered and that its value can be between 1 and 5.

The |

black bold

Elements in black bold are selectable menu items or button names.

blue italics

Elements in blue italics precede configuration options or types.

The > symbol separates a series of operations required to access a specific element.

Configuration command tables: Sections 6/ and 7/ contain tables that describe steps that can be performed in the CLI-type interface(s) specified in

the header. IPMI management The ME1100 BMC includes an IPMI management process used to manage the CPU and all the other hardware

resources on board:

 Health Status reporting  Temperature data reporting for proper chassis cooling management  Firmware upgrade handling for server components (BMC, FPGA and BIOS)

As for the CPU, its management process has its own logical power state. From an , the BMC acts as a carrier for the CPU; it must therefore llow power control over the CPU.

Note that because the ME1100 activates automatically on system power-up, there should be no reason to target FRU0 with power control commands unless the ME1100 needs to be powered down or control over the power states of the CPU is required.

CPU Power ON, Power OFF and Reset

To power ON the CPU (i.e., go in ACPI S0 state):

IPMITOOL

From the IPMITOOL prompt of the BMC (FRU0) of the targeted server:

ipmitool> power on

IPMITOOL:

RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H <ME1100_FRU0_IP> -U admin -P admin power on

To power OFF the CPU (i.e., go in ACPI S5 state):

IPMITOOL

From the IPMITOOL prompt of the BMC (FRU0) of the targeted server:

ipmitool> power off

RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H <ME1100_FRU0_IP> -U admin -P admin power off

ME1100 Doc. Rev. 1.3

www.kontron.com // 43

To reset the CPU:

IPMITOOL

From the IPMITOOL prompt of the BMC (FRU0) of the targeted server:

ipmitool> power reset

RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H <ME1100_FRU0_IP> -U admin -P admin power reset

Chassis ID Led Control

IPMITOOL

From the IPMITOOL prompt of the BMC (FRU0) of the targeted server:

ipmitool> chassis identify <nb_sec>

RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H <ME1100_FRU0_IP> -U admin -P admin chassis identify <nb_sec>

Notes

Variable the number of seconds the ID LED will blink. Default is 15 seconds.

Boot Order

To choose the boot order:

CPU serial console

1) Perform a CPU reset (see Section 6.1)

From the CPU serial console:

2) Press [Del] or [F2] when prompted to enter the BIOS setup menu Select the Boot tab to display the current boot order

Choose the Boot Option Priority

3) Use the up or down arrow key to select a boot device Press Enter to select the device to position Select the Save & Exit tab Select Save Changes and Reset

Notes

The motherboard can boot from LAN (disabled in BIOS by default), from a USB device connected to the external USB port or from onboard storage.

The default Boot Priority Order is: solid state drive (if installed), LAN interface (if enabled) and UEFI shell.

ME1100 Doc. Rev. 1.3

www.kontron.com // 44

To change the boot order temporarily:

CPU serial console, IPMITOOL

1) Perform a CPU reset (see Section 6.1)

From the CPU serial console:

2.1) Press [Del] or [F2] when prompted to enter the BIOS setup menu Select the Save & Exit tab Bootable devices are listed under Boot Override

Choose the Boot Override:

a) Use the up or down arrow key to select a boot device Press Enter

b) For a one-time boot Press [F7] when prompted to enter the Boot Menu Select the device to boot from

OR From IPMITOOL:

2.2) ipmitool> chassis bootdev <device>

Within 30 seconds, issue the following command to reset the server:

ipmitool> power reset

Notes for IPMITOOL

The possible values for <device> are: none: Do not change boot device order pxe: Force PXE boot (disabled in BIOS by default), PXE boot must first be enabled in BIOS. disk: Force boot from default hard drive bios: Force boot into BIOS Setup

OS Installation

To install an OS:

CPU serial console

a) Boot from LAN (disabled in BIOS by default) OR b) From a USB device connected to the external USB port Proceed with the installation as guided from the OS

ME1100 Doc. Rev. 1.3

www.kontron.com // 45

Disable Remote Management Using the IPMI Protocol

To disable the IPMI access through one of the interfaces, instruct the BMC not respond to IPMI commands over that interface:

IPMITOOL

From the IPMITOOL prompt of the BMC (FRU0) of the targeted server:

ipmitool> lan set 1 access off This disables the IPMI protocol in IOL1 (which corresponds to the RJ45 connector). ipmitool> lan set 2 access off This disables the IPMI protocol in IOL2 (which corresponds to SFP+ port 2 in Figure 5).

Notes

Disabling the access through the IPMI protocol does not disable the LAN interface involved. The SSH access remains available.

Disable a BMC LAN Interface

The BMC can be connected to two different networks using the RJ45 connector and/or SFP+ port 2 (see Figure 5). If a BMC LAN interface must be disabled, its respective LAN interface can be set to use the static address 0.0.0.0. The following example is for IOL2

IPMITOOL

From the IPMITOOL prompt of the BMC (FRU0) of the targeted server:

ipmitool> lan set 2 ipsrc static This sets IOL2 to use a static address.

ipmitool> lan set 2 ipaddr 0.0.0.0 This sets the IP address to 0.0.0.0.

ME1100 Doc. Rev. 1.3

www.kontron.com // 46

Performing Updates

The ME1100 firmware components are updated via IPMITOOl using HPM package provided by Kontron. Both can be downloaded from Symkloud.com.

All BIOS settings, including the boot order, are reset to their default value after a BIOS upgrade.

Update the Firmware

To update the firmware of BMC, BIOS and FPGA:

IPMITOOL

RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H <ME1100_FRU0_IP> -U admin -P admin power off

To confirm the server power status is OFF:

RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H < ME1100_FRU0_IP > -U admin -P admin power status

To proceed with firmware upgrade:

RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H < ME1100_FRU0_IP > -U admin -P admin hpm upgrade

<HPM bundle(hpm file)> all activate

Notes

The upgrade can be done without a power off and the power status verification; however, when an all activate command is executed, a complete system reboot will occur.

ME1100 Doc. Rev. 1.3

www.kontron.com // 47

Appendix A: Sensor List

This list does not cover PCIe Add-in Card sensors which are specific to design implementation.

The following tables contain information on the sensors of the ME1100 server. Table 20 provides detailed information on the sensors described in blue in Table 19.

Table 19: BMC sensor list

Sensor name

Sensor type code

Reading type code

Description

Event offset

Temp Inlet

01h (Temperature Sensor)

01h (Threshold Based)

Inlet Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp BMC

01h (Temperature)

01h (Threshold Based)

BMC Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp Vcore

01h (Temperature)

01h (Threshold Based)

Vcore Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp Cortina

01h (Temperature)

01h (Threshold Based)

Cortina interface Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp CPU

01h (Temperature)

01h (Threshold Based)

CPU Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp DIMM A

01h (Temperature)

01h (Threshold Based)

CPU DIMM A Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp DIMM B

01h (Temperature)

01h (Threshold Based)

CPU DIMM B Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp PCIe

01h (Temperature)

01h (Threshold Based)

PCIe Card Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp M.2

01h (Temperature)

01h (Threshold Based)

M.2 Disk Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp SFP 1

01h (Temperature)

01h (Threshold Based)

SFP1 Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Temp SFP 2

01h (Temperature)

01h (Threshold Based)

SFP2 Temperature (Degrees C)

See IPMI v2.0 table 42-2 for threshold based event

Vcc+0.9V LAN

02h (Voltage)

01h (Threshold Based)

+0.9V 10GbE PHY supply voltage

See IPMI v2.0 table 42-2 for threshold based event

ME1100 Doc. Rev. 1.3

www.kontron.com // 48

Sensor name

Sensor type code

Reading type code

Description

Event offset

Vcc+1.8V LAN

02h (Voltage)

01h (Threshold Based)

+1.8V 10GbE PHY supply voltage

See IPMI v2.0 table 42-2 for threshold based event

V_VPP DDR

02h (Voltage)

01h (Threshold Based)

+2.5V DDR4 memory supply voltage

See IPMI v2.0 table 42-2 for threshold based event

V_VTT DDR

02h (Voltage)

01h (Threshold Based)

+0.6V DDR4 memory terminations supply voltage

See IPMI v2.0 table 42-2 for threshold based event

V_VDDQ DDR

02h (Voltage)

01h (Threshold Based)

+1.2V DDR4 memory main supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Vcc+1.05 SUS

02h (Voltage)

01h (Threshold Based)

On board +1.05V suspend supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Vcc+1.3 SUS

02h (Voltage)

01h (Threshold Based)

On board +1.3V suspend supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Vcc+1.7V SUS

02h (Voltage)

01h (Threshold Based)

On board +1.7V suspend supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Vcc+3.3V SUS

02h (Voltage)

01h (Threshold Based)

On board +3.3V suspend supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Vcc+1.5V SUS

02h (Voltage)

01h (Threshold Based)

On board +1.5V suspend supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Vcc+1.35V SUS

02h (Voltage)

01h (Threshold Based)

On board +1.35V suspend supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Vcc+1.17V SUS

02h (Voltage)

01h (Threshold Based)

On board +1.17V suspend supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Vcc+12V SUS

02h (Voltage)

01h (Threshold Based)

PSU module +12.0V suspend supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Vcc+ 5V SUS

02h (Voltage)

01h (Threshold Based)

On board +5.0V suspend supply voltage

See IPMI v2.0 table 42-2 for threshold based event

Fan Tray Presence

25h (Presence)

6Fh (Sensor

Specific)

Specify the presence of the Fan Tray in the chassis (Present)

See IPMI v2.0 table 42-2, Sensor type code 25h for sensor definition.

monitored.

Fan Presence

04h (Fan)

7Dh (Kontron instancespecifier)

Indicates the presence of a fan

See OEM table, Event/Reading type code 7Dh (OEM Health Severity Status Sensor) for sensor definition

Fan Fault

04h (Fan)

7Dh (Kontron instancespecifier)

Indicates a defective fan

See OEM table, Event/Reading type code 7Dh (OEM Health Severity Status Sensor) for sensor definition

ME1100 Doc. Rev. 1.3

www.kontron.com // 49

Sensor name

Sensor type code

Reading type code

Description

Event offset

Fan1:Speed

04h (Fan)

01h (Threshold Based)

Fan 1 RPM

See IPMI v2.0 table 42-2 for threshold based event

Fan2:Speed

04h (Fan)

01h (Threshold Based)

Fan 2 RPM

See IPMI v2.0 table 42-2 for threshold based event

Fan3:Speed

04h (Fan)

01h (Threshold Based)

Fan 3 RPM

See IPMI v2.0 table 42-2 for threshold based event

Fan4:Speed

04h (Fan)

01h (Threshold Based)

Fan 4 RPM

See IPMI v2.0 table 42-2 for threshold based event

Power State

D1h (OEM Power State)

6Fh (Sensor Specific)

Board Power State

See OEM sensor table, Sensor type code D1h for sensor definition

ACPI State

22h (System ACPI Power State)

6Fh (Sensor Specific)

Advanced Configuration and Power Interface State

Only offset 0,5 are used See IPMI v2.0 table 42-3, Sensor type code 22h (ACPI Power State) for

sensor definition

Power Good

08h (Power Supply)

77h (OEM Kontron Power Good)

Board Input Power

See Table 20 below

Power Latch

08h (Power Supply)

03h (Digital Discrete)

Power good latch status

See IPMI v2.0 table 42-3, Sensor type code 08h for sensor definition

IPMI Watchdog

23h (Watchdog)

6Fh (Sensor Specific)

IPMI Watchdog (Payload Watchdog)

Only offset 0,1,2,3,8 are used See IPMI v2.0 table 42-3, Sensor type code 23h (Watchdog 2) for sensor definition

Board Reset

CFh (OEM Kontron Reset)

03h ( Standard IPMI

Board Reset status

See OEM sensor table, Sensor type code CFh for sensor definition

CPU Status

07h (Processor)

6Fh (Sensor Specific)

Processor Status

Only offset 0,1,5 are used See IPMI v2.0 table 42-3, Sensor type code 07h for sensor definition

POST Value

C6h (OEM Post Value)

6Fh (Sensor Specific)

Show current POST code value

See OEM sensor table, Sensor type code C6h for sensor definition

POST Error

0Fh (Firmware

Programming)

6Fh (Sensor

Specific)

Show current POST error value

See OEM sensor table, Sensor type code 0Fh for sensor definition

Jumper Status

D3h (OEM Jumper Status)

6Fh (Sensor

Specific)

Reflects on-board jumper presence

Offsets 0 to 14 are used. See OEM table, Sensor type code D3h (Kontron OEM Jumper Status) for sensor definition

Ver Change BMC

2Bh (Version Change)

6Fh (Sensor Specific)

IPMC Firmware Change Detection

See IPMI v2.0 table 42-3, Sensor type code 2Bh for sensor definition

Ver Change FPGA

2Bh (Version Change)

6Fh (Sensor Specific)

FPGA Firmware Change Detection

See IPMI v2.0 table 42-3, Sensor type code 2Bh for sensor definition

ME1100 Doc. Rev. 1.3

www.kontron.com // 50

Sensor name

Sensor type code

Reading type code

Description

Event offset

Ver Change BIOS

2Bh (Version Change)

6Fh (Sensor Specific)

BIOS Firmware Change Detection

See IPMI v2.0 table 42-3, Sensor type code 2Bh for sensor definition

BMC Reboot

24h (Platform Alert)

03h (Digital Discrete)

BMC reboot detection

Only offset 0,1 are used See IPMI v2.0 table 42-3, Sensor type code 24h for sensor definition

BMC SEL State

10h (Event Logging Disable)

6Fh (Sensor Specific)

Specify the status of the SEL (Cleared/Almost full/Full)

Only offset 2,4,5 are used See IPMI v2.0 table 42-3, Sensor type code 10h (Event Log Disable) for sensor definition

SEL Time Set

12h (System)

6Fh (Sensor Specific)

Specify when SEL time change

Only offset 5 is used See IPMI v2.0 table 42-3, Sensor type code 12h for sensor definition

Health Status

24h (Platform Alert)

7Fh (OEM Health Severity Status Sensor)

General health status (Aggregation of critical sensors)

See OEM table, Sensor type code 24h (Platform Alert) for sensor definition and Event/Reading type code 7Fh (OEM Health Severity Status Sensor)

IPMI Info-1

C0h (OEM Firmware Info)

70h (OEM Kontron Internal Diagnostic)

Internal Management Controller firmware diagnostic

See OEM table, Sensor type code C0h (Kontron OEM Firmware Info) for sensor definition and Event/Reading type code 70h (Kontron OEM Internal Diagnostic)

IPMI Info-2

C0h (OEM Firmware Info)

71h (OEM Kontron Internal Diagnostic)

Internal Management Controller firmware diagnostic

See OEM table, Sensor type code C0h (Kontron OEM Firmware Info) for sensor definition and Event/Reading type code 71h (Kontron OEM Internal Diagnostic)

ME1100 Doc. Rev. 1.3

www.kontron.com // 51

Table 20: Detailed information for Kontron OEM Firmware Info

Sensor name

Event/reading type code

Sensor type

Sensor specific offset

Event trigger

Fan Presence Fan Fault

7Dh OEM Kontron

Instance-specifier

04h (Fan)

00h Fan1 01h Fan2 02h Fan3 03h Fan4

0 = State Deasserted 1 = State Asserted State for the fan status described by sensor

name, for the fan instance specified by the offset

Power State

6Fh Standard IPMI sensor specific

D1h Kontron OEM Power state sensor

00h 01h 02h 03h 04h

Power ON Power OFF Power ON Request Power OFF Request Full Reset In Progress

Power Good

77h OEM Kontron Power Good

08h Standard IPMI Power Supply

00h 01h 02h 03h 04h 05h 06h 07h 08h 09h 0Ah 0Bh 0Ch 0Dh 0Eh 0Fh

1.5V SUS

1.35V SUS

0.9V LAN

1.8V LAN

1.7V SUS

1.3V SUS

1.05V SUS V_VPP V_VDDQ V_VTTDDR

1.05V

1.5V

3.3V

5.0 V

12.0 V VCCIN

ME1100 Doc. Rev. 1.3

www.kontron.com // 52

Sensor name

Event/reading type code

Sensor type

Sensor specific offset

Event trigger

Board Reset

03h Standard IPMI Discrete

CFh OEM Kontron Reset

00h 01h State Asserted / State Deasserted

Event Data 2: Reset Type 00h: Warm reset 01h: Cold reset 02h: Forced Cold [ Warm reset reverted to Cold ] 03h: Soft reset [ Software jump ] 04h: Hard Reset 05h: Forced Hard [ Warm reset reverted to Hard ]

Event Data 3: Reset Source 00h: IPMI Watchdog [ cold, warm or forced cold ] ( IPMI Watchdog2 sensors gives additionnal details ) 01h: IPMI commands [ cold, warm or forced cold ] ( chassis control, fru control ) 02h: Processor internal checkstop 03h: Processor internal reset request 04h: Reset button [ warm or forced cold ] 05h: Power up [ cold ] 06h: Legacy Initial Watchdog / Warm Reset Loop Detection * [ cold reset ] 07h: Legacy Programmable Watchdog [ cold, warm or forced cold ] 08h: Software Initiated [ soft, cold, warm of forced cold ] 09h: Setup Reset [ Software Initiated Cold ] 0Ah: Power Cycle / Full Reset / Global Platform Reset FFh: Unknown

POST Value

6Fh Standard IPMI sensor specific

C6h OEM Kontron POST Code Value

00h to 07h

14h

POST code LOW byte value, no event generated on these offsets

POST Code Error Event Trigger Event Data 2: POST Low Nibble Event Data 3: POST High Nibble

POST Error

6Fh Standard IPMI sensor specific

C6h OEM Kontron POST Code Value

00h

Event Data 1: 0xC0 when sensor value is 1 Event Data 2: No memory: 0x01

BIOS Corrupt: 0x0B Event Data 3: unused (0xFF)

Jumper Status

6Fh Standard IPMI sensor specific

D3h Kontron OEM Jumper Status Sensor

00h 01h 02h 03h 04h 05h

Jumper 00 Present (JP1: 1-2) Jumper 01 Present (JP1: 3-4) Jumper 02 Present (JP1: 5-6) Jumper 03 Present (JP1: 7-8) Jumper 04 Present (JP1: 9-10) Jumper 05 Present (JP1: 11-12)

ME1100 Doc. Rev. 1.3

www.kontron.com // 53

Sensor name

Event/reading type code

Sensor type

Sensor specific offset

Event trigger

Health Status

7Fh OEM Health Severity Status Sensor

24h (Platform Alert)

00h Status not available in current state 01h Healthy 02h Informational fault 03h Minor fault 04h Major fault 05h Critical fault

Event Data2: The ID of the first sensor from the aggregation that caused the fault.

Event Data3: Not used

Sensor Aggregation List (FRU0): ID - Sensor Name

0 - Temp Inlet 1 - Temp BMC 2 - Temp Vcore 3 - Temp Regulators

4 Temp Cortina 5 - Temp CPU 6 - Temp DIMM A 7 - Temp DIMM B 8 - Temp PCIe 9 - Temp M.2 10 - Temp SFP 1 11 - Temp SFP 2 12 Vcc+0.9V LAN

13 Vcc+1.8V LAN 14 V_VPP DDR 15 V_VTT DDR 16 V_VDDQ DDR 17 Vcc+1.05 SUS 18 Vcc+1.3 SUS 19 Vcc+1.7V SUS 20 Vcc+3.3V SUS 21 Vcc+1.5V SUS 22 Vcc+1.35V SUS 23 Vcc+1.17V SUS 24 - Vcc +12V SUS

25 - Vcc +5V SUS 27 Fan Presence 28 Fan Fault 36 Power Latch 37 IPMI Watchdog 39 CPU Status

IPMI Info-1

70h OEM Kontron Firmware Info 1

C0h OEM Kontron Firmware Info

00h 01h 02h to 0Eh 0Fh

Event Code Assert Trigger Event Overflow Trigger Code Assert Line (Binary Encoded) Unused, Reserved

IPMI Info-2

70h OEM Kontron

Firmware Info 2

C0h OEM Kontron Firmware Info

00h 01h 02h to 0Eh

0Fh

Event Code Assert Trigger Unused Trigger Code Assert File Id (Binary Encoded) Unused, Reserved

ME1100 Doc. Rev. 1.3

www.kontron.com // 54

Appendix B: IPMI Command List

Table 21 lists the commands that are supported and unsupported by the FRU0.

Table 21: Supported and unsupported commands for FRU0

Command

ME1100 (FRU0)

IPM Device "Global" Commands (NetFN/LUN 06h/0h)

Get Device ID (01h)

Supported

Cold Reset (02h)

Supported

Warm Reset (03h)

Unsupported

Get Self-Test Results (04h)

Supported

Manufacturing Test On (05h)

Supported

Set ACPI Power State (06h)

Supported

Get ACPI Power State (07h)

Supported

Get Device GUID (08h)

Supported

Broadcast "Get Device ID" (00h)

Supported

BMC Watchdog Timer Commands (NetFN/LUN 06h/0h)

Reset Watchdog Timer (22h)

Supported

Set Watchdog Timer (24h)

Supported

Get Watchdog Timer (25h)

Supported

BMC Device and Messaging Commands (NetFN/LUN 06h/0h)

Set BMC Global Enables (2Eh)

Supported

Get BMC Global Enables (2Fh)

Supported

Clear Message Flags (30h)

Supported

Get Message Flags (31h)

Supported

Enable Message Channel Receive (32h)

Supported

Get Message (33h)

Supported

Send Message (34h)

Supported

Read Event Message Buffer (35h)

Supported

Get BT Interface Capabilities (36h)

Unsupported

Get System GUID (37h)

Supported

Get Channel Authentication Capabilities (38h)

Supported

Get Session Challenge (39h)

Supported

Activate Session (3Ah)

Supported

Set Session Privilege Level (3Bh)

Supported

Close Session (3Ch)

Supported

Get Session Info (3Dh)

Supported

Get AuthCode (3Fh)

Unsupported

Set Channel Access (40h)

Supported

Get Channel Access (41h)

Supported

Get Channel Info (42h)

Supported

ME1100 Doc. Rev. 1.3

www.kontron.com // 55

Command

ME1100 (FRU0)

Set User Access (43h)

Supported

Get User Access (44h)

Supported

Set User Name (45h)

Supported

Get User Name (46h)

Supported

Set User Password (47h)

Supported

Master Write-Read (52h)

Supported

Get Channel Cipher Suites (54h)

Supported

Set Channel Security Keys (56h)

Unsupported

Get System Interface Capabilities (57h)

Supported

RMCP+ Support and Payload Commands (NetFN/LUN 06h/0h)

Activate Payload (48h)

Supported

Deactivate Payload (49h)

Supported

Get Payload Activation Status (4Ah)

Supported

Get Payload Instance Info (4Bh)

Supported

Set User Payload Access (4Ch)

Supported

Get User Payload Access (4Dh)

Supported

Get Channel Payload Support (4Eh)

Supported

Get Channel Payload Version (4Fh)

Supported

Get Channel OEM Payload Info (50h)

Unsupported

Suspend/Resume Payload Encryption (55h)

Supported

Chassis Device Commands (NetFN/LUN 00h/0h)

Get Chassis Capabilities (00h)

Supported

Get Chassis Status (01h)

Supported

Chassis Control (02h)

Supported

Chassis Reset (03h)

Unsupported

Chassis Identify (04h)

Supported

Set Chassis Capabilities (05h)

Unsupported

Set Power Restore Policy (06h)

Unsupported

Get System Restart Cause (07h)

Unsupported

Set System Boot Options (08h)

Supported

Get System Boot Options (09h)

Supported

Get POH Counter (0Fh)

Unsupported

Event Commands (NetFN/LUN 04h/0h)

Set Event Receiver (00h)

Supported

Get Event Receiver (01h)

Supported

Platform Event (02h)

Supported

PEF and Alerting Commands (NetFN/LUN 04h/0h)

Get PEF Capabilities (10h)

Supported

Arm PEF Postpone Timer (11h)

Supported

Set PEF Configuration Parameters (12h)

Supported

Get PEF Configuration Parameters (13h)

Supported

ME1100 Doc. Rev. 1.3

www.kontron.com // 56

Command

ME1100 (FRU0)

Set Last Processed Event ID (14h)

Supported

Get Last Processed Event ID (15h)

Supported

Alert Immediate (16h)

Unsupported

PET Acknowledge (17h)

Unsupported

Sensor Device Commands (NetFN/LUN 04h/0h)

Get Device SDR Info (20h)

Supported

Get Device SDR (21h)

Supported

Reserve Device SDR Repository (22h)

Supported

Get Sensor Reading Factors (23h)

Unsupported

Set Sensor Hysteresis (24h)

Supported

Get Sensor Hysteresis (25h)

Supported

Set Sensor Threshold (26h)

Supported

Get Sensor Threshold (27h)

Supported

Set Sensor Event Enable (28h)

Supported

Get Sensor Event Enable (29h)

Supported

Re-arm Sensor Events (2Ah)

Unsupported

Get Sensor Event Status (2Bh)

Unsupported

Get Sensor Reading (2Dh)

Supported

Set Sensor Type (2Eh)

Unsupported

Get Sensor Type (2Fh)

Unsupported

Set Sensor Reading and Event Status (30h)

Supported

FRU Device Commands (NetFN/LUN 0Ah/0h)

Get FRU Inventory Area Info (10h)

Supported

Read FRU Data (11h)

Supported

Write FRU Data (12h)

Supported

SDR Device Commands (NetFN/LUN 0Ah/0h) ** UNSUPPORTED FEATURE

Get SDR Repository Info (20h)

Unsupported

Get SDR Repository Allocation Info (21h)

Unsupported

Reserve SDR Repository (22h)

Unsupported

Get SDR (23h)

Unsupported

Add SDR (24h)

Unsupported

Partial Add SDR (25h)

Unsupported

Delete SDR (26h)

Unsupported

Clear SDR Repository (27h)

Unsupported

Get SDR Repository Time (28h)

Unsupported

Set SDR Repository Time (29h)

Unsupported

Enter SDR Rep Update Mode (2Ah)

Unsupported

Exit SDR Repository Update Mode (2Bh)

Unsupported

Run Initialization Agent (2Ch)

Unsupported

SEL Device Commands (NetFN/LUN 0Ah/0h)

ME1100 Doc. Rev. 1.3

www.kontron.com // 57

Command

ME1100 (FRU0)

Get SEL Info (40h)

Supported

Get SEL Allocation Info (41h)

Supported

Reserve SEL (42h)

Supported

Get SEL Entry (43h)

Supported

Add SEL Entry (44h)

Supported

Partial Add SEL Entry (45h)

Unsupported

Delete SEL Entry (46h)

Unsupported

Clear SEL (47h)

Supported

Get SEL Time (48h)

Supported

Set SEL Time (49h)

Supported

Get Auxiliary Log Status (5Ah)

Unsupported

Set Auxiliary Log Status (5Bh)

Unsupported

LAN Device Commands (NetFN/LUN 0Ch/0h)

Set LAN Configuration Parameters (01h)

Supported

Get LAN Configuration Parameters (02h)

Supported

Suspend BMC ARPs (03h)

Supported

Get IP/UDP/RMCP Statistics (04h)

Supported

Serial/Model Device Commands (NetFN/LUN 0Ch/0h) ** UNSUPPORTED FEATURE

Set Serial/Modem Configuration (10h)

Unsupported

Get Serial/Modem Configuration (11h)

Unsupported

Set Serial/Modem Mux (12h)

Unsupported

Get TAP Response Codes (13h)

Unsupported

Set PPP UDP Proxy Transmit Data (14h)

Unsupported

Get PPP UDP Proxy Transmit Data (15h)

Unsupported

Send PPP UDP Proxy Packet (16h)

Unsupported

Get PPP UDP Proxy Receive Data (17h)

Unsupported

Serial/Modem Connection Active (18h)

Unsupported

Callback (19h)

Unsupported

Set User Callback Options (1Ah)

Unsupported

Get User Callback Options (1Bh)

Unsupported

Serial-Over-LAN (SOL) Commands (NetFN/LUN 0Ch/0h)

SOL Activating (20h)

Supported

Set SOL Configuration Params (21h)

Supported

Get SOL Configuration Params (22h)

Supported

HPM.1 Commands (NetFN/LUN 2Ch/0h)

Get Target Upgrade Capabilities (2Eh)

Supported

Get Component Properties (2Fh)

Supported

Abort Firmware Upgrade (30h)

Supported

Initiate Upgrade Action (31h)

Supported

Upload Firmware Block (32h)

Supported

Finish Firmware Upload (33h)

Supported

ME1100 Doc. Rev. 1.3

www.kontron.com // 58

Command

ME1100 (FRU0)

Get Upgrade Status (34h)

Supported

Activate Firmware (35h)

Supported

Query Self-Test Results (36h)

Supported

Query Rollback Status (37h)

Supported

Initiate Manual Rollback (38h)

Supported

ME1100 Doc. Rev. 1.3

www.kontron.com // 59

Appendix C: Additional Options to Configure IOL Interfaces

Three methods are available to configure IOL interfaces. One is described in the Getting Started section and the two others are described in this appendix.

IOL configuration methods:

1. Using CPU/Operating System (KCS) (IOL 1 and IOL 2)

2. Using FRU0 IOL channels (IOL 1 or IOL 2)

1. Using CPU/Operating System (KCS) (IOL 1 and IOL 2)

a) Install OS with open IPMI KCS support. b) Install Kontron's version of ipmitool. c) Configure IOL using LAN commands.

Configure and set the IP address, the netmask and the gateway (optional for a static IP). Choose Option 1 for a static IP or Option 2 for a DHCP IP.

Option 1 Static IP Configure and set the IP address, the netmask and the gateway of IOL2 FRU0 and IOL1 FRU0 from the OS of the CPU:

COMMAND

PURPOSE

CPU_OSPrompt:~# ipmitool lan set 2 ipsrc static

CPU_OSPrompt:~# ipmitool lan set 2 ipaddr 192.169.102.12 CPU_OSPrompt:~# ipmitool lan set 2 netmask 255.255.255.0 CPU_OSPrompt:~# ipmitool lan set 2 defgw

ipaddr 192.169.102.254

CPU_OSPrompt:~# ipmitool lan set 1 ipsrc static

CPU_OSPrompt:~# ipmitool lan set 1 ipaddr 192.168.101.11 CPU_OSPrompt:~# ipmitool lan set 1 netmask 255.255.255.0 CPU_OSPrompt:~# ipmitool lan set 1 defgw ipaddr 192.168.101.254

Configure IP source to STATIC for IOL2 FRU0. Define static IP address for IOL2 FRU0. Define netmask for IOL2 FRU0. Define default gateway IP address for IOL2 FRU0. Configure IP source to STATIC for IOL1 FRU0. Define static IP address for IOL1 FRU0. Define netmask for IOL1 FRU0. Define default gateway IP address for IOL1 FRU0.

Option 2 DHCP IP Configure and set the IP address of IOL2 FRU0 and IOL1 FRU0 from the OS of the CPU:

COMMAND

PURPOSE

CPU_OSPrompt:~# ipmitool lan set 2 ipsrc dhcp

CPU_OSPrompt:~# ipmitool lan set 1 ipsrc dhcp

Configure IP source to DHCP for IOL2 FRU0. Configure IP source to DHCP for IOL1 FRU0.

ME1100 Doc. Rev. 1.3

www.kontron.com // 60

2. Using FRU0 IOL channels (IOL 1 or IOL 2)

The example below shows the configuration of IOL2 FRU0 from the Management port. To configure IOL1 FRU0, connect the cable in the SFP+ 2 port and replace lan set 2 by lan set

a) Install Kontron's version of ipmitool on a remote computer. b) Connect a cable in the MNGT port (must be configured and accessible from a remote computer) (see Figure 23). c) Configure IOL using ipmitool commands.

The safest method to configure IOL2 is to connect to the MNGT port and the safest method to configure IOL1 is to connect to the SFP+ 2 port.

If IOL1 is configured from the MNGT RJ45 port (IOL1) or if IOL2 is configured from the SFP+ 2 port (IOL2) (see Figure 23), there is a possibility of getting locked out of the system when changing the IP address or the netmask.

Figure 23: Default IP addresses in a ME1100 server

Table 22: Default IP addresses

IOL1 FRU0

192.168.0.2, netmask 255.255.255.0

IOL2 FRU0

0.0.0.0

Option 1 Static IP Configure and set the IP address of IOL2 FRU0:

COMMAND

PURPOSE

RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H [BMC_IP] -U admin -P admin lan set 2 ipsrc static RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H [BMC_IP] -U admin -P admin lan set 2 ipaddr 192.169.102.12 RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H [BMC_IP] -U admin -P admin lan set 2 netmask 255.255.255.0 RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H [BMC_IP] -U admin -P admin lan set 2 defgw ipaddr 192.169.102.254

Configure IP source to STATIC for IOL2 FRU0. Define static IP address for IOL2 FRU0. Define netmask for IOL2 FRU0.

Define default gateway IP address for IOL2 FRU0.

Option 2 DHCP IP Configure and set the IP address of IOL2 FRU0 :

COMMAND

PURPOSE

RemoteComputer_OSPrompt:~# ipmitool -I lanplus -H [BMC_IP] -U admin -P admin lan set 2 ipsrc DHCP

Configure IP source to DHCP for IOL2 FRU0.

ME1100 Doc. Rev. 1.3

www.kontron.com // 61

Appendix D: User Application Providing Feedback to BMC

The ME1100 allows customers to integrate their capabilities. This interaction takes place at a lower level than with IPMI commands.

Three main tasks can be achieved:

 Control the Power LED to indicate system has completed booting (no blink status)  Tell the BMC the temperatures of the PCIe add-in card, M.2 module, SFP+ port 1 module and/or SFP+ port 2

module (when this information is available, depending on the hardware used)

 Set the BMC time

This action can be performed through IPMI or the FPGA. To support this feature the FPGA exposes five 8-bit registers via the LPC interface.

FPGA registers available to the customer

Name

I/O space address

Details

Application running flag (set the value to 0x01 to stop the blinking)

0x0a20

This is a flag that indicates the application is booted and running. Only bit 0 is used, and only to reset the blink mode. Write 1 to stop the Power LED (green) blink.

Temperature reporting PCIe slot (in deg. C as a signed char, no decimal values)

0x0a28

complement format to represent -128°C to +127°C. The value of -128°C (0x80) is reserved and indicates nothing has been written in the register.

The registers reset automatically after 4 seconds. The user application has to update the registers at a rate faster than each 4 seconds.

Temperature reporting M.2 slot (in deg. C as a signed char, no decimal values)

0x0a29

Temperature reporting SFP1 (in deg. C as a signed char, no decimal values)

0x0a2a

Temperature reporting SFP2 (in deg. C as a signed char, no decimal values)

0x0a2b

The mechanism used is common for all elements and there are three methods to configure blinking and report temperatures:

a) Bash commands (section 1) b) Compiled code (section 2) c) Special set of OEM commands using the IPMI protocol (section 3)

1. Bash demo using FPGA registers To facilitate the tests and enable a quick start, the following bash script has to be executed on the CPU (example

provided on a CentOS operating system). The script contains an infinite loop which provides continuous updates of the FPGA registers with the user monitored

temperatures. Users have to add this demo script to their own method for reading the actual temperatures.

ME1100 Doc. Rev. 1.3

www.kontron.com // 62

Bash

#!/bin/sh # Kontron Canada Inc. # ME1100_UserAppMon.sh # Demo script of the application LED control and # temperatures monitoring # by directly setting the FPGA registers

#Stop the green LED blinking: #(write the value 0x01 to the port 2592) printf "\x01" | dd seek=2592 bs=1 count=1 of=/dev/port 2> /dev/null

while true do

# Here the customer has to add the means to read the actual temperatures from the PCIe, M.2 and SFPs) # …

# After having read the temperatures, set the four monitored temperatures #The printf parameter values are some test values #The ports are 2600...2603

# Set the PCIe temperature to 17 deg.C : printf "\x11" | dd seek=2600 bs=1 count=1 of=/dev/port 2> /dev/null

# Set the M.2 Temperature to 34 deg.C : printf "\x22" | dd seek=2601 bs=1 count=1 of=/dev/port 2> /dev/null

# Set the SFP1 Temperature to 51 deg.C : printf "\x33" | dd seek=2602 bs=1 count=1 of=/dev/port 2> /dev/null

# Set the SFP2 Temperature to 51 deg.C : printf "\x33" | dd seek=2603 bs=1 count=1 of=/dev/port 2> /dev/null

# Update the temperatures every 3 seconds sleep 3

done

Stop LED blinking and report temperatures

1. Boot the OS.

2. After the OS completes the boot, check the green Power LED. It should be blinking.

3. Copy the bash script file on the target CPU.

4. Set the execution rights of the shell script file.

5. Run the script, either as a separate process or inside the console already open.

Example:

COMMAND

[root@CentOS73 ~]# ls -lah /tmp/ME1100_UserAppMon.sh

-rwxr-xr-x 1 root root 391 Dec 31 21:10 /tmp/ME1100_UserAppMon.sh

[root@CentOS73 ~]# /tmp/ME1100_UserAppMon.sh &

[1] 4786 [root@CentOS73 ~]#

6. Check the green Power LED on the faceplate. It should have stopped blinking.

7. Set the thresholds (refer to section 4 of this Appendix).

ME1100 Doc. Rev. 1.3

www.kontron.com // 63

2. C application demo using FPGA registers For a demo closer to the look and feel of a customer's application, the following C source file has to be transferred

and compiled on the CPU (example provided on a CentOS operating system).

C application

#include <sys/io.h> #include <stdio.h> #include <unistd.h>

/* * Kontron Canada Inc. * * Demo application of the application LED control and * temperatures monitoring by directly setting the FPGA registers */

#define REFRESH_RATE 3 /* seconds */

int main(void) { /* Stop the green LED blinking: *(write the value 0x01 to the port 2592) */ iopl(3); outb(0x01, 0xa20); iopl(0);

printf("Blink is off\n");

/* Set the four monitored temperatures every 3 seconds: * The parameter values are some test values * The ports are 2600...2603 */ while (1) { // Here the customer has to add the means to read the actual temperatures from the PCIe, M.2 and SFPs // …

/* Set the PCIe temperature to 17 deg.C : */ iopl(3); outb(0x11, 0xa28); iopl(0);

/* Set the M.2 Temperature to 34 deg.C: */ iopl(3); outb(0x22, 0xa29); iopl(0);

/* Set the SFP1 Temperature to 51 deg.C: */ iopl(3); outb(0x33, 0xa2a); iopl(0);

/* Set the SFP2 Temperature to 51 deg.C: */ iopl(3); outb(0x33, 0xa2b); iopl(0);

printf("*"); sleep(REFRESH_RATE); }

return 0; }

ME1100 Doc. Rev. 1.3

www.kontron.com // 64

Stop LED blinking and report temperatures

1. Boot the OS.

2. After the OS completes the boot, check the green Power LED. It should be blinking.

3. Copy the C source code script file on the target CPU.

4. Compile the script file.

5. Run the binary file, either as a separate process or inside the console already open.

Example:

COMMAND

[root@CentOS73 ~]# gcc -o /tmp/ME1100_UserAppMon /tmp/ME1100_UserAppMon.c [root@CentOS73 ~]#/tmp/ME1100_UserAppMon &

[root@CentOS73 ~]#

6. Check the green Power LED on the faceplate. It should have stopped blinking.

7. Set the thresholds (refer to section 4 of this Appendix).

3. IPMI demo

If an IPMI method of setting the temperatures and stopping the green Power LED blink is required, the BMC implements five board-specific control-state commands to help with the setup using the IPMI protocol.

NOTE: Using these IPMI OEM commands will implicitly tell the BMC to ignore the FPGA reported values for these temperature sensors, until the next BMC reboot. This means the user has to choose, from the beginning of a session, by which method the update of the four temperatures will be done: writing into the FPGA registers (methods 1 and 2) or using IPMI OEM commands (method 3 described in this section). All four temperatures must be reported the same way.

Upon reset, the BMC's default behavior is restored, i.e. read the temperatures from the FPGA. However, as soon as one temperature was set using an IPMI command, the BMC expects that if the user wants to provide the other three then they will also be provided by means of IPMI commands.

There are two options using IPMI commands: Option 1 Entering manual IPMI commands in the OS prompt Option 2 Executing a script

Option 1 Entering manual IPMI commands in the OS prompt

1. Stop LED blinking:

COMMAND

PURPOSE

root@ME1100-BMC:~# ipmitool -v raw 0x3e 0x20 0xc4 0

Running PICMG GetDeviceLocator ipmi_vks_open called !

No PICMG Extenstion discovered, keeping IPMB address 0x20 No PICMG Extenstion discovered, keeping IPMB address 0x20 RAW REQ (channel=0x0 netfn=0x3e lun=0x0 cmd=0x20 data_len=2) RAW REQUEST (2 bytes) 1a 00 RAW RSP (0 bytes)

Command to stop LED blinking where 0xc4 is the control-state and 0 the only possible parameter value.

ME1100 Doc. Rev. 1.3

www.kontron.com // 65

2. Check the green Power LED on the faceplate. It should have stopped blinking.

3. Set user-reported temperatures:

COMMAND

PURPOSE

root@ME1100-BMC:~# ipmitool sensor | grep Temp | tail -n 4 Temp PCIe | na| degrees C| na | 0.000 | -1.000| 0.000 |

59.000| 69.000| 99.000 Temp M.2 | na| degrees C| na | 0.000 | -1.000| 0.000 |

59.000| 69.000| 99.000 Temp SFP 1| na| degrees C| na | 0.000 | -1.000| 0.000 |

74.000| 84.000| 99.000 Temp SFP 2| na| degrees C| na | 0.000 | -1.000| 0.000 |

74.000| 84.000| 99.000 root@ME1100-BMC:~# ipmitool raw 0x3e 0x20 0xc0 0x11

root@ME1100-BMC:~# ipmitool raw 0x3e 0x20 0xc1 0x22

root@ME1100-BMC:~# ipmitool raw 0x3e 0x20 0xc2 0x33

root@ME1100-BMC:~# ipmitool raw 0x3e 0x20 0xc3 0x33

root@ME1100-BMC:~# ipmitool sensor | grep Temp | tail -n 4 Temp PCIe | 17.000| degrees C| ok| 0.000| -1.000| 0.000|

59.000| 69.000| 99.000 Temp M.2 | 34.000| degrees C| ok| 0.000| -1.000| 0.000|

59.000| 69.000| 99.000 Temp SFP 1| 51.000| degrees C| ok| 0.000| -1.000| 0.000|

74.000| 84.000| 99.000 Temp SFP 2| 51.000| degrees C| ok| 0.000| -1.000| 0.000|

74.000| 84.000| 99.000

Display current temperature thresholds.

Set the PCIe Card Temperature, where 0xC0 is the control-state for the PCIe Temperature and 0x11 the (test) value of the temperature (17°C).

Set the M.2 Temperature, where 0xC1 is the control-state for the M.2 Temperature and 0x22 the (test) value of the temperature (34°C).

Set the SFP1 Temperature, where 0xC2 is the control-state for the SFP1 Temperature and 0x33 the (test) value of the temperature (51°C).

Set the SFP2 Temperature, where 0xC3 is the control-state for the SFP2 Temperature and 0x33 the (test) value of the temperature (51°C).

Display current temperature thresholds.

4. Set the thresholds (refer to section 4 of this Appendix).

Option 2 Executing a script In the real application these temperature updates have to be refreshed faster than every 4 seconds. The following

script exemplifies the usage. The actual user implementation may be based on any programming language that provides the appropriate IPMI bindings:

IPMI

#!/bin/sh # Kontron Canada Inc. # ME1100_UserAppMon_wIPMI.sh # Demo script of the application LED control and # temperatures monitoring using OEM IPMI commands

#Stop the green LED blinking:

ME1100 Doc. Rev. 1.3

www.kontron.com // 66

#(write the value 0x00 to the control-state #0xc4) ipmitool raw 0x3e 0x20 0xc4 0 2> /dev/null

while true do

# Here the customer has to add the means to read the actual temperatures from the PCIe, M.2 and SFPs) # …

#Set the four monitored temperatures every 3 seconds: #The printf parameter values used are some test values

# Set the PCIe temperature to 17 deg.C : ipmitool raw 0x3e 0x20 0xC0 0x11 2> /dev/null

# Set the M.2 Temperature to 34 deg.C : ipmitool raw 0x3e 0x20 0xC1 0x22 2> /dev/null

# Set the SFP1 Temperature to 51 deg.C : ipmitool raw 0x3e 0x20 0xC2 0x33 2> /dev/null

# Set the SFP2 Temperature to 51 deg.C : ipmitool raw 0x3e 0x20 0xC3 0x33 2> /dev/null

sleep 3

done

4. Temperature monitoring Once the steps above are completed, while the demo script or the compiled C binary file is still running, check with the

temperatures reported using ipmitool.

COMMAND

PURPOSE

[root@CentOS73 ~]# ipmitool sensor | grep Temp | tail -n 4 Temp PCIe | 17.000| degrees C| ok| 0.000| -1.000| 0.000| 59.000|

69.000| 99.000 Temp M.2 | 34.000| degrees C| ok| 0.000| -1.000| 0.000| 59.000|

69.000| 99.000 Temp SFP 1| 51.000| degrees C| ok| 0.000| -1.000| 0.000| 74.000|

84.000| 99.000 Temp SFP 2| 51.000| degrees C| ok| 0.000| -1.000| 0.000| 74.000|

84.000| 99.000 [root@CentOS73 ~]#

Check sensor status.

Setting thresholds If needed, set the required thresholds (upper threshold only, in the order: non-critical, critical, unrecoverable). The

values used are in degree C as decimal integers.

COMMAND

PURPOSE

[root@CentOS73 ~]# ipmitool sensor thresh "Temp PCIe" upper 10 30 50

Locating sensor record 'Temp PCIe'... Setting sensor "Temp PCIe" Upper Non-Critical threshold to

10.000 Setting sensor "Temp PCIe" Upper Critical threshold to 30.000 Setting sensor "Temp PCIe" Upper Non-Recoverable threshold to

50.000 [root@CentOS73 ~]# ipmitool sensor thresh "Temp SFP 1" upper

10 30 50

Locating sensor record 'Temp SFP 1'... Setting sensor "Temp SFP 1" Upper Non-Critical threshold to

10.000

Set upper threshold for PCIe Card Temperature.

Set upper threshold for SFP1 Temperature.

ME1100 Doc. Rev. 1.3

www.kontron.com // 67

Setting sensor "Temp SFP 1" Upper Critical threshold to 30.000 Setting sensor "Temp SFP 1" Upper Non-Recoverable threshold to

50.000 [root@CentOS73 ~]# ipmitool sensor thresh "Temp SFP 2" upper

10 30 50

Locating sensor record 'Temp SFP 2'... Setting sensor "Temp SFP 2" Upper Non-Critical threshold to

10.000 Setting sensor "Temp SFP 2" Upper Critical threshold to 30.000 Setting sensor "Temp SFP 2" Upper Non-Recoverable threshold to

50.000 [root@CentOS73 ~]# ipmitool sensor thresh "Temp M.2" upper 10

30 50

Locating sensor record 'Temp M.2'... Setting sensor "Temp M.2" Upper Non-Critical threshold to

10.000 Setting sensor "Temp M.2" Upper Critical threshold to 30.000 Setting sensor "Temp M.2" Upper Non-Recoverable threshold to

50.000 [root@CentOS73 ~]#

[root@CentOS73 ~]# ipmitool sensor | grep Temp | tail -n 4 Temp PCIe | 17.000 | degrees C | nc | 0.000 | -1.000 | 0.000 | 10.000 | 30.000 | 50.000 Temp M.2 | 34.000 | degrees C | cr | 0.000 | -1.000 | 0.000 | 10.000 | 30.000 | 50.000 Temp SFP 1 | 51.000 | degrees C | ok | 0.000 | -1.000 | 0.000 | 74.000 | 84.000 | 99.000 Temp SFP 2 | 51.000 | degrees C | nr | 0.000 | -1.000 | 0.000 | 10.000 | 30.000 | 50.000 [root@CentOS73 ~]#

Set upper threshold for SFP2 Temperature.

Set upper threshold for M.2 Temperature.

Check sensor status.

Functionality in degraded modes a) When updating the BMC's temperatures through FPGA registers When the user application running on the OS stops, for whatever reason, sending the temperatures to the FPGA, the

BMC will consider that these temperatures are not available and will take no particular action. The BMC will continue to control the fans using data from the other available sensors.

When of the actual temperature for these four temperatures.

Example:

COMMAND

[root@CentOS73 ~]# ipmitool sensor | grep Temp | tail -n 4 Temp PCIe | na | degrees C | na | 0.000 | -1.000 | 0.000 |

59.000 | 69.000 | 99.000

Temp M.2 | na | degrees C | na | 0.000 | -1.000 | 0.000 |

59.000 | 69.000 | 99.000

Temp SFP 1 | na | degrees C | na | 0.000 | -1.000 | 0.000 |

74.000 | 84.000 | 99.000

Temp SFP 2 | na | degrees C | na | 0.000 | -1.000 | 0.000 |

74.000 | 84.000 | 99.000

b) When updating the BMC's temperatures through IPMI commands When the user application running on the OS stops, for whatever reason, sending the temperatures to the BMC using

IPMI, the BMC will consider that the last value received is still valid for these sensors. The BMC will continue to control the fans using data from the other available sensors and also the last values received from the user application for the four temperature sensors.

When checking sensor status, the last temperature received for the four sensors will be displayed. These temperatures will be considered when computing the speed of the fans.

ME1100 Doc. Rev. 1.3

www.kontron.com // 68

c) When only the BMC is restarted (e.g. firmware upgrade) The thresholds of the temperature sensors in the BMC can be set by users, but the values set are volatile. When the BMC is restarted while the payload CPU continues operating, the temperature thresholds are restored to

the default values. The user application in charge of temperature monitoring has to detect this condition and set the user thresholds

again, as needed. The BMC can be monitored based on the response to IPMI commands, either used to set the user temperatures or to

get the BMC's status: observing timeouts on these commands is an indication that the BMC is rebooting.

5. Setting BMC time For safety purposes, the ME1100 BMC does not use a battery to store time. The NTP is provided as solution for BMC

time synchronization. An OEM command was added to the kipmid for the user to set the NTP server(s) or periodically set the time,

depending on preference. The command is: IPMI_OEMAP_CMD_SET_NTP_SERVER with the Func. code 86h. This command supports several sub-functions required by different use cases.

No SEL event is generated by the NTP because time lapses greater than one second would generally not occur other than at boot or when commissioning the server.

1. Use case 1 Using up to three NTP servers to synchronize the time of the BMC The sub-function OEMAP_NTP_SET_CONFIG (01h) is used to set one, two or three IPv4 addresses, corresponding to

the NTP servers. The kipmid will update the NTP configuration with the addresses and restart the NTP service. At first, a time lap is

executed, and then the NTP protocol is used for continuous time synchronization. The kipmid verifies that the data byte count is exact and that the first byte of each IP address is not zero. Example:

COMMAND

PURPOSE

[root@CentOS73 ~]# ipmitool raw 0x3e 0x86 0x01 10 1 20 10

[root@CentOS73 ~]# ipmitool kontronoem ntp addr 10.1.20.10

Set the IP address to 10.1.20.10 for the NTP server.

2. Use case 2 Relying solely on the local hardware for time synchronization and setting the epoch time periodically

a) The sub-function OEMAP_NTP_SET_CONFIG (02h) is called to set the usage of the local hardware only. No data bytes are used.

The kipmid will update the NTP configuration and restart the NTP service. Example:

COMMAND

PURPOSE

[root@CentOS73 ~]# ipmitool raw 0x3e 0x86 0x02

[root@CentOS73 ~]# ipmitool kontronoem ntp local

Set the BMC to use only its own hardware for time.

ME1100 Doc. Rev. 1.3

www.kontron.com // 69

NOTE: Each time the BMC restarts (e.g. after a version update), its time is reset and needs to be updated by the user.

b) The sub-function OEMAP_NTP_SET_OFFSET (03h) allows the user to set the time by providing 4 data bytes with the epoch time requested.

Each time an epoch time is pushed by the user, the BMC creates the time lap required to be at the time requested. Example:

COMMAND

PURPOSE

[root@CentOS73 ~]# ipmitool raw 0x3e 0x86 0x03 0x5b 0xad 0xbe 0xef

[root@CentOS73 ~]# ipmitool kontronoem ntp epoch 1538113263

Set the time to Sep 28 05:41:03 UTC

2018.

Set the time to Sep 28 05:41:03 UTC

2018.

ME1100 Doc. Rev. 1.3

www.kontron.com // 70

Appendix E:

Several useful IPMI commands are implemented by Kontron as OEM commands. (The ipmitool version should be at least 1.8.13-K12 to support the NTP OEM commands.)

Below is a short list of the available commands (00 = Linear and 01 = Circular):

1. Set SEL buffer Linear:

~/$ ipmitool raw 0x3E 0x84 0x00 0x00

2. Set SEL buffer Circular (the SEL buffer is circular by default):

~/$ ipmitool raw 0x3E 0x84 0x00 0x01

3. Get SEL buffer type:

~/$ ipmitool raw 0x3E 0x84 0x00

4. Enable the NTP and set up to 3 NTP server IP addresses:

~/$ ipmitool kontronoem ntp adddr <xxx.xxx.xxx.xxx> [yyy.yyy.yyy.yyy] [zzz.zzz.zzz]

5. Disable the NTP and follow the local HW clock only:

~/$ ipmitool kontronoem ntp local

6. When using the local HW clock only, set the date and time:

~/$ ipmitool kontronoem ntp epoch 1538113263

ME1100 Doc. Rev. 1.3

www.kontron.com // 71



CORPORATE OFFICES

KONTRON CANADA

EUROPE, MIDDLE EAST & AFRICA

NORTH AMERICA

ASIA PACIFIC

4555 Ambroise-Lafortune Boisbriand, QC Canada J7H 0A4 Tel.: +1 450 437-5682 Tel.: +1 800 387-4223

Lise-Meitner-Str. 3-5 86156 Augsburg Germany

Fax: + 49 821 4086-111 info@kontron.com

14118 Stowe Drive Poway, CA 92064-7147 USA Tel.: + 1 888 294 4558 Fax: + 1 858 677 0898 info@us.kontron.com

1~2F, 10 Building, No. 8 Liangshuihe 2nd Street, Economical & Technological Development Zone, Beijing, 100176, P.R. China Tel.: + 86 10 63751188 Fax: + 86 10 83682438 info@kontron.cn

About Kontron Kontron, a global leader in embedded computing technology and trusted advisor in IoT,

works closely with its customers, allowing them to focus on their core competencies by offering a complete and integrated portfolio of hardware, software and services designed to help them make the most of their applications.

With a significant percentage of employees in research and development, Kontron creates

life numerous technologies and applications that touch millions of lives. The result is an accelerated time-to-market, reduced total-cost-of-ownership, product longevity and the best possible overall application with leading-edge, highest reliability embedded technology

For more information, please visit: http://www.kontron.com/.

Kontron ME1100 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual