CISCO-BSTUN-MIB
AI MIB Summary
The CISCO-BSTUN-MIB manages Cisco router configurations and operational states for Block Serial Tunneling (BSTUN) over IP networks, specifically monitoring global SAP settings, LLC2 keepalive sessions, and the status of serial interfaces, groups, and routes used to tunnel BSC traffic. Key metrics include peer IP addresses, group protocol types, interface-to-group bindings, and per-route packet/byte counters with peer priority and state indicators.
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.
Main OID:
ciscoBstunMIB.1.3.6.1.4.1.9.9.35
52
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
52 total| Object Name |
|---|
ciscoBstunMIBThe 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. MODULE-IDENTITY .1.3.6.1.4.1.9.9.35 |
bstunObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.1 |
bstunGlobal OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.1.1 |
bstunIPAddrThe configured IP address used by the BSTUN component in
this router.ro IpAddress .1.3.6.1.4.1.9.9.35.1.1.1 |
bstunLisnSapThe configured Listening SAP address used by the BSTUN
component when routed via frame-relay local-ack in
this router.ro Integer32 .1.3.6.1.4.1.9.9.35.1.1.2 |
bstunPeerKeepaliveIntervalThe time interval between keepalives in this router.ro Integer32 .1.3.6.1.4.1.9.9.35.1.1.3 |
bstunPeerKeepaliveLimitThe number of keepalives which can be missed in a continuous
interval before session declared down in this router.ro Integer32 .1.3.6.1.4.1.9.9.35.1.1.4 |
bstunGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.1.2 |
bstunGroupTableA table of entries representing BSTUN groups configured on the
router. Each BSTUN-enabled interface is assigned to a BSTUN
group, and packets can only travel between BSTUN-enabled
interfaces in the same group. SEQUENCE OF BstunGroupEntry .1.3.6.1.4.1.9.9.35.1.2.1 |
bstunGroupEntryStatus and parameter values for a group. BstunGroupEntry .1.3.6.1.4.1.9.9.35.1.2.1.1 |
bstunGroupIndexThe configured BSTUN group number. The significance of this
number is that it must match the BSTUN group number configured in
the router at the other end of the BSTUN tunnel. INTEGER .1.3.6.1.4.1.9.9.35.1.2.1.1.1 |
bstunProtocolTypeThe protocol type for this BSTUN group.ro Enumeration .1.3.6.1.4.1.9.9.35.1.2.1.1.2 |
bstunLocalAckIndicates if the BSTUN connection is locally acknowledged.
TRUE-> BSTUN connection is locally acknowledged
FALSE-> BSTUN connection is not locally acknowledgedro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.35.1.2.1.1.3 |
bstunGroupUnroutableTransmitThe number of unroutable frames received
by this group from the remote partner. They
were unroutable because the address was not
recognized; that is there is no bstun route command
configured for this address. This indicates that the
configuration in this router is incompatible with the
peer router.ro Counter32 .1.3.6.1.4.1.9.9.35.1.2.1.1.4 |
bstunGroupUnroutableReceiveCount of frames received from a serial
interface with an unsupported poll address.
Note that there may be several ports configured
within this bstun group; a non-zero value in this
field indicates that a least one of these ports
is receiving frames for which there are no
bstun route commands configured. This indicates that
the configuration in this router is incompatible with
the configuration in at least one of the attached devices.ro Counter32 .1.3.6.1.4.1.9.9.35.1.2.1.1.5 |
bstunPorts OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.1.3 |
bstunPortTableA list of BSTUN-enabled interfaces (ports). SEQUENCE OF BstunPortEntry .1.3.6.1.4.1.9.9.35.1.3.1 |
bstunPortEntryStatus and parameter values for a BSTUN port. BstunPortEntry .1.3.6.1.4.1.9.9.35.1.3.1.1 |
bstunPortGroupNumberThe group number to which the bstun port
belongs. Frames will only be routed to other
ports (on this or another router) in the same
bstun group. This group should match a bstunGroupIndex
in the bstunGroupTable.ro INTEGER .1.3.6.1.4.1.9.9.35.1.3.1.1.1 |
bstunPortDefaultPeerTypeThe type of identification of the remote default partner.
(This is as configured with the 'route all' command.)
If ip then the value is in bstunPortDefaultPeerIP; if serial or
serialDirect then the value is in bstunPortDefaultPeerSerial.ro Enumeration .1.3.6.1.4.1.9.9.35.1.3.1.1.2 |
bstunPortDefaultPeerIPThe ip address of the remote default BSTUN partner,
for unrecognized addresses.
0.0.0.0 if partner address type is not ip.ro IpAddress .1.3.6.1.4.1.9.9.35.1.3.1.1.3 |
bstunPortDefaultPeerSerialIf bstunRouteType is serial then this is the
serial interface index of the point-to-point
link to the remote partner;
if bstunRouteType is serialDirect then the
partner is in the local BSTUN.
if bstunRouteType is ip then this field is
0.ro InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.35.1.3.1.1.4 |
bstunRoutes OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.1.4 |
bstunRouteTableA table containing information about specific poll
addresses. There is one table entry for each
address configured by the BSTUN ROUTE command. SEQUENCE OF BstunRouteEntry .1.3.6.1.4.1.9.9.35.1.4.1 |
bstunRouteEntryThe information regarding a single poll address. BstunRouteEntry .1.3.6.1.4.1.9.9.35.1.4.1.1 |
bstunRouteGroupIndexThe index of the BSTUN Group owning this
station. INTEGER .1.3.6.1.4.1.9.9.35.1.4.1.1.1 |
bstunRouteStationAddressThe poll address of the station. 256 indicates the ALL parameter
on the STUN ROUTE command, which is the route for all
unrecognized addresses. INTEGER .1.3.6.1.4.1.9.9.35.1.4.1.1.2 |
bstunRouteTypeThe type of identification of the remote partner.
If ip then the value is in bstunRouteIP; if serial or
serialDirect then the value is in bstunRouteSerial; if
bip or apip then the value is in bstunRouteIP,
bstunRouteBIPLocalPort and bstunRouteBIPForeignPort.ro Enumeration .1.3.6.1.4.1.9.9.35.1.4.1.1.3 |
bstunRouteIPThe ip address of the remote BSTUN partner.
0.0.0.0 if partner address type is not ip.ro IpAddress .1.3.6.1.4.1.9.9.35.1.4.1.1.4 |
bstunRouteSerialIf bstunRouteType is serial then this is the
serial interface index of the point-to-point
link to the remote partner;
if bstunRouteType is serialDirect then the
partner is in the local BSTUN.
if bstunRouteType is ip then this field is
0.ro InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.35.1.4.1.1.5 |
bstunRoutePriorityThe priority with which this station's traffic will
be routed across the network.ro Enumeration .1.3.6.1.4.1.9.9.35.1.4.1.1.6 |
bstunRoutePeerStateThe state of the peer connection through the
BSTUN tunnel.ro Enumeration .1.3.6.1.4.1.9.9.35.1.4.1.1.7 |
bstunRouteRxPacketsCount of frames received from the serial
interface with this station's address.ro Counter32 .1.3.6.1.4.1.9.9.35.1.4.1.1.8 |
bstunRouteTxPacketsCount of frames transmitted at the serial
interface with this station's address.ro Counter32 .1.3.6.1.4.1.9.9.35.1.4.1.1.9 |
bstunRouteRxBytesCount of bytes received from the serial
interface with this station's address.ro Counter32 .1.3.6.1.4.1.9.9.35.1.4.1.1.10 |
bstunRouteTxBytesCount of bytes transmitted at the serial
interface with this station's address.ro Counter32 .1.3.6.1.4.1.9.9.35.1.4.1.1.11 |
bstunRouteDLCIIf bstunRouteType is serialFrameRelay or serialLLC2
then this is the frame relay dlci circuit used for
the point-to-point link to the remote partner;
if bstunRouteType is ip or serial then this field is
0.ro Integer32 .1.3.6.1.4.1.9.9.35.1.4.1.1.12 |
bstunRouteRSAPIf bstunRouteType is serialLLC2 then this
is the llc2 sap value used for the point-to-point
link to the remote partner;
if bstunRouteType is ip or serial or serialFrameRelay
then this field is 0.ro Integer32 .1.3.6.1.4.1.9.9.35.1.4.1.1.13 |
bstunLLC2PriorityIf bstunRouteType is serialLLC2 then this
is the llc2 priority used for the point-to-point
link to the remote partner;
if bstunRouteType is ip or serial or serialFrameRelay
then this field is 0.ro Integer32 .1.3.6.1.4.1.9.9.35.1.4.1.1.14 |
bstunRouteBIPPassiveSpecifies whether the bip peer will wait for an inbound connection
or actively connect to the remote peer.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.35.1.4.1.1.15 |
bstunRouteBIPLocalPortIf bstunRouteType is bip then this is the local port used when
connecting to the remote peer.ro Integer32 .1.3.6.1.4.1.9.9.35.1.4.1.1.16 |
bstunRouteBIPForeignPortIf bstunRouteType is bip then this is the for port used to
connect to the remote peer.ro Integer32 .1.3.6.1.4.1.9.9.35.1.4.1.1.17 |
bstunRouteBIPDeviceStatusIf bstunRouteType is bip then this indicates the OR bit mask
status of the mapped bisync device:
if no bits are set, indicates that the
bisync device is up and operational.
Bit 0, if set, indicates that the bisync device is
reporting an operation check error.
Bit 2, if set, indicates that the bisync device is
reporting a data check error.
Bit 3, if set, indicates that the bisync device is
reporting an equipment check error.
Bit 4, if set, indicates that the bisync device is
reporting that intervention is required.
Bit 5, if set, indicates that the bisync device is
reporting that a command has been rejected.
Bit 6, if set, indicates that the bisync device is
not responding to polls.
Bit 7, if set, indicates that the bisync device is
now responding to polls and is operational.
Bit 9, if set, indicates that the bisync device is
reporting that is no longer busy.
Bit 10, if set, indicates that the bisync device is
reporting a device unit specify.
Bit 11, if set, indicates that the bisync device is
reporting a busy condition.ro Bits .1.3.6.1.4.1.9.9.35.1.4.1.1.18 |
bstunRouteAPIPHeaderVersionSpecifies the tunneling header format to use for APIP:
v0, if set, indicates a 2 byte encapsulation header.
The length of the header is included in the size of
the sent packet.
v1, if set, indicates a 2 byte encapsulation header.
The length of the header is excluded from the size of
the sent packet.
v2, if set, indicates a 4 byte encapsulation header.
The length of the header is excluded from the size of
the sent packet.ro Enumeration .1.3.6.1.4.1.9.9.35.1.4.1.1.19 |
bstunNotificationPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.2 |
bstunNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.2.0 |
bstunPeerStateChangeNotificationThis notification indicates that the state of a BSTUN route
has transitioned to active (connected) or inactive
(dead or closed). NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.35.2.0.1 |
bstunPeerStateChangeNotification2This notification indicates that the state of a BSTUN route
has transitioned to active (connected) or inactive
(dead or closed). NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.35.2.0.2 |
bstunCUStatusChangeNotificationThis notification is generated when a mapped BIP bisync
device state has changed. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.35.2.0.3 |
bstunMibConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.3 |
bstunMibCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.3.1 |
bstunMibGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.35.3.2 |