ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

DX APM - SysEdge Agent not reporting any metrics when installing Multiple Instances of the Infrastructure Agent

book

Article ID: 240097

calendar_today

Updated On:

Products

DX Application Performance Management

Issue/Introduction

Symptoms:
1/ The Hostmonitoring is being installed by default when installing the DX APMIA Agent even if it is disabled in the extensions.profile file. Even if there is no host monitoring extension configured it installs the Hostmonitoring Agent anyway.

 

https://api-broadcom-ca-user.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=c+pZgXbE9oTI+dH8dgLaVA==

https://api-broadcom-ca-user.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=Fm1ILqtgOMqb2qWBqV/ECg== 

Also, it seems to detect that a Hostmonitoring agent on port 1691 is already installed and selects 1791 by default. When the uninstall is run afterward, it removes the Sysedge Service installed previously from 10.7.

 

2/ Once the 2nd agent is installed successfully without the host monitoring extension, the Agent appears in the DX APM Metrics view displaying also the Sysedge extension in its tree but no metric data are being reported: 

 

Cause

Lack of proper configuration of the 2nd APMIA instance as far as the previous versions of SysEdge agents were not compatible with SNMP v3.

Environment

Windows Server 2012/2019 with the all the following agents installed on the same box:
1. ServiceDesk Server 17.3
2. Sysedge Agent 5.9.0
3. APM Infrastructure Agent 10.7SP3 - 1st instance sending monitoring data from the Service Desk Server to APM Manager 10.7.x
4. DX APM Infrastructure Agent 22.1.0.25 downloaded from SaaS - 2nd instance sending monitoring data from the Service Desk Server to DX APM 21.x
This 2nd instance of DX APMIA is intended to detect automatically the SysEdge instance previously installed and to correctly report the SysEdge metrics to DX APM 21.x

Resolution

1/ Disable sysedge installation on the second APMIA agent by setting the following property to false in '<Agent installation location>\apmia\core\config\IntroscopeAgent.profile' file and reinstall the 2nd agent. It will report to the sysedge service of the first agent.

Property before: introscope.agent.hostmonitor.sysedge.enabled=true
Property after: introscope.agent.hostmonitor.sysedge.enabled=false

In order to achieve backward compatibility of the SysEdge extension from the latest SaaS APMIA agent with the SysEdge agent installed with the APMIA 10.7:

2/ Change the SNMP version from v3 to v2 in your <your_agent_directory>\apmia\extensions\hostmonitor-<apmia_version_id>\bundle.properties file.

# SNMP v3 configuration default: V2 , Supported value : V2, V3 
#
# Changing this property requires restarting the Monitored Process
introscope.agent.hostmonitor.profiles.localhost.version=V3

change V3 to V2:

introscope.agent.hostmonitor.profiles.localhost.version=V2

3/ In the same file comment on all the 6 new following authentication and cryptographic properties that have been added in SNMP v3 and are not compatible with SNMP v2. After this action all the lines listed below should be commented on:

# default: "AUTH_PRIV" , Supported value : AUTH_PRIV, AUTH_NOPRIV, NOAUTH_NOPRIV
#
# Changing this property requires restarting the Monitored Process
#introscope.agent.hostmonitor.profiles.localhost.securityLevel=AUTH_PRIV

# default: "apmhmuser" , Supported value :
#
# Changing this property requires restarting the Monitored Process
#introscope.agent.hostmonitor.profiles.localhost.securityName=apmhmuser

# default: "SHA" , Supported value : MD5, SHA
#
# Changing this property requires restarting the Monitored Process
#introscope.agent.hostmonitor.profiles.localhost.authProtocol=SHA

# default: "ENC(wJdwOX6LsY9SzszDqg==" , Supported value :
#
# Changing this property requires restarting the Monitored Process
#introscope.agent.hostmonitor.profiles.localhost.authPassword=ENC(wJdwOX6LsY9SzszDqg==

# default: "AES" , Supported value : DES, AES, 3DES
#
# Changing this property requires restarting the Monitored Process
#introscope.agent.hostmonitor.profiles.localhost.privProtocol=AES

# default: "ENC(2JdwOX6LsY9SyMbJqg==" , Supported value :
#
# Changing this property requires restarting the Monitored Process
#introscope.agent.host monitor.profiles.localhost.privPassword=ENC(2JdwOX6LsY9SyMbJqg==

4/ Still in the same file set the host monitor community flag to the public by adding the following line just below the last property from the above list. 

introscope.agent.host monitor.profiles.localhost.community=public

5/ Save the bundle.properties file and restart the SysEdge windows service. After this restart, the sysedge metrics should be now reported correctly by the 2nd agent as well.

Additional Information

1/ To install the second instance of APMIA on the same server you will follow the steps from DX APM - SaaS:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-apm-saas/SaaS/implementing-agents/infrastructure-agent/Install-the-Infrastructure-Agent-on-Windows.html

2/ Important Note: If you would like a SaaS agent to report to a 10.7 EM you have to add the following hidden property to the IntroscopeAgent.properties:

Interscope.agent.connection.compatibility.version=10.7

3/ Also, instead of using one 10.7 Agent and one DX SaaS Agent, we would strictly recommend using 2 instances of the same latest available version of DX SaaS Agent.

  • 1st one with introscope.agent.hostmonitor.sysedge.enabled=true
  • 2nd one with introscope.agent.hostmonitor.sysedge.enabled=false

Important Note: In such a scenario, steps 2/ to 5/ from the resolution section above will not be needed as both instances will be compatible with SNMP v3.

Attachments