Install the SA Agent on a VM

To gain the most benefit from SA, you should always install the SA Agent on all managed servers, both VMs and physical servers.

If you created the VM from an agent-managed server or an agent-managed VM template, the SA Agent is already installed on the VM. You only need to install the SA Agent if you created a VM without an SA Agent.

To determine if the SA Agent is running on a VM (or any server), locate the VM or server in the SA Client and hover your mouse pointer over the icon for the server. The SA Client will display the agent status of the server, either agentless or agent managed. You can also select or open the server in the SA Client, and select the Summary view. This view gives the status of the SA Agent. To ensure connectivity, you can run a Communication test by selecting the Actions menu, then selecting Run > Communication Test.

For more information about the SA Agent, agent-managed servers, and installing the agent on multiple servers, see the SA 10.51 Use section

Prerequisites for OpenStack

The OpenStack instance must have a user name and password set up on the VM. Enable SSH on the server to allow remote logins.

Requirements for OpenStack Instance

An OpenStack instance must have:

  • A working username/password login.
  • A routable IP (typically a floating IP) that the SA core can reach.

Installing the SA Agent on the VM

  1. In the SA Client, select the Virtualization tab to display your virtualization inventory.
  2. Navigate to the VM on which you want to install the SA Agent.
  3. Select the desired VM and right-click or select the Actions menu. Select Install SA Agent to display the Install SA Agent window.
  4. Select the IP address for the VM from the drop-down list. Select the IP the SA core can reach.
  5. Select Scan. SA attempts to establish communications with the VM and determines the best protocol to use to install the SA Agent. If the scan fails, check the power status and network settings of the VM.
  6. Select a network protocol to connect to the VM from the drop-down list.

    In most cases, you should choose Select Automatically to allow SA to select an appropriate protocol for the VM.

  7. Enter a user name and password to use for logging into the VM.

    For Windows-based systems, specify the Windows administrator user name and password.

    For UNIX systems, specify a root user and password.

    • If you are unable to deploy the agent to a UNIX server by logging in as root, the system you are deploying to may be configured to disallow direct root logins. In such cases, SA allows you to log in as a non-root user and escalates your privileges using either the su or sudo command.

      To deploy agents as non-root users:

      • Enter the non-root user name in the Username field to log into the server.
      • Enter the non-root password in the Password field.
      • Select the Become root (UNIX) checkbox. Select “Supply root password” and enter the password or select “Use sudo.” If you use sudo, the non-root account must be able to run any command as root.

    In OpenStack, you must enable “Security Group Rule” on a project to allow required port 1002 through. If this is not open, installing an agent will not work.

  8. Select one of the following deployment actions:
    • Verify installation prerequisites.

      Checks for sufficient disk space for agent installation on the VM, verifies that no other applications are using port 1002, and verifies that ports to the SA gateway are accessible.

    • Verify prerequisites and copy agent installer to servers.

      Copies the agent installer to the VM.

    • Verify prerequisites, copy installer, and install agent.

      Installs the SA Agent on the VM.

  9. Optionally specify the agent installer options and advanced options to control the way the agent is installed on a server. See the SA 10.51 Use section for more information.
  10. Select OK to perform your selected actions.
  11. After the deployment action is completed, the SA Client displays the results and updates the status icons for the VM.

For more information on agent installation status and troubleshooting, see Use section.