BIANCA-BRICK-FR-MIB

All MIBs › BIANCA-BRICK-FR-MIB

Category: Frame Relay

Description: Manages Frame Relay interface configuration and statistics on BIANCA/BRICK routers.

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 BIANCA-BRICK-FR-MIB?

BIANCA-BRICK-FR-MIB is a vendor-specific MIB from BinTec (originally BIANCA/BRICK) that models Frame Relay multiprotocol routing (MPR) virtual interfaces on BIANCA/BRICK routers. Its single table, frMprTable, lets a manager create or delete a virtual routing interface over a Frame Relay DCE connection — each row (frMprIfIndex) maps onto a corresponding entry in the standard ifTable and specifies the interface MTU (frMprMtu, 576-8180), whether it uses the Q.933a/RFC 1490 multiprotocol encapsulation or is being deleted (frMprEncapsulation), whether the interface behaves as multipoint or point-to-point (frMprIfcType), and whether Inverse ARP is enabled to auto-discover upper-layer network addresses (frMprInverseArp). Because a single Frame Relay hardware interface can be split into several virtual routing interfaces (or several physical interfaces combined into one), this MIB's main monitoring value is confirming that the expected virtual interfaces exist, have the correct MTU/encapsulation, and have Inverse ARP set appropriately for the DLCI's use — misconfiguration here typically shows up as IP/IPX routing failures over an otherwise-up Frame Relay circuit. It is deployed on BIANCA/BRICK routers running Frame Relay WAN links, and administrators can perform a BIANCA-BRICK-FR-MIB download to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BIANCA-BRICK-FR-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

BinTec BIANCA/BRICK routers

Monitoring Examples

An operator polls frMprTable to check frMprEncapsulation and frMprInverseArp for a given frMprIfIndex; an encapsulation value of delete or a mismatched frMprIfcType (multipoint vs point-to-point) relative to the DLCI's actual topology would explain why routing protocols aren't establishing adjacency over that Frame Relay circuit.

What Can Be Monitored

Frame Relay virtual routing interface table entries
interface MTU configuration
multiprotocol encapsulation / row creation-deletion state
multipoint vs point-to-point interface type
Inverse ARP enable/disable state

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter

OIDs

OID symbolic	OID numeric	Type	Access	Description
org	1.3
dod	1.3.6
internet	1.3.6.1
private	1.3.6.1.4
enterprises	1.3.6.1.4.1
bintec	1.3.6.1.4.1.272
bibo	1.3.6.1.4.1.272.4
fr	1.3.6.1.4.1.272.4.13
frMprTable	1.3.6.1.4.1.272.4.13.1		not-accessible	This table contains an entry for each frame relay DCE virtual interface. This interface is called virtual because it does not necessarily reflect to a single hardware interface; it is possible to either narrow (many hardware interfaces looking as a single virtual) or widen (a single hardware interface with several VCs is mapped to several virtual interfaces) the interface. Entries in this table are created manually and will result to the creation of a multiprotocol routing interface in the ifTable. This interface can than be used by higher level protocols like ip, ipx and bridging. The object frMprIfIndex shall be set to 0 for creation of new entries. The BRICK will allocate the next free interface index and assign it to frMprIfIndex. Rows of this table can be deleted by setting the object frMprEncapsulation to the value delete.
frMprEntry	1.3.6.1.4.1.272.4.13.1.1		not-accessible
INT frMprIfIndex	1.3.6.1.4.1.272.4.13.1.1.1	INTEGER	read-write	This object contains an interface index and assigns the row to an entry in ifTable. When creating new entries in the table, the value of this object shall be set to 0. The next free ifIndex value is than allocated by the BRICK and assigned to the object. At the same time a new interface is created in the IfTable.
INT frMprMtu	1.3.6.1.4.1.272.4.13.1.1.2	INTEGER	read-write	The Maximum transfer unit to be used with the interface (see also ifMtu).
INT frMprEncapsulation	1.3.6.1.4.1.272.4.13.1.1.3	INTEGER	read-write	This object specifies the encapsulation method to be used. If this object is set to mpr, the encapsulation method described in Q933a is used for the protocols IP, IPX and transparent bridging. This encapsulation is also explained in RFC 1490.
INT frMprIfcType	1.3.6.1.4.1.272.4.13.1.1.4	INTEGER	read-write	This object specifies wether the interface is a multipoint(1) or a point-to-point(2) interface.
INT frMprInverseArp	1.3.6.1.4.1.272.4.13.1.1.5	INTEGER	read-write	This object specifies the use of Inverse Arp (as described in RFC 1490) to automatically detect upper layer network addresses.

RFC description

Manages Frame Relay multiprotocol routing interfaces and virtual interface configuration on Bianca BRICK devices.

Start monitoring bintec BIANCA/BRICK ISDN/VPN routers (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 BIANCA-BRICK-FR-MIB

What Is BIANCA-BRICK-FR-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description