VMware vCenter Operations Manager Enterprise 5.0.1 Release Notes
vCenter Operations Manager 5.0.1 | Build 678276
Last Document Update: 26 April 2012
Check frequently for additions and updates to these release notes.
These release notes include the following topics:
- Introduction to vCenter Operations Manager
- What's New
- Before You Begin
- Installation and Upgrades
- Resolved Issues
- 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
This section contains information that you must review and take into account 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
For system requirements, installation instructions, and configuration options, see the vCenter Operations Manager Enterprise Installation and Configuration Guide.
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.
During the upgrade of vCenter Operations Manager for Linux, the wrapper.conf file is overwritten
During the upgrade process of vCenter Operations Manager Enterprise for Linux, the wrapper.conf file used by Analytics is overwritten with the latest installation configuration file. Therefore, your custom garbage collector settings are lost. Only the wrapper.java.initmemory and wrapper.java.maxmemory properties are preserved from the old configuration after upgrade.
Workaround: If you want to preserve other custom settings from your old installation, create a backup copy of the wrapper.conf file.
- Before you initiate the upgrade procedure, navigate to $ALIVE_BASE/user/conf/analytics/, and create a backup copy of the wrapper.conf file in a folder outside the $ALIVE_BASE directory.
- After the upgrade, use the backup copy of the wrapper.conf file to update the new wrapper.conf file with your custom settings.
Customized Analysis heat maps are not preserved after upgrade from vCenter Operations Manager 5.0 to 5.0.1
During the upgrade, vCenter Operations Manager 5.0.1 overwrites the configuration files that contain the heat map settings. As a result, the customized heat maps that you created in vCenter Operations Manager 5.0 are no longer found.
Workaround: Create a backup copy of your heat map configuration files before you initiate the upgrade.
- Navigate to the directory that contains the heat map configuration file: <installation path>/tomcat/webapps/ROOT/WEB-INF/classes/.
- Create a backup copy of the heatmapConfigs.xml file to a folder outside the installation path.
- After the upgrade, use the backup copy of the heatmapConfigs.xml file to update the new heatmapConfigs.xml file with your custom settings.
- To install the standalone version of vCenter Operations Manager Enterprise 5.0.1, run the 5.0.1 installation files. Follow the installation procedure that corresponds to your operating system.
See Chapter 5, Installing vCenter Operations Manager Enterprise, of the vCenter Operations Manager Enterprise Installation and Configuration Guide for detailed installation procedures.
- To upgrade from vCenter Operations Manager version 1.0, 1.0.1, 1.0.2, 5.0, or 5.0 Hotfix to 5.0.1, run the 5.0.1 installation files.
- 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, keep the mode that is selected by default.
- 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.
- Under the <installation_path>/vcenter-operations/user/log directory, check if any upgrade issues are logged in the following files.
- If you have vCenter Operations Manager Enterprise adapters installed on the system that you upgraded, download and install the latest adapter versions.
- Log in to vCenter Operations Manager and verify that the user interface is displayed properly.
The standard upgrade procedure does not handle all possible database upgrade scenarios
To save time during the standard upgrade procedure, the db upgrader logics of vCenter Operations Manager Enterprise Standalone does not run the database scripts that handle some specific use cases.
Workaround: See The Configuration wizard does not update the database during an upgrade (KB 2017042).
- 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.
The documentation set for vCenter Operations Manager Enterprise 5.0 is applicable to vCenter Operations Manager 5.0.1.
In addition to the scalability and performance improvements, the following problems from previous product versions have been fixed in the vCenter Operations Manager 5.0.1 release.
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 emailFilter.xml file that is located in folder %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 emailFilter.xml file. Filtering is needed to limit the number of email messages that vCenter Operations Manager sends.
In the current release, email messages from the Filter plug-in are sent with the default fromName of "Alive." You cannot configure the fromName in the emailFilter.xml file, but you can configure the sendFrom email.
The From format of the email is: [fromName] [sendFrom]
For example: From "Alive" [email@example.com]
Email notifications with SSL or TLS are not supported
vCenter Operations Manager does not send email notifications if encrypted connection (SSL or TLS) is required.
This problem has been fixed.
This section contains known issues for the vCenter Operations Manager 5.0.1 release.
Remote collectors do not work if firewall is enabled
If an installation of vCenter Operations Manager involves remote collectors, and there is a firewall between the main server and the remote collectors, the installation of remote collector will fail with errors indicating inability to reach the heartbeat or ActiveMQ service.
Workaround: Contact VMware Support Services to discuss workarounds.
vCenter Operations Manager might stop responding about a day after the upgrade
In about a day after you upgraded vCenter Operations Manager, the application might stop responding. Existing user sessions remain open, but you cannot create new login sessions. The application views stop responding and data collection stops.
The problem occurs because the upgrade process does not check the database deployment and table space configuration. If custom table space modifications have been made by a third party (for example to improve DBMS performance) between release updates, the upgrade can place the indexes into the wrong table space, which can result in the data table space exceeding its allocated space requirement. This might also happen if the default table space gets full, without any modifications applied.
Workaround: Try one of the following, 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.
Installing a Microsoft SQL server with Windows authentication does not work
You cannot use Integrated Windows Authentication while using the Microsoft SQL server.
Workaround: The JDBC driver supports the use of Type 2 integrated authentication on Windows operating systems through the integratedSecurity connection string property. To use integrated authentication, copy the sqljdbc_auth.dll file to folder %ALIVE_BASE%/common/bin.
Filter email plugin sends email using generic template though a custom template is specified
When you create an email Filter.xml file using the Filter plugin configuration file editor tool, in the Email template window, you can specify the template to use by typing its name in the Template field. If you do not specify the template to use, vCenter Operations Manager Enterprise sends alert emails that are created using a generic template.
However, in the 5.0.1 release, the filter email plugin always sends alert emails using a generic template, even though you specified the template to use.
You cannot export Anomaly Correlation Reports to PDF when vCenter Operations Manager Enterprise is running on a 64-bit server, and the browser is Internet Explorer 9
If you use Internet Explorer 9 to view the vCenter Operations Manager Enterprise interface, and vCenter Operations Manager is running on a 64-bit server, if you try to export an anomaly correlation report to PDF report type, the resulting PDF file is 0 bytes in size.
Adapter Data Source icons are not displayed on the Environment Overview page after installing a new adapter and restarting all services
After restarting all services, the icons in the Data Source column of the Environment Overview list are not displayed. This problem occurs with icons for resources that are collected from adapters.
Workaround: After installing a new adapter, do not restart all vCenter Operations Manager services on the server.
To display adapter kind icons in the user interface, perform a manual adapter describe process:
- After you installed a new adapter, log in to vCenter Operations Manager.
- From the ADMIN menu, select Support, and click the Info tab.
- In the Adapter Info section, click the Describe icon.
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.
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, open the /usr/lib/vmware-vcops/user/conf/analytics/advanced.properties file and set the FSDBCheckAndRepair property to 2.
The errors will be corrected within 7 days.
Procedure on automated gathering of statistics for Oracle database tables and their indexes
You must update the statistics of data tables periodically, so that the Oracle SQL native query analyzer can operate and fetch data efficiently. vCenter Operations Manager does not provide a user interface for you to configure database updates.
Workaround: See Automated gathering of statistics for Oracle database tables and their indexes (KB 2016451).
Missing information on MIB files
vCenter Operations Manager can send SNMP traps as you configure it. The following *.mib file contains the information that you need to enable the receiving party to interpret these traps.
Missing information on configuring No Data Receiving alerts
You can configure adapter instances in vCenter Operations Manager Enterprise not to generate alerts when no data is received by the instance.
- Navigate to %ALIVE_BASE%\user\conf\analytics.
- Use a text editor to open the advanced.properties file and add the following property.
disabledNoDataReceivingAlertIds = <AIR_ID> where <AIR_ID> is the ResourceID of the adapter instance.
- Save the advanced.properties file and restart the AnalyticsService service for the changes to take effect.
Information about a non-existing tab in the in-product help
The in-product help contains a section about the Resolution tab which was removed from the user interface in this release.
Workaround: Ignore any information that pertains to the Resolution tab.