2.0
Table Of Contents
- vCenter Chargeback Manager User’s Guide
- Contents
- About the User's Guide
- Introduction to vCenter Chargeback Manager
- Configuring Administration Settings
- Authenticating and Managing Users, Roles, and Permissions
- Resource Based Authorization in vCenter Chargeback Manager
- Permissions Defined in vCenter Chargeback Manager
- Managing Roles
- Managing Users
- vCenter Chargeback Manager User Authentication
- Managing Chargeback Hierarchies
- Creating a Chargeback Hierarchy
- Managing a Chargeback Hierarchy
- View a Chargeback Hierarchy
- Add a vCenter Chargeback Manager 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 Manager Cost Elements
- Generating Reports
- Monitoring System Health
- Administration Utilities
- Index
2 In the Log Setting section, select the required log level from the Select Log level list.
Option Description
trace
The trace level is the most informative level providing fine-grained
information about the events.
debug
The debug level provides event information that are most useful to debug
an application.
info
(default): The info level provides coarse-grained informational messages that
highlight the progress of the application.
warn
The warn level provides information about potentially harmful situations.
error
The error level designates error events that might still allow the application
to continue running.
fatal
The fatal level designates very severe error events that will presumably lead
the application to abort.
3 Click Apply.
Remove a vCenter Chargeback Manager
You must ensure that vCenter Chargeback Manager instances that are unavailable or not required are removed
from the cluster.
In a cluster configuration, the load balancer forwards the requests to a vCenter Chargeback Manager instance
that has a lighter load. However, even if a vCenter Chargeback Manager instance is unavailable and not
responding, the load balancer tries to forward the requests to such an instance. You must, therefore, monitor
the health of the vCenter Chargeback Manager instances and remove those instances from the cluster that are
not responding.
When you remove a vCenter Chargeback Manager from the UI, the corresponding entries for the instance is
removed from the System Health. However, the instance is still in the cluster and the load balancer sends
requests to it. You must manually remove the instance from the load balancer by running the
ModifyLBWorkers.bat file. You must have the Super User role to perform this task.
NOTE Removing a vCenter Chargeback Manager instance does not correspond to uninstalling the instance.
Only the details of the instance is removed from a database table and from the application UI. The instance
exists on the system that it is installed. You can log in to this instance and use it, if the instance functions
correctly.
Procedure
1 In the Settings tab, click General.
A list of vCenter Chargeback Manager instances is displayed under the Chargeback Servers section.
2 Select the vCenter Chargeback Manager that you want to remove.
3 Click Remove.
4 Click OK to confirm the remove operation.
The vCenter Chargeback Manager details are removed from the database and the System Health page.
What to do next
You must run the ModifyLBWorkers.bat file to remove the corresponding vCenter Chargeback Manager entry
from the load balancer. Run the following commands from the command-line prompt:
> cd
Installation_Folder
\vCenter-CB-Tools\load-balancer\bin\
> ModifyLBWorkers delete
Server_Instance_Name
vCenter Chargeback Manager User’s Guide
14 VMware, Inc.