BAS-RIPv2-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BAS-RIPv2-MIB

Organization: Broadband Access Systems

Last Updated: 1998-10-07

Category: DOCSIS and Cable, Routing Protocols

Description: Manages RIPv2 routing protocol configuration, authentication, and route statistics on BAS CMTS.

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 BAS-RIPv2-MIB?

BAS-RIPv2-MIB is a vendor MIB for a Broadband Access System (BAS) IP forwarding component, specifically managing RIPv2 routing protocol configuration, authentication settings, and route statistics, and it is noted as used on BAS-based CMTS (cable modem termination system) platforms. Its exposed data centers on RIP global configuration and per-interface RIP parameters within basRip2GlobalsTable/basRip2GlobalEntry, i.e., routing-protocol configuration and state rather than physical hardware sensors. Its monitoring value is confirming the RIPv2 routing process is correctly configured and, implicitly, exchanging routes as expected -- a software/routing-protocol health indicator that affects reachability of subscriber and management networks behind the CMTS. It explicitly depends on the IETF RIPv2 protocol standard (RFC 2453) it manages, and sits under the broader basRipObjects IP-forwarding framework. It is deployed on Broadband Access System CMTS platforms in cable operator head-end networks. Engineers can download the BAS-RIPv2-MIB file directly to load it into their MIB browser.

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

  • Broadband Access System (BAS) CMTS

Monitoring Examples

An operator would poll basRip2GlobalsTable/basRip2GlobalEntry to verify RIPv2 is enabled and authentication is configured as expected on each routed interface of the CMTS. If subscriber routes are missing from the routing table, checking this table's RIP configuration status per interface would confirm whether RIPv2 is actually active and correctly authenticated on the interface facing the affected subnet.

What Can Be Monitored

  • RIPv2 global enable/configuration state
  • RIP authentication settings
  • per-interface RIP configuration
Imported Objects

From BAS-MIB

BasChassisId
BasInterfaceId
BasLogicalPortId
BasSlotId
basAliasRipOBJECT-IDENTITY

From SNMPv2-SMI

Counter32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using basRip2GlobalRouteChanges OID:

Select a Broadband Access Systems (BAS) CMT (legacy) 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 basRip2GlobalRouteChanges 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.
OIDs

RFC description

A Bay Access Server (Bay Networks/Nortel) MIB for RIPv2 routing protocol. Extends RFC 1724 with vendor-specific objects for monitoring and managing RIPv2 on Bay Access Server equipment.

Start monitoring Broadband Access Systems (BAS) CMTS (legacy) 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 BAS-RIPv2-MIB