BOUNDARY-ACCESSS-NODE-MIB

All MIBs › BOUNDARY-ACCESSS-NODE-MIB

Category: DSL and Broadband, IP and Core Protocols

Description: Manages boundary access node (BAN) configuration for DSL aggregation and subscriber management.

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 BOUNDARY-ACCESSS-NODE-MIB?

BOUNDARY-ACCESSS-NODE-MIB is an IBM-originated SNMP module for managing Boundary Access Node (BAN) functionality, a bridging technique that maps SNA/DLSw-style traffic onto bridged LAN ports for DSL and remote-access aggregation scenarios. It exposes configuration data for each BAN-capable bridge port, including the bridge port, ifIndex, DLCI MAC address, and boundary node ID/type, alongside operational status and frame-level protocol counters. Its monitoring value centers on software/protocol status: ibmBANstatus reports whether a boundary node is operational, while counters such as ibmBANinIFrames, ibmBANinRRs, ibmBANinRNRs, and ibmBANinRejs track information, receiver-ready, receiver-not-ready, and reject frame counts that reveal link-layer congestion or protocol errors. It builds on standard bridge MIB concepts and IBM's SNA/DLSw architecture rather than being a standalone standard. It is typically deployed in legacy IBM SNA-over-bridged-LAN or DSL aggregation environments where boundary nodes translate between SNA end stations and bridged network segments. Engineers can download the BOUNDARY-ACCESSS-NODE-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BOUNDARY-ACCESSS-NODE-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

IBM Boundary Access Node capable bridge/router
DSL aggregation device

Monitoring Examples

An administrator would poll ibmBANTable/ibmBANEntry indexed by ibmBANbridgePort to read ibmBANstatus and compare ibmBANinRejs against ibmBANinIFrames over time; a rising reject count relative to information frames would reveal a degrading SNA link or DLCI mismatch. ibmBANDLCImacAddress and ibmBANboundaryNodeID let an operator correlate a specific boundary node instance with the bridge port and ifIndex it rides on. Sudden drops in ibmBANinRRs versus ibmBANinRNRs can also indicate a downstream device signaling flow-control backpressure.

What Can Be Monitored

boundary node operational status
boundary node type
DLCI MAC address mapping
inbound information frame counts
inbound RR/RNR/reject frame counts

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
enterprises

OIDs

OID symbolic	OID numeric	Type	Access	Description
ibmBANMIB	1.3.6.1.4.1.2.6.119.4.12
ibmBANTable	1.3.6.1.4.1.2.6.119.4.12.1		not-accessible	A table of information related to bridge ports configured for Boundary Access Node capability.
ibmBANEntry	1.3.6.1.4.1.2.6.119.4.12.1.1		not-accessible	Statistics, status and configuration information on a specific Boundary Access Node port.
INT ibmBANbridgePort	1.3.6.1.4.1.2.6.119.4.12.1.1.1	INTEGER	not-accessible	The BAN bridge port number. It is the same value as the bridge MIBs dot1dBasePort.
INT ibmBANifIndex	1.3.6.1.4.1.2.6.119.4.12.1.1.2	INTEGER	read-only	The interface index identifying the physical interface this bridge port is assicated with. It is the same value as mib-2 ifIndex.
OCT ibmBANDLCImacAddress	1.3.6.1.4.1.2.6.119.4.12.1.1.3	OCTET STRING	read-only	The MAC address of the frame relay DLCI.
OCT ibmBANboundaryNodeID	1.3.6.1.4.1.2.6.119.4.12.1.1.4	OCTET STRING	read-only	The boundary node identifier for the SNA node.
INT ibmBANtype	1.3.6.1.4.1.2.6.119.4.12.1.1.5	INTEGER	read-only	An indication whether this port is bridged or DLSw terminated.
INT ibmBANstatus	1.3.6.1.4.1.2.6.119.4.12.1.1.6	INTEGER	read-only	The status of the ban port with the following values: up(1) - FR DLCI up and running as intended down(2) - FR DLCI is not running initFail(3) - A configuration problem exists
CTR ibmBANinIFrames	1.3.6.1.4.1.2.6.119.4.12.1.1.7	Counter	read-only	Count of received I-frames.
CTR ibmBANinRRs	1.3.6.1.4.1.2.6.119.4.12.1.1.8	Counter	read-only	Count of received RRs.
CTR ibmBANinRNRs	1.3.6.1.4.1.2.6.119.4.12.1.1.9	Counter	read-only	Count of received RNRs.
CTR ibmBANinRejs	1.3.6.1.4.1.2.6.119.4.12.1.1.10	Counter	read-only	Count of received frame rejects.
CTR ibmBANinTests	1.3.6.1.4.1.2.6.119.4.12.1.1.11	Counter	read-only	Count of received TESTs.
CTR ibmBANinTestRsps	1.3.6.1.4.1.2.6.119.4.12.1.1.12	Counter	read-only	Count of received TEST responses.
CTR ibmBANinXIDs	1.3.6.1.4.1.2.6.119.4.12.1.1.13	Counter	read-only	Count of received XIDs.
CTR ibmBANinXIDRsps	1.3.6.1.4.1.2.6.119.4.12.1.1.14	Counter	read-only	Count of received XID responses.
CTR ibmBANinSABMEs	1.3.6.1.4.1.2.6.119.4.12.1.1.15	Counter	read-only	Count of received SABMEs.
CTR ibmBANinUAs	1.3.6.1.4.1.2.6.119.4.12.1.1.16	Counter	read-only	Count of received UAs.
CTR ibmBANinDMs	1.3.6.1.4.1.2.6.119.4.12.1.1.17	Counter	read-only	Count of received DMs.
CTR ibmBANinDISCs	1.3.6.1.4.1.2.6.119.4.12.1.1.18	Counter	read-only	Count of received DISCs.
CTR ibmBANinFRMRs	1.3.6.1.4.1.2.6.119.4.12.1.1.19	Counter	read-only	Count of received FRMRs.
CTR ibmBANinOthers	1.3.6.1.4.1.2.6.119.4.12.1.1.20	Counter	read-only	Count of other packets not counted by the other incoming counters.
CTR ibmBANoutIFrames	1.3.6.1.4.1.2.6.119.4.12.1.1.21	Counter	read-only	Count of transmitted I-frames.
CTR ibmBANoutRRs	1.3.6.1.4.1.2.6.119.4.12.1.1.22	Counter	read-only	Count of transmitted RRs.
CTR ibmBANoutRNRs	1.3.6.1.4.1.2.6.119.4.12.1.1.23	Counter	read-only	Count of transmitted RNRs.
CTR ibmBANoutRejs	1.3.6.1.4.1.2.6.119.4.12.1.1.24	Counter	read-only	Count of transmitted frame rejects.
CTR ibmBANoutTests	1.3.6.1.4.1.2.6.119.4.12.1.1.25	Counter	read-only	Count of transmitted TESTs.
CTR ibmBANoutTestRsps	1.3.6.1.4.1.2.6.119.4.12.1.1.26	Counter	read-only	Count of transmitted TEST responses.
CTR ibmBANoutXIDs	1.3.6.1.4.1.2.6.119.4.12.1.1.27	Counter	read-only	Count of transmitted XIDs.
CTR ibmBANoutXIDRsps	1.3.6.1.4.1.2.6.119.4.12.1.1.28	Counter	read-only	Count of transmitted XID responses.
CTR ibmBANoutSABMEs	1.3.6.1.4.1.2.6.119.4.12.1.1.29	Counter	read-only	Count of transmitted SABMEs.
CTR ibmBANoutUAs	1.3.6.1.4.1.2.6.119.4.12.1.1.30	Counter	read-only	Count of transmitted UAs.
CTR ibmBANoutDMs	1.3.6.1.4.1.2.6.119.4.12.1.1.31	Counter	read-only	Count of transmitted DMs.
CTR ibmBANoutDISCs	1.3.6.1.4.1.2.6.119.4.12.1.1.32	Counter	read-only	Count of transmitted DISCs.
CTR ibmBANoutFRMRs	1.3.6.1.4.1.2.6.119.4.12.1.1.33	Counter	read-only	Count of transmitted FRMRs.
CTR ibmBANoutOthers	1.3.6.1.4.1.2.6.119.4.12.1.1.34	Counter	read-only	Count of other packets not counted by the other outgoing counters.

RFC description

Monitors Boundary Access Node port statistics and configuration for IBM bridge devices.

Start monitoring IBM Boundary Access Node bridge/router (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 BOUNDARY-ACCESSS-NODE-MIB

What Is BOUNDARY-ACCESSS-NODE-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description