TIMETRA-RIP-NG-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-RIP-NG-MIB

Organization: Nokia

Last Updated: 2013--0-4-

Description: TIMETRA-RIP-NG-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 TIMETRA-RIP-NG-MIB?

TIMETRA-RIP-NG-MIB is a Nokia (formerly Alcatel-Lucent Timetra) proprietary MIB for the SR OS implementation of RIP and RIP-NG (RIP for IPv6) routing protocols. It exposes both global protocol-instance statistics — learned and timed-out routes, current and maximum memory usage — and per-instance configuration objects such as protocol version, authentication type/key, message size, and inbound metric. This MIB supports monitoring of the software routing process's health and resource consumption: tmnxRipNgGlobalCurrentMemory versus tmnxRipNgGlobalMaximumMemory reveals whether the RIP-NG process is approaching a memory ceiling, and tmnxRipNgGlobalTimedoutRoutes indicates route instability or lost neighbor updates, both important indicators of routing software health. It naturally depends on IETF RIP concepts (RFC 2453/2080) as its baseline protocol semantics, reimplemented in Nokia's proprietary instrumentation. It is typically deployed on Nokia (Alcatel-Lucent) 7750 SR and related service router platforms in service-provider IP/MPLS networks running RIP-NG for IPv6 routing. Engineers can download the TIMETRA-RIP-NG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TIMETRA-RIP-NG-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) 7750 SR service router
  • Nokia SR OS-based routing platform

Monitoring Examples

An administrator would poll tmnxRipNgGlobalLearnedRoutes and tmnxRipNgGlobalTimedoutRoutes to track how many RIP-NG routes are currently learned versus timing out, which would reveal an unstable adjacency or flapping link if timeouts spike. Checking tmnxRipNgGlobalCurrentMemory against tmnxRipNgGlobalMaximumMemory on a given instance (tmnxRipNgInstTable/tmnxRipNgInstEntry) would show whether the RIP-NG process is nearing a configured memory limit, a precursor to route-table truncation. Per-instance settings like tmnxRipNgInstAuthType, tmnxRipNgInstAuthKey, and tmnxRipNgInstMetricIn confirm authentication and metric configuration are as expected.

What Can Be Monitored

  • learned route count
  • timed-out route count
  • current memory usage
  • maximum memory limit
  • RIP-NG instance authentication configuration
  • inbound metric configuration
Imported Objects

From IF-MIB

InterfaceIndex

From INET-ADDRESS-MIB

InetAddress
InetAddressPrefixLength
InetAddressType

From RIPv2-MIB

RouteTag

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

From TIMETRA-GLOBAL-MIB

timetraSRMIBModulesOBJECT-IDENTITY
tmnxSRConfsOBJECT-IDENTITY
tmnxSRNotifyPrefixOBJECT-IDENTITY
tmnxSRObjsOBJECT-IDENTITY

From TIMETRA-TC-MIB

TItemDescription
TNamedItem
TNamedItemOrEmpty
TPolicyStatementNameOrEmpty
TPriorityOrUndefined
TmnxAdminState
TmnxOperState

From TIMETRA-VRTR-MIB

vRtrIDOBJECT-TYPE
vRtrIfIndexOBJECT-TYPE

How to Use in IPNetwork Monitor

Example using tmnxRipNgGlobalLearnedRoutes OID:

Select a Nokia (Alcatel-Lucent) 7750 SR service router (RIP/RIP-NG process memory/route-stability status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type tmnxRipNgGlobalLearnedRoutes into the Find box to locate it in the OID tree, then select it and click OK. It reports tmnxRipNgGlobalLearnedRoutes is the number of routes learned by RIP/RIP-NG. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Nokia SROS RIP/RIP-NG routing protocol management with per-virtual router configuration and defaults.

Start monitoring Nokia (Alcatel-Lucent) 7750 SR service router (RIP/RIP-NG process memory/route-stability 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 TIMETRA-RIP-NG-MIB