Chargeback Manager 2.7.2 for Service Providers Release Notes
The release notes cover the following topics:
Chargeback Manager 2.7.2 for Service Providers | 20 October 2016| Build 4483989
Last Document Update: 21 November 2016
What's New in this Release
vCenter Chargeback Manager 2.6 is the last enterprise version and 2.7.1 is the first release for service providers. Chargeback Manager 2.7.2 for Service Providers release is intended for use only by service providers under the terms and conditions of VMware Service Provider Partner (VSPP) Program.
- Chargeback Manager 2.7.2 supports vCenter 6.x
Chargeback Manager 2.7.2 supports vCenter 6.0 and 6.5 Beta. Chargeback Manager 2.7.2 uses storage policies as part of vCenter 6.x as storage profiles are deprecated. Chargeback Manager 2.7.2 can collect vCenter 6.x storage policies and continues to collect storage profiles for versions prior to vCenter 6.x.
- Upgraded Apache Tomcat to 8.5.4
Apache Tomcat is upgraded to 8.5.4 in this release.
- Upgraded Open SSL to version 1.0.2j
The Open SSL version is upgraded to 1.0.2j.
- Chargeback Manager 2.7.1 and 2.7.2 supports TLS v1.1/1.2
Chargeback Manager 2.7.1 and 2.7.2 supports TLS v1.1/1.2 for data collectors. To use a particular version of SSL protocol, enter -Dhttps.protocols argument and mention SSL versions in the DATA_COLLECTOR_service_install.bat file.
For example, to use TLS v1.2, enter -Dhttps.protocols="TLSv1.2" in the DC_Service_Install.bat file.
- Upgraded Java version to 1.7.0_111
Java version is upgraded to 1.7.0_111.
Chargeback Manager 2.7.2 includes the following product documentation.
This section provides information about the supported operating
systems, database management systems, and vCenter Server versions. The vCenter Chargeback Manager Installation and Upgrade Guide 2.7.0 provides detailed information about the system requirements for installing and running the application.
- Microsoft SQL 2008 R2 Service Pack 2 Enterprise and Standard Edition (64-bit)
- Microsoft SQL 2008 R2 Enterprise and Standard Edition (64-bit)
- Microsoft SQL 2012 Enterprise and Standard Edition (64-bit)
- Oracle Database 11 g R2 Enterprise and Standard (64-bit)
- Oracle Database 12c Enterprise and Standard (64-bit)
- SQL Server 2014 Enterprise (SP2) and Standard (SP2) (64-bit)
Supported Operating Systems
Supported VMware vCenter Server Versions
- vCenter Server 6.0
- vCenter Server 6.0 Update 1
- vCenter Server 6.0 Update 2
- vCenter Server 6.5 Beta
- vCenter Server 5.1 Update 2
- vCenter Server 5.5 Update 1
- vCenter Server 5.5 Update 2
- vCenter Server 5.5 Update 3
Supported VMware vCloud Director Versions
- VMware vCloud Director 8.0, 8.0.1, 8.0.2 and 8.10
- VMware vCloud Director 5.5
- VMware vCloud Director 5.5.1 through 5.5.5
- VMware vCloud Director 5.6.3, 5.6.4, 5.6.5
Supported vShield Manager Versions
- vShield Manager 5.1.3
- vShield Manager 5.5.1 through 5.5.4
- vShield Manager 5.5
- vShield Manager 184.108.40.206
Supported VMware NSX Manager Versions
- VMware NSX Manager 6.2.2 and 6.2.3
- VMware NSX Manager 6.2.4
The following section describes the minimum requirement for Chargeback Manager 2.7.2.
Ensure to have at least 8 GB RAM for 64-bit Chargeback Manager 2.7.2.
Upgrading Chargeback Manager
You can upgrade an existing vCenter Chargeback Manager 2.7 or later instance to vCenter Chargeback Manager 2.7.2. If you are upgrading Chargeback Manager 2.5.1 or later to 2.7.2, you need the VMware Service Provider Partner license key. See the vCenter Chargeback Manager 2.7 Installation and Upgrade Guide for detailed instructions.
The known issues in this release are listed in this section. Workarounds, if any, are provided in the issue description.
- After you upgrade Chargeback Manager, the installer log displays a warning message
After you upgrade a multi-node Chargeback Manager to 2.7.2, the installer log displays the following warning messages:
Note: This warning does not cause any functional impact on the installation of Chargeback Manager.
- Copy Folder:
Destination: C:\Program Files\VMware\VMware vCenter Chargeback\Apache2.4\conf\ssl
Additional Notes: WARNING - There was a problem copying C:\Program Files\VMware\VMware vCenter Chargeback\Backup\conf\ssl
Additional Notes: WARNING - Source C:\Program Files\VMware\VMware vCenter Chargeback\Backup\conf\ssl\default.cert does not exist.
- Delete Folder:
Additional Notes: WARNING - There was a problem deleting C:\Program Files (x86)\VMware\VMware vCenter Chargeback\vCenter-CB-Tools
- Copy File:
Destination: C:\Program Files\VMware\VMware vCenter Chargeback\DataCollector-Embedded\classes\dc.properties
Additional Notes: WARNING - Source C:\Program Files\VMware\VMware vCenter Chargeback\Backup\dc.properties does not exist.
Reason: As this is fresh setup, Backup folder will not be there, still installer is searching for it.
- After the Chargeback Manager upgrade, installation is completed with a fatal warning message
When you upgrade Chargeback Manager to 2.7.2 with an Oracle database, the installation is completed with a fatal error message. This is due to the upgrade scripts that insert a NULL name in a column where NULL is not allowed.
This warning does not affect the functionality of Chargeback Manager.
Report Management Issues
The on-demand report generation fails with an error Decryption of the failed password
If you add vCenter Server Appliance, which is configured in embedded
Postgres database to Chargeback Manager in on-demand mode and that has
Enable Stats Replication flag set to false, then on-demand reports
generation fails with an error:
Decryption of the password failed.
Hierarchy Management Issues
Changes to a chargeback hierarchy are not reflected in the concurrent user sessions
When you perform a hierarchy creation, deletion, and renaming an operation, these are not automatically reflected in a concurrent user session. 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
While getting active moids for large a vCenter server hierarchy, the VI inventory faces timeout issues
When fetching active moids for large a vCenter server hierarchy, the VI inventory displays a timeout message impl.Inventory: java.net.SocketTimeoutException.
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.
When you click the Test VMware cloud Director database connection link, the following error message is displayed:
Connection with VMware Cloud Director database failed
This warning does not affect the functionality of Chargeback Manager.
Additional vCloud data collector and vShield Manager data
collector appears in the system health page. This happens when new Chargeback Manager
2.7.2 installation is pointed to an existing Chargeback Manager database. You can see more vCloud data collector and vShield Manager data collector on the system health page as PASSIVE. Database also has to display two vCloud data collector and vShield Manager data collectors.
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. 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 during daylight saving.
If daylight saving is configured, then the vShield Manager data
collector does not account for the external network utilization data in
the 25th hour.
vCenter Chargeback Manager shows duplicate datastore entries
If you share a datastore with more than one ESXi host and each ESXi host
is added to different vCenter Servers, after adding these vCenter
Server instances to vCenter Chargeback Manager you can see the datastore listed
multiple times in the vCenter Chargeback Manager UI. When a datastore is shared by two ESXi hosts and each of these are added to
different vCenter Server instances. 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. You
must set the same rate factors on both the datastore entries and keep
them under the same datastore tier always. Otherwise, the corresponding cost
and data usage reported might have errors.
Ensure that the Windows User account password does not contain any special characters
The Windows User account password cannot contain any special
characters, the installer might fail if the password contains special
Problem with datastore tier rate factors at vCenter Data-Collector level
If you want to generate allocation reports at vCenter Data-Collector level that have multiple datastores grouped under different datastore tiers, and if you want to charge them separately by using different rate factors that are set through the Infrastructure cost option, then those rate factors cannot be applied at the vCenter Data-Collector level because by default Chargeback Manager applies the rate factor as 1 at this level.
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 vCenter Server
with DHCP, vCenter Server is assigned a static IP address.
You might not connect to the vCenter Server from Chargeback Manager, and even if you attempt
to remove the vCenter Server entry from the Chargeback Manager, the operation fails.
For more information, see KB 2054587.