Missing Information in jaws․log for SNMPv3 Informs in Automation Analytics

Products

• Automation Analytics & Intelligence

Issue/Introduction

After configuring AAI to use SNMP v3 INFORM messages, the traps are going through to Service Now, but no INFORM messages are seen in the AAI logs.

 

 

Environment

Automation Analytics & Intelligence Integration for non-Broadcom Automation - Distributed (IWS-Dist, ControlM-Dist, Tidal) Product Release 24․4

Cause

Using the wrong value for Remote Engine ID in the SNMP configuration in the AAI configuration tool

Resolution

1․ RETRIEVE ENGINE ID VIA SERVICE NOW UI

Path: Event Management > Integrations > MID SNMP Trap Listener

Open the record for your specific trap listener․ Ensure the SNMP version is set to v3․ Locate the EngineID field containing a hexadecimal string (e․g․, 80001f8880e6)․ Copy this value and paste it into the Remote EngineID or EngineID field on your network device's SNMP configuration․

EXPECTED: The EngineID field displays the correct value․ NOTE: Ensure you have the agent_admin role and the form layout displays the field․

 

2․ RETRIEVE ENGINE ID VIA MID SERVER LOGS

Path: /agent/logs/

Log into the host machine where the MID Server is installed․ Open the agent․log file․ Search for the term SNMPTrapListener or EngineID․ Locate the line stating "Successfully started SNMP Trap Listener on port 162 with EngineID: [value]"․

EXPECTED: The log file reveals the EngineID․

 

3․ RETRIEVE ENGINE ID VIA NETWORK PROBING

Command: snmpget -v3 -u <MID_Server_IP>: ․1․3․6․1․2․1․1․1․0

Run the command from a machine that can reach the MID Server to exchange EngineIDs before authentication occurs․

EXPECTED: The MID Server returns the EngineID․ NOTE: If the command fails with an authentication error, capture the response packet with Wireshark and locate the msgAuthoritativeEngineID field within the SNMPv3 header․