|
Netmond V2. Trap directive
The Trap directive defines the way Netmond process
SNMP traps.
There are four forms of Trap directive usage:
- Trap Deny
- Globally, disable catching of SNMP traps.
Default: if no traps defined - traps catching disabled. Otherwise - enabled.
- Trap SourceCheck
- Globally, enable source IP address checking - source IP have to match
agent address value from inside trap body. Default - no check.
- Trap "name" {
- Enterprise oid
- [ Specific number ]
- [ Community "string" ]
- }
- Declare SNMP trap and define it parameters:
- name
- Unique trap name.
- oid
- Enterprise OID of this trap (1.3.6.1...).
- number
- Specific number for Enterprise, by default is 0.
- string
- SNMP community, by default - "public".
- Trap ( Generic | "name" )
[ "arguments" ]
- Being used inside objects or subobject declaration, bind this trap to
parent object.
When trap received, OIDs from trap compared with object's
variable's OIDs. If match happen, value from trap copied to this
object's variable.
- Generic
- Use built-in processing of Cold/Warm Start, Link Up/Down,
BGP Peer Established/Down è Cisco Reload traps on an object.
- arguments
- Argument string. Usually, used for SNMP Community passing.
Community "$1" expression in global-level trap declaration
mean "use first argument as a SNMP trap community".
Traps with various Enterprise and Specific
have their own OIDs set. Netmond don't know the meaning of these OIDs
and have no default handler for them. (exception is Trap Generic).
So, you have to explicitly define object's variables and OID's to utilize
trap notifications.
See also:
Catching specific SNMP trap example
Object directive
© 1998-2002, Rinet Software
|