EM connection List provided on Agent connection.

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


 In an APM Clustered and Loadbalancing environment, the Agent first connects to the MOM. MOM then sends the list of available Collectors to the Agent.  The Agent then disconnects from the MOM and connects to an available Collector. This same process is used for each Agent that connects to the MOM.


 Why does the "Enterprise Manger List" contain other IP addresses than what is set in the MOM properties file?


 APM 10.x


 The "New List" is enumerated from all the NICs of that EM.
 To verify, please run the below command on the system where the EM runs.

 /usr/sbin/ifconfig -a

 ipconfig / all

Additional Information:

 Here is an example when a WebSphere Agent(WASLOD) is assigned to connect to an EM  (CAtestEM.CAtest.com):

 An improper EM list is given to the Agent. Even though the loadbalancing.xml is configured with the Agents are assigned to appropriate collectors.
IntroscopeEnterpriseManager.properties files are configured with the correct Collectors assigned for the APM cluster.

[INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected controllable Agent to the Introscope Enterprise Manager at CATestCollector:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "WASLODtestNA", Process = "WebSphere", Agent Name = "WASLOD", Active = "false".
[INFO] [IntroscopeAgent.ConnectionThread] New list {test1.CAtest.com@5001, test2.CAtest.com@5001,,,}@1434950431283 downloaded from CAtestEM.CAtest.com:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory  
[INFO] [IntroscopeAgent.Agent] New list accepted

According to the CA APM configuration, the list should contain :

But it additionally lists the following IP Addresses: