HP-SN-ROUTER-TRAP-MIB

All MIBs › HP-SN-ROUTER-TRAP-MIB

Category: Alarm and Event Management, Vendor: HP/HPE

Description: HP ServerNet (Foundry-heritage) SNMP MIB defining trap notifications for routing protocol events on HP SN network devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is HP-SN-ROUTER-TRAP-MIB?

HP-SN-ROUTER-TRAP-MIB is an HP ServerNet (Foundry-heritage) MIB that defines SNMP trap notifications for routing protocol events on HP SN-series network devices. Rather than exposing polled counters, it focuses on fault and event data: asynchronous notifications about routing protocol state changes, adjacency failures, and similar routing-layer conditions. Its primary monitoring value is for faults/traps -- alerting operators in near real time to routing instability or failures rather than steady-state hardware metrics like temperature or CPU. It is dependent on underlying routing-protocol MIBs (e.g., OSPF-MIB, BGP4-MIB) and the SNMPv2 notification framework for its trap definitions. It is typically deployed on HP/Foundry-based core or edge routers where operators want immediate alerting on routing protocol events via an SNMP trap receiver or NMS. Engineers can download the HP-SN-ROUTER-TRAP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HP-SN-ROUTER-TRAP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

HP ServerNet (Foundry-heritage) routers

Monitoring Examples

No sample objects were listed for this module, so specific trap names cannot be confirmed from the given data. Given the description, an admin would configure their NMS to receive traps corresponding to routing protocol events (e.g., adjacency down, route flap) generated by the HP SN router, alerting them to routing instability without needing to poll routing tables directly. Further concrete object detail would be speculative without sample objects.

Imported Objects

From HP-SN-OSPF-GROUP-MIB

snOspfConfigErrorType	OBJECT-TYPE
snOspfExtLsdbLimit	OBJECT-TYPE
snOspfIfStatusIpAddress	OBJECT-TYPE
snOspfIfStatusState	OBJECT-TYPE
snOspfLsdbAreaId	OBJECT-TYPE
snOspfLsdbLsId	OBJECT-TYPE
snOspfLsdbRouterId	OBJECT-TYPE
snOspfLsdbType	OBJECT-TYPE
snOspfNbrIpAddr	OBJECT-TYPE
snOspfNbrRtrId	OBJECT-TYPE
snOspfNbrState	OBJECT-TYPE
snOspfPacketSrc	OBJECT-TYPE
snOspfPacketType	OBJECT-TYPE
snOspfRouterId	OBJECT-TYPE
snOspfVirtIfStatusAreaID	OBJECT-TYPE
snOspfVirtIfStatusNeighbor	OBJECT-TYPE
snOspfVirtIfStatusState	OBJECT-TYPE
snOspfVirtNbrArea	OBJECT-TYPE
snOspfVirtNbrRtrId	OBJECT-TYPE
snOspfVirtNbrState	OBJECT-TYPE

From HP-SN-ROOT-MIB

hp	OBJECT-IDENTITY

From RFC-1215

TRAP-TYPE

OIDs

OID symbolic	OID numeric	Description
NTF snTrapOspfIfStateChange	1.3.6.1.4.1.11.0.3	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).
NTF snTrapOspfVirtIfStateChange	1.3.6.1.4.1.11.0.4	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).
NTF snOspfNbrStateChange	1.3.6.1.4.1.11.0.5	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.
NTF snOspfVirtNbrStateChange	1.3.6.1.4.1.11.0.6	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).
NTF snOspfIfConfigError	1.3.6.1.4.1.11.0.7	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.
NTF snOspfVirtIfConfigError	1.3.6.1.4.1.11.0.8	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.
NTF snOspfIfAuthFailure	1.3.6.1.4.1.11.0.9	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.
NTF snOspfVirtIfAuthFailure	1.3.6.1.4.1.11.0.10	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.
NTF snOspfIfRxBadPacket	1.3.6.1.4.1.11.0.11	An ospfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.
NTF snOspfVirtIfRxBadPacket	1.3.6.1.4.1.11.0.12	An ospfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.
NTF snOspfTxRetransmit	1.3.6.1.4.1.11.0.13	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.
NTF ospfVirtIfTxRetransmit	1.3.6.1.4.1.11.0.14	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.
NTF snOspfOriginateLsa	1.3.6.1.4.1.11.0.15	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.
NTF snOspfMaxAgeLsa	1.3.6.1.4.1.11.0.16	An ospfMaxAgeLsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge.
NTF snOspfLsdbOverflow	1.3.6.1.4.1.11.0.17	An ospfLsdbOverflow trap signifies that the number of LSAs in the router's link-state data- base has exceeded ospfExtLsdbLimit.
NTF snOspfLsdbApproachingOverflow	1.3.6.1.4.1.11.0.18	An ospfLsdbApproachingOverflow trap signifies that the number of LSAs in the router's link- state database has exceeded ninety percent of ospfExtLsdbLimit.

RFC description

OSPF routing protocol event traps and notifications for HP/Foundry network routers.

Start monitoring HP ServerNet (Foundry-heritage) router (routing-protocol event traps) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download HP-SN-ROUTER-TRAP-MIB

What Is HP-SN-ROUTER-TRAP-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description