Adding servers that are already running an operating system

Servers currently running a production operating system can be added to IC server provisioning without rebooting by adding the HP Server Automation (SA) agent to the target server, and then registering the server’s iLO.

To add the HP Server Automation Agent to a managed server:

  1. Determine the SA agent filename from http://xxx.xxx.xxx.xxx:8081 where xxx.xxx.xxx.xxx is the Deployment IP address or DNS name of the IC server provisioning virtual appliance. Look for the files with .current extension. There are different agent files depending on the operating system version and architecture type.

    The SA Agent files are listed below:

    Operating System SA Agent to download
    Windows 2008 x64 opsware-agent-NT-6.0-X64.current
    Windows 2008 R2 x64 opsware-agent-NT-6.1-X64.current
    Windows 2012 x64, Windows 2012 R2 x64 opsware-agent-NT-6.2-X64.current

    opsware-agent-NT-6.3–64.current

    Red Hat EL 5.x opsware-agent-LINUX-5SERVER-X86_64.current
    Red Hat EL 6.x opsware-agent-LINUX-6SERVER-X86_64.current
    SLES 11, SLES 11 SPx opsware-agent-LINUX-SLES-11-X86_64.current

    [NOTE: ]

    NOTE: There is no SA agent that runs on VMware ESXi.


  2. Download the SA agent using the exact filename in the URL without the .current extension, http://xxx.xxx.xxx.xxx:8081/<filename> where <filename> is name of the SA agent file.


    [IMPORTANT: ]

    IMPORTANT: Do not download the file by listing all the agent files and then using the right-click Save link to save it. The file will contain only HTML content and not work with IC server provisioning.


  3. Once a Windows agent file is downloaded, rename the filename with a .exe extension. For Linux, the filename without an extension is appropriate.

  4. Install the SA agent on the target server with the parameters, –s --opsw_gw_list coreip:3001 where coreip is the IP address of the IC server provisioning virtual appliance. Be sure to use the Deployment IP address, not the Appliance IP address.

  5. Verify the target server shows up in IC server provisioning.

  6. Before an OS Build Plan can be run on this target server, the server’s iLO must also be registered with IC server provisioning. This can be done by either of the following ways:

    1. You can add each target server’s iLO information manually. From the IC server provisioning Servers screen, choose ActionsAdd Servers, enter the iLO IP address and credentials of a target server, and be sure to check the box that says Do not boot to maintenance. Choose Add to initiate the iLO registration or Add+ to enter more IP addresses.

    2. You can add each server’s iLO information using the programmatic REST API (see the HP Insight Control Server Provisioning Administrator Guide Advanced Topics section). Be sure to use the option that does not boot the server into maintenance.

  7. You can verify that the iLO has been properly registered with the server by going to the Servers screen and seeing if the iLO IP address is listed there.