CISCO-BSTUN-MIB

        The MIB module for Block Serial Tunneling.
        
Overview of BSTUN MIB
        
MIB description
        
The BSTUN MIB provides the configuration and operational information 
on Cisco's blocked serial tunnelling implementation.  The following 
entities are managed:
 1) Global BSTUN information
 2) BSTUN groups
 3) BSTUN ports
 4) BSTUN routes
        
The following example configuration shows how the BSTUN MIB returns
BSTUN information, from either CISCO A or CISCO B.
        
 HOST == BSC  == Cisco A == IP Network == Cisco B == BSC   == BSC
         line                                        line     device
        
1) The BSTUN global entry identifies the IP address by which the
   router is known to other BSTUN peers, a configurable SAP value
   on which to listen to LLC2 peers, and keepalive values to maintain
   a session between TCP/IP peers.
2) The BSTUN group table identifies the BSTUN group number and protocol
   type that Cisco A and Cisco B use to route BSC traffic over the 
   IP network.  The table contains an entry for each BSTUN group
   defined on the router. (The group number must be the same in Cisco A 
   and Cisco B, for traffic to flow from one router to the other.)
3) The BSTUN port table identifies the serial interface to the BSC 
   line for which the router is doing serial tunnelling.  The MIB also
   identifies the BSTUN group this interface is defined for, and
   identifies the default routing for unrecognized BSC addresses.
   There is a port entry for each BSTUN-enabled interface on the router.
4) The BSTUN route table has an entry for each address defined for
   routing within the BSTUN group, and an entry for the default routing
   if the 'bstun route all' command is configured.  The route entry
   includes identification of the BSTUN peer, priority, state, and 
   packet and byte counters.
                 
                 
    
Source file
CISCO-BSTUN-MIB
Last revised
Identity
ciscoBstunMIB
Base OID
1.3.6.1.4.1.9.9.35
Imported Objects
CISCO-SMI ciscoMgmt
IF-MIB ifIndex InterfaceIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC TruthValue
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-BSTUN-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-BSTUN-MIB::ciscoBstunMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-BSTUN-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-BSTUN-MIB::ciscoBstunMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (49)
.1.3.6.1.4.1.9.9.35
.1.3.6.1.4.1.9.9.35.1
.1.3.6.1.4.1.9.9.35.1.1
.1.3.6.1.4.1.9.9.35.1.1.1
Integer32
.1.3.6.1.4.1.9.9.35.1.1.2
decisecondsInteger32
.1.3.6.1.4.1.9.9.35.1.1.3
Integer32
.1.3.6.1.4.1.9.9.35.1.1.4
.1.3.6.1.4.1.9.9.35.1.2
.1.3.6.1.4.1.9.9.35.1.2.1
.1.3.6.1.4.1.9.9.35.1.2.1.1
Integer32
.1.3.6.1.4.1.9.9.35.1.2.1.1.1
Enumeration
.1.3.6.1.4.1.9.9.35.1.2.1.1.2
.1.3.6.1.4.1.9.9.35.1.2.1.1.3
.1.3.6.1.4.1.9.9.35.1.2.1.1.4
.1.3.6.1.4.1.9.9.35.1.2.1.1.5
.1.3.6.1.4.1.9.9.35.1.3
.1.3.6.1.4.1.9.9.35.1.3.1
.1.3.6.1.4.1.9.9.35.1.3.1.1
Integer32
.1.3.6.1.4.1.9.9.35.1.3.1.1.1
Enumeration
.1.3.6.1.4.1.9.9.35.1.3.1.1.2
.1.3.6.1.4.1.9.9.35.1.3.1.1.3
.1.3.6.1.4.1.9.9.35.1.3.1.1.4
.1.3.6.1.4.1.9.9.35.1.4
.1.3.6.1.4.1.9.9.35.1.4.1
.1.3.6.1.4.1.9.9.35.1.4.1.1
Integer32
.1.3.6.1.4.1.9.9.35.1.4.1.1.1
.1.3.6.1.4.1.9.9.35.1.4.1.1.10
.1.3.6.1.4.1.9.9.35.1.4.1.1.11
Integer32
.1.3.6.1.4.1.9.9.35.1.4.1.1.12
Integer32
.1.3.6.1.4.1.9.9.35.1.4.1.1.13
Integer32
.1.3.6.1.4.1.9.9.35.1.4.1.1.14
.1.3.6.1.4.1.9.9.35.1.4.1.1.15
Integer32
.1.3.6.1.4.1.9.9.35.1.4.1.1.16
Integer32
.1.3.6.1.4.1.9.9.35.1.4.1.1.17
Bits
.1.3.6.1.4.1.9.9.35.1.4.1.1.18
Enumeration
.1.3.6.1.4.1.9.9.35.1.4.1.1.19
Integer32
.1.3.6.1.4.1.9.9.35.1.4.1.1.2
Enumeration
.1.3.6.1.4.1.9.9.35.1.4.1.1.3
.1.3.6.1.4.1.9.9.35.1.4.1.1.4
.1.3.6.1.4.1.9.9.35.1.4.1.1.5
Enumeration
.1.3.6.1.4.1.9.9.35.1.4.1.1.6
Enumeration
.1.3.6.1.4.1.9.9.35.1.4.1.1.7
.1.3.6.1.4.1.9.9.35.1.4.1.1.8
.1.3.6.1.4.1.9.9.35.1.4.1.1.9
.1.3.6.1.4.1.9.9.35.2
.1.3.6.1.4.1.9.9.35.2.0
.1.3.6.1.4.1.9.9.35.3
.1.3.6.1.4.1.9.9.35.3.1
.1.3.6.1.4.1.9.9.35.3.2
Dependencies (7) 5 direct · 2 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
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. CISCO-BSTUN-MIBciscoselected
Conformance Groups (12)
A collection of objects providing global BSTUN information.
.1.3.6.1.4.1.9.9.35.3.2.1
A collection of objects providing information about
BSTUN groups .
.1.3.6.1.4.1.9.9.35.3.2.2
A collection of objects providing information about
BSTUN enabled interfaces.
.1.3.6.1.4.1.9.9.35.3.2.3
A collection of objects providing information about
BSTUN defined routes.
.1.3.6.1.4.1.9.9.35.3.2.4
A collection of objects providing global BSTUN information.
.1.3.6.1.4.1.9.9.35.3.2.5
A collection of objects providing information about
BSTUN defined routes.
.1.3.6.1.4.1.9.9.35.3.2.6
A collection of objects providing information about
BSTUN defined routes.
.1.3.6.1.4.1.9.9.35.3.2.7
A collection of notifications.
.1.3.6.1.4.1.9.9.35.3.2.8
A collection of notifications.
.1.3.6.1.4.1.9.9.35.3.2.9
A objects providing information about
BSTUN defined routes for BIP protocol.
.1.3.6.1.4.1.9.9.35.3.2.10
A objects providing port number informaton information
about BSTUN defined routes for BIP and APIP protocols.
.1.3.6.1.4.1.9.9.35.3.2.11
A objects providing information about
BSTUN defined routes for APIP protocol.
.1.3.6.1.4.1.9.9.35.3.2.12
Compliance Statements (4)

OID .1.3.6.1.4.1.9.9.35.3.1.1
The compliance statement for BSTUN.
Required groups

OID .1.3.6.1.4.1.9.9.35.3.1.2
The compliance statement for all Cisco systems that
implement BSTUN functions.
Required groups

OID .1.3.6.1.4.1.9.9.35.3.1.3
The compliance statement for all Cisco systems that
implement BSTUN functions.
Required groups

OID .1.3.6.1.4.1.9.9.35.3.1.4
The compliance statement for all Cisco systems that
implement BSTUN functions.
Required groups
mandatory bstunGlobalGroupRev1
mandatory bstunGroupGroup
mandatory bstunPortGroup
mandatory bstunRouteGroupRev1
mandatory bstunNotificationGroupRev1
optional bstunRouteBipGroup This group is mandatory when implementing
the bip route type.
optional bstunRoutePortsGroup This group is mandatory when implementing
the bip or apip route types.
optional bstunRouteApipGroup This group is mandatory when implementing
the apip route type.
Notifications / Traps (3)
NameOIDDescription
.1.3.6.1.4.1.9.9.35.2.0.1
This notification indicates that the state of a BSTUN route
has transitioned to active (connected) or inactive
(dead or closed).
.1.3.6.1.4.1.9.9.35.2.0.2
This notification indicates that the state of a BSTUN route
has transitioned to active (connected) or inactive
(dead or closed).
.1.3.6.1.4.1.9.9.35.2.0.3
This notification is generated when a mapped BIP bisync
device state has changed.