This is the MIB module for objects used to manage SDLLC.

Overview of SDLLC conversion MIB


MIB description                        
The SDLLC MIB includes read-only configuration and operational
information on Cisco's implementation of SDLC to LLC2 media
translation.  The following example shows the entities managed
by the SDLLC MIB.


 FEP/ ==  Token == CISCO A == WAN/RSRB == CISCO B == Serial == SDLC  
 Host     Ring                                       line      station

  |=============== LLC2 session ============|=== SDLC session ====|
  
  In this example configuration, CISCO B is performing the SDLLC 
  conversion, and so we query CISCO B for this MIB.
  The SDLC device believes it is talking to the host via a direct
  SDLC session.  The host believes it is talking to the SDLC station on 
  the same token ring.  CISCO A is also unaware of the SDLLC conversion
  going on at CISCO B; it just believes it has an RSRB session with 
  its peer CISCO B to bridge two token ring separated by a WAN.
  So CISCO B is the only agent that can provide the SDLLC conversion
  details.  We can combine this MIB with the CISCO-RSRB-MIB from
  either CISCO A or CISCO B to get a better picture of the network.
  
  This MIB has two tables:  
  
  convSdllcPortTable has an entry for each serial interface for 
  general SDLLC information on an interface, such as administered 
  virtual MAC addresses and virtual ring and bridge numbers.
  This table is indexed by ifIndex.
  
  convSdllcAddrTable has an entry for each serial interface and
  SDLC address pair.  It contains information specific to an SDLC
  address on an interface, such as the partner MAC address, 
  XID value, and address state.  This table is indexed by ifIndex
  and convSdllcAddrSdlcAddr (the address of the SDLC station).

  The above configuration would have a single entry in each table.
  If CISCO B had two serial lines configured for sdllc conversion, 
  there would be two entries per table.  If there
  were only one serial line, but it was multipoint and
  supported two sdlc addresses on the other end of the 
  line, there would be a single entry in convSdllcPortTable, and
  two entries in convSdllcAddrTable.
  
  The MIB provides the following information for convSdllcPortTable:
  
  convSdllcPortVirtMacAddr - The locally administered MAC addressed
    assigned to the serial interface.  Note that this address must
    always end in '00'.  CISCO B replaces the 00 with the sdlc
    address of the serial device.  For a multipoint configuration
    with two SDLC stations the llc2 side will 'see' two token ring 
    stations with unique MAC addresses on the sdlc side.
  convSdllcPortVirtRing - The locally administered token ring number
    assigned to the serial interface.  This gives the serial interface
    a token ring appearance to the llc2 side of the conversion, so
    that it appears that it is a token ring on the other side of
    a bridge.
  convSdllcPortBridge - The bridge number assigned to CISCO B 
  convSdllcPortLlc2Ring - The token ring number on the LLC2 session
    side.  In this case it is the RSRB virtual ring group number
    between CISCO A and CISCO B.  
  convSdllcPortLocalAck - indicates whether local acknowledgement
    of SDLLC sessions is active.        
  convSdllcPortLocalAckState - indicates the state of
   the local acknowledgement session.   
  convSdllcPortMaxLlc2FrameSize - the largest I-frame size that
    can be sent or received on the LLC2 session.

  The MIB provides the following information for convSdllcAddrTable:
  convSdllcAddrSdlcAddr - The address of the SDLC station.
  convSdllcAddrPartnerMacAddr - The MAC address of the FEP, as
    specified with the sdllc partner command.
  convSdllcAddrXID - The IDBLK and IDNUM of the SDLC station;
    these must match the VTAM configured values
  convSdllcAddrState - indicates the state of the SDLLC conversion
  convSdllcAddrMaxSdlcFrameSize - the largest I-frame size that
    can be sent or received on the SDLC session.