VMware vCenter Operations Manager 5.8
VMware

VMware vCenter Operations Manager 5.8 Release Notes

vCenter Operations Manager 5.8 | Build 1448123

Last Document Update: 10 DECEMBER 2013

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

What's New

vCenter Operations Manager 5.8 is the latest release of VMware's integrated operations suite, converging performance, capacity, and configuration management. This new release introduces the following enhancements.

Improved Enterprise Readiness

  • Optimized query execution to improve performance at scale.
  • Enhanced authentication options with new active directory integration for authentication.
  • Improved security with upgrades to the OS and runtime environment.

Expanded Integration

  • New integration with VMware vCenter Log Insight using a vCenter Operations Manager Content Pack that enables you to monitor your vCenter Operations Manager infrastructure.
  • Expanded integration with vCenter Hyperic using the vCenter Operations Management Pack for vCenter Hyperic. This management pack provides many new capabilities, such as:
    • Support for Microsoft Hyper-V servers, including out of the box dashboards for troubleshooting and performance analysis.
    • Support for Microsoft Exchange and SQL Servers, with out of the box dashboards for troubleshooting.
  • Several new management packs are available for download. Check the Cloud Management Marketplace on the VMware Solution Exchange for more details: https://solutionexchange.vmware.com/store/vcops.

Top of Page

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.

Note: Beta versions of vCenter Server and ESXi hosts are not supported in this 5.8 release.

Licensing vCenter Operations Manager 5.8

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

  • Important License keys for vCenter Operations Management Suite 5.8 with vCenter Server 5.0 or 4.1
    The vCenter Operations Management Suite 5.8 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.8 Standard/Advanced/Enterprise is supported across all the components in the suite.
  • After you apply the license, you can wait for the license manager cache to update automatically, which occurs in twenty minute intervals. For immediate license refresh, click the Reload button on the Status tab of the Administration portal 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.8 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.8 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.
  • Existing EMC licenses will not work after upgrading vCenter Operations Manager 5.6 to 5.8. If you upgrade vCenter Operations Manager 5.6 having EMC license key to 5.8, the existing EMC license key will become invalid and vCenter Operations Manager will run in Foundation mode. Apply the new EMC DLF license key supported by vCenter Operations Manager 5.8. If you apply the old license key, it will be accepted by vCenter Server but will not be considered by vCenter Operations Manager 5.8.

Top of Page

Product Compatibility and Requirements

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.8 supports the following:
  • VMware vCenter Server 4.0 Update 2 and later, managing hosts running ESX/ESXi 4.0 and later.

    Note: Beta versions of vCenter Server and ESXi hosts are not supported in this 5.8 release.

  • vCenter Infrastructure Navigator 2.0
  • vCenter Configuration Manager 5.6
  • vCenter Operations Manager for View 1.5

Browser Support

vCenter Operations Manager 5.8 supports the following:
  • Google Chrome 24 and 25
  • Internet Explorer for Windows 8.0 and 9.0
  • Note: There are some limitations with the Dashboards feature in the custom interface if Internet Explorer 8 is used.

  • Mozilla Firefox 18 and higher

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.

vApp Requirements

The following section lists the computing requirements and assumptions for the vCenter Operations Manager vApp.

Balanced Profile
  • Maximum number of objects: 12K, 2.2 million metrics
  • Memory
    • Analytics VM: 21GB
    • UI VM: 26GB
  • vCPU
    • Analytics VM: 8 vCPU
    • UI VM: 8 vCPU
Full Profile
  • Maximum number of objects: 12K, 5 million metrics
  • Memory
    • Analytics VM: 63GB
    • UI VM: 26GB
  • vCPU
    • Analytics VM: 24 vCPU
    • UI VM: 16 vCPU

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 hosting vCenter Server credentials are needed to repair the vApp with broken connectivity using the vCenter Operations Manager Administration interface. The minimum privilege required for this credential 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 when you first access the vCenter Operations Manager Administration portal.

Top of Page

Upgrading from a Previous Version

This section includes the following upgrade procedures:

Upgrade from any vCenter Operations Manager 5.x version

This procedure is applicable when updating to vCenter Operations Manager 5.8 vApp from the following product versions.
  • vCenter Operations Manager 5.0, 5.0.1, 5.0.2, 5.0.3, 5.6, 5.7, 5.7.1, and 5.7.2, including any Hotfix versions.

The upgrade to vCenter Operations Manager 5.8 also requires the operating system upgrade described in: Upgrade the OS to SLES 11 SP2 for vCenter Operations Manager 5.8.

Important For upgrade requirements, including important information about disk space requirements, refer to the VMware vCenter Operations Manager Deployment and Configuration Guide.

VMware recommends that you take virtual machine snapshots before you upgrade the vApp. After the upgrade is successful, delete the snapshots.

  1. Save the .pak file for the vCenter Operations Manager 5.8 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.8 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 interface to verify that the vCenter Operations Manager interface is displayed properly.

Upgrade the OS to SLES 11 SP2 for vCenter Operations Manager 5.8

This procedure is applicable when performing an in-place vApp OS upgrade to SUSE Linux Enterprise Server (SLES) 11 SP2. An OS upgrade is required to run vCenter Operations Manager 5.8.
  1. Verify that vCenter Operations Manager 5.8 is installed and running.
  2. Back-up the UI virtual machine and the Analytics virtual machine.
  3. Download or copy the SLES 11 SP2 PAK file from the VMware download site for vCenter Operations Manager to the /data drive on the UI virtual machine.

  4. scp VMware-vcops-SP2-1381807.pak root@ip_address_of_webui:/data
  5. Start the SLES 11 SP2 upgrade, with the command:

  6. /usr/lib/vmware-vcops/user/conf/upgrade/va_sles11_sp2_init.sh
    /data/VMware-vcops-SP2-1381807.pak

    The process automatically upgrades both the UI virtual machine and the Analytics virtual machine.

  7. After the upgrade completes successfully, restart the vApp.
  8. Login to the vCenter Operations Manager UI to verify that it is working.

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

This procedure is 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.8 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.8. 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.8 using the .pak file and the procedure described in the previous section.

Top of Page

Resolved Issues

There are no resolved issues for the vCenter Operations Manager 5.8 release.

Top of Page

Known Issues

This section contains known issues for this release.

Installation and Upgrade

  • The vApp version of vCenter Operations Manager uses a suboptimal kernel IO scheduler
    The kernel IO scheduler is set to CFQ by default. Changing the setting to NOOP improves the performance.
    Workaround: After installing or upgrading vCenter Operations Manager, restart the vApp to activate the NOOP setting for the IO scheduler.
  • Unable to change the admin password after upgrade to vCenter Operations Manager 5.8
    vCenter Operations Manager 5.8 has implemented a stronger password policy. If the new admin password does not fit the policy, the password is not accepted.
    Workaround: Provide a new password that is a minimum of eight characters, with at least one upper, one lower, one digit, and one special character.
  • Some vCenter Operations Manager services fail to start following upgrade to vCenter Operations Manager 5.8
    In compliance with STIG, vCenter Operations Manager 5.8 implements a new security hardening measure that sets a password expiration period for the vCenter Operations Manager admin user. In the upgrade log, check for the message "admin user password has expired".
    Workaround: If your vCenter Operations Manager password is more than 365 days old, change the password before upgrading. In addition, the new password must fit the stronger password policy required for vCenter Operations Manager 5.8.
  • Admin interface shows License Mode "Unknown" and License Status "Expired"
    Beginning with the 5.7.2 release, the vCenter Operations Manager Standard Edition feature set is enabled with the Standard license for vCloud Suite or vSphere with Operations Management (vSOM) Suite. However, if a Standard license for vCloud or vSOM Suite that supported an earlier version of vCenter Operations Manager is used, the Standard Edition feature set will not be enabled and the admin interface will not recognize the license. Also, if vCenter Operations Manager 5.7.1 or earlier is installed with a new Standard license, the admin interface will not recognize the license.
    Workaround: Use the Standard license for vCloud or vSOM Suite that is compatible with the vCenter Operations Manager version that is running.
  • Custom views and reports are overwritten after upgrade
    If you upgrade to vCenter Operations Manager 5.8, and your custom views or reports are overwritten, it is because you are using the same view or report key as our out-of-the-box view and report key for 5.8.
    Workaround: To recover your version of a custom view or report, find the corresponding XML that contains your view or report definition. Change the view or report key and run the "update" command.
  • Problems with the registration of vCenter Configuration Manager
    You cannot register a vCenter Configuration Manager if the server address contains Non-ASCII characters, and you use Windows authentication method.
    Workaround: None.
  • Change events and vCenter Operations Manager 5.8 and vCenter Configuration Manager (VCM) 5.5.x interoperability
    Change event collection from VCM in vCenter Operations Manager 5.8 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.8:
    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.
  • 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.8, 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.
  • World metrics are lost after upgrading to vCenter Operations Manager 5.8
    When you upgrade from vCenter Operations Manager from 5.0.x to 5.8, 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.8, 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.
  • vCenter Operations Manager is unable to retrieve health data from a host
    If you deploy vCenter Operations Manager 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 interface
    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 <VCENTER-OPS>\tools\FilterPluginConfEditor folder to the remote machine.

General

  • System performance impacts data collection
    A large vCenter Management Operations deployment that manages many vCenters can experience a computational bottleneck when calculating world object group metrics during every data collection cycle.
    Workaround: The Analytics virtual machine in vCenter Operations Manager dynamically disables the world metrics calculation. No manual intervention is required.
  • In the vCenter Operations Manager custom environment, the datastore count in the Custom Overview displays zero.
    When the Datastore tag in the Environment Overview treeview is expanded, all of the listed datastores display datastore count "0". Resources related to the selected datastore are not visible.
    Workaround: None
  • '!' appears at the upper right corner of the Log Insight user interface, indicating that Log Insight could not send an alert to vCenter Operations Manager.
    This problem occurs when an alert title in Log Insight has punctuation or special characters such as '/' or '%'. If alerts integration between Log Insight and vCenter Operations Manager is enabled and an alert is triggered, Log Insight cannot send the alert.
    Workaround: Remove all punctuation and special characters from the alert title in Log Insight.
  • Log Insight launch in context from vCenter Operations Manager displays all messages instead of filtered messages.
    If the query string used to create the Log Insight alert includes special characters such as '/', Log Insight launch in context from vCenter Operations Manager displays all messages received in the last five minutes instead of displaying only the messages filtered by the query string and received five minutes prior to triggering the alert. This is because special characters are not properly encoded in the URL.
    Workaround: None
  • SSH Connection Fails Due to Cipher Mismatch
    Due to security enhancements in vCenter Operations Manager 5.7, you might encounter secure shell connection errors. For example, you might see the error "couldn't agree on a client-server cipher." vCenter Operations Manager 5.7 was updated to support only AES256-ctr and AES128-ctr ciphers for SSH client connections.
    Workaround: Upgrade SSH client tools (such as PuTTY) to a version that supports ctr based OpenSSH server ciphers.
  • The export to .csv file fails if there is no file name specified in Conf.properties file
    If you configure the Conf.properties file to export data to .csv file, and you provide the path of the file, the Repository Adapter does not create the file under the path specified in the conf.properties file.
    Workaround: Include a file name with the file path.
  • Additional privilege required to collect vCenter Health Service metrics
    The vCenter Server collection user is unable to collect information from the vCenter Health Service. The vCenter Server collection user instance used by vCenter Operations Manager requires a specific privilege to collect information from the vCenter Health Service.
    Workaround : Assign the following privilege to the vCenter server collection user.
    * Global.Health - Required to access the vCenter Health Service

    For more information on assigning privileges, please see "Granting Access to vCenter Operations" in the vCenter Operations Manager vApp Deployment and Configuration Guide.

  • Some Custom UI widgets lose configuration settings after upgrading from 5.0 hotfix to 5.7.x
    The Size By, and Color By settings selections highlights for Heat Maps are lost after upgrading, but the Heat Map displays data for the selected options only. The selection highlighting for Metric Weather Map, and Top-N Analysis widgets is lost after upgrading, but the filtering criteria displays the selected metric.
    Workaround: Before you upgrade from 5.0, remove the widget configurations for the Heat Maps, Metric Weather Map, and Top-N Analysis widgets.
  • A resource that is in maintenance mode in the vCenter cannot be permanently removed from maintenance mode in vCenter Operations Manager.
    vCenter Operations Manager pulls maintenance mode data from the vCenter, and puts resources in manual maintenance mode in vCenter Operations Manager. While you can remove a resource from maintenance mode in vCenter Operations Manager, during the next collection cycle, the resource is put back into maintenance mode.
    Workaround: There is no workaround. If a resource is in maintenance mode in the vCenter, do not remove the resource from maintenance mode in vCenter Operations Manager.
  • The CPU load heat map displays the wrong color
    In the custom interface, the CPU load heat map under Heatmaps dashboard > CPU Load widget > Hosts by CPU Usage, displays the color for memory usage instead of CPU usage. This applies to upgrades from vCenter Operations Manager 5.7.1 or 5.7.2 to 5.8. It does not apply to a new installation of vCenter Operations Manager 5.8.
    Workaround: To configure the correct color display for the CPU Load Widget:
    1. Select the CPU Load Widget and click the edit widget icon.
    2. From the Edit screen, choose the CPU Usage from the "color by" option and choose Usage (%).
    3. Click the update selected configuration icon (image of a disk).
    4. Click OK to save the configuration.
  • No reduction in license count after restricting the collection user.
    Reducing the scope of objects seen by the collection user does not reduce the license count of monitored objects in the admin interface.
    Workaround: Delete the unwanted objects or restart the vCenter Operations Manager services.

  • SSL using a signed Certificate Authority (CA) certificate imported through the admin interface does not work.
    Workaround: None.

  • vCenter Server health badge and metric profile change
    Changing the metric profile (from Balanced Profile to Full Profile or from Full Profile to Balanced) can affect the active fault score of a vCenter Server object. The fault badge score will be reset to zero (0) from a previous score although the fault alert is still active. This can directly affect the health badge of the vCenter Server object. This is specific only to the vCenter Server objects. Fault badges of other objects are not affected by profile changes.
    Workaround: To change Fault and health badge scores to their previous state, restart the collector.
  • vCenter Server Inventory in vCenter Operations Manager does not display in the vSphere Client.
    If the vCenter Server IP address changes, Inventory and details data for the vCenter Server may not display in the vSphere Client.
    Workaround: From the Environment Overview page, edit the resource and manually set the new IP address for the vCenter Server. After the IP address is set, no data is lost.
  • An unregistered vCenter Server appears in the vSphere Client UI as registered and collecting data
    If you unregister a vCenter Server from vCenter Operations Manager using the vCenter Operations Manager Administration portal, it is removed from the list of registered servers, but continues to display in the vSphere Client as registered and collecting data.
    Workaround: To remove the vCenter Server as registered in the vSphere Client, restart vcopsweb on the UI VM. To do this, restart the Apache Tomcat web server by entering the command as root: service vcopsweb restart
  • vCenter Operations Manager Administration fails to report vCenter Server registration in the Admin portal
    If you register a vCenter Server using the command line interface, the registration is successful; however, the newly registered vCenter Server fails to appear in vCenter Operations Manager Administration.
    Workaround: Restart vCenter Operations Manager Administration. To restart the Admin portal, log in to the UI VM console as root and run the following command: /etc/init.d/vcopsadmin restart
  • vCenter Operations Manger recognizes only one HA failover host in vCenter Server 5.0
    In vCenter Server release 5.0 and above, you can specify more than one dedicated HA failover host. HA capacity calculations can account for only one failover host when the admission control policy is set to "Specify failover hosts" in vCenter Server. If you specify multiple failover hosts, only one of them is considered.
    Workaround: None
  • Top-N Analysis widget does not respond to resource tag changes
    You cannot change the resource tag that you selected in the initial Top-N Analysis widget configuration. Although you can edit the widget configuration and select a different resource tag, the new configuration has no effect and the widget continues to show the previously selected resource tag.
    Workaround: None.
  • The total sum in legends for the custom groups does not match 100 percent
    On the Dashboard tab the sum of all groups' members percentages does not always match 100. This is caused due to rounding the fraction values. For example, if the calculated percentages are 10,5 and 89,5, they are displayed as 11 and 90, which equals 101 percent.
    Workaround: None.
  • Child dashboard information is lost during multilevel dashboard export and import operations
    If you export a parent dashboard and then import it, the parent dashboard appears in the user interface of the target instance but the child dashboard does not.
    Workaround: None.
  • OVF deployment by 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.
  • 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.
  • 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.8 does not support vSphere 5.1 SSO authentication
    The 5.8 release of vCenter Operations Manager does not support authentication with Single Sign On (SSO), 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).
  • 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.

User Interface

  • World compliance breakdown displays "No Data"
    After running vCenter Configuration Manager compliance, the vCenter Operations Manager World > Planning > Views > Compliance gallery displays "No Data" under Details.
    Workaround: None
  • SSL certificate import messages appear in English
    If the user of a localized version of vCenter Operations Manager selects a .pem file to install, the message that appears on the SSL tab of the admin interface is not localized. It is in English. Possible messages include:
    • "Successfully imported the SSL Certificate" appears when a proper .pem file is successfully imported.
    • "Cannot import SSL certificate because it does not contain the private key." appears when the imported .pem file doesnt have a private key.
    • "Cannot import SSL certificate because it is not encoded in PEM format." appears when the imported file is not in .pem format.
    • "Cannot import SSL certificate because the private key is encrypted with a passphrase." appears when the imported .pem file has a private key, encrypted with a passphrase.
    • "Cannot import SSL certificate because it is expired." appears when the imported SSL certificate is expired
    • "Cannot import invalid SSL certificate." appears when any other criteria fails.

  • "Disk I/O, Network I/O" boxes unchecked on Default Policy
    After installing vCenter Operations Manager 5.8, the Capacity and Time remaining configuration page for the default policy shows the Disk I/O and Network I/O boxes unchecked. This indicates that the Disk I/O and Network I/O metrics are not included in the demand for resource calculations.
    Workaround: This affects new installations, not upgrades. This change was implemented to reduce the amount of detailed data provided for capacity planning. To include Disk I/O and Network I/O metrics in the demand for resource calculations, check the boxes.
  • Online help does not support the Safari browser.
    Workaround: None.
  • Cannot delete a user who has a shared dashboard
    A user who creates a dashboard and shares it with the Administrator group cannot be deleted. On the Manage Security page, the admin user can select and confirm the user to delete, but the user is not deleted.
    Workaround: None.
  • "No data available" icon and exceptions appear on the EMC Storage Metrics and Storage Topology page
    After a valid VMAX instance with slaves is deleted on a vCenter Operations Manager environment configured with the EMC adapter:
    • On the EMC Storage Metrics page, the "no data available" icon appears in the Resource Selector and NullPointerException appears in the Metric Selector.
    • On the EMC Storage Topology page, the "no data available" icon appears in the Storage Topology and Health and exceptions appear in Parent and Child Resources.
    Workaround: Add a VMAX instance again or log out and log back in.
  • Once populated, a Launch-in-Context menu cannot be removed or disabled for Log Insight adapter
    The Log Insight adapter lacks the mechanism to remove or disable its relationship with Launch-in-Context.
    Workaround: Remove the Log Insight adapter from vCenter Operations Manager.
    NOTE: The commands must be on a single line. Lines of text are broken here to improve readability. Do not copy and paste the curl commands from this page.
    • Query vCenter Operations Manager for the Log Insight adapter.


      curl -k --user <vcops username>:<vcops passwd> https://<vcops url>:443/HttpPostAdapter/OpenAPIServlet -d
      "action=getRelationships&resourceName=Log Insight Server&adapterKindKey=LogInsight&resourceKindKey=LogInsightLogServer
      &getChildren=true&getParents=false"

    • Within the query results, find the lines with the Log Insight location that appear as:

      resourceName=Log Insight Server<log insight location>&

      identifiers=HOST::<log insight location>

    • Use the log insight location in the command to remove the Log Insight Adapter.


      curl -k --user <vcops username>:<vcops passwd>
      https://<vcops url>:443/HttpPostAdapter/OpenAPIServlet -d
      "action=addRemoveParentChildRelationship&parentResource=Log Insight Server
      &adapterKindKey=LogInsight&resourceKindKey=LogInsightLogServer
      &addFlag=false&childResources=Log Insight Server<log insight location>,LogInsight,LogInsightLogServerHost,HOST::<log insight location>"

  • The vSphere client reports the error: "You don't have privileges to view this object."
    If you select a deleted object before data collection occurs, you may see the error "You don't have privileges to view this object. This error occurs because vCenter Operations Manager collects data every five minute and no data is collected for this object.
    Workaround: After data for this object is collected, information for this object displays.
  • Inappropriate list of groups displayed in Edit dialog for Default Policy
    The list of groups in Associations section does not always display the complete set of groups for which the default policy is applied.
    To explicitly associate a group with Default Policy you must select Manage policy from the Actions drop-down menu of the group.
    Workaround: None.
  • Edit Custom Relationship widget page lets you select multiple metrics
    When you configure the Custom Relationship widget, you must map one metric type to each resource kind that you select, the Metric Selector with Resource Selection pane lets you select multiple metrics.
    Workaround: If you select more than one metric for a resource kind, the error message "You can select only one metric per badge" appears. Click OK in the message dialog box, select only one metric, and click OK to save your changes.
  • Planning views and reports do not show names for objects.
    In the CIQ adapter, planning views and reports do not show names for objects.
    Workaround:
    • Log in to the UI virtual machine as user root.
    • Run service vcopsweb restart.

      Allow 15 minutes for the name to appear in planning views.
  • 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 interface, 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.

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.

Top of Page

Documentation

    The following product changes were not described in the release documentation.
  • 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.
  • Missing information in the vApp Deployment and Configuration Guide for how to send syslog to Log Insight
    See Configure vCenter Operations Manager to send syslog to Log Insight for details.
  • Missing information in the custom interface online help: "Data Age" field displays "Unknown" in the VCOps/VCM Compliance breakdown.
    vCenter Operations Manager will only display the last collection date (Data Age) if a collection filter is assigned to the VCM compliance rule group.
  • Missing information on consolidated alerts in the custom interface documentation
    See Aggregating and Filtering Alerts in vCenter Operations Manager 5.6 (Custom UI) (KB 2039020) for details.

Top of Page