FOUNDRY-SN-ROUTER-TRAP-MIB

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

Description: FOUNDRY-SN-ROUTER-TRAP-MIB module

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 FOUNDRY-SN-ROUTER-TRAP-MIB?

FOUNDRY-SN-ROUTER-TRAP-MIB is the Foundry Networks (later acquired by Brocade/HP) counterpart trap MIB for ServerNet-heritage SN-series routers, defining SNMP trap notifications for routing protocol events. As no module description or sample objects were provided, exact object names cannot be confirmed, but by its naming pattern it mirrors HP-SN-ROUTER-TRAP-MIB in defining fault/event notifications rather than polled performance counters. Its monitoring value would be in real-time alerting on routing protocol state changes (e.g., adjacency or route changes) on Foundry SN routers rather than steady-state hardware metrics like temperature or CPU. It likely depends on underlying routing-protocol MIBs and the SNMPv2 notification framework for trap structure. It would typically be deployed on Foundry Networks SN-series routers for NMS-based alerting on routing instability. Network engineers evaluating or troubleshooting this functionality can download the FOUNDRY-SN-ROUTER-TRAP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in FOUNDRY-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

Foundry Networks SN-series routers

Monitoring Examples

No sample objects or module description were provided for this module, so specific trap names or monitoring scenarios cannot be confirmed from the given data. Based on the naming convention paralleling HP-SN-ROUTER-TRAP-MIB, this module would define routing-protocol event traps that an NMS would subscribe to for real-time alerting rather than data intended for periodic polling. No further technical detail can be honestly provided without object names.

Imported Objects

From FOUNDRY-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 FOUNDRY-SN-ROOT-MIB

foundry

MODULE-IDENTITY

From RFC-1215

TRAP-TYPE

OIDs

OID symbolic	OID numeric	Description
NTF snTrapOspfIfStateChange	1.3.6.1.4.1.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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.1991.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

Defines SNMP trap notifications for Foundry Networks router platforms, including OSPF interface state changes, neighbor changes, and authentication failures.

Start monitoring Foundry Networks SN-series 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 FOUNDRY-SN-ROUTER-TRAP-MIB

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

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description