How to change SNMP Trap destination port

Document ID : KB000111001
Last Modified Date : 14/08/2018
Show Technical Document Details
Introduction:
CA Workload Automation AE uses Simple Network Management Protocol (SNMP) to send alarms and signals to SNMP managers. The SNMP trap mechanism is used to post alarms and signals. The SNMP manager typically receives SNMP notifications (TRAPs and INFORMs) on UDP port number 162. However, the receiving port could be different depending on the SNMP Manager software.
Question:

How can CA Workload Automation AE be configured to send SNMP traps to a different SNMP trap port than the default (162/UDP)?
Our SNMP Manager solution listens on a non-default port.
Environment:

CA Workload Automation AE 11.3.6 SPx on supported UNIX and LINUX operating environments.
Answer:

CA Workload Automation AE uses the SNMP target port defined in the services file for "snmptrap" (or "snmp-trap") service. Hence, a workaround is to update the /etc/services file and change the port numbers, corresponding to the "snmptrap" (or "snmp-trap") service, to the desired target SNMP Trap port.

For example, the following excerpt shows the snmptrap service port changed to 1612 from the default 162/tcp and 162/tcp.

# grep ^snmptrap /etc/services
snmptrap           1612/tcp      # SNMPTRAP  [Marshall_Rose]
snmptrap           1612/udp      # SNMPTRAP  [Marshall_Rose]

After updating the /etc/services file, restart CA Workload Automation AE Scheduler service for the change to take effect.

NOTE: 
1) Since /etc/services is a system-wide configuration file for services, any changes could impact other application relying on it.
2) Take a backup copy of /etc/services file before making any changes.
Additional Information:

CA Workload Automation AE DocOps: SnmpManagerHosts and SnmpCommunity