Page tree

Skip to end of metadata
Go to start of metadata

This section explains how you can pinpoint and troubleshoot issues with BMC Capacity Optimization. Refer to the following sections in this topic for more information:

Troubleshooting the installation, migration or upgrade

The following sections provide information about troubleshooting issues that occur during an installation, migration, orupgrade.

Troubleshooting post-installation tasks

SymptomResolution
During post-installation, the database machine halts or restarts, and the post-installation task halts at Data ware house Preparing space.To fix this and to ensure that the post-installation task completes correctly, you must force restart the post-installation task using the following command:

<BCOurl>/ home.do?resetStatus=POST_INSTALL&forceStop=true

Troubleshooting communication port conflicts and other issues

The following table lists the default ports and protocols BMC Capacity Optimization components use, which can help you resolve communication port conflicts and other issues. 

BMC Capacity Optimization ports and protocols

Type of communication

Default Port

From

To

Protocol

Command line administration

22

CLI

BMC Capacity Optimization application server

SSH

Command line administration

22

CLI

(Remote) ETL Engine server

SSH

Web access, when an Apache web server is installed on the BMC Capacity Optimization application server Note

443
(configurable)

Browser

BMC Capacity Optimization application server

HTTPS

Web access, when an Apache web server is installed on the BMC Capacity Optimization application server Note

8000
(configurable)

Browser

BMC Capacity Optimization application server 

HTTP

Web access, when a web server that is not Apache is installed on the BMC Capacity Optimization application server Note

8080 / 8081
(configurable)

Browser

BMC Capacity Optimization application server

HTTP / HTTPS

Web access

8080
(configurable)

Integration Studio

BMC Capacity Optimization application server

HTTP

Access to BMC Capacity Optimization Analyzer from an external (user-written or third-party) application server

6311
(configurable)

External application server

BMC Capacity Optimization application server
(Analyzer)

TCP

Access to Data Hub from an external (user-written or third-party) application server

1299
(configurable)

External application server

BMC Capacity Optimization application server
(Data Hub)

TCP

Access to Data Hub from ETL (Remote) Engine server if JMS over TCP is configured (default)

61616
(configurable)

(Remote) ETL Engine server

BMC Capacity Optimization application server
(Data Hub)

TCP

Access to Data Hub from ETL (Remote) Engine server if JMS over HTTP is configured

61617
(configurable)

(Remote) ETL Engine server

BMC Capacity Optimization application server
(Data Hub)

HTTP

Access to DataHub Web services

8280
(configurable)

(Remote) ETL Engine servers

BMC Capacity Optimization application server
(Data Hub)

HTTP

DB access from BMC Capacity Optimization application server

8280
(configurable)

BMC Capacity Optimization application server (Console JSP engine, Data Hub, and scheduler)

Database server

SQL*Net

DB access from (Local) ETL Engine servers

8280
(configurable)

(Local) ETL Engine servers (scheduler)

Database server

SQL*Net

Notification email

25 / 465
(configurable)

ETL Engine server
(Scheduler)

SMTP gateway

SMTP / SSL

Notification email

25 / 465
(configurable)

BMC Capacity Optimization application server
(Scheduler)

SMTP gateway

SMTP

Notification traps

162
(configurable)

ETL Engine server
(Scheduler)

Trap receiver

SNMP

Notification traps

162
(configurable)

BMC Capacity Optimization application server
(Scheduler)

Trap receiver

SNMP

User authentication via external LDAP service (optional)

389
(configurable)

BMC Capacity Optimization application server

LDAP service

LDAP / SSL

JDBC

1521
(configurable)

BMC Capacity Optimization application server

Database server

JDBC

Access to data sources

Specific to each connector

(Remote) ETL Engine servers (connectors, Data Accum)

Data source

Specific for each connector


If the Web server is not configured to listen at the default port 8000, you will need to modify the BMC Capacity Optimization URL.
To configure BMC Capacity Optimization to the correct port, update the Capacity Optimization Console URL field under Administration > SYSTEM > Configuration > General. This ensures that the BPPM integration launch-in-context from events works correctly.
If you do not update the url field, the url that gets embedded in the event, points to the wrong port, causing the cross launch to fail.

Troubleshooting BMC Capacity Optimization features integrated with BMC Cloud Lifecycle Management

This following sections explain how you can troubleshoot the integration of BMC Capacity Optimization features with BMC Cloud Lifecycle Management.

Troubleshooting the Capacity-Aware Placement Advice service

The Capacity-Aware Placement Advice service allows you to make choices for the placement and provisioning of virtual machines based on the available capacity. This service runs inside BMC Capacity Optimization Data Hub; for more information, see BMC Capacity Optimization Data Hub administration.

To verify that it is working properly and is ready to be used in connection to BMC Cloud Lifecycle Management for placement advice, access the BMC Capacity Optimization Console and navigate to Administration > Data Hub > Status; then, follow these steps:

  1. Check the status of the API Providers - Capacity Aware Placement Advice service by looking at the color of the corresponding row:
    • Green: The service is active.
    • Red: The service is inactive due to deployment errors.
    • White: The service has not been deployed.
  2. Click on the  icon at the end of the row to inspect the application log for the most recent executions of the service. Error messages are identified by a unique error code; for more information, see Troubleshooting BMC Capacity Optimization - error codes.

    In addition to viewing service logs for API Providers - Capacity Aware Placement Advice service, you can also view Capacity Aware-Placement Advice placement call details.
  3. Click on API Providers - Capacity-Aware Placement Advice service in the Active services table to access the detail page for the service, where you can view statistics for the last three 5-minute execution intervals. 

    Capacity-Aware Placement Advice Statistics page

Using csm.log files present on the CSM PlatformManager server to debug CAPA

The csm.log files present on the CSM PlatformManager server (PlatformManager/log) also aid in debugging Capacity-Aware Placement Advice, and various integration and functionality issues. The data in the log file includes:

  • Placement advice calls generated by BMC Cloud Lifecycle management
  • Requests sent by BCMProvider and responses from Capacity-Aware Placement Advice API

Troubleshooting Cloud Capacity Visibility

If your installation of the Cloud Capacity Visibility view is showing incomplete data, or none at all, you should examine the logs of the following BMC Capacity Optimization components:

  • BMC Capacity Optimization view log: To view it, follow these steps:
    1. Log in to the BMC Capacity Optimization Application Server.
    2. Access the folder $BCO_HOME/web/log; for example, /opt/cpit/web/log.
    3. Open the file dash.log
  • Cloud Capacity ER Materializer task log: To view it, follow these steps:
    1. Access the BMC Capacity Optimization Console and navigate to Administration > Scheduler > System tasks.
    2. Locate the Cloud Capacity ER Materializer task. 

      Locating the Cloud Capacity ER Materializer task
    3. Click on the  icon at the end of the corresponding row to inspect the task log. 

      Viewing the Cloud Capacity ER Materializer task log