ENTERASYS-RIPv2-EXT-MIB

All MIBs › ENTERASYS-RIPv2-EXT-MIB

Organization: Enterasys Networks, Inc.

Last Updated: 2009-02-06

Category: Technology: Routing/L3, Vendor: Enterasys/Cabletron

Description: Enterasys Networks RIPv2 extension MIB providing additional RIP-2 configuration parameters beyond the standard RIPv2-MIB.

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 ENTERASYS-RIPv2-EXT-MIB?

ENTERASYS-RIPv2-EXT-MIB is an Enterasys Networks enterprise MIB that extends the standard RIPv2-MIB with additional configuration parameters for tuning RIP-2 routing protocol behavior on Enterasys switches and routers. It exposes global administrative and operational status for the RIP-2 process, along with timing parameters such as refresh interval, triggered update delays, route check/expiry/flush intervals, and maximum equal-cost multipath hops. Its monitoring value is in routing protocol software status: confirming RIP is administratively and operationally enabled, and that timer values are tuned appropriately, which affects how quickly the device detects and propagates route changes. It explicitly extends the standard IETF RIPv2-MIB and depends on it for base RIP object definitions. It is deployed on Enterasys (later Extreme Networks) routers and Layer 3 switches running RIP-2 in enterprise networks. Engineers can download the ENTERASYS-RIPv2-EXT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ENTERASYS-RIPv2-EXT-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

Enterasys (Extreme Networks) router/Layer 3 switch

Monitoring Examples

An administrator can check etsysRip2ExtAdminStatus against etsysRip2ExtOperStatus to confirm RIP-2 is both enabled and actually running on the device, and review etsysRip2ExtMaxEcmpHops to verify the configured equal-cost path limit matches network design. If routes are converging slowly after a topology change, the admin might inspect etsysRip2ExtTriggeredDelayMin/Max and etsysRip2ExtRouteExpiryInterval to see if timer values are set too conservatively. etsysRip2ExtRouteFlushInterval would be checked to confirm stale routes are being purged from the routing table in a timely manner.

What Can Be Monitored

RIP-2 administrative status
RIP-2 operational status
maximum ECMP hops
route refresh/expiry/flush intervals
triggered update delay timers

Imported Objects

From ENTERASYS-MIB-NAMES

etsysModules

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
etsysRip2ExtMIB	1.3.6.1.4.1.5624.1.2.66			This MIB module defines a portion of the SNMP MIB under the Enterasys Networks enterprise OID pertaining to the RIPv2 configuration This MIB was designed to be used for configuring the RIP-2 protocol parameters.
etsysRip2ExtObjects	1.3.6.1.4.1.5624.1.2.66.1
etsysRip2ExtGlobals	1.3.6.1.4.1.5624.1.2.66.1.1
INT etsysRip2ExtAdminStatus	1.3.6.1.4.1.5624.1.2.66.1.1.1	INTEGER	read-write	The current administrative state of the RIP protocol. Setting this object to adminStatusUp turns on the RIP protocol, while setting it to adminStatusDown turns off the RIP protocol. When the object is set to adminStatusUp, it triggers the RIP process to begin normal operation by populating its routing table and sending/receiving routing updates. Setting this object to adminStatusDown turns off the RIP protocol. This causes the etsysRip2ExtOperStatus object to change its state to operStatusGoingDown. This has the effect of removing all of the RIP routes from the RIB.
INT etsysRip2ExtOperStatus	1.3.6.1.4.1.5624.1.2.66.1.1.2	INTEGER	read-only	The current operational state of the RIP Protocol. Changing the state of the etsysRip2ExtAdminStatus object may effect the state of this object. If etsysRip2ExtAdminStatus is set to adminStatusDown, this object's status is changed to operStatusGoingDown. Once the RIP process has finished cleaning up its routing table and freeing its resources, the status is changed to operStatusDown. If etsysRip2ExtAdminStatus is set to adminStatusUp, this object's status is changed to operStatusGoingUp. After RIP allocates its resources and begins operation, the status of this object changes to operStatusUp. If there are problems acquiring the resources needed to operate the RIP protocol, the status changes to operStatusActFailed.
U32 etsysRip2ExtMaxEcmpHops	1.3.6.1.4.1.5624.1.2.66.1.1.3	Unsigned32	read-write	The maximum number of equal-cost next hops that RIP can program in the Routing Table Manager. Changing this value causes RIP to refresh all of its routes in the Routing Table Manager with the new maximum number of equal-cost next hops.
U32 etsysRip2ExtRefreshInterval	1.3.6.1.4.1.5624.1.2.66.1.1.4	Unsigned32	read-write	The frequency at which RIP sends periodic updates to all of its peers. A change to this value takes effect after the next periodic update is sent.
U32 etsysRip2ExtTriggeredDelayMin	1.3.6.1.4.1.5624.1.2.66.1.1.5	Unsigned32	read-write	The lower bound of the random time period that RIP waits between sending Triggered Updates. A change to this value takes effect after the next Triggered Update is sent. This value MUST be less than etsysRip2ExtTriggeredDelayMax.
U32 etsysRip2ExtTriggeredDelayMax	1.3.6.1.4.1.5624.1.2.66.1.1.6	Unsigned32	read-write	The upper bound of the random time period that RIP waits between sending Triggered Updates. A change to this value takes effect after the next Triggered Update is sent. This value MUST be greater than etsysRip2ExtTriggeredDelayMin.
U32 etsysRip2ExtRouteCheckInterval	1.3.6.1.4.1.5624.1.2.66.1.1.7	Unsigned32	read-write	The frequency with which RIP checks the routing table for expired routes. A change to this value takes effect after the next scheduled route check.
U32 etsysRip2ExtRouteExpiryInterval	1.3.6.1.4.1.5624.1.2.66.1.1.8	Unsigned32	read-write	The period from the point of the last refresh after which a route received from a peer times out and is marked as expired. This period is expressed as a multiple of the etsysRip2ExtRouteCheckInterval. A change to this value takes effect at the next scheduled route check.
U32 etsysRip2ExtRouteFlushInterval	1.3.6.1.4.1.5624.1.2.66.1.1.9	Unsigned32	read-write	The period from the point of route expiry that a route is finally removed from the routing table, also known as the 'garbage collection time'. This period is expressed as a multiple of the etsysRip2ExtRouteCheckInterval. A change to this value takes effect at the next scheduled route check.
etsysRip2ExtConformance	1.3.6.1.4.1.5624.1.2.66.2
etsysRip2ExtGroups	1.3.6.1.4.1.5624.1.2.66.2.1
etsysRip2ExtGlobalGroup	1.3.6.1.4.1.5624.1.2.66.2.1.1			This group defines global controls for Enterasys RIPv2 systems.
etsysRip2ExtCompliances	1.3.6.1.4.1.5624.1.2.66.2.2
etsysRip2ExtCompliance	1.3.6.1.4.1.5624.1.2.66.2.2.1			The compliance statement for devices that support etsysRip2Ext.

RFC description

Extends RIPv2 protocol configuration for Enterasys Networks routers with routing protocol management.

Start monitoring Enterasys Networks router/Layer 3 switch (legacy, later Extreme Networks) (RIP-2 protocol tuning) 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 ENTERASYS-RIPv2-EXT-MIB

What Is ENTERASYS-RIPv2-EXT-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description