HP-ICF-RIP

All MIBs › HP-ICF-RIP

Organization: HP Networking

Last Updated: 2003-05-13

Category: Routing Protocols, Technology: Routing/L3, Vendor: HP/HPE

Description: HP ICF SNMP MIB for RIP (Routing Information Protocol) configuration and route table management on HP ProCurve Layer 3 switches.

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 HP-ICF-RIP?

HP-ICF-RIP contains Hewlett-Packard's proprietary extensions to the standard RIP MIB, providing additional configuration and status objects for the Routing Information Protocol on HP ProCurve Layer 3 switches. It covers RIP interface configuration (version, timers, redistribution) and route-table/neighbor status rather than hardware sensors. Its monitoring value is protocol/software health — confirming RIP is advertising and receiving routes correctly on expected interfaces, and detecting route flapping or a RIP process that has stopped updating its table. It explicitly extends the standard RFC 1724 RIP-2 MIB, adding HP-specific objects on top of that base model. It is used in smaller enterprise or legacy networks where HP switches still run RIP as an interior routing protocol. Engineers can download the HP-ICF-RIP file directly to load it into their MIB browser.

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

HP ProCurve Layer 3 switch/router

Monitoring Examples

No concrete object names were present in the sampled source beyond the module description, so specifics cannot be confirmed from this MIB alone. In practice such extensions would be polled together with the base RIP-2 MIB's interface and route tables to confirm a switch's RIP process is still exchanging routes and its routing table entries are current rather than stale.

What Can Be Monitored

RIP interface configuration
RIP route table status
RIP timers/redistribution settings

Imported Objects

From HP-ICF-OID

hpSwitch

OBJECT-IDENTITY

From IANA-RTPROTO-MIB

IANAipRouteProtocol

From RIPv2-MIB

rip2IfConfEntry

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
hpicfRip	1.3.6.1.4.1.11.2.14.11.5.1.13			This MIB module contains HP proprietary extensions to the standard RIP MIB.
hpicfRipObjects	1.3.6.1.4.1.11.2.14.11.5.1.13.1
hpicfRipGeneral	1.3.6.1.4.1.11.2.14.11.5.1.13.1.1
INT hpicfRipAdminStatus	1.3.6.1.4.1.11.2.14.11.5.1.13.1.1.1	INTEGER	read-write	The operational status of the RIP routing protocol.
I32 hpicfRipDefaultMetric	1.3.6.1.4.1.11.2.14.11.5.1.13.1.1.2	Integer32	read-write	Default metric value for routes redistributed to RIP.
T/F hpicfRipAutoSummary	1.3.6.1.4.1.11.2.14.11.5.1.13.1.1.3	TruthValue	read-write	A flag indicating whether RIP should perform border filtering on subnet routes when crossing a network boundary. Interfaces that are configured for RIPv1 or RIPv1-compatible mode must always filter subnets at network boundaries. Interfaces configured for RIPv2 mode will only filter subnets if this flag is set to 'true'. Setting this to 'true' will result in all subnets within a class-based network to be summarized using a single route for the subnet number, which can decrease the size of the routing tables. However, if any networks are discontiguous, this flag should be set to 'false' for proper routing.
I32 hpicfRipDistance	1.3.6.1.4.1.11.2.14.11.5.1.13.1.1.4	Integer32	read-write	The administrative distance to associate with routes learned by RIP. Routes with lower distances are preferred. By default, RIP routes have an administrative distance of 120.
hpicfRipIfConfTable	1.3.6.1.4.1.11.2.14.11.5.1.13.1.2		not-accessible	HP extensions to the rip2IfConfTable.
hpicfRipIfConfEntry	1.3.6.1.4.1.11.2.14.11.5.1.13.1.2.1		not-accessible	HP extensions for a single RIP interface.
T/F hpicfRipIfConfDoPoison	1.3.6.1.4.1.11.2.14.11.5.1.13.1.2.1.1	TruthValue	read-create	Flag indicating if router should perform poison reverse on this interface.
I32 hpicfRipIfConfCost	1.3.6.1.4.1.11.2.14.11.5.1.13.1.2.1.2	Integer32	read-create	RIP metric for this interface.
hpicfRipRedistTable	1.3.6.1.4.1.11.2.14.11.5.1.13.1.3		not-accessible	Table for configuring route redistribution into RIP.
hpicfRipRedistEntry	1.3.6.1.4.1.11.2.14.11.5.1.13.1.3.1		not-accessible	An entry in the table for configuring route redistribution into RIP from a single source protocol. Entries in this table are not created dynamically. There will be a single entry for each supported source protocol.
IAN hpicfRipRedistSrcProto	1.3.6.1.4.1.11.2.14.11.5.1.13.1.3.1.1	IANAipRouteProtocol	not-accessible	Source protocol to redistribute routes from.
T/F hpicfRipRedistEnabled	1.3.6.1.4.1.11.2.14.11.5.1.13.1.3.1.2	TruthValue	read-write	A flag indicating whether RIP should redistribute routes from this source protocol.
hpicfRipRedistRestrictTable	1.3.6.1.4.1.11.2.14.11.5.1.13.1.4		not-accessible	A table of route prefixes for filtering out routes that RIP should not redistribute. Any route that is contained by a range in this table (in other words, has a longer mask than that specified by hpicfRipRedistRestrictMask and where the route destination ANDed with the hpicfRipRedistRestrictMask is equal to hpicfRipRedistRestrictAddr) will not be redistributed as an external route by RIP.
hpicfRipRedistRestrictEntry	1.3.6.1.4.1.11.2.14.11.5.1.13.1.4.1		not-accessible	A single entry in the table. Any route, regardless of source protocol which is contained within the specified range will not be redistributed into RIP. Entries in this table are created dynamically using the hpicfRipRedistRestrictStatus object.
IP hpicfRipRedistRestrictAddr	1.3.6.1.4.1.11.2.14.11.5.1.13.1.4.1.1	IpAddress	not-accessible	The IP address of the range of route entries to exclude from redistribution into RIP.
IP hpicfRipRedistRestrictMask	1.3.6.1.4.1.11.2.14.11.5.1.13.1.4.1.2	IpAddress	not-accessible	The mask for the range of route entries to exclude from redistribution into RIP.
ROW hpicfRipRedistRestrictStatus	1.3.6.1.4.1.11.2.14.11.5.1.13.1.4.1.3	RowStatus	read-create	The status of this entry.
hpicfRipConformance	1.3.6.1.4.1.11.2.14.11.5.1.13.2
hpicfRipGroups	1.3.6.1.4.1.11.2.14.11.5.1.13.2.1
hpicfRipBaseGroup	1.3.6.1.4.1.11.2.14.11.5.1.13.2.1.1			Basic RIP configuration information that is not present in the standard RIP MIB.
hpicfRipIfGroup	1.3.6.1.4.1.11.2.14.11.5.1.13.2.1.2			RIP interface configuration information that is not present in the standard RIP MIB.
hpicfRipRedistGroup	1.3.6.1.4.1.11.2.14.11.5.1.13.2.1.3			A collection of objects for controlling the redistribution of external routes by RIP.
hpicfRipDistanceGroup	1.3.6.1.4.1.11.2.14.11.5.1.13.2.1.4			A collection of objects for configuring the administrative distance of routes learned by RIP.
hpicfRipCompliances	1.3.6.1.4.1.11.2.14.11.5.1.13.2.2
hpicfRipCompliance	1.3.6.1.4.1.11.2.14.11.5.1.13.2.2.1			The compliance statement for HP Routing switches that support RIP.
hpicfRipDistanceCompliance	1.3.6.1.4.1.11.2.14.11.5.1.13.2.2.2			The compliance statement for HP Routing switches that support RIP.

RFC description

HP proprietary extensions to RIPv1/RIPv2 routing protocol, including administrative distance, auto-summarization, and default metric configuration.

Start monitoring HP ProCurve Layer 3 switch/router (RIP extensions) 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 HP-ICF-RIP

What Is HP-ICF-RIP?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description