Thread View: comp.protocols.snmp
1 messages
1 total messages
Started by Joachim Martillo
Sat, 10 Oct 1992 15:35
Cold Start Trap
Author: Joachim Martillo
Date: Sat, 10 Oct 1992 15:35
Date: Sat, 10 Oct 1992 15:35
50 lines
2305 bytes
2305 bytes
I was looking through RFC1157. According to this RFC,
The form of the Trap-PDU is:
Trap-PDU ::=
[4]
IMPLICIT SEQUENCE {
enterprise -- type of object generating
-- trap, see sysObjectID in [5]
OBJECT IDENTIFIER,
agent-addr -- address of object generating
NetworkAddress, -- trap
generic-trap -- generic trap type
INTEGER {
coldStart(0),
warmStart(1),
linkDown(2),
linkUp(3),
authenticationFailure(4),
egpNeighborLoss(5),
enterpriseSpecific(6)
},
specific-trap -- specific code, present even
INTEGER, -- if generic-trap is not
-- enterpriseSpecific
time-stamp -- time elapsed between the last
TimeTicks, -- (re)initialization of the network
-- entity and the generation of the
trap
variable-bindings -- "interesting" information
VarBindList
}
I assume that the variable bindings are specific to both the type of
trap and the type of device. For example, on cold start a
multiprotocol router would probably have different information to
convey to a management station than a network printer would.
Is there a specification for "typical" "interesting" information as
relates to trap and to device.
--
Joachim Carlo Santos Martillo Ajami
The article represents noone's opinions other than the author's.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads