TIMETRA-RIP-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-RIP-MIB

Organization: Alcatel-Lucent

Last Updated: 2011-02-01

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

TIMETRA-RIP-MIB is Alcatel-Lucent's (Nokia SROS) enterprise MIB for managing RIPv2 routing on their service routers, using the "vRtr" (virtual router) naming convention that reflects SROS's multi-instance routing architecture. It exposes both global RIP statistics -- learned and timed-out route counts, current and maximum memory consumed by the RIP process -- and per-instance configuration data such as authentication type/key, message size, and inbound/outbound route metrics, organized per virtual router instance. Its monitoring emphasis blends software/protocol health (RIP process memory consumption, a rising current-memory value approaching the maximum-memory ceiling signaling resource pressure) with routing-configuration status (authentication settings and metric adjustments per interface) that affects whether routes are correctly learned and advertised. As an SROS virtual-router-scoped MIB it depends on Alcatel-Lucent's virtual-router MIB for instance context and general RIPv2 semantics for its protocol behavior. It is deployed on Alcatel-Lucent/Nokia SROS service routers in service-provider and enterprise WAN networks running RIP within one or more virtual router instances, making TIMETRA-RIP-MIB SNMP monitoring a standard part of SROS RIP operations oversight.

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

  • Alcatel-Lucent/Nokia SROS service routers

Monitoring Examples

An operator would poll vRtrRipGlobalLearnedRoutes and vRtrRipGlobalTimedoutRoutes to gauge overall RIP routing-table churn, and watch vRtrRipGlobalCurrentMemory against vRtrRipGlobalMaximumMemory to catch the RIP process approaching a configured memory ceiling, which could cause dropped routes. Within vRtrRipInstanceTable/vRtrRipInstanceEntry, indexed per virtual router instance, checking vRtrRipInstanceAuthType and vRtrRipInstanceAuthKey confirms authentication is correctly configured between RIP neighbors, since a mismatch would silently drop route updates. vRtrRipInstanceMetricIn/MetricOut let an administrator verify metric adjustments are applied as intended on a per-instance basis, explaining unexpected route-preference behavior.

What Can Be Monitored

  • global learned/timed-out route counts
  • RIP process memory usage
  • per-instance authentication type/key
  • per-instance inbound/outbound metric
  • message size configuration
Imported Objects

From IF-MIB

InterfaceIndex

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

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 vRtrRipGlobalLearnedRoutes OID:

Select an Alcatel-Lucent/Nokia SROS service router (RIP process memory/route-count 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 vRtrRipGlobalLearnedRoutes into the Find box to locate it in the OID tree, then select it and click OK. It reports vRtrRipGlobalLearnedRoutes is the number of routes learned by RIP. 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

RIPv2 routing protocol management for Alcatel-Lucent SROS virtual routers.

Start monitoring Alcatel-Lucent/Nokia SROS service routers (RIP process memory/route-count 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-MIB