LAN-EMULATION-CLIENT-MIB: View SNMP OID List / Download MIB

This module defines a portion of the management information base (MIB) for managing ATM LAN Emulation Client nodes. It is meant to be used in connection with the AToM MIB and MIB-II / RFC 1573 'ifTable' entries for each LEC / emulated 802.x network interface.

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.

Each table entry contains configuration information for one LAN Emulation Client. Most of the objects are derived from Initial State Parameters in the LAN Emulation specification.

A value which uniquely identifies this conceptual row in the lecConfigTable. If the conceptual row identified by this value of lecIndex is recreated following an agent restart, the same value of lecIndex must be used to identify the recreated row. (However, the Interfaces table index associated with the client may change.)

This object lets network managers create and delete LAN Emulation Clients, on systems that support this optional capability. It does not control Joins and Terminations; they are controlled by 'ifAdminStatus'. However, taking rows out of service will have the side effect of changing their 'ifAdminStatus' values to 'down', thus causing any active emulated LAN connections to be terminated. Within each conceptual lecConfigTable row, objects which are writable may be modified regardless of the value of lecRowStatus. It is not necessary to set a row's status to 'notInService' first. When creating a LAN Emulation Client, it is up to the management station to determine a suitable 'lecIndex'. To facilitate interoperability, agents should not put any restrictions on the 'lecIndex' beyond the obvious ones that it be valid and unused. If you create a LAN Emulation Client via this object, it will initially have 'ifAdminStatus' = 'down' 'ifOperStatus' = 'down' 'lecInterfaceState' = 'initialState'

The entity that configured this entry and is therefore using the resources assigned to it.

Indicates whether this LAN Emulation Client should auto-configure the next time it is (re)started. In automatic(1) mode, a client uses a LAN Emulation Configuration Server to learn the ATM address of its LAN Emulation Server, and to obtain other parameters. lecConfig{ LanType, MaxDataFrameSize, LanName } are used in the Configure request. lecConfigLesAtmAddress is ignored. In manual(2) mode, management tells the client the ATM address of its LAN Emulation Server and the values of other parameters. lecConfig{ LanType, MaxDataFrameSize, LanName } are used in the Join request. lecConfigLesAtmAddress tells the client which LES to call. Enumeration: 'manual': 2, 'automatic': 1.

C2 LAN Type. The data frame format which this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their Configure requests. Manually-configured clients use it in their Join requests. This MIB object will not be overwritten with the new value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead, lecActualLanType will be.

C3 Maximum Data Frame Size. The maximum data frame size which this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their Configure requests. Manually-configured clients use it in their Join requests. This MIB object will not be overwritten with the new value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead, lecActualMaxDataFrameSize will be.

C5 ELAN Name. The ELAN Name this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their Configure requests. Manually-configured clients use it in their Join requests. This MIB object will not be overwritten with the new value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead, lecActualLanName will be.

C9 LE Server ATM Address. The LAN Emulation Server which this client will use the next time it is started in manual configuration mode. When lecConfigMode is 'automatic', there is no need to set this address, and no advantage to doing so. The client will use the LECS to find a LES, putting the auto-configured address in lecActualLesAtmAddress while leaving lecConfigLesAtmAddress alone.

C7 Control Time-out. Time out period used for timing out most request/response control frame interactions, as specified elsewhere [in the LAN Emulation specification]. This time value is expressed in seconds.

C10 Maximum Unknown Frame Count. See the description of lecMaxUnknownFrameTime below.

C11 Maximum Unknown Frame Time. Within the period of time defined by the Maximum Unknown Frame Time, a LE Client will send no more than Maximum Unknown Frame Count frames to the BUS for a given unicast LAN Destination, and it must also initiate the address resolution protocol to resolve that LAN Destination. This time value is expressed in seconds.

C12 VCC Time-out Period. A LE Client SHOULD release any Data Direct VCC that it has not used to transmit or receive any data frames for the length of the VCC Time-out Period. This parameter is only meaningful for SVC Data Direct VCCs. This time value is expressed in seconds. The default value is 20 minutes. A value of 0 seconds means that the timeout period is infinite. Negative values will be rejected by the agent.

C13 Maximum Retry Count. A LE CLient MUST not retry a LE_ARP_REQUEST for a given frame's LAN destination more than Maximum Retry Count times, after the first LE_ARP_REQUEST for that same frame's LAN destination.

C17 Aging Time. The maximum time that a LE Client will maintain an entry in its LE_ARP cache in the absence of a verification of that relationship. This time value is expressed in seconds.

C18 Forward Delay Time. The maximum time that a LE Client will maintain an entry for a non-local MAC address in its LE_ARP cache in the absence of a verification of that relationship, as long as the Topology Change flag C19 is true. lecForwardDelayTime SHOULD BE less than lecAgingTime. When it is not, lecAgingTime governs LE_ARP aging. This time value is expressed in seconds.

C20 Expected LE_ARP Response Time. The maximum time that the LEC expects an LE_ARP_REQUEST/ LE_ARP_RESPONSE cycle to take. Used for retries and verifies. This time value is expressed in seconds.

C21 Flush Time-out. Time limit to wait to receive a LE_FLUSH_RESPONSE after the LE_FLUSH_REQUEST has been sent before taking recovery action. This time value is expressed in seconds.

C22 Path Switching Delay. The time since sending a frame to the BUS after which the LE Client may assume that the frame has been either discarded or delivered to the recipient. May be used to bypass the Flush protocol. This time value is expressed in seconds.

C23 Local Segment ID. The segment ID of the emulated LAN. This is only required for IEEE 802.5 clients that are Source Routing bridges.

C24 Multicast Send VCC Type. Signalling parameter that SHOULD be used by the LE Client when establishing the Multicast Send VCC. This is the method to be used by the LE Client when specifying traffic parameters when it sets up the Multicast Send VCC for this emulated LAN. Enumeration: 'constantBitRate': 3, 'variableBitRate': 2, 'bestEffort': 1.

C25 Multicast Send VCC AvgRate. Signalling parameter that SHOULD be used by the LE Client when establishing the Multicast Send VCC. Forward and Backward Sustained Cell Rate to be requested by LE Client when setting up Multicast Send VCC, if using Variable bit rate codings.

C26 Multicast Send VCC PeakRate. Signalling parameter that SHOULD be used by the LE Client when establishing the Multicast Send VCC. Forward and Backward Peak Cell Rate to be requested by LE Client when setting up the Multicast Send VCC when using either Variable or Constant bit rate codings.

C28 Connection Complete Timer. Optional. In Connection Establishment this is the time period in which data or a READY_IND message is expected from a Calling Party. This time value is expressed in seconds.

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

Each table entry contains information about one LAN Emulation Client.

This object identifies the logical interface number ('ifIndex') assigned to this client, and is used to identify corresponding rows in the Interfaces MIB. Note that re-initialization of the management agent may cause a client's 'lecIfIndex' to change.

C1 LE Client's ATM Addresses. The primary ATM address of this LAN Emulation Client. This address is used to establish the Control Direct and Multicast Send VCCs, and may also be used to set up Data Direct VCCs. A client may have additional ATM addresses for use with Data Direct VCCs. These addresses are readable via the lecAtmAddressTable.

C14 LE Client Identifier. Each LE Client requires a LE Client Identifier (LECID) assigned by the LE Server during the Join phase. The LECID is placed in control requests by the LE Client and MAY be used for echo suppression on multicast data frames sent by that LE Client. This value MUST NOT change without terminating the LE Client and returning to the Initial state. A valid LECID MUST be in the range X'0001' through X'FEFF'. The value of this object is only meaningful for a LEC that is connected to a LES. For a LEC which does not belong to an emulated LAN, the value of this object is defined to be 0.

The current state of the LAN Emulation Client. Note that 'ifOperStatus' is defined to be 'up' when, and only when, 'lecInterfaceState' is 'operational'.

Status code from the last failed Configure response or Join response. Failed responses are those for which the LE_CONFIGURE_RESPONSE / LE_JOIN_RESPONSE frame contains a non-zero code, or fails to arrive within a timeout period. If none of this client's requests have failed, this object has the value 'none'. If the failed response contained a STATUS code that is not defined in the LAN Emulation specification, this object has the value 'undefinedError'. The value 'timeout' is self-explanatory. Other failure codes correspond to those defined in the specification, although they may have different numeric values. Enumeration: 'invalidRequestParameters': 5, 'none': 1, 'leConfigureError': 14, 'insufficientInformation': 15, 'versionNotSupported': 4, 'noConfiguration': 13, 'duplicateLanDestination': 6, 'invalidAtmAddress': 12, 'insufficientResources': 8, 'duplicateAtmAddress': 7, 'timeout': 2, 'undefinedError': 3, 'invalidRequesterId': 10, 'invalidLanDestination': 11, 'accessDenied': 9.

The state this client was in when it updated the 'lecLastFailureRespCode'. If 'lecLastFailureRespCode' is 'none', this object has the value initialState(1).

The LAN Emulation protocol which this client supports, and specifies in its LE_JOIN_REQUESTs.

The LAN Emulation protocol version which this client supports, and specifies in its LE_JOIN_REQUESTs.

C19 Topology Change. Boolean indication that the LE Client is using the Forward Delay Time C18, instead of the Aging Time C17, to age non-local entries in its LE_ARP cache C16. For a client which is not connected to the LES, this object is defined to have the value 'false'.

The ATM address of the LAN Emulation Configuration Server (if known) or the empty string (otherwise).

Indicates whether this LAN Emulation Client used the LAN Emulation Configuration Server, and, if so, what method it used to establish the Configuration Direct VCC. Enumeration: 'didNotUseLecs': 4, 'gotAddressViaIlmi': 1, 'usedWellKnownAddress': 2, 'usedLecsPvc': 3.

C2 LAN Type. The data frame format that this LAN Emulation Client is using right now. This may come from * lecConfigLanType, * the LAN Emulation Configuration Server, or * the LAN Emulation Server This value is related to 'ifMtu' and 'ifType'. See the LEC management specification for more details.

C3 Maximum Data Frame Size. The maximum data frame size that this LAN Emulation client is using right now. This may come from * lecConfigMaxDataFrameSize, * the LAN Emulation Configuration Server, or * the LAN Emulation Server

C5 ELAN Name. The identity of the emulated LAN which this client last joined, or wishes to join. This may come from * lecConfigLanName, * the LAN Emulation Configuration Server, or * the LAN Emulation Server

C9 LE Server ATM Address. The LAN Emulation Server address currently in use or most recently attempted. If no LAN Emulation Server attachment has been tried, this object's value is the zero-length string.

C4 Proxy. Indicates whether this client is acting as a proxy. Proxy clients are allowed to represent unregistered MAC addresses, and receive copies of LE_ARP_REQUEST frames for such addresses.

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

Each row describes one ifIndex --> lecIndex mapping.

The 'lecIndex' of the client which implements the specified interface.

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

Each row in this table contains traffic statistics for one LAN Emulation client.

The number of LE_ARP_REQUESTs sent over the LUNI by this LAN Emulation Client.

The number of LE_ARP_REQUESTs received over the LUNI by this LAN Emulation Client. Requests may arrive on the Control Direct VCC or on the Control Distribute VCC, depending upon how the LES is implemented and the chances it has had for learning. This counter covers both VCCs.

The number of LE_ARP_RESPONSEs sent over the LUNI by this LAN Emulation Client.

The number of LE_ARP_RESPONSEs received over the LUNI by this LAN Emulation Client. This count includes all such replies, whether solicited or not. Replies may arrive on the Control Direct VCC or on the Control Distribute VCC, depending upon how the LES is implemented. This counter covers both VCCs.

The total number of control packets sent by this LAN Emulation Client over the LUNI.

The total number of control packets received by this LAN Emulation Client over the LUNI.

The total number of * outgoing LAN Emulation SVCs which this client tried, but failed, to open; * incoming LAN Emulation SVCs which this client tried, but failed to establish; and * incoming LAN Emulation SVCs which this client rejected for protocol or security reasons.

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

Each row in this table describes the Control VCCs and Multicast VCCs for one LAN Emulation client.

The interface associated with the Configuration Direct VCC. If no Configuration Direct VCC exists, this object has the value 0. Otherwise, the objects ( lecConfigDirectInterface, lecConfigDirectVpi, lecConfigDirectVci ) identify the circuit.

If the Configuration Direct VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Configuration Direct VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The interface associated with the Control Direct VCC. If no Control Direct VCC exists, this object has the value 0. Otherwise, the objects ( lecControlDirectInterface, lecControlDirectVpi, lecControlDirectVci ) identify the circuit.

If the Control Direct VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Control Direct VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The interface associated with the Control Distribute VCC. If no Control Distribute VCC has been set up to this client, this object has the value 0. Otherwise, the objects ( lecControlDistributeInterface, lecControlDistributeVpi, lecControlDistributeVci ) identify the circuit.

If the Control Distribute VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Control Distribute VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object contains the value 0.

The interface associated with the Multicast Send VCC. If no Multicast Send VCC exists, this object has the value 0. Otherwise, the objects ( lecMulticastSendInterface, lecMulticastSendVpi, lecMulticastSendVci ) identify the circuit.

If the Multicast Send VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Multicast Send VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The interface associated with the Multicast Forward VCC. If no Multicast Forward VCC has been set up to this client, this object has the value 0. Otherwise, the objects ( lecMulticastForwardInterface, lecMulticastForwardVpi, lecMulticastForwardVci ) identify the circuit.

If the Multicast Forward VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Multicast Forward VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

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

Each row in this table describes one of a client's ATM addresses.

The ATM address this row describes. This could be either a primary address or a secondary address.

Used to create and delete rows in this table. A management station may not change the status of a primary ATM address to 'notInService' or 'destroy' unless the client's ifAdminStatus is 'down', and the client's lecInterfaceState is 'initialState'. Secondary ATM addresses may be destroyed at any time permitted by the agent.

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.

Each table row describes a (MAC address, ATM address) pair registered for a particular client.

A unicast MAC address which the LE client denoted by 'lecIndex' has registered with its LE Server.

The ATM address registered for 'lecMacAddress'.

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.

Each table row describes a (Route Descriptor, ATM address) pair registered for a particular client.

The LAN ID portion of the IEEE 802.5 route descriptor associated with this conceptual row.

The Bridge Number portion of the IEEE 802.5 route descriptor associated with this conceptual row.

The ATM address registered for the IEEE 802.5 route descriptor ('lecRouteDescrSegmentID', 'lecRouteDescrBridgeNumber').

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.

An ATM LAN Emulation ARP cache entry containing information about the binding of one MAC address to one ATM address.

The MAC address for which this cache entry provides a translation. Since ATM LAN Emulation uses an ARP protocol to locate the Broadcast and Unknown Server, the value of this object could be the broadcast MAC address. MAC addresses should be unique within any given ATM Emulated LAN. However, there's no requirement that they be unique across disjoint emulated LANs.

The ATM address of the Broadcast & Unknown Server or LAN Emulation Client whose MAC address is stored in 'leArpMacAddress'. This value may be determined through the use of the LE_ARP procedure, through source address learning, or through other mechanisms. Some agents may provide write access to this object, as part of their support for 'static' LE_ARP entries. The effect of attempting to write an ATM address to a 'learned' row is explicitly undefined. Agents may disallow the write, accept the write and change the row's type, or even accept the write as-is.

Indicates whether this entry is for a local or remote MAC address. In this context, 'local' means 'a MAC address that is local to the remote client', as opposed to 'one of my addresses'. true(1) The address is believed to be remote - or its local/remote status is unknown. For an entry created via the LE_ARP mechanism, this corresponds to the 'Remote address' flag being set in the LE_ARP_RESPONSE. During Topology Change periods, remote LE_ARP entries generally age out faster than others. Specifically, they are subject to the Forward Delay Time as well as to the Aging Time. false(2) The address is believed to be local - that is to say, registered with the LES by the client whose ATM address is leArpAtmAddress. For an entry created via the LE_ARP mechanism, this corresponds to the 'Remote address' flag being cleared in the LE_ARP_RESPONSE.

Indicates how this LE_ARP table entry was created and whether it is aged.

Lets users create and delete LE_ARP cache entries, on systems that support this capability. Normally clients will maintain their LE_ARP caches automatically. However, managers may occasionally want to create 'static' LE_ARP cache entries. Rules 1. Before a new row can become 'active', values must be supplied for the columnar objects leArpAtmAddress and leArpEntryType. 2. It is not necessary to set leArpRowStatus to 'notInService' in order to modify a writable object in the same conceptual row. 3. LE_ARP entries whose status is 'notReady' or 'notInService' will not be used to translate LAN Destinations to ATM Addresses. However, clients may overwrite such entries with data obtained from other sources. For example, a client which needed to transmit a data frame to a given MAC address (or via a given Route Descriptor) might find that its LE_ARP entry for the LAN Destination is 'notInService' or 'notReady'. The client might then act as if the LAN Destination was unknown - generating a LE_ARP_REQUEST, flooding the data frame to the BUS, and creating a new, 'active' LE_ARP cache entry based on the LE_ARP_RESPONSE.

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.

An ATM LAN Emulation ARP cache entry containing information about the binding of one IEEE 802.5 route descriptor to one ATM address.

The LAN ID portion of the IEEE 802.5 route descriptor associated with this ARP cache entry.

The Bridge Number portion of the IEEE 802.5 route descriptor associated with this ARP cache entry.

The ATM address of the LAN Emulation Client which is associated with the route descriptor ('leRDArpSegmentID', 'leRDArpBridgeNumber'). This value may be determined through the use of the LE_ARP procedure, through source address learning, or through other mechanisms. Some agents may provide write access to this object, as part of their support for 'static' LE_ARP entries. The effect of attempting to write an ATM address to a 'learned' row is explicitly undefined. Agents may disallow the write, accept the write and change the row's type, or even accept the write as-is.

Indicates how this LE_ARP table entry was created and whether it is aged.

Lets users create and delete LE_ARP cache entries, on systems that support this capability. Normally clients will maintain their LE_ARP caches automatically. However, managers may occasionally want to create 'static' LE_ARP cache entries. Rules 1. Before a new row can become 'active', values must be supplied for the columnar objects leRDArpAtmAddress and leRDArpEntryType. 2. It is not necessary to set leRDArpRowStatus to 'notInService' in order to modify a writable object in the same conceptual row. 3. LE_ARP entries whose status is 'notReady' or 'notInService' will not be used to translate LAN Destinations to ATM Addresses. However, clients may overwrite such entries with data obtained from other sources. For example, a client which needed to transmit a data frame to a given MAC address (or via a given Route Descriptor) might find that its LE_ARP entry for the LAN Destination is 'notInService' or 'notReady'. The client might then act as if the LAN Destination was unknown - generating a LE_ARP_REQUEST, flooding the data frame to the BUS, and creating a new, 'active' LE_ARP cache entry based on the LE_ARP_RESPONSE.

A collection of objects used for creating and configuring LAN Emulation Clients.

A collection of objects describing the status and operational parameters of the managed LAN Emulation Clients.

A collection of objects which map a LAN Emulation Client's 'ifIndex' to its 'lecIndex'.

A collection of objects which act as an extension to the lecConfigTable. These objects provide statistics on LAN Emulation control traffic and SVC establishment.

A collection of objects which act as an extension to the lecConfigTable. These objects identify Configuration Direct, Control, and Multicast VCCs for each client, making it easier to locate their entries in the AToM MIB.

A collection of objects which describe all of the ATM addresses belonging to each client.

A collection of objects which describe all of the MAC addresses registered for each client.

A collection of objects which describe all of the Route Descriptors registered for each client.

A collection of objects which describe the MAC- to-ATM address mappings that this LAN Emulation Client has learned.

A collection of objects which describe the IEEE 802.5 Route Descriptor-to-ATM address mappings that this LAN Emulation Client has learned.

The compliance statement for SNMP entities which support ATM LAN Emulation Clients. For a host to conform to this MIB, it must also implement - RFC 1213 - MIB II. - Interfaces table entries for each LE Client, as per the LAN Emulation Client management specification. - The AToM MIB (RFC 1695 - Definitions of Managed Objects for ATM Management), according to the conformance statements defined in that RFC. Optionally, a host may implement - RFC 1573 - Evolution of the Interfaces Group of MIB-II. - The 'ifRcvAddressGroup' from RFC 1573, which provides a way to represent and configure interfaces with multiple addresses. See the LAN Emulation Client management specification for interpretations of RFC 1573 / MIB-II as they apply to LAN Emulation Clients.