VMware vCenter Operations Standard 1.0.1
VMware

VMware vCenter Operations Standard 1.0.1 Release Notes

vCenter Operations Standard 1.0.1 | Build 462725

Last Document Update: 24 AUG 2011

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

What's New in vCenter Operations Standard 1.0.1

vCenter Operations Standard 1.0.1 is a maintenance release that adds support for vCenter Server 5.0 and resolves some known issues.

Introduction to vCenter Operations Standard

VMware vCenter Operations is an automated operations management solution that provides integrated performance, capacity and configuration management for highly virtualized and cloud infrastructure. Deep VMware vSphere integration provides the most comprehensive management of VMware environments. VMware vCenter Operations is available in three editions. VMware vCenter Operations Standard is purpose-built for VMware administrators to more effectively manage the performance of their VMware environments as they move to the private cloud.

Key Benefits

  • Actionable intelligence to automate manual operations processes
  • Visibility across infrastructure and applications for rapid problem resolution
  • Proactively ensures optimal resource utilization and virtual and cloud infrastructure performance

Top of Page

Before You Begin

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

Virtual Appliance Deployment

Always use a vSphere Client to connect to a vCenter Server and deploy the vCenter Operations virtual appliance through the vCenter Server. The vCenter Operations virtual appliance should be deployed on an ESX/ESXi host version 4.0 or above that is managed by one of the following versions of VMware vCenter Server:

  • VMware vCenter Server 4.0 Update 2 or later
  • VMware vCenter Server 4.1 or later

Upgrading the Virtual Appliance

If you have vCenter Operations Standard 1.0 running on your vCenter Server and you want to upgrade to vCenter Operations Standard 1.0.1, complete the following steps.

  1. Download the vCenter Operations update file from the VMware Download center to your local storage.
    The file name of the update file is VMware-vcops-1.0.1-XXXXXX.pak, where XXXXXX stands for the product build number.
  2. Use a browser to navigate to the VMware vCenter Operations virtual appliance administration portal.
    The URL format is https://<VA_IP>:5480 where VA_IP is the IP address of the vCenter Operations Standard virtual appliance.
  3. Use the root user credentials to log in.
    The default user name is root, and the password is vmware.
    Note: These credentials might vary if you have modified them.
  4. On the Appliance Administration tab, click Browse to locate the update *.pak file.
  5. Type the root user password and click Upgrade.
  6. Wait for the upgrade procedure to complete and verify that the upgrade is successfully applied.
If the upgrade procedure fails, you can check the following log files on the vCenter Operations virtual appliance:
  • /var/log/upgrade_upload_xxx.log, where xxx represents the time when the upload process started.
  • /var/log/upgrade_yyy.log, where yyy represents the time when the upgrade process started.
  • /var/log/upgrade_error_zzz.log, where zzz represents the time when the first upgrade error occurred.

Licensing vCenter Operations Standard

This paragraph contains important notes on vCenter Operations Standard licensing.

  • You cannot view monitoring data if you do not assign a license to vCenter Operations Standard.
  • vCenter Operations Standard is licensed as an asset to the vCenter Server that it monitors. You must register vCenter Operations with a vCenter Server before you assign a license. To register vCenter Operations with a vCenter Server, open the vCenter Operations Standard Administration portal and follow the procedure described in the VMware vCenter Operations Standard Installation and Administration Guide.
  • All license management tasks are performed in the vSphere Client. You cannot assign licenses in the vCenter Operations Standard Administration portal. Follow the instructions from the VMware vCenter Operations Standard Installation and Administration Guide to assign a license.
  • You must re-assign the license each time you register vCenter Operations Standard with a vCenter Server. You create a new asset each time you register vCenter Operations Standard with a vCenter Server. Therefore, you must re-assign the vCenter Operations Standard license each time you register with a vCenter Server, even if the vCenter Server has been registered before. For example, if you un-register vCenter Operations virtual appliance from a monitored vCenter Server and then register the appliance with the same vCenter Server, vCenter Operations Standard creates a new asset on this vCenter Server. However, the license remains associated with the vCenter Operations asset that corresponds to the previous registration. Therefore, you must un-assign the license from the old asset and assign it to the latest created asset in order to access the vCenter Operations user interface.

Product Compatibility

  • With this release of vCenter Operations Standard you can monitor the following platforms:
    • VMware vCenter Server 4.0 Update 2 and later
    • VMware vCenter Server 4.1 and later
  • Datastore statistics is supported only for vCenter Servers and ESX hosts of version 4.1 and later.
  • This release of vCenter Operations Standard supports Internet Explorer 7.0 or later. You must use this browser when connecting to the vCenter Operations virtual appliance settings page and when accessing the vCenter Operations Standard Administration page for the first time, before you define a vCenter Server to monitor. You can use Mozilla Firefox 2.0.x or later only to access the vCenter Operations Standard Administration page after you defined a vCenter Server to monitor.
  • You use the vSphere Client to connect to vCenter Operations Standard monitoring interface. Internet Explorer 7.0 or later must be installed on the machine where the vSphere Client runs.

User Accounts

  • To register vCenter Operations Standard with a vCenter Server, you must provide the user credentials of an administrator user for that vCenter Server.
  • The user account you use for collecting data with vCenter Operations Standard determines the scope and accuracy of the monitoring data.
    • vCenter Operations Standard 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 Standard Administration portal.
    • vCenter Operations Standard 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 default credentials for the Administrator user are admin/admin. To improve security, vCenter Operations Standard requires you to change these credentials when you first access the vCenter Operations Standard Administration portal. The new password you assign to the Administrator user is automatically assigned to the root user on the vCenter Operations virtual appliance.
  • The default credentials for the root user on the vCenter Operations virtual appliance are root/vmware. The root password is changed automatically when you assign a new Administrator password in the vCenter Operations Standard Administration portal.

Top of Page

Resolved Issues

This release includes fixes in the following subject areas:

  • Search by Instance on the Self Info tab of the vCenter Operations Standard Administration portal is case-sensitive
    The Search text box in the Metric Selector pane was case-sensitive if you sorted by Instance. This was inconsistent as compared to the Metric or Group search, which is not case-sensitive.
  • Search by Instance on the All Metrics tab of the vCenter Operations Standard user interface is case-sensitive
    The Search text box in the Metric Selector pane was case-sensitive if you sorted by Instance. This was inconsistent as compared to the Metric or Group search, which is not case-sensitive.

Top of Page

Known Issues

This section contains known issues for this release.

Installation and Upgrade


  • Product version is not displayed properly in the Plug-in Manager window after an upgrade from vCenter Operations Standard 1.0.0 to vCenter Operations Standard 1.0.1
    After you upgrade the vCenter Operations virtual appliance from version 1.0.0 to version 1.0.1, the Plug-in Manager window of the vSphere Client still displays the version as 1.0.0 instead of 1.0.1. The upgraded product version is displayed properly in the virtual appliance console and in the vCenter Operations Standard 1.0.1 user interface.
    This problem is not observed with new installations of vCenter Operations Standard 1.0.1.
    Workaround: Re-register vCenter Operations Standard with the same vCenter Server to view the correct version number.
    Note: After re-registering, you must use the vSphere Client to reassign the license to the newly created vCenter Operations asset. See the details in section Licensing vCenter Operations Standard .
  • Product version is not displayed properly in the Summary tab after an upgrade from vCenter Operations Standard 1.0.0 to vCenter Operations Standard 1.0.1
    After you upgrade the vCenter Operations virtual appliance from version 1.0.0 to version 1.0.1, the Summary tab of the virtual appliance in the vSphere Client still displays the version as 1.0.0.0 instead of 1.0.1.0. The upgraded product version is displayed properly in the virtual appliance console and in the vCenter Operations Standard 1.0.1 user interface.
    This problem is not observed with new installations of vCenter Operations Standard 1.0.1.

Top of Page

General


  • After the registration with a vCenter Server, vCenter Operations Standard is not visible as an asset on the Licensing page of the vSphere Client
    If the vSphere Client is open while you register vCenter Operations Standard with a vCenter Server, vCenter Operations Standard does not appear in the list of assets on the Licensing page.
    Workaround: You must close the vSphere Client and open it again to be able to see vCenter Operations Standard in the list of assets.
  • The ESX version and build number is not displayed on the Details page of ESX host objects
    In a newly installed vCenter Operations Standard, if you navigate to the Details page of an ESX host object and check the ESX Resources pane, you might see that the ESX Version is displayed as a question mark, and the ESX build number is missing. This is because vCenter Operations Standard requires time to populate all fields on the Details page. Workaround: Wait for the ESX version and build number to update.
  • vCenter Operations Standard stops collecting data
    In large environments, where virtual machines are created and deleted intensively, vCenter Operations Standard might stop collecting data and the following error message might appear in the controller.log file:
    ERROR [Task Processor worker thread 2]
    com.integrien.alive.common.communication.CommunicatorWorkItem.run - Unable to process task Ask for Config id:2 from collector:1
    java.lang.OutOfMemoryError: Java heap space

    This is because vCenter Operations Standard keeps track of all resources that have been added to the database. Even if you delete a virtual machine from the vCenter Server, the monitoring data for that deleted virtual machine remains in the vCenter Operations Standard database. Therefore, if you add and delete numerous virtual machines, the controller service might not have enough memory to start collecting data.
    Workaround: Delete all non-existing resources from the vCenter Operations Standard database. See VMware Knowledge Base article Deleting non-existing resources from the vCenter Operations Standard database (KB 2004239) for details.
  • vCenter Operations Standard creates too many sessions on the vCenter Server
    Occasionally, vCenter Operations Standard creates new sessions to the vCenter Server without closing the old sessions it opened. This way, old sessions become idle or stale sessions that never time out or log out. This might cause performance issues in vCenter Server. When the per-user session limit is exceeded, vCenter Operations might stop working properly. The vCenter Server might deny service to the user that vCenter Operations uses to connect to vCenter Server. Workaround: Restart the vCenter Operations service to clear old sessions.
    1. On the vCenter Operations Standard virtual appliance settings page, click the Appliance Administration tab.
    2. Type the root user password above the Restart button and click Restart.
      The Restart successful message appears when the restart operation completes.
  • When you start vCenter Operations for the first time, it takes several minutes before the inventory is loaded in the user interface.
    The time required to load objects in the Inventory view depends on the size of the inventory you are monitoring.
  • The Inventory view displays objects with question marks
    When you restart the vCenter Operations system, the inventory objects display question marks <?> instead of performance data. It takes up to several minutes for vCenter Operations Standard to get data from the vCenter Server and to refresh the Inventory view with performance data for all objects.
  • Message Not Calculated Yet is displayed for normal values of performance metrics
    After you install vCenter Operations Standard, it takes approximately 7 days for the analytics logic to calculate normal values for performance metrics. During that time, vCenter Operations displays Not Calculated Yet for normal values.
  • Inconsistent metric data is displayed if the time zone on the vCenter Server differs from the time zone on the vCenter Operations virtual appliance
    If you select an object in the Infrastructure view and navigate to the Details page, you might see a No data message for a key metric and, at the same time, a numeric value displayed next to it. This issue is observed when the time zone on the vCenter Operations virtual appliance is different from the time zone on the vCenter Server that is being monitored. The vCenter Operations analytics module uses the time zone setting of the vCenter Operations virtual appliance for reference when calculating key metric values. Therefore, it cannot calculate values that have time stamps that differ from the current system time of the analytics module. As a result, the latest recorded value for a metric is displayed, but there is no data for calculated values.
    Workaround: Ensure you set the same time zone on the vCenter Operations virtual appliance and on the vCenter Server that you monitor.
  • System time zone set on the vCenter Operations Standard virtual appliance settings page is not applied properly
    If you log in to the vCenter Operations Standard virtual appliance settings page at https://<IP>:5480/, modify the system time zone settings, and click Save Settings, you might notice that the time zone does not change.
    Workaround: Restart the vCenter Operations service.
    1. On the vCenter Operations Standard virtual appliance settings page, click the Appliance Administration tab.
    2. Type the root user password above the Restart button and click Restart.
      The Restart successful message appears when the restart operation completes.
  • vCenter Operations Standard might display outdated performance data for powered-off objects
    If you navigate to the Details page of a powered-off object, you might see the last known state of the health and the workload metrics that was recorded before the power-off event. This is because not all data is updated properly for powered-off objects in the monitored inventory.
  • ESX hosts in maintenance mode are not indicated in the vCenter Operations Standard user interface
    vCenter Operations Standard uses the same icon to visualize running hosts and hosts in maintenance mode. Besides, the user interface does not display any event information when an ESX host switches to maintenance mode. Therefore, you cannot distinguish between running hosts and hosts in maintenance mode if you look at the vCenter Operations Standard user interface.
  • Virtual Disk|Total Latency metric is not supported for virtual machines hosted on ESX host versions 4.0 and earlier
    On the Details page of a virtual machine hosted on an ESX host version 4.0 or earlier, on the Disk I/O tab of the Key Metrics pane, vCenter Operations displays the No data message for the Virtual Disk|Total Latency metric. This message is misleading because the Virtual Disk|Total Latency metric is not supported for ESX host versions 4.0 and earlier.
  • You cannot distinguish between missing metrics data and unsupported metrics in the vCenter Operations user interface
    When metrics data is missing, vCenter Operations Standard displays a question mark and does not distinguish between the reasons why that data is missing. Therefore, you cannot be sure if a question mark means that the selected metric is not supported on the monitored object or that there is not enough data collected to display.
  • Hosts, Clusters, Datacenters, vCenter Servers, and data store objects (dubbed 'containers') might show partial or incorrect data in vCenter Operations Standard
    vCenter Operations Standard calculates metric values based on the visibility that the Collection user has to the inventory. If certain objects are not visible to the collector, these objects are not taken into account when calculating metrics for their container objects. This can result in incorrect object counts (for example, the number of hosts in the cluster) or incorrect metric values (for example, incorrect demand values on the host).
    Workaround: Always set the read permissions to the vCenter Server objects as high as possible in the hierarchy. We recommend that you set read permissions at either the datacenter or cluster level. If a data store is shared between two hosts, we recommend that the collection user has read permissions to both hosts. Do not set read permissions on individual virtual machines.
  • vCenter Operations Standard might display inventory objects even if you do not have permissions to view them
    vCenter Operations Standard calculates metric values based on the visibility that the Collection user has to the inventory. If certain objects are not visible to the collector, these objects are not taken into account when calculating metrics for their container objects. This can result in incorrect object counts (for example, the number of hosts in the cluster) or incorrect metric values (for example, incorrect demand values on the host).
    Workaround: Always set the read permissions to the vCenter Server objects as high as possible in the hierarchy. We recommend that you set read permissions at either the datacenter or cluster level. If a data store is shared between two hosts, we recommend that the collection user has read permissions to both hosts. Do not set read permissions on individual virtual machines.
  • You cannot find the custom configuration you created if the configuration name uses non-ASCII characters
    If you create a new custom configuration from the ANALYSIS menu of vCenter Operations Standard, and you name that custom configuration using non-ASCII characters, you might not be able to find the configuration under the search text box in the grid.
    Workaround: Use only English characters to name your custom configurations.
  • You have to complete two different procedures to install your custom SSL certificates
    By default, vCenter Operations Standard uses two self-signed SSL certificates, one for the Tomcat server of the vCenter Operations virtual appliance and one for the vCenter Operations Administration portal. The two self-signed certificates have different formats and different principle name parameters.< br />
    • The SSL certificate used by the Tomcat sever is located in /usr/lib/vmware-vcops/tomcat/conf/oxygen.keystore, and is a Java JKS-format keystore. This certificate is auto-generated on first start of the vCenter Operations virtual appliance. Its principal name is CN=vmware, OU=Inc., O=VMware, L=US, S=CA, C=US.
    • The SSL certificate used by the vCenter Operations Administration portal on port 5480 is located in /opt/vmware/etc/lighttpd/server.pem, and is a simple PEM-format (base64-encoded ASCII) certificate, not a full keystore. principal name is CN=VMware, Inc., O=VMware, Inc., OU=Management Platform, C=US.
    Therefore, if you want to replace the default self-signed certificates with your custom SSL certificates, you have to accomplish two different procedures.
  • vCenter Operations Standard stops collecting data if you rename an NFS datastore
    If you rename an NFS datastore, vCenter Operations Standard can no longer collect data for that datastore. This is because vCenter Operations Standard collects real time performance data from the host performance manager. When you rename a datastore, the host performance manager does not pick up the changed name, marks the renamed datastore as inaccessible, and stops collecting data for this datastore.
    Workaround: Restart the hostd service on the ESX server that hosts the renamed datastore.
    1. Log in to the ESX host machine using the console or ssh.
    2. Run the following command to restart the hostd service: /etc/init.d/mgmt-vmware restart
    Note: While restarting the mgmt-vmware service does not affect the virtual machines running on the ESX host, it affects operations performed on the ESX host, for example, operations performed by the vCenter Server. Therefore, you must minimize the number of operations performed on the ESX host before you restart the mgmt-vmware service.
  • User roles are not propagated properly in vCenter Operations Standard
    In the vSphere Client, vCenter Operations Standard does not take into account the Propagate check box for user roles. For example, if you assign to a user No access role at the host level and select to propagate this role, the user can still access child objects of the host in the vCenter Operations interface.
  • You might not be able to create a support bundle using the vCenter Operations Standard user interface
    If the vCenter Operations Standard Administration portal is not accessible to you but you need to create a support bundle, you can use the virtual appliance console to access the log files.
    Workaround: Generate a support bundle using the vCenter Operations virtual appliance console.
    1. Use a vSphere Client to log in to the ESX host or vCenter Server that host the vCenter Operations virtual appliance.
    2. From the inventory tree, select the vCenter Operations virtual appliance and click the Console tab.
    3. Log in using the root user credentials.
    4. In the console, type cd /usr/lib/vmware-vcops and press Enter.
    5. Type tar cvzf /tmp/vcops-support.tar.gz user tomcat/logs and press Enter to extract all log files.
    6. Exit the console of the vCenter Operations virtual appliance.
    7. Use a secure copy client to transfer the support bundle to your local machine:
      Type scp root@<VAaddress>:/tmp/vcops-support.tar.gz <local_destdir>, where VAaddress is the IP address of the vCenter Operations virtual appliance, and local_destdir is the local directory to which the support bundle will be copied.
  • Objects appear with question marks if you change the password for the Collection user in the vSphere Client
    vCenter Operations uses the credentials you provide on the vCenter Operations Standard Administration portal to connect to the vCenter Server to monitor. If you change the password for the Collection user in the vSphere Client, the password is not updated in vCenter Operations Standard. The application continues to use the old Collection password until the data collector is restarted. After the restart, vCenter Operations tries to log in to the vCenter Server using the old Collection password. Because this password is no longer valid, the connection fails and vCenter Operations Standard can no longer collect any data for the vCenter Server. All objects in the Inventory view appear with question marks.
    Workaround: Update the password for the Collection user in the vCenter Operations Standard Administration portal.
    1. Log in to the vCenter Operations Standard Administration portal.
      The URL format is https://<VAaddress>/adminMain.action, where VAaddress is the IP address of the vCenter Operations virtual appliance.
    2. On the Setup tab, click Update.
      The vCenter Server Info dialog box opens.
    3. In the Collection password text box, type the new password for the Collection user.
    4. Click Test to verify that vCenter Operations Standard connects successfully to the vCenter Server.
    5. Click Save to update the Collection password.
  • You cannot access vCenter Operations Standard from the vSphere Client if you change the IP address of the vCenter Operations virtual appliance
    If you change the IP address of the vCenter Operations virtual appliance, the vCenter Operations Standard icon disappears from the vSphere Client Home page. In the Plug-in Manager window, vCenter Operations Standard becomes Disabled and the following error message might appear in the Errors column: viClientConfigxml: Unable to connect to the remote server.
    If you restart the vSphere Client and navigate to the Plug-in Manager window, vCenter Operations Standard appears in the list of available plug-ins. If you click the Download and Install link, the following error message appears:
    An internal error occurred in the vSphere Client.
    Details: Invalid URI: The URI is empty.

    Workaround: Update the registration with the vCenter Server on the vCenter Operations Standard Administration portal.
    1. Close the vSphere Client.
    2. Log in to the vCenter Operations Standard Administration portal.
      The URL format is https://<VAaddress>/adminMain.action, where VAaddress is the new IP address of the vCenter Operations virtual appliance.
    3. On the Setup tab, click Update.
      The vCenter Server Info dialog box opens.
    4. Click Test to verify that vCenter Operations Standard connects successfully to the vCenter Server.
    5. Click Save to close the vCenter Server Info dialog box.
    6. Log in to the vSphere Client and navigate to the Home page.
      vCenter Operations Standard appears in the Solutions and Applications pane.
  • Changes in vCenter Server inventory and object properties are not reflected in vCenter Operations Standard after a network failure
    If the network connection on the vCenter Server that you monitor fails, and you modify the inventory on the vCenter Server, vCenter Operations Standard will not display the changes in the inventory when the network connection is restored.
    Workaround: Restart the vCenter Operations service.
    1. On the vCenter Operations Standard virtual appliance settings page, click the Appliance Administration tab.
    2. Type the root user password above the Restart button and click Restart.
      The Restart successful message appears when the restart operation completes.

Top of Page

Documentation and Online Help


  • Incorrect product name in vCenter Operations Standard online help
    • Topic Start vCenter Operations Standard in section Installing and Starting vCenter Operations Standard of the online help reads In the Solutions and Applications panel, click Operations Manager.
      Should read:
      In the Solutions and Applications panel, click vCenter Operations Standard.
    • Section Compare Objects of the online help contains four instances of the following sentence: You must open vCenter Operations Standard by clicking Operations Manager in the Solutions and Applications panel of the vSphere Client.
      Should read:
      You must open vCenter Operations Standard by clicking vCenter Operations Standard in the Solutions and Applications panel of the vSphere Client.
    • Section Determine Where to Power On a New Virtual Machine of the online help contains two instances of the following sentence: You must open vCenter Operations Standard by clicking Operations Manager in the Solutions and Applications panel of the vSphere Client.
      Should read:
      You must open vCenter Operations Standard by clicking vCenter Operations Standard in the Solutions and Applications panel of the vSphere Client.
    • Section Check Specific Metrics of a Particular Object reads You must open vCenter Operations Standard by clicking Operations Manager in the Solutions and Applications panel of the vSphere Client.
      Should read:
      You must open vCenter Operations Standard by clicking vCenter Operations Standard in the Solutions and Applications panel of the vSphere Client.
    • Section Find Objects With Potential Performance Problems reads You must start vCenter Operations Standard by clicking Operations Manager in the Solutions and Applications panel of the vSphere Client.
      Should read:
      You must start vCenter Operations Standard by clicking vCenter Operations Standard in the Solutions and Applications panel of the vSphere Client.
    • Section Display Information for an Object with a Reported Problem reads You must start vCenter Operations Standard by clicking Operations Manager in the Solutions and Applications panel of the vSphere Client.
      Should read:
      You must start vCenter Operations Standard by clicking vCenter Operations Standard in the Solutions and Applications panel of the vSphere Client.
  • Incorrect information on supported browsers in vCenter Operations Standard Installation and Administration Guide
    The VMware vCenter Operations Standard Installation and Administration Guide that is distributed as part of the VMware vCenter Operations Standard media kit contains incorrect information on supported browsers.
    For the latest information about supported browsers, see the updated guide on the VMware Web site.

Top of Page