Setting up Onboard Administrator using the CLI

  1. Connect to the Onboard Administrator CLI using the serial port, management port, service port, or c3000 KVM Module option.
  2. Log in to the Onboard Administrator with the “Administrator” user account and the OA dogtag password.
  3. Set Onboard Administrator name: “SET OA NAME 1 <name>”.
  4. If a redundant Onboard Administrator is present, set the name to: “SET OA NAME 2 <name>”.
  5. Configure Onboard Administrator IP address
    1. Select whether to use either the OA1/OA2 IP address or Enclosure IP address.
    2. Configure OA1 IP address as static or DHCP. Example for static: “SET IPCONFIG STATIC 1 <ipaddress><netmask>”
  6. If a redundant Onboard Administrator is present: “SET IPCONFIG STATIC 2 <ip address> <netmask>”.
  7. Set Onboard Administrator gateway: “SET OA GATEWAY 1 <ip address>.
  8. If a redundant Onboard Administrator is present: “SET OA GATEWAY 2 <ip address>.
  9. Set the iLO IP address: “SET EBIPA SERVER <ip address> <netmask>. Allocate each IP address needed (up to 32) consecutive static IP addresses.
  10. If a gateway exists on the management network, set the iLO gateway to the IP address: SET EBIPA SERVER GATEWAY <ip address>.
  11. Start EBIPA FOR iLO: “ENABLE EBIPA SERVER”.
  12. Complete the remainder of the settings as required. The CLI User Guide indicates the enclosure defaults for each setting.

Configuring c-Class iLO IP addresses

Each c-Class iLO factory default configuration enables DHCP network settings. To use the iLO with a DHCP network, connect the Onboard Administrator management port to a network with a DHCP server and Onboard Administrator and all iLO management processors and supporting interconnect modules such as Virtual Connect obtain IP addresses from the DHCP server.

To configure each iLO for static IP addresses there are five alternatives. Use Onboard Administrator to setup an IP address for each iLO using EBIPA. This enables iLO to be addressed using TCP/IP so that the network settings can be reconfigured. The client PC must be configured to access these iLO IP addresses temporarily for Alternatives 2-4.

Alternative 1 using EBIPA:

Configuring each iLO with an IP address using EBIPA provides a fixed network configuration including IP address, netmask and gateway that is based on the enclosure bay where the server is installed. The new iLO obtains the IP address for that bay without further configuration needed.

Alternative 2 using the OA GUI:

Log in to the OA GUI with an account having administrator privilege and bay permissions to the corresponding iLO. Select the iLO link on the desired server to single-sign-on to the iLO web GUI. Select Administration | Network Settings. Change iLO to DHCP disabled and enter the desired IP address, subnet mask and gateway. Select Apply and the iLO that has been configured for a static IP address. Repeat these steps for each iLO. When all iLOs in the enclosure have static IP addresses configured, turn off the EBIPA setting for the servers.

Alternative 3 using the OA CLI:

Login to the OA CLI with an account having administrator privilege and bay permissions to the corresponding iLO. Perform the connect server X command where X is the bay number containing the iLO to be configured. Use iLO SMASH/CLP interface to set the iLO to the desired IP address subnet mask and gateway. This resets the iLO network settings to the configured values. Repeat these steps for each iLO. When all iLOs in the enclosure have static IP addresses configured, turn off the EBIPA setting for the servers.

Alternative 4 using iLO RIBCL scripts:

Create a unique RIBCL xml script to configure the iLO network settings to the desired values for each iLO. Copy these scripts to an HTTP, FTP, or TFTP server that can be accessed by the Onboard Administrator.

Login to the OA CLI with an account having administrator privilege and bay permissions to the corresponding iLO. Perform the hponcfg X Y command where X is the bay number containing the iLO to be configured and Y is the HTTP, FTP, or TFTP server network path to the script file (example hponcfg 2 http://10.128.126.204/Mod_Network_Settings.xml). Using Onboard Administrator to perform the hponcfg command uses single-sign-on to the selected iLO, instead of configuring the RIBCL script with the unique default iLO username/password. Application of the RIBCL script resets the iLO network settings to the configured values. Repeat these steps for each iLO. When all iLOs in the enclosure have static IP addresses configured, turn off the EBIPA setting for the servers.

Alternative 5 using the iLO BIOS ROM during server POST:

Connect each server to a KVM. Reboot each server and stop POST during iLO ROM initialization. Change the iLO network configuration and manually enter the IP address, netmask and gateway. Reboot the server. Repeat for each iLO.

Setting up Onboard Administrator using the CLI