LAN-EMULATION-CLIENT-MIB

File: LAN-EMULATION-CLIENT-MIB.mib (118900 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC SNMPv2-CONF
RFC1213-MIB

Imported symbols

MODULE-IDENTITY OBJECT-TYPE enterprises
Counter32 Integer32 TEXTUAL-CONVENTION
MacAddress RowStatus TruthValue
DisplayString MODULE-COMPLIANCE OBJECT-GROUP
ifIndex

Defined Types

OwnerString  
DisplayString    

AtmLaneAddress  
A twenty-octet binary string, containing a standard ATM Forum address -- or the zero-length string, indicating the absence of an address. For LAN Emulation purposes, the eight-octet address format is not used.
TEXTUAL-CONVENTION    
  OCTET STRING Size(0|20)  

VpiInteger  
An integer large enough to hold a VPI.
TEXTUAL-CONVENTION    
  INTEGER 0..255  

VciInteger  
An integer large enough to hold a VCI.
TEXTUAL-CONVENTION    
  INTEGER 0..65535  

LeConnectionInterface  
A combination flag and ifTable index, indicating whether a LAN Emulation circuit exists - and, if so, which interface is associated with it at the point where it connects to a LE Client. Objects of this type are always defined as part of a set that includes fooInterface LeConnectionInterface fooVpi VpiInteger fooVci VciInteger The interpretation of these objects is as follows. 1. If no connection exists, 'fooInterface' has a value of 0. Because Interfaces table entries always have 'ifIndex' values larger than 0, 'fooInterface' reliably serves as a 'connection exists' flag. In this case, 'fooVpi' and 'fooVci' are meaningless, and have the value 0. 2. If a PVC or SVC exists, 'fooInterface' is defined to have the value of the MIB-II/RFC 1573 'ifIndex' of the 'atm' interface associated with the VCC. 'fooVpi' and 'fooVci' will contain its VPI/VCI. Therefore, ('fooInterface', 'fooVpi', 'fooVci') give you an index into the AToM MIB which allows you to examine and play with the circuit further. 3. If a proprietary connection (such as an internal data path between co-located components) exists, this specification does not mandate how it should be managed. One option is to set 'fooInterface' to the value of the MIB-II/RFC 1573 'ifIndex' for the LAN Emulation Client. This indicates that a connection exists, but is not being managed in the same fashion as an ATM VCC.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

LecState  
An official protocol state of a LAN Emulation Client.
TEXTUAL-CONVENTION    
  INTEGER initialState(1), lecsConnect(2), configure(3), join(4), initialRegistration(5), busConnect(6), operational(7)  

LecDataFrameFormat  
A 'LAN Type' value. C2 LAN Type. The type of LAN that the LE Client is, or wishes to become, a member of. This MUST be one of Ethernet/IEEE 802.3, IEEE 802.5, or Unspecified.
TEXTUAL-CONVENTION    
  INTEGER unspecified(1), aflane8023(2), aflane8025(3)  

LecDataFrameSize  
A 'Maximum Data Frame Size' value. C3 Maximum Data Frame Size. The maximum AAL-5 SDU size of a data frame that the LE Client wishes to send on the Multicast Send VCC or to receive on the Multicast Send VCC or Multicast Forward VCC. This parameter also specifies the maximum AAL-5 SDU on all of a LE Client's Data Direct VCCs. This MUST be either 1516, 4544, 9234, or 18190 octets, or Unspecified.
TEXTUAL-CONVENTION    
  INTEGER unspecified(1), max1516(2), max4544(3), max9234(4), max18190(5)  

LeArpTableEntryType  
Indicates how a LE_ARP table entry was created and whether it is subject to aging. other(1) The LE_ARP entry does not fall into one of the categories defined below. learnedViaControl(2) This LE_ARP entry was learned by using the LE_ARP_REQUEST / LE_ARP_RESPONSE protocol, or by otherwise observing relevant traffic on Control VCCs. Entries of this type are aged. learnedViaData(3) This LE_ARP entry was learned by observing incoming traffic on Data VCCs. Entries of this type are aged. staticVolatile(4) This LE_ARP entry was created by management. It will not be aged. On the other hand, it will not survive a restart of the client. If an agent permits LE_ARP entries of this type to be created, it may require that the LAN Emulation Client be in the 'operational' state at the time. staticNonVolatile(5) This LE_ARP entry was created by management. It will not be aged, and it will survive a restart of the client. The values 'learnedViaData' and 'learnedViaControl' can be read, but may not be written.
TEXTUAL-CONVENTION    
  INTEGER other(1), learnedViaControl(2), learnedViaData(3), staticVolatile(4), staticNonVolatile(5)  

LecConfigEntry  
SEQUENCE    
  lecIndex INTEGER
  lecRowStatus RowStatus
  lecOwner OwnerString
  lecConfigMode INTEGER
  lecConfigLanType LecDataFrameFormat
  lecConfigMaxDataFrameSize LecDataFrameSize
  lecConfigLanName OCTET STRING
  lecConfigLesAtmAddress AtmLaneAddress
  lecControlTimeout INTEGER
  lecMaxUnknownFrameCount INTEGER
  lecMaxUnknownFrameTime INTEGER
  lecVccTimeoutPeriod Integer32
  lecMaxRetryCount INTEGER
  lecAgingTime INTEGER
  lecForwardDelayTime INTEGER
  lecExpectedArpResponseTime INTEGER
  lecFlushTimeOut INTEGER
  lecPathSwitchingDelay INTEGER
  lecLocalSegmentID INTEGER
  lecMulticastSendType INTEGER
  lecMulticastSendAvgRate Integer32
  lecMulticastSendPeakRate Integer32
  lecConnectionCompleteTimer INTEGER

LecStatusEntry  
SEQUENCE    
  lecIfIndex Integer32
  lecPrimaryAtmAddress AtmLaneAddress
  lecID INTEGER
  lecInterfaceState LecState
  lecLastFailureRespCode INTEGER
  lecLastFailureState LecState
  lecProtocol INTEGER
  lecVersion INTEGER
  lecTopologyChange TruthValue
  lecConfigServerAtmAddress AtmLaneAddress
  lecConfigSource INTEGER
  lecActualLanType LecDataFrameFormat
  lecActualMaxDataFrameSize LecDataFrameSize
  lecActualLanName OCTET STRING
  lecActualLesAtmAddress AtmLaneAddress
  lecProxyClient TruthValue

LecMappingEntry  
SEQUENCE    
  lecMappingIndex INTEGER

LecStatisticsEntry  
SEQUENCE    
  lecArpRequestsOut Counter32
  lecArpRequestsIn Counter32
  lecArpRepliesOut Counter32
  lecArpRepliesIn Counter32
  lecControlFramesOut Counter32
  lecControlFramesIn Counter32
  lecSvcFailures Counter32

LecServerVccEntry  
SEQUENCE    
  lecConfigDirectInterface LeConnectionInterface
  lecConfigDirectVpi VpiInteger
  lecConfigDirectVci VciInteger
  lecControlDirectInterface LeConnectionInterface
  lecControlDirectVpi VpiInteger
  lecControlDirectVci VciInteger
  lecControlDistributeInterface LeConnectionInterface
  lecControlDistributeVpi VpiInteger
  lecControlDistributeVci VciInteger
  lecMulticastSendInterface LeConnectionInterface
  lecMulticastSendVpi VpiInteger
  lecMulticastSendVci VciInteger
  lecMulticastForwardInterface LeConnectionInterface
  lecMulticastForwardVpi VpiInteger
  lecMulticastForwardVci VciInteger

LecAtmAddressEntry  
SEQUENCE    
  lecAtmAddress AtmLaneAddress
  lecAtmAddressStatus RowStatus

LecMacAddressEntry  
SEQUENCE    
  lecMacAddress MacAddress
  lecMacAddressAtmBinding AtmLaneAddress

LecRouteDescrEntry  
SEQUENCE    
  lecRouteDescrSegmentID INTEGER
  lecRouteDescrBridgeNumber INTEGER
  lecRouteDescrAtmBinding AtmLaneAddress

LeArpEntry  
SEQUENCE    
  leArpMacAddress MacAddress
  leArpAtmAddress AtmLaneAddress
  leArpIsRemoteAddress TruthValue
  leArpEntryType LeArpTableEntryType
  leArpRowStatus RowStatus

LeRDArpEntry  
SEQUENCE    
  leRDArpSegmentID INTEGER
  leRDArpBridgeNumber INTEGER
  leRDArpAtmAddress AtmLaneAddress
  leRDArpEntryType LeArpTableEntryType
  leRDArpRowStatus RowStatus

Defined Values

atmfLanEmulation 1.3.6.1.4.1.353.5.3
OBJECT IDENTIFIER    

leClientMIB 1.3.6.1.4.1.353.5.3.1
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.
MODULE-IDENTITY    

leClientMIBObjects 1.3.6.1.4.1.353.5.3.1.1
OBJECT IDENTIFIER    

lecConfigTable 1.3.6.1.4.1.353.5.3.1.1.1
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LecConfigEntry

lecConfigEntry 1.3.6.1.4.1.353.5.3.1.1.1.1
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  LecConfigEntry  

lecIndex 1.3.6.1.4.1.353.5.3.1.1.1.1.1
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.)
Status: current Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..2147483647  

lecRowStatus 1.3.6.1.4.1.353.5.3.1.1.1.1.2
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'
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

lecOwner 1.3.6.1.4.1.353.5.3.1.1.1.1.3
The entity that configured this entry and is therefore using the resources assigned to it.
Status: current Access: read-create
OBJECT-TYPE    
  OwnerString Size(0..127)  

lecConfigMode 1.3.6.1.4.1.353.5.3.1.1.1.1.4
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER automatic(1), manual(2)  

lecConfigLanType 1.3.6.1.4.1.353.5.3.1.1.1.1.5
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.
Status: current Access: read-create
OBJECT-TYPE    
  LecDataFrameFormat  

lecConfigMaxDataFrameSize 1.3.6.1.4.1.353.5.3.1.1.1.1.6
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.
Status: current Access: read-create
OBJECT-TYPE    
  LecDataFrameSize  

lecConfigLanName 1.3.6.1.4.1.353.5.3.1.1.1.1.7
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.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0..32)  

lecConfigLesAtmAddress 1.3.6.1.4.1.353.5.3.1.1.1.1.8
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.
Status: current Access: read-create
OBJECT-TYPE    
  AtmLaneAddress  

lecControlTimeout 1.3.6.1.4.1.353.5.3.1.1.1.1.9
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 10..300  

lecMaxUnknownFrameCount 1.3.6.1.4.1.353.5.3.1.1.1.1.10
C10 Maximum Unknown Frame Count. See the description of lecMaxUnknownFrameTime below.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 1..10  

lecMaxUnknownFrameTime 1.3.6.1.4.1.353.5.3.1.1.1.1.11
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 1..60  

lecVccTimeoutPeriod 1.3.6.1.4.1.353.5.3.1.1.1.1.12
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.
Status: current Access: read-create
OBJECT-TYPE    
  Integer32  

lecMaxRetryCount 1.3.6.1.4.1.353.5.3.1.1.1.1.13
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 0..2  

lecAgingTime 1.3.6.1.4.1.353.5.3.1.1.1.1.14
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 10..300  

lecForwardDelayTime 1.3.6.1.4.1.353.5.3.1.1.1.1.15
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 4..30  

lecExpectedArpResponseTime 1.3.6.1.4.1.353.5.3.1.1.1.1.16
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 1..30  

lecFlushTimeOut 1.3.6.1.4.1.353.5.3.1.1.1.1.17
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 1..4  

lecPathSwitchingDelay 1.3.6.1.4.1.353.5.3.1.1.1.1.18
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 1..8  

lecLocalSegmentID 1.3.6.1.4.1.353.5.3.1.1.1.1.19
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 0..4095  

lecMulticastSendType 1.3.6.1.4.1.353.5.3.1.1.1.1.20
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER bestEffort(1), variableBitRate(2), constantBitRate(3)  

lecMulticastSendAvgRate 1.3.6.1.4.1.353.5.3.1.1.1.1.21
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.
Status: current Access: read-create
OBJECT-TYPE    
  Integer32  

lecMulticastSendPeakRate 1.3.6.1.4.1.353.5.3.1.1.1.1.22
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.
Status: current Access: read-create
OBJECT-TYPE    
  Integer32  

lecConnectionCompleteTimer 1.3.6.1.4.1.353.5.3.1.1.1.1.23
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 1..10  

lecStatusTable 1.3.6.1.4.1.353.5.3.1.1.2
A read-only table containing identification, status, and operational information about the LAN Emulation Clients this agent manages.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LecStatusEntry

lecStatusEntry 1.3.6.1.4.1.353.5.3.1.1.2.1
Each table entry contains information about one LAN Emulation Client.
Status: current Access: not-accessible
OBJECT-TYPE    
  LecStatusEntry  

lecIfIndex 1.3.6.1.4.1.353.5.3.1.1.2.1.1
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.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

lecPrimaryAtmAddress 1.3.6.1.4.1.353.5.3.1.1.2.1.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  AtmLaneAddress  

lecID 1.3.6.1.4.1.353.5.3.1.1.2.1.3
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER 0..65279  

lecInterfaceState 1.3.6.1.4.1.353.5.3.1.1.2.1.4
The current state of the LAN Emulation Client. Note that 'ifOperStatus' is defined to be 'up' when, and only when, 'lecInterfaceState' is 'operational'.
Status: current Access: read-only
OBJECT-TYPE    
  LecState  

lecLastFailureRespCode 1.3.6.1.4.1.353.5.3.1.1.2.1.5
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER none(1), timeout(2), undefinedError(3), versionNotSupported(4), invalidRequestParameters(5), duplicateLanDestination(6), duplicateAtmAddress(7), insufficientResources(8), accessDenied(9), invalidRequesterId(10), invalidLanDestination(11), invalidAtmAddress(12), noConfiguration(13), leConfigureError(14), insufficientInformation(15)  

lecLastFailureState 1.3.6.1.4.1.353.5.3.1.1.2.1.6
The state this client was in when it updated the 'lecLastFailureRespCode'. If 'lecLastFailureRespCode' is 'none', this object has the value initialState(1).
Status: current Access: read-only
OBJECT-TYPE    
  LecState  

lecProtocol 1.3.6.1.4.1.353.5.3.1.1.2.1.7
The LAN Emulation protocol which this client supports, and specifies in its LE_JOIN_REQUESTs.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER 1..255  

lecVersion 1.3.6.1.4.1.353.5.3.1.1.2.1.8
The LAN Emulation protocol version which this client supports, and specifies in its LE_JOIN_REQUESTs.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER 1..255  

lecTopologyChange 1.3.6.1.4.1.353.5.3.1.1.2.1.9
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'.
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

lecConfigServerAtmAddress 1.3.6.1.4.1.353.5.3.1.1.2.1.10
The ATM address of the LAN Emulation Configuration Server (if known) or the empty string (otherwise).
Status: current Access: read-only
OBJECT-TYPE    
  AtmLaneAddress  

lecConfigSource 1.3.6.1.4.1.353.5.3.1.1.2.1.11
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER gotAddressViaIlmi(1), usedWellKnownAddress(2), usedLecsPvc(3), didNotUseLecs(4)  

lecActualLanType 1.3.6.1.4.1.353.5.3.1.1.2.1.12
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.
Status: current Access: read-only
OBJECT-TYPE    
  LecDataFrameFormat  

lecActualMaxDataFrameSize 1.3.6.1.4.1.353.5.3.1.1.2.1.13
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
Status: current Access: read-only
OBJECT-TYPE    
  LecDataFrameSize  

lecActualLanName 1.3.6.1.4.1.353.5.3.1.1.2.1.14
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
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..32)  

lecActualLesAtmAddress 1.3.6.1.4.1.353.5.3.1.1.2.1.15
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.
Status: current Access: read-only
OBJECT-TYPE    
  AtmLaneAddress  

lecProxyClient 1.3.6.1.4.1.353.5.3.1.1.2.1.16
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.
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

lecMappingTable 1.3.6.1.4.1.353.5.3.1.1.3
A table mapping the 'ifIndex' values of 'aflane8023' and 'aflane8025' interfaces to the 'lecIndex' values of the corresponding LAN Emulation Clients.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LecMappingEntry

lecMappingEntry 1.3.6.1.4.1.353.5.3.1.1.3.1
Each row describes one ifIndex --> lecIndex mapping.
Status: current Access: not-accessible
OBJECT-TYPE    
  LecMappingEntry  

lecMappingIndex 1.3.6.1.4.1.353.5.3.1.1.3.1.1
The 'lecIndex' of the client which implements the specified interface.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER 1..2147483647  

lecStatisticsTable 1.3.6.1.4.1.353.5.3.1.1.4
An extension table containing traffic statistics for all the LAN Emulation Clients this host implements.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LecStatisticsEntry

lecStatisticsEntry 1.3.6.1.4.1.353.5.3.1.1.4.1
Each row in this table contains traffic statistics for one LAN Emulation client.
Status: current Access: not-accessible
OBJECT-TYPE    
  LecStatisticsEntry  

lecArpRequestsOut 1.3.6.1.4.1.353.5.3.1.1.4.1.1
The number of LE_ARP_REQUESTs sent over the LUNI by this LAN Emulation Client.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

lecArpRequestsIn 1.3.6.1.4.1.353.5.3.1.1.4.1.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

lecArpRepliesOut 1.3.6.1.4.1.353.5.3.1.1.4.1.3
The number of LE_ARP_RESPONSEs sent over the LUNI by this LAN Emulation Client.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

lecArpRepliesIn 1.3.6.1.4.1.353.5.3.1.1.4.1.4
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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

lecControlFramesOut 1.3.6.1.4.1.353.5.3.1.1.4.1.5
The total number of control packets sent by this LAN Emulation Client over the LUNI.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

lecControlFramesIn 1.3.6.1.4.1.353.5.3.1.1.4.1.6
The total number of control packets received by this LAN Emulation Client over the LUNI.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

lecSvcFailures 1.3.6.1.4.1.353.5.3.1.1.4.1.7
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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

lecServerVccTable 1.3.6.1.4.1.353.5.3.1.1.5
A table identifying the Control and Multicast VCCs for each LAN Emulation Client this host implements.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LecServerVccEntry

lecServerVccEntry 1.3.6.1.4.1.353.5.3.1.1.5.1
Each row in this table describes the Control VCCs and Multicast VCCs for one LAN Emulation client.
Status: current Access: not-accessible
OBJECT-TYPE    
  LecServerVccEntry  

lecConfigDirectInterface 1.3.6.1.4.1.353.5.3.1.1.5.1.1
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.
Status: current Access: read-only
OBJECT-TYPE    
  LeConnectionInterface  

lecConfigDirectVpi 1.3.6.1.4.1.353.5.3.1.1.5.1.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  VpiInteger  

lecConfigDirectVci 1.3.6.1.4.1.353.5.3.1.1.5.1.3
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.
Status: current Access: read-only
OBJECT-TYPE    
  VciInteger  

lecControlDirectInterface 1.3.6.1.4.1.353.5.3.1.1.5.1.4
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.
Status: current Access: read-only
OBJECT-TYPE    
  LeConnectionInterface  

lecControlDirectVpi 1.3.6.1.4.1.353.5.3.1.1.5.1.5
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.
Status: current Access: read-only
OBJECT-TYPE    
  VpiInteger  

lecControlDirectVci 1.3.6.1.4.1.353.5.3.1.1.5.1.6
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.
Status: current Access: read-only
OBJECT-TYPE    
  VciInteger  

lecControlDistributeInterface 1.3.6.1.4.1.353.5.3.1.1.5.1.7
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.
Status: current Access: read-only
OBJECT-TYPE    
  LeConnectionInterface  

lecControlDistributeVpi 1.3.6.1.4.1.353.5.3.1.1.5.1.8
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.
Status: current Access: read-only
OBJECT-TYPE    
  VpiInteger  

lecControlDistributeVci 1.3.6.1.4.1.353.5.3.1.1.5.1.9
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.
Status: current Access: read-only
OBJECT-TYPE    
  VciInteger  

lecMulticastSendInterface 1.3.6.1.4.1.353.5.3.1.1.5.1.10
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.
Status: current Access: read-only
OBJECT-TYPE    
  LeConnectionInterface  

lecMulticastSendVpi 1.3.6.1.4.1.353.5.3.1.1.5.1.11
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.
Status: current Access: read-only
OBJECT-TYPE    
  VpiInteger  

lecMulticastSendVci 1.3.6.1.4.1.353.5.3.1.1.5.1.12
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.
Status: current Access: read-only
OBJECT-TYPE    
  VciInteger  

lecMulticastForwardInterface 1.3.6.1.4.1.353.5.3.1.1.5.1.13
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.
Status: current Access: read-only
OBJECT-TYPE    
  LeConnectionInterface  

lecMulticastForwardVpi 1.3.6.1.4.1.353.5.3.1.1.5.1.14
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.
Status: current Access: read-only
OBJECT-TYPE    
  VpiInteger  

lecMulticastForwardVci 1.3.6.1.4.1.353.5.3.1.1.5.1.15
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.
Status: current Access: read-only
OBJECT-TYPE    
  VciInteger  

lecAtmAddressTable 1.3.6.1.4.1.353.5.3.1.1.6
A table listing all of the ATM addresses belonging to this host's LAN Emulation Clients.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LecAtmAddressEntry

lecAtmAddressEntry 1.3.6.1.4.1.353.5.3.1.1.6.1
Each row in this table describes one of a client's ATM addresses.
Status: current Access: not-accessible
OBJECT-TYPE    
  LecAtmAddressEntry  

lecAtmAddress 1.3.6.1.4.1.353.5.3.1.1.6.1.1
The ATM address this row describes. This could be either a primary address or a secondary address.
Status: current Access: not-accessible
OBJECT-TYPE    
  AtmLaneAddress  

lecAtmAddressStatus 1.3.6.1.4.1.353.5.3.1.1.6.1.2
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.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

lecMacAddressTable 1.3.6.1.4.1.353.5.3.1.1.7
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LecMacAddressEntry

lecMacAddressEntry 1.3.6.1.4.1.353.5.3.1.1.7.1
Each table row describes a (MAC address, ATM address) pair registered for a particular client.
Status: current Access: not-accessible
OBJECT-TYPE    
  LecMacAddressEntry  

lecMacAddress 1.3.6.1.4.1.353.5.3.1.1.7.1.1
A unicast MAC address which the LE client denoted by 'lecIndex' has registered with its LE Server.
Status: current Access: not-accessible
OBJECT-TYPE    
  MacAddress  

lecMacAddressAtmBinding 1.3.6.1.4.1.353.5.3.1.1.7.1.2
The ATM address registered for 'lecMacAddress'.
Status: current Access: read-only
OBJECT-TYPE    
  AtmLaneAddress  

lecRouteDescrTable 1.3.6.1.4.1.353.5.3.1.1.8
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LecRouteDescrEntry

lecRouteDescrEntry 1.3.6.1.4.1.353.5.3.1.1.8.1
Each table row describes a (Route Descriptor, ATM address) pair registered for a particular client.
Status: current Access: not-accessible
OBJECT-TYPE    
  LecRouteDescrEntry  

lecRouteDescrSegmentID 1.3.6.1.4.1.353.5.3.1.1.8.1.1
The LAN ID portion of the IEEE 802.5 route descriptor associated with this conceptual row.
Status: current Access: not-accessible
OBJECT-TYPE    
  INTEGER 0..4095  

lecRouteDescrBridgeNumber 1.3.6.1.4.1.353.5.3.1.1.8.1.2
The Bridge Number portion of the IEEE 802.5 route descriptor associated with this conceptual row.
Status: current Access: not-accessible
OBJECT-TYPE    
  INTEGER 0..15  

lecRouteDescrAtmBinding 1.3.6.1.4.1.353.5.3.1.1.8.1.3
The ATM address registered for the IEEE 802.5 route descriptor ('lecRouteDescrSegmentID', 'lecRouteDescrBridgeNumber').
Status: current Access: read-only
OBJECT-TYPE    
  AtmLaneAddress  

leArpTable 1.3.6.1.4.1.353.5.3.1.1.9
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LeArpEntry

leArpEntry 1.3.6.1.4.1.353.5.3.1.1.9.1
An ATM LAN Emulation ARP cache entry containing information about the binding of one MAC address to one ATM address.
Status: current Access: not-accessible
OBJECT-TYPE    
  LeArpEntry  

leArpMacAddress 1.3.6.1.4.1.353.5.3.1.1.9.1.1
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  MacAddress  

leArpAtmAddress 1.3.6.1.4.1.353.5.3.1.1.9.1.2
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.
Status: current Access: read-create
OBJECT-TYPE    
  AtmLaneAddress  

leArpIsRemoteAddress 1.3.6.1.4.1.353.5.3.1.1.9.1.3
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.
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

leArpEntryType 1.3.6.1.4.1.353.5.3.1.1.9.1.4
Indicates how this LE_ARP table entry was created and whether it is aged.
Status: current Access: read-create
OBJECT-TYPE    
  LeArpTableEntryType  

leArpRowStatus 1.3.6.1.4.1.353.5.3.1.1.9.1.5
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.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

leRDArpTable 1.3.6.1.4.1.353.5.3.1.1.10
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LeRDArpEntry

leRDArpEntry 1.3.6.1.4.1.353.5.3.1.1.10.1
An ATM LAN Emulation ARP cache entry containing information about the binding of one IEEE 802.5 route descriptor to one ATM address.
Status: current Access: not-accessible
OBJECT-TYPE    
  LeRDArpEntry  

leRDArpSegmentID 1.3.6.1.4.1.353.5.3.1.1.10.1.1
The LAN ID portion of the IEEE 802.5 route descriptor associated with this ARP cache entry.
Status: current Access: not-accessible
OBJECT-TYPE    
  INTEGER 0..4095  

leRDArpBridgeNumber 1.3.6.1.4.1.353.5.3.1.1.10.1.2
The Bridge Number portion of the IEEE 802.5 route descriptor associated with this ARP cache entry.
Status: current Access: not-accessible
OBJECT-TYPE    
  INTEGER 0..15  

leRDArpAtmAddress 1.3.6.1.4.1.353.5.3.1.1.10.1.3
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.
Status: current Access: read-create
OBJECT-TYPE    
  AtmLaneAddress  

leRDArpEntryType 1.3.6.1.4.1.353.5.3.1.1.10.1.4
Indicates how this LE_ARP table entry was created and whether it is aged.
Status: current Access: read-create
OBJECT-TYPE    
  LeArpTableEntryType  

leRDArpRowStatus 1.3.6.1.4.1.353.5.3.1.1.10.1.5
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.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

leClientMIBConformance 1.3.6.1.4.1.353.5.3.1.2
OBJECT IDENTIFIER    

leClientMIBGroups 1.3.6.1.4.1.353.5.3.1.2.1
OBJECT IDENTIFIER    

leClientMIBCompliances 1.3.6.1.4.1.353.5.3.1.2.2
OBJECT IDENTIFIER    

leClientMIBCompliance 1.3.6.1.4.1.353.5.3.1.2.2.1
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.
Status: current Access: read-only
MODULE-COMPLIANCE    

leClientConfigGroup 1.3.6.1.4.1.353.5.3.1.2.1.1
A collection of objects used for creating and configuring LAN Emulation Clients.
Status: current Access: read-only
OBJECT-GROUP    

leClientStatusGroup 1.3.6.1.4.1.353.5.3.1.2.1.2
A collection of objects describing the status and operational parameters of the managed LAN Emulation Clients.
Status: current Access: read-only
OBJECT-GROUP    

leClientMappingGroup 1.3.6.1.4.1.353.5.3.1.2.1.3
A collection of objects which map a LAN Emulation Client's 'ifIndex' to its 'lecIndex'.
Status: current Access: read-only
OBJECT-GROUP    

leClientStatisticsGroup 1.3.6.1.4.1.353.5.3.1.2.1.4
A collection of objects which act as an extension to the lecConfigTable. These objects provide statistics on LAN Emulation control traffic and SVC establishment.
Status: current Access: read-only
OBJECT-GROUP    

leClientServerVccGroup 1.3.6.1.4.1.353.5.3.1.2.1.5
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.
Status: current Access: read-only
OBJECT-GROUP    

leClientAtmAddressesGroup 1.3.6.1.4.1.353.5.3.1.2.1.6
A collection of objects which describe all of the ATM addresses belonging to each client.
Status: current Access: read-only
OBJECT-GROUP    

leClientMacAddressesGroup 1.3.6.1.4.1.353.5.3.1.2.1.7
A collection of objects which describe all of the MAC addresses registered for each client.
Status: current Access: read-only
OBJECT-GROUP    

leClientRouteDescriptorsGroup 1.3.6.1.4.1.353.5.3.1.2.1.8
A collection of objects which describe all of the Route Descriptors registered for each client.
Status: current Access: read-only
OBJECT-GROUP    

leClientArpGroup 1.3.6.1.4.1.353.5.3.1.2.1.9
A collection of objects which describe the MAC- to-ATM address mappings that this LAN Emulation Client has learned.
Status: current Access: read-only
OBJECT-GROUP    

leClientRDArpGroup 1.3.6.1.4.1.353.5.3.1.2.1.10
A collection of objects which describe the IEEE 802.5 Route Descriptor-to-ATM address mappings that this LAN Emulation Client has learned.
Status: current Access: read-only
OBJECT-GROUP