1.6
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
4 If you are using Oracle Database for vCenter Chargeback database, then you must set the maximum limit
of server appropriately.
vCenter Chargeback and each data collector registered with it connect to the vCenter Chargeback
database. In the case of a cluster installation the number of connections to the database is higher. To ensure
the smooth functioning of vCenter Chargeback, the Oracle Database must be configured to allow a larger
number of server process to run.
a In the Oracle Database, run the following command from the SQL prompt.
ALTER SYSTEM SET PROCESSES=
NNN
SCOPE=SPFILE;
Here,
NNN
is the maximum limit for server processes. The default value is 150.
b Restart the Oracle Database service and the corresponding Oracle TNS Listener service.
c Restart the vCenter Chargeback and data collector services.
Unable to Connect to the vCenter Server Database
vCenter Chargeback data collector must connect to the vCenter Server database to synchronize the vCenter
Chargeback database.
Problem
n
The vCenter Chargeback data collector is unable to connect to the vCenter Server database.
n
vCenter Chargeback is unable to connect to the vCenter Server database when adding the vCenter Server.
Cause
This issue can occur due to multiple reasons.
n
The database service is not started and running.
n
The database is not reachable over the network.
n
The port number for the SQL Server named database instance has changed.
n
TCP/IP protocol is not enabled for the vCenter Server database.
Solution
1 Check whether the database service is started and running.
2 Check whether the database machine is reachable over the network.
3 If you are using SQL Server for the vCenter Server database and using the port number of the named
database instance to connect to it, ensure that the port is a dedicated or static port for the database instance.
In SQL Server, the default configuration is to use dynamic ports for named database instances. You must
modify it to use dedicated ports. You must also configure the database named instance with the formerly
configured port number. If you configure the database named instance with a different static port, ensure
that you make the necessary changes in vCenter Chargeback so that the connection to the vCenter Server
database is restored.
4 If you are using SQL Server or SQL Express for the vCenter Server database, ensure that the TCP/IP
protocol is enabled for the vCenter Server database.
The TCP/IP protocol is enabled by default. You can use the SQL Server Configuration Manager to check
whether the TCP/IP protocol is enabled for the database.
Use the SQL Server Surface Area Configuration tool to ensure that the SQL Server Browser Service and
Database Engine Service & Remote Connections services are running.
vCenter Chargeback User’s Guide
148 VMware, Inc.