PRVT-ROUTE-MIB

All MIBs › PRVT-ROUTE-MIB

Organization: BATM Advanced Communication

Last Updated: 2009-01-27

Category: Routing

Description: Manages BATM Advanced Communication IP routing table, static route configuration, and route redistribution policy.

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 PRVT-ROUTE-MIB?

PRVT-ROUTE-MIB is a BATM Advanced Communications enterprise MIB that manages IP routing information, exposing both dynamically learned and statically configured routes along with basic redistribution-related route attributes. It provides tables detailing route prefixes, next hops, route types, administrative distance, and flags. Administrators use it to monitor the software-level routing status of the device, including how long a route has been active (uptime) and which interface it egresses through, which helps detect route flapping or unexpected route withdrawal. It complements the standard IETF IP-FORWARD-MIB/ipRouteTable concepts but is a proprietary BATM extension rather than a standards-based module. It is deployed on BATM Advanced Communications routing/switching platforms used in telecom and enterprise WAN environments. Engineers can download the PRVT-ROUTE-MIB file directly to load it into their MIB browser.

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

BATM Advanced Communications router/switch

Monitoring Examples

An admin would poll prvtDynamicRouteTable/prvtDynamicRouteEntry, examining prvtDynamicRoutePrefix, prvtDynamicRouteNextHop, and prvtDynamicRouteIfName to confirm expected routes are present and pointing to the correct next hop and egress interface. A sudden change in prvtDynamicRouteUptime (reset to a low value) or a route disappearing from the table would indicate route flapping or a routing protocol reconvergence event, while prvtDynamicRouteFlags and prvtDynamicRouteType help distinguish static from dynamically learned entries during troubleshooting.

What Can Be Monitored

route prefix and next hop
route type (static/dynamic)
route uptime/age
administrative distance/metrics
egress interface per route
route flags

Imported Objects

From IPV6-TC

Ipv6Address

From PRVT-OSPF-EXTENSION-MIB

routingProtocols

OBJECT-IDENTITY

From SNMPv2-SMI

IpAddress
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
prvtRouteMIB	1.3.6.1.4.1.738.1.6.4.3			Mib containing information about dynamic and configurable routes in the system.
prvtRouteMIBObjects	1.3.6.1.4.1.738.1.6.4.3.1
prvtDynamicRouteTable	1.3.6.1.4.1.738.1.6.4.3.1.1		not-accessible	System dynamic routes.
prvtDynamicRouteEntry	1.3.6.1.4.1.738.1.6.4.3.1.1.1		not-accessible	The conceptual row represents a routing entry.
OCT prvtDynamicRoutePrefix	1.3.6.1.4.1.738.1.6.4.3.1.1.1.1	OCTET STRING	not-accessible	Dynamic route prefix.
IP prvtDynamicRouteNextHop	1.3.6.1.4.1.738.1.6.4.3.1.1.1.2	IpAddress	not-accessible	Dynamic route next hop.
INT prvtDynamicRouteType	1.3.6.1.4.1.738.1.6.4.3.1.1.1.3	INTEGER	not-accessible	Dynamic route type.
U32 prvtDynamicRouteDistance	1.3.6.1.4.1.738.1.6.4.3.1.1.1.4	Unsigned32	not-accessible	Dynamic route distance.
BIT prvtDynamicRouteFlags	1.3.6.1.4.1.738.1.6.4.3.1.1.1.5	Bits	read-only	Dynamic route flags.
INT prvtDynamicRouteNextHopType	1.3.6.1.4.1.738.1.6.4.3.1.1.1.6	INTEGER	read-only	Dynamic route hop type.
BIT prvtDynamicRouteNextHopFlags	1.3.6.1.4.1.738.1.6.4.3.1.1.1.7	Bits	read-only	Dynamic route hop flags.
U32 prvtDynamicRouteMetrics	1.3.6.1.4.1.738.1.6.4.3.1.1.1.8	Unsigned32	read-only	Dynamic route metrics.
OCT prvtDynamicRouteUptime	1.3.6.1.4.1.738.1.6.4.3.1.1.1.9	OCTET STRING	read-only	A length of time. Duration values are in the ISO 8601 duration format, where P represents 'Period', nY represents the number of years, nM the number of months, nD the number of days, T is the date/time separator, nH the number of hours, nM the number of minutes, nS the number of seconds. So P2DT23H32M51S means 'A period of 2 days, 23 hours, 32 minutes, and 51 seconds'. PnYnMnDTnH nMnS (e.g., P2DT23H32M51S) We use the duration data type to convey values like the time left until a listing ends. For ended listings, the time left is PT0S (zero seconds). xs:duration is part of the XML schema namespace defined as: xmlns:xs='http://www.w3.org/2001/XMLSchema'
OCT prvtDynamicRouteIfName	1.3.6.1.4.1.738.1.6.4.3.1.1.1.10	OCTET STRING	read-only	Dynamic route name.
prvtCfgRouteTable	1.3.6.1.4.1.738.1.6.4.3.1.2		not-accessible	Table with configurable routes. To create entry in this table use prvtCfgRouteRowStatus with createAndGo(4) or createAndWait(5). For example static route : static-route 88.65.85.4/32 43.13.15.18 3 will be represented as : prvtCfgRouteRowStatus.88.65.85.4.32.43.13.15.18.3
prvtCfgRouteEntry	1.3.6.1.4.1.738.1.6.4.3.1.2.1		not-accessible	The conceptual row represents a routing entry.
OCT prvtCfgRoutePrefix	1.3.6.1.4.1.738.1.6.4.3.1.2.1.1	OCTET STRING	not-accessible	Route prefix.
IP prvtCfgRouteNextHop	1.3.6.1.4.1.738.1.6.4.3.1.2.1.2	IpAddress	not-accessible	Route next hop.
U32 prvtCfgRouteDistance	1.3.6.1.4.1.738.1.6.4.3.1.2.1.3	Unsigned32	not-accessible	Route distance.
ROW prvtCfgRouteRowStatus	1.3.6.1.4.1.738.1.6.4.3.1.2.1.4	RowStatus	read-create	Create static route.
prvtCfgIPv6RouteTable	1.3.6.1.4.1.738.1.6.4.3.1.3		not-accessible	Table with configurable routes. To create entry in this table use prvtCfgIPv6RouteRowStatus with createAndGo(4) or createAndWait(5). For example static route : router static-ipv6-route ::/0 2001:fd8::7 10 will be represented as : prvtCfgIPv6RouteRowStatus.4.58.58.47.48.32.1.15.216.0.0.0.0.0.0.0.0.0.0.0.7.10 or 1.3.6.1.4.1.738.10.6.4.3.1.3.1.4 --> prvtCfgIPv6RouteRowStatus OID v --> Value --> createAndGo(4) prvtCfgIPv6RouteRowStatus <--\|v : : / 0 2001:0f d8: 00: 00: 00: 00: 00: 07\|10 1.3.6.1.4.1.738.10.6.4.3.1.3.1.4.4.58.58.47.48.32.1.15.216.0.0.0.0.0.0.0.0.0.0.0.7.10
prvtCfgIPv6RouteEntry	1.3.6.1.4.1.738.1.6.4.3.1.3.1		not-accessible	The conceptual row represents a IPv6 routing entry.
OCT prvtCfgIPv6RoutePrefix	1.3.6.1.4.1.738.1.6.4.3.1.3.1.1	OCTET STRING	not-accessible	IPv6 route prefix.
ADR prvtCfgIPv6RouteNextHop	1.3.6.1.4.1.738.1.6.4.3.1.3.1.2	Ipv6Address	not-accessible	IPv6 route next hop.
U32 prvtCfgIPv6RouteDistance	1.3.6.1.4.1.738.1.6.4.3.1.3.1.3	Unsigned32	not-accessible	IPv6 route distance.
ROW prvtCfgIPv6RouteRowStatus	1.3.6.1.4.1.738.1.6.4.3.1.3.1.4	RowStatus	read-create	Create static IPv6 route.
INT prvtGlobalIPv6Forwarding	1.3.6.1.4.1.738.1.6.4.3.1.4	INTEGER	read-write	Configure IPv6 behavior.
T/F prvtGlobalIPv6Disable	1.3.6.1.4.1.738.1.6.4.3.1.5	TruthValue	read-write	Configure IPv6 behavior.

RFC description

Monitors dynamic and configurable routes on BATM Advanced Communication T-Metro switches.

Start monitoring BATM Advanced Communications router/switch (IP routing table) 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 PRVT-ROUTE-MIB

What Is PRVT-ROUTE-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description