HP BladeSystem Onboard Administrator User Guide - HP Business ...

Onboard Administrator requires you to log in to the web GUI or CLI with an account and password. The
account can be a local account where the password is stored on Onboard Administrator or an LDAP
account, where Onboard Administrator contacts the defined LDAP server to check the user credentials.
Two-factor authentication enables even tighter security for the user management session to Onboard
Administrator.
Rather than requiring separate logins to multiple resources (once to each enclosure, once to every server
management processor, or both), Onboard Administrator enables single point access. In this way, the
administrator can use single sign-on to log in to a single Onboard Administrator and use the web GUI to
graphically view and manage the HP BladeSystem c-Class components in up to four linked enclosures. For
example, an IT administrator can automatically propagate management commands, such as changing the
enclosure power mode, across all the linked enclosures.
Login security
Onboard Administrator provides several login security features. No penalty is imposed after an initial failed
login attempt. With all subsequent failed attempts, Onboard Administrator imposes a 10- to 20-second
delay. An information page appears during each delay. This action continues until a valid login is
completed. This feature assists in defending against possible dictionary attacks against the browser login
port.
Onboard Administrator saves a detailed log entry for all failed login attempts.
Running Onboard Administrator for the first time
Setting up a c-Class enclosure using the Onboard Administrator is simplified by using the Insight Display first
time installation wizard, followed by use of the Onboard Administrator GUI First Time Wizard or Onboard
Administrator CLI to complete the reset of the enclosure settings.
When operating in FIPS Mode, configure FIPS Mode before performing any other enclosure or Onboard
Administrator configuration, including configuration of the Virtual Connect or First Time Setup Wizard.
Enabling FIPS Mode on an Onboard Administrator module or redundant pair of modules forces the Onboard
Administrator modules to be reset to factory defaults. After configuring FIPS Mode, perform the configuration
steps in this section.
The Onboard Administrator modules, server blade iLO management processors and many interconnect
modules default to DHCP for their management IP address. If the user has DHCP and connects the Onboard
Administrator management port to the DHCP server, then the Onboard Administrator modules, all iLO, and
interconnect modules supporting and configured to use the Onboard Administrator internal management
network will all automatically obtain DHCP addresses from the user DHCP server.
If you do not have a DHCP server for assigning IP addresses to management processors, you must configure
each Onboard Administrator IP address and then all the individual device and interconnect module
management IP addresses by using one of the following methods:
• Recommended Practice - configure each Onboard Administrator with a static IP address using the
Insight Display. Then log into the Onboard Administrator GUI and use the First Time Setup Wizard or
log into the Onboard Administrator CLI and configure and enable Enclosure Bay IP Addresses (EBIPA)
for Device Bays and Interconnect Bays. Enabling EBIPA for a bay will allow that server or interconnect
module to be replaced and the new module will automatically obtain the previously configured IP
address for that bay.
• Alternatively configure each device and interconnect module for static IP manually. For ProLiant server
blades, you must connect to each server blade from SUV port (using the SUV cable included with each
enclosure) and configure the iLO IP address manually during POST by pressing F8 to access the iLO
Introduction 14