VMware

VMware vCenter Chargeback Manager 2.5 Release Notes

vCenter Chargeback Manager 2.5 | 10 September 2012 | Build 833114

Last Document Update: 12 December 2012

Recent Updates:

What's in the Release Notes

The release notes cover the following topics:

What's New in this Release

The vCenter Chargeback Manager 2.5 provides various new features.

  • Cost model is now pricing model
    Starting with this release of vCenter Chargeback Manager, we have a terminology change. Cost model is now referred to as pricing model.

  • Support for new VMware vCloud Director features
    This release of vCenter Chargeback Manager supports VMware vCloud Director 5.1. vCenter Chargeback supports the new vCloud Director features like elastic vDCs, independent disks, and storage classes. If an independent disk is associated with a virtual machine, then the allocation and usage is accounted for based on the billing policy used. If the independent disk is not associated with a virtual machine, then allocation set on the disk is accounted for when generating reports.
    The vCloud Director storage classes utilize the vSphere storage profiles. Therefore, the rate factors that you define on the storage profiles are accounted for when calculating storage costs for a vCloud Director entity that is mapped to the corresponding storage class.
    vCenter Chargeback Manager also supports the networking changes in vCloud Director 5.1, such as networks under an organization now belong to the org vDCs, introduction of the Gateway entity, and counters for accounting load-balancer service, static routing service, and full gateway configuration.

  • Support for database partitioning
    In this release, the vCenter Chargeback Manager installer checks whether the database support partitioning and provides you with an option to partition the vCenter Chargeback Manager database. Database partitioning helps in improving the performance of vCenter Chargeback Manager. The installer check for the database partitioning support during both fresh installation and during upgrade of existing setup.

  • Support for read-only domain controllers
    When configuring an LDAP server on vCenter Chargeback Manager, you can use a Microsoft Windows Server 2008 Active Directory read-only domain controller.

  • Support for charging a minimum cost if resource utilization is less than resource allocation
    In this release of vCenter Chargeback Manager, you can configure the base rates in the pricing models such that the corresponding computing resources are charged for the entire allocated units even if the actual resource utilization is less than the resource allocation. This ensures that a minimum cost is charged for computing resources on which allocations have been defined.

  • Configuring guest operating system cost as one-time cost
    In vCenter Chargeback Manager, you can now configure the guest operating system costs as one-time costs in the pricing model. Guest operating system costs that are configured as one-time costs cannot be prorated and also cannot be based on the power-state of the virtual machine . Also, you can configure a common cost for all guest operating systems, except the ones for which you have explicitly configured costs in the pricing model, by using the All Other Operating Systems option from Guest OS Name list when creating and modifying a pricing model.

  • Charging fixed costs on entities based on attribute name-value pair
    In this release of vCenter Chargeback Manager, you can associate fixed costs with attribute name-value pairs in a pricing model. When a report is generated on a entity by using this pricing model, the appropriate fixed cost is charged on the entity based on the attribute name-value pair configured on the entity. For example, you want to charge different fixed costs on virtual machines based on the type of storage on which the virtual machine files reside. This can be done by tagging the virtual machines with attribute name-value pairs that define the storage type used by the virtual machines. You can then define attribute-based fixed cost rules in the pricing model.

  • Ability to stop report generation
    In this release, vCenter Chargeback Manager enables you to stop and delete any running report. You might want to stop report generation in many cases, such as report generation is taking too much time or generation of multiple large reports is using too many resources. In such cases, you can stop and delete the report generation from the Reports tab of vCenter Chargeback Manager.

  • Email alert notification of system health
    You can now configure the alert notification settings in vCenter Chargeback Manager to ensure that you are notified through email whenever a component in your vCenter Chargeback Manager setup goes down or comes back up. vCenter Chargeback Manager sends an email alert whenever a component in your vCenter Chargeback Manager setup, such as the data collector or a vCenter Server, goes down or is restored after a downtime. Additionally, vCenter Chargeback Manager sends a periodic email listing all the components that are down.

System Requirements

This section provides information about the supported operating systems, database management systems, and vCenter Server versions. The vCenter Chargeback Manager User's Guide provides detailed information about the system requirements for installing and running the application.

Supported Operating Systems

  • Microsoft Windows Server 2003 with SP2 (32-bit and 64-bit)
  • Microsoft Windows Server 2003 R2 (32-bit and 64-bit)
  • Microsoft Windows Server 2008 with SP2 (32-bit and 64-bit)
  • Microsoft Windows Server 2008 R2 (64-bit)

You can install and run vCenter Chargeback Manager on any supported localized Windows operating system. However, all the labels and text messages in the installer and application user interface (including the plug-in in the vSphere Client) are displayed in English only. The application supports ASCII, extended ASCII, and non-ASCII characters. However, the characters are rendered correctly only if the client machine uses the appropriate fonts and the Web browser supports all the characters. The installer does not support all characters. Ensure that the information entered in the installer contains only the supported characters as specified in the install and upgrade instructions in this release notes and in the vCenter Chargeback Manager User's Guide.

Supported Database Management Systems
vCenter Chargeback Manager supports the following database management systems:

  • Microsoft SQL Server 2008 R2 (32-bit and 64-bit) (Standard and Enterprise)
  • Microsoft SQL Server 2008 with SP2 (32-bit and 64-bit) (Standard, Enterprise, and Datacenter)
  • Microsoft SQL Server 2008 Express (64-bit)
  • Microsoft SQL Server 2005 with SP4 (32-bit and 64-bit)(Standard, Enterprise, and Datacenter)

vCenter Chargeback Manager supports the Standard and Enterprise edition of the following database management systems:

  • Oracle Database 11g Release 2
  • Oracle Database 11g Release 1
  • Oracle Database 10g Release 2
  • Oracle Database 10g Release 1

Supported vCenter Server Versions and vCenter Server Databases

  • vCenter Server 5.1
  • vCenter Server 5.0 Update 1b
  • vCenter Server 4.1 and all corresponding Update Releases
  • vCenter Server 4.0 and all corresponding Update Releases

Important: We recommend that you do not add a vCenter Server 5.0 or vCenter Server 5.0 Update 1 server to vCenter Chargeback Manager because of a known memory leak issue. Also, do not add a vCenter Server 5.0 Update 1a server because of a known upgrade issue in vCenter Server. If you have a vCenter Server 5.0, vCenter Server 5.0 Update 1, or vCenter Server 5.0 Update 1a server, then first upgrade this to vCenter Server 5.0 Update 1b and then configure it in vCenter Chargeback Manager.

vCenter Chargeback Manager only supports vCenter Server databases that are created in Microsoft SQL Server or Oracle Database. vCenter Chargeback Manager does not support vCenter Server databases created in DB2.

Supported Web Browsers and Flash Player Plug-in

  • Microsoft Internet Explorer 7.x, and 8.x
  • Mozilla Firefox
  • Adobe Flash Player for Windows Plug-in version 10.1
  • Adobe Flash Player for Linux version 10.1 (Plug-in for Mozilla Firefox running on Linux Platform)

Supported VMware vCloud Director Versions

  • VMware vCloud Director 5.1
  • VMware vCloud Director 1.5 and later

vCenter Chargeback Manager 2.5 does not support any release of VMware vCloud Director prior to VMware vCloud Director 1.5

Supported VMware vCenter Operations Versions

  • VMware vCenter Operations 5.0 and later releases

Supported vCenter Chargeback Manager API Versions

The table below lists the different vCenter Chargeback Manager versions and the corresponding API versions that they support.

Product/API Versions API 1.5 API 2.0 API 2.5
vCenter Chargeback Manager 2.5.0 Yes Yes Yes
vCenter Chargeback Manager 2.0.1 Yes Yes No
vCenter Chargeback Manager 2.0.0 Yes Yes No
vCenter Chargeback Manager 1.6.2 Yes No No
vCenter Chargeback Manager 1.6.1 Yes No No
vCenter Chargeback Manager 1.6.0 Yes No No
vCenter Chargeback Manager 1.5.0 Yes No No

Preinstallation Tasks

Before you install and use the VMware vCenter Chargeback Manager application, you must perform the following tasks. For detailed pre-install and pre-upgrade instructions, refer to the vCenter Chargeback Manager Install and Upgrade Guide.

  • Create a vCenter Chargeback Manager database and database user
    You must create a database for vCenter Chargeback Manager to store the application-specific data. Ensure that this database is not configured to be case-sensitive. In addition, you must also create a database user having permissions to create and delete schema, as well as read from and write to the database.
  • Set a static IP address on the machine
    You must set a static IP address on the machine on which you plan to install vCenter Chargeback Manager. You can obtain a static IP address from your network administrator. Preferably, obtain and set static IP addresses on all the servers and databases that the application will communicate with. In the case of a multi-homed machine, you can configure vCenter Chargeback Manager with only one interface. That is to say, although you can install vCenter Chargeback Manager on a multi-homed machine, you can use only the IP address or FQDN that you provide during the installation to access and use vCenter Chargeback Manager. Also, if the different components, such as data collectors and vCenter Servers, in a vCenter Chargeback Manager setup are installed on multi-homed machines, vCenter Chargeback Manager communicates with these components by using the URL specified when configuring the components in vCenter Chargeback Manager.
  • Ensure that MSI installation is enabled
    You must ensure that MSI installation is enabled on the machine. If it is not, you must manually install Microsoft Visual C++ 2005 Redistributable Package (x86) before running the vCenter Chargeback Manager installer.
  • Check whether the required ports are free
    Ensure that the ports that you specify during the installation are free. While installing vCenter Chargeback Manager, you must specify the port numbers for the HTTP port (default 8080), load-balancer port (default 8009), and HTTPS port (default 443).
  • Ensure that port exceptions are configured on Windows Firewall
    If Windows Firewall is enabled, you must set port exceptions for the HTTP, load-balancer, and HTTPS ports on the Windows Firewall. If these exceptions are not set, the application will not be usable.
  • Ensure that system time of all the servers and databases are in sync
    You must ensure that the system time of the machines on which you install vCenter Chargeback Manager and vCenter Chargeback Manager database are in sync. If you plan to install a separate data collector on a different machine, then the system time of this machine must be in sync with that of the other machines.
  • Ensure that the Windows user has the Log on as a service permission
    If you want to use the Windows Authentication option for the vCenter Chargeback Manager database, you must ensure that the Windows user has the Log on as a service permission. If this permission is not set on the user, the installation fails. Also, the installer must be run in the context of this Windows user.
  • Ensure that the SQL Server Browser service is running if you are using a Microsoft SQL Server database and using the database instance name and a dynamic database instance port to connect to the vCenter Chargeback Manager database or vCloud Director database.
  • Ensure that the vCenter Chargeback Manager database is case-insensitive.

Quick Install

Download the vCenter-CB-2.5.0-826950.zip file, and extract the contents on to the machine on which you want to install vCenter Chargeback Manager. Do not run the installer from a remote machine. To install vCenter Chargeback Manager:

  1. Run the vCenter-CB.exe file.
    The installation wizard is displayed.
  2. Click Next on the Introduction screen.
  3. Accept the end-user license agreement, and click Next.
  4. Provide the path for the installation directory, and click Next.
    Ensure that the installation directory path has at least one directory (for example, C:\vCenterChargeback\) and does not point to just a drive (for example, C:\). If the specified installation directory exists, ensure that it is empty. If the specified installation directory does not exist, the installer will create the directory. Also, the directory path must contain only ASCII characters.
  5. Configure the following vCenter Chargeback Manager database-related information, and click Next:
    • Database Type: The type of database used to create the vCenter Chargeback Manager database. This can be either SQL SERVER or ORACLE.
    • Database URL: The IP address of the system on which the vCenter Chargeback Manager database is installed along with either the port at which the database listener service is running or the vCenter Chargeback Manager database instance name. The database instance name must contain only ASCII characters.
      For Oracle Database, the database URL can be in any of the following formats:
      • <IP Address>
      • <Host Name>
      For SQL Server, the database URL can be in any of the following formats:
      • <IP Address>
      • <Host Name>
      • <IP Address>\<Database Instance Name>
      • <Host Name>\<Database Instance Name>
      You can also specify a well formed JDBC URL that starts with 'jdbc' and contains the database name.
    • Database Port: (Optional) The port on which the database service is listening for requests. If the port number is not specified, the installer uses the default port. For an Oracle database, you must specify the TNS listener port if you are not using the default port 1521. For an SQL Server database, specify the database instance port if you are using a static port.
    • Database Name: Name of the database in which vCenter Chargeback Manager stores the application-specific data. For Oracle Database, ensure that you provide the service name and not the SID.
    • SQL Authentication Mode: This option is applicable only for SQL Server database. For an SQL Server database, the authentication type can be either SQL Server Authentication or Windows Authentication.
    • Database Username: The name of the database user. The database user must have privileges to create and delete schema, as well as read from and write to the database. If you select Windows Authentication for SQL Authentication Mode, you must provide the Windows user account name. The user name must be of the form <Domain_Name>\<User_Name>. The user must have the Log on as a service permission.
    • Database Password: Password for the user name that you have provided. If you select Windows Authentication for SQL Authentication Mode, you must provide the password for the Windows user account. Ensure that the Windows user account password does not contain any special characters. The installer might fail if the password contains special characters.
    If the database does not support partitions, a dialog recommending you upgrade the database to one that supports database partitions is displayed. If you want to use the specified database details, click Continue, else click Change database, go to previous screen and provide new database details.
    If the installer successfully connects to the database and the database user has CREATE, INSERT, and DROP privileges, the next screen is displayed.
  6. Enter the load balancer-related information, and click Next:
    • IP Address: Static IP address or the FQDN of the machine on which you are installing the load balancer. Do not use localhost instead of the IP address or FQDN.
      Note: In the case of a multi-homed machine, you can configure vCenter Chargeback Manager with only one interface. If you are installing vCenter Chargeback Manager on a multi-homed machine, you can only use the IP address or FQDN that you provide in this step to access and use vCenter Chargeback Manager.
    • Admin Email Address: Email address of the server administrator. Ensure that the email address contains only ASCII characters.
    • HTTPS Port: An unused port through which the Apache Server communicates. The load balancer listens on this port for user requests.
    If the specified port is free, the next screen is displayed.
  7. Select Install vCenter Chargeback Server, enter IP address and port details for the vCenter Chargeback Manager, and click Next:
    • IP Address: Static IP address or the FQDN of the machine on which you are installing vCenter Chargeback Manager. Do not use localhost instead of the IP address or FQDN.
    • HTTP Port: An unused HTTP port through which vCenter Chargeback Manager communicates.
    • Load-Balancer Port: An unused port through which vCenter Chargeback Manager can communicate with the load balancer (Apache Server).
    • Server Instance Name: A user-defined name for the vCenter Chargeback Manager instance. This name is used by the load balancer to identify the instance. Ensure that the instance name contains only ASCII characters.
    If the specified ports are free, the next screen is displayed.
  8. Enter a user name and password for the administrative account that will be used to manage the vCenter Chargeback Manager application, and click Next.
    The password must be less than or equal to 24 characters in length.
    Note: If you are using Oracle Database for your vCenter Chargeback Manager database, ensure that the user name for the administrative account contains only ASCII and non-ASCII characters. Extended ASCII characters in the user name is not supported. This restriction is not applicable if you are using Microsoft SQL Server for you vCenter Chargeback Manager database.
  9. Select the Install Data Collector option and click Next.
    You must have at least one instance of the data collector that is running and registered with the application for the database synchronization jobs to run.
  10. Review the information displayed on the Pre-Installation Summary screen, and click Install.
    The installer starts installing the various components and creating the database schema. If the installation is successful, the URL for accessing the vCenter Chargeback Manager application is displayed.
  11. Note this URL, and click Done.
    The installer displays a dialog stating whether you want to generate a default SSL certificate or a self-signed SSL certificate.
  12. Click Generate my own SSL Certificate.
    A command window is displayed.
    1. Provide a pass phrase for the default key and press Enter.
      You are prompted to enter the pass phrase three more times. Provide the same pass phrase and press Enter each time.
    2. Provide the required certificate information and press Enter.
      You are prompted to enter the following information:
      • Country Code: A two letter code for the country.
      • State or Province Name: Name of the state or province.
      • Locality Name: Name of the city or town.
      • Organization Name: Name of the organization.
      • Organization Unit Name: Name of the department or organization unit.
      • Common Name: Your name.
      • Email Address: An email address.
    3. Provide the requested extra attributes for the certificate and press Enter.
      You are prompted to enter the following information:
      • A challenge password: A user-defined password.
      • An optional company name: Company name. This is optional and can be left blank.
    4. Provide the pass phrase and press Enter.
      You are prompted to enter the pass phrase again. Provide the same pass phrase and press Enter.
    5. Press any key to complete the process and close the window.
    An SSL certificate is successfully installed.
    If you click Generate default SSL Certificate, an SSL certificate with default values is generated. You are not prompted for any information. Press any key, when prompted, to close the command-line window.

For detailed install instruction, refer to the vCenter Chargeback Manager User's Guide.

IMPORTANT: After installing vCenter Chargeback Manager 2.5, you must install the patches from KB 2041041.

Upgrading vCenter Chargeback Manager

You can upgrade an existing vCenter Chargeback Manager 2.0 or later setup to vCenter Chargeback Manager 2.5. Refer to the vCenter Chargeback Manager Installation and Upgrade Guide for detailed instructions.
If you have a vCenter Chargeback 1.5.x or 1.6.x setup, you must first upgrade to vCenter Chargeback Manager 2.0 before upgrading to vCenter Chargeback Manager 2.5.

IMPORTANT: After installing vCenter Chargeback Manager 2.5, you must install the patches from KB 2041041.

Resolved Issues

This section lists the issues that have been fixed in this release.

Report Management Issues

  • Cost variance graph in the report dashboard includes an extra day of costs for non-prorated fixed costs
    In prior releases of vCenter Chargeback Manager, if a non-prorated fixed cost is set on a entity, then the cost variance graph for this entity includes the fixed cost for t + 1 days, where t is duration for which the cost is set on the entity. However, this issue does not occur in the cost reports. This issue is fixed in this release.

  • Generation of Cost Projection and Cost Optimization reports fails with error for entities having more than 50 characters in their name
    vCenter Chargeback Manager fails to generate the Cost Projection and Cost Optimization reports in the Report Dashboard and logs an error similar to the following:

    Error while retrieving usage information from VC: 90.110.10.11
    Entry "T_Win2K3R2_64 (29e3e78a-3d32-402e-8804-ca8a5e08fd70)" on line 37 column 1 is not within the string sizes 0 - 50

    This issue occurs if the name of any entity in the vCenter Server inventory contains more than 50 characters. This issue is fixed in this release.

Other Issues

  • Storage Synchronization job fails with Violation of UNIQUE KEY constraint error
    If you have configured a vCenter Server 5.0 server in vCenter Chargeback Manager, then the Storage Synchronization job of the data collector might fail with the following error:

    ERROR util.JDBCExceptionReporter 6771: Violation of UNIQUE KEY constraint 'CB_STORAGE_CAPABILITY_U1'. Cannot insert duplicate key in object 'dbo.CB_STORAGE_CAPABILITY'.

    This issue occurs if you have defined storage capabilities in vCenter Server and delete and re-add a storage capability with the same name in vCenter Server. This issue is fixed in this release of vCenter Chargeback Manager.

Known Issues

The known issues in this release are listed in this section. Workarounds, if any, are provided in the issue description.

Hierarchy Management Issues

  • Changes to a chargeback hierarchy are not reflected in the concurrent user sessions
    Hierarchy creation, deletion, and renaming operations performed by a user are not automatically reflected in concurrent user sessions. The concurrent users must log out and then log in again to see these changes. Any other change to the chargeback hierarchy, such as adding or deleting an entity, might not reflect immediately in the concurrent user sessions. After a change is made to the chargeback hierarchy, the hierarchy must be manually refreshed in the concurrent user sessions. Users can refresh the chargeback hierarchy by clicking the refresh button next to the chargeback hierarchy or by loading another chargeback hierarchy and then reloading the chargeback hierarchy. The refresh button appears only if vCenter Chargeback Manager detects changes to the chargeback hierarchy.

  • Re-added virtual machine does not have the cost information configured on it
    If you delete an ESX host from a vCenter Server, all the virtual machines belonging to the ESX host are deleted from the chargeback hierarchy. After re-adding the ESX host to the vCenter Server, you can add the virtual machines on this ESX host back to the respective chargeback hierarchies in vCenter Chargeback Manager. However, any entity-specific cost configuration set on the virtual machines prior to deleting the ESX host from the vCenter Server is lost. You must, therefore, migrate all the virtual machines on an ESX host before removing the ESX host from the vCenter Server.

Cost Management and Configuration Issues

  • Storage cost for non-compliant virtual machines is calculated using the rate factor set on the datastore
    For non-compliant virtual machines, vCenter Chargeback Manager uses the rate factor set on the datastore in which the virtual machine resides. If the datastore is grouped under any storage profile or tier, then the rate factors defined on the profile or tier is used. The rate factor for the profile configured on the non-compliant virtual machine is not used.

  • Incorrect costs reported if resource allocation and fixed costs are set with a start time lesser than the hierarchy creation time
    If resource allocation and fixed costs are set on the hierarchy root node with a start time that occurs before the hierarchy creation time, then the report includes the costs incurred before hierarchy creation time if the reporting period start time also occurs before the hierarchy creation time. For example, you have created a hierarchy on February 1. You then set a fixed cost on the hierarchy root node starting from January 1 although the hierarchy is created only on February 1. Now, if you generate a report on the hierarchy with the reporting period start time as January 1, then the report includes the fixed cost from January 1 to January 31 in the report even though the hierarchy was created on February 1.
    This issue occurs only for allocation units and fixed costs set on the hierarchy root node. The workaround for this issue is that you set resource allocation units and fixed costs on the hierarchy root node with a start time equal to or greater than the hierarchy creation time. Or generate a report on the hierarchy where the reporting duration has a start time equal to or greater than the hierarchy creation time.

Report Management Issues

  • Reports for a vCenter Server user might not contain the correct entities
    A report scheduled for a vCenter Server user might contain the usage and cost details for entities on which the user does not have permissions. The report might also exclude some entities on which the user has permissions. There is currently no workaround for this issue. However, reports might be generated correctly for the vCenter Server user whose credentials are used to add the vCenter Server to vCenter Chargeback Manager.

  • Inconsistent usage and cost data reported
    If you generate a report that considers the actual resource usage for a billing period including the past 24 to 36 hours from the report generation time, the usage data and cost included in the report might be inconsistent. This inconsistency might occur if vCenter Server has not completed the statistics roll-up or the data collector has not synchronized the rolled-up statistics in the vCenter Chargeback Manager database.

Other Issues

  • An Administrator user cannot exercise administrative privileges on a hierarchy created by a child user
    As a user with an Administrator role, you create a user, say UserA, and assign appropriate roles to the user on the application and resources in the application. UserA creates an hierarchy. Although you can access this hierarchy, you cannot exercise any administrative privileges on this hierarchy, such as creating and scheduling reports. If you create an automatic report scheduler that creates a report schedule for this hierarchy, then the schedule creation fails. Also, duplicate schedules might be created for other hierarchies on which you have access and that match the criteria defined in the automatic report scheduler. This might eventually lead to a out-of-memory issue as the number of duplicate report schedules increase in the application. This issue does not occur for other resources created by UserA.
    Workaround: Log in to vCenter Chargeback Manager as a Super User and explicitly assign the Administrator role to the Administrator user on the hierarchies created by the child users of the Administrator user.

  • vCenter Server user account is assigned the vCenter Guest User role instead of the Hierarchy Manager role
    You add a vCenter Server 5.1 machine to vCenter Chargeback Manager with the Register As vSphere Client Plug-in option selected. The vCenter Server user account provided has Single Sign-On enabled. When you access vCenter Chargeback Manager through the plug-in by using this user account, the user account is assigned the vCenter Guest User role instead of the Hierarchy Manager role.
    Workaround: Log in to vCenter Chargeback Manager as a super user and assign the Hierarchy Manager role to the vCenter Server user on the application and on the corresponding vCenter Server resource.

  • vCenter Chargeback Manager shows duplicate datastore entries
    If a datastore is shared by more than one ESXi host and each ESXi host is added to different vCenter Servers, after adding these vCenter Servers to vCenter Chargeback Manager you can see the datastore listed multiple times in the vCenter Chargeback Manager UI. Let us consider a datastore is shared by two ESXi hosts and each of these are added to different vCenter Servers. You add both these vCenter Servers to vCenter Chargeback Manager. When you select DataStores on the Edit Infrastructure Cost page of the Configure Cost tab, this shared datastore is listed twice.
    You must ensure that you perform the same set of action on both these datastores entries in vCenter Chargeback Manager. That is to say, you must set the same rate factors on both the datastore entries and keep them under the same datastore tier always. Else, the corresponding cost and usage data reported might be inconsistent or erroneous. Also, if the datastores are appearing under different storage profiles, as a best practice ensure that the storage profiles are grouped in to the same datastore tier.

  • The Hosts & Clusters and VMs & Templates Synchronization data collector jobs fails with an error
    You have added a vCenter Server, which does not have any datacenters, to vCenter Chargeback Manager. When you add the first datacenter to the vCenter Server, the Hosts & Clusters and VMs & Templates Synchronization data collector job fails and logs an error similar to the following:
    ERROR impl.HibernateVCenterBaseDAOImpl:
    com.vmware.vim.vcenter.chargeback.dao.impl.HibernateVcEntityRelationDAOImpl@b3319f
    org.hibernate.PropertyValueException: not-null property references a null or transient value:
    com.vmware.vim.vcenter.chargeback.dto.CbVcEntityRelation.cbVcEntityByVcParentEntityId

    Workaround: Restart the Data Collector service.

  • Correct reservation values are not reflected for expandable vApps and resource pools
    For expandable vApps and resource pools, the memory and CPU reservation values reflected in vCenter Chargeback Manager might differ from the actual reservation values as shown in vSphere Client. vCenter Chargeback Manager shows the last explicitly set reservation value for expandable vApps and resource pools. To ensure that the correct values are reflected in vCenter Chargeback Manager, you must edit the settings for the vApp or resource pool in vSphere Client and save the current reservation values.

  • vCenter Chargeback Manager displays the disconnected hosts and orphaned virtual machines
    vCenter Chargeback Manager does not distinguish between connected and disconnected ESX hosts. Therefore, vCenter Chargeback Manager displays the disconnected hosts and orphaned virtual machines and accounts for the same in generated reports. Also, vCenter Chargeback Manager does not display the state of these ESX hosts and virtual machines. If a ESX host is disconnected from a vCenter Server and added to another vCenter Server, and both the vCenter Server instances are added to vCenter Chargeback Manager, then vCenter Chargeback Manager will display a duplicate entry for the ESX host. That is, vCenter Chargeback Manager will display an ESX host entry corresponding to the disconnected host and another corresponding to the host connected to the second vCenter Server. As a result, vCenter Chargeback Manager accounts for the disconnected host CPUs and orphaned virtual machines in vCenter Chargeback Manager licensing.

  • vCenter Chargeback Manager throws an error when deleting vCenter Server
    When you delete a vCenter Server whose entities are added to a hierarchy, vCenter Chargeback Manager shows a dialog box asking whether you want to retain the entities or delete them from vCenter Chargeback Manager. If you choose to delete the entities, then an error message similar to the following is displayed:
    vCenter Server 'vcId' or it's 'Hosts & Clusters and VMs & Templates Synchronization' job is not found.
    However, the delete operation is successful. This error message is displayed only if the vCenter Server hierarchy is displayed in the Manage Hierarchy tab when the vCenter Server is deleted. You must close all the relevant error dialog boxes displayed to continue normal functioning of vCenter Chargeback Manager.

  • Unable to download and install the vCenter Chargeback Manager plug-in from the Plug-ins Manager window of the vSphere Client
    This is a vSphere Client issue. Restart the vSphere Client and accept the vCenter Chargeback Manager SSL certificate. This might rectify the issue if the vSphere Client is able to communicate with vCenter Chargeback Manager. If the vSphere Client and vCenter Chargeback Manager are on different network domains, this issue might persist.

  • vCenter Chargeback Manager instance is not recognized as a part of the cluster
    If you have a two-instance cluster and the first vCenter Chargeback Manager instance fails due to some reason, all the requests currently being served by the first instance are moved to the second instance. After the first instance is restarted, if the second instance fails, the requests handled by the second instance are not moved to the first instance. That is, the failover does not happen because the second instance does not recognize the first instance as a part of the cluster. A workaround for this issue is to restart all the vCenter Chargeback Manager instances in the cluster. This issue also occurs for clusters with more than two instances. If any of the vCenter Chargeback Manager instances fails and is restarted, that instance starts serving user requests but is not recognized by the cluster until other instances are restarted.

  • The version of the vCenter Chargeback Manager plug-in in vSphere Client is not updated after upgrading vCenter Chargeback Manager
    After upgrading vCenter Chargeback Manager, vSphere Client reports the plug-in version as the version prior to upgrade when you check the version from Plug-ins > Manage Plug-ins. Although the plug-in is upgraded, the plug-in version is reported incorrectly. However, the plug-in version is reported correctly when checked from Tools > About in the plug-in.

VMware vCloud Director Data Collector and vShield Manager Data Collector Issues

Some of the following listed issues are common for both the VMware vCloud Director Data Collector and the vShield Manager Data Collector.

  • If the VMware vCloud Director database has a large history of chargeback events, the processing of the events might take a long time to complete. This issue happen if you integrate a vCloud Director 1.5 or vCloud Director 1.5.1 setup. For vCloud Director 5.1, the inventory synchronization time depends on the size of the inventory.

  • The vShield Manager data collector does not account for one hour of external network utilization data in the case of daylight savings time. If daylight savings is configured, then the vShield Manager data collector does not account for the external network utilization data in the 25th hour.