CISCO-BUS-MIB

         The MIB module for the management of LANE broadcast and 
unknown servers.
    
Source file
CISCO-BUS-MIB
Last revised
Identity
ciscoBusMIB
Base OID
1.3.6.1.4.1.9.9.40
Imported Objects
CISCO-SMI ciscoMgmt
LAN-EMULATION-CLIENT-MIB AtmLaneAddress
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC DisplayString RowStatus TEXTUAL-CONVENTION (no object page) TimeStamp
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-BUS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-BUS-MIB::ciscoBusMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-BUS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-BUS-MIB::ciscoBusMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (34)
.1.3.6.1.4.1.9.9.40
.1.3.6.1.4.1.9.9.40.1
.1.3.6.1.4.1.9.9.40.1.1
.1.3.6.1.4.1.9.9.40.1.1.1
OctetString
.1.3.6.1.4.1.9.9.40.1.1.1.1
busMaxFrm r/w
Enumeration
.1.3.6.1.4.1.9.9.40.1.1.1.10
secondsInteger32
.1.3.6.1.4.1.9.9.40.1.1.1.11
.1.3.6.1.4.1.9.9.40.1.1.1.12
.1.3.6.1.4.1.9.9.40.1.1.1.13
.1.3.6.1.4.1.9.9.40.1.1.1.14
.1.3.6.1.4.1.9.9.40.1.1.1.15
.1.3.6.1.4.1.9.9.40.1.1.1.16
.1.3.6.1.4.1.9.9.40.1.1.1.17
Enumeration
.1.3.6.1.4.1.9.9.40.1.1.1.18
Enumeration
.1.3.6.1.4.1.9.9.40.1.1.1.19
Integer32
.1.3.6.1.4.1.9.9.40.1.1.1.2
busStatus r/w
.1.3.6.1.4.1.9.9.40.1.1.1.20
.1.3.6.1.4.1.9.9.40.1.1.1.3
OctetString
.1.3.6.1.4.1.9.9.40.1.1.1.4
.1.3.6.1.4.1.9.9.40.1.1.1.5
.1.3.6.1.4.1.9.9.40.1.1.1.6
.1.3.6.1.4.1.9.9.40.1.1.1.7
.1.3.6.1.4.1.9.9.40.1.1.1.8
Enumeration
.1.3.6.1.4.1.9.9.40.1.1.1.9
.1.3.6.1.4.1.9.9.40.1.2
.1.3.6.1.4.1.9.9.40.1.2.1
.1.3.6.1.4.1.9.9.40.1.2.1.1
.1.3.6.1.4.1.9.9.40.1.2.1.2
.1.3.6.1.4.1.9.9.40.1.2.1.3
.1.3.6.1.4.1.9.9.40.1.2.1.4
.1.3.6.1.4.1.9.9.40.1.2.1.5
.1.3.6.1.4.1.9.9.40.2
.1.3.6.1.4.1.9.9.40.2.1
.1.3.6.1.4.1.9.9.40.2.2
Dependencies (9) 5 direct · 4 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (2)
Integer32 range: -1..65535
Integer32 range: -1..255
Conformance Groups (3)
A collection of objects for the managing of BUS operation.
.1.3.6.1.4.1.9.9.40.2.1.1
For those implementations that wish to tie their LE service
components to an aflane_802x ifIndex.
.1.3.6.1.4.1.9.9.40.2.1.2
A collection of objects for the identification of a
BUS's multicast send VCs.
.1.3.6.1.4.1.9.9.40.2.1.3
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.40.2.2.1
The compliance statement for SNMP entities that support
Cisco's BUS MIB.
Required groups
mandatory ciscoBusGroup
optional ciscoBusSubIfGroup The group of objects necessary to allow multiple LANE
components to share a common ifIndex.
Object refinements
ObjectAccessSyntaxDescription
busAtmAddrSpec readonly
Those implementations that do not support separately
configured broadcast/unknown and LAN emulation servers
are not required to provide write access to the
busAtmAddrSpec object.
busAtmAddrMask readonly
Those implementations that do not support separately
configured broadcast/unknown and LAN emulation servers
are not required to provide write access to the
busAtmAddrMask object.
busIfIndex readonly
Those implementations that do not support separately
configured broadcast/unknown and LAN emulation servers
are not required to provide write access to the
busIfIndex object.
busSubIfNum readonly
Those implementations that do not support separately
configured broadcast/unknown and LAN emulation servers
are not required to provide write access to the
busSubIfNum object.
busLanType readonly
Those implementations that do not support separately
configured broadcast/unknown and LAN emulation servers
are not required to provide write access to the
busLanType object.
busMaxFrm readonly
Those implementations that do not support separately
configured broadcast/unknown and LAN emulation servers
are not required to provide write access to the
busMaxFrm object.
busAdminStatus readonly
Those implementations that do not support separately
configured broadcast/unknown and LAN emulation servers
are not required to provide write access to the
busAdminStatus object. The BUS's administrative status
should be controlled via access to the lesAdminStatus.
Refer to CISCO-LES-MIB for details.