The System plug-in is updated to include system counters related to memory and swap.

The WebSphere plug-in is updated to prevent override of JRE files.

The MSSQL plug-in is updated to add mopre counters that are collected directly from the database. It also now requires credentials for collection of metrics.

The Hyper-V plug-in is updated to support Windows 2012R2.

The IBM DB2 plug-in is updated to support version 10.

The Oracle DB plug-in is updated to support version 12.

The following new Plug-ins have been added:

OpenStack

vCenter Orchestrator

vRealize Automation Appliance

vRealize Automation AppServices

vRealize Automation IaaS

vRealize Business Standard

vSphere SSO

Documentation for the vRealize Hyperic 5.8.4 Release

The documentation for vRealize Hyperic 5.8.4 is an update of the vCenter Hyperic 5.8 documentation center, incorporating the product name change.

Issues Addressed in vRealize Hyperic 5.8.4

When you upgrade the Hyperic server from vCenter Hyperic 5.8.3 to vRealize Hyperic 5.8.4 on a Windows OS, after the upgrade has been completed successfully, you must run setup.bat -remove and setup.bat -install to complete the installation process.

This issue was relevant when you were using a new installation of vRealize Hyperic 5.8.3, not an upgrade from an earlier version. It has now been addressed. If you were using vRealize Operations Manager with vRealize Hyperic Management Pack, a restart of either the vRealize Operations Manager or vRealize Hyperic Management Pack caused duplicate vRealize Hyperic objects to be created in vCenter Operations Manager. This situation occured because each time that a get GUID query was called, a different GUID was returned, which led to creation of the duplicate.

The long startup time for the vRealize Hyperic server has been improved.

The dependencies between the email server and alert notifications have been removed. Alert notifications are still triggered.

The regression error in which the log tracking configuration was corrupt when a platform was created using HQAPI has been addressed.

The regression error in which an HQAPI resource could not be moved between platforms has been addressed.

It is now possible to configure multiple SNMP v3 platforms on a single agent.

The issue in which a call for HQAPI alertdefinition list by ID returns an AlertDefinitionResponse object and other alertdefinition list calls return an AlertDefinitionsResponse object has been addressed. The new alertdefinition: idAsList API call returns alert in a list structure.

In the vApp installation for medium-sized environments, the memory has now been increased from 4GB to 5GB, to support the DRS environment.

SSL v3 has been removed from the vRealize Hyperic server to eliminate the POODLE vulnerability.

The issues in which you were unable to create alerts for JBoss Datasource has been addressed.

Known Issues and Limitations in vRealize Hyperic 5.8.4

The following known issues and limitations affect the vRealize Hyperic 5.8.4 release.

New When you upgrade vRealize Hyperic to a new version, the Hyperic VAMI and virtual machine console incorrectly display the upgraded version with the old version number, even though the upgrade to the new version was successful. You can verify that the upgraded version is successfully deployed by opening the user interface for the vRealize Hyperic server (http://server name:7080/) and noting that the new version number appears.

New When the POODLE security vulnerability was addressed for vRealize Hyperic, the handshake operation, which is necessary to determine which SSL protocol is in use, was removed from the vRealize Hyperic server. As a result, vRealize Hyperic agents that use Java 6 no longer send metrics to the vRealize Hyperic server.Workaround: It is necessary to restore the handshake operation by updating the server.xml file.

Navigate to [server name]/hq-engine/hq-server/conf and open server.xml in a text editor.

Locate the protocols= attribute and add SSLv2Hello to the list of protocols. For example, protocols="SSLv2Hello,TLSv1.2,TLSv1.1,TLSv1".

Save the file.

Restart the vRealize Hyperic server.

Metrics start to appear in the user interface.

To monitor MS SQL 2012/2014 using the SQL Query plug-in, the sqljdbc4.jar JDBC driver for the target database must be present in the vRealize Hyperic agent's AgentHome/bundles/agent-X.X.X/pdk/lib/jdbc directory. If your version of vRealize Hyperic does not include this driver for the target database, download and install it in the directory.

Time zone changes in Russia are supported by common Java classes. The patch must be installed manually. The following procedure enables you to install the patch for the JRE embedded in vRealize Hyperic.Procedure For Linux operating systems:

Run java -version to verify that your Java version is specified in the %PATH% variable.

Run java -jar tzupdater.jar -u -v -f.

Run findstr tzdata <java-home>\lib\zi\ZoneInfoMappings to verify the TZUpdater version.

New indicators have been added to the System plug-in. When you perform a version upgrade, the new indicators do not display data. This issue affects the Total Memory, Used Memory, and Swap Total metrics that are now converted to indicators, and the two new metrics Total Disk Capacity and Total Disk Usage.Workaround: Either

Define a policy that includes all the default metric configurations.

Create a dynamic group that includes all the platforms.

Assign the policy that you defined to the dynamic group.

The metrics update and are displayed as expected.
Or
For each platform resource, on the
Metrics tab go to
Metric Data > Show all Metrics and configure an interval for the missing and empty indicators.
Following the interval configuration, the indicators display the metrics.

When using an Oracle database, in the event that the listener is down, the Start action only works if the vRealize Hyperic agent is running using the same Windows user credentials as those that are being used for Oracle.

The vRealize Hyperic agent monitors an Oracle database by maintaining an open connection to the database. If the listener goes down, but the Oracle database instance is still up, vRealize Hyperic continues to detect the instance as available, because the existing connection remains open. However, new connections cannot be made because the listener is down, meaning that the database is not actually available. Workaround Restart the hq agent. The Oracle database availability becomes red, and the control actions work.

In Administration > Edit HQ Server Settings, if you incorrectly configure credentials under the vCenter Settings, you are not alerted that you have provided invalid credentials but vCenter mapping does not function.

Nltest only runs on Microsoft Exchange 2007 installed on Windows Server. You must run vRealize Hyperic as a domain user of Microsoft Exchange, not the default local system user that is specified during vRealize Hyperic installation.

After upgrading to vRealize Hyperic 5.8, mysql-plugin.jar continues to appear in the Plug-in Manager, even though it no longer exists.

Occasionally, when the vRealize Hyperic agent is down, the Resource Health status appears as down, when the actual status is unknown.

When you rename a resource, you must update the group before the change is visible to the group.

After you have installed a vRealize Hyperic agent on a Windows virtual machine, the agent starts automatically.

When you upgrade a vRealize Hyperic agent, if you select an option that is incompatible with the upgrade, the agent becomes unavailable and the displayed messages are misleading.Workaround:

Open the rollback.properties file to roll back version 5.8 to 5.0.

Specify set.HQ_AGENT_BUNDLE=agent-5.0.0

Specify set.HQ_AGENT_ROLLBACK_BUNDLE=agent-5.0.0

Restart the agent.

Note that, although the vRealize Hyperic agent version is version 5.0, under Administration > HQ Health > Agents, the version number still displays 5.8.

The Add/Update Plugin(s) button does not apply updates to plug-ins, it only adds new plug-ins.Workaround:To update a plug-in, go to Metric Data > Show All Metrics and set the interval for any metric. The agent will collect the new metrics.

If you change the pattern property in an HTTP resource, the change does not take effect.Workaround: Delete the HTTP resource, and recreate it with the new pattern.

The default vRealize Hyperic installation directory on Windows is C:\Program Files. The vRealize Hyperic installer does not recognize spaces in directory names. Workaround: Change the default installation directory to one with no spaces in its name.

A user who is the owner of a policy cannot be deleted. Workaround: Delete the policies that are owned by the user, before deleting the user.

An Availability metric for platforms that is set for one minute must be treated as a minimum of two minutes when you choose the recurrency option for an alert definition.

The Exchange 2007 standalone plug-in must be installed in Windows server 2003.

In the case in which multiple vCenter servers contain virtual machines that share the same MAC address, if some of the vCenter servers are configured to vRealize Hyperic server, or have vRealize Hyperic agents running on them, the vRealize Hyperic server might interpret and display those platforms as a single virtual machine.Workaround: Configure all the vCenter Servers to the vRealize Hyperic server. A vCenter Server mapping mechanism is generated that removes the MOREF data from the virtual machines with a common MAC address.

When you attempt to install the vRealize Hyperic plug-in on an Exchange machine, the server might be unavailable and the message Error retrieving value: \MSExchangeIS Mailbox(_Total)\Messages Sent might be displayed. Workaround: Go to http://technet.microsoft.com/en-us/library/aa995801%28v=exchg.80%29.aspx and follow the directions to enable the MSExchangeIS object in the Performance Manager.

A virtual machine that does not have VMware Tools installed is not mapped to the vRealize Hyperic server.

When you install vRealize Hyperic usings the non-JRE Windows installer, it might take some time before the user interface appears, and invalid exceptions might appear in the log.

Deleting a resource from the inventory causes any resources currently in the auto-discovery queue to be removed from the queue and from the Auto-Discovery portlet on the dashboard. The resources reappear in the portlet when they are next auto-discovered and added to the queue.

In a large vRealize Hyperic deployment, deleting multiple platforms simultaneously from the user interface can result in orphaned resources, browse errors, incorrect results in the user interface, and under some circumstances, a stack trace. The following message in server.log indicates that this error condition has occurred: 05-04-2012 13:10:54,185 EDT ERROR [tomcat-http--19] [org.hyperic.hq.ui.util.UIErrorHandler@49] An exception was thrown for the following request URI '/resource/group/monitor/Visibility.do': java.lang.NullPointerException at org.hyperic.hq.bizapp.server.session.MeasurementBossImpl.findGroupCurrentHealth (MeasurementBossImpl.java:3204) If you experience this problem, contact VMware Global Support Services.

The Operations Center page intermittently is empty and displays Sorry, an error occurred. A stack trace is written to server.log when the error occurs.

If a vRealize Hyperic agent is deployed on an operating system with an IP address that is currently associated with an existing resource (platform) in vRealize Hyperic , the agent will not auto-discover the platform, servers, and services associated with this operating system.Workaround: Prior to deploying the application, remove vRealize Hyperic resources that are currently associated with the IP address to be reused.

When adding alert definitions that include a recovery alert to a plug-in JAR file, the loader fails to parse the recovery alert.Workaround: Comment out the recovery alert and the loader will parse correctly.

Role names and group names in vRealize Hyperic must be prefixed by org/. For example org/Admin.

Do not start or restart the vRealize Hyperic server using root credentials.

When SELinux is enabled, the CentOS 5.8/5.7 32-bit vRealize Hyperic agent running on Java 7 fails to start, and the message failed /work/hyperic-hq-agent-5.8.0/bundles/agent-x86-linux-5.8.0/jre/lib/i386/client/libjvm.so, because /work/hyperic-hq-agent-5.8.0/bundles/agent-x86-linux-5.8.0/jre/lib/i386/client/libjvm.so: cannot restore segment prot after reloc: Permission denied is displayed.Workaround: Attempt to run chcon -t texrel_shlib_t /work/hyperic-hq-agent-5.8.0/bundles/agent-x86-linux-5.8.0/jre/lib/i386/client/libjvm.so so that the agent and SELinux run on the same virtual machine.

When using Internet Explorer, you cannot customize SNMP trap OIDs for escalation actions and SNMP notifications.

Emails are not sent when vRealize Hyperic is deployed from an OVA file. Workaround: Update the email configuration properties on the Administration page.

In the HQ API, when you call get resource config, the platform.config_track.files value is empty.

Sometimes, an incorrect DSN for collecting virtual machine or ESX server data is passed by the server to the vRealize Hyperic agent. In this case, the virtual machine or ESX server appears to be unavailable.Workaround: Change the default collection interval for the affected resources, so that the server sends the DSN to the agent again.