VMware vCenter Operations Manager Enterprise 5.0 Release Notes
vCenter Operations Manager 5.0 | Build 562039
Last Document Update: 22 Feb 2012
Check frequently for additions and updates to these release notes.
These release notes include the following topics:
- Introduction to vCenter Operations Manager 5.0
- Before You Begin
- Installation and Upgrades
- Known Issues
VMware vCenter Operations Manager is an automated operations management solution that provides integrated performance, capacity, and configuration management for highly virtualized and cloud infrastructure. Deep VMware vSphere integration provides the most comprehensive management of VMware environments. VMware vCenter Operations Manager is purpose-built for VMware administrators to more effectively manage the performance of their VMware environments as they move to the private cloud.
- Actionable intelligence to automate manual operations processes
- Visibility across infrastructure and applications for rapid problem resolution
- Proactively ensures optimal resource utilization and virtual and cloud infrastructure performance
Review this section before you begin installing and configuring VMware vCenter Operations Manager Enterprise.
The vCenter Operations Manager Enterprise edition is available as a standalone executable. Installing and upgrading on Windows and Linux platforms is supported in this release. The vCenter Operations Manager Enterprise standalone edition should be installed on one of the supported operating systems.
- Windows Server 2003 64-bit SP2 or later
- Windows Server 2008 64-bit
- Red Hat Enterprise Linux 5 64-bit
Note: vCenter Operations Manager Enterprise is also supported as a vApp and deployed using the vSphere Client. For more information about vSphere deployments, see the vCenter Operations Manager Deployment and Configuration Guide.
- To install vCenter Operations Manager Enterprise 5.0, run the installation files.
- To upgrade from vCenter Operations Manager version 1.0 or 1.0.1 to 5.0, run the 5.0 installation files. Select the Reinstall (upgrade) option and continue with the installation.
- The same installation procedure is used for both fresh installations and upgrades to version 5.0. Follow the installation procedure in Chapter 5, Installing vCenter Operations Manager Enterprise in the vCenter Operations Manager Enterprise Installation and Configuration Guide.
- VMware vCenter Operations Manager Enterprise Installation and Configuration Guide—Explains installation and post-installation tasks of vCenter Operations Manager Enterprise
- VMware vCenter Operations Manager Enterprise Getting Started Guide—Contains conceptual and procedural information on using vCenter Operations Manager Enterprise.
- VMware vCenter Operations Manager Enterprise Administration Guide—Explains the administration of vCenter Operations Manager Enterprise
- VMware vCenter Operations Manager Enterprise online help—Contains conceptual and procedural information to help you complete your tasks when administering and using vCenter Operations Manager Enterprise.
This section contains known issues for this release.
When connected to an Oracle database with the default character setting, vCenter Operations Manager displays characters of high ASCII as question marks
When vCenter Operations Manager is deployed with an Oracle database, and configurations such as dashboards or resource tags are created with 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. Characters will then display correctly.
Email notifications with SSL or TLS is not supported in this release
vCenter Operations Manager does not send email notifications if encrypted connection (SSL or TLS) is required.
Cyclic redundancy check errors manifest as missing data
In vCenter Operations Manager, cyclic redundancy check (CRC) errors will appear as missing data for a given resource.
Workaround: If you see missing data for a resource, check the log file in /data/vcops/log/analytics.log to see if CRC-related errors are being 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 you see such errors, set the property FSDBCheckAndRepair to 2 in /usr/lib/vmware-vcops/user/conf/analytics/advanced.properties. The errors will be corrected within seven days.
Default fromName in the Filter plug-in defaults to "Alive"
The Filter plug-in is an outbound plug-in that sends email messages for specific alerts, as configured in the file emailFilter.xml. This file is located in: %ALIVE_BASE%\user\plugins\outbound\filter_alertplugin\conf
An email message is sent when an alert is added, updated, or cancelled, and the email message passes through the filtering rules configured in the XML file. (Filtering is needed to limit the number of email messages sent.)
In the current release, email messages from the Filter plug-in are sent with the default fromName of "Alive." The fromName is not configurable in the XML file, while the sendFrom email is.
Workaround: The From format of the email is: [fromName] [sendFrom]
For example: From "Alive" [firstname.lastname@example.org]
it is located