VMware

VMware vCenter Operations Enterprise 1.0 Release Notes

VMware vCenter Enterprise 1.0 | Build 385830

Last Document Update: 12 APR 2011

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

What's New

The following information provides highlights of some of the enhancements available in this release of vCenter Operations Enterprise 1.0.

New Features

  • Installation and Deployment
    • Each vCenter Operations Enterprise adapter now has its own independent installer. Adapters are no longer shipped automatically with vCenter Operations Enterprise.
    • vCenter Operations Enterprise can now connect to a SQL Server database using Windows authentication.
    • A new installation and configuration option enables synchronization between the primary vCenter Operations Enterprise server and a replication server.
    • The default installation directory for vCenter Operations Enterprise has changed to \vmware\vcenter-operations.
    • The product is no longer installed with configured limits to the number of resources and metrics. However, defining more resources or metrics than the server host's configuration can support will result in inadequate performance. Contact VMware Professional Services to discuss hardware and software requirements for your environment.
  • User Interface
    This release placed a special emphasis on improving the user experience throughout the product. The user interface was made more intuitive and more interactions among the widgets were added. Information rendering performance was improved. The major enhancements to the user interface are listed below.
    • An administrative alert is generated when none of the Analytics processors is communicating with the vCenter Operations Enterprise server.
    • You can now select a date range on the Mashup tab of the Alert Details page.
    • The list of alerts on the Alerts Overview page displays more quickly.
    • The Alerts Overview page now includes filtering by resource tag.
    • You can return a suspended or suppressed alert to an open state by using the Release Ownership icon on the Alerts Overview page.
    • The Alert Summary and Alert Details pages include a Help icon.
    • The new capacity analysis feature uses the performance history of a selected metric to predict its future growth and when it is likely to reach a limit you set. You can use this to help plan when to perform infrastructure upgrades, such as adding disk storage to a server or increasing your network capacity.
    • The Cross-Silo Analysis page now includes a Health Tree pane.
    • The Collection State column of the Environment Overview page was replaced by two columns: Collection State (whether vCenter Operations Enterprise is supposed to be collecting values for the resource) and Collection Status (whether vCenter Operations Enterprise is actually receiving values for the resource).
    • The LDAP integration feature now supports SSL for secure communication with the LDAP Server.
    • LDAP integration now includes auto-synchronization, which imports users from LDAP into vCenter Operations Enterprise Server at a pre-defined interval.
    • Logging can now be turned on for widgets.
    • Adapter logging is improved. vCenter Operations Enterprise creates a separate log file for each adapter instance.
    • The Manage Resource Kind Defaults window now includes default settings for whether to calculate dynamic thresholds and generate early warning smart alerts for the resource kind.
    • The Resource Detail page now includes the relation to the resource's parent resource and child resources, as well as root cause metrics for the resource's current state.
    • There are additional icons available for resource kinds. You can associate icons with resource kinds during adapter installation.
    • The Status tab of the Support page is now the Application Detail page for the vCenter Operations Enterprise application.
    • The new Info tab of the Support page displays information previously found on the Status tab. It also shows information on the replication status of vCenter Operations Enterprise to a backup server.
    • The Info tab of the Support page include the version of each installed adapter in the Adapter Info pane.
    • The default resource tags now include Health Ranges and Adapter Instances. This allows you to filter by these values wherever you can filter by resource tags.
    • The Time Preference for all new users is set to Browser.
    • On the Heat Map widget, the tip displayed when you hover over the rectangle for resource now includes a Show Sparkline link. Click this link to see a small sparkline of the metric being tracked by the heat map color.
    • vCenter Operations Enterprise now saves when the health status of a resource is unknown (blue). This value is shown on the Health Status widget graph.
    • The Health Tree widget now shows alerts for a resource as badges on the resource kind icon. Selecting a resource and clicking the Show Alerts icon lists all active alerts for the resource.
    • The configuration page for the Health Tree widget now includes a Tag Filter pane. You can filter the parent and child resources that appear in the widget by tag value.
    • The Health Workload Scoreboard widget can now use any metric for the resource as the workload metric.
    • The Health Workload Scoreboard widget can now be configured to have the resources to track be provided by the Alerts, Health Status, Health Tree, Advanced Health Tree, Heat Map, Resources, Generic Scoreboard, or Root Cause Ranking widget.
    • There are more icons to select from when choosing how to display resources in the Health Workload Scoreboard widget.
    • On the Mashup Charts widget and the Mashup tab of the Alert Details page, you can now double-click an alert icon in the health chart to open the Alert Summary page for that alert.
    • From the Metric Graph widget, you can now save the metric graph as a full-page image file.
    • In the Metric Graph widget, the graph for the vCenter Operations Enterprise-generated metric Self - Total Anomalies displays the calculated noise line for the resource.
    • The toolbar of the Root Cause Ranking widget now includes a Change Mode icon. Click this icon to switch between Resource mode and Symptom mode.
    • Everywhere that shows root causes now includes a time stamp on top of the symptoms bar. This provides information on when the symptoms occurred relative to each other.
  • Application Programming Interface (API)
    • The Adapter Framework was redesigned to consolidate three different APIs into one API with two different interfaces. If data collection fails, improved error handling clearly notifies the user about the point of failure.
    • The HTTP Post API now supports web authentication. When web authentication is enabled, only vCenter Operations Enterprise users with the Administrative Access right can post data to vCenter Operations Enterprise.
  • High Availability and Scalability
    • vCenter Operations Enterprise Platform was created to separate the user interface from the back end engine for analytical processing of data.
  • Analytics
    • A mathematical model for aggregate anomaly detection is added to improve accuracy in generating alarms for dynamic threshold violations.
    • Dynamic threshold calculation performance is improved in all analytics plug-ins.
    • The Multinomial and Binomial analytics plug-ins were replaced with a single MultinomialDT plug-in.
    • The health calculation algorithm was improved. A health score of 0 indicates a resource is down.
    • A new analytics plugin, Delta Variance, is added. It defines the normal range for metrics which have constant value or constant slope for most of the time.
    • A new plugin, Null Plugin, is added. When none of the analytics plugins/algorithms can define a normal range for a metric based on its time series data, by default it is assigned to Null Plugin. This ensures that no dynamic threshold violation events for this metric are generated.
  • Tools and Utilities
    • The new Reporting Repository Adapter tool populates either a relational database or a comma-separated text file with a subset of data from the vCenter Operations Enterprise FSDB on a set schedule.
    • The new FSDB Cleaner tool removes system-generated metrics from the FSDB files. This is intended for use during an historical proof of concept.
    • The new Auto Configuration tool estimates the number of resources a server host can support based on the server's CPU, disk space, memory, and file I/O specifications.

Discontinued Features

The following features are discontinued in vCenter Operations Enterprise 1.0.
  • There is no longer an option to install the vCenter Operations Enterprise Anomaly Detector.
  • Adapters required to collect metrics are not shipped with vCenter Operations Enterprise. Every adapter has its own installer.
  • The Resolutions tab of the Alert Details page is disabled. You cannot enter resolution notes for an alert.

Before You Begin

System Requirements

vCenter Operations Enterprise requires the following system resources:

  • Windows Installation: Windows Server 2003 Service Pack 2 or higher (x64-bit), Windows Server 2008 (x64 bit).
  • Linux Installations: Red Hat Enterprise Linux release 5 (x64-bit).
    The following prerequisites are required for the Linux version of vCenter Operations Enterprise 1.0:
    • Linux user account for installing vCenter Operations Enterprise should have root-level privileges.
    • X Windows System release 11 (X11) needs to be on the server where vCenter Operations Enterprise is to be installed.
    • GUI mode installation also requires a Standard Terminal Emulator for X Windows System.
  • Disk Performance: 150MB/s Sustained READ/WRITE performance for each 1 million metrics collected at 5 minute collection interval with Total IOPS of 800.
  • Disk Usage: 800GB of usage per 250,000 metrics per year for storage based on five minute collection interval.
  • CPU: At least 4x64-bit Multi-Core Processors (2GHz or faster) to collect up to 250,000 metrics. 8x64-bit Multi-Core Processors (2GHz or faster) to collect up to one million metrics.
  • RAM: At least 8GB to collect 250,000 metrics; 24GB to collect one million or more metrics, 64GB to collect four million or more metrics.

    NOTE: Remote collectors and the analytics processor can also be installed on 32-bit CPUs.

The following system resources are required to install the vCenter Operations Enterprise database:

  • RAM: At least 2GB, 8GB for systems collecting more than 1 million metrics.
  • CPU: At least two 32-bit CPUs (P4 2GHz or faster), two 64-bit CPUs for systems collecting more than one million metrics.
  • Database application: Oracle 10g R2 or 11g R2, Microsoft SQL Server 2005 Service Pack 2 or higher, or Microsoft SQL Server 2008 (SQL Server not supported if the vCenter Operations Enterprise server runs Linux).

    NOTE: The database must be configured and accessible to the vCenter Operations Enterprise server and ping time between the servers should be less than one millisecond. We suggest the database server hosts only the vCenter Operations Enterprise database due to the resource requirements of the application.

The vCenter Operations Enterprise Client requires the following system resources:

  • RAM: At least 2GB
  • CPU: At least Pentium 4 2GHz or faster
  • Browser: Internet Explorer version 7.x or 8.x; Mozilla Firefox 3.x; JavaScript enabled and pop-up blockers removed or disabled
  • PDF viewer: A viewer, such as Adobe Reader, for viewing reports in PDF format.

    NOTE: vCenter Operations Enterprise is fully capable of running in a virtual environment, on one or several virtual machines). In order to configure the necessary hardware environment, please refer to the Technical Support and Education Resources section of the vCenter Operations Enterprise Installation and Administration Guide.

Installation Notes

  • To deploy vCenter Operations Enterprise 1.0, please run the electronically-obtained installation files.
  • For new deployments, you must refer to the vCenter Operations Enterprise Installation and Administration Guide, which is part of the documentation kit for this release.

vCenter Operations Enterprise Documentation

The documentation set for vCenter Operations Enterprise 1.0 Consists of the following documents.

Known Issues

This section contains known issues for this release.

  • Manually created resources should have a unique identifier
    Manually created resources having the same unique identification (Adapter Kind + Resource Kind + Resource Name or Adapter Kind + Resource Kind + List of Identifiers) can result in wrong system behavior, including resources hanging in start and stop status. This issue also applies to Application Tiers sharing the same name. This does not apply to resources added in system through manual or automatic discovery as uniqueness is enforced by the system.
    Workaround: If resources with the same unique identification are duplicate, delete the duplicate resources. If they are different resources, rename the resource or change the List of identifiers conflict. For Application Tiers, use the following rule for naming: Tier Name=Application Name + ' ' + Tier Type. For example, for "Online Banking" Application tiers, use the names "Online Banking DB," "Online Banking App," etc.
  • On the Alert Overview page, you cannot search the Root Cause or Info columns
    If the text you enter in the Search field on the Alerts Overview page exists only in the Root Cause or Info column, the search will not find it.
    Workaround: None
  • You cannot remove the Time Range constraint in the Manage Alert Watch List window by clicking the check box next to it
    Workaround: To remove the constraint, bring up the Pick a Time Range pop-up window and remove the date and time from the text boxes.
  • On Red Hat Enterprise Linux release 5, the services do not restart automatically after you make changes in the configuration wizard
    If you run the configuration wizard in console mode under Red Hat Enterprise Linux release 5 to change properties on an existing server, your changes do not take effect automatically after they are saved.
    Workaround: You must restart the vCenter Operations Enterprise services manually. Use the run level script vcops.sh to restart the services.
  • vCenter Operations Enterprise can be set up to be accessed via HTTPS protocol only on the standard port 443.
    Workaround: None. If you want to use HTTPS, you must use port 443.
  • You can install vCenter Operations Enterprise only with root user credentials
    Workaround: Please contact VMware Support or Professional Services for information about installing vCenter Operations Enterprise on Linux using non-root user account .
  • The Configuration Overview widget reflects only collecting resources
    All of the information shown on the Configuration Overview widget--resource counts, metric counts, and so on--includes only resources for which metrics are being collected. If collection is off for a metric, its data is not included. For performance reasons, the information is taken from the memory used by the analytics process. If metrics are not being collected for the resource, the analytics process does not keep its information in memory.
    Workaround: Start collection for all resources you want to be included in the information shown in the Configuration Overview widget.
  • Maintenance schedules cannot span for more than 24 hours
    Workaround: Split any maintenance schedule that spans two days into two different maintenance schedules.
  • vCenter Operations Enterprise does not support Network Area Storage (NAS) for storing FSDB files.
    Workaround: Use only SAN or DAS devices to store FSDB files.
  • Role-based security is implemented on the server side, which means access rights are checked when an action is taken
    As a result, some actions will not give a message of insufficient access rights until after the user has completed entering information for the action. For example, when cloning a dashboard, the insufficient rights message will not appear until after the user enters the name of the new dashboard.
    Workaround: None.
  • Metric value time stamps are not always displayed
    The time stamps for metric values are not shown when you are viewing a period longer than 24 hours even if Show Data Values is selected for the graph.
    Workaround: To show the time stamp for displayed metric values, view a period of less than 24 hours.
  • vCenter Operations Enterprise stops responding if you delete an application with a large number of resources
    Deleting an application which comprises a large number of resources might take a very long time, and vCenter Operations Enterprise might stop responding.
    Workaround: Delete the individual tiers in the application before you delete the application.
  • Manual fingerprint preview mode time ranges may overlap
    Depending on the screen resolution and number of intervals chosen, creating a manual fingerprint may result in overlapping time range in preview modes.
  • You cannot uninstall the vCenter Operations Enterprise Collector using console mode on 32-bit Red Hat Enterprise Linux
    The command to uninstall the vCenter Operations Enterprise Collector does not work from console mode on 32-bit Red Hat Enterprise Linux.
    Workaround:
  • If you select HTTPS during installation, the host IP address defaults to localhost
    During vCenter Operations Enterprise installation, if you choose "HTTPS" as the protocol for communication with the Web site, the detected Host IP is replaced with localhost.
    Workaround: Manually replace localhost with the detected IP address before continuing.
  • A blank page is displayed when you log in to vCenter Operations Enterprise if the Skype plug-in for Internet Explorer is enabled
    If you have the Skype Plug-in for Internet Explorer installed and enabled, the browser displays a blank white page after you sign into vCenter Operations Enterprise.
    Workarounds:
    • Disable or remove the Skype plug-in.
    • Press F5 after signing in to reload the vCenter Operations Enterprise page.
  • The number of allowed login attempts is incorrect
    vCenter Operations Enterprise allows one more login attempt than is specified in the Allowed Login Attempts field of the Account Lockout Policy pane.
    Workaround: Set the Login Attempts field to one less than the actual desired limit.
  • Filtering the Alerts widget by Time Range displays an incorrect message
    When the Alerts widget is configured to filter by Time Range, clicking the Display Filtering Criteria icon in the toolbar of the widget incorrectly displays a message saying There is no selected filter criteria.
    Workaround: To see the active filtering criteria, edit the widget. Each active filter type will have a check mark by it.
  • Filtering the Resources widget by Adapter kind displays an incorrect message
    When the Resources widget is configured to filter by adapter kind, clicking the Display Filtering Criteria icon in the toolbar of the widget incorrectly displays a message saying There is no selected filter criteria.
    Workaround: To see the active filtering criteria, including the selected adapter kinds, edit the widget.
  • The Tag Selector widget state is not saved
    If you leave a dashboard which includes the Tag Selector widget, then return to it, any tags selected for interaction with other widgets will not be marked.
    Workaround: None
  • Environment Overview page and Resources widget do not always sort correctly by health
    When sorting by health, resources may be listed in the wrong order on the Environment Overview page and the Resources widget. This is for two reasons: 1) The resources are sorted according to the value in the database, while the value shown comes from the analytics cache. This means the sorting will be wrong while analytics is loading resources. 2) The database stores only the health state (Normal, Degraded, and so on), not the numeric health score. This means that resources in the same state are not necessarily in numeric order.
    Workaround: None
  • Filtering Environment Overview resource list by health state can list wrong resources
    When filtering the Environment Overview page by health (for example, listing only those resources with "Good" health), the resources listed do not always show as having the requested state. This is because the filtering is done according to the health state in the database, while the health state shown is taken from the analytics cache. if these disagree, the filter appears to include the wrong resources.
    Workaround: None
  • "Too many files open" message on Linux server
    At times, the vCenter Operations Enterprise Web client can cause Tomcat to have too many file descriptors open at once. This leads to a "Too many files" open error message.
    Workaround: The number of descriptors is limited at both the system level and shell level. You may need to increase the shell ulimit maximum or the maximum number of system file descriptors by adding or modifying the fs.file-max parameter in the /etc/sysctl.conf file.
  • Users without permission to edit adapters or applications can edit them through Environment Overview
    Users with permission to edit resources can edit all resources through the Environment Overview page, even if it conflicts with other security settings. Users without permission to edit adapter instances, but with permission to edit resources, cannot edit adapter instances through the Manage Adapter Instances window, but can through Environment Overview. The same is true for applications. Users who have permission to edit resources, but not applications, are able to edit applications through Environment Overview.
    Workaround: Give permission to edit resources only to users who should be able to edit all resources, including adapter instances and applications.
  • Cannot see total number of metrics for a resource that is not collecting
    If metric collection is stopped for a resource, the total number of metrics for the resource shows as "?." This is true everywhere that the total number of metrics is displayed. This is because, for performance reasons, the number of metrics is taken from the memory used by the analytics process. If metrics are not being collected for the resource, the analytics process does not keep its information in memory.
    Workaround: To see the total number of metrics for a resource, start collection for the resource.
  • The maximum length for a credential password is 30 characters
    When entering a credential, you can enter only up to 30 characters for the password.
    Workaround: Make sure that all user names used in credentials have passwords of 30 characters or less.

Updates to the Documentation

This section contains updates and corrections to the documentation for this release.

vCenter Operations Enterprise User Guide

  • The description of the Root Cause Ranking widget in Chapter 7, Widgets, is not completely accurate. The Anomalies Activity Period field has been removed from the widget. In Symptom mode, the widget shows root cause information based on anomalies occurring during the previous six hours, unless a different time period has been passed to it by a providing widget. In Resource mode, it shows information based on the previous two hours. When a time period is passed to it by a providing widget, it shows information for all anomalies active in that time period.
  • The description of the Root Cause Ranking pane of the Resource Detail page in Chapter 4, Viewing Resources and Applications, is not completely accurate. The Anomalies Activity Period field has been removed from the Root Cause Ranking pane. In Symptom mode, the pane shows root cause information based on anomalies occurring during the previous six hours. In Resource mode, it shows information based on the previous two hours.

vCenter Operations Enterprise 1.0 EMC Smarts Integration Guide

  • In the section "Installing the vCenter Operations Enterprise Custom View" on page 17, the path to the rncmd_env.sh file in step 2a is not correct for EMC Smarts versions 8.x. For 8.x versions, the correct path is <SmartsRoot>\CONSOLE\smarts\local\conf\runcmd_env.sh.