

Administration › Administration Page Reference › Incident Responses - SNMP Trap Notification
Incident Responses - SNMP Trap Notification
Use an SNMP trap notification to update a SNMP Manager about the Open or Closed status of the affected applications, servers, or networks. Use the Duration and Severity options to filter temporary incident conditions.
You can assign a SNMP trap notification to any incident response. Unlike incident responses for applications, servers, and networks, a monitoring device incident response can be filtered by severity (Major or Unavailable) but not by duration.
The management console sends SNMP trap notifications.
Unlike email notifications, the management console sends an SNMP trap when a Server or network incident:
- Opens and Closes
- Changes its severity, for example, from Minor to Major (optional).
To include more than one application, server, or network in the same SNMP trap, assign the same incident response to more than application, server, or network. If more than one application, server, or network is affected, the SNMP trap includes a URL with the details.
Frequently Asked Questions
- Why doesn’t the trap receiver understand a management console trap notification? To enable an SNMP manager to understand a management console SNMP trap notification, compile the CA Application Delivery Analysis MIB into the trap receiver on the SNMP manager. The compiling method varies depending on the SNMP manager. The CA Application Delivery Analysis MIB must be downloaded separately from the CA Support website at http://ca.com/support.
- When does the management console notify you of a change? The management console automatically notifies you when an Open incident meets the severity and duration criteria, and when the management console changes the incident status to Closed. The management console can notify you about the same Open incident more than once, if the metric threshold that was violated meets the severity and threshold criteria. For example, on a 10-minute duration, the management console sends 2 email notifications for a single Open incident where the 5-minute intervals were rated Yellow-Yellow-Green-Yellow-Yellow. In this example, the management console creates separate email notifications because the 10-minute duration criteria was met before and after the Normal (green) 5-minute interval.
- Why should I send a test SNMP trap notification? Sending a test SNMP trap notification verifies that the monitoring device can communicate with the third-party alert system on port 162, the specified SNMP credentials are known on the trap receiver, and the trap receiver can understand the trap message.
- Why do I need to assign an SNMP profile to a trap notification? When sending an SNMP trap notification, the management console cannot validate the SNMP credentials are valid, therefore, the management console cannot discover a valid SNMP profile. To ensure the specified SNMP credentials are known on the trap receiver, send a test trap message. If you do not specify a SNMP profile for a SNMP Trap notification, the management console uses the Default SNMPv2 profile with a community of SuperAgent. Note that the Default SNMP profile is only available for SNMP traps and is not synchronized with the CA Performance Center.
- What port does the management console use to send SNMP trap notifications? The management console sends SNMP traps to UDP port 162. Note that you cannot configure the port on which the management console sends SNMP traps.
- How does the trap message report the affected applications? The management console sends traps for a single network or server. If multiple applications are experiencing the same performance degradation, the management console shows the number of applications affected and provides a link to the list of affected applications. If a single application is affected, the trap message includes the application name.
- How does the trap message report the affected applications? The management console sends traps for a single network or server. If multiple applications are experiencing the same performance degradation, the management console shows the number of applications affected and provides a link to the list of affected applications. If a single application is affected, the trap message includes the application name.
Property Details
Complete the following fields:
- Minimum Conditions for Taking Action
-
Specify the minimum severity and duration required for the management console to launch the responsive action. Both criteria must be met for the management console to launch the responsive action.
- Severity
-
Choose an option to specify the incident severity that is required for the management console to launch the responsive action:
- Duration
-
Choose a threshold, in minutes, for the consecutive amount of time that the same Network or Server metric threshold must be violated for the management console to launch the responsive action.
For example, if Network Round Trip Time (NRTT) is Minor at 1:20, the management console opens a network incident. If NRTT is Minor again at 1:25, and the Duration for the responsive action is 10 minutes, the management console can launch the responsive action.
- SNMP Trap Options
-
- Send SNMP trap to
-
Specify the IP address of the SNMP trap receiver, such as a 3rd-party SNMP manager.
To enable an SNMP manager to understand a SNMP trap notification from the management console, compile the CA Application Delivery Analysis MIB into the trap receiver on the SNMP manager. The compiling method varies depending on the SNMP manager.
The CA Application Delivery Analysis MIB is downloaded separately from the CA Support Web site at http://support.ca.com.
Note: The management console sends SNMP trap notifications to UDP port 162. You cannot configure the management console to send SNMP trap notifications to a different port.
- Send SNMP trap from
-
Select the monitoring device that should send the SNMP trap.
- SNMP profile
-
Select the SNMP profile that identifies a known SNMP user on the trap receiver.
If you do not specify a SNMP profile for a SNMP Trap notification, the management console uses the Default SNMPv2 profile with a community of SuperAgent. Note that the Default SNMP profile is only available for SNMP traps and is not synchronized with the CA Performance Center.
- Time Zone
-
Select the time zone. The management console offsets report data to this time zone. The default time zone is CST6CDT, which is GMT minus 6 hours during Central Standard Time and minus 5 hours during Central Daylight Time. Use specific time zones instead of the Etc version of your time zone where possible because the Etc version does not account for daylight saving time and the offset is the opposite of what you would expect; that is Etc/GMT+4 is four hours behind GMT, not 4 hours ahead.
- Severity Updates
-
Specify whether you want the management console to notify you want the incident severity changes, for example, for Minor to Major:
- Send update traps when incident severity changes: Select this option to send a trap every time the severity of the incident changes.
- Send only incident open and close traps: Select this option to send a trap when the management console opens or closes an incident.
- To send a test SNMP trap to the specified computer
-
Click Send Test Trap.
More information:
Manage SNMP Profiles
Copyright © 2015 CA Technologies.
All rights reserved.
 
|
|