VCP-IaaS Study Notes: Section 3.4

This is Section 3.4 in the VCP-IaaS blueprint Guide 1.2. The rest of the (completed) sections can be found here.

Collect logs

  • You must run the troubleshooting utility to collect the required logs for troubleshooting the application.
    • Run the trouble shooting utility by running the following command from the command prompt.
      • cd Installation_Directory\vCenter-CB-Tools\troubleshooting\bin\vCenterCB-support.bat
      • You can also run this utility by selecting Collect vCenter Chargeback Manager Logs from the Start > Programs > VMware > VMware vCenter Chargeback > vCenter Chargeback Manager Tools menu.
    • Provide the folder name and directory path where the generated logs have to be stored when prompted.
      • You can choose to collect the system event logs.
    • The Application log and System log is collected.
    • Enter the number of stand-alone data collector instances (not embedded) installed on the same machine.
    • If you have any standalone data collector instance running, you must provide the path of each such data collector installation.

Run troubleshooting utility

  • See first bullet.

Explain impact of vSphere statistics levels on report generation

  • A vCenter Chargeback Manager 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.
    • A vCenter Chargeback Manager report displays the memory usage and cost information if the memory computing resource is selected when the report is generated
    • A vCenter Chargeback Manager report displays the network bandwidth usage and cost information if the network transmitted and network received computing resources are selected when the report is generated.
    • For all these report statitics you will need to:
    • For vCenter Server 2.5 Update 3, vCenter Server 2.5 Update 4, and vCenter Server shipped with vSphere 4.0 and later, the statistics collection level must be set to 3 or above for the average disk read and write counters to be available.

Explain impact of local firewall settings on vCenter Chargeback services

  • Although you have provided the correct URL, you are unable to access the application.
    • The issue might occur due to multiple reasons.
      • The application-related services are not started or not running.
      • Windows Firewall is enabled on the machine on which vCenter Chargeback Manager and the load balancer is installed and running.
        • 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 Manager during the installation. Ensure that you set an inbound rule for these port. That is, allow access to the machine through these ports.

Given a service failure, determine root cause

  • Best way to find out what is not working is using the Health Dashboard.
  • I recommend reading over Troubleshooting Issues chapter in Best Practices and Troubleshooting Guide, just to get an overview of what could potentially be wrong.

About larushjartar
VMware Specialist and IBM Technician.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: