Classes in this File | Line Coverage | Branch Coverage | Complexity | ||||
GenericSnmpTrapType |
|
| 0.0;0 |
1 | package net.sf.snmpadaptor4j.object; | |
2 | ||
3 | /** | |
4 | * Enumeration of generic type of SNMP traps. | |
5 | * @author <a href="http://fr.linkedin.com/in/jpminetti/">Jean-Philippe MINETTI</a> | |
6 | */ | |
7 | 48 | public enum GenericSnmpTrapType { |
8 | ||
9 | /** | |
10 | * RFC1157 says: | |
11 | * <p> | |
12 | * A coldStart(0) trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity | |
13 | * implementation may be altered. | |
14 | * </p> | |
15 | */ | |
16 | 1 | coldStart, |
17 | ||
18 | /** | |
19 | * RFC1157 says: | |
20 | * <p> | |
21 | * A warmStart(1) trap signifies that the sending protocol entity is reinitializing itself such that neither the agent configuration nor the protocol entity | |
22 | * implementation is altered. | |
23 | * </p> | |
24 | */ | |
25 | 1 | warmStart, |
26 | ||
27 | /** | |
28 | * RFC1157 says: | |
29 | * <p> | |
30 | * A linkDown(2) trap signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration. | |
31 | * </p> | |
32 | * <p> | |
33 | * The Trap-PDU of type linkDown contains as the first element of its variable-bindings, the name and value of the ifIndex instance for the affected interface. | |
34 | * </p> | |
35 | */ | |
36 | 1 | linkDown, |
37 | ||
38 | /** | |
39 | * RFC1157 says: | |
40 | * <p> | |
41 | * A linkUp(3) trap signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come | |
42 | * up. | |
43 | * </p> | |
44 | * <p> | |
45 | * The Trap-PDU of type linkUp contains as the first element of its variable-bindings, the name and value of the ifIndex instance for the affected interface. | |
46 | * </p> | |
47 | */ | |
48 | 1 | linkUp, |
49 | ||
50 | /** | |
51 | * RFC1157 says: | |
52 | * <p> | |
53 | * An authenticationFailure(4) trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. While | |
54 | * implementations of the SNMP must be capable of generating this trap, they must also be capable of suppressing the emission of such traps via an | |
55 | * implementation-specific mechanism. | |
56 | * </p> | |
57 | */ | |
58 | 1 | authenticationFailure, |
59 | ||
60 | /** | |
61 | * RFC1157 says: | |
62 | * <p> | |
63 | * An egpNeighborLoss(5) trap signifies that an EGP neighbor for whom the sending protocol entity was an EGP peer has been marked down and the peer relationship | |
64 | * no longer obtains. | |
65 | * </p> | |
66 | * <p> | |
67 | * The Trap-PDU of type egpNeighborLoss contains as the first element of its variable-bindings, the name and value of the egpNeighAddr instance for the affected | |
68 | * neighbor. | |
69 | * </p> | |
70 | */ | |
71 | 1 | egpNeighborLoss; |
72 | ||
73 | } |