NETSCREEN-VR-RIPv2-MIB :: nsVrRip2GlobalRouteChanges

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NETSCREEN-VR-RIPv2-MIB › nsVrRip2GlobalRouteChanges

nsVrRip2GlobalRouteChanges

Module: NETSCREEN-VR-RIPv2-MIB

OID (symbolic): NETSCREEN-VR-RIPv2-MIB::nsVrRip2GlobalRouteChanges

OID (numeric): 1.3.6.1.4.1.3224.18.7.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of route changes made to the IP Route Database by RIP. This does not include the refresh of a route's age.

What is nsVrRip2GlobalRouteChanges?

A running count of route changes RIP has made to this virtual router's IP route database, not counting a route's normal age refresh; a sudden spike can indicate route flapping.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3224.18.7.1.1.1
snmpwalk -v2c -c public <target> NETSCREEN-VR-RIPv2-MIB::nsVrRip2GlobalRouteChanges

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3224.18.7.1.1.1.1
snmpget -v2c -c public <target> NETSCREEN-VR-RIPv2-MIB::nsVrRip2GlobalRouteChanges.1

Start monitoring Juniper (NetScreen) ScreenOS firewall (RIPv2 per virtual router) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NETSCREEN-VR-RIPv2-MIB::nsVrRip2GlobalRouteChanges OID value, configure state conditions and alerts, and monitor any Juniper (NetScreen) ScreenOS firewall (RIPv2 per virtual router) from a single console.

How to Use in IPNetwork Monitor

Select a Juniper (NetScreen) ScreenOS firewall (RIPv2 per virtual router) 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 nsVrRip2GlobalRouteChanges into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of route changes made to the IP Route Database 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 (8 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.3224netscreenNETSCREEN-SMI
1.3.6.1.4.1.3224.18netscreenVRNETSCREEN-SMI
Numeric OIDNameModule
1.3.6.1.4.1.3224.18.7nsVrRip2NETSCREEN-VR-RIPv2-MIB
1.3.6.1.4.1.3224.18.7.1nsVrRip2GlobalsTableNETSCREEN-VR-RIPv2-MIB
1.3.6.1.4.1.3224.18.7.1.1nsVrRip2GlobalsEntryNETSCREEN-VR-RIPv2-MIB
1.3.6.1.4.1.3224.18.7.1.1.1nsVrRip2GlobalRouteChangesNETSCREEN-VR-RIPv2-MIB