HP Integrity Superdome 2 8/16 HP Integrity Superdome 2 Onboard Administrator U - Page 14

Onboard Administrator requires the user 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. The Onboard Administrator contacts the defined LDAP server to verify the user credentials. Two-factor Authentication enables even tighter security for the user management session to Onboard Administrator. The default Administrator account from the Monarch OA is synchronized to the other OAs in the complex. Use the default credentials from the Monarch OA to access all OAs. Rather than requiring separate logins to multiple resources (once to each enclosure or once to every server management processor or both), Onboard Administrator enables single-point access. Thus, 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 Superdome 2 components in the entire complex. For example, an IT administrator can automatically propagate management commands, such as changing the enclosure power mode, throughout the complex. Running Onboard Administrator for the first time Setting up a Superdome 2 enclosure using the Onboard Administrator is simplified by using the Insight Display setup process, followed by the use of the Onboard Administrator GUI First Time Setup Wizard or Onboard Administrator CLI to complete the reset of the enclosure settings. The Onboard Administrator modules and many interconnect modules default to DHCP for the management IP address. If the user has DHCP and connects the Onboard Administrator management port to the DHCP server, then the Onboard Administrator modules and interconnect modules supporting and configured to use the Onboard Administrator internal management network automatically get DHCP addresses from the user DHCP server. If you do not have a DHCP server for assigning IP addresses to management processors, then you must configure each Onboard Administrator with a static IP address using the Insight Display, then log in to the Onboard Administrator GUI and use the First Time Setup Wizard or log in to the Onboard Administrator CLI and configure and enable EBIPA for device bays and interconnect bays. Enabling EBIPA for a bay enables that server or interconnect module to be replaced and the new module automatically gets the previously configured IP address for that bay. See "Enclosure Bay IP Addressing screen" (page 91) for more information on EBIPA. The initial credentials to log on to a new Onboard Administrator module are printed on a label on each module. The user is Administrator and the password is unique to each module. This password must be captured by the installer and communicated to the remote Administrator for the first remote logon to the Onboard Administrator GUI or Onboard Administrator CLI. The enclosure settings can be configured manually or uploaded from a configuration script or file. The web GUI offers a First Time Setup Wizard. The CLI can be accessed from the Onboard Administrator serial port, Ethernet management port, service port, or by using the Enclosure KVM - Onboard Administrator CLI button. An alternative to manual configuration is to upload a enclosure configuration file to the active Onboard Administrator using either the GUI or CLI with an HTTP, FTP or TFTP network location for the configuration file, or use the GUI, CLI or Insight Display to upload a configuration file from a USB key drive plugged into the active Onboard Administrator USB port. HP recommends creating an enclosure configuration file to use the GUI, CLI, or Insight Display USB Menu to save the existing configuration to a file. The saved configuration file is a set of CLI text commands for each configuration item. The Onboard Administrator does not save user passwords when it saves a configuration file. The user can edit the configuration file and insert the password commands for each user account-or use the Administrator local account to individually update all user passwords after restoring a previously saved enclosure configuration file. If the enclosure contains redundant Onboard Administrator modules, the remaining Onboard Administrator updates the new Onboard Administrator with all the settings. 14 Introduction