Database Reference
In-Depth Information
logy changes. In addition, a managed device agent cannot send a trap, if the device has
had a catastrophic outage.
SNMPv1 traps are defined in RFC 1157 with the following fields:
•
Enterprise
: This identifies the type of the managed object that generates the trap
•
Agent address
: This provides the address of the managed object that generates
the trap
•
Generic trap type
: This indicates one of the numbers of generic trap types
•
Specific trap code
: This indicates one of the number of specific trap codes
•
Time stamp
: This provides the amount of time that has elapsed between the last
network reinitialization and generation of the trap
•
Variable bindings:
This refers to the data field of the trap that contains PDU.
Each variable binding associates a particular MIB object instance with its current
value
In SNMPv2c, a trap is defined as
NOTIFICATION
and formatted differently compared to
SNMPv1. It has these parameters:
•
sysUpTime
: This is the same as a time stamp in the SNMPv1 trap
•
snmpTrapOID
: This is the trap identification field
•
VarBindList
: This is a list of variable bindings
SOA on SNMP traps? Yes, why not! We believe that nobody here at the final chapter is
under the illusion that SOA is only SOAP (or REST). The concept of EDN is just one of
the many patterns under the roof of service orientation; SNMP as a transport protocol
works just fine for communication, in addition to the traditional TR-69 telecom.
Just look at the fields from the previous specification and compare them with the elected
SBDH elements we proposed earlier. It is also needless to say that here we are also deal-
ing with objects and notifications based on the objects' changes, not just with some occur-
Handling
, will be incomplete without handling SNMP notifications from network devices.
Oracle Event Processing Suite is highly suitable for aggregating all types of events: Busi-
ness/Functional and SNMP Traps notifications.
Search WWH ::
Custom Search