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
Cause
The issue might occur due to multiple reasons.
n
The application-related services are not started or not running.
n
Windows Firewall is enabled on the machine on which vCenter Chargeback and the load balancer is
installed and running.
Solution
1 Check whether all the relevant services are running.
The following services must be started and running:
n
VMware vCenter Chargeback Service
n
VMware vCenter Chargeback Load Balancer Service
n
VMware vCenter Chargeback DataCollector
2 If Windows Firewall is enabled, ensure that port exceptions are added for the HTTP, load balancer, and
HTTPS ports that are configured for vCenter Chargeback during the installation.
Ensure that you set an inbound rule for these port. That is, allow access to the machine through these
ports.
Unable to Add an LDAP Server
vCenter Chargeback lets you configure one or more LDAP servers in vCenter Chargeback.
Problem
When configuring the LDAP server in vCenter Chargeback, an error is thrown and the operation fails. The
error is similar to the following message:
An error occurred. Entity not found in LDAP server.
Cause
A probable cause is that you are adding a sever that is a child domain of a primary LDAP server and not
provided the base DN.
Solution
If you are add an LDAP server that is a child domain of a primary LDAP server, then you must specify the
base DN. vCenter Chargeback cannot automatically fetch the correct base DN in this case.
Unable to Add vCenter Server in vCenter Chargeback
You must add a vCenter Server in vCenter Chargeback before you can add entities from the vCenter Server to
a hierarchy in vCenter Chargeback.
Problem
When adding a vCenter Server to vCenter Chargeback, the add operation fails.
Cause
The issue might occur due to multiple reasons.
n
The vCenter Server is not running.
n
The vCenter Server is not reachable on the network.
n
The proxy settings on the Web browser are inappropriate.
Chapter 10 Troubleshooting vCenter Chargeback
VMware, Inc. 139