VMware

VMware vCenter Chargeback Manager 2.5.1 Release Notes

vCenter Chargeback Manager 2.5.1 | 11 June 2013 | Build 1131433

Last Document Update: 11 June 2013

What's in the Release Notes

The release notes cover the following topics: The vCenter Chargeback Manager 2.5.1 release provides a number of key bug fixes detailed in the Resolved Issues section. The vCenter Chargeback Manager 2.5.1 release also includes the following new feature.

  • Stats Migration Tool
  • Stats Migration Tool enables you to partition the Chargeback database performance stats table without requiring you to do an application upgrade. Earlier this option was available only as part of the Chargeback installer, if you did proceed with an upgrade to Chargeback version 2.5 without opting for partitioning then you did not have an option to enable partitioning later on, until you opted for an upgrade to the next version. This tool helps you partition the Chargeback database performance stats table anytime post Chargeback application upgrade to a version of 2.5 or later.Some of the advantages of using this tool instead of the installer option.
    • Time estimate & Monitoring progress of partitioning
    • Option to exit and run the tool at a later point
    • No downtime for datacollector although it is recommended that it should not be under heavy loads at the time of using the tool
    For more information on Stats Migration Tool see Knowledge Base article 2053665.

    Important
    The vCenter Chargeback Manager (CBM) contains a vulnerability in its handling of file uploads. Exploitation of this issue might allow an unauthenticated attacker to execute code remotely. To address this issue the ability to upload images and files has has been disabled in Chargeback 2.5.1.The Common Vulnerabilities and Exposures project cve.mitre.org has assigned the name CVE-2013-3520 to this issue.

    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 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.1 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.1-1131433.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.

    Upgrading vCenter Chargeback Manager

    You can upgrade an existing vCenter Chargeback Manager 2.0 or later setup to vCenter Chargeback Manager 2.5.1. 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.1.

    Resolved Issues

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

    Report Management Issues

    • Scheduled Reports Fail to Run
      The scheduled reports must be executed within a specific time frame as the report creation process is sensitive to the time at which the report schedule is executed. So, if multiple report schedules are run at the same instance of time, then all the reports might not be executed within the specific time frame which might result in error messages. This issue is fixed in this release.

    • Cancellation of running reports resulted in Usability issuesx
      In the earlier versions of Chargeback when you cancelled a running report the usability issues like a disabled delete button in the dashboard and insufficient time to query queued tasks were observed. These issues are resolved in this release.

    • Reports become unresponsive while in In-Progress or Cancellation state
      When you attempt to cancel a running report, the Chargeback Manager becomes unresponsive and the subsequent reports are not processed. This issue is resolved in this release.

    Cost Management Issues

    • Report is not considering the VC perfomance stats properly if the hierarchy contains the entities from more than one VC server.
      When you create a hierarchy with entities from two different VC servers with the performance stats for both the servers and attempt to generate a report. There is inconsistency in the entity cost of one of the VC, as one of the VC fails to consider the hierarchy level report. This issue is resolved in this release.

    • Custom Attribute based Report does not filter the fixed cost of the Virtual Machines.
      When you create custom hierarchy for two virtual machines and configure both of them with fixed cost and set the location value for one of them. There is inconsistency in the custom attribute report generated. This issue is resolved in this release.

    vCenter Data Collector Isssues

    • The Chargeback Manager displays incorrect status for the Embedded Data Collector.
      If a virtual machine is added and deleted during data collector down time, whenever data collector comes and tries to delete the virtual machine, there are two relations with the same key which cause the Chargeback Manager to report incorrect Data Collector status. This issue is resolved in this release.

    • The vCenter Data Collector creates multiple relations resulting in doubled cost for the affected entities.
      When a Data collector is found not responsive because of load then, the admin console automatically assigns jobs to another data collector and if the original data collector becomes responsive, it again assigns the job back to it. This kind of dynamic load balancing is causing multiple relations resulting in doubled costs for entities. This issue is resolved in this release.

    vCloud Integration Isssues

    • The NetworkSubTypeUpgrader fails during vCloud Director data collector upgrade.
      If the database contains network entities which has a vCloud Director data collector defined custom attribute in the old format (VcloudNetworkEntity-xxxxx) where a vCloud Director entity ID is present instead of a UUID, then the NetworkSubTypeUpgrader step fails during vCloud Director data collector upgrade. This issue is resolved in this release.

    • vApp networks is deleted in fresh CBM 2.5 with VCD 1.5 when vApp network event comes after the vApp event.
      When you deploy VCD 1.5 and create vApp events before vApp network events and deploy a new installation of CBM 2.5 setup pointing to the deployed VCD 1.5, the vApp network events are getting processed and deleted in CBM and are not displayed in the CBM user interface. This issue is resolved in this release.

    • Alert users when vCloud or vShield Manager Data Collectors encounter fatal errors.
      In the earlier versions of Chargeback Manager there was no option to alert users when vCloud or vShield Manager Data Collectors encountered fatal errors. This issue is resolved in this release.

    • VMware vShield Manager data collector stops working if the VSM provides the NaN valued stats instead of 0.
      When you deploy CBM 2.5 Setup with VCD 5.1.1 and monitor VSM data collector for some days, the VSM job stops working if the VSM gives the NaN value stats instead of 0 value. This issue is resolved in this release.

    vCenter Plugin (VI Client Plugin) Issues

    • Reports generated using Chargeback Manager plug-in are incorrect.
      When an exported report is requested through Chargeback VI plug-in, the Chargeback manager sends incorrect user authentication information which might result in incorrect report generation. This issue is resolved in this release.

    Other Issues

    • Chargeback Manager fails to delete the old license files after an upgrade.
      When you upgrade Chargeback Manager from one version to another version, Chargeback Manager fails to delete the license files of the previous version. Removing .dlf extension from the license files uploaded to vCenter resolves this issue. This issue is resolved in this release.

    • Reports run on different dates produce different values for the same date range.
      When you run reports of same date range but on different dates, the values generated by the reports are different, this is incorrect. Modifying the NTP configuration file resolves this issue.This issue is resolved in this release.

    • Base rate calculator in CBM 2.5 incorrectly changes the total of other costs to zero if total exceeds three digits.
      The Base rate calculator in CBM 2.5 is incorrectly changes the total of other costs to zero, if the total exceeds beyond three digits. This issues is resolved in this release.

    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.

    • While getting active moids for large vCenter server hierarchies the VI inventory faces timeout issues
      When fetching active moids for large vCenter server hierarchies the VI inventory timesout with impl.Inventory: java.net.SocketTimeoutException.

    Report Management Issues

    • Dashboard reports for hierarchy cancelled in previous run affect the execution of the same in the next report cycle
      When you cancel a Dashboard report which is in running state and you attempt to reconfigure the same in the next Dashboard report schedule, the report fails with the following error
      Requested report information cannot be found!.

    SQL Server Issues

    • Windows Authentication for SQL server on vCenter Chargeback virtual appliance is not supported
      The Chargeback Manager no longer supports the Windows authentication for SQL server using vCenter Chargeback virtual appliances.

    Other Issues

    • 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 erroneous.

    • Ensure that the Windows User account password does not contain any special characters
      The Windows User account password should not contain any special characters, the installer might fail if the password contains special characters.

    • The Chargeback Manager cannot delete or update vCenter server entry if the vCenter server is down
      When you add a vCenter Server to Chargeback Manager and configure the VC with DHCP, the VC is assigned a static IP. Now you might not be able to contact the VC from CBM even if you attempt to remove the VC entry from the CBM the operation fails. For more information see Knowledge Base article 2054587

      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.