VMware vCenter Operations Manager Enterprise 5.0.3 Release Notes
VMware vCenter Operations Manager 5.0.3 | Build 818423
Last Document Update: 30 August 2012
Check frequently for additions and updates to these release notes.
These release notes include the following topics:
- What's New
- Before You Begin
- Installation and Upgrade Instructions
- Resolved Issues
- Known Issues
The VMware vCenter Operations Manager Enterprise 5.0.3 release is an update to vCenter Operations Manager Enterprise 5.0.2. vCenter Operations Manager 5.0.3 includes bug fixes, and feature improvements.VMware vCenter Operations Manager Enterprise Installation and Configuration Guide lists all compatible versions of vSphere and other components that vCenter Operations Manager supports.
vCenter Operations Manager 5.0.3 supports the following browsers.
- Internet Explorer for Windows 8.0 and 9.0
Note: The Compatibility View mode must be disabled.
- Mozilla Firefox for Windows 3.6 and 14.0
The minimum supported browser resolution is 1024 by 768 pixels.
VMware vCenter Operations Manager Enterprise 5.0.3 is available as a standalone executable and as a vApp that you deploy with the vSphere Client.
You can install and upgrade the standalone version of vCenter Operations Manager Enterprise 5.0.3 on the following operating systems:
- Windows Server 2003 64-bit SP2 or later
- Windows Server 2008 64-bit
- Red Hat Enterprise Linux 5 64-bit
For system requirements, installation instructions, and configuration options for the standalone version, see the VMware vCenter Operations Manager Enterprise Installation and Configuration Guide.
For information about vApp deployments, see the VMware vCenter Operations Manager Deployment and Configuration Guide.
To install the standalone version of vCenter Operations Manager Enterprise 5.0.3, run the 5.0.3 installation files for your operating system. For more information, see the VMware vCenter Operations Manager Enterprise Installation and Configuration Guide.
To upgrade from vCenter Operations Manager Enterprise 1.0, 1.0.1, 1.0.2, 5.0, 5.0 Hotfix, 5.0.1, 5.0.2, or 5.0.2 Hotfix to 5.0.3:
- Depending on the operating system, download the latest .exe or .bin file to the machine where the old product version is installed.
- Run the .exe or .bin file.
- Select the Reinstall (Upgrade) option.
- Select the installation mode.
- To preserve your settings from the original installation, do not change the default setting..
- To modify installation options, select Basic or Custom.
- On the Database configurations screen, do not modify any settings, and click Finish.
- On the main installation screen, click Done.
- Check the following log files under the vcenter-ops/user/log folder for upgrade issues:
- If adapters are installed on the system that you upgraded, download and install the latest adapter versions.
- Log in to vCenter Operations Manager Enterprise and verify that the user interface displays properly.
Important: To save time during the standard upgrade procedure, the DB upgrader logic of vCenter Operations Manager Enterprise Standalone does not run the database scripts that handle some specific use cases. For more information, see Configuration wizard does not update the database during an upgrade (KB 2017042).
- VMware vCenter Operations Manager Enterprise Installation and Configuration Guide
- VMware vCenter Operations Manager Enterprise Getting Started Guide
- VMware vCenter Operations Manager Enterprise Administration Guide
- VMware vCenter Operations Manager Enterprise online help
The vCenter Operations Manager Enterprise 5.0 documentation also applies to vCenter Operations Manager 5.0.3.
The following problems have been resolved in this release.
Remote collectors do not work if firewall is enabled
If a firewall exists between the main vCenter Operations Manager Enterprise server and a remote collector, the remote collector installation fails. Error messages indicate that the heartbeat or ActiveMQ service cannot be reached.
Installing Microsoft SQL Server with Windows authentication does not work
You cannot use Integrated Windows Authentication while using Microsoft SQL Server.
The version of Apache Struts in vCenter Operations has been updated to 2.3.4
Apache Struts 2.3.4 addresses an arbitrary file overwrite vulnerability. This vulnerability allows an attacker to create a denial of service by overwriting arbitrary files without authentication. The attacker would need to be on the same network as the system where vCenter Operations Manager is installed. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0393 to this issue.
Note: Apache Struts 2.3.4 also addresses the following issues that do not affect vCenter Operations Manager: CVE-2011-5057, CVE-2012-0391, CVE-2012-0392, CVE-2012-0394.
This release contains the following known problems.
vCenter Operations Manager Enterprise might stop responding after an upgrade
vCenter Operations Manager Enterprise might stop responding about a day after an upgrade. Existing user sessions remain open, but you cannot create new login sessions. Views stop responding and data collection stops. This problem occurs because the upgrade process does not check the database deployment and table space configuration. If a third party made custom table space modifications between updates (for example, to improve DBMS performance), the upgrade can place the indexes into the wrong table space and the data table space can exceed its allocated space requirement. This problem can also occur if the default table space becomes full and no modifications are applied between updates.
Workaround: Use one of the following workarounds, depending on the cause of the problem.
- After the upgrade, migrate the indexes to the appropriate table space.
- After the upgrade, revert the database to the default configuration on a larger table space.
You cannot export Anomaly Correlation Reports to a PDF file when vCenter Operations Manager Enterprise is running on a 64-bit server and the browser is Internet Explorer 9
When you export the Anomaly Correlation Report to the PDF report type, the exported PDF file is 0 bytes.
Workaround: Make sure that the Do not save encrypted pages to disk option in Internet Explorer is disabled. To disable this option, select Tools > Internet Options > Advanced and deselect the Do not save encrypted pages to disk check box in the Security area under Settings.
vCenter Operations Manager Enterprise displays characters of high ASCII as question marks when connected to an Oracle database with the default character setting
For example, if dashboards or resource tags that have high ASCII characters in their names, those letters appear as question marks (?).
Workaround: Configure the Oracle database to use a Unicode character set such as UTF-8 to make characters display correctly.
Cyclic redundancy check (CRC) errors manifest as missing data
CRC errors appear as missing data for a given resource.
Workaround: Check the vcenter-ops/data/vcops/log/analytics.log file to see if CRC-related errors are logged, for example:
com.integrien.alive.FSDB.FSDBException: CRC Failure in file for Resource 6773, filename = /data/vcops/data/6/6773/2011_10_6773.dat
2011-11-11 03:04:31,552 ERROR [Calc DT worker thread 3]
com.integrien.analytics.datareceiver.MetricDataRetriever.getDataPointBundle - CRC Failure in file for Resource 6773, filename = /data/vcops/data/6/6773/2011_10_6773.dat
If the log file contains CRC-related errors, set the FSDBCheckAndRepair property to 2 in the vcenter-ops/user/conf/analytics/advanced.properties file. Errors are corrected within seven days.
You must update the statistics of data tables periodically so that the Oracle SQL native query analzyer can operate and fetch data efficiently
vCenter Operations Manager Enterprise does not provide a user interface to configure database updates.
Workaround: See Automated gathering of statistics for Oracle database tables and their indexes (KB 2016451).
Administration Guide does not describe MIB file for SNMP traps
You can configure vCenter Operations Manager to send alert notifications as SNMP traps. The vcenter-ops/user/plugins/outbound/snmp_alertplugin/mibs/VMWARE-VCOPS-EVENT_MIB.mib file contains the information that you need to enable the receiving party to interpret these traps.
Administration Guide does not describe how to suppress No Data Receiving alerts
To configure an adapter instance not to generate alerts when it is not receiving data:
- Open the vcenter-ops/user/conf/analytics/advanced.properties file.
- Add the
resourceID is the resource ID of the adapter instance.
- Save your changes and close the advanced.properties file.
- Restart the Analytics service for your changes to take effect.
Online help describes nonexistent Resolution tab
The Resolution tab was removed from the user interface, but it is still described in the online help.
- Administration Guide describes nonexistent emailFilter.xml file option
The option to set the reload interval for the emailFilter.xml file (FileReloadTimeInMinutes property and File reload time (minutes) text box in the Configuration File Editor) was removed from the user interface, but it is still described in the administration guide.
- Documentation and online help do not describe the new features for the 5.0.2 release
The documentation and online help were not updated for the 5.0.3 release. For descriptions of the new features, see What's New.