TIMETRA-RIP-MIB :: vRtrRipGlobalLearnedRoutes

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-RIP-MIB › vRtrRipGlobalLearnedRoutes

vRtrRipGlobalLearnedRoutes

Module: TIMETRA-RIP-MIB

OID (symbolic): TIMETRA-RIP-MIB::vRtrRipGlobalLearnedRoutes

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.9.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: vRtrRipGlobalLearnedRoutes is the number of routes learned by RIP.

What is vRtrRipGlobalLearnedRoutes?

Counter of the total number of RIP routes this router has learned from its RIP neighbors; a sysadmin watches this to confirm RIP is actually exchanging routes and to spot a sudden drop that suggests a neighbor or link failure.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.9.1.1
snmpwalk -v2c -c public <target> TIMETRA-RIP-MIB::vRtrRipGlobalLearnedRoutes

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.9.1.1.1
snmpget -v2c -c public <target> TIMETRA-RIP-MIB::vRtrRipGlobalLearnedRoutes.1

Start monitoring Alcatel-Lucent/Nokia SROS service routers (RIP process memory/route-count status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-RIP-MIB::vRtrRipGlobalLearnedRoutes OID value, configure state conditions and alerts, and monitor any Alcatel-Lucent/Nokia SROS service routers (RIP process memory/route-count status) from a single console.

How to Use in IPNetwork Monitor

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.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.2tmnxSRObjsALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.2.9vRtrRipObjsTIMETRA-RIP-MIB
1.3.6.1.4.1.6527.3.1.2.9.1vRtrRipGlobalsTIMETRA-RIP-MIB
1.3.6.1.4.1.6527.3.1.2.9.1.1vRtrRipGlobalLearnedRoutesTIMETRA-RIP-MIB