VMware vCenter Operations Manager 5.8.4 Release Notes
vCenter Operations Manager 5.8.4
Last Document Update: 28 OCTOBER 2014
Check frequently for additions and updates to these release notes.
These release notes include the following topics:
- What's New
- Before You Begin
- Product Compatibility and Requirements
- Upgrading from a Previous Version
- Resolved Issues
- Known Issues
vCenter Operations Manager 5.8.4 is the latest release of VMware's integrated operations suite, converging performance, capacity, and configuration management. This release of vCenter Operations Manager 5.8.4 updates the Bash libraries in vCenter Operations Manager 5.8.4 to resolve multiple critical security issues, also referred to as Shellshock. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the identifiers CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, and CVE-2014-7187 to these issues. This issue has been documented in the Resolved Issues section.
Review this section before you begin installing and configuring vCenter Operations Manager.
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.4 release.
This section contains important notes on vCenter Operations Manager 5.8.4 licensing.
vCloud Suite Licensing and Integration
You can license vCenter Operations Manager 5.8.4 individually or as part of vCloud Suite 5.8. You should consider the licensing and integration options that are available to you.
Some vCloud Suite components are available as standalone products that are licensed on a per-virtual machine basis. When the products are part of vCloud Suite, they are licensed on a per-CPU basis. You can run unlimited number of virtual machines on CPUs that are licensed with vCloud Suite.
You can combine the features of vCenter Operations Manager 5.8.4 with other components of vCloud Suite to leverage the full capabilities of the software-defined data center. For more information, see the vCloud Suite Architecture Overview and Use Cases at https://www.vmware.com/support/pubs/vmware-vcloud-suite-pubs.html.
Not all features and capabilities of vCloud Automation Center are available in all editions. For a comparison of feature sets in each edition, see https://www.vmware.com/products/vcloud-automation-center/.
- Important License keys for vCenter Operations Management Suite 5.8.4 with vCenter Server 5.0 or 4.1
The vCenter Operations Management Suite 5.8.4 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:
- vCenter Operations Manager 5.8.4 (Standard, Advanced, and Enterprise editions): https://www.vmware.com/go/download-vcops
- vCenter Infrastructure Navigator (VIN) 2.0: https://www.vmware.com/go/download-infrastructure-navigator
- 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.4 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.4 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.4. If you upgrade vCenter Operations Manager 5.6 having EMC license key to 5.8.4, 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.4. 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.4.
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.4 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.4 release.
- vCenter Infrastructure Navigator 2.0
- vCenter Configuration Manager 5.7.2
- vCenter Operations Manager for View 1.5
vCenter Operations Manager 5.8.4 supports the following:
- Google Chrome 24 and 25
- Internet Explorer for Windows 8.0 and 9.0
- Mozilla Firefox 18 and higher
Note: There are some limitations with the Dashboards feature in the custom interface if Internet Explorer 8 is used.
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.
For sizing guielines, read the vCenter Operations Manager Sizing Guidelines KB article (2057607) at http://kb.vmware.com/kb/2057607.
The following section lists the computing requirements and assumptions for the vCenter Operations Manager vApp.Use of third-party tools
Customers should not load any third-party tools into the vCenter Operations Manager virtual appliance, although VMware cannot prevent customers from doing so. The appliance is configured and tested with the assumption that no additional processes or software will be added to the appliance. Changes to the appliance could invalidate our testing, scalability, security, and supportability claims.Balanced Profile
- Maximum number of objects: 12K, 2.2 million metrics
- Analytics VM: 21GB
- UI VM: 26GB
- Analytics VM: 8 vCPU
- UI VM: 8 vCPU
- Maximum number of objects: 12K, 5 million metrics
- Analytics VM: 63GB
- UI VM: 26GB
- Analytics VM: 24 vCPU
- UI VM: 16 vCPU
- 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 requires a vCenter Server user to register vCenter Operations Manager with vCenter Server. The user should be an Administrative user and can also act as Collection user if a Collection user is not assigned during vCenter Operations Manager registration.
- If a Collection user is assigned, 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 through vCenter Server 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.
- Upgrade from any vCenter Operations Manager 5.x version
- Upgrade the OS to SUSE Linux Enterprise Server 11 SP3 for vCenter Operations Manager 5.8.4
- Upgrade from vCenter Operations 1.0.x or Capacity IQ 1.5.x
This procedure is applicable when updating to vCenter Operations Manager 5.8.4 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, 5.7.2, and 5.x including any Hotfix versions.
A side by side upgrade path is not supported.
Important Following the upgrade to vCenter Operations Manager 5.8.4, the operating system upgrade described in: Upgrade the OS to SUSE Linux Enterprise Server 11 SP3 for vCenter Operations Manager 5.8.4 is required for the vApp to function properly.
For upgrade requirements, including 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.
- Save the .pak file for the vCenter Operations Manager 5.8.4 build to your local storage.
- Log in to the Administration portal using the admin user credentials.
- Click on the Account tab and change the password for both the admin and root user. The new password policy is a minimum of eight characters, with at least one upper, one lower, one digit, and one special character (other than $). The new password must not be one of the most recent passwords; the last five passwords are not accepted.
- On the Update tab, click Browse and select the .pak file that you saved to local disk.
- Click Update.
- Accept the EULA by selecting the check box and click OK.
- Accept and confirm the update.
- The update process will start, and the Administration portal page might refresh after some time and ask you to login again.
- 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.
- Log in to the vCenter Server that manages the license for vCenter Operations Manager, and apply the new vCenter Operations Manager 5.8.4 license key, if applicable.
Note: You must re-apply the new license key in the vCenter Server after the upgrade, if the licence key has changed. If you do not, you will see reduced functionality in the vCenter Operations Manager interface.
- In the Administration portal, navigate to the Status tab and restart all services.
- Log in to the vSphere client or the custom interface to verify that the vCenter Operations Manager interface is displayed properly.
This procedure is applicable when performing an in-place vApp OS upgrade to SUSE Linux Enterprise Server (SLES) 11 SP3. You can upgrade the OS to run vCenter Operations Manager 5.8.4.
- Verify that vCenter Operations Manager 5.8.4 is installed and running.
- Back-up the UI virtual machine and the Analytics virtual machine.
- Verify that vCenter Operations Manager 5.8.x root password does not expire by running the following command in the UI VM: chage -l root. If the password expires, create a new password and proceed with the upgrade.
- Download or copy the SLES 11 SP3 PAK file from the VMware download site for vCenter Operations Manager to the /data drive on the UI virtual machine.
- Start the SLES 11 SP3 upgrade, with the command:
- After the upgrade completes successfully, restart the vApp.
- Login to the vCenter Operations Manager UI to verify that it is working.
scp VMware-vcops-SP3-2191616.pak root@ip_address_of_webui:/data
The process automatically upgrades both the UI virtual machine and the Analytics virtual machine.
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.4 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.4. You must follow the procedure described in this document.
- 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.
- After the vCenter Operations Manager 5.0.3 finishes data import, allow the deployment to run for at least two hours.
- Perform an in-place upgrade to vCenter Operations Manager 5.8.4 using the .pak file and the procedure described in the previous section.
vCenter Operations Manager 5.8.4 resolves the following issue.
- The vCenter Operations Manager virtual appliance uses the Bash shell, which is a part of the Linux operating system. In the earlier versions of vCenter Operations Manager, the Bash shell could be exploited through the bash security vulnerability commonly referred to as ShellShock (CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187).
This issue is resolved in this release.
This section contains known issues for this release.
- Installation and Upgrade
- vApp Management
- User Interface
- vCenter Operations Manager in the vSphere Web Client
Installation and Upgrade
Some vCenter Operations Manager services fail to start following upgrade to vCenter Operations Manager 5.8.4
In compliance with STIG, vCenter Operations Manager 5.8.4 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.4.
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.4, 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.4.
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.
Change events and vCenter Operations Manager 5.8.4 and vCenter Configuration Manager (VCM) 5.5.x interoperability
Change event collection from VCM in vCenter Operations Manager 5.8.4 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.4:
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
Error: Could not open input file: /usr/java/jre1.7.0_07/lib/jsse.pack
Error: Could not open input file: /usr/java/jre1.7.0_07/lib/charsets.pack
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.4, the product version and build number do not appear in the left corner of the vCenter Operations Manager Administration screen.
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.
Groups created by different vCenter Servers, and monitored from the same instance of vCenter Operations Manager, display in the vSphere Client Inventory
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.
- Port WWN details are displayed incorrectly in the custom UI
When you view the port WWN information from the custom UI of vCenter Operations Manager, the details are truncated and shown as an integer instead of a hexadecimal value in the metric graph.
Workaround: View the correct value of port WWN from the vSphere UI of vCenter Operations Manager.
An error occurs when the World resource is placed in maintenance mode or data collection for the World resource is stopped manually from the custom UI
An error occurs when you access the vSphere UI after you perform either of the following actions for the World resource in the custom UI of the vCenter Operations Manager:
- Select the World resource from the custom UI of vCenter Operations Manager and start the maintenance mode by clicking the Start Maintenance button.
- Stop data collection of the World resource from the custom UI by clicking the Stop Collecting button.
The following error message appears when you next log in to the vSphere UI and access the World resource:
500 The call failed on the server; see server log for details (StatusCode:500)
You cannot view the World resource in the the left hand pane of the vSphere UI.
Workaround: To view the the World resource in the vSphere UI and to address the error, perform the following actions from the custom UI of the vCenter Operations Manager.
- Log in to custom UI from the browser and open the Environment Overview page. Select the World resource and click the End Maintenance mode button.
- Log in to the custom UI from the browser. Select the World resource and click the Start Collecting button, if you had previously stopped data collection.
Alerts for SMS collection failures are not clear
The source of the alerts for communication failures with the vCenter Server is not clear. The reason for the communication failure with the vCenter Server is not specified clearly in the alerts.
- Repository Adapter export tool data limits
The Repository Adapter tool fails to export data if the number of resources is more than 8.5K, or the number of metric data is more than 19000000 (Approximately 19 Million) in vCenter Operations Manager.
Some metrics are missing in the Custom UI
Some metrics listed in the documentation do not appear in the Custom UI. For example, some UI elements that visualize attributes or metrics, hide property-type attributes because of certain limitations related to that type of attribute. These metrics are hidden from the attribute package editor in the Custom UI but may still contribute to the overall attribute count displayed when selecting a group in the attribute package editor.
Workaround: This is expected behavior and there is no workaround.
Metric names are displayed in English only
Regardless of the language setting, metric names are only displayed in English.
Problems with attribute packages management with vCenter Configuration Manager
If you select Manage Attribute Packages, and configure VCM as a new instance, you cannot configure vCenter Configuration Manager as a new instance if the entry contains Non-ASCII characters. If you enter Non-ASCII characters, the instance cannot be saved successfully.
Workaround: Enter ASCII characters.
- 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.
- '!' 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.
- 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.
Scheduling the Repository tool to export data
If you want to export data at a scheduled time, run the runOnce = false command in the file to run the data export manually. After the manual run, the export will continue to run on schedule.
- 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.
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.4. It does not apply to a new installation of vCenter Operations Manager 5.8.4.
Workaround: To configure the correct color display for the CPU Load Widget:
- Select the CPU Load Widget and click the edit widget icon.
- From the Edit screen, choose the CPU Usage from the "color by" option and choose Usage (%).
- Click the update selected configuration icon (image of a disk).
- 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.
SSL using signed Certificate Authority (CA) certificate imported through the admin interface does not work
Workaround: Configure vCenter Operations Manager (vApp) for SSL using a chain of certificates (KB 2079782) addresses this issue.
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.
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.
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.
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.
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.
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.
vCenter Operations Manager 5.8.4 does not support vSphere 5.1 SSO authentication
The 5.8.4 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).
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.
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.4, 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.
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.
"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
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
&addFlag=false&childResources=Log Insight Server<log insight location>,LogInsight,LogInsightLogServerHost,HOST::<log insight location>"
- Query vCenter Operations Manager for the Log Insight adapter.
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.
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.
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.
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.
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.
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:
- VMwareAdapter Instance
- VCMAdapter Instance
- VinAdapter Instance
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.
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.
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.
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.
- 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.
- 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.
- If you select from the Inventory tree a vCenter Server object that has no child objects attached.
- Error in the vApp Deployment and Configuration Guide
In chapter 6 of the vApp Deployment and Configuration Guide, the topic called "Upgrade the OS to SLES 11 SP2 for vCenter Operations Manager 5.8.x", includes a command that is incorrect. The correct command is
chage -l root.
- The online help does not contain information about certain metrics
The online help does not contain information about metrics such as Total Virtual Disk Space Configured and Disk Space Total Used.
- The online help does not contain information about the CPU Active (%) (1 min. average) metric
The online help does not describe how run time and ready time are used to compute the CPU Active (%) (1 min. average) metric.
For information about collected metrics, refer to the VMware vCenter Installation and Configuration Guide.
Error in vApp Deployment and Configuration Guide
In chapter 3 of the vApp Deployment and Configuration Guide, the URL format in step 1 on page 24 is incorrect. The correct URL format is:
Help error in identifying undersized or oversized machines
For Identifying Undersized Virtual Machines, the VM area taken in account should be documented as the area above the "CPU/Mem Demand greater than" threshold minus the area under the "CPU/Mem Demand greater than" threshold.
For Identifying Oversized Virtual Machines, the VM area taken in account should be documented as the area under the "CPU/Mem Demand less than" threshold minus the area above the "CPU/Mem Demand less than" threshold.
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:
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.