NETSCREEN-OSPF-TRAP-MIB

All MIBs › NETSCREEN-OSPF-TRAP-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2004-05-03

Category: OSPF

Description: Specifies SNMP traps that notify on OSPF neighbor state transitions and routing events for NetScreen firewalls.

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 NETSCREEN-OSPF-TRAP-MIB?

NETSCREEN-OSPF-TRAP-MIB is a Juniper NetScreen (ScreenOS) private enterprise MIB that defines SNMP notifications specifically for OSPFv2 protocol events on NetScreen firewall/security appliances. It exposes trap-control and trap objects that signal changes in OSPF neighbor adjacency and routing state rather than continuously polled counters. For monitoring software status, it is used to detect routing faults and instability -- such as an OSPF neighbor going down or a routing adjacency flapping -- which is a proxy for the health of the device's dynamic-routing process. As an OSPF-specific extension it conceptually depends on the semantics of the standard OSPF-MIB/OSPF-TRAP-MIB defined by IETF RFC 1850, tailored to NetScreen's trap-control model. It is typically deployed on NetScreen/Juniper firewalls acting as OSPF routers at enterprise or service-provider network edges where routing-protocol stability must be tracked in real time. Engineers can download the NETSCREEN-OSPF-TRAP-MIB file directly to load it into their MIB browser.

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

Juniper NetScreen firewall
NetScreen ScreenOS security appliance

Monitoring Examples

An admin enables nsOspfTrapControl so the device emits notifications defined under nsOspfTraps whenever an OSPF neighbor state transitions (e.g., Full to Down). Receiving repeated traps under nsOspfTraps without a matching recovery event indicates a flapping or failed OSPF adjacency, prompting investigation of a WAN link or misconfigured area. Since this module only defines trap-control and notification objects, there are no pollable performance counters -- it is consumed passively via an SNMP trap receiver rather than periodic GET polling.

What Can Be Monitored

OSPF neighbor state changes
OSPF trap enable/disable status
routing adjacency flaps

Imported Objects

From NETSCREEN-OSPF-MIB

nsOspf	MODULE-IDENTITY
nsOspfAddressLessIf	OBJECT-TYPE
nsOspfExtLsdbLimit	OBJECT-TYPE
nsOspfIfIpAddress	OBJECT-TYPE
nsOspfIfState	OBJECT-TYPE
nsOspfIfVRID	OBJECT-TYPE
nsOspfLsdbAreaId	OBJECT-TYPE
nsOspfLsdbLsid	OBJECT-TYPE
nsOspfLsdbRouterId	OBJECT-TYPE
nsOspfLsdbType	OBJECT-TYPE
nsOspfLsdbVRID	OBJECT-TYPE
nsOspfNbrAddressLessIndex	OBJECT-TYPE
nsOspfNbrIpAddr	OBJECT-TYPE
nsOspfNbrRtrId	OBJECT-TYPE
nsOspfNbrState	OBJECT-TYPE
nsOspfNbrVRID	OBJECT-TYPE
nsOspfRouterId	OBJECT-TYPE
nsOspfVirtIfAreaId	OBJECT-TYPE
nsOspfVirtIfNeighbor	OBJECT-TYPE
nsOspfVirtIfState	OBJECT-TYPE
nsOspfVirtIfVRID	OBJECT-TYPE
nsOspfVirtNbrArea	OBJECT-TYPE
nsOspfVirtNbrRtrId	OBJECT-TYPE
nsOspfVirtNbrState	OBJECT-TYPE
nsOspfVirtNbrVRID	OBJECT-TYPE

From NETSCREEN-TRAP-MIB

netscreenTrapDesc	OBJECT-TYPE
netscreenTrapType	OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
nsOspfTrap	1.3.6.1.4.1.3224.18.2.16			The MIB module to describe traps for the OSPF Version 2 Protocol.
nsOspfTrapControl	1.3.6.1.4.1.3224.18.2.16.1
OCT nsOspfSetTrap	1.3.6.1.4.1.3224.18.2.16.1.1	OCTET STRING	read-only	A four-octet string serving as a bit map for the trap events defined by the OSPF traps. This object is used to enable and disable specific OSPF traps where a 1 in the bit field represents enabled. The right-most bit (least significant) represents trap 0.
INT nsOspfConfigErrorType	1.3.6.1.4.1.3224.18.2.16.1.2	INTEGER	read-only	Potential types of configuration conflicts. Used by the nsOspfConfigError and nsOspfConfigVir- tError traps.
INT nsOspfPacketType	1.3.6.1.4.1.3224.18.2.16.1.3	INTEGER	read-only	OSPF packet types.
IP nsOspfPacketSrc	1.3.6.1.4.1.3224.18.2.16.1.4	IpAddress	read-only	The IP address of an inbound packet that can- not be identified by a neighbor instance.
nsOspfTraps	1.3.6.1.4.1.3224.18.2.16.2
NTF nsOspfVirtIfStateChange	1.3.6.1.4.1.3224.18.2.16.2.1			An nsOspfIfStateChange 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 nsOspfNbrStateChange	1.3.6.1.4.1.3224.18.2.16.2.2			An nsOspfNbrStateChange 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 nsOspfIfStateChange.
NTF nsOspfVirtNbrStateChange	1.3.6.1.4.1.3224.18.2.16.2.3			An nsOspfIfStateChange 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 nsOspfIfConfigError	1.3.6.1.4.1.3224.18.2.16.2.4			An nsOspfIfConfigError 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 nsOspfVirtIfConfigError	1.3.6.1.4.1.3224.18.2.16.2.5			An nsOspfConfigError 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 nsOspfIfAuthFailure	1.3.6.1.4.1.3224.18.2.16.2.6			An nsOspfIfAuthFailure 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 nsOspfVirtIfAuthFailure	1.3.6.1.4.1.3224.18.2.16.2.7			An nsOspfVirtIfAuthFailure 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 nsOspfIfRxBadPacket	1.3.6.1.4.1.3224.18.2.16.2.8			An nsOspfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.
NTF nsOspfVirtIfRxBadPacket	1.3.6.1.4.1.3224.18.2.16.2.9			An nsOspfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.
NTF nsOspfTxRetransmit	1.3.6.1.4.1.3224.18.2.16.2.10			An nsOspfTxRetransmit 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 nsOspfVirtIfTxRetransmit	1.3.6.1.4.1.3224.18.2.16.2.11			An nsOspfTxRetransmit 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 nsOspfOriginateLsa	1.3.6.1.4.1.3224.18.2.16.2.12			An nsOspfOriginateLsa 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 nsOspfMaxAgeLsa	1.3.6.1.4.1.3224.18.2.16.2.13			An nsOspfMaxAgeLsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge.
NTF nsOspfLsdbOverflow	1.3.6.1.4.1.3224.18.2.16.2.14			An nsOspfLsdbOverflow trap signifies that the number of LSAs in the router's link-state data- base has exceeded nsOspfExtLsdbLimit.
NTF nsOspfLsdbApproachingOverflow	1.3.6.1.4.1.3224.18.2.16.2.15			An nsOspfLsdbApproachingOverflow trap signifies that the number of LSAs in the router's link- state database has exceeded ninety percent of nsOspfExtLsdbLimit.
NTF nsOspfIfStateChange	1.3.6.1.4.1.3224.18.2.16.2.16			An nsOspfIfStateChange 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).

RFC description

Defines SNMP trap notifications for OSPF neighbor state changes and routing events on NetScreen firewalls.

Start monitoring Juniper NetScreen firewall (OSPFv2 trap notifications) 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 NETSCREEN-OSPF-TRAP-MIB

What Is NETSCREEN-OSPF-TRAP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description