Missing traps from CA Performance Management (CAPM) Notifications on the destination system
search cancel

Missing traps from CA Performance Management (CAPM) Notifications on the destination system


Article ID: 32144


Updated On:


CA Infrastructure Management CA Performance Management - Usage and Administration



After configuring CAPC Notifications to send traps to a target destination, no traps are seen arriving on the target destination.


The CAPC and IM DA User Guides instructions for configuring traps to be sent to a target destination, through Notification configuration in CAPC, are not complete.

When configuring the trap sends in CAPC Notifications, CAPC uses it's EM (Event Manager (caperfcenter_eventmanager) service to send the traps to the destination specified in the Notification rules.

The EM service uses SNMP Profiles configured in CAPC (normally used for Discovery Profile execution) to know what SNMP Port and, if necessary, what community string, to use when sending the trap to the target destination.

Normally, by default, most trap destinations use SNMP port 162 to listen for, receive and process traps sent to it.

What is missing from CAPC and the user guides is an SNMP Profile that specifies port 162 and the correct community string to use when sending the trap to the target destination.

So when the trap is sent to the destination, CAPC defaults to using the default SNMP Profile, often set with an SNMP communication port of 161. This results in the trap being sent to a port on the destination that isn't actually listening for traps to arrive. This results in the traps being dropped on the destination target.

In order to resolve this in CAPC complete the following steps.

Part 1: Create a new SNMP Profile

  1. Log in to the CAPC web UI as the admin user. 

  2. Under the Admin menu option, select the 'SNMP Profiles' option under the System Settings area 

  3. Select the 'New' button to create a new SNMP Profile.

  4. Enter the following values:

Profile Name: <profileName> (best to use a name, such as 'HostName_trapProfile' to remove confusion about what that profile is for)

SNMP Version: SNMPv1/SNMPv2c

Port: Set this to port 162 if the destination is using the default SNMP trap listening port, or the correct port if the destination uses a custom port to listen for traps.

Community Name: Set this to public as it is rarely set to something unique for trap reception duties

Use by default for new devices: Set this to disabled so it won't be used mistakenly by devices as a default profile.

Part 2: Edit the Notification Rule set to send traps

  1. Under the Admin menu option, select the 'Notifications' option under the System Settings area 

  2. Select the Notification that is at issue that is sending the traps involved 

  3. Select the Edit button to expose its configured settings

  4. Navigate to the 'Actions' area.

  5. Select the SNMP Profile created in Part 1 above and save the changes.

After doing so, the Notification rule should use the newly created SNMP Profile to send the traps using the correct port to the target destination.

If this still does not work, and traps are not received on the target destination, please open an issue with CA Support for further assistance.

A future CA IM release will contain updated user documentation to address this shortcoming of the current user documentation.


Release: IMDAGG99000-2.5-Infrastructure Management-Data Aggregator