Piszki Lab | EN

My case study in the clouds…

hyperic

Integrating VMware Hyperic 5.8.2 and vCenter 5.5 (via Infrastructure Navigator 5.8)

| 7 Comments

VMware Hyperic is the perfect complement to a whole range of applications for vSphere environment monitoring. However, compared to VMware Operations Manager, LogInsight and Infrastructure Navigator, VMware Hyperic is more than just another probe servant to collect data (which does not change the fact that highly accurate probe). With it, you can load up to tcServer or Apache Tomcat application and run it. You can automatically restart a application service  that stopped working, you can start emergency plans containing a range of activities carried out step by step in case of emergency. In this article I will describe one of the underrated function of which is to integrate the vSphere Web Client with VMware Hyperic. With this integration, it is possible to install the Hyperic agents from the Web Client and monitoring their status!

hy0

 

VMware Hyperic 5.8.2 is currently the latest release, the installation files can be downloaded in any configuration. However, I recommend the appliance containing (vCenter-Hyperic-5.8.2-EE.ova), a machine with Hyperic (and agents) and additional machine with vPostgres. We can of course install the Hyperic Server on Windows and PostgreSQL database anywhere and everything will work. But how many times I’ve written on this blog, and yet not once write, VMware turns towards to Linux, and supply products as ready-configured appliance. Where this is already possible, let’s benefit from this solution. In addition to the Hyperic server, we need to have installed and configured VMware Infrastructure Navigator 5.8. VIN is a very nice service, analyze our environment and shows graphically the relationship between the individual applications. Graphic form can be used in the creation of documentation, but it is also possible to export the tables as the CSV files .

hy7

Why do we need to install the Infrastructure Navigator? In this model, VIN provide appropriate plug-in to the vSphere Web Client, and is a repository of Hyperic agents (VIN 5.8.2 includes angets in 5.8.0 version). It also provides appropriate cmdlets in PowerShell using the Agent is installed and configured on the target machine. The process of integration of the entire solution boils down to create the desired profile in the vSphere Web Client (section Administration -> Agent Management):

hy8

Same profile as follows:

hy9

All settings are clear and directly translate into the parameters that will be included in the agent.properties file. Keep in mind that this form of installing agents should use the force agent.setup.acceptUnverifiedCertificate = yes, meaning it is not possible to adopt a trusted SSL certificates on the side of the Agent (User defined keystore ). In 99% of the communities will not be a problem (I’ve never used the trusted certificates on the side of the agent). Self install the agent is very simple (see Manage -> Hyperic Agents for the entire environment or vApp):

hy3

Icon “Install Hyperic Agent on the selected VMs” (it is possible to deploy the agents on multiple machines). When the installation and configuration of Agent coming to an end, we see a view of the following:

hy6

The new machine appears in the vCenter Hyperic (see Auto-Discovery):

hy4

And that’s basically the end to close the circle of integrated components, I suggest you perform the operation even integrate Hyperic with vCenter Operations Manager and the Hyperic with vCenter (HQ Server Settings -> vCenter Settings):

hy2

This allows Hyperic knows that he has to deal with virtual machines. What is the advantage as to the integration? Basic is that it removes the need to manually install the agents on the machines (the process is quite tiring). Possible becomes a mass installation of agents. In complex environments where vCenter Hypric is extensively used, the ability to quickly check of the agent status is not irrelevant.

ha18

This is useful also if we are going to use vSphere App HA.

 

Was this information is helpful? Tell me, please leave a comment!

Source

Rate this article:
[Total: 1    Average: 5/5]

Author: Piotr Pisz

Computer always, since I got a Commodore 64 at the end of primary school, through his beloved Amiga and Linux infinite number of consoles, until today, fully virtual day. Since 2001, Unix/Linux Systems Administrator, for seven years a faithful companion and protector of Solaris system, until his sad end. In the year 2011 came in the depths of virtualization, then smoothly ascended into the clouds and continues there today. Professionally working as Systems Architect in the Polish Security Printing Works.

7 Comments

  1. Hi There,

    I have a problem with my Hyperic Version 5.8.2. i have recent update my TC instance from 3.1.0 to 3.1.1. But Hyperic console shows the current version as 3.1.0 instead of 3.1.1. please help me. my email is dileeptikkisetty@gmail.com.
    Thanks
    Dileep

    • Hi, Have You tried to remove the tc server from agent configuration and add it again (or manual run auto discovery)? For me it does not matter which version shows hyperic, Important to handle it ;)
      Regards!

  2. Hey,

    I have a vC environment with abt 50 VMs. I had a Hyperic setup and i used the above method to install agents on most of them.
    Now i hav scrapped the hyperic and reinstalled it (with same IP and credentials). The problem now is the vC shows the VMs have an agent installed but it never appears in the Hyperic Dashboard. It would be very helpful if you could point me in the right direction.

    • Hi Rishab,

      This is normal, you lost auth tokens between agent and Hyperic server. You need to run “bin/hq-agent.sh (bat) setup” on any agent and say yes to this question: Would you like to re-setup auth tokens?

      Regards,
      Piotr

      • Hi,
        Thanks for the reply. Is there a way to automate the process, or I’ll have to RDP to all windows machine and do it and putty to all linux VMs and do it?
        Thanks for the reply.

        -R

Leave a Reply

Required fields are marked *.


.

Enjoyed the post? Support Piszki Lab | EN, click on the AD! :-)

.