| bscPortRole | .1.3.6.1.4.1.9.9.36.1.1.1.1.1 | 
    
      | 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. | 
    
      | bscPortCodeSet | .1.3.6.1.4.1.9.9.36.1.1.1.1.2 | 
    
      | The code set used for the line controls. | 
    
      | bscPortPause | .1.3.6.1.4.1.9.9.36.1.1.1.1.3 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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. | 
    
      | bscCUAddress | .1.3.6.1.4.1.9.9.36.1.2.1.1.1 | 
    
      | 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 | 
    
      | State of the BSC Control Unit; when active this indicates that
        the remote Control Unit is polling or responding to polls. | 
    
      | bscCUBytesSent | .1.3.6.1.4.1.9.9.36.1.2.1.1.3 | 
    
      | Count of sent bytes (octets).
        Includes all control characters. | 
    
      | bscCUBytesReceived | .1.3.6.1.4.1.9.9.36.1.2.1.1.4 | 
    
      | Count of received bytes (octets).
        Includes all control characters. | 
    
      | bscCUTotalFramesSent | .1.3.6.1.4.1.9.9.36.1.2.1.1.5 | 
    
      | Count of sent frames (blocks).
        Includes all control frames. | 
    
      | bscCUTotalFramesReceived | .1.3.6.1.4.1.9.9.36.1.2.1.1.6 | 
    
      | Count of received frames (blocks).
        Includes all control frames. | 
    
      | bscCUDataFramesSent | .1.3.6.1.4.1.9.9.36.1.2.1.1.7 | 
    
      | Count of sent data frames (blocks). | 
    
      | bscCUDataFramesReceived | .1.3.6.1.4.1.9.9.36.1.2.1.1.8 | 
    
      | Count of received data frames (blocks). | 
    
      | bscCUSoftErrors | .1.3.6.1.4.1.9.9.36.1.2.1.1.9 | 
    
      | 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 | 
    
      | 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 | 
    
      | 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. | 
    
      | bscExtPollAddress | .1.3.6.1.4.1.9.9.36.1.3.1.1.1 | 
    
      | 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 | 
    
      | The select address of the station configured by the
        bsc extended-address command. |