VMware vCenter Operations Manager 5.6
VMware

VMware vCenter Operations Manager 5.6 Release Notes

vCenter Operations Manager 5.6 | Build 923459

Last Document Update: 21 DECEMBER 2012

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

What's New

vCenter Operations Manager 5.6 is the latest release of VMware's integrated operations suite, converging performance, capacity, and configuration management. This new release introduces the following features and enhancements.
  • vCenter Server Compatibility
    vCenter Operations Manager now supports VMware vCenter Server 5.1 and ESXi 5.1. Beta versions of vCenter Server and ESXi hosts are not supported in this 5.6 release.
  • Integration with VMware vCenter Infrastructure Navigator
    This release introduces integration with vCenter Infrastructure Navigator. You can use application awareness for operations monitoring, troubleshooting, and planning. Monitor the health of your application infrastructure and gain visibility into installed applications. With this feature, groups of virtual machines with application dependencies are automatically populated in the vCenter Operations Manager interface.
    Note: vCenter Infrastructure Navigator 2.0 is the recommended version for vCenter Operations Manager 5.6. vCenter Infrastructure Navigator 2.0 must be used with vCenter Server version 5.1. vCenter Operations 5.6 can support application awareness with VIN 1.1, but the information provided is limited.
  • Integration with VMware vCenter Configuration Manager
    This release provides deeper integration with vCenter Configuration Manager. A new Compliance badge under the Risk badge enables you to understand compliance risks, and to correlate the changes that are affecting the compliance risk. With this feature, machine groups created by vCenter Configuration Manager are automatically populated in the vCenter Operations Manager user interface and a launch-in-context link is provided.
  • Integration in the VMware vSphere Web Client
    This release introduces vCenter Operations Manager integration in the vSphere Web Client. Badges appear in the vSphere Web Client interface when you register an instance of VMware vCenter Operations Manager with a vCenter Server that you want to monitor. Your vCenter Operations Manager license determines which badges and widgets you can see in the vSphere Web Client.

    Note: vCenter Operations Manger supports integration in the VMware vSphere Client for vCenter Server 5.1.

  • Custom Groups
    This release introduces user-defined and pre-defined custom groups. You can use the groups feature to customize the operational view of your infrastructure, tailoring it to your business environment. You can also customize group settings using policies.
  • Capacity Analysis
    This release enhances capacity planning by introducing more granular setting for capacity analysis. Customize capacity policies across your business groups or environments, including badge thresholds. Create custom policies for capacity configuration for groups, customize group-level thresholds using policies, and resolve conflict by policy order.
  • Improvements in stress detection and computation
    • This release supports peak-based calculations. Peak accommodation can be achieved through configuration of stressed and undersized settings. These setting determine the time duration over which stress detection will be applied. This functionality supports identification of short-lived peak workloads: if the stress duration setting is one hour, the stress calculation is based on peak values during that time period.
    • This release introduces a Consider Stress option that affects the calculation of Capacity Remaining and Time Remaining metrics and corresponding badge scores. When Consider Stress is enabled, vCenter Operations Manager uses effective CPU and memory demand metrics. The latter takes into account peak values of demand and limited demand that cause accumulation of stress conditions over time. (When Consider Stress is disabled, the behavior matches the 5.0 release and is based on analysis interval averages.)

  • Interpretations and Recommendations
    This release introduces context-sensitive explanations and next-step guidance for virtual machine, host, datastore, and cluster details. The Details Page now includes a link to view more information, which provides detailed explanations to troubleshoot a performance or capacity issue and guidance on next steps.
  • Consider Stress Feature
    This release introduces a Consider Stress option that affects the calculation of Capacity Remaining and Time Remaining metrics and corresponding badge scores. When Consider Stress is enabled, vCenter Operations Manager considers hourly peak values of demand and limited demand that cause accumulation of stress conditions over time. (When Consider Stress is disabled, the behavior matches the 5.0 release and is based on analysis interval averages.)
  • Custom Reports (Experimental)
    This release introduces an experimental feature for configuring user-defined and pre-defined custom reports. You can use the XML-based reporting feature to generate capacity optimization reports at the custom group level, and to run custom reports that contain performance and operational data.
  • Custom User Interface Enhancements
    This release provides enhancements to the Custom user interface, including:
    • Configuration of multi-level alert rules: You can now configure complex alert rules that evaluate multiple conditions on related resources. See Configuring multi-level alert rules for vCenter Operations Manager Enterprise (KB 2021314).
    • Dashboard import and export: You can now transfer and share pre-configured dashboards across users and environments using a new set of commands.
    • Consolidated alerts: Available only in the Custom UI, you can configure consolidated alerts through advanced configuration using an XML template.
  • Internationalization
    The vCenter Operations Manager 5.6 user interface and online help are available in Simplified Chinese, German, and Japanese. The vCenter Operations Manager 5.6 documentation set is also available in these languages.

Before You Begin

Review this section before you begin installing and configuring vCenter Operations Manager.

Virtual Appliance Deployment

Always use a VMware vSphere Client to connect to a VMware vCenter Server and deploy the vCenter Operations Manager virtual appliance through the vCenter Server. The vCenter Operations Manager virtual appliance should be deployed on an ESX/ESXi host version 4.0 or later that is managed by VMware vCenter Server 4.0 Update 2 or later.

Licensing vCenter Operations Manager 5.6

This paragraph contains important notes on vCenter Operations Manager 5.6 licensing.

  • Important License keys for vCenter Operations Management Suite 5.6 with vCenter Server 5.0 or 4.1
    The vCenter Operations Management Suite 5.6 supports a Single Suite license key to enable functionality across all the suite components. To use this Suite license key with Operations Manager and Infrastructure navigator (VIN), you must have at least one instance of vCenter Server 5.1.

    To use vCenter Operations Manager and vCenter Infrastructure navigator components with vCenter Server versions 5.0 or 4.1, obtain the compatible license keys for these products from the text file located under each of the Product downloads: For vCenter Server version 5.1, the single Suite license keys for vCenter Operations 5.6 Standard/Advanced/Enterprise is supported across all the components in the suite.
  • After you apply the license, you must restart vCenter Operations Manager service or run the command vcops-admin license update from the UI VM as admin to refresh the vCenter Operations Manager license.
  • vCenter Operations Manager is licensed as an asset to the vCenter Server that it monitors. You must register vCenter Operations with a vCenter Server before you assign the 5.6 license. To register vCenter Operations Manager with a vCenter Server, open the vCenter Operations Manager Administration portal and follow the procedure described in the VMware vCenter Operations Manager Deployment and Configuration Guide.
  • All license management tasks are performed in the vSphere Client. You cannot assign licenses in the vCenter Operations Manager Administration portal. Follow the instructions from the VMware vCenter Operations Manager Deployment and Configuration Guide to assign a license.
  • You must reassign the 5.6 license each time you register vCenter Operations Manager with a vCenter Server. You create a new asset each time you register vCenter Operations Manager with a vCenter Server. Therefore, you must reassign the vCenter Operations Manager license each time you register with a vCenter Server, even if the vCenter Server has been registered before. For example, if you unregister the vCenter Operations Manager virtual appliance from a monitored vCenter Server and then register the appliance with the same vCenter Server, vCenter Operations Manager creates a new asset on this vCenter Server. However, the license remains associated with the vCenter Operations Manager asset that corresponds to the previous registration. Therefore, you must de-assign the license from the old asset and assign it to the latest created asset in order to access the vCenter Operations Manager user interface.
  • vCenter Operations Manager operates in Foundation mode if no license key or an incompatible license key is applied. Assign the license key for the edition you purchased.

Product Compatibility

Refer to the VMware Compatibility Guide for more information about VMware certified compatibility for vCenter Operations Manager: http://www.vmware.com/resources/guides.html.

vCenter Operations Manager 5.6 supports the following.
  • vCenter Operations Manager supports VMware vCenter Server 4.0 Update 2 and later, managing hosts running ESX/ESXi 4.0 and later.

    Note: This release does not support Beta versions of vCenter Server 5.1 and ESXi 5.1.

  • vCenter Infrastructure Navigator 2.0 is the recommended version for vCenter Operations Manager 5.6.
  • vCenter Operations Manager for View is not officially supported for the vCenter Operations Manager 5.6 release.

Browser Support

  • Internet Explorer for Windows 8.0 and 9.0
  • Note: There are some limitations with the Dashboards feature in the Custom user interface if Internet Explorer 8 is used.

  • Mozilla Firefox 3.6 and above

The minimum supported browser resolution is 1024 by 768 pixels.

If you use the vSphere Client to connect to the vCenter Operations Manager monitoring interface, verify that a supported Internet Explorer version is installed where the vSphere Client runs.

User Accounts

  • To register vCenter Operations Manager with a vCenter Server, you must provide the minimum set of user credentials for that vCenter Server. The minimum privileges required to register and unregister vCenter Operations Manager with a vCenter Server are Global: Licenses and Extension: Register extension, unregister extension, update extension.
  • The user account you use for collecting data with vCenter Operations Manager determines the scope and accuracy of the monitoring data.
    • vCenter Operations Manager does not require administrator privileges to collect data from a vCenter Server. However, the scope of data collected depends on the privileges of the user you assign as the Collection user on the vCenter Operations Manager Administration portal. The minimum privileges required to collect data are Global: Health and Storage Views: View.
    • vCenter Operations Manager calculates metric values based only on visibility the Collection user has to the inventory. If certain objects are not visible, the values for these objects are not taken into account when calculating metrics for their container objects.
  • The minimum privilege required to repair a vApp with broken connectivity using the vCenter Operation Administration interface is Read-only.
  • The default credentials for the Administrator user are admin/admin. To improve security, vCenter Operations Manager requires you to change these credentials during CLI registration or when you first access the vCenter Operations Manager Administration portal.
  • The default credentials for the root user on the vCenter Operations virtual appliance are root/vmware. You are prompted to change the admin and root account passwords during CLI registration or when you first access the vCenter Operations Manager Administration portal.

Top of Page

Upgrading from a Previous Version

This section contains two sets of upgrade procedures:

Upgrade from any vCenter Operations Manager 5.0.x version

This procedure is applicable when updating to vCenter Operations Manager 5.6 vApp from the following product versions.
  • vCenter Operations Manager 5.0, 5.0.1, 5.0.2, and 5.0.3, including any Hotfix versions.
Important For upgrade requirements, including important information about disk space requirements, refer to the VMware vCenter Operations Manager Deployment and Configuration Guide.
  1. Save the .pak file for the vCenter Operations Manager 5.6 build to your local storage.
  2. Log in to the Administration portal using the admin user credentials.
  3. On the Update tab, click Browse and select the .pak file that you saved to local disk.
  4. Click Update.
  5. Accept the EULA by selecting the check box and click OK.
  6. Accept and confirm the update.
  7. The update process will start, and the Administration portal page might refresh after some time and ask you to login again.
  8. Log in to the Administration portal, wait for the update to complete, and verify that the Upgrade tab indicates a successful upgrade.
    Note: You might need to refresh the browser to view the updated product version and build number.
  9. Log in to the vCenter Server that manages the license for vCenter Operations Manager, and apply the new vCenter Operations Manager 5.6 license key.
    Note: You must re-apply the new license key in the vCenter Server after the upgrade.
  10. If you do not, you will see reduced functionality in the vCenter Operations Manager interface.
  11. In the Administration portal, navigate to the Status tab and restart all services.
  12. Log in to the vSphere Client or the Custom UI to verify that the vCenter Operations Manager interface is displayed properly.

Upgrade from vCenter Operations 1.0.x or Capacity IQ 1.5.x

This procedure if applicable if you need to import data from vCenter Operations Manager 1.0.x or Capacity IQ 1.5.x.

Note: When you deploy the 5.6 vApp and log in to the Administration portal for initial configuration, you are given the option to import data from vCenter Operations 1.0.x or Capacity IQ 1.5.x. Proceeding with that option will cause data problems. You cannot upgrade directly from vCenter Operations 1.0.x and/or Capacity IQ 1.5.x to vCenter Operations Manager 5.6. You must follow the procedure described in this document.
  1. Deploy vCenter Operations Manager 5.0.3 vApp and choose to import data from vCenter Operations 1.0.x and/or CapacityIQ 1.5.1 in the first-time initialization wizard of the Administration interface.
  2. After the vCenter Operations Manager 5.0.3 finishes data import, allow the deployment to run for at least two hours.
  3. Perform an in-place upgrade to vCenter Operations Manager 5.6 using the .pak file and the procedure described in the previous section.

Known Issues

This section contains known issues for this release.

Installation and Upgrade

  • Change events and vCenter Operations Manager 5.6 and vCenter Configuration Manager (VCM) 5.5.x interoperability
    Change event collection from VCM in vCenter Operations Manager 5.6 does not work for VCM versions older than 5.6.
    Workaround: To ensure event collection continues unimpeded, upgrade to VCM 5.6 or contact Global Support Services to determine if your environment is eligible for the scripted fix provided in KB 2040281. For upgrade instructions, see the VCM 5.6 Installation Guide. The guide is available at https://www.vmware.com/support/pubs/vcm_pubs.html.
  • Java 7 errors are logged during installation and upgrade
    The following types of errors appear in the file updatecoordinator.log when you install or upgrade to vCenter Operations Manager 5.6:
    warning: /etc/init.d/jexec saved as /etc/init.d/jexec.rpmsave
    Unpacking JAR files... rt.jar...
    Error: Could not open input file: /usr/java/jre1.7.0_07/lib/rt.pack
    jsse.jar...
    Error: Could not open input file: /usr/java/jre1.7.0_07/lib/jsse.pack
    charsets.jar...
    Error: Could not open input file: /usr/java/jre1.7.0_07/lib/charsets.pack
    localedata.jar...
    Error: Could not open input file: /usr/java/jre1.7.0_07/lib/ext/localedata.pack
    Workaround: None, but the errors are harmless and can be disregarded.

  • After upgrading from vCenter Operations Manager 5.0.x to 5.6, the Generic scoreboard widget reports an error
    The Generic scoreboard wizard reports the error "NumberFormatException..." after upgrading from VCenter Operations 5.0.x to 5.6.
    Workaround: Change the ranges to boundaries for all resources. For example, if the configuration was set to Yellow Bound 30 - 50, Orange Bound 50 - 70, and Red Bound 70, in the Selected Metrics section, change the ranges to boundaries: Yellow Bound 30, Orange Bound 50, and Red Bound 70. Click OK to save the settings.
  • Product version and build number do not appear in vCenter Operations Manager Administration portal
    After you upgrade from vCenter Operations Manager 5.0.x to 5.6, the product version and build number do not appear in the left corner of the vCenter Operations Manager Administration screen.
    Workaround: Refresh your browser to load the new version of JavaScript and make the vCenter Operations Manager Administration pages work correctly.
  • vCenter Configuration Manager registration allows you to select SQL Authentication or Windows Authentication, but VCM supports only Windows Authentication
    When registering vCenter Configuration Manager in the vCenter Operations Manager Administration Portal, you are allowed to select SQL Authentication. VCM supports Windows Authentication, not SQL Authentication.
    Workaround: When you register VCM, select Windows Authentication as the Authentication method.
  • Change events and vCenter Operations Manager 5.6 and vCenter Configuration Manager (VCM) 5.5.x interoperability
    Change event collection from VCM in vCenter Operations Manager 5.6 does not work for VCM versions older than 5.6.
    Workaround: To ensure event collection continues unimpeded, upgrade to VCM 5.6. For upgrade instructions, see the VCM 5.6 Installation Guide. The guide is available at https://www.vmware.com/support/pubs/vcm_pubs.html.

  • World metrics are lost after upgrading to vCenter Operations Manager 5.6
    When you upgrade from vCenter Operations Manager from 5.0.x to 5.6, all of the historical data gathered for World before the upgrade is lost. After the upgrade, vCenter Operations Manager starts collecting new metrics for World and the calculated data is displayed.
    Workaround: None.
  • Badge scores and metrics for World object does not display after the upgrade. The "?" value displays
    After upgrading from vCenter Operations Manager 5.0.x to 5.6, badge scores and metrics for World object do not display in the vSphere user interface even though they are being collected normally. This issue occurs because some of the scores and derived metrics are re-calculated due to the change in the formulas.
    Workaround: If the information does not appear after a few hours after the upgrade, restart the vCenter Operations Manager vApp. This resets all the badge scores and metrics. Also, you can click the "?" to view information about the stressed hosts.
  • Groups created by different vCenter Servers, and monitored from the same instance of vCenter Operations Manager, display in the vSphere Client Inventory
    Adapter-based groups from all monitored vCenter Server instances are visible in the vCenter Operations Manager plugin inside the vSphere Client. If you click an adapter-based group created from another instance of vCenter Server, an error message or JavaScript error displays.
    Workaround: None.
  • Groups appear with missing name information after upgrading to vCenter Operations Manager 5.6
    If you created groups in vCenter Operations Manager 5.6 Beta, and upgrade to version 5.6, the name of the group is missing from Capacity Views and Reports.
    Workaround: From the Groups navigation pane, rename the group (you can use the original group name). To do this, select the group and click the Edit group option from the Actions drop-down menu. Assign the group a name and click OK. The group name is updated in the database and also becomes visible in Capacity Views and Reports.
  • Upgrading from 5.0.3 HotFix to version 5.6 overwrites consolidated-alert-definition.xml
    Upgrading from 5.0.3 Hot Fix to version 5.6 will overwrite any changes made to the consolidated-alert-definition.xml file located in /usr/lib/vmware-vcops/user/conf/analytics on the Analytics VM.
    Workaround: Create a backup copy of /usr/lib/vmware-vcops/user/conf/analytics/consolidated-alert-definition.xml and overwrite the file after the upgrade is complete.
  • vCenter Operations Manager is unable to retrieve health data from a host
    If you deploy vCenter Operations Manger and register using the vCenter Server Appliance, the Auto Deploy service is not running by default. If the service is not running, vCenter Operations Manager reports the error: "Unable to retrieve health data from https://<host>:6502//vmw/rdb/health-inf" causing Health for the vCenter Server to equal zero.
    Workaround: To enable Auto Deploy, start Auto Deploy in the vCenter Server Appliance:
    /etc/init.d/vmware-rbd-watchdog start

vApp Management

  • The FilterPluginConfEditor tool cannot be used in the vApp Custom UI
    You cannot use the FilterPluginConfEditor tool in a vCenter Operations Manager vApp installation.
    Workaround: Run FilterPluginConfEditor on a remote machine and copy the XML file to the vApp. To install FilterPluginConfEditor on a remote machine, install the JDK and copy the \tools\FilterPluginConfEditor folder to the remote machine.

General

  • OVF deployment on the vSphere Web Client is not supported with Internet Explorer
    If you use the vSphere Web Client (also known as the vSphere Next Generation Client) with Internet Explorer to deploy the vCenter Operations Manager OVF file, the wizard displays junk characters.
    Workaround: Use Firefox or Chrome instead of Internet Explorer, or deploy the OVF by using the vSphere Client.

  • Japanese and Chinese characters are dropped in User Audit Report (PDF format)
    In the Custom UI, create a user or group with Japanese and Chinese character in the username or group name (by choosing Admin > Security > User Management). When you choose User Audit Report from the Admin menu and select PDF format, the Japanese and Chinese characters are dropped from the PDF report.
    Workaround: Select HTML format to generate the User Audit Report.
  • After login, the vSphere user interface indicates that vCenter Operations Manager is being configured
    On a large deployment of vCenter Operations Manager, you might see the following message after you log in to the vSphere user interface: vCenter Operations Manager is being configured to work with your virtual environment. You might also see errors such as: 500. The call failed on the server. You might have initiated the service startup manually, or the service might have started because of operations such as vApp startup or a vCenter registration or unregistration activity from the Administration interface. These messages appear because the Analytics service is still initializing and the data is not available for the vSphere user interface to display.
    Workaround: On a large deployment, you might need to wait up to 20 minutes after a service startup for the Analytics service to finish initialization before you can use the vSphere user interface.
  • On Internet Explorer 9, attempting to upload a new SSL certificate results in an endless progress bar On Internet Explorer 9 only, attempting to upload a new SSL certificate for the first time causes the pop-up window with the progress bar run forever. No error message appears, although if opened from different window, the vCenter Operations Manager vSphere UI is functional.
    Workaround: Refresh the page after one minute.

  • Limitations with Mozilla Firefox and Google Chrome browsers
    If you open vCenter Operations Manager from the vSphere Web Client using Mozilla Firefox or Google Chrome, there are some limitations, including the following:
    • Closing the vSphere Web Client invalidates the vCenter Operations Manager session.
    • The logout link from vCenter Operations Manager fails.
    • The Troubleshoot button fails after one attempt.
    Workaround: Use a supported version of Internet Explorer for vCenter Operations Manager.
  • Setting the vApp time zone to Mexico/Sonora causes a 404 error in the vSphere user interface
    If you set the vApp time zone to Mexico/Sonora, the vSphere user interface displays a 404 error.
    Workaround: Set the time zone to Mountain Standard Time - Arizona. This time zone provides the same time as the Mexico/Sonora time zone and does not cause the 404 error.

Troubleshooting

  • vCenter Operations Manager 5.6 does not support vSphere 5.1 SSO authentication
    The 5.6 release of vCenter Operations Manager does not support authentication with Single Sign On (SSO) support, introduced in the vSphere 5.1 release. User accounts maintained using SSO will not function with vCenter Operations Manager.
    Workaround: Use the traditional authentication mechanism and user registration process(the same used previous vSphere versions).
  • Environment Overview page in the Custom UI loads slowly when it displays more than 100 resources per page
    If you set Resources Per Page to more than 100 on the List tab, the Environment Overview page in the Custom UI is slow to load.
    Workaround: Set Resources Per Page to 100.
  • ActiveMQ might fail to start because of data file corruption
    When you restart vCenter Operations Manager services, the ActiveMQ service might fail to start after stopping because its data file has been corrupted. When this problem occurs, you might see the following error in the /data/vcops/log/activemq.log file on the Analytics virtual machine: Failed to start ActiveMQ JMS Message Broker. Reason: java.io.FileNotFoundException: /data/activemq/data/kahadb/db.free (No such file or directory)
    Workaround:Delete all of the files in the /data/activemq/data/kahadb directory and start the vCenter Operations Manager services again. ActiveMQ should start.
  • Connection to vCenter server is lost and cannot be re-established
    If connections to the vCenter server are lost due to a network outage or the vCenter server going down, these connections might not be reestablished. The lost connections can result in no metrics being collected after the network is restored or the vCenter server comes back up.
    Workaround:Restart the collector service.

User Interface

  • The Change Default Policy Configuration link doesn't work in Germany, Japanese, and Simplified Chinese UIs
    In the View Information panel on the Views tab under the Planning tab in the vSphere UI, if you click Change Default Policy Configuration, the Edit Policy dialog box appears but you cannot edit the policy.
    Workaround: Click the Configuration link at the top right, select Default Policy from the list, and click the Edit Policy icon.
  • Normal state and unknown state population counts do not match
    The normal state and unknown state population count under Environment > Overview does not always match with the population count under All Metrics for the World object and groups.
    Workaround: For an accurate population count, refer to the All Metrics count.
  • Custom Groups do not filter data based on member objects
    Some badges and planning views do not apply to all objects. For example, the Stress badge is not applicable to datastores, and Capacity views are not applicable to virtual machines. The Custom Groups functionality does not limit the display of data to only those objects to which the data applies. As a result:
    • Question marks appear for the Stress badge when a custom group contains only datastores
    • Capacity views are listed, but empty for custom groups that contain only virtual machines.
    Workaround: None.
  • Virtual machines that do not have VMware Tools show ? for Disk Space
    Disk Space under the Time Remaining badge shows ? for virtual machines that do not have VMware Tools installed and running.
    Workaround: Install and start VMware Tools on the affected virtual machines.
  • vCenter Operations Manager vSphere user interface reports errors when accessing certain objects in the Inventory
    If you log in to the vSphere user interface of vCenter Operations Manager using your vCenter Server user credentials, you may see error messages while accessing certain objects. These objects belong to a vCenter Server instance that is not accessible and permission checks fail against those objects.
    Workaround: Log in to the vSphere UI as admin.
  • The Dashboard displays the World view after refreshing the page
    If you refresh the view of a selected object in the navigation tree, the Dashboard displays the World view instead of the view for the selected object.
    Workaround: Refresh the page a second time to view the selected object.
  • The Capacity Remaining chart on the Dashboard tab and the Capacity Remaining values on the Views tab under Planning might display very high values for virtual machine capacity
    For container objects where all virtual machines are powered-off during the view interval, the capacity remaining value is calculated based on disk space resources only. When the datastores connected to the host have large remaining capacity compared to the average of virtual disk space usage, the value for virtual machine count capacity and virtual machine count capacity remaining might grow very high.
    Workaround: None.
  • Capacity views might be mismatched
    When you switch between the Host and Clusters and Groups inventory views, capacity views such as Idle Machines and Stressed Hosts and Clusters might be mismatched around hourly boundaries. This problem is caused by a delay in data persistence between the different capacity views.
    Workaround: The mismatch is typically resolved within one to ten minutes, depending on the inventory size.

  • Capacity views do not show data for the Virtual Center or World object
    Capacity views do not show data for the Virtual Center or World object, but data appears for other objects. This problem is caused by an error in inventory data collection.
    Workaround: Restart vCenter Operations Manager. The data appears in about an hour.

  • Disk space waste for World is less than sum of disk space waste of all vCenter servers.
    Disk space waste for World (and other groups) is computed by aggregating virtual machine waste. For all other resources in the environment (vCenter server, cluster, datastore, and so on), it is computed by aggregating the datastore waste. Datastore waste accounts for template usage, which is not present in the virtual machine waste aggregation. This computation can cause the World disk space waste to show a smaller value.
    Workaround: None

  • The total number of alerts displayed do not match
    There is discrepancy in the number of alerts displayed and alert counts do not match based on the alert type and source of the alert. The reasons for this can be one of the following:
    • The label of administrative alerts is imprecise, and the alert type can confused with other kinds of alerts.
    • The alerts on the grid chart do not match because the data sources are derived from calculated metrics from objects based on relationships.
    • The number of alerts reported are from the last data point list and the accurate numbers that are stored inside the analytics cache are not yet written to the FSDB.
    Workaround: None.
  • Events are displayed inconsistently in the correlation graph
    Events can be displayed inconsistently for a given timeline in the correlation graph on the Events tab. The number of events shown in the graph might vary depending on which badge is selected. This variation can happen even if the event filter and chosen timeline are consistent while switching between badges. Workaround: This problem will resolve itself within five to ten minutes.
  • Key metrics values are not displayed for Custom Groups
    When viewing the details for the Key Metrics of a Custom Group, Key Metrics do not display. Key Metrics are only computed when group members include Virtual Machines, Hosts, or Datastores.
    Workaround: None.
  • Changes in effective policies for groups are not immediately visible on the group members
    If you change the effective policy on a group, there might be a delay of about a minute before the system applies the policy to all members of the group.
    Workaround: To update the effective policy for a group member, click the Refresh button in the upper middle of the vCenter Operations Manager window. This should reflect the new effective policy if the system has already updated it.
  • Descendant equal to GROUP NAME creates a group that has only direct children members from GROUP NAME
    If you create a group and select Descendant of = GROUP NAME, the new group includes only direct children members. The new group does not include indirect children members. This behavior is different from Descendent of = HOST, CLUSTER, DATACENTER, VC, or WORLD NAME, which causes the new group to include all descendants of the object, including direct and indirect children members.
    Workaround: To choose the other hierarchy children, either select from the navigation tree to always include objects or add a rule set that makes descendants of direct child members.

  • If all objects in groups are virtual machines, the Population Dashboard shows Capacity Remaining and Density
    Capacity Remaining and Density values are calculated based on the container objects (Host/Clusters) limits. If the group contains only virtual machines, those values do not have a meaning since there are no container objects. Groups containing only virtual machines as objects should not display information about Capacity Remaining and Density.
    Workaround: None
  • Capacity pages don't load when clicking on some custom groups
    When creating new group types, the Group type name cannot belong to one of these reserved internal keywords:
    • VirtualMachine
    • HostSystem
    • ResourcePool
    • ClusterComputeResource
    • Datacenter
    • ComputeResource
    • Datastore
    • VMwareAdapter Instance
    • VCMAdapter Instance
    • VinAdapter Instance
    • ContainerAdapterInstance
    • World
    If you use these names and create a group with that type, capacity views will not load for those objects.
    Workaround: If you accidentally use one of these keywords, rename the group type of the group, and the capacity views will load.
  • The VM Health badge on the Relationships tab is in yellow or red, but the Applications Health badge is green while both badges have the same values The thresholds used for virtual machines are different from the thresholds used for Applications. Currently, the color scheme for Applications follows the thresholds set in section 2a: Infrastructure badge thresholds of the policy configuration dialog box. The Infrastructure badge thresholds apply to all object types except virtual machines and group objects.
    Workaround: None.
  • The Members List on the Scoreboard tab is not updated in real-time when you change the view in the Custom Overview pane, and the Status filter is active. If you go to the Scoreboard tab and use the STATUS FILTER to filter objects in a particular state (for example, Normal State), the Members List pane displays objects in that state for the selected View (for example, Health).If you select another View (for example, Efficiency), the Members List pane does not change to display the objects that have normal Efficiency.
    Workaround: Click the Refresh button in the upper section of the vCenter Operations Manager window.
  • The compliance badge is not available in capacity views and reports
    Metrics for the compliance badge (metric key = badge|compliance) are not available in capacity views and reports.
    Workaround: None
  • No data or a question mark (?) appears for custom group Compliance badge score on the View tab
    When viewing the Compliance Breakdown view for a custom group, no data or a question mark (?) appears rather than a compliance score. The compliance score that appears for the badge should be the aggregated compliance scores for the member objects.
    Workaround: None
  • Cannot configure Alerts widget to show only Compliance alerts
    In the Custom user interface, users have the ability to configure the Alerts widget to show alerts for specific Alert subtypes. Open the Alerts widget in edit mode and in the Filter by section click the Alert Type link. In the Risk section of the Pick Alert Type dialog box, there is no Compliance toggle to filter Compliance alerts.
    Workaround: None
  • Compliance template and compliance mapping names that include the | character are incorrectly displayed If a VCM compliance template or compliance mapping includes the | character, the template names that appear in vCenter Operations Manager might be incorrect or unreadable.
    Workaround: In VCM, create or modify the compliance templates and mappings to ensure that they do not include the | character. The procedures for creating or editing compliance templates or mapping are provided in the VCM online help or the VCM Administration Guide.
  • When VCM is integrated, some panels are shown for objects to which they do not apply
    When VCM is integrated with vCenter Operations Manager, these panels appear for the following objects, yet they do not apply to those objects:
    • Virtual machines: Capacity, Density, Reclaimable waste
    • Datastores: Stress, Density
    • Groups: For groups that only contain virtual machines or datastores, the corresponding panels listed above appear.

    Workaround: None

vCenter Operations Manager in the vSphere Web Client

  • No data displays on the Workload widget for folder objects
    No data displays on the Workload widget for folder objects in the vSphere Web Client.
    Workaround: None.
  • Error message: The selected object does not exist in VCOps server: group-d1
    The error message The selected object does not exist in VCOps server: group-d1 might appear instead of the Health badge under any of the following circumstances.
    • If you select from the Inventory tree a vCenter server object that has no child objects attached.
      Workaround: None.
    • If you select from the Inventory tree an object that is not yet created in the vCenter Operations Manager database.
      Workaround: Wait for 5 to 10 minutes until the object is added to the database.
  • The Health tab is missing under the Monitor tab after forced registration with a vCenter Server and subsequent unregistration
    If an instance of vCenter Operations Manager is registered with a vCenter Server and you try to register a second instance of vCenter Operations Manager with the same vCenter Server, you can select whether to force the registration of the second instance. When you force the registration of the second instance, you override the access of the vCenter Operations Manager plug-in for the vSphere Web Client to the first instance of vCenter Operations Manager. If you override the connection to the first instance, and then unregister the second instance from the vCenter Server, the Health tab no longer appears in the vSphere Web Client.
    This is because when you unregister the second instance of vCenter Operations Manager from the vCenter Server, you delete the extension point that is used to visualize the Health tab. The first instance of vCenter Operations Manager cannot recover the extension point automatically. Though the first instance is still registered with vCenter Server, there is no extension point that the vCenter Operations Manager plug-in for the vSphere Web Client can use to display health data.
    Workaround:
    1. Navigate to the ExtensionManager of the vCenter Server and use the administrator credentials to log in.
      The URL format is https://<VC-IP-address>/mob/?moid=ExtensionManager&doPath=extensionList%5b%22com%2evmware%2evcops%22%5d%2eclient
      If vCenter Server is running on a virtual machine, log in as root user.
    2. Verify that the vCenter Operations Manager extension point is missing.
      Search the extension list for the following value: extensionList["com.vmware.vcops"]
    3. Update the registration with the vCenter Server on the first instance of vCenter Operations Manager.
      1. Navigate to the Administration portal of the first vCenter Operations Manager instance.
        The URL format is https://<ui-vm-IP-address>/admin/
      2. Click Update next to the vCenter Server on which the extension point is missing.
      3. Type the passwords for the registration and the collector user, and click Test Connection.
      4. Click Apply and Close.

Top of Page

API

  • The result of getBusinessServiceConfigAsXml does not contain resource identifiers
    This might cause problems interpreting the result of the API call since resources might not be uniquely identified.
    1. The getBusinessServiceConfigAsXml method returns an XML string containing business service configuration. The resource tag in the result does not contain identifiers. This is a limitation with no workaround. As a result, the XML received from getBusinessServiceConfig call posted to the configBusinessService method might not produce the same result, as configBusinessService now requires identifiers to be present.
    2. The background issue is that in 5.6 configBusinessService was fixed to take into account resource identifiers. This behavior is consistent with the product logic and documentation. It might brake existing client applications that used to call the API in a different way. Before the fix, the API method only used resource name for identification and could produce inaccurate results by adding all resources with a matching name into specified tiers.

    Workaround: Specify identifiers as part of the configBusinessService call. If identifiers are unknown, they can be looked up using the lookupResource API call before being added into the business service config XML.

Documentation

    The following product changes were not described in the release documentation.
  • VMWARE-VCOPS-EVENT-MIB.mib file changed
    The VMWARE-VCOPS-EVENT_MIB.mib file contains information that the receiving party needs to interpret the SNMP traps that vCenter Operations Manager (Custom UI) sends. The Object Identifier (OID) for vCenter Operations Manager (Custom UI) is changed from 19004 to 6876 in this MIB file.
  • New menu next to Search on Environment Overview page
    A new drop-down menu has been added next to the Search text box on the Environment Overview page in the Custom user interface. You can use this drop-down menu to select a column name and search by column, or you can select All to search all columns. For example, you can select Name to search the Name column.
  • All and group options for dashboard commands
    For the dashboard import, dashboard delete, and dashboard reorder commands, you can use one of the following options instead of specifying a user name:
    * --all
    * --group:<group_name[,<group_name>]

    The --all option applies the command to all user accounts. The --group:<group_names[,<group_name>] option applies the command to all user accounts that belong to the specified user groups. For example, the command dashboard import group:Administrators,Operators "templates\MyDashboard.bin" imports the dashboard MyDashboard.bin to all user accounts that belong to the Administrators and Operators user groups.

    The dashboard import command also has a --set <rank> option that enables you to set the dashboard order. For example, the command dashboard import MyUser2 "dashboards/MyDashboard.bin" --set 1 imports the dashboard MyDashboard.bin and makes it the first dashboard in the dashboard list for the user MyUser2.
  • Incorrect examples in topic Determining the Underused and Stressed Capacity Thresholds of the vSphere UI help
    Topic Determining the Underused and Stressed Capacity Thresholds contains examples that suggest that the % Stressed and % Underused metrics are time percentages while they are actually area percentages. Please ignore the examples in this topic.
  • Missing information on consolidated alerts in the Custom UI documentation
    See Aggregating and Filtering Alerts in vCenter Operations Manager 5.6 (Custom UI) (KB 2039020) for details.

Top of Page