That will be a tough one since it was trial and error to get this to work and I went through a ton of emailing back and forth and webex sessions to get it to work and I dont remember the exact thing that got it working.
I installed the agent on a Windows 7 VM since its not recommended to install it on the vCenter server. The tricky part was getting the agent to work and stay running. The agent.properties file has to be just right and you need an SSL certificate for version 5 at least. I didnt set that part up so I cant help you there and it sounds like that may be what you need help on.
Here are some of the notes that I was given to do the setup. Hopefully it makes sense.
Couple key notes - you need to pre-configure the agent via its properties file:
When doing remote monitoring of vSphere, which is recommended, the adding of the vSphere resource is done manually. So no autodiscovery of vSphere/vCenter.
There is a dependency on having a properly configured agent.properties file. (see below)
Also a more recent dependency in newer versions of Hyperic on having the SSL certificates in place - see doc for this one.
http://pubs.vmware.com/vfabric51/topic/com.vmware.vfabric.hyperic.4.6/vSphere.html
http://pubs.vmware.com/vfabric5/index.jsp?topic=/com.vmware.vfabric.hyperic.4.6/Configure_SSL_Option...
I suggest:
1 - Stop the agent
2 - Wipe the agent's /data directory clean
3 - Remove the platform (that the agent sits on) from the Hyperic inventory
...This will clean your slate and allow you to start fresh.
Then proceed to get the SSL cert in place, and configure the agent.properties file as specified below.
Only then, restart the agent. Allow it to report into Hyperic and add a new platform.
Then manually add the vSphere resource as defined below (Tools -> new server)
==
Port 443 needs to be network routable for a remote agent to connect to it.
To setup the agent on another platform:
- Choose a platform to do the remote monitoring from
- populate agent.properties, see below
- From the 'tools' menu for the platform, click on create new server
- Choose 'vcenter' as the resource type
- In the URL stick in the IP for the control center server: https://<ip>/sdk
- Credentials - save yourself time and verify that you can log in from the vsphere client with the credentials they give you
agent.setup.camIP=172.161.0.11
agent.setup.camPort=7080
agent.setup.camSSLPort=7443
agent.setup.camSecure=yes
agent.setup.camLogin=hqadmin
agent.setup.camPword=hqadmin
agent.setup.agentIP=172.16.0.21
agent.setup.agentPort=2144
agent.setup.resetupTokens=no
##
## enables unidirectional communications between HQ Agent
## and HQ Server in HQ Enterprise Edition
##
agent.setup.unidirectional=no
In the above block, agent.setup.camIP is the IP address of the Hyperic server.
The agent properties must be setup without using the *default* macros. The reason being that the vsphere plugin will check with this file to find the HQ Servers IP, credentials to log in with, along with the IP/port of the box its sitting on. As part of its auto discovery process, the vsphere plugin will make webservice calls through hqapi to the hq server to handle resource creation for the ESX hosts/vms that it discovers.
Edit the agent.properties file to contain the needed info *before* starting the agent.
If things dont work for whatever reason.
- verify again that the credentials you were given work
- verify that you have network connectivity to the control center server, do not try to telnet to the port as it does not respond for some reason, instead you can check the logs to verify that the url is accessible. Ping check for network routing
- Enable debug logging on the agent
- Forward debug logs for agent + last 10,000 lines from the HQ server ( tail -10000 server.log) tar'ed and gziped, the logs for the most part will generally help you determine where the issue lies.
After creating the vsphere resource, the vsphere hqu plugin should show up, after configuring the resource with credentials/sdk api, you should see resources pop up into the recently added portlet within a minute.
