MIBs Depot

HP-SN-ROUTER-TRAP-MIB

Registered at
1.3.6.1.4.1.11.0.3
1.3.6.1.4.1.11.0.4
1.3.6.1.4.1.11.0.5
1.3.6.1.4.1.11.0.6
1.3.6.1.4.1.11.0.7
1.3.6.1.4.1.11.0.8
1.3.6.1.4.1.11.0.9
1.3.6.1.4.1.11.0.10
1.3.6.1.4.1.11.0.11
1.3.6.1.4.1.11.0.12
1.3.6.1.4.1.11.0.13
1.3.6.1.4.1.11.0.14
1.3.6.1.4.1.11.0.15
1.3.6.1.4.1.11.0.16
1.3.6.1.4.1.11.0.17
1.3.6.1.4.1.11.0.18
Namespace
hp
Source file
HP-SN-ROUTER-TRAP-MIB
Digest
sha256:79ee501b1da4c7f2c8d4d236fe0d06a8e4e2e02dc4d41ee90f6853e59adfeed8

Imports

FromSymbols
HP-SN-OSPF-GROUP-MIBsnOspfConfigErrorType, snOspfExtLsdbLimit, snOspfIfStatusIpAddress, snOspfIfStatusState, snOspfLsdbAreaId, snOspfLsdbLsId, snOspfLsdbRouterId, snOspfLsdbType, snOspfNbrIpAddr, snOspfNbrRtrId, snOspfNbrState, snOspfPacketSrc, snOspfPacketType, snOspfRouterId, snOspfVirtIfStatusAreaID, snOspfVirtIfStatusNeighbor, snOspfVirtIfStatusState, snOspfVirtNbrArea, snOspfVirtNbrRtrId, snOspfVirtNbrState
HP-SN-ROOT-MIBhp
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMIMODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, TRAP-TYPE, iso
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

HP-SN-OSPF-GROUP-MIB
HP-SN-ROOT-MIB
HP-SN-ROUTER-TRAP-MIB
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC

Notifications

NameOIDStatus
snTrapOspfIfStateChange
NOTIFICATION-TYPE
An ospfIfStateChange trap signifies that there has been a change in the state of a non-virtual OSPF interface. This trap should be generated when the interface state regresses (e.g., goes from Dr to Down) or progresses to a terminal state (i.e., Point-to-Point, DR Other, Dr, or Backup).
1.3.6.1.4.1.11.0.3
snTrapOspfVirtIfStateChange
NOTIFICATION-TYPE
An ospfIfStateChange trap signifies that there has been a change in the state of an OSPF vir- tual interface. This trap should be generated when the inter- face state regresses (e.g., goes from Point- to-Point to Down) or progresses to a terminal state (i.e., Point-to-Point).
1.3.6.1.4.1.11.0.4
snOspfNbrStateChange
NOTIFICATION-TYPE
An ospfNbrStateChange trap signifies that there has been a change in the state of a non- virtual OSPF neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., 2-Way or Full). When an neighbor transitions from or to Full on non-broadcast multi-access and broadcast networks, the trap should be gen- erated by the designated router. A designated router transitioning to Down will be noted by ospfIfStateChange.
1.3.6.1.4.1.11.0.5
snOspfVirtNbrStateChange
NOTIFICATION-TYPE
An ospfIfStateChange trap signifies that there has been a change in the state of an OSPF vir- tual neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., Full).
1.3.6.1.4.1.11.0.6
snOspfIfConfigError
NOTIFICATION-TYPE
An ospfIfConfigError trap signifies that a packet has been received on a non-virtual in- terface from a router whose configuration parameters conflict with this router's confi- guration parameters. Note that the event op- tionMismatch should cause a trap only if it prevents an adjacency from forming.
1.3.6.1.4.1.11.0.7
snOspfVirtIfConfigError
NOTIFICATION-TYPE
An ospfConfigError trap signifies that a pack- et has been received on a virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event optionMismatch should cause a trap only if it prevents an ad- jacency from forming.
1.3.6.1.4.1.11.0.8
snOspfIfAuthFailure
NOTIFICATION-TYPE
An ospfIfAuthFailure trap signifies that a packet has been received on a non-virtual in- terface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type.
1.3.6.1.4.1.11.0.9
snOspfVirtIfAuthFailure
NOTIFICATION-TYPE
An ospfVirtIfAuthFailure trap signifies that a packet has been received on a virtual interface from a router whose authentication key or au- thentication type conflicts with this router's authentication key or authentication type.
1.3.6.1.4.1.11.0.10
snOspfIfRxBadPacket
NOTIFICATION-TYPE
An ospfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.
1.3.6.1.4.1.11.0.11
snOspfVirtIfRxBadPacket
NOTIFICATION-TYPE
An ospfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.
1.3.6.1.4.1.11.0.12
snOspfTxRetransmit
NOTIFICATION-TYPE
An ospfTxRetransmit trap signifies than an OSPF packet has been retransmitted on a non- virtual interface. All packets that may be re- transmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.
1.3.6.1.4.1.11.0.13
ospfVirtIfTxRetransmit
NOTIFICATION-TYPE
An ospfTxRetransmit trap signifies than an OSPF packet has been retransmitted on a virtual interface. All packets that may be retransmit- ted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.
1.3.6.1.4.1.11.0.14
snOspfOriginateLsa
NOTIFICATION-TYPE
An ospfOriginateLsa trap signifies that a new LSA has been originated by this router. This trap should not be invoked for simple refreshes of LSAs (which happesn every 30 minutes), but instead will only be invoked when an LSA is (re)originated due to a topology change. Addi- tionally, this trap does not include LSAs that are being flushed because they have reached MaxAge.
1.3.6.1.4.1.11.0.15
snOspfMaxAgeLsa
NOTIFICATION-TYPE
An ospfMaxAgeLsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge.
1.3.6.1.4.1.11.0.16
snOspfLsdbOverflow
NOTIFICATION-TYPE
An ospfLsdbOverflow trap signifies that the number of LSAs in the router's link-state data- base has exceeded ospfExtLsdbLimit.
1.3.6.1.4.1.11.0.17
snOspfLsdbApproachingOverflow
NOTIFICATION-TYPE
An ospfLsdbApproachingOverflow trap signifies that the number of LSAs in the router's link- state database has exceeded ninety percent of ospfExtLsdbLimit.
1.3.6.1.4.1.11.0.18