LAN-EMULATION-CLIENT-MIB Table View

A table describing all of the LAN Emulation Clients
implemented by this host.  Each LE Client has a row
in the MIB-II/RFC 1573 Interfaces table (describing
the emulated packet interface it presents to higher
layers).  Each LE Client also has a row in this and
other LEC MIB tables (describing its interface with
other LAN Emulation components).
This table contains configuration variables.  Three
extension tables contain client status, performance
statistics, and information about control/multicast
VCCs.
Unlike hardware ports, LE Clients can be created by
management.  However, the RFC 1573 Interfaces table
does not directly support row creation.  Therefore,
creating or deleting a row in the lecConfigTable is
defined to have the side effect of creating or
deleting corresponding rows in
          
    -  the MIB-II / RFC 1573 Interfaces table,
    -  the 'lecMappingTable',
    -  the 'lecStatusTable',
    -  the 'lecServerVccTable',
    -  the 'lecStatisticsTable', and
    -  any other dependent tables
New Interfaces table rows for LAN Emulation Clients
always have 'ifAdminStatus' set to 'down'.
          
A Note On Indexing:
-------------------
Most of the tables in this MIB are indexed in whole
or in part by 'lecIndex' - not by 'ifIndex'.
Why is there a separate index?
Traditionally, ifIndex values are chosen by agents,
and are permitted to change across restarts.  Using
ifIndex to index lecConfigTable could complicate
row creation and/or cause interoperability problems
(if each agent had special restrictions on ifIndex).
Having a separate index avoids these problems.

A read-only table containing identification, status,
and operational information about the LAN Emulation
Clients this agent manages.

A table mapping the 'ifIndex' values of 'aflane8023'
and 'aflane8025' interfaces to the 'lecIndex' values
of the corresponding LAN Emulation Clients.

An extension table containing traffic statistics for
all the LAN Emulation Clients this host implements.

A table identifying the Control and Multicast VCCs
for each LAN Emulation Client this host implements.

A table listing all of the ATM addresses belonging
to this host's LAN Emulation Clients.

This table contains entries for all of the registered
MAC addresses belonging to this agent's LE clients.
C6  Local Unicast MAC Address(es).  Each LE Client has
zero or more local unicast MAC addresses.  In an
operational LE Client, every address in this
variable MUST have been registered with the LE
Server.  Two LE CLients joined to the same
emulated LAN MUST NOT have the same local unicast
MAC address.  A LE Client's MAC addresses may
change during normal operations.  When answering
a LE_ARP_REQUEST for any address in this list, the
'Remote Address' bit in the FLAGS field of the
LE_ARP_RESPONSE MUST be clear.

This table lists all of the Route Descriptors which
are registered by this host's LAN Emulation Clients.
C8  Route Descriptor(s).  Route Descriptors exist only
for source-routed IEEE 802.5 LE Clients that are
Source-Route Bridges.  All Route Descriptors in
any given emulated LAN MUST be unique.  A LE
Client MAY have zero or more Route Descriptors
and these Route Descriptors MAY change during
normal operation.  In an operational LE Client,
every Local Route Descriptor in C8 MUST have been
registered with the LE Server.  When answering a
LE_ARP_REQUEST for any address in this list, the
'Remote Address' bit in the FLAGS field of the
LE_ARP_RESPONSE MUST be clear.

This table provides access to an ATM LAN Emulation
Client's MAC-to-ATM ARP cache.  It contains entries
for unicast addresses and for the broadcast address,
but not for multicast MAC addresses.
C16 LE_ARP Cache.  A table of entries, each of which
    establishes a relationship between a LAN
    Destination external to the LE Client and the
    ATM address to which data frames for that LAN
    Destination will be sent.

This table provides access to an ATM LAN Emulation
Client's Route Descriptor-to-ATM ARP cache.
Implementation of this table is optional for hosts
that do not support emulated IEEE 802.5 Token Ring
LANs, and mandatory for hosts which do.
C16 LE_ARP Cache.  A table of entries, each of which
establishes a relationship between a LAN
Destination external to the LE Client and the
ATM address to which data frames for that LAN
Destination will be sent.

A table identifying Multicast Forward VCCs for LAN
Emulation Version 2.0 clients.

This table provides a place for an agent to store
interesting TLVs associated with
          
    o  Registered LAN destinations
          
    o  LE_ARP entries
          
    o  Query results from the LE_ARP response group
          
    o  Initialization / configuration
          
and any other categories the ATM Forum adds.
          
Unless otherwise stated,
          
    o  Entries in this table are completely optional.
          
    o  An implementation may choose to keep only the
       TLVs which are 'interesting' to its designers,
       such as MPOA TLVs in LE_ARP_RESPONSEs.
          
    o  TLVs which already have their own MIB objects
       should not be duplicated here.
          
    o  Where write / create access is allowed, it is
       not mandatory.
          
Implementors should document the specific lecTlvTable
features of their agent.