Справочник Пользователя для 3e Technologies International Inc. 523E-900
AirGuard WiMesh 3e-
523 Series User’s Guide
Copyright
2015 Ultra Electronics, 3eTI
October 2015
45
29000169-005 Revision C1
Trap-directed notification can result in substantial savings of network and agent resources by eliminating
the need for frivolous SNMP requests. However, it is not possible to totally eliminate SNMP polling. SNMP
requests are required for discovery and topology changes. In addition, a managed device agent can not
send a trap, if the device has had a catastrophic outage.
the need for frivolous SNMP requests. However, it is not possible to totally eliminate SNMP polling. SNMP
requests are required for discovery and topology changes. In addition, a managed device agent can not
send a trap, if the device has had a catastrophic outage.
SNMPv1 traps are defined in RFC 1157, with the following fields:
Enterprise
Identifies the type of managed object generating the trap.
Agent address Provides the address of the managed object generating the trap.
Generic trap type
Indicates one of a number of generic trap types.
Specific trap code
Indicates one of a number of specific trap codes.
Time stamp
Provides the amount of time that has elapsed between the last network
reinitialization and generation of the trap.
Variable bindings
The data field of trap containing PDU. Each variable binding associates a
particular MIB object instance with its current value.
Standard generic traps are: coldStart, warmStart, linkDown, linkUp, authenticationFailure,
egpNeighborLoss.
egpNeighborLoss.
In the current release, 3eTI has implemented warmStart, link-Down, linkUp, and authenticationFailure 5
generic traps and transports those traps using SNMPx2, V2c Trap PDU format.
generic traps and transports those traps using SNMPx2, V2c Trap PDU format.
For generic SNMPv1 traps, 3eTI also redefined some generic traps (see the 3eti-trap-mibs document) by
adding some bound variables.
adding some bound variables.
For example, when a trap is received for a warmStart, the receiving system will be able to see one variable
associated with this trap. The received variableName field will shows the 3eTI enterprise oid. The
varibleValue field will indicate a warmStart reason.
associated with this trap. The received variableName field will shows the 3eTI enterprise oid. The
varibleValue field will indicate a warmStart reason.
Additionally, a device does not send a trap to a network management system unless it is configured to do
so.
so.