HPE ilo 4 Release Notes

(1)

HPE iLO 4 Release Notes

2.40

Part Number: 684917-406 Published: April 2016 Edition: 1

(2)

The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.

Acknowledgements

Java is a registered trademark of Oracle and/or its affiliates.

Linux®is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft®, Windows Server®, and Windows®are trademarks of the Microsoft group of companies. Red Hat®is a registered trademark of Red Hat, Inc. in the United States and other countries.

(3)

Description

The HPE iLO subsystem is a standard component of HPE ProLiant servers that simplifies initial server setup, server health monitoring, power and thermal optimization, and remote server administration. The iLO subsystem includes an intelligent microprocessor, secure memory, and a dedicated network interface. This design makes iLO independent of the host server and its operating system.

iLO enables and manages the HPE Active Health System and also features HPE Agentless

Management. iLO monitors all key internal subsystems. When enabled, SNMP alerts are sent directly by iLO, regardless of the host operating system or whether a host operating system is installed. Embedded remote support software is available on ProLiant Gen8 and Gen9 servers with iLO 4, regardless of the operating system software and without installing OS agents on the server.

Update recommendation

Recommended. Update to this firmware version if your system is affected by one of the documented fixes or to take advantage of the enhanced functionality provided by this version.

Supersede information

Supersedes: 2.30

Product models

iLO 4

Devices supported

Gen9 servers

• ProLiant BL660c Gen9 Server Blade • ProLiant BL460c Gen9 Server Blade • ProLiant DL580 Gen9 Server

• ProLiant DL560 Gen9 Server • ProLiant DL380 Gen9 Server • ProLiant DL360 Gen9 Server • ProLiant DL180 Gen9 Server • ProLiant DL160 Gen9 Server • ProLiant DL120 Gen9 Server • ProLiant DL80 Gen9 Server • ProLiant DL60 Gen9 Server • ProLiant DL20 Gen9 Server • ProLiant ML350 Gen9 Server • ProLiant ML150 Gen9 Server • ProLiant ML110 Gen9 Server • ProLiant ML30 Gen9 Server • ProLiant XL450 Gen9 Server • ProLiant XL750f Gen9 Server

(4)

• ProLiant XL740f Gen9 Server • ProLiant XL730f Gen9 Server • ProLiant XL250a Gen9 Server • ProLiant XL230a Gen9 Server • ProLiant XL230b Gen9 Server • ProLiant XL190r Gen9 Server • ProLiant XL170r Gen9 Server

• ProLiant WS460c Gen9 Graphics Server Blade

Gen8 servers

• ProLiant BL660c Gen8 Server Blade • ProLiant BL465c Gen8 Server Blade • ProLiant BL460c Gen8 Server Blade • ProLiant BL420c Gen8 Server Blade • ProLiant DL580 Gen8 Server

• ProLiant DL560 Gen8 Server • ProLiant DL385p Gen8 Server • ProLiant DL380p Gen8 Server • ProLiant DL380e Gen8 Server • ProLiant DL360p Gen8 Server • ProLiant DL360e Gen8 Server • ProLiant DL320e Gen8 v2 Server • ProLiant DL320e Gen8 Server • ProLiant DL160 Gen8 Server • ProLiant ML350e Gen8 Server • ProLiant ML350p Gen8 Server • ProLiant ML310e Gen8 v2 Server • ProLiant ML310e Gen8 Server • ProLiant SL4540 Gen8 Server • ProLiant SL210t Gen8 Server • ProLiant SL270s Gen8 Server • ProLiant SL270s Gen8 SE Server • ProLiant SL250s Gen8 Server • ProLiant SL230s Gen8 Server • ProLiant XL220a Gen8 v2 Server • ProLiant MicroServer Gen8

• ProLiant WS460c Gen8 Graphics Server Blade

(5)

Operating systems

• Microsoft Windows Server 2008 • Microsoft Windows Server 2008 R2 • Microsoft Windows Server 2012 • Microsoft Windows Server 2012 R2

• Red Hat Enterprise Linux 6 (x86, AMD64/EM64T) • Red Hat Enterprise Linux 7

• SUSE Linux Enterprise Server 11 (x86, AMD64/EM64T) • SUSE Linux Enterprise Server 12

• VMware ESX 4.0, 4.1

• VMware vSphere 5.1, 5.5, 6.0

Browser requirements

The following browsers are supported for running the iLO web interface: • Internet Explorer 11

• Firefox (latest version) • Chrome (latest version)

The following settings must be enabled:

• JavaScript—Client-side JavaScript is used extensively by this application. • Cookies—Cookies must be enabled for certain features to function correctly.

• Pop-up windows—Pop-up windows must be enabled for certain features to function correctly. Verify that pop-up blockers are disabled.

• TLS—To access the iLO 4 2.03 or later web interface, you must enable TLS in your browser.

Languages

Languages supported for this release: English, Japanese, Simplified Chinese.

Enhancements

• The iLO web interface has been updated to support the Hewlett Packard Enterprise style, URLs, and company information.

• The Java IRC now includes two alternatives: A Java Web Start console and a Java applet-based console. The Java Web Start option works in newer browsers that do not allow the applet version to run. On systems with OpenJDK, you must use the Java applet-based console with a browser (such as Firefox) that supports a Java plug-in.

• The newCritical Temperature Remain Offsetting can be configured via RIBCL for all nonblade servers. This setting controls system behavior when the system is shut down due to thermal protection circuitry. This is a hardware-based protection mechanism for thermal events, and it is not based on temperature sensor thresholds, OS policy, or the environmental abnormality automatic shutdown configuration.

• The following service events are now supported with embedded remote support registration: ATA Disk Drive Status Changed Event

◦

Fibre Channel Host Controller Status Changed Event

(6)

• TheServer Resetbutton is now available on theBoot Orderpage when theBoot Modeis modified.

• The NVMe Backplane PIC firmware can now be updated via iLO. • The logical drive label and ID were added to the RESTful API.

• NIC auto-selection can now be configured to search both Shared Network Ports on servers that support this hardware configuration. This feature can be configured via the CLI and RIBCL. • NIC auto-selection can now be configured to support NIC failover. When enabled, iLO

automatically begins searching for a NIC connection when the current connection fails. This feature can be configured via the CLI and RIBCL.

Fixes

• NIC auto-selection can be configured via RIBCL on DL60 and DL80 Gen9 servers. These servers do not support the iLO Dedicated Network Port or NIC auto-selection.

• There is no POST error after one or more fans are removed.

• iLO does not collect and delete out of date or unused BIOS provider schemas and registries. • The iLO 4 web server might stop responding after an invalid file is submitted on the firmware

update page.

• When system throttling occurs on Gen8 servers, the duration is longer than necessary.

• Cookies set by older versions of iLO were not understood correctly and might cause problems when you try to select iLO Federation groups.

• The chassis firmware version number is not displayed consistently in the web interface. • Sorting by column does not work in some iLO web interface tables.

• The language icon at the bottom of the browser window is not displayed in Internet Explorer. • The domain name cannot be set via the CLP when the Shared Network Port is enabled. • A drive failure does not trigger an action when IPMI PEF is enabled.

• The json/power_alert API returns an incorrect error (HTTP error 500) for bad parameters. • The wrong iLO self-test nameUnknownSelfTestis displayed for the NVRAM space test in

Redfish output.

• TheUID Indicatorstatus does not change to BLINK when the Integrated Remote Console is active.

• Kerberos authentication cannot be enabled when FIPS mode is enabled.

• Keystrokes are repeated in the Integrated Remote Console when the server is in the UEFI Shell. • Data is not displayed in the power meter 20 minute or 24 hour graph.

• TheLicensepage does not refresh to update the status after an iLO Advanced license is installed.

• Redfish output does not group the Average, Minimum, and Peak values together in the Fast Power Meter output.

• TheNIC Informationpage displays the address0.0.0.0when the IPv6 address is the only IP address available for the iLO NIC.

• Duplicate entries for network cards are displayed on theDevice Inventorypage. • Redfish output displays an incorrect memory type for non-HPE memory.

• TheNIC Informationpage displays the valueN/Awhen a NIC team is configured.

(7)

• An incorrect error message is displayed for theTESTTRAPcommand after SNMP alerts are disabled.

• Power consumption values are incorrect in RedfishChassis/1/Power/FastPowerMeter/

output.

• Power supply bay numbering is inconsistent between the web interface and RESTful API output. • If an SNMP test alert is sent when SNMPv1 traps are disabled and SNMPv3 users are not

defined, iLO reports a successful test when an error should be displayed.

• An event log message is not logged when an SSL certificate is imported via the RESTful API. • A password that contains the equals sign (=) cannot be set when a user is added by using the

CLI.

• The value null is displayed for all RESTful APINetworkAdapterspacket statistics. • The RESTful API schema file does not include the supported values forSpeedMbps. • An infinite loop in the file system check utility causes slow system performance. • DL580 Gen9 servers might fail to boot from an SD card.

• The 53-Sensor LOM is displayed as missing on theTemperaturespage for DL580 Gen8 servers. • After a vulnerability scan, iLO 4 might be left doing ACK flood with the scanner software. • iLO 4 might become unresponsive when attempting to delete an old Active Health System file

with an invalid character in its name.

• AlertMail rejects email addresses with hyphen characters. • Only one LDAP server can be configured by using RIBCL.

• Insight Remote Support is not alerted if a failed hard drive is on a bay number above 18.

Prerequisites

iLO utilities

For best performance, IPv6 support, and TLS v1.1 or later support, Hewlett Packard Enterprise recommends upgrading to the latest versions of the iLO utilities:

Notes Version

Utility

This replaced the CPQLOCFG utility. 1.5.0

HPQLOCFG

4.80 Lights-Out XML Scripting Sample bundle

4.7.0.0 HPONCFG for Windows

4.6.0-0 HPONCFG for Linux

Available in the Lights-Out XML Scripting Sample bundle. 4.80

LOCFG.PL

Upgrade HPLOMIG before installing this version of iLO 4. 4.80

HPLOMIG

Licensing

Some features are part of an iLO licensing package. For more information about iLO licensing, see the following website:http://www.hpe.com/info/ilo/licensing.

(8)

Integrated Remote Console

• You must install Java Runtime Environment 8 or later to use the Java IRC.

• Google Chrome version 42 and later does not support the Java plug-in. The following alternatives are available:

◦

Windows users: Use the Java IRC Java Web Start application.

◦

Linux users with Oracle JRE: Use the Java IRC Java Web Start application.

◦

Linux users with OpenJDK JRE: Use the Java IRC applet.

• The .NET IRC requires one of the following versions of the .NET Framework: .NET Framework 3.5 Full (SP1 recommended)

◦

.NET Framework 4.0 Full

◦

.NET Framework 4.5

◦

.NET Framework 4.6

For Windows 7, 8, 8.1, and 10, a supported version of the .NET Framework is included in the OS. The .NET Framework is also available at the Microsoft Download Center:http://

www.microsoft.com/download.

The .NET Framework versions 3.5 and 4.0 have two deployment options: Full and Client Profile. The Client Profile is a subset of the Full framework. The .NET IRC is supported with the Full framework only; the Client Profile is not supported. Version 4.5 and later of the .NET Framework do not have the Client Profile option.

• The .NET IRC is launched using Microsoft ClickOnce, which is part of the .NET Framework. Mozilla Firefox requires an add-on to launch .NET applications. You can launch the .NET IRC from a supported version of Firefox by using a ClickOnce add-on such as the Microsoft

◦

.NET Framework Assistant. You can download the .NET Framework Assistant fromhttp:// addons.mozilla.org/.

◦

Google Chrome requires an extension to launch .NET applications. As a workaround, use one of the following:

– The Java IRC.

– The .NET IRC with a different browser.

– The standalone .NET IRC.

– The iLO mobile app.

Installation instructions

See the following document for installation instructions: HPE iLO 4 user guide

Part number: 684918-403 Edition: 1

Support

iLO 4 firmware updates and utilities can be found here:http://www.hpe.com/support/ilo4.

(9)

IPv6

• iLO 4 supports the following IPv6 dedicated network communications: IPv6 Static Address Assignment

◦

IPv6 SLAAC Address Assignment

◦

IPv6 Static Route Assignment

◦

IPv6 Static Default Gateway Entry

◦

DHCPv6 Stateful Address Assignment

◦

DHCPv6 Stateless DNS, Domain Name, and NTP Configuration

◦

Integrated Remote Console

◦

HPE Onboard Administrator Single Sign-On

◦

HPE SIM Single Sign-On

◦

Web Server

◦

SSH Server

◦

SNTP Client

◦

DDNS Client

◦

RIBCL over IPv6

◦

SNMP

◦

AlertMail

◦

Remote Syslog

◦

WinDBG Support

◦

HPQLOCFG/HPLOMIG over an IPv6 connection

◦

Scriptable Virtual Media

◦

CLI/RIBCL key import over an IPv6 connection

◦

Authentication using LDAP and Kerberos over IPv6

◦

iLO Federation

◦

IPMI

• iLO 4 does not support the following IPv6 networking features: Shared Network Port Connections

◦

NETBIOS-WINS

◦

ESKM Support for Storage

◦

Embedded Remote Support

(10)

Shared Network Port selection

This feature allows you to choose between port 1 and port 2 for Shared Network Port functionality. You can configure this setting on theNetwork→Shared Network Port→Generalpage in the iLO web interface.

Not all sideband NICs are supported. In some cases, port 2 might not be fully functional. The following NICs work with port 2:

• 361i-2port-1GB NIC • 331FLR-4P-1G NIC • 366FLR-4P-1G NIC • 561FLR-T-2P-10GB NIC • 526FLR-SFP+2P-10GB NIC

• HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (Port #2 Only) • 534FLR-SFP+2P-10GB NIC

• HPE Ethernet 1GB 2-port 330i Adaptor

• BCM57810 NetXtreme II 10 GigE (NDIS VBD) • HPE FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter • HPE Ethernet 10Gb 2P 560FLR-SFP+ Adapter

Documentation feedback

Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.