CISCO-BBSM-MIB

        This mib is designed to send BBSM specific
notifications.  There are variables that contain detail data
that are bind to a notification. The SNMP Manager that 
receives the notifications should look at the binding 
variables for further details of the notification data.
        
BBSM stands for Building Broadband Service Manager.  It is a 
software-based service platform that enables customers to 
create, market, and operate broadband access services, 
such as high-speed Internet access with plug-and-play, 
multiple authentication and billing options and Web-based 
management, reporting, and configuration.
    
Source file
CISCO-BBSM-MIB
Last revised
Identity
ciscoBbsmMIB
Base OID
1.3.6.1.4.1.9.9.358
Imported Objects
CISCO-SMI ciscoMgmt
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DateAndTime
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-BBSM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-BBSM-MIB::ciscoBbsmMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-BBSM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-BBSM-MIB::ciscoBbsmMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (12)
.1.3.6.1.4.1.9.9.358
.1.3.6.1.4.1.9.9.358.0
.1.3.6.1.4.1.9.9.358.1
.1.3.6.1.4.1.9.9.358.1.1
OctetString
.1.3.6.1.4.1.9.9.358.1.1.1
.1.3.6.1.4.1.9.9.358.1.1.2
.1.3.6.1.4.1.9.9.358.1.1.3
Enumeration
.1.3.6.1.4.1.9.9.358.1.1.4
.1.3.6.1.4.1.9.9.358.1.1.5
.1.3.6.1.4.1.9.9.358.2
.1.3.6.1.4.1.9.9.358.2.1
.1.3.6.1.4.1.9.9.358.2.2
Dependencies (5) 5 direct 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
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-CONFrfc
  4. SNMPv2-TCrfc
  5. SNMP-FRAMEWORK-MIBrfc
  6. CISCO-BBSM-MIBciscoselected
Conformance Groups (2)
A set of objects providing details of a event
to a Cisco agent.
.1.3.6.1.4.1.9.9.358.2.2.1
Set of notifications implemented in this module.
.1.3.6.1.4.1.9.9.358.2.2.2
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.358.2.1.1
The compliance statement for entities which implement
the Cisco BBSM MIB
Required groups
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.9.9.358.0.1
Notification of a BBSM event. The details of the
event is binded in variables listed. These variables
are identical to the same event logged on the Microsoft
Event Viewer.

For example, if BBSM had problem connecting to RADIUS
server and SNMP Service on BBSM is configured to send
notifications, a notification of ciscoBbsmEvent will
be sent and binded variables will have following values
cbbsmEventDescription = 'Failed to connect to RADIUS server
xx.yy.zz.aa'
cbbsmEventSource = 'BBSM_RADIUS'
cbbsmEventID = '1'
cbbsmEventType = 2