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). 9 (leArpTable). 1 (leArpEntry). 5 (leArpRowStatus)
TXT : iso. org. dod. internet. private. enterprises. atmForum. atmForumNetworkManagement. atmfLanEmulation. leClientMIB. leClientMIBObjects. leArpTable. leArpEntry. leArpRowStatus
Pas d'enfants disponibles pour cet OID
Description 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.
SyntaxeRowStatus (SNMPv2-TC)