New Data Collector does not appear in the Performance Management list

Products

CA Performance Management Network Observability

Issue/Introduction

New Data Collector (DC) is added, however, it does not appear in the list on the Performance Management Portal. The Data Aggregator (DA) is connected and online, but the DC still does not appear.

The following is shown in the DC shutdown log:

[root@host ~/apache-karaf-4.3.8]# cat shutdown.log
2020-06-15 08:42:12,031 | WARN | roxyReg-thread-1 | shutdown | om.ca.im.osgishell.BundleManager 142 | 190 - com.ca.im.data-collection-manager.osgishell - 23.3.13-RELEASE-355 | | Unable to connect to the Data Aggregator at host <IP>. Shutting down the Data Collector. This may take up to 10 minutes.
2020-06-19 10:17:40,529 | WARN | roxyReg-thread-1 | shutdown | om.ca.im.osgishell.BundleManager 142 | 190 - com.ca.im.data-collection-manager.osgishell - 23.3.13-RELEASE-355 | | Unable to connect to the Data Aggregator at host <IP>. Shutting down the Data Collector. This may take up to 10 minutes.

Environment

DX NetOps Performance Management all currently supported releases

Resolution

1 - The Data Collector version MUST match the new Data Aggregator it will connect to.

2 - When a Data Collector starts it will connect to the Data Aggregator configured in it's com.ca.im.dm.core.collector.cfg file

Steps:
Stop the Data Collector to me moved.
Open the (default path) /opt/IMDataCollector/apache-karaf-4.3.8/etc/com.ca.im.dm.core.collector.cfg file for editing.
Ensure the collector-manager-tenant-id is set to the correct Tenant Name the DC will be assigned to.
Ensure the collector-manager-ip-domain-id is set to the correct IP Domain the DC will be assigned to.
Ensure the collector-manager-da-hostname is set to the Data Aggregator host name the DC will communicate with.

Before restarting the Data Collector ensure:
The Tenant Name set in collector-manager-tenant-id is already created in the Performance Management
The IP Domain Name set in collector-manager-ip-domain-id is already created in Performance Management
The Data Aggregator host name set in collector-manager-da-hostname is correct and routable between the DC and DA.

Start the Data Collector

When the Data Collector starts post IP change on the server it will send new information to the Data Aggregator to record in http://<DA_HOST>:8581/rest/dcms
You can edit this dcms via REST if necessary

Additional Information

TechDocs : DX NetOps CAPM 23.3 : Prepare to Install the Data Collectors - Verify the Prerequisites

Verify the Prerequisites
Meet the following prerequisites before you install Data Collector:
On the Data Aggregator system, verify that ports 61616, 61618, 61620, and 61622 are open. These ports enable communication between the Data Collector and the Data Aggregator.
Verify that ports 1099 and 11099 are blocked from external access.
These ports must remain open locally for internal communication.
Verify that Security Enhanced Linux (SELinux) is disabled on the computer where you are going to install Data Collector. By default, some Linux distributions enable this feature, which does not allow Data Collector to function properly. Disable SELinux or create a policy to exclude Data Collector processes from SELinux restrictions.
For information about configuring an SELinux security policy, see the Red Hat documentation.

+

Set a Unique Hostname for the Data Collector Host
Set a unique hostname for the computer where you plan to install Data Collector.
Follow these steps:
As the root user, log in to the Data Collector host
Verify the unique hostname on the computer.
The hostname for the computer must be associated with the IP address and not the loopback address of 127.0.0.1.
Verify that the following lines appear in the /etc/hosts file on the computer:
Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
IP address of your host YourHostName YourHostName.ca.com

If the hostname required any changes, restart the network:
service network restart

The /etc/hosts file is configured correctly.
The unique hostname is set.
These ports must remain open locally for communication between the Data Aggregator and Data Collectors.