BLADETYPE2-NETWORK-MIB :: ripStatInPkts

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBLADETYPE2-NETWORK-MIBripStatInPkts

ripStatInPkts

Module: BLADETYPE2-NETWORK-MIB

OID (symbolic): BLADETYPE2-NETWORK-MIB::ripStatInPkts

OID (numeric): 1.3.6.1.4.1.11.2.3.7.11.33.1.2.3.2.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The total number of good RIP packets recieved.

What is ripStatInPkts?

Reports the cumulative total number of valid RIP packets received by the device. This counter can be used to gauge RIP routing protocol traffic volume inbound.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.3.7.11.33.1.2.3.2.1.1
snmpwalk -v2c -c public <target> BLADETYPE2-NETWORK-MIB::ripStatInPkts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.3.7.11.33.1.2.3.2.1.1.1
snmpget -v2c -c public <target> BLADETYPE2-NETWORK-MIB::ripStatInPkts.1

Start monitoring HP BladeSystem Type 2 embedded network switch modules with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BLADETYPE2-NETWORK-MIB::ripStatInPkts OID value, configure state conditions and alerts, and monitor any HP BladeSystem Type 2 embedded network switch modules from a single console.

How to Use in IPNetwork Monitor

Select an HP BladeSystem Type 2 embedded network switch module 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 ripStatInPkts into the Find box to locate it in the OID tree, then select it and click OK. The total number of good RIP packets recieved. 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 (14 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.11hpCLJ8500-MIB
1.3.6.1.4.1.11.2nmCLJ8500-MIB
1.3.6.1.4.1.11.2.3hpsystemCLJ8500-MIB
1.3.6.1.4.1.11.2.3.7netElementHP-ICF
1.3.6.1.4.1.11.2.3.7.11hpEtherSwitchHP-ICF-OID
1.3.6.1.4.1.11.2.3.7.11.33hpSwitchProliantHP-ICF-OID
1.3.6.1.4.1.11.2.3.7.11.33.1hpSwitchModuleBladetype2HP-SWITCH-PL-MIB
1.3.6.1.4.1.11.2.3.7.11.33.1.2hpSwitchBladeType2_MgmtHP-SWITCH-PL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.11.2.3.7.11.33.1.2.3layer3BLADETYPE2-NETWORK-MIB
1.3.6.1.4.1.11.2.3.7.11.33.1.2.3.2layer3StatsBLADETYPE2-NETWORK-MIB
1.3.6.1.4.1.11.2.3.7.11.33.1.2.3.2.1ripStatsBLADETYPE2-NETWORK-MIB
1.3.6.1.4.1.11.2.3.7.11.33.1.2.3.2.1.1ripStatInPktsBLADETYPE2-NETWORK-MIB