Defined Values

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.

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.

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).

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.

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.

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.

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.

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.

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).

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.

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.