CISCO-BSC-MIB: View SNMP OID List / Download MIB

VENDOR: CISCO


 Home MIB: CISCO-BSC-MIB
Download as:   
SNMPv2-CONF, IF-MIB, SNMPv2-SMI, CISCO-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 ciscoBscMIB 1.3.6.1.4.1.9.9.36
The MIB module for BSC. Overview of BSC MIB MIB description The BSC MIB provides the configuration and operational information on Cisco's Binary Synchronous Communications implementation. The following entities are managed: 1) BSC ports (serial interfaces) 2) BSC Control Units (stations on a port) The BSC ports are identified by the interface index, and additional information about this interface can be obtained from the Cisco Serial Interface MIB. The BSC Control Units are identified by the Control Unit address; this is the address used by BSTUN to route the BSC traffic - it is therefore equivalent to the bstunRouteStationAddress in the bstunRouteTable MIB.
       bscObjects 1.3.6.1.4.1.9.9.36.1
           bscPorts 1.3.6.1.4.1.9.9.36.1.1
               bscPortTable 1.3.6.1.4.1.9.9.36.1.1.1 no-access
A list of port (serial interfaces) which have been configured to support a BSC BSTUN group.
                   bscPortEntry 1.3.6.1.4.1.9.9.36.1.1.1.1 no-access
Status and parameter values for a port.
                       bscPortRole 1.3.6.1.4.1.9.9.36.1.1.1.1.1 integer read-only
The router's DLC role to the attached node. If the bscPortRole is primary, this implies that the port is connected to a remote secondary device. If the role is generic, this indicates that the port will be running framed bisynchronous frames with an unknown protocol. If this object does not have the value 'contention' then bscPortVirtualAddress will not be instantiated. If this object does not have the value 'dialContention' then bscPortContentionDialTimeout will not be instantiated. Enumeration: 'generic': 5, 'dialContention': 4, 'primary': 1, 'contention': 3, 'secondary': 2.
                       bscPortCodeSet 1.3.6.1.4.1.9.9.36.1.1.1.1.2 integer read-only
The code set used for the line controls. Enumeration: 'ascii': 2, 'ebcdic': 1.
                       bscPortPause 1.3.6.1.4.1.9.9.36.1.1.1.1.3 integer read-only
For primary, it is the minimum time to be taken for a cycle round the active poll table; if this time has not elapsed when the bottom of the poll table is reached, then polling will pause until this timer expires. A value of zero means there will be no pause between cycles round the poll table. For secondary, the pause time out is the delay taken before sending a response to a poll when it has no data frame to send. The units are tenths of a second. The default is 10 (1 second).
                       bscPortServlim 1.3.6.1.4.1.9.9.36.1.1.1.1.4 integer read-only
This parameter is valid for primary only. It is the number of times the active poll table will be cycled before a non-responding control unit will be polled. The default is 3.
                       bscPortPollTimeout 1.3.6.1.4.1.9.9.36.1.1.1.1.5 integer read-only
This parameter is valid for primary only. It is the time that the primary will wait for a response to a poll or select. The units are tenths of a second. The default is 10 (1 second).
                       bscPortRecoveryRetries 1.3.6.1.4.1.9.9.36.1.1.1.1.6 integer read-only
This is the number of times that a recovery sequence will be retried before the connection is considered to have failed. The default is 5.
                       bscPortUnknownControlUnitsReceived 1.3.6.1.4.1.9.9.36.1.1.1.1.7 counter32 read-only
Count of frames received from the serial interface with an unsupported control unit address. If this value is non-zero it indicates a problem in the configuration.
                       bscPortSoftErrors 1.3.6.1.4.1.9.9.36.1.1.1.1.8 counter32 read-only
Count of soft errors; these are errors which have been recovered. This includes CRC errors received, frames which were retransmitted for any reason (NAK received or the wrong ACK received), etc. This count is a measure of the quality of the port/line, but should be considered in relation to the amount of traffic on the port (frames or bytes sent and received). This count includes all control unit soft errors on this port, plus errors which were not for a specific control unit.
                       bscPortHardErrors 1.3.6.1.4.1.9.9.36.1.1.1.1.9 counter32 read-only
Count of hard errors; these are errors which have not been recovered after bscPortRecoveryRetries number of retries, and therefore the connection has been terminated. These errors could be caused by a hardware error in the line or in the remote device; or possibly the bscPortRecoveryRetries value is set too low for the quality of the line. This count includes all control unit hard errors on this port, plus errors which were not for a specific control unit.
                       bscPortProtocolViolations 1.3.6.1.4.1.9.9.36.1.1.1.1.10 counter32 read-only
Count of protocol violations. This counter is incremented when an unexpected BSC Data Link Control character is received from the remote device; that is, the control character is invalid in the current state of the local BSC FSM. This indicates that there is an incompatibility between the two implementations of the BSC protocol. This count includes all control unit protocol violations on this port, plus errors which were not for a specific control unit.
                       bscPortHostTimeout 1.3.6.1.4.1.9.9.36.1.1.1.1.11 integer32 read-only
This parameter is valid for interfaces configured secondary which additionally are running local-acknowledgement. If the configuration does not match the value will be shown as zero. It is the time the interface will wait for a poll from the host before putting the CU on the inactive list. The default is 60 seconds.
                       bscPortSpecPoll 1.3.6.1.4.1.9.9.36.1.1.1.1.12 truthvalue read-only
This parameter is valid for primary, local-acknowledgement interfaces only. It is set to TRUE when the interface is configured to treat specific polls as general polls. If the configuration cannot support this value, it will be set to FALSE. The default is FALSE.
                       bscPortVirtualAddress 1.3.6.1.4.1.9.9.36.1.1.1.1.13 integer32 read-only
This parameter is valid for contention only. It is the address to be used for this interface when the remote peer router is being used as a concentrator. The default is 01.
                       bscPortContentionDialTimeout 1.3.6.1.4.1.9.9.36.1.1.1.1.14 integer32 read-only
This parameter is valid for dialContention only. It is the amount of time an interface can be quiescent before return the interface to the dial-in pool. The default is 5 seconds.
           bscControlUnits 1.3.6.1.4.1.9.9.36.1.2
               bscControlUnitTable 1.3.6.1.4.1.9.9.36.1.2.1 no-access
A table containing information about specific Control Units.
                   bscCUEntry 1.3.6.1.4.1.9.9.36.1.2.1.1 no-access
The information regarding a single Control Unit.
                       bscCUAddress 1.3.6.1.4.1.9.9.36.1.2.1.1.1 integer no-access
This value is the poll address of the BSC Control Unit. This address must be unique within a BSTUN Group.
                       bscCUState 1.3.6.1.4.1.9.9.36.1.2.1.1.2 integer read-only
State of the BSC Control Unit; when active this indicates that the remote Control Unit is polling or responding to polls. Enumeration: 'active': 2, 'inactive': 1.
                       bscCUBytesSent 1.3.6.1.4.1.9.9.36.1.2.1.1.3 counter32 read-only
Count of sent bytes (octets). Includes all control characters.
                       bscCUBytesReceived 1.3.6.1.4.1.9.9.36.1.2.1.1.4 counter32 read-only
Count of received bytes (octets). Includes all control characters.
                       bscCUTotalFramesSent 1.3.6.1.4.1.9.9.36.1.2.1.1.5 counter32 read-only
Count of sent frames (blocks). Includes all control frames.
                       bscCUTotalFramesReceived 1.3.6.1.4.1.9.9.36.1.2.1.1.6 counter32 read-only
Count of received frames (blocks). Includes all control frames.
                       bscCUDataFramesSent 1.3.6.1.4.1.9.9.36.1.2.1.1.7 counter32 read-only
Count of sent data frames (blocks).
                       bscCUDataFramesReceived 1.3.6.1.4.1.9.9.36.1.2.1.1.8 counter32 read-only
Count of received data frames (blocks).
                       bscCUSoftErrors 1.3.6.1.4.1.9.9.36.1.2.1.1.9 counter32 read-only
Count of soft errors; these are errors which have been recovered. This includes CRC errors received, frames which were retransmitted for any reason (NAK received or the wrong ACK received), etc. This count is a measure of the quality of the connection, but should be considered in relation to the amount of traffic on the connection (frames or bytes sent and received).
                       bscCUHardErrors 1.3.6.1.4.1.9.9.36.1.2.1.1.10 counter32 read-only
Count of hard errors; these are errors which have not been recovered after bscPortRecoveryRetries number of retries, and therefore the connection has been terminated. These errors could be caused by a hardware error in the link or in the remote device; or possibly the bscPortRecoveryRetries value is set too low for the quality of the connection.
                       bscCUProtocolViolations 1.3.6.1.4.1.9.9.36.1.2.1.1.11 counter32 read-only
Count of protocol violations. This counter is incremented when an unexpected BSC Data Link Control character is received from the remote device; that is, the control character is invalid in the current state of the local BSC FSM. This indicates that there is an incompatibility between the two implementations of the BSC protocol.
           bscExtAddresses 1.3.6.1.4.1.9.9.36.1.3
               bscExtAddressTable 1.3.6.1.4.1.9.9.36.1.3.1 no-access
List of all addresses configured by the bsc extended-address command. This applies only to interfaces with an ifType of 'bsc'. The address entries must be unique per interface.
                   bscExtAddressEntry 1.3.6.1.4.1.9.9.36.1.3.1.1 no-access
The information regarding a single extended addresses.
                       bscExtPollAddress 1.3.6.1.4.1.9.9.36.1.3.1.1.1 integer32 no-access
The poll address of the station configured by the bsc extended-address command.
                       bscExtSelectAddress 1.3.6.1.4.1.9.9.36.1.3.1.1.2 integer32 read-only
The select address of the station configured by the bsc extended-address command.
       bscMibConformance 1.3.6.1.4.1.9.9.36.3
           bscMibCompliances 1.3.6.1.4.1.9.9.36.3.1
               bscMibCompliance 1.3.6.1.4.1.9.9.36.3.1.1
The compliance statement for BSTUN.
               bscMibComplianceRev1 1.3.6.1.4.1.9.9.36.3.1.2
The compliance statement for all Cisco Systems that implement BSC functions.
           bscMibGroups 1.3.6.1.4.1.9.9.36.3.2
               bscPortsGroup 1.3.6.1.4.1.9.9.36.3.2.1
A collection of objects providing information about BSC enabled interfaces.
               bscControlUnitsGroup 1.3.6.1.4.1.9.9.36.3.2.2
A collection of objects providing information about BSC Control Units .
               bscPortsGroupRev1 1.3.6.1.4.1.9.9.36.3.2.3
A collection of objects providing information about BSC enabled interfaces.
               bscExtAddressGroup 1.3.6.1.4.1.9.9.36.3.2.4
A collection of objects providing information about BSC extended addresses.