BNET-ATM-TOPOLOGY-MIB

All MIBs › BNET-ATM-TOPOLOGY-MIB

Category: ATM, IP and Core Protocols

Description: Handles topology discovery and link information for ATM networks on BroadNet ATM equipment.

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 BNET-ATM-TOPOLOGY-MIB?

BNET-ATM-TOPOLOGY-MIB is a vendor MIB (BroadNet/Bnet ATM equipment) for discovering and reporting the topology of ATM (Asynchronous Transfer Mode) links between network elements. It exposes global topology status, revision/version, and a per-link table keyed by slot, port, and logical channel number (LCN) describing each link's topology state and its peer slot. Its monitoring value centers on hardware/link operational status: global operational status of the topology discovery process and per-link topology state reveal whether an ATM link between two switches or nodes is properly discovered and synchronized versus stale or down. It is specific to ATM networking concepts (VPI/VCI, LCN) and typically used alongside standard ATM-MIB interface objects rather than replacing them. Deployment context is legacy carrier or enterprise ATM backbone/access equipment, where operators can download the BNET-ATM-TOPOLOGY-MIB file to verify inter-node link topology for provisioning and fault isolation.

IPNetwork Monitor allows you to monitor SNMP objects defined in BNET-ATM-TOPOLOGY-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

BroadNet ATM switching/access equipment

Monitoring Examples

An admin would poll bnetAtmTopLinksTable/bnetAtmTopLinksEntry indexed by bnetAtmTopLinksSlotNumIndx, bnetAtmTopLinksPortNumIndx, and bnetAtmTopLinksLcnIndx to check bnetAtmTopLinksTopoState and confirm the discovered bnetAtmTopLinksPeerSlotNum matches the expected far-end. A global bnetAtmTopGblOperStatus showing down alongside a stale bnetAtmTopGblLstChg timestamp would indicate topology discovery has stalled. An unexpected change in bnetAtmTopGblCurNum (link count) signals a link was added or dropped from the ATM mesh.

What Can Be Monitored

global ATM topology operational status
per-link topology state
peer slot/port discovery
link count changes
topology last-change timestamp

Imported Objects

From LAN-EMULATION-CLIENT-MIB

VpiInteger

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

IpAddress
TimeTicks

From S5-ROOT-MIB

s5AtmTop

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
bnetAtmTopGbl	1.3.6.1.4.1.45.1.6.14.1
INT bnetAtmTopGblStatus	1.3.6.1.4.1.45.1.6.14.1.1	INTEGER	read-write	Indicates if the agent is participating in ATM topology discovery. The values are: topOn(1)....topology is on topOff(2)...topology is off When the value is topOff(2) the status of bnetAtmTopLinkTable entries is undefined and the topolgy discovery is disabled for the entire device. When the value is topOn(1) the status of the topology discovery of a given port is defined by the bnetAtmTopLinksPeerStatus in the bnetAtmTopLinkTable. The agent must save the setting of this object in nonvolatile memory (i.e., save across reboots).
TIK bnetAtmTopGblLstChg	1.3.6.1.4.1.45.1.6.14.1.2	TimeTicks	read-only	The value of sysUpTime the last time an entry in the bnetAtmTopLinkTable was added, deleted, or modified. If bnetAtmTopLinkTable has not changed since cold/warm start of the agent, then the value is zero.
INT bnetAtmTopGblCurNum	1.3.6.1.4.1.45.1.6.14.1.3	INTEGER	read-only	The current number of entries in the bnetAtmTopLinkTable.
INT bnetAtmTopGblCurMibVer	1.3.6.1.4.1.45.1.6.14.1.4	INTEGER	read-only	The current version of the ATM Topology mib. This object is provided by agent so NMS can distinguish variations in the mib as they occur in the future.
INT bnetAtmTopGblOperStatus	1.3.6.1.4.1.45.1.6.14.1.5	INTEGER	read-only	Indicates if the agent is participating in ATM topology discovery. The values are: topOn(1)....topology is on topOff(2)...topology is off When the value is topOff(2) the status of bnetAtmTopLinkTable entries is undefined and the topolgy discovery is disabled for the entire device. When the value is topOn(1) the status of the topology discovery of a given port is defined by the bnetAtmTopLinksPeerStatus in the bnetAtmTopLinkTable. The agent must save the setting of this object in nonvolatile memory (i.e., save across reboots). When status is topUnavailable(3), this implies that ilmi is not configured on this switch at all.
bnetAtmTopLinks	1.3.6.1.4.1.45.1.6.14.2
bnetAtmTopLinksTable	1.3.6.1.4.1.45.1.6.14.2.1		not-accessible	A table of all physical and virtual links attached to this switch. This table is built by aggregating information from all ILMI or PNNI entities in the switch and adding local port information.
bnetAtmTopLinksEntry	1.3.6.1.4.1.45.1.6.14.2.1.1		not-accessible	A row in the ATM topology table. Entries in the table can not be created or deleted via SNMP.
INT bnetAtmTopLinksSlotNumIndx	1.3.6.1.4.1.45.1.6.14.2.1.1.1	INTEGER	read-only	Our slot number.
INT bnetAtmTopLinksPortNumIndx	1.3.6.1.4.1.45.1.6.14.2.1.1.2	INTEGER	read-only	Our port number.
NUM bnetAtmTopLinksLcnIndx	1.3.6.1.4.1.45.1.6.14.2.1.1.3	VpiInteger	read-only	Logical Channel Number, This will give the VP, when the ILMI entity uses the VP signalling. This allows to have multiple NNI or UNI links on a single port.
INT bnetAtmTopLinksTopoState	1.3.6.1.4.1.45.1.6.14.2.1.1.4	INTEGER	read-only	The current state of link from topology point of view. Possible values: unavailable(1) - third party device or older version of Bay device notParticipating(2) - peer has set TopoOff participating(3) - actively providing topo info.
INT bnetAtmTopLinksPeerSlotNum	1.3.6.1.4.1.45.1.6.14.2.1.1.5	INTEGER	read-only	The peer's slot number.
INT bnetAtmTopLinksPeerPortNum	1.3.6.1.4.1.45.1.6.14.2.1.1.6	INTEGER	read-only	The peer's port number.
IP bnetAtmTopLinksPeerIpAddr	1.3.6.1.4.1.45.1.6.14.2.1.1.7	IpAddress	read-only	The peer's IP address.
INT bnetAtmTopLinksPeerChassisType	1.3.6.1.4.1.45.1.6.14.2.1.1.8	INTEGER	read-only	The chassis type of the device that sent the topology message. This number is the leaf of the s5 ChassisType OID registered in s5reg*.mib.
INT bnetAtmTopLinksPeerChassisSubType	1.3.6.1.4.1.45.1.6.14.2.1.1.9	INTEGER	read-only	Any relavant additional information of the chassis of the peer Bay device. This is an integer field which could be used as backplane type or any information for stackable devices etc.
INT bnetAtmTopLinksEosSize	1.3.6.1.4.1.45.1.6.14.2.2	INTEGER	read-only	The current size of a row in the table bnetAtmTopLinksEosTable. This allows applications to be able to break apart rows in the table.
bnetAtmTopLinksEosTable	1.3.6.1.4.1.45.1.6.14.2.3		not-accessible	A table of encoded octet strings of entries in table bnetAtmTopLinksTable. The number of entries is determined by packing of 'rows' from bnetAtmTopLinksTable.
bnetAtmTopLinksEosEntry	1.3.6.1.4.1.45.1.6.14.2.3.1		not-accessible	A row in the table of encoded octet strings for table bnetAtmTopLinksTable. Instance returned in Response PDU: On GETs: instance specified is the instance returned. On GET-NEXTs: instance returned is the instance of the last record contained in the octet string. Entries in the table can not be created or deleted via SNMP.
OCT bnetAtmTopLinksEos	1.3.6.1.4.1.45.1.6.14.2.3.1.1	OCTET STRING	read-only	An encoded octet string. On reads it contains an integral number of 'rows' from table bnetAtmTopLinksTable. All 'rows' are the same size which is defined by object bnetAtmTopLinksEosSize.

RFC description

Manages ATM network topology discovery and link information for BroadNet ATM equipment.

Start monitoring BroadNet ATM switching equipment 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 BNET-ATM-TOPOLOGY-MIB

What Is BNET-ATM-TOPOLOGY-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description