SNMP trap troubleshooting in Autosys
search cancel

SNMP trap troubleshooting in Autosys

book

Article ID: 144155

calendar_today

Updated On:

Products

CA Workload Automation AE - Scheduler (AutoSys) Autosys Workload Automation

Issue/Introduction

Autosys can be configured to send SNMP Traps to your SNMP Manager (SNMP Communities)

This document provides some tips on what to look for, in case those traps are not being seen on the SNMP manager

Environment

Workload Automation AutoSys

Cause

Potential causes for this are:

- An incorrect value in the SNMP parameters
- AutoSys services have not been refreshed since implementing the SNMP parameters
- A communication issue between the AutoSysScheduler and the SNMP server host/port.
- The SNMP viewer being used needs to be configured to display the AutoSys SNMP Traps

Resolution

  • Make sure the SnmpManagerHosts and SnmpCommunity parameters are set to the correct values in $AUTOUSER/config.$AUTOSERV.
  • Make sure either Scheduler is restarted one time or have send a kill -HUP <pid> signal to the event_demon process to ensure the Scheduler picks up the SNMP configuration changes.
  • When AutoSys is correctly configured to send SNMP traps, a message similar to the following is seen in the $AUTOUSER/event_demon.$AUTOSERV log file when is restarts or is refreshed with a kill -HUP pid :

[01/16/2020 12:19:26.8783] 6895 4117374720 CAUAJM_I_40356 SNMP trap generation : ENABLED (Trap Hosts: snmp.manager.example.com).

  • This is the only message that gets logged in AE. If the above is seen see, then it is more likely an issue with communication over the network or the configuration of the SNMP manager/viewer which is not displaying the messages or catching them.
    Note: With ISDBGACTIV=LIGHT,COMM tracing enabled, some additional info can be seen, though not very detailed

[01/16/2020 12:21:35.0097] 6895 3877546816 L:1 as_hostname.cpp 133 getaddrinfo [hostname.example.com:162]
[01/16/2020 12:21:35.0101] 6895 3894389568 L:1 as_hostname.cpp 256 getaddrinfo [hostname.example.com:162] gai_ret=0
[01/16/2020 12:25:34.0089] 10158 3899652928 GaiTimeOut[hostname.example.com:162]=[15]

Additional Information

To enable LIGHT and COMM traces:

  • backup $AUTOUSER/config.$AUTOSERV
  • edit the original file $AUTOUSER/config.$AUTOSERV and change the line that looks like below:
    #ISDBGACTIV=OFF

TO


ISDBGACTIV=LIGHT,COMM

  • Save the file
  • Restart the Scheduler
  • $AUTOUSER/out/event_demon.$AUTOSERV file will now contain he traces
Powered by Wolken Software