User`s guide
Table Of Contents
- vCenter Chargeback User’s Guide
- Contents
- About This Book
- Introduction to vCenter Chargeback
- Installing vCenter Chargeback
- Hardware Requirements
- Software Requirements
- Prerequisites for vCenter Chargeback
- Download and Extract the vCenter Chargeback Installer
- Install vCenter Chargeback
- Create a vCenter Chargeback Cluster
- Install vCenter Chargeback with an Existing Database Schema
- Upgrading vCenter Chargeback
- Services Related to the vCenter Chargeback Application
- Accessing the vCenter Chargeback Application
- Data Collector
- Uninstall vCenter Chargeback
- Configuring Administration Settings
- Authenticating and Managing Users, Roles, and Permissions
- Managing Chargeback Hierarchies
- Creating a Chargeback Hierarchy
- Managing a Chargeback Hierarchy
- View a Chargeback Hierarchy
- Add a vCenter Chargeback Entity
- Add a vCenter Server Entity
- Rename a Chargeback Hierarchy or a Chargeback Entity
- Delete an Entity from the Hierarchy
- Delete a Chargeback Hierarchy
- Assign Attributes
- Move Entities Within a Hierarchy
- Allocate Computing Resource Units for a Chargeback Entity
- Share Virtual Machine Cost
- Backdate a Chargeback Hierarchy
- View Properties of a vCenter Server Entity
- Managing and Configuring vCenter Chargeback Cost Elements
- Generating Reports
- Monitoring System Health
- Administration Utilities
- Troubleshooting vCenter Chargeback
- Troubleshooting Utility
- Troubleshooting Issues in vCenter Chargeback
- Changed Timezone Setting Is Not Reflected
- Changes to Chargeback Hierarchy Are Not Reflected in the Concurrent User-Sessions
- Changes to the vCenter Server Hierarchy Are Not Reflected in vCenter Chargeback
- Installer Throws the SQL Driver Not Found Error
- LDAP Server Configuration Fails
- Non-English Characters Are Not Correctly Stored in the vCenter Chargeback Database
- Report Does Not Display the Disk Read and Disk Write Information
- Report Does Not Display the Memory Usage Value and the Corresponding Cost
- Report Does Not Display the Network Transmitted and Network Received Information
- Service Temporarily Unavailable Error
- Status of Failed Data Collector Is Not Reflected Immediately on the System Health Tab
- Storage Synchronization Job Fails
- Text and Messages on the vCenter Chargeback User Interface Are Not Correctly Displayed
- Unable to Access the vCenter Chargeback Application
- Unable to Add an LDAP Server
- Unable to Add vCenter Server in vCenter Chargeback
- Unable to Change the Password for the vCenter Chargeback Keystore
- Unable to Configure Another VMware Cloud Director Setup with vCenter Chargeback
- Unable to Connect to the vCenter Chargeback Database
- Unable to Connect to the vCenter Server Database
- Unable to Email Report
- Unable to Fetch the Primary Group of a LDAP User
- Unable to Use Custom SSL Certificates
- Unable to View the vCenter Chargeback Plug-In in the VI Client
- Index
Non-English Characters Are Not Correctly Stored in the vCenter Chargeback
Database
You can store data with non-English characters in the vCenter Chargeback database.
Problem
The vCenter Chargeback database might be deployed in a non-English locale or synchronized with a vCenter
Server database that contains non-English data. However, the vCenter Chargeback database does not store the
non-English characters correctly. Therefore, this information is not displayed correctly in the application.
Cause
If you using Oracle Database for the vCenter Chargeback database, the character set configured on the database
might not be supporting non-English data.
Solution
Configure the Oracle Database to use the Unicode (AL32UTF8) character set.
Report Does Not Display the Disk Read and Disk Write Information
A vCenter Chargeback report displays the disk read and write information and the corresponding cost if the
disk read and disk write computing resources are selected when the report is generated.
Problem
Although the disk read and disk write computing resources are selected when generating a report, the disk
read and disk write information and the corresponding costs are not displayed in the report.
Cause
A probable reason might be that the statistics collection level is not properly set on the vCenter Server.
Solution
u
On the vCenter Server, check whether the statistics collection level is correctly set.
For vCenter Server 2.5 Update 3, vCenter Server 2.5 Update 4, and vCenter Server shipped with vSphere
4.0, the statistics collection level must be set to 3 or above for the average disk read and write counters to
be available.
Report Does Not Display the Memory Usage Value and the Corresponding Cost
A vCenter Chargeback report displays the memory usage and cost information if the memory computing
resource is selected when the report is generated.
Problem
Although the memory computing resource was selected when generating a report, the memory usage and cost
information is not displayed in the report.
Cause
A probable reason might be that the statistics collection level is not properly set on the vCenter Server.
vCenter Chargeback User’s Guide
136 VMware, Inc.