Home/Catalog/IBMBNA-MIB

IBMBNA-MIB

AI MIB Summary

Standard SNMP MIB module defining data structures for IBMBNA-MIB.

29
Objects
Active
Status
3
Dependencies

Imported Objects

Objects

29 total
Object Name
ibm
OBJECT IDENTIFIER
.1.3.6.1.4.1.2
RFC1155-SMI
Unknown
.1.3.6.1.4.1.2
ibmArchitecture
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.5
ibmBna
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.5.21
ibmBnaObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.5.21.1
ibmBnaLocalTgTableTable 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.
SEQUENCE OF IbmBnaLocalTgEntry
.1.3.6.1.4.1.2.5.21.1.1
ibmBnaLocalTgEntryThis table is indexed by the destination CP name and the TG number.
IbmBnaLocalTgEntry
.1.3.6.1.4.1.2.5.21.1.1.1
ibmBnaLocalTgDestAdministratively 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.ro
DisplayString
.1.3.6.1.4.1.2.5.21.1.1.1.1
ibmBnaLocalTgNumNumber associated with this transmission group.ro
INTEGER
.1.3.6.1.4.1.2.5.21.1.1.1.2
ibmBnaLocalTgLinkTypeBranch 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.ro
Enumeration
.1.3.6.1.4.1.2.5.21.1.1.1.3
ibmBnaNnTopologyFRTableTable 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).
SEQUENCE OF IbmBnaNnTopologyFREntry
.1.3.6.1.4.1.2.5.21.1.2
ibmBnaNnTopologyFREntryThis table is indexed by FRSN and by fully qualified node name.
IbmBnaNnTopologyFREntry
.1.3.6.1.4.1.2.5.21.1.2.1
ibmBnaNnNodeFRFrsnFlow 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.ro
Gauge
.1.3.6.1.4.1.2.5.21.1.2.1.1
ibmBnaNnNodeFRNameAdministratively assigned network name that is locally defined at each network node in the format NetId.CpName.ro
DisplayString
.1.3.6.1.4.1.2.5.21.1.2.1.2
ibmBnaNnNodeFRBranchAwarenessIndicates whether this node supports branch awareness. This object corresponds to cv4580, byte 8, bit 4.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.2.5.21.1.2.1.3
ibmBnaNnTgTopologyFRTableTable 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).
SEQUENCE OF IbmBnaNnTgTopologyFREntry
.1.3.6.1.4.1.2.5.21.1.3
ibmBnaNnTgTopologyFREntryThis table is indexed by four columns: FRSN, TG owner fully qualified node name, TG destination fully qualified node name, and TG number.
IbmBnaNnTgTopologyFREntry
.1.3.6.1.4.1.2.5.21.1.3.1
ibmBnaNnTgFRFrsnFlow 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.ro
Gauge
.1.3.6.1.4.1.2.5.21.1.3.1.1
ibmBnaNnTgFROwnerAdministratively assigned name for the originating node for this TG. The format is NetId.CpName and is the same name specified in the node table.ro
DisplayString
.1.3.6.1.4.1.2.5.21.1.3.1.2
ibmBnaNnTgFRDestAdministratively assigned fully qualified network name for the destination node for this TG.ro
DisplayString
.1.3.6.1.4.1.2.5.21.1.3.1.3
ibmBnaNnTgFRNumNumber associated with this transmission group. Range is 0-255.ro
INTEGER
.1.3.6.1.4.1.2.5.21.1.3.1.4
ibmBnaNnTgFRBranchTgIndicates 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.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.2.5.21.1.3.1.5
ibmBnaDirTableTable 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).
SEQUENCE OF IbmBnaDirEntry
.1.3.6.1.4.1.2.5.21.1.4
ibmBnaDirEntryThis table is indexed by the LU name.
IbmBnaDirEntry
.1.3.6.1.4.1.2.5.21.1.4.1
ibmBnaDirLuNameFully 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 '*'.ro
DisplayString
.1.3.6.1.4.1.2.5.21.1.4.1.1
ibmBnaDirApparentLuOwnerNameFully 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.ro
DisplayString
.1.3.6.1.4.1.2.5.21.1.4.1.2
ibmBnaConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.5.21.2
ibmBnaCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.5.21.2.1
ibmBnaConfGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.5.21.2.2
IBMBNA-MIB - SNMP MIB Reference | MIBs Explorer