posted

0 Comments

Time for Part 3, we are almost done! Here are links if you are looking for Part 1 or Part 2

Deploying the Hyperic Agent(s)

You only need to do this on VMs with applications you want to protect. For additional guidance on these steps and details for how to install multiple agents simultaneously see: Getting Started with vFabric Hyperic 5.7 starting at pages 53 & 25

Prerequisites

  • Ensure that both the Hyperic server and the VM are using the same time source or have their time synchronized in some other way
  • Make sure to either turn off the local firewall or configure it to allow inbound & outbound Hyperic Agent traffic

Windows:

  • Create a directory for the vFabric Hyperic Agent
  • Unpack the archive into the agent directory
  • Open a command shell
  • Change directory to <Path to Agent Folder>/bin and type:
  • hq-agent.bat install
  • hq-agent.bat start

Non-windows/Linux:

  • Create a directory for the vFabric Hyperic Agent
  • Unpack the tarball into the agent directory. 
Note: Starting the agent will run it as a daemon process
  • Open a command shell
  • Change directory to <Path to Agent Folder>/bin and type:
  • hq-agent.sh start

Now step through the agent configuration steps – this is the same for both Windows and Linux. For additional detail see Getting Started with vFabric Hyperic 5.7 page 64

  • Should Agent communications to HQ be unidirectional [default=no]? – select “no”
  • What is the HQ server IP address?
 – enter the Hyperic sever IP address
  • Should Agent communications to HQ always be secure [default=yes]? – select “no” unless your environment requires otherwise. If secure is required see Getting Started with vFabric Hyperic 5.7 page 64 for details
  • What is the HQ server port [default=7080] – leave as default unless you changed this when configuring the Hyperic server
  • What is your HQ login [default=hqadmin]?
 – by default, the vFabric Hyperic Server is initially configured with an administrative account with username hqadmin. Unless you have configured a different vFabric Hyperic user account for agent-server communications, accept the default
  • What is your HQ password?
 – Enter the password for the username you supplied at the previous prompt
  • What IP should HQ use to contact the agent [default=x.x.x.x]? – The prompt will show the first IP address the agent detects on the host. If there is another IP address on the host you prefer to use, enter it. If there is a firewall blocking traffic from the server to the agent, enter the IP address of the firewall, and configure the firewall to forward traffic intended for the vFabric Hyperic Agent to the listen address of the agent host
  • What port should HQ use to contact the agent [default=2144]?
 – Enter the agent port the vFabric Hyperic Server should use when it initiates contact with the agent. Specify the port that the agent binds to at startup, which by default is 2144. If there is a firewall blocking traffic from the server to the agent, configure the device to forward traffic on TCP port 2144 to the vFabric Hyperic Agent
  • After you respond to the last prompt the agent initiates a connection to the server and the server verifies that it can communicate with the agent
Hyperic Windows Agent Install

Next we will add the VM to the Hyperic Server

  • Log into Hyperic and verify that the Hyperic Agent is discovered by Hyperic Server (it will show up in the Auto-Discovery” section of the dashboard page).
Hyperic Agent Install - AutoDiscovery
  • Select the VM, ensure all resources are checked and click “Add to Inventory”

Final steps

  • Verify that the VM and its resources show up in the vSphere Web Client under Monitor>Applications Availability
Application Services Availability
  • You’re now all ready to create policies, assign them to VMs and start protecting your applications. For details see the vSphere App HA Users Guide

Note: Before you deploy App HA in production test to ensure that everything related to the agents and the ability of the Hyperic server to monitor and restart services is working correctly. A good way to do this is from the Hyperic Server verify that you can successfully stop and start services on VMs with the agent installed

Resources