How do I configure CCI and OPR for NSM 11.2 Event Agents installed on UNIX/Linux systems with the remote MDB installed on a Windows Cluster?

Document ID : KB000050507
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

In NSM 11.2, the Event Manager (OPR) is cluster aware but CCI is not. CCI must be installed and running on all nodes of a Windows cluster. In order to do this, it is necessary to properly configure CCI on the Windows cluster nodes as well as on all UNIX/Linux Event Agent nodes that point to the Event Manager running on the Windows cluster. If CCI is not configured correctly, the Event Agent will not be able to communicate with the Event Manager.

Solution:

In order to correctly configure the RMT CCI service on each node of a Windows Cluster and any UNIX/Linux Event Agents which are using the Remote MDB installed on the Windows Cluster, you must use the physical hostname of the nodes in the Windows Cluster in the CCIRMTD.RC and ccirmtd.prf CCI configuration files. The following example shows the correct way to configure CCI on all of the nodes in a Windows Cluster as well as how to configure CCI and OPR on the Event Agent installed on a UNIX/Linux system.

Windows Cluster Virtual Node Name = lodclust11
Physical Hostname of first node in Windows Cluster = lod11n21
Physical Hostname of second node in Windows Cluster = lod11n22
NSM 11.2 installed in the C:\Program Files\CA directory on both nodes of the Windows Cluster

Hostname of the UNIX/Linux system = lod1015
CAIGLBL0000 on UNIX/Linux system = /opt/CA/SharedComponents/ccs

CCI configuration on first node in Windows Cluster:
Contents of C:\Program Files\CA\CA_APPSW\CCIRMTD.RC must be:

LOCAL = lod11n21 lod11n21 32768 startup

CCI configuration on second node in Windows Cluster:
Contents of C:\Program Files\CA\CA_APPSW\CCIRMTD.RC must be:

LOCAL = lod11n22 lod11n22 32768 startup

CCI configuration on UNIX/Linux Event Agent system:
Contents of $CAIGLBL0000/cci/config/lod1015/ccirmtd.prf must be:

LOCAL = lod1015 lod1015 32768 startup
REMOTE = lod11n21 lod11n21 32768 startup
REMOTE = lod11n22 lod11n22 32768 startup

OPR configuration on UNIX/Linux Event Agent system:
The following environment variables in the $CAIGLBL0000/scripts/envset environment setup file must be set to the following:

CAI_OPR_REMOTEDB=lodclust11
CAI_CAL_REMOTEDB=lodclust11
CA_CAL_SYSTEMID=lodclust11

Before making any changes to these configuration files, first make sure that you shut down the CCI RMT service on all nodes in your Windows Cluster with the following command:

C:> ccicntrl stop rmt

Shut down all of NSM on the UNIX/Linux Event Agent system:

# unishutdown all

Make all of the appropriate CCI and OPR configuration changes on all systems. Once all modifications are made, restart the CCI RMT remote service on all nodes of the Windows Cluster with the following command:

c:> ccicntrl start rmt

After the CCI RMT service is started on the Windows Cluster nodes, you can start all of NSM on your UNIX/Linux Event Agent:

# unistart all

To verify that your CCI connections are active between the active node in the Windows Cluster and the UNIX/Linux Event Agent, execute the following command on the active Cluster node and make sure that you see an ACTIVE state for the UNIX/Linux Event Agent hostname:

C:> rmtcntrl status
SUCCESS: information returned
Sysid           State                 Last Send Time       Last Receive Time
---------------|---------------------|--------------------|--------------------
lod1015       ACTIVE                May-05-2011 15:07:38 May-03-2011 13:52:01
 
From the UNIX/Linux Event Agent, you would execute the following command and make sure you see an ACTIVE state for all nodes in your Windows Cluster:
 
# rmtcntrl status
  Sysid         State           Last Send Time  Last Receive Time
---------------|--------------|---------------|------------------
lod11n21     ACTIVE         050311 13:45:42 050511 15:01:18
lod11n22     ACTIVE

If you are still experiencing CCI communication problems, please open a Support Request on CA Support Online (support.ca.com) to request additional assistance.