DISMAN-NSLOOKUP-MIB
AI MIB Summary
The DISMAN-NSLOOKUP-MIB facilitates remote DNS resolution queries to retrieve IP addresses for hostnames or hostnames for IP addresses, enabling automated monitoring of name-to-address mappings and reverse DNS lookups across networked devices.
The Lookup MIB (DISMAN-NSLOOKUP-MIB) enables determination of either the name(s) corresponding to a host address or of the address(es) associated with a host name at a remote host. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4560; see the RFC itself for full legal notices.
Main OID:
lookupMIB.1.3.6.1.2.1.82
25
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
25 total| Object Name |
|---|
lookupMIBThe Lookup MIB (DISMAN-NSLOOKUP-MIB) enables determination of either the name(s) corresponding to a host address or of the address(es) associated with a host name at a remote host. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4560; see the RFC itself for full legal notices. MODULE-IDENTITY .1.3.6.1.2.1.82 |
lookupObjects OBJECT IDENTIFIER .1.3.6.1.2.1.82.1 |
lookupMaxConcurrentRequestsThe maximum number of concurrent active lookup requests that are allowed within an agent implementation. A value of 0 for this object implies that there is no limit for the number of concurrent active requests in effect. The limit applies only to new requests being activated. When a new value is set, the agent will continue processing all the requests already active, even if their number exceed the limit just imposed.rw Unsigned32 UNITS "requests" .1.3.6.1.2.1.82.1.1 |
lookupPurgeTimeThe amount of time to wait before automatically deleting an entry in the lookupCtlTable and any dependent lookupResultsTable entries after the lookup operation represented by a lookupCtlEntry has been completed. A lookupCtEntry is considered complete when its lookupCtlOperStatus object has a value of completed(3). A value of 0 indicates that automatic deletion of entries is disabled.rw Unsigned32 .1.3.6.1.2.1.82.1.2 |
lookupCtlTableDefines the Lookup Control Table for providing the capability of performing a lookup operation for a symbolic host name or for a host address from a remote host. SEQUENCE OF LookupCtlEntry .1.3.6.1.2.1.82.1.3 |
lookupCtlEntryDefines an entry in the lookupCtlTable. A lookupCtlEntry is initially indexed by lookupCtlOwnerIndex, which is a type of SnmpAdminString, a textual convention that allows for the use of the SNMPv3 View-Based Access Control Model (RFC 3415, VACM) and that also allows a management application to identify its entries. The second index element, lookupCtlOperationName, enables the same lookupCtlOwnerIndex entity to have multiple outstanding requests. The value of lookupCtlTargetAddressType determines which lookup function to perform. LookupCtlEntry .1.3.6.1.2.1.82.1.3.1 |
lookupCtlOwnerIndexTo facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to create or modify entries independently, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString and can thus be trivially mapped to a securityName or groupName defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible. SnmpAdminString .1.3.6.1.2.1.82.1.3.1.1 |
lookupCtlOperationNameThe name of a lookup operation. This is locally unique, within the scope of an lookupCtlOwnerIndex. SnmpAdminString .1.3.6.1.2.1.82.1.3.1.2 |
lookupCtlTargetAddressTypeSpecifies the type of address for performing a lookup operation for a symbolic host name or for a host address from a remote host. Specification of dns(16) as the value for this object means that a function such as, for example, getaddrinfo() or gethostbyname() should be performed to return one or more numeric addresses. Use of a value of either ipv4(1) or ipv6(2) means that a functions such as, for example, getnameinfo() or gethostbyaddr() should be used to return the symbolic names associated with a host.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.82.1.3.1.3 |
lookupCtlTargetAddressSpecifies the address used for a resolver lookup at a remote host. The corresponding lookupCtlTargetAddressType objects determines its type, as well as the function that can be requested. A value for this object MUST be set prior to transitioning its corresponding lookupCtlEntry to active(1) via lookupCtlRowStatus.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.82.1.3.1.4 |
lookupCtlOperStatusReflects the operational state of an lookupCtlEntry: enabled(1) - Operation is active. notStarted(2) - Operation has not been enabled. completed(3) - Operation has been completed. An operation is automatically enabled(1) when its lookupCtlRowStatus object is transitioned to active(1) status. Until this occurs, lookupCtlOperStatus MUST report a value of notStarted(2). After the lookup operation is completed (success or failure), the value for lookupCtlOperStatus MUST be transitioned to completed(3).ro Enumeration .1.3.6.1.2.1.82.1.3.1.5 |
lookupCtlTimeReports the number of milliseconds that a lookup operation required to be completed at a remote host. Completed means operation failure as well as success.ro Unsigned32 UNITS "milliseconds" .1.3.6.1.2.1.82.1.3.1.6 |
lookupCtlRcThe system-specific return code from a lookup operation. All implementations MUST return a value of 0 for this object when the remote lookup operation succeeds. A non-zero value for this objects indicates failure. It is recommended that implementations return the error codes that are generated by the lookup function used.ro Integer32 .1.3.6.1.2.1.82.1.3.1.7 |
lookupCtlRowStatusThis object allows entries to be created and deleted in the lookupCtlTable. A remote lookup operation is started when an entry in this table is created via an SNMP set request and the entry is activated. This occurs by setting the value of this object to CreateAndGo(4) during row creation or by setting this object to active(1) after the row is created. A value MUST be specified for lookupCtlTargetAddress prior to the acceptance of a transition to active(1) state. A remote lookup operation starts when its entry first becomes active(1). Transitions in and out of active(1) state have no effect on the operational behavior of a remote lookup operation, with the exception that deletion of an entry in this table by setting its RowStatus object to destroy(6) will stop an active remote lookup operation. The operational state of a remote lookup operation can be determined by examination of its lookupCtlOperStatus object.rw RowStatus (SNMPv2-TC) .1.3.6.1.2.1.82.1.3.1.8 |
lookupResultsTableDefines the Lookup Results Table for providing the capability of determining the results of a operation at a remote host. One or more entries are added to the lookupResultsTable when a lookup operation, as reflected by an lookupCtlEntry, is completed successfully. All entries related to a successful lookup operation MUST be added to the lookupResultsTable at the same time that the associating lookupCtlOperStatus object is transitioned to completed(2). The number of entries added depends on the results determined for a particular lookup operation. All entries associated with an lookupCtlEntry are removed when the lookupCtlEntry is deleted. A remote host can be multi-homed and have more than one IP address associated with it (returned by lookup function), or it can have more than one symbolic name (returned by lookup function). A function such as, for example, getnameinfo() or gethostbyaddr() is called with a host address as its parameter and is used primarily to determine a symbolic name to associate with the host address. Entries in the lookupResultsTable MUST be made for each host name returned. If the function identifies an 'official host name,' then this symbolic name MUST be assigned a lookupResultsIndex of 1. A function such as, for example, getaddrinfo() or gethostbyname() is called with a symbolic host name and is used primarily to retrieve a host address. The entries MUST be stored in the order that they are retrieved from the lookup function. lookupResultsIndex 1 MUST be assigned to the first entry. SEQUENCE OF LookupResultsEntry .1.3.6.1.2.1.82.1.4 |
lookupResultsEntryDefines an entry in the lookupResultsTable. The first two index elements identify the lookupCtlEntry that a lookupResultsEntry belongs to. The third index element selects a single lookup operation result. LookupResultsEntry .1.3.6.1.2.1.82.1.4.1 |
lookupResultsIndexEntries in the lookupResultsTable are created when the result of a lookup operation is determined. Entries MUST be stored in the lookupResultsTable in the order that they are retrieved. Values assigned to lookupResultsIndex MUST start at 1 and increase consecutively. Unsigned32 (1..'ffffffff'h) .1.3.6.1.2.1.82.1.4.1.1 |
lookupResultsAddressTypeIndicates the type of result of a remote lookup operation. A value of unknown(0) implies either that the operation hasn't been started or that it has failed.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.82.1.4.1.2 |
lookupResultsAddressReflects a result for a remote lookup operation as per the value of lookupResultsAddressType. The address type (InetAddressType) that relates to this object is specified by the corresponding value of lookupResultsAddress.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.82.1.4.1.3 |
lookupConformance OBJECT IDENTIFIER .1.3.6.1.2.1.82.2 |
lookupCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.82.2.1 |
lookupComplianceThe compliance statement for SNMP entities that fully implement the DISMAN-NSLOOKUP-MIB. Unknown .1.3.6.1.2.1.82.2.1.1 |
lookupMinimumComplianceThe minimum compliance statement for SNMP entities that implement the minimal subset of the DISMAN-NSLOOKUP-MIB. Implementors might choose this subset for small devices with limited resources. Unknown .1.3.6.1.2.1.82.2.1.2 |
lookupGroups OBJECT IDENTIFIER .1.3.6.1.2.1.82.2.2 |
lookupGroupThe group of objects that constitute the remote Lookup operation. Unknown .1.3.6.1.2.1.82.2.2.1 |