IBMBNA-MIB

All MIBs › IBMBNA-MIB

Category: Domain: SNA/Legacy, SNA and Legacy Protocols, Vendor: IBM

Description: IBM MIB covering Boundary Network Access (BNA), used for SNA boundary node management and session statistics.

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 IBMBNA-MIB?

IBMBNA-MIB is an IBM private MIB for Boundary Network Access (BNA), extending the APPN MIB to manage SNA/APPN branch-network-node uplinks, downlinks, and topology for branch-aware APPN nodes. Its data covers local transmission-group tables (destination, transmission-group number, link type) describing branch uplinks/downlinks, plus network-node frame-relay topology tables that record branch-awareness status for nodes in the APPN network. This is a software/protocol topology MIB rather than a hardware-sensor MIB: ibmBnaLocalTgTable reveals the state of branch uplink/downlink transmission groups, and the table being unexpectedly empty on a node is itself a meaningful software-configuration signal that branch network node support is disabled; ibmBnaNnTopologyFRTable/ibmBnaNnNodeFRBranchAwareness lets an operator confirm which nodes in the topology are recognized as branch-aware. It explicitly extends the appnLocalTgTable defined in the base APPN MIB, making that MIB its core dependency. It is deployed on IBM mainframe/AS400-era SNA networking equipment and APPN-capable routers/gateways in legacy IBM networking environments. Engineers can download the IBMBNA-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in IBMBNA-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 SNA/APPN networking equipment (mainframe gateways, APPN-capable routers)

Monitoring Examples

An operator checks ibmBnaLocalTgTable/ibmBnaLocalTgEntry (ibmBnaLocalTgDest, ibmBnaLocalTgNum, ibmBnaLocalTgLinkType) to confirm branch uplink/downlink transmission groups are established with the expected link type, and an unexpectedly empty table indicates branch network node support is disabled on that device. ibmBnaNnTopologyFRTable/ibmBnaNnTopologyFREntry (ibmBnaNnNodeFRFrsn, ibmBnaNnNodeFRName, ibmBnaNnNodeFRBranchAwareness) would be walked to verify which nodes in the topology are recognized as branch-aware, useful when diagnosing an APPN routing/topology inconsistency.

What Can Be Monitored

branch uplink/downlink transmission group status
transmission group link type
APPN topology branch-awareness status
network node frame-relay topology entries

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Gauge
enterprises

From RFC1213-MIB

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
ibm	1.3.6.1.4.1.2
ibmArchitecture	1.3.6.1.4.1.2.5
ibmBna	1.3.6.1.4.1.2.5.21
ibmBnaObjects	1.3.6.1.4.1.2.5.21.1
ibmBnaLocalTgTable	1.3.6.1.4.1.2.5.21.1.1		not-accessible	Table of objects that identify the branch uplinks and downlinks for an APPN node implementing the APPN Branch Network Architecture. This table is effectively an extension to the appnLocalTgTable defined in the APPN MIB (RFC nnnn). If an implementation that supports the architecture has its branch network node support disabled, then this table is empty. Conversely, if a Management Station determines that there are entries present in this table, then by implication the agent where the table resides currently has its branch network node functionality enabled.
ibmBnaLocalTgEntry	1.3.6.1.4.1.2.5.21.1.1.1		not-accessible	This table is indexed by the destination CP name and the TG number.
STR ibmBnaLocalTgDest	1.3.6.1.4.1.2.5.21.1.1.1.1	DisplayString	read-only	Administratively assigned name of the destination node for this TG. This is the fully qualified name of a network node, end node, LEN node, or virtual routing node.
INT ibmBnaLocalTgNum	1.3.6.1.4.1.2.5.21.1.1.1.2	INTEGER	read-only	Number associated with this transmission group.
INT ibmBnaLocalTgLinkType	1.3.6.1.4.1.2.5.21.1.1.1.3	INTEGER	read-only	Branch link type of this TG: other(1) = the agent has determined the TG's branch link type to be a value other than branch uplink or branch downlink. This is the value used for a connection network TG owned by a node that implements the APPN Branch Network Architecture. uplink(2) = the TG is a branch uplink. downlink(3) = the TG is a branch downlink to an end node. downlinkToBranchNetworkNode(4) = the TG is a branch downlink to a cascaded branch network node. unknown(255) = the agent cannot determine the branch link type of the TG.
ibmBnaNnTopologyFRTable	1.3.6.1.4.1.2.5.21.1.2		not-accessible	Table of objects that identify which of the network nodes in an APPN topology subnet support branch awareness. This table is effectively an extension to the appnNnTopologyFRTable defined in the APPN MIB (RFC nnnn).
ibmBnaNnTopologyFREntry	1.3.6.1.4.1.2.5.21.1.2.1		not-accessible	This table is indexed by FRSN and by fully qualified node name.
GAU ibmBnaNnNodeFRFrsn	1.3.6.1.4.1.2.5.21.1.2.1.1	Gauge	read-only	Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last relative time this resource was updated at the agent node.
STR ibmBnaNnNodeFRName	1.3.6.1.4.1.2.5.21.1.2.1.2	DisplayString	read-only	Administratively assigned network name that is locally defined at each network node in the format NetId.CpName.
T/F ibmBnaNnNodeFRBranchAwareness	1.3.6.1.4.1.2.5.21.1.2.1.3	TruthValue	read-only	Indicates whether this node supports branch awareness. This object corresponds to cv4580, byte 8, bit 4.
ibmBnaNnTgTopologyFRTable	1.3.6.1.4.1.2.5.21.1.3		not-accessible	Table of objects that identify which of the TGs owned by network nodes in an APPN topology subnet are branch TGs. This table is effectively an extension to the appnNnTgTopologyFRTable defined in the APPN MIB (RFC nnnn).
ibmBnaNnTgTopologyFREntry	1.3.6.1.4.1.2.5.21.1.3.1		not-accessible	This table is indexed by four columns: FRSN, TG owner fully qualified node name, TG destination fully qualified node name, and TG number.
GAU ibmBnaNnTgFRFrsn	1.3.6.1.4.1.2.5.21.1.3.1.1	Gauge	read-only	Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last time this resource was updated at this node.
STR ibmBnaNnTgFROwner	1.3.6.1.4.1.2.5.21.1.3.1.2	DisplayString	read-only	Administratively assigned name for the originating node for this TG. The format is NetId.CpName and is the same name specified in the node table.
STR ibmBnaNnTgFRDest	1.3.6.1.4.1.2.5.21.1.3.1.3	DisplayString	read-only	Administratively assigned fully qualified network name for the destination node for this TG.
INT ibmBnaNnTgFRNum	1.3.6.1.4.1.2.5.21.1.3.1.4	INTEGER	read-only	Number associated with this transmission group. Range is 0-255.
T/F ibmBnaNnTgFRBranchTg	1.3.6.1.4.1.2.5.21.1.3.1.5	TruthValue	read-only	Indicates whether the transmission group is a branch TG (equivalently, whether the destination of the transmission group is a node supporting the APPN Branch Network Architecture). This object corresponds to cv4680, byte m+1, bit 1.
ibmBnaDirTable	1.3.6.1.4.1.2.5.21.1.4		not-accessible	Table of objects that identify the apparent owning control point for an LU below a node that supports the APPN Branch Network Architecture. This table is effectively an extension to the appnDirTable defined in the APPN MIB (RFC nnnn).
ibmBnaDirEntry	1.3.6.1.4.1.2.5.21.1.4.1		not-accessible	This table is indexed by the LU name.
STR ibmBnaDirLuName	1.3.6.1.4.1.2.5.21.1.4.1.1	DisplayString	read-only	Fully qualified network LU name in the domain of the serving network node. Entries take one of three forms: - Explicit entries do not contain the character ''. - Partial wildcard entries have the form 'ccc', where 'c' represents a character in a legal SNA LuName. - A full wildcard entry consists of the single character '*'.
STR ibmBnaDirApparentLuOwnerName	1.3.6.1.4.1.2.5.21.1.4.1.2	DisplayString	read-only	Fully qualified CP name of the node at which the LU appears to be located. This object and the appnDirLuOwnerName object in the APPN MIB are related as follows: Implementations that support this object save in their directory database information about an LU's owning control point that was communicated in two control vectors: - an Associated Resource Entry (X'3C') CV with resource type X'00F4' (ENCP) - a Real Owning Control Point (X'4A') CV. The X'4A' CV is created by a branch network node to preserve the name of the real owning control point for an LU below the branch network node, before it overwrites this name with its own name in the X'3C' CV. The X'4A' CV is not present for LUs that are not below branch network nodes. If the information a node has about an LU's owning CP came only in a X'3C' CV, then the name from the X'3C' is returned in the appnDirLuOwnerName object, and a null string is returned in this object. If the information a node has about an LU's owning CP came in both X'3C' and X'4A' CVs, then the name from the X'4A' is returned in the appnDirLuOwnerName object, and the name from the X'3C' (which will be the branch network node's name) is returned in this object.
ibmBnaConformance	1.3.6.1.4.1.2.5.21.2
ibmBnaCompliances	1.3.6.1.4.1.2.5.21.2.1
ibmBnaConfGroups	1.3.6.1.4.1.2.5.21.2.2

RFC description

IBM MIB for Boundary Network Access (BNA) providing SNA boundary node management and session statistics.

Start monitoring IBM SNA/APPN networking equipment (Branch Network Architecture topology) 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 IBMBNA-MIB

What Is IBMBNA-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description