Data Controllers cannot be assign to the proper ip domain in CA Performance Management (CAPM)

book

Article ID: 132413

calendar_today

Updated On:

Products

CA Infrastructure Management CA Infrastructure Management CA Performance Management - Usage and Administration

Issue/Introduction

After uninstalling then reinstalling data collectors, sometimes when attempting to assign them to an IP Domain, it fails with the following error:

data collector could not be assigned to the IP domain


The data collector may be successfully sent a re-assignment message but cannot confirm re-assignment. 

Cause

We use the AT command to recycle the DC services to update the configuration.

Environment

CAPM 3.7 on linux

Resolution

First verify that the rpm (Linux Package Management) AT is installed as CAPM uses the AT command to schedule a recycle of the DC services.

rpm -qa ^at


If it is not, then install it:

yum install -y at


Second, see if the DC services are running as root or a non-root user. If you are running as a non-root user, CAPM will be unable to cycle the services using AT.
 
So, as root user, re-cycle the services:

  • service dcmd stop
  • Wait to see the collector go red or "not connected" in the UI
  • service dcmd start
  • go back to the CAPC console and assign a new ip_domain

Additional Information

The AT command is an install pre-req:
https://docops.ca.com/ca-performance-management/3-6/en/installing/prepare-to-install-the-data-collectors#PreparetoInstalltheDataCollectors-VerifythePrerequisites

For the non-root users this has been fixed in CAPM 3.7.7/DX Netops 20.2.1 Performance Management :

Symptom: When the Data Collector runs as a non-root user, the user would be unable to re-assign the DC to a different tenant and/or IP domain due to permissions to restart the DC from inside the DC.
Resolution: Updated the restart logic to call sudo to restart the DC if it's running as non-root user.  Be sure to check the documentation for an additional sudo command to allow the DC to run as the install user.
(3.7.7, DE418500, 01363625)

Symptom: When the Data Collector runs as a non-root user, the user would be unable to re-assign the DC to a different tenant and/or IP domain due to permissions to restart the DC from inside the DC.
Resolution: Updated the restart logic to call sudo to restart the DC if it's running as non-root user.  Be sure to check the documentation for an additional sudo command to allow the DC to run as the install user.
(20.2.1, DE418500, 01363625)