TROPIC-OSPF-MIB

All MIBs › TROPIC-OSPF-MIB

Organization: Nokia

Last Updated: 2015-04-03

Category: Nokia Optical Transport

Description: Manages Nokia Tropic OSPF routing protocol configuration and neighbor state in optical transport.

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 TROPIC-OSPF-MIB?

TROPIC-OSPF-MIB is part of Nokia's Tropic DWDM MIB suite, covering the OSPF routing protocol as used for control-plane signaling within the optical transport network. It exposes OSPF configuration objects and neighbor/adjacency state specific to Nokia's DWDM control plane. Its monitoring role is chiefly software/protocol status: tracking OSPF neighbor and adjacency state reveals whether control-plane connectivity between optical network elements is healthy, which is essential for automated wavelength/path provisioning to function. Notably, it builds on standard OSPF protocol concepts (as in the IETF OSPF-MIB) adapted for use within the optical transport control plane. It is deployed on Nokia DWDM network elements that use OSPF for control-plane routing in service-provider optical backbone networks. Engineers can download the TROPIC-OSPF-MIB file directly to load it into their MIB browser.

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

Nokia (Alcatel-Lucent) Tropic DWDM optical transport network element

Monitoring Examples

No sample object names were provided for this module. Based on its description as the Nokia DWDM OSPF MIB, an admin would typically poll OSPF neighbor state objects to confirm control-plane adjacencies between network elements remain established, since a neighbor stuck in a non-full state would indicate a control-plane fault that could prevent automated path or wavelength provisioning from completing.

What Can Be Monitored

OSPF neighbor/adjacency state
OSPF configuration parameters
control-plane routing status

Imported Objects

From IF-MIB

ifIndex

OBJECT-TYPE

From OSPF-MIB

AreaID

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION

From TROPIC-GLOBAL-REG

tnOspfMIB	OBJECT-IDENTITY
tnProtocolModules	OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
tnOspfMibModule	1.3.6.1.4.1.7483.1.1.2.4.3			The Nokia DWDM OSPF MIB.
tnOspfConf	1.3.6.1.4.1.7483.2.5.1.1
tnOspfGroups	1.3.6.1.4.1.7483.2.5.1.1.1
tnOspfAreaGroup	1.3.6.1.4.1.7483.2.5.1.1.1.2
tnOspfPortGroup	1.3.6.1.4.1.7483.2.5.1.1.1.21
tnOspfMultiAreaConfigGroup	1.3.6.1.4.1.7483.2.5.1.1.1.22
tnOspfCompliances	1.3.6.1.4.1.7483.2.5.1.1.2
tnOspfCompliance	1.3.6.1.4.1.7483.2.5.1.1.2.1
tnOspfObjs	1.3.6.1.4.1.7483.2.5.1.2
tnOspfAreaTable	1.3.6.1.4.1.7483.2.5.1.2.2		not-accessible
tnOspfAreaEntry	1.3.6.1.4.1.7483.2.5.1.2.2.1		not-accessible
TNT tnOspfAreaTopologyId	1.3.6.1.4.1.7483.2.5.1.2.2.1.1	TnTopologyId	not-accessible
ARE tnOspfAreaId	1.3.6.1.4.1.7483.2.5.1.2.2.1.2	AreaID	not-accessible
tnOspfPortTable	1.3.6.1.4.1.7483.2.5.1.2.21		not-accessible
tnOspfPortEntry	1.3.6.1.4.1.7483.2.5.1.2.21.1		not-accessible
TNT tnOspfPortTopologyId	1.3.6.1.4.1.7483.2.5.1.2.21.1.1	TnTopologyId	read-create
tnOspfMultiAreaConfigTable	1.3.6.1.4.1.7483.2.5.1.2.22		not-accessible
tnOspfMultiAreaConfigEntry	1.3.6.1.4.1.7483.2.5.1.2.22.1		not-accessible
ARE tnOspfMultiAreaId	1.3.6.1.4.1.7483.2.5.1.2.22.1.1	AreaID	read-create
INT tnOspfMultiAreaConfigType	1.3.6.1.4.1.7483.2.5.1.2.22.1.2	INTEGER	read-create	Specifies an OSPF area type: normal areas are defined as areas that can accept intra-area, inter-area and external routes. stub areas do not accept routes belonging to external autonomous systems (AS); however, these areas have inter-area and intra-area routes. This reduces the size of the routing databases for the area's internal routers. Routers in the stub area also contain a default route which is advertised to the area by the Area Border Router (ABR). totallyStub areas do not allow routes other than intra-area and the default route to be propagated within the area. This further reduces the size of the routing databases for the area's internal routers. The ABR advertises a default route into the area and all the routers belonging to this area use the default route to send any traffic outside the area. nssa (Not So Stub Areas) can import AS external routes from within the area and send them to other areas, but cannot receive AS external routes from other areas. Inter-area and intra-area routes are allowed along with a default route which is advertised to the area by the ABR. nssaTotallyStub areas are similar to nssa with the added restriction that inter-area routes are not allowed.
INT tnOspfMultiAreaConfigDnsOpaqueLsa	1.3.6.1.4.1.7483.2.5.1.2.22.1.3	INTEGER	read-create	Opaque LSA status for the DNS application. Determines whether opaque LSAs for the DNS application shall be distributed into this OSPF area, and received from this area. yes - DNS opaque LSAs are distributed to the area, and received from the area. no - DNS opaque LSAs are not distributed to the area, and not received from the area.
INT tnOspfMultiAreaConfigWavekeyOpaqueLsa	1.3.6.1.4.1.7483.2.5.1.2.22.1.4	INTEGER	read-create	Opaque LSA status for the Wave key application. Determines, whether opaque LSAs for the Wave key application shall be distributed into this OSPF area, and received from this area. Wave Key opaque LSAs can only be enabled in one OSPF Area. yes - Wave key opaque LSAs are distributed to the area, and received from the area no - Wave key opaque LSAs are not distributed to the area, and not received from the area.
INT tnOspfMultiAreaConfigNssaTranslate	1.3.6.1.4.1.7483.2.5.1.2.22.1.5	INTEGER	read-create	Applicable only if area type is nssa or nssaTotallyStub. Determines behavior of NSSA ABR router translation of internal area type 7 LSAs to type 5 LSAs which get propagated into other areas. candidate ospf elects one of candidate routers to be a translator for this area. always router will be always used as translator for this area. never router will never be used as translator for this area. notApplicable is when the type is not nssa or nssaTotallyStub.
I32 tnOspfMultiAreaConfigDefaultCost	1.3.6.1.4.1.7483.2.5.1.2.22.1.6	Integer32	read-create	Specifies the cost in the range -1 to 16777215 for the default route originated by stub, totallyStub, nssa or nssaTotallyStub area ABR. -1 indicates that the default cost is not applicable. Current configurable range: 0 to 16777215. Note: If the cost is set to the maximum value of 16777215 this prevents the ABR from distributing a default route within the Stub or NSSA area.
IP tnOspfMultiAreaConfigVirtualLinkIp	1.3.6.1.4.1.7483.2.5.1.2.22.1.7	IpAddress	read-create	Applicable only for normal Areas. Allows for the creation of a virtual link for this area. OSPF requires that all areas attach directly to Area 0.0.0.0 but not that the attachment be physical. One can take any physical arrangement of areas and attach them logically through OSPF virtual links. Specifies the Loopback interface IP Address of the NE to terminate the virtual link. This NE should have an interface that is connected to Area 0.0.0.0 and a non 0.0.0.0 Area. Note: A virtual link must be configured on both NEs. Virtual links cannot be established through Area 0.0.0.0, stub, totallyStub, nssa or nssaTotallyStub type areas. The IP address of 0.0.0.0 means no virtual link.
ROW tnOspfMultiAreaConfigRowStatus	1.3.6.1.4.1.7483.2.5.1.2.22.1.8	RowStatus	read-create	Status of this OSPF area. supported values: 1 - active 4 - createAndGo 6 - destroy. To create an OSPF area, set the value to 4. To delete an OSPF area, set the value to 6. After an OSPF area is created, upon a retrieve of this attribute, 1 is returned. That is, the active state is not set but it is transitioned after the OSPF area has been created.

RFC description

Nokia DWDM OSPF MIB providing management of OSPF routing protocol on optical transport platforms.

Start monitoring Nokia (Alcatel-Lucent) Tropic DWDM optical transport network element (OSPF control-plane neighbor/adjacency 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.

Download TROPIC-OSPF-MIB

What Is TROPIC-OSPF-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description