FANDOM


Background: Know: Trap, element, object, TimeTicks , community , prerequisites - EGP, coldStart, warmStart, Recognize:


Up
Previous Next
Down

Generic TrapsEdit

Traps are the pathways for the agents to send an asynchronous notification to the monitoring station about the condition that the monitor should be aware of. These traps are sent using UDP and are hence unreliable. So the sender can neither assume that the trap arrive accurately nor he can assume that the trap are sent away.

Traps are classified into two categories, Generic and enterprise specific. The generic traps are seven in number from 0 to 6 for condition ranging initially from ColdStart to the Enterprise specific.The latter ones are the loopholes that make the trap mechanism very powerful. The following Table lists generic trap Types that can be reveived by SNMP[1][2].

Value

Type

Description


0


coldStart

Indicates that the agent has rebooted. The entire set of management variables are reset.CounterS and GaugeS will be reset to zero . It can be used to determine when new hardware is added to the network. When a device is powered on, it sends this trap to its trap destination. If the trap destination is set correctly the NMS can receive the trap and determine whether it needs to manage the device

1

warmStart

Indicates that the agent has reinitialized itself. The Varaiables are not reset

2

linkDown

When an interface on a device goes down this occurs. The first variable binding identifies which interface went down

3

Linkup

Sent when an interface on a device goes down. The first variable binding identifies which interface went down

4

authenticationFailure

Indicates that someone has tried to query your agent with an incorrect community string; useful in determining if someone is trying to gain unauthorized access to one of your devices


5


egpNeighborLoss

Indicates that an Exterior Gateway Protocol (EGP) neighbor has gone down.


6


enterpriseSpecific

Indicates that the trap is enterprise-specific. SNMP vendors and users define their own traps under the private-enterprise branch of the SMI object tree. To process this trap properly, the NMS has to decode the specific trap number that is part of the SNMP message


References: 1: [1] 2: [2]