ActiveXperts Network Monitor 2019##AdminFavorites

CISCO-BUS-MIB.mib object view, vendor Cisco

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2019 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2019 can import MIB file CISCO-BUS-MIB and use it to monitor vendor specific OID's.

CISCO-BUS-MIB file content

Object view of CISCO-BUS-MIB:

Scalar Object
busEntry .1.3.6.1.4.1.9.9.40.1.1.1
An entry (conceptual row) in the busTable.
busClientEntry .1.3.6.1.4.1.9.9.40.1.2.1
An entry (conceptual) row that denotes a client that is establishing/has established a multicast send VC to the BUS.
Tabular Object
busElanName .1.3.6.1.4.1.9.9.40.1.1.1.1
The ELAN name of the designated bridge.
busIndex .1.3.6.1.4.1.9.9.40.1.1.1.2
A unique identifier for this particular BUS on this ELAN. This value must remain constant while the entry is in existence and during the operation of the agent (i.e. It is allowed to change after reboot). For implementations that do not support more than one BUS entity per ELAN per device, it is sufficient to always report 1 for this object and only to accept the value 1 for row creation.
busAtmAddrSpec .1.3.6.1.4.1.9.9.40.1.1.1.3
The specified ATM address of the BUS on the interface of interest. Note that setting this object will have the side effect of reinitializing the BUS and consequently dropping all clients connected to it. If this object is not specified at row creation time then the BUS will choose a value for itself and attempt to register with the switch with that value. If an address is specified which is not acceptable to the switch then the busOperStatus will remain inactive until an acceptable address is set.
busAtmAddrMask .1.3.6.1.4.1.9.9.40.1.1.1.4
An address mask that when used with the busAtmAddrSpec, specifies the portion of the BUS' ATM address that is desired to be configured. Note that setting this object will result in the reinitialization of the BUS, consequently dropping all clients connected to it. At row creation time this object cannot be set without also supplying a value for the busAtmAddrSpec. If the BUS ATM address is omitted at creation time then this object defaults to the value of all zeros (none of the busAtmAddrSpec value is relevant). If the BUS ATM address is specified at creation time but this object omitted, then this object defaults to the value of all ones (all of the busAtmAddrSpec is relevant).
busAtmAddrActl .1.3.6.1.4.1.9.9.40.1.1.1.5
The resultant ATM address in use by the BUS. This object is a product of the specified ATM address, mask and interaction with the switch via the ILMI.
busIfIndex .1.3.6.1.4.1.9.9.40.1.1.1.6
The interface that a BUS will forward traffic over. The value specified for this object must equate to a value of ifIndex in the ifTable. The interface will be for that particular ATM port (the physical interface, not a logical layer on top of it). This object can only be specified upon row creation and cannot be altered there after.
busSubIfNum .1.3.6.1.4.1.9.9.40.1.1.1.7
Specifies the sub-interface number that the BUS will reside on. This sub-interface may be shared with a LEC or BUS of the same ELAN but is not required to do so. If no value is specified for this object at row creation time, then a sub-interface will be chosen by the agent. This object may only be specified at row creation time and cannot be altered thereafter.
busUpTime .1.3.6.1.4.1.9.9.40.1.1.1.8
The value of sysUpTime when this BUS became enabled.
busLanType .1.3.6.1.4.1.9.9.40.1.1.1.9
The type of legacy LAN that this LES emulates.
busMaxFrm .1.3.6.1.4.1.9.9.40.1.1.1.10
The maximum frame size that the emulated LAN may accept.
busMaxFrmAge .1.3.6.1.4.1.9.9.40.1.1.1.11
The maximum number of seconds a BUS will hold onto a packet for forwarding until it is dropped. Dropping a packet will result in the incrementing of the busFrmTimeOuts counter.
busOutFwdOctets .1.3.6.1.4.1.9.9.40.1.1.1.12
The number of octets that this BUS has forwarded since its initialization.
busOutFwdUcastFrms .1.3.6.1.4.1.9.9.40.1.1.1.13
The number of frames that the BUS has forwarded which were unicast data frames including all control frames (i.e. they were flooded from the client).
busOutFwdNUcastFrms .1.3.6.1.4.1.9.9.40.1.1.1.14
The number of frames that the BUS has forwarded which were multicast frames.
busFrmTimeOuts .1.3.6.1.4.1.9.9.40.1.1.1.15
The number of frames dropped by the BUS due to time out.
busMultiFwdVpi .1.3.6.1.4.1.9.9.40.1.1.1.16
The virtual path identifier for the multicast forward VCC.
busMultiFwdVci .1.3.6.1.4.1.9.9.40.1.1.1.17
The virtual channel identifier for the multicast forward VCC.
busOperStatus .1.3.6.1.4.1.9.9.40.1.1.1.18
This object reflects the actual state of the BUS which may differ from that of the busAdminStatus object. This can occur when the interface ifOperStatus is 'down' but the corresponding busAdminStatus is 'active'.
busAdminStatus .1.3.6.1.4.1.9.9.40.1.1.1.19
The desired state of the designated BUS as prescribed by the operator. The actions of the agent will, if at all possible, eventually result in the desired state being reflected in the busOperStatus.
busStatus .1.3.6.1.4.1.9.9.40.1.1.1.20
The status of the BUS entry. This object cannot be set to active until the busIfIndex object has an appropiate value. Note that implementations that do not support separate LES/BUS entities may refuse row creation in this table. Creation of BUS entities for those implementation is facilitated in the LES MIB.
busClientId .1.3.6.1.4.1.9.9.40.1.2.1.1
A unique identifier for a LEC which is establishing/ has-established a multicast send VC to the BUS. The identifier only persists for as long as the LEC is associated with this particular BUS. If the LEC is dropped and rejoins the ELAN then a new identifier may be attributed to it.
busClientIfIndex .1.3.6.1.4.1.9.9.40.1.2.1.2
The interface of the uni-directional multicast send connection between the LEC and BUS.
busClientMSendVpi .1.3.6.1.4.1.9.9.40.1.2.1.3
The VPI of the uni-directional multicast send connection between the LEC and BUS.
busClientMSendVci .1.3.6.1.4.1.9.9.40.1.2.1.4
The VCI of the uni-directional multicast send connection between the LEC and BUS.
busClientAtmAddress .1.3.6.1.4.1.9.9.40.1.2.1.5
The address associated with the LANE client on the mulicast send VCC.
Table
busTable .1.3.6.1.4.1.9.9.40.1.1
A (conceptual) table representing all the instantiations of BUSs on the designated device. This table may or may not allow the creation of rows depending on whether the LANE service elements allow the separate creation of LES and BUS components. In the event that separate components are not allowed then the MINIMUM-ACCESS detailed in the MODULE-COMPLIANCE should be used by those BUS implementations
busClientTable .1.3.6.1.4.1.9.9.40.1.2
A (conceptual) table listing the clients associated with a BUS. Note that the local or network management will not create or destroy rows in this table but may only inspect what LECs are currently joined with the BUS.
Object Identifier
ciscoBusMIB .1.3.6.1.4.1.9.9.40
The MIB module for the management of LANE broadcast and unknown servers.
ciscoBusMIBObjects .1.3.6.1.4.1.9.9.40.1
ciscoBusMIBConformance .1.3.6.1.4.1.9.9.40.2
ciscoBusMIBGroups .1.3.6.1.4.1.9.9.40.2.1
ciscoBusMIBCompliances .1.3.6.1.4.1.9.9.40.2.2
Group
ciscoBusGroup .1.3.6.1.4.1.9.9.40.2.1.1
A collection of objects for the managing of BUS operation.
ciscoBusSubIfGroup .1.3.6.1.4.1.9.9.40.2.1.2
For those implementations that wish to tie their LE service components to an aflane_802x ifIndex.
ciscoBusClientGroup .1.3.6.1.4.1.9.9.40.2.1.3
A collection of objects for the identification of a BUS's multicast send VCs.