If you do not want to notify one of 5 predefined traps (for example, cold start, warm start): yes, you need to define an enterpriseSpecific trap, and you will need to highlight object identifiers (and there are many of them).
Parameters are passed in variable bindings; these are structures defined as
VarBind ::=
SEQUENCE {
name ObjectName,
value ObjectSyntax
}
VarBindList ::= SEQUENCE OF VarBind
ObjectName ::= OBJECT IDENTIFIER
ObjectSyntax ::= CHOICE {
simple SimpleSyntax,
application-wide ApplicationSyntax
}
SimpleSyntax ::= CHOICE {
number INTEGER,
string OCTET STRING,
object OBJECT IDENTIFIER,
empty NULL
}
ApplicationSyntax ::= CHOICE {
address NetworkAddress,
counter Counter,
gauge Gauge,
ticks TimeTicks,
arbitrary Opaque
}
You somehow need to tell your library what the name and meaning are; the library must provide an API to support the various types of data available as values. Note that the variable names are again the identifiers of the object.
source
share