MIB Discovery
1856 modules enregistr├ęs
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 353 (atmForum). 5 (atmForumNetworkManagement). 3 (atmfLanEmulation). 1 (leClientMIB). 1 (leClientMIBObjects). 1 (lecConfigTable)
TXT : iso. org. dod. internet. private. enterprises. atmForum. atmForumNetworkManagement. atmfLanEmulation. leClientMIB. leClientMIBObjects. lecConfigTable
DescriptionA 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.