NEC iLO 5 User Manual

Download

Page 1

iLO 5 User’s Guide

1. iLO

2. Setting up iLO

3. Using the iLO web interface

4. Viewing iLO information and logs

5. Viewing general system information

6. Managing firmware, software, and language packs

7. Configuring and using iLO Federation

8. iLO Integrated Remote Console

9. Using a text-based Remote Console

10. Using iLO Virtual Media

11. Using the power and thermal features

12. Configuring iLO network settings

13. Using the iLO administration features

14. Using the iLO security features

15. Configuring iLO management settings

16. IPMI server management

17. Managing iLO reboots, factory reset, and NMI

18. Troubleshooting

2017/10

NEC Express Server Express5800 Series

Page 2

Notices

The information contained herein is subject to change without notice. The only warranties for NEC Corporation 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. NEC Corporation shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from NEC Corporation 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 NEC Corporation website. NEC Corporation has no control over and is not responsible for information outside the NEC Corporation website.

Acknowledgments

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Java® and Oracle® are registered trademarks of Oracle and/or its affiliates. Google™ is a

trademark of Google Inc.

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

Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.

SD is a trademark or registered trademark of SD-3C in the United States, other countries or both.

VMware® is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions.

Redfish® is a registered trademark of Distributed Management Task Force.

Page 3

Contents

1. iLO ..................................................................................... 1

iLO key features ............................................................................................................................................ 1

ROM-based configuration utility ..................................................................................................................... 2

iLO RESTful API ............................................................................................................................................ 2

RESTful Interface Tool ................................................................................................................................... 2

iLO scripting and command line ..................................................................................................................... 2

2. Setting up iLO .................................................................. 4

Preparing to set up iLO .................................................................................................................................. 4

Initial setup steps: Process overview.............................................................................................................. 8

Connecting iLO to the network ................................ ................................................................ ....................... 8

Setting up iLO by using the BMC Configuration Utility .................................................................................... 8

Logging in to iLO for the first time ................................................................................................................ 12

iLO default credentials ................................................................................................................................. 12

iLO licensed features ................................................................................................................................... 12

iLO drivers ................................................................................................................................................... 13

iLO time zone .............................................................................................................................................. 13

3. Using the iLO web interface .......................................... 16

iLO web interface ........................................................................................................................................ 16

Supported browsers .................................................................................................................................... 16

Browser requirements.................................................................................................................................. 16

Configuring the Internet Explorer JavaScript setting ..................................................................................... 16

Logging in to the iLO web interface .............................................................................................................. 17

Cookie sharing between browser instances and iLO .................................................................................... 17

iLO web interface ........................................................................................................................................ 19

Changing the language from the login page ................................................................................................. 20

4. Viewing iLO information and logs ................................ 22

Viewing iLO overview information ................................................................................................................ 22

Managing iLO sessions ............................................................................................................................... 25

iLO Event Log ............................................................................................................................................. 26

Integrated Management Log ........................................................................................................................ 31

Active Health System .................................................................................................................................. 38

Downloading the Active Health System Log for a date range ....................................................................... 38

Viewing iLO self-test results ......................................................................................................................... 41

5. Viewing general system information ............................ 43

Viewing processor information ..................................................................................................................... 45

Viewing memory information ........................................................................................................................ 46

Viewing network information ........................................................................................................................ 52

Viewing the device inventory........................................................................................................................ 55

Viewing storage information ......................................................................................................................... 57

6. Managing firmware, software, and language packs ... 62

Firmware updates ........................................................................................................................................ 62

Viewing and updating firmware from the iLO web interface .......................................................................... 63

Viewing installed firmware information ......................................................................................................... 67

iLO Repository............................................................................................................................................. 69

Install Sets .................................................................................................................................................. 73

Installation Queue ....................................................................................................................................... 76

Installing language packs ............................................................................................................................ 78

Viewing software information ....................................................................................................................... 79

7. Configuring and using iLO Federation ........................ 81

iLO Federation ............................................................................................................................................ 81

Page 4

Configuring iLO Federation .......................................................................................................................... 81

iLO Federation groups ................................................................................................................................. 84

Managing iLO Federation group memberships (local iLO system) ................................................................ 86

Adding iLO Federation group memberships (multiple iLO systems) .............................................................. 90

Using the iLO Federation features ............................................................................................................... 94

iLO Federation Multi-System view................................................................................................................ 96

iLO Federation Group Virtual Media ............................................................................................................. 99

iLO Federation Group Power ..................................................................................................................... 102

Configuring group power capping .............................................................................................................. 105

iLO Federation Group Firmware Update .................................................................................................... 108

Installing license keys (iLO Federation group) ............................................................................................ 111

8. iLO Integrated Remote Console ................................. 112

.NET IRC requirements ............................................................................................................................. 113

Starting the Integrated Remote Console .................................................................................................... 115

Console Capture (.NET IRC only) .............................................................................................................. 120

Remote Console hot keys .......................................................................................................................... 123

Configuring Remote Console Computer Lock settings ............................................................................... 126

Configuring the Integrated Remote Console Trust setting (.NET IRC) ......................................................... 127

9. Using a text-based Remote Console .......................... 128

Using the iLO Virtual Serial Port................................................................................................................. 128

10. Using iLO Virtual Media ............................................. 135

Virtual Media operating system information ................................ ................................................................ 137

Using Virtual Media from the iLO web interface .......................................................................................... 139

Remote Console Virtual Media .................................................................................................................. 143

11. Using the power and thermal features ..................... 148

Server power-on ........................................................................................................................................ 148

Brownout recovery..................................................................................................................................... 148

Graceful shutdown..................................................................................................................................... 148

Power efficiency ........................................................................................................................................ 149

Managing the server power ....................................................................................................................... 149

Configuring the System Power Restore Settings ........................................................................................ 151

Viewing server power usage ...................................................................................................................... 152

Power settings ........................................................................................................................................... 157

Viewing power information ......................................................................................................................... 161

Viewing fan information ............................................................................................................................. 165

Temperature information ............................................................................................................................ 167

12. Configuring iLO network settings ............................ 170

iLO network settings .................................................................................................................................. 170

Viewing the network configuration summary .............................................................................................. 170

General network settings ........................................................................................................................... 173

Configuring iLO SNTP settings .................................................................................................................. 185

iLO NIC auto-selection............................................................................................................................... 189

Viewing iLO systems in the Windows Network folder ................................................................ .................. 191

13. Using the iLO administration features ..................... 192

iLO directory groups .................................................................................................................................. 198

Boot Order ................................................................................................................................................ 202

Installing a license key by using a browser ................................................................................................. 207

Language packs ........................................................................................................................................ 209

iLO Backup & Restore ............................................................................................................................... 212

14. Using the iLO security features ................................ 216

iLO security ................................................................................................................................ ............... 216

iLO access settings ................................................................................................................................... 218

Page 5

iLO Service Port ........................................................................................................................................ 226

Administering SSH keys ............................................................................................................................ 231

Directory authentication and authorization ................................................................................................. 240

Configuring encryption settings .................................................................................................................. 248

NEC SSO .................................................................................................................................................. 250

Configuring the Login Security Banner ....................................................................................................... 251

iLO security with the system maintenance switch ....................................................................................... 253

15. Configuring iLO management settings .................... 254

Agentless Management and AMS .............................................................................................................. 254

Configuring SNMP settings ........................................................................................................................ 255

SNMPv3 authentication ................................................................ ............................................................. 256

SNMP traps ................................................................................................................................ ............... 263

iLO AlertMail .............................................................................................................................................. 269

Remote Syslog .......................................................................................................................................... 271

16. IPMI server management .......................................... 273

17. Managing iLO reboots, factory reset, and NMI ........ 275

Rebooting (resetting) iLO ................................................................ ........................................................... 275

Reset iLO to the factory default settings ..................................................................................................... 278

Generating an NMI .................................................................................................................................... 280

18. Troubleshooting ................................ ........................ 281

Using the iLO Virtual Serial Port with Windbg ............................................................................................. 281

Using the Server Health Summary ................................................................ ............................................. 283

Incorrect time stamp on iLO Event Log entries ........................................................................................... 285

Login and iLO access issues ..................................................................................................................... 286

iLO management port not accessible by name ........................................................................................... 286

Unable to connect to iLO IP address .......................................................................................................... 290

Directory issues ......................................................................................................................................... 294

Remote Console issues ............................................................................................................................. 302

SSH issues................................................................................................................................................ 313

iLO Federation issues ................................................................................................................................ 314

Firmware update issues ............................................................................................................................. 317

Licensing issues ........................................................................................................................................ 319

License key installation errors ................................................................ .................................................... 319

Unable to access Virtual Media or graphical Remote Console .................................................................... 320

Agentless Management, AMS, and SNMP issues ...................................................................................... 320

A. iLO license options ...................................................... 321

B. Ports used in iLO ......................................................... 322

Glossary .............................................................................. 323

Page 6

Page 7

1. iLO

iLO 5 is a remote server management processor embedded on the system boards of NEC Express servers. iLO enables the monitoring and controlling of servers from remote locations. iLO management is a powerful tool that provides multiple ways to configure, update, monitor, and repair servers remotely. iLO (Standard) comes preconfigured on servers without an additional cost or license.

Features that enhance server administrator productivity and additional new security features are licensed.

iLO key features

• Server health monitoring—iLO monitors temperatures in the server and sends corrective

signals to the fans to maintain proper server cooling. iLO also monitors installed firmware and software versions and the status of fans, memory, the network, processors, power supplies, storage, and devices installed on the system board.

• Agentless Management—With Agentless Management, the management software (SNMP)

operates within the iLO firmware instead of the host OS. This configuration frees memory and processor resources on the host OS for use by server applications. iLO monitors all key internal subsystems, and can send SNMP alerts directly to a central management server, even with no host OS installed.

• Integrated Management Log—View server events and configure notifications through SNMP

alerts, remote syslogs, and email alerts.

• Active Health System Log—Download the Active Health System log. You can send the log file

to NEC Corporation when you have an open support case.

• iLO Federation management—Use the iLO Federation features to discover and manage

multiple servers at a time.

• Integrated Remote Console—If you have a network connection to the server, you can access

a secure high-performance console to manage the server from any location.

• Virtual Media—Remotely mount high-performance Virtual Media devices to the server.

• Power management—Securely and remotely control the power state of the managed server.

• Deployment and provisioning—Use Virtual Power and Virtual Media for tasks such as the

automation of deployment and provisioning.

• Power consumption and power settings—Monitor the server power consumption, configure

server power settings, and configure power capping on supported servers.

• User access—Use local or directory-based user accounts to log in to iLO.

• Two-factor authentication—Two-factor authentication is supported with Kerberos.

• iLO interface controls—For enhanced security, enable or disable selected iLO interfaces and

features.

• Firmware management—Save components to the iLO Repository and use SUM to configure

install sets and manage the installation queue.

• iLO Service Port—Use a supported USB Ethernet adapter to connect a client to the iLO

Page 8

Service Port to access the server directly. You can also connect a USB key to download the Active Health System Log.

• IPMI—The iLO firmware provides server management based on the IPMI version 2.0

specification.

• iLO RESTful API and RESTful Interface Tool (iLOrest)—iLO 5 includes the iLO RESTful API,

which is Redfish API conformant

• iLO Backup & Restore—Back up the iLO configuration and then restore it on a system with

the same hardware configuration when replacing the motherboard etc.

ROM-based configuration utility

You can use the BMC Configuration Utility in the UEFI System Utilities to configure network parameters, global settings, and user accounts.

The BMC Configuration Utility is designed for the initial iLO setup, and is not intended for continued iLO administration. You can start the utility when the server is booted, and you can run it remotely with the Remote Console.

You can configure iLO to require users to log in when they access the BMC Configuration Utility, or you can disable the utility for all users. These settings can be configured on the Access Settings page. Disabling the BMC Configuration Utility prevents reconfiguration from the host unless the system maintenance switch is set to disable iLO security.

To access the BMC Configuration Utility, press F9 during POST to start the UEFI System Utilities. Click System Configuration, and then click BMC Configuration Utility.

iLO RESTful API

iLO includes the iLO RESTful API, which is Redfish API conformant. The iLO RESTful API is a management interface that server management tools can use to perform configuration, inventory, and monitoring tasks by sending basic HTTPS operations (GET, PUT, POST, DELETE, and PATCH) to the iLO web server.

RESTful Interface Tool

The RESTful Interface Tool (iLOrest) is a scripting tool that allows you to automate Express server management tasks. It provides a set of simplified commands that take advantage of the iLO RESTful API.

You can install the tool on your computer for remote use or install it locally on a server with a Windows or Linux Operating System. The RESTful Interface Tool offers an interactive mode, a scriptable mode, and a file-based mode to help decrease automation times.

iLO scripting and command line

Page 9

You can use the iLO scripting tools to configure multiple servers, to incorporate a standard configuration into the deployment process, and to control servers and subsystems.

The iLO scripting and CLI guide describes the syntax and tools available for using iLO through a command line or scripted interface.

Page 10

2. Setting up iLO

Express Server

Production

Network

Management

Network

Management Clients

Production Clients

Preparing to set up iLO

Before setting up an iLO management processor, you must decide how to handle networking and security. The following questions can help you configure iLO:

Procedure

1. How will iLO connect to the network?

2. Will NIC Teaming be used with the Shared Network Port configuration?

3. How will iLO acquire an IP address?

4. What access security is required, and what user accounts and privileges are needed?

5. What tools will you use to configure iLO?

iLO network connection options

Typically, iLO is connected to the network through a dedicated management network or a shared connection on the production network.

Dedicated management network

In this configuration, the iLO port is on a separate network. A separate network improves performance and security because you can physically control which workstations are connected to the network. A separate network also provides redundant access to the server when a hardware failure occurs on the production network. In this configuration, iLO cannot be accessed directly from the production network. The Dedicated management network is the preferred iLO network configuration.

Figure 1: Dedicated management network

Production network

In this configuration, both the NIC and the iLO port are connected to the production network. In iLO, this type of connection is called the Shared Network Port configuration. Certain NEC Corporation embedded NICs and add-on cards provide this capability. This connection enables access to iLO from anywhere on the network and reduces the amount of networking hardware and infrastructure required to support iLO.

Page 11

Express Server

Server NIC/iLO Shared NIC

Management Clients

Hub/Switch

Management/

Production

Network

Production Clients

• There are some drawbacks to using this configuration.

• With a shared network connection, traffic can hinder iLO performance.

• During the server boot process and when the OS NIC drivers are loading and unloading, there

are brief periods of time (2–8 seconds) when iLO cannot be reached from the network. After these short periods, iLO communication is restored and iLO will respond to network traffic.

Figure 2: Shared network connection

NIC teaming with Shared Network Port configurations

NIC teaming is a feature you can use to improve server NIC performance and reliability.

NIC teaming constraints

When you select a teaming mode to use when iLO is configured to use the Shared Network Port:

• iLO network communications will be blocked in the following conditions: ◦ The selected NIC teaming mode causes the switch that iLO is connected with to ignore

traffic from the server NIC/port that iLO is configured to share.

◦ The selected NIC teaming mode sends all traffic destined for iLO to a NIC/port other than

the one that iLO is configured to share.

• Because iLO and the server transmit and receive on the same switch port, the selected NIC teaming mode must allow the switch to tolerate traffic with two different MAC addresses on the same switch port. Some implementations of LACP (802.3ad) will not tolerate multiple MAC addresses on the same link.

NIC teaming modes

If your server is configured to use NIC teaming, observe the following guidelines.

Network Fault Tolerance

The server transmits and receives on only one NIC (the primary adapter). The other NICs (secondary adapters) that are part of the team do not transmit server traffic and they ignore received traffic. This mode allows the iLO Shared Network Port to function correctly.

Select the NIC/port iLO uses as the Preferred Primary Adapter.

Page 12

Transmit Load Balancing

The server transmits on multiple adapters but receives only on the primary adapter. This mode allows the iLO Shared Network Port to function correctly. Select the NIC/port iLO uses as the Preferred Primary Adapter.

Switch Assisted Load Balancing

In this mode, there is no concept of primary and secondary adapters. All adapters are considered equal for the purposes of sending and receiving data. This mode is the most problematic for iLO Shared Network Port configurations because traffic destined for iLO can be received on only one of the server NIC/ports. To determine the constraints that your switch vendor places on their implementation of switch assisted load balancing, see the switch vendor documentation.

iLO IP address acquisition

To enable iLO access after it is connected to the network, the iLO management processor must acquire an IP address and subnet mask. You can use a dynamic address or a static address.

Dynamic IP address

A dynamic IP address is set by default. iLO obtains the IP address and subnet mask from DNS or DHCP servers. This method is the simplest.

If you use DHCP:

• The iLO management port must be connected to a network that is connected to a DHCP

server, and iLO must be on the network before power is applied. DHCP sends a request soon after power is applied. If the DHCP request is not answered when iLO first boots, it will reissue the request at 90-second intervals.

• The DHCP server must be configured to provide DNS and WINS name resolution.

Static IP address

If DNS or DHCP servers are not available on the network, a static IP address is used. A static IP address can be configured by using the BMC Configuration Utility.

If you plan to use a static IP address, you must have the IP address before starting the iLO setup process.

iLO access security

You can use the following methods to manage access to iLO:

Local accounts

Up to 12 user accounts can be stored in iLO. This configuration is ideal for small environments such as labs and small-sized or medium-sized businesses.

Page 13

Directory services

Up to six directory groups can be configured in iLO. Use a directory to authenticate and authorize iLO access. This configuration enables an unlimited number of users and easily scales to the number of iLO devices in an enterprise.

If you plan to use directory services, consider enabling at least one local administrator account for alternate access.

A directory provides a central point of administration for iLO devices and users, and the directory can enforce a strong password policy.

iLO configuration tools

iLO supports various interfaces for configuration and operation. This guide discusses the following interfaces:

iLO web interface

Use the iLO web interface when you can connect to iLO on the network by using a web browser. You can also use this method to reconfigure an iLO management processor.

ROM-based setup

Use the BMC Configuration Utility when the system environment does not use DHCP, DNS, or WINS. Other configuration options not discussed in this guide follow:

EXPRESSBUILDER

To start EXPRESSBUILDER, press F10 during POST.

iLO RESTful API

A management interface that server management tools can use to perform configuration, inventory, and monitoring of a supported server through iLO.

Scripting

You can use scripting to set up multiple iLO management processors. You can use scripts to configure iLO on the network during initial deployment or from a deployed host.

• SMASH CLP—A command-line protocol that can be used when a command line is

accessible through SSH or the physical serial port.

Page 14

Initial setup steps: Process overview

The iLO default settings enable you to use most features without additional configuration. However, the configuration flexibility of iLO enables customization for multiple enterprise environments. This chapter discusses the initial iLO setup steps.

Procedure

1. Connect iLO to the network.

2. If you are not using dynamic IP addressing, use the ROM-based setup utilities to configure a

static IP address.

3. If you will use the local accounts feature, use the ROM-based setup utilities to

configure user accounts.

4. Configure a time zone to iLO. iLO 5 Firmware Version 1.15 Aug 17 2017 needs a time zone

configuration to display a correct date and time.

5. Optional: Install an iLO license.

6. If necessary, install the iLO drivers.

Connecting iLO to the network

Connect iLO to the network through a production network or a dedicated management network.

iLO uses standard Ethernet cabling, which includes CAT 5 UTP with RJ-45 connectors. Straightthrough cabling is necessary for a hardware link to a standard Ethernet hub or switch.

For more information about setting up your hardware, see the server user guide.

More Information

iLO network connection options

Setting up iLO by using the BMC Configuration Utility

NEC Corporation recommends using the BMC Configuration Utility to set up iLO for the first time and to configure iLO network parameters for environments that do not use DHCP, DNS, or WINS.

NOTE:

If you can connect to iLO on the network by using a web browser, you can also use the iLO web interface to configure iLO. Access iLO from a remote network client by using a supported browser and providing the default DNS name, user name, and password.

Configuring a static IP address (BMC Configuration Utility)

This step is required only if you want to use a static IP address. When you use dynamic IP addressing, the DHCP server automatically assigns an IP address for iLO.

To simplify installation, NEC Corporation recommends using DNS or DHCP with iLO.

Page 15

Procedure

1. Optional: If you access the server remotely, start an iLO remote console session.

2. Restart or power on the server.

3. Press F9 in the server POST screen.

The UEFI System Utilities start.

4. Click System Configuration.

5. Click BMC Configuration Utility.

6. Disable DHCP:

a. Click Network Options. b. Select OFF in the DHCP Enable menu.

The IP Address, Subnet Mask, and Gateway IP Address boxes become editable. When DHCP Enable is set to ON, you cannot edit these values.

7. Enter values in the IP Address, Subnet Mask, and Gateway IP Address boxes.

8. To save the changes and exit, press F12.

9. The BMC Configuration Utility prompts you to confirm that you want to save the pending configuration changes.

10. To save and exit, click Yes - Save Changes.

11. The BMC Configuration Utility notifies you that iLO must be reset in order for the changes to take effect.

12. Click OK.

iLO resets, and the iLO session is automatically ended. You can reconnect in approximately 30 seconds.

13. Resume the normal boot process: a. Start the iLO remote console.

The BMC Configuration Utility is still open from the previous session.

b. Press ESC several times to navigate to the System Configuration page. c. To exit the System Utilities and resume the normal boot process, click Exit and resume

system boot.

Managing local user accounts with the BMC Configuration Utility Adding user accounts (BMC Configuration Utility)

Procedure

1. Optional: If you access the server remotely, start an iLO remote console session.

Page 16

2. Restart or power on the server.

3. Press F9 in the server POST screen.

The UEFI System Utilities start.

4. Click System Configuration, click BMC Configuration Utility, click User Management, and then click Add User.

5. Select the privileges for the new user.

To assign a privilege, select YES in the menu next to the privilege name. To remove a privilege, select NO.

The Login privilege is assigned to every user by default, so it is not listed in the BMC Configuration Utility.

You cannot assign the Recovery Set privilege through the BMC Configuration Utility, so it is not available in the list.

6. Enter the user name and login name in the New User Name and Login Name boxes.

7. Enter the password. a. Move the cursor to the Password box, and then press Enter.

The Enter your new password box opens.

b. Type the password, and then press Enter.

The Confirm your new password box opens.

c. Type the password again to confirm, and then press Enter.

8. The BMC Configuration Utility confirms the new account creation.

9. To close the confirmation dialog box, click OK.

10. Create as many user accounts as needed, and then press F12 to save the changes and exit the system utilities.

11. When prompted to confirm the changes, click Yes - Save Changes to exit the utility and resume the boot process.

More Information

iLO user privileges iLO user account options

Editing user accounts (BMC Configuration Utility)

Procedure

1. Optional: If you access the server remotely, start an iLO remote console session.

2. Restart or power on the server.

3. Press F9 in the server POST screen.

Page 17

The UEFI System Utilities start.

4. Click System Configuration, click BMC Configuration Utility, click User Management, and then click Edit/Remove User.

5. In the Action menu for the user you want to edit or remove, select Edit.

The account properties are displayed.

6. Update the Login Name.

7. Update the Password. a. Move the cursor to the Password box, and then press Enter.

The Enter your new password box opens.

b. Type the password, and then press Enter.

The Confirm your new password box opens.

c. Type the password again to confirm, and then press Enter.

8. Modify the user account privileges.

To assign a privilege, select YES in the menu next to the privilege name. To remove a privilege, select NO.

The Login privilege is assigned to every user by default, so it is not available in the BMC Configuration Utility.

You cannot assign the Recovery Set privilege through the BMC Configuration Utility, so it is not available in the list.

9. Update as many user accounts as needed, and then press F12 to save the changes and exit the system utilities.

10. When prompted to confirm the changes, click Yes - Save Changes to exit the utility and resume the boot process.

More Information

iLO user privileges iLO user account options

Removing user accounts (BMC Configuration Utility)

Procedure

1. Optional: If you access the server remotely, start an iLO remote console session.

2. Restart or power on the server.

3. Press F9 in the server POST screen.

The System Utilities start.

4. Click System Configuration, click BMC Configuration Utility, click User Management, and then

Page 18

click Edit/Remove User.

5. In the Action menu for the user you want to remove, select Delete.

The user name is marked to be deleted when you save the changes on this page.

6. If needed, mark other user accounts to delete, and then press F12 to save the changes and exit the system utilities.

7. When prompted to confirm the changes, click Yes - Save Changes to exit the utility and resume the boot process.

Logging in to iLO for the first time

Procedure

1. Enter https://<iLO hostname or IP address>.

HTTPS (HTTP exchanged over an SSL encrypted session) is required for accessing the iLO web interface.

2. Enter the default user credentials, and then click Log In.

iLO default credentials

The iLO firmware is configured with a default user name, password, and DNS name. The default information is on the serial label pull tab attached to the server that contains the iLO management processor. Use these values to access iLO remotely from a network client by using a web browser.

• User name—Administrator

• Password—A random eight-character string

• DNS name—BMCXXXXXXXXXXXX, where the X characters represent the server serial

number.

IMPORTANT:

NEC Corporation recommends changing the default password after you log in to iLO for the first time.

If you reset iLO to the factory default settings, use the default iLO account credentials to log in after the reset.

iLO licensed features

iLO (Standard) is preconfigured on Express servers without an additional cost or license. Features that enhance productivity are licensed.

To activate iLO licensed features, install an iLO license.

Page 19

iLO drivers

iLO is an independent microprocessor running an embedded operating system. The architecture ensures that most iLO functionality is available, regardless of the host operating system. The iLO driver enables software such as the Agentless Management Service to communicate with iLO. The installed OS and system configuration determine the installation requirements.

The iLO drivers will be applied automatically when you install using EXPRESSBUILDER and Starter Pack.

iLO time zone

Configure time zone to iLO . Login to iLO Web Interface using an user has Configure iLO Settings privilege. Click iLO Dedicated Network Port and Click SNTP when iLO is using iLO Dedicated Network Port. Click iLO Shared Network Port and Click SNTP when iLO is using iLO Shared Network Port.

If you would like to sync a date and time between iLO and SNTP server, configure iLO SNTP settings.

If you won’t use time syncing function with SNTP server, configure following parameters. Use DHCPv4 Supplied Time Settings – Disable Use DHCPv6 Supplied Time Settings – Disable Primary Time Server – Blank Secondary Time Server – Blank Time Zone – Refer next page.

IMPORTANT:

The Time Zone setting is required to display correct time by iLO5 Firmware Version 1.15 Aug 17 2017 even granting that you won’t use time syncing function with SNTP server.

Page 20

If Time Format on BIOS/Platform Configuration(RBSU) is Local time, set Unspecified Time Zone (GMT) to iLO Time Zone.

BIOS/Platform Configuration(RBSU) :

iLO Web Interface:

Page 21

If Time Format on BIOS/Platform Configuration(RBSU) is Coordinated Universal Time (UTC), set same time zone parameter to iLO Time Zone.

BIOS/Platform Configuration(RBSU) :

iLO Web Interface:

After setting, Click Apply and Click Reset. iLO will restart to apply the settings.

Page 22

3. Using the iLO web interface

iLO web interface

You can use the iLO web interface to manage iLO. You can also use a Remote Console, SMASH CLP, or the iLO RESTful API.

Supported browsers

iLO 5 supports the latest versions of the following browsers:

• Microsoft Edge

• Mozilla Firefox

• Google Chrome mobile and desktop

• Microsoft Internet Explorer 11

Browser requirements

The iLO web interface requires a browser that meets the following requirements:

• JavaScript—The iLO web interface uses client-side JavaScript extensively.

This setting is not enabled by default in all versions of Internet Explorer. To check or change this setting, see Configuring the Internet Explorer JavaScript setting.

• 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 web interface, you must enable TLS 1.0 or later in your browser.

Configuring the Internet Explorer JavaScript setting

Some versions of Internet Explorer have JavaScript disabled by default. Use the following procedure to enable JavaScript.

Procedure

1. Start Internet Explorer.

2. Select Tools > Internet options.

3. Click Security.

4. Click Custom level.

5. In the Scripting section, set Active scripting to Enable.

6. Click OK.

7. Refresh your browser window.

Page 23

Logging in to the iLO web interface

Procedure

1. Enter https://<iLO host name or IP address>.

When you access the iLO web interface, you must use HTTPS (HTTP exchanged over an SSL encrypted session).

The iLO login page opens. If a login security banner is configured, the banner text is displayed in the NOTICE section.

2. Do one of the following:

• On the login page, enter a directory or local user account name and password, and then

click Log In.

• Click the Zero Sign In button.

If iLO is configured for Kerberos network authentication, the Zero Sign In button is displayed below the Log In button. You can use the Zero Sign In button to log in without entering a user name and password.

More Information

iLO default credentials

Cookie sharing between browser instances and iLO

When you browse to iLO and log in, one session cookie is shared with all open browser windows that share the iLO URL in the browser address bar. As a consequence, all open browser windows share one user session. Logging out in one window ends the user session in all the open windows. Logging in as a different user in a new window replaces the session in the other windows.

This behavior is typical of browsers. iLO does not support multiple users logged in from two different browser windows in the same browser on the same client.

Shared instances

When the iLO web interface opens another browser window or tab (for example, a help file), this window shares the connection to iLO and the session cookie.

When you are logged into the iLO web interface, and you open a new browser window manually, a duplicate instance of the original browser window opens. If the domain name in the address bar matches the original browser session, the new instance shares a session cookie with the original browser window.

Cookie order

During login, the login page builds a browser session cookie that links the window to the appropriate session in the iLO firmware. The firmware tracks browser logins as separate sessions

Page 24

listed on the Session List page.

For example, when User1 logs in, the web server builds the initial frames view, with User1 listed as the active user, menu items in the navigation pane, and page data in the right pane. When User1 clicks from link to link, only the menu items and page data are updated.

While User1 is logged in, if User2 opens a browser window on the same client and logs in, the second login overwrites the cookie generated in the User1 session. Assuming that User2 is a different user account, a different current frame is built, and a new session is granted. The second session appears on the Session List page as User2.

The second login has effectively orphaned the first session by overriding the cookie generated during the User1 login. This behavior is the same as closing the User1 browser without clicking the Log Out button. The User1 orphaned session is reclaimed when the session timeout expires.

Because the current user frame is not refreshed unless the browser is forced to refresh the entire page, User1 can continue navigating by using the browser window. However, the browser is now operating by using the User2 session cookie settings, even though it might not be readily apparent.

If User1 continues to navigate in this mode (User1 and User2 sharing a process because User2 logged in and reset the session cookie), the following might occur:

• User1 session behaves consistently with the privileges assigned to User2.

• User1 activity keeps User2 session alive, but User1 session can time out unexpectedly.

• Logging out of either window causes both sessions to end. The next activity in the other

window can redirect the user to the login page as if a session timeout or premature timeout occurred.

• Clicking Log Out from the second session (User2) results in the following warning message:

Logging out: unknown page to display before redirecting the user to the login page.

• If User2 logs out and then logs back in as User3, User1 assumes the User3 session.

• If User1 is at login, and User2 is logged in, User1 can alter the URL to redirect to the index

page. It appears as if User1 has accessed iLO without logging in.

These behaviors continue as long as the duplicate windows are open. All activities are attributed to the same user, using the last session cookie set.

Displaying the current session cookie

After logging in, you can force the browser to display the current session cookie by entering the following in the URL navigation bar:

javascript:alert(document.cookie)

The first field visible is the session ID. If the session ID is the same among the different browser

Page 25

windows, these windows are sharing iLO session.

You can force the browser to refresh and reveal your true identity by pressing F5, selecting View >

Refresh, or clicking the Refresh button.

Best practices for preventing cookie-related issues

• Start a new browser for each login by double-clicking the browser icon or shortcut.

• To close an iLO session before you close the browser window, click the Log Out button.

iLO web interface

The iLO web interface groups similar tasks for easy navigation and workflow. The interface is organized with a navigation tree in the left pane. To use the web interface, click an item in the navigation tree, and then click the name of the tab you want to view.

Using the iLO controls

iLO control icons

When you log in to the iLO web interface, the iLO controls are available from any iLO page.

• Power icon—Click this icon to access the Virtual Power Button features.

• UID icon—Click this icon to turn the UID LED on and off.

• Language—Click this icon to select a language for the current iLO web interface session.

Page 26

• To view or modify the language settings, click the language icon, and then select Settings.

• Health icon—Click this icon to view the overall health status for the server fans,

temperature sensors, and other monitored subsystems. For all components except the Agentless Management Service (AMS), click a component to view additional details.

• User icon—Click this icon to do the following: ◦ To log out of the current iLO web interface session, click the user icon, and then select

Logout.

◦ To view the active iLO sessions, click the user icon, and then select Sessions. ◦ To view or modify iLO user accounts, click the user icon, and then select Settings.

• Help icon—Click this icon to view online help for the current iLO web interface page.

• Ellipsis icon—This icon is displayed on the Firmware & OS Software page when the browser window is too small to show the full page. To access the Update Firmware and Upload to iLO Repository options, click this icon. These options are available on all Firmware & OS Software tabs.

iLO navigation pane

iLO has a collapsible navigation pane that is accessible from each page.

• To toggle between showing and hiding the navigation pane, click the icon in the top left corner of the iLO web interface.

• To hide the navigation pane, click the X icon.

• To show the navigation pane, click the icon in the top left corner of the iLO web interface.

• The navigation pane shows a thumbnail of the Remote Console. To start a Remote Console,

click the thumbnail and select a console option from the menu.

• For servers with monitors, click the Remote Console thumbnail in the navigation pane, and then select Wake-Up Monitor to wake up a monitor that is in sleep mode.

Changing the language from the login page

If a language pack is installed, use the language menu on the login screen to select the language for the iLO session. This selection is saved in a browser cookie for future use.

Prerequisites

Procedure

A language pack is installed.

1. Navigate to the iLO Login page.

2. Select a language from the Language menu.

Page 27

Page 28

4. Viewing iLO information and logs

Viewing iLO overview information

Procedure

1. Navigate to the Information page.

The iLO Overview page displays high-level details about the server and the iLO subsystem, as well as links to commonly used features.

System information details

• Server Name—The server name defined by the host operating system. To navigate to the Access Settings page, click the Server Name link.

• Product Name—The product with which this iLO processor is integrated.

• UUID—The universally unique identifier that software uses to identify this host. This value is

assigned when the system is manufactured.

• UUID (Logical)—The system UUID that is presented to host applications. This value is displayed only when set by other software. This value might affect operating system and application licensing. The UUID (Logical) value is set as part of the logical server profile that is assigned to the system. If the logical server profile is removed, the system UUID value reverts from the UUID (Logical) value to the UUID value. If no UUID (Logical) value is set, this item is not displayed.

• Server Serial Number —The server serial number, which is assigned when the system is manufactured. You can change this value by using the ROM-based system utilities during POST.

• Serial Number (Logical)—The system serial number that is presented to host applications. This value is displayed only when set by other software. This value might affect operating system and application licensing. The Serial Number (Logical) value is set as part of the

Page 29

logical server profile that is assigned to the system. If the logical server profile is removed, the serial number value reverts from the Serial Number (Logical) value to the Server Serial Number value. If no Serial Number (Logical) value is set, this item is not displayed.

• Chassis Serial Number—The serial number of the chassis that contains the server node.

• Product ID—This value distinguishes between different systems with similar serial numbers.

The product ID is assigned when the system is manufactured. You can change this value by using the UEFI system utilities during POST.

• System ROM—The version of the active system ROM.

• System ROM Date—The date of the active system ROM.

• Backup System ROM—The version of the backup system ROM. If a system ROM update

fails or is rolled back, the backup system ROM is used. This value is displayed only if the system supports a backup system ROM.

• Integrated Remote Console—Provides links to start the .NET IRC or Java IRC for remote, out-of- band communication with the server console.

For information about the available remote console options, see iLO Integrated Remote Console.

• License Type—The level of licensed iLO firmware functionality.

• iLO Firmware Version—The version and date of the installed iLO firmware. To navigate to

the Firmware Update page, click the iLO Firmware Version link.

• IP Address—The network IP address of the iLO subsystem.

• Link-Local IPv6 Address—The SLAAC link-local address of the iLO subsystem. To navigate

to the Network Summary page, click the Link-Local IPv6 Address link. This value is displayed only for iLO Dedicated Network Port configurations.

• iLO Hostname—The fully qualified network name assigned to the iLO subsystem. By default, the hostname is BMC, followed by the system serial number and the current domain name. This value is used for the network name and must be unique.

System status details

• System Health—The server health indicator. This value summarizes the condition of the monitored subsystems, including overall status and redundancy (ability to handle a failure). Lack of redundancy in any subsystem at startup will not degrade the system health status. To navigate to the Health Summary page, click the System Health link.

• Server Power—The server power state (ON or OFF). To access the Virtual Power Button features, click the Server Power icon.

• UID Indicator—The state of the UID LED. The UID LED helps you identify and locate a server, especially in high-density rack environments. The possible states are UID ON, UID OFF, and UID BLINK.

Page 30

If the iLO Service Port is in use, UID BLINK status includes the Service Port status. The possible values are UID BLINK (Service Port Busy), UID BLINK (Service Port Error), and UID BLINK (Service Port Finished).

To turn the UID LED on or off, click the UID Indicator icon, click the UID control at the top of the iLO web interface window, or use the UID buttons on the server chassis.

When the UID is blinking, and then it stops blinking, the status reverts to the previous value (UID ON or UID OFF). If a new state is selected while the UID LED is blinking, that state takes effect when the UID LED stops blinking.

CAUTION:

The UID LED blinks automatically to indicate that a critical operation is underway on the host, such as Remote Console access or a firmware update. Do not remove power from a server when the UID LED is blinking.

• TPM Status or TM Status—The status of the TPM or TM socket or module. The possible

values are Not Supported, Not Present, or Present-Enabled.

Trusted Platform Modules and Trusted Modules are computer chips that securely store artifacts used to authenticate the platform. These artifacts can include passwords, certificates, or encryption keys. You can also use a TPM or TM to store platform measurements to make sure that the platform remains trustworthy.

On a supported system, ROM decodes the TPM or TM record and passes the configuration status to iLO, the iLO RESTful API, and the CLP.

• Module Type—The TPM or TM type and specification version. The possible values are TPM

1.2, TPM 2.0, TM 1.0, TPM Module 2.0 (Intel PTT), Not Specified, and Not Supported.

This value is displayed when a TPM or TM is present on a server.

• SD-Card Status—The status of the internal SD card. If present, the number of blocks in the SD card is displayed.

• Access Panel Status—The state of the access panel. The possible states are OK (the access panel is installed) and Intrusion (the access panel is open). This value is displayed only on servers that are configured for chassis intrusion detection.

• iLO Date/Time—The internal clock of the iLO subsystem.

Page 31

Managing iLO sessions

Prerequisites

Administer User Accounts privilege

Procedure

1. Navigate to the Information page, and then click the Session List tab. The Session List page displays information about the active iLO sessions.

2. Optional: To disconnect one or more sessions, click the check box next to each session you want to disconnect, and then click Disconnect Session.

Session list details

iLO displays the following details in the Current Session and Session List tables:

• User—The iLO user account name.

• IP—The IP address of the computer used to log in to iLO.

• Login Time—The date and time that the iLO session started.

• Access Time—The date and time that iLO was last active in the session.

• Expires—The date and time that the session will end automatically.

• Source—The session source (for example, Remote Console, web interface, ROM-based

setup utility, iLO RESTful API, or SSH).

• Privilege icons (current user only)—The privileges assigned to the current user account.

Page 32

iLO Event Log

The event log provides a record of significant events recorded by the iLO firmware.

Logged events include major server events such as a server power outage or a server reset, and iLO events such as unauthorized login attempts. Other logged events include successful or unsuccessful browser and Remote Console logins, virtual power and power-cycle events, clearing the log, and some configuration changes, such as creating or deleting a user.

iLO provides secure password encryption, tracking all login attempts and maintaining a record of all login failures. The Authentication Failure Logging setting allows you to configure logging criteria for failed authentications. The event log captures the client name for each logged entry to improve auditing capabilities in DHCP environments, and records the account name, computer name, and IP address.

Viewing the event log

Procedure

1. Click Information in the navigation tree, and then click the iLO Event Log tab.

2. Optional: Use the event log sort, search, and filter features to customize the log view.

3. Optional: To view the event details pane, click an event.

Event log details

• ID—The event ID number. Events are numbered in the order in which they are generated. By

Page 33

default, the event log is sorted by the ID, with the most recent event at the top.

• Severity—The importance of the detected event.

• Description—The description identifies the component and detailed characteristics of the

recorded event. If the iLO firmware is rolled back to an earlier version, the description UNKNOWN EVENT TYPE might be displayed for events recorded by the newer firmware. You can resolve this issue by updating the firmware to the latest supported version, or by clearing the event log.

• Last Update—The date and time when the latest event of this type occurred. This value is based on the date and time stored by the iLO firmware.

If the iLO firmware did not recognize the date and time when an event was updated, [NOT SET] is displayed.

• Count—The number of times this event has occurred (if supported).

In general, important events generate an event log entry each time they occur. They are not consolidated into one event log entry.

When less important events are repeated, they are consolidated into one event log entry, and the Count and Last Update values are updated. Each event type has a specific time interval that determines whether repeated events are consolidated or a new event is logged.

• Category—The event category.

Event log icons

iLO uses the following icons to indicate event severity:

• Critical—The event indicates a service loss or imminent service loss. Immediate attention is needed.

• Caution—The event is significant but does not indicate performance degradation.

• Informational—The event provides background information.

• Unknown—The event severity could not be determined.

Event log event pane details

• Initial Update—The date and time when the first event of this type occurred. This value is based on the date and time stored by the iLO firmware.

If iLO did not recognize the date and time when the event was first created, [NOT SET] is displayed.

• Event Code—A unique identifier for an event within a given event class displayed in hexadecimal format.

Page 34

Customizing the event log view

Sorting events

Click a column heading to sort the event log table by that column.

To change the display to ascending or descending order, click the column heading again.

Event filters

To access the event log filters, click .

• To filter by severity, select a severity level from the Severity menu.

• To filter by event category, select a value in the Category menu.

• To change the displayed date and time for events, select a value in the Time menu. Choose

from the following:

◦ Show Default—Display UTC time. ◦ Show Local Time—Display the iLO web interface client time. ◦ Show ISO Time—Display UTC time in ISO 8601 format.

In iLO 5 Firmware Version 1.10 Jun 07 2017, when SNTP setting is not configured or when it is not used in an environment where can be synchronized with the time server, the following times are displayed.

 If Show Default and Show ISO Time are selected, the following is displayed.

System time(UTC±Time Zone) displayed in BIOS/Platform Configuration(RBSU)

 If Show Local Time is selected, the following is displayed.

Added to the System time(UTC±Time Zone) displayed in BIOS/Platform Configuration(RBSU) and the time zone of the environment of the client connected to iLO.

In iLO 5 Firmware Version 1.15 Aug 17 2017, when SNTP setting is not configured and Time Format on BIOS/Platform Configuration(RBSU) is Local Time, the following times are displayed.

 If Show Default and Show ISO Time are selected, the following is displayed.

System time(UTC±Time Zone) displayed in BIOS/Platform Configuration(RBSU)

 If Show Local Time is selected, the following is displayed.

Added to the System time(UTC±Time Zone) displayed in BIOS/Platform Configuration(RBSU) and the time zone of the environment of the client connected to iLO.

• To filter by the last update date, select a value in the Last Update menu.

Based on the time displayed in Show Default, the filter will be applied.

• To set the filters back to the default values, click Reset filters.

Page 35

Searching for an event

To search for events based on dates, event ID, or description text, click , and then enter text in the search box.

Saving the event log to a CSV file

Use a supported browser to export the event log to a CSV file.

Procedure

1. Click Information in the navigation tree, and then click the iLO Event Log tab.

2. Click the CSV icon

3. In the CSV Output window, click Save, and then follow the browser prompts to save or open

the file.

Clearing the event log

Prerequisites

Configure iLO Settings privilege

Procedure

1. Click Information in the navigation tree, and then click the iLO Event Log tab.

2. Click .

3. When prompted to confirm the request, click OK.

Page 36

The event log is cleared of all previously logged information and an event is recorded in the log.

Page 37

Integrated Management Log

The IML provides a record of historical events that have occurred on the server. Events are generated by the system ROM and by services such as the iLO driver. Logged events include all server-specific events recorded by the iLO driver, including operating system information and ROM-based POST codes.

Entries in the IML can help you diagnose issues or identify potential issues. Preventative action might help to avoid disruption of service.

iLO manages the IML, which you can access through a supported browser, even when the server is off. The ability to view the log when the server is off can be helpful when troubleshooting remote host server issues.

Examples of the types of information recorded in the IML follow:

• Fan inserted

• Fan removed

• Fan failure

• Fan degraded

• Fan repaired

• Fan redundancy lost

• Fans redundant

• Power supply inserted

• Power supply removed

• Power supply failure

• Power supplies redundancy lost

• Power supplies redundant

• Temperature over threshold

• Temperature normal

• Automatic shutdown started

• Automatic shutdown canceled

• Drive failure

Viewing the IML

Procedure

1. Click Information in the navigation tree, and then click the Integrated Management Log

tab.

2. Optional: Use the IML sort, search, and filter features to customize the log view.

3. Optional: To view the event details pane, click an event.

Page 38

IML details

• The first column on the left side of the web interface displays an active check box next to

each event with Critical or Caution status. Use this check box to select an event to mark as repaired.

• ID—The event ID number. Events are numbered in the order in which they are generated.

By default, the IML is sorted by the ID, with the most recent event at the top. A factory reset will reset the counter.

• Severity—The importance of the detected event.

• Class—Identifies the type of event that occurred, for example, network, maintenance, or

system revision.

• Description—The description identifies the component and detailed characteristics of the

recorded event.

If the iLO firmware is rolled back, the description UNKNOWN EVENT TYPE might be displayed for events recorded by the newer firmware. You can resolve this issue by updating the firmware to the latest supported version, or by clearing the log.

• Last Update—The date and time when the latest event of this type occurred. This value is

based on the date and time stored by the iLO firmware.

If iLO did not recognize the date and time when an event was updated, [NOT SET] is displayed.

• Count—The number of times this event has occurred (if supported).

Page 39

• Category—The event category. For example, Hardware Failure, Firmware Failure, Power, or

IML icons

iLO uses the following icons to indicate IML event severity:

• Critical—The event indicates a service loss or an imminent service loss. Immediate attention

• Caution—The event is significant but does not indicate performance degradation.

• Informational—The event provides background information.

In general, important events generate an IML entry each time they occur. They are not consolidated into one event log entry.

When less important events are repeated, they are consolidated into one IML entry, and the Count and Last Update values are updated. Each event type has a specific time interval that determines whether repeated events are consolidated or a new event is logged.

Administration.

is needed.

• Repaired—An event has undergone corrective action.

• Unknown—The event severity could not be determined.

IML event pane details

• Initial Update—The date and time when the first event of this type occurred. This value is

based on the date and time stored by the iLO firmware.

If iLO did not recognize the date and time when the event was first created, [NOT SET] is displayed.

• Event Code—A unique identifier for an event within a given event class (displayed in

hexadecimal format).

• Recommended Action— A short description of the recommended action for a failure

condition.

Customizing the IML view

Sorting events

Click a column heading to sort the IML table by that column.

To change the display to ascending or descending order, click the arrow next to the column heading.

Event filters

To access the event log filters, click .

• To filter by severity, select a severity level from the Severity list.

Page 40

• To filter by class, select a class from the Class list.

• To filter by event category, select a value in the Category list.