Troubleshooting

View troubleshooting tips and error messages.
capm360
HID_Troubleshooting
Use the troubleshooting section to diagnose and resolve issues with
CA Performance Management
. Each troubleshooting page in this section contains one or more symptoms, and at least one solution to resolve the issue.
Insufficient Permissions During Installation
Symptom:
After you specify an installation path the following error appears:
Error: Insufficient permissions for installation path:
Folder_Path
Path must have executable permission for 'other'.Exiting the installer...
Solution:
Run the following command to ensure all child and parent directories have the necessary executable permission:
chmod 755 "
Folder_Path
"
Installation Stopped Abruptly
In CA Virtual Network Assurance 3.6.6, when the installation stops abruptly for any reason, and you start the installation again, the installer does not prompt you to install the product on a custom directory. Perform the following steps to resolve the issue and install the product on a custom directory.
Follow these steps:
  1. On the server where the installation stopped, navigate to the
    /etc
    directory.
  2. Delete the VNA.cfg file using the
    rm -rf VNA.cfg
    command.
  3. Follow the steps in the Installing section and complete the installation.
Enable
Performance Center
Logging
If you encounter an issue with a specific view in the
Performance Center
user interface, you can easily enable logging on that view. You can use this method to provide the necessary details to CA Support.
Follow these steps:
  1. Log in as a user who has the Generate URLs from Views role right.
  2. Open the dashboard that contains the problematic view.
  3. Click the
    Edit
    (gear) icon on the view, and select
    Generate URL
    .
    The Generate URL dialog opens.
  4. Enable
    Detailed View Logging
    .
  5. Click
    Preview.
  6. Take a screenshot of the preview for CA Support.
  7. Run CARE on the
    Performance Center
    host and the Data Aggregator host.
  8. Provide the archive files from CARE and the screenshot to CA Support.
Enable Data Collector Logging
If you encounter missing data, detailed poll logging is available from the Data Collector debug tool. When enabled for an IP address, the tool generates logs on the Data Collector. Before you download the logs, you should wait at least two poll cycles (ten minutes) after enabling logging to collect sufficient data.
The logs record the following details of every poll for the specified IP address:
  • The requests that are sent to the device
  • The responses that are received from the device
  • The delta processing the Data Collector performs on the responses
  • The expression evaluation the Data Collector performs on the responses
You cannot enable detailed poll logging for more than one IP address at a time. If a second IP address is enabled, detailed poll logging for the previous IP address is disabled. The logs for the previous IP address are discarded.
Detailed poll logging stores a maximum of 60 MB of logged messages by default. If the limit is reached, the oldest entries are discarded to make room for the newer messages. You can configure this limit with the cache setting.
Logging can be filtered by Poll Group ID, or by Component Item ID. Filtering restricts the logging to a specific Vendor Certification or a specific component.
Detailed poll logging is stored in the runtime memory of the Data Collector. If the Data Collector is shut down, the log is lost. If the Data Collector restarts, the log resets.
Follow these steps:
  1. Go to the following location:
    DA_host
    :
    port
    /dcdebug/enabledebug.html
  2. Specify the IP address of the polled device.
  3. Select an IP domain.
  4. (Optional) Specify Filtering and Cache settings.
  5. Select
    Enable Debug Logging
    .
  6. Click
    Enable Debug Logging
    .
Download Data Collector Logs
If you encounter missing data, you can use the Data Collector debug tool to download the relevant logs. Before you download the logs, you should wait at least two poll cycles (ten minutes) after enabling logging to collect sufficient data. You can use this method to provide the necessary details to CA Support. After you download the logs, you should disable detailed poll logging.
Follow these steps:
  1. Go to the following location:
    DA_host
    :
    port
    /dcdebug/searchdebug.html
  2. Specify the IP address of the polled device.
  3. Select an IP domain.
  4. Select
    Download all logs for IP
    .
  5. Click
    Download As Zip
    .
Disable Data Collector Logging
After you download the Data Collector logs, you should disable detailed poll logging.
Follow these steps:
  1. Go to the following location:
    DA_host
    :
    port
    /dcdebug/enabledebug.html
  2. Specify the IP address of the polled device.
  3. Select an IP domain.
  4. Select
    Disable Debug Logging
    .
  5. Click
    Disable Debug Logging
    .
SNMP Querying Tools
SNMP querying tools are included with
CA Performance Management
. The
sapwalk2
utility and the
sappoll
utility are available in the
DC_Install_Directory
/scripts/
directory. The
sapwalk2
command line tool gathers an SNMP snapshot of network devices. Internal CA engineers can use this snapshot to reproduce issues and verify SNMP values on devices. The
sappoll
utility retrieves SNMP data for a timeframe.
CA Support finds the following
sapwalk2
command helpful:
sapwalk2 -i
ip_address
-v
snmp_version
-s
starting_oid
-c
community_name
-xv
bridge_table_oid
-o
output_file
.walk
Example:
sapwalk2 -i 10.253.190.15 -v v2c -s 1.3.6.1 -c public -xv 1.3.6.1.2.1.17 -o 10.253.190.15.walk
CA Support finds the following
sappoll
command helpful:
sappoll - i
ip_address
-v
snmp_version
-c
community_name
-p
snmp_port
-r
retries
-d
timeout
-f
file_containing_oids
-n
number_of_polls
-t
poll_interval
Example:
sappoll -i 138.42.110.45 -v v2c -c xxxxx -p 161 -r 3 -d 3000 -f /tmp/OidList -n 5 -t 2
The file containing OIDs (for example,
/tmp/OidList
), should include the OIDs to poll in the following format:
I
instance_oid
N
node_oid
Example:
I 1.3.6.1.2.1.1.1
Enable the ActiveMQ Admin Console for the Data Aggregator or Data Collector
Generally, the ActiveMQ admin console should not be available on the network. However, if you absolutely need the console to address a problem, you can enable it for the Data Aggregator or Data Collector.
Follow these steps:
  1. Go to one of the following files:
    • Data Aggregator
      DA_Install_Directory
      /broker/apache-activemq-
      version
      /conf/activemq.xml
    • Data Collector
      DC_Install_Directory
      /broker/apache-activemq-
      version
      /conf/activemq.xml
  2. Uncomment
    <import resource="jetty.xml"/>
    .
  3. (Optional) To update user access, edit the
    jetty-realm.properties
    .
  4. (Optional) To encrypt the user passwords, run one of the following commands:
    • Data Aggregator
      DA_Install_Directory
      /broker/apache-activemq-
      version
      /lib/web run java -cp jetty-all-9.2.22.v20170606.jar org.eclipse.jetty.util.security.Password
      password
      password
    • Data Collector
      DC_Install_Directory
      /broker/apache-activemq-
      version
      /lib/web run java -cp jetty-all-9.2.22.v20170606.jar org.eclipse.jetty.util.security.Password
      password
      password
  5. Shut down the ActiveMQ broker on each Data Collector:
    service activemq stop
  6. Shut down the ActiveMQ broker on the Data Aggregator:
    service activemq stop
  7. Start the ActiveMQ broker on the Data Aggregator:
    service activemq start
    If you do not, the Data Aggregator starts the broker automatically.
  8. The Data Collectors automatically restart the ActiveMQ brokers. Use the following command to restart the brokers manually:
    service activemq start