Snmp Traps And Informs - Cisco ACE-4710-K9 Administration Manual

Chapter 8 Configuring SNMP
SNMP Overview

SNMP Traps and Informs

You can configure the ACE to send notifications (such as traps or inform requests)
to SNMP managers when particular events occur. In some instances, traps can be
unreliable because the receiver does not send any acknowledgment when it
receives a trap and the sender cannot determine if the trap was received. However,
an SNMP manager that receives inform requests acknowledges the message with
an SNMP Response PDU. If the sender never receives a Response, the inform
request is usually retransmitted. Inform requests are more likely to reach their
intended destination.
Notifications may contain a list of MIB variable bindings that clarify the status
being relayed by the notification. The list of variable bindings associated with a
notification is included in the notification definition in the MIB. For standard
MIBs, Cisco has enhanced some notifications with additional variable bindings
that further clarify the cause of the notification.
The clogOriginID and clogOriginIDType variable bindings appended with each
Note
notification can be used by the NMS application to uniquely identify the device
originating the trap. You can configure the values for clogOriginID and
clogOriginIDType varbinds to uniquely identify the device by using the logging
device-id configuration mode command. For details on the logging device-id
command, see the Cisco 4700 Series Application Control Engine Appliance
System Message Guide.
Use the SNMP-TARGET-MIB to obtain more information on trap destinations
and inform requests.
For details on SNMP notifications supported by the ACE, see the "Supported
MIBs and Notifications" section.
Cisco 4700 Series Application Control Engine Appliance Administration Guide
8-5
OL-11157-01