Description: This is the Management Information Base (MIB) 
             module for objects used to manage the cisco internal 
             LAN support in Cisco Mainframe Channel Connection 
             (CMCC) environments.

    1) LAN
    2) Adapter 

   The following example configuration of a router that
   shows the entities managed by the CIPLAN MIB.

                                Router A
   -----------------------------------------
   | ------------------------------------- |
   | |                                   | |
   | | -------------------               | |
   | | | Adapter         |      --       | |
   | | | 400000000401    |    /    \     | |
   | | | ADAPNO 0        |---| Ring |    | |
   | | -------------------   |      |----| |
   | | | Adapter         |---| 1000 |    | |
   | | | 400000000402    |    \    /     | |
   | | | ADAPNO 1        |      --       | |
   | | -------------------               | |
   | |                       Token Ring  | |
   | |                       LAN 0       | |
   | |                                   | |
   | |                          --       | |
   | | -------------------    /    \     | |
   | | | Adapter         |---| Ring |    | |
   | | | 400000000401    |   |      |----| |
   | | | ADAPNO 3        |---| 1001 |    | |
   | | -------------------    \    /     | |
   | |                          --       | |
   | |                                   | |
   | |                       Token Ring  | |
   | |                       LAN 1       | |
   | |                                   | |
   | |                                   | |
   | | -------------------               | |
   | | | Adapter         |           |   | |
   | | | 0200000000C1    |---------------| |
   | | | ADAPNO 4        |     |         | |
   | | -------------------               | |
   | |                       Ethernet    | |
   | |                       LAN 0       | |
   | |                                   | |
   | |                                   | |
   | | -------------------      =        | |
   | | | Adapter         |    /   \      | |
   | | | 400000000001    |===|     |=====| |
   | | | ADAPNO 5        |    \   /      | |
   | | -------------------      =        | |
   | |                                   | |
   | |                       FDDI        | |
   | |                       LAN 0       | |
   | |                                   | |
   | |     CMCC CARD 6                   | |
   | ------------------------------------- |
   |                                       |
   -----------------------------------------

 NOTE:  A special ifIndex has been created to address
        internal LAN objects that are on the CMCC card.
        
        Physically the CMCC card would have two ifIndex's
        of type `other` for each CMCC Slot/Daughter Board.
        The additional ifIndex is made looks like the
        physical with the Daughter Board being replaced
        with a simple integer.  For example:
        
        If the CMCC is in slot/bay 6; The first daughter
        board would have the ifIndex of 6/0.  The
        second daughter board would have the ifIndex
        of 6/1.  The internal objects on this CMCC card
        would have the ifIndex of 6/2.
        
        The ifIndex is an INTEGER to which the values will
        be translated to agent specific number by the 
        agent itself.


The first table is the LAN Admin table.
  Each entry created in this table will represent a
  internal CIP LAN that will be used by MAC adapters
  to bridge data to and from the host.
  The indices of the table are:
    * The special ifIndex that addresses the virtual
      objects on a CMCC card
    * The LAN type (token-ring, ethernet, fddi)
    * The unique LAN identifier
      NOTE:  This value is used to uniquely identify
             each and every LAN based on LAN type
             and on a single CMCC card.
  The fields included in this table represent:
    * The LAN type used as on index
    * The unique LAN identifier used as an index
    * The bridging type
    * For Source Route Bridging, the local ring number
    * For Source Route Bridging, the next bridge number
    * For Source Route Bridging, the target ring number
    * For Transparent Bridging, the bridge group
    * The row control variable
  In the example above, four entries would exist.
  The first entry would be:
    - ifIndex is created by the agent
    - LAN type of token ring
    - LAN identifier of 0
    - bridging type of Source Route
    - local ring number 1000
    - next bridge number is unknown
    - target ring number is unknown
    - transparent bridge group has no meaning
  The second entry would be:
    - ifIndex is created by the agent
    - LAN type of token ring
    - LAN identifier of 1
    - bridging type of Source Route
    - local ring number 1001
    - next bridge number is unknown
    - target ring number is unknown
    - transparent bridge group has no meaning
  The third entry would be:
    - ifIndex is created by the agent
    - LAN type of ethernet
    - LAN identifier of 0
    - bridging type of transparent
    - local ring number has no meaning
    - next bridge number has no meaning
    - target ring number has no meaning
    - transparent bridge group is unknown
  The fourth entry would be:
    - ifIndex is created by the agent
    - LAN type of fddi
    - LAN identifier of 0
    - bridging type of transparent
    - local ring number has no meaning
    - next bridge number has no meaning
    - target ring number has no meaning
    - transparent bridge group is unknown

The last table is the CIP LAN Adapter Admin table.
  Each entry created in this table will represent a
  LAN adapter on one of the CMCC internal LAN's
  defined in the first table.
  The indices of the table are:
    * The special ifIndex that addresses the virtual
      objects on a CMCC card
    * The LAN type (token-ring, ethernet, fddi)
    * The unique LAN identifier from the first table
    * The unique Adapter Number for this LAN type
      NOTE:  When multiple LANs of the same type
             exist, this number must be kept unique
             by the agent.  (The LAN type is defined
             by the Virtual LAN Admin table.)
  The fields included in this table represent:
    * The unique Adapter Number for this LAN type
      as defined by the LAN Admin Entry
      corresponding the the first two indices in
      this table
    * The MAC Address for this Adapter;  this
      MAC Address is unique for all Adapters
      define on this LAN, but does not need to be
      unique across LANs for redundancy
    * The Adapter name
    * The row control variable
  In the example above, five entries would exist.
  The first entry would be:
    - ifIndex is created by the agent
    - the LAN type from the first table
    - the LAN identifier from the first table = 0
    - adapter number of 0
    - Mac Address of 400000000401
    - Configured Name
  The second entry would be:
    - ifIndex is created by the agent
    - the LAN type from the first table
    - the LAN identifier from the first table = 0
    - adapter number of 1
    - Mac Address of 400000000402
    - Configured Name
  The first entry would be:
    - ifIndex is created by the agent
    - the LAN type from the first table
    - the LAN identifier from the first table = 1
    - adapter number of 2
    - Mac Address of 400000000401
    - Configured Name
  The first entry would be:
    - ifIndex is created by the agent
    - the LAN type from the first table
    - the LAN identifier from the first table = 0
    - adapter number of 3
    - Mac Address of 0200000000C1
    - Configured Name
  The first entry would be:
    - ifIndex is created by the agent
    - the LAN type from the first table
    - the LAN identifier from the first table = 0
    - adapter number of 4
    - Mac Address of 400000000001
    - Configured Name