-- extracted from draft-ietf-disman-remops-mib-03.txt -- at Mon Nov 15 17:10:50 1999 DISMAN-LOOKUP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, experimental FROM SNMPv2-SMI -- RFC1902 RowStatus, TestAndIncr FROM SNMPv2-TC -- RFC1903 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC1904 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC2271 DnsName FROM DNS-SERVER-MIB -- RFC1611 HostAddress, OperationStatus FROM DISMAN-PING-MIB; lookupMIB MODULE-IDENTITY LAST-UPDATED "9812200000Z" ORGANIZATION "IETF Distributed Management Working Group" CONTACT-INFO "Kenneth White International Business Machines Corporation Network Computing Software Division Research Triangle Park, NC, USA E-mail: wkenneth@us.ibm.com" DESCRIPTION "The Lookup MIB (DISMAN-LOOKUP-MIB) enables determination of either the name corresponding to a host address or of the address associated with a host name at a remote host via use of the SNMP protocol," ::= { experimental 84 3 } -- Top-level structure of the MIB lookupNotifications OBJECT IDENTIFIER ::= { lookupMIB 0 } lookupObjects OBJECT IDENTIFIER ::= { lookupMIB 1 } lookupConformance OBJECT IDENTIFIER ::= { lookupMIB 2 } -- Simple Object Definitions lookupSpinLock OBJECT-TYPE SYNTAX TestAndIncr MAX-ACCESS read-write STATUS current DESCRIPTION "An advisory lock used to allow cooperating applications to coordinate their use of the lookupTable. This object should be used when an application seeks to create an new entry or alter an existing entry in the lookupTable. A management implementation MAY utilize the lookupSpinLock to serialize its changes or additions. Its usage is NOT REQUIRED." ::= { lookupObjects 1 } lookupMaxConcurrentRequests OBJECT-TYPE SYNTAX Integer32 (1..100) MAX-ACCESS read-write STATUS current DESCRIPTION "The maximum number of concurrent active Lookup requests that are allowed within an agent implementation." DEFVAL { 10 } ::= { lookupObjects 2 } lookupPurgeTime OBJECT-TYPE SYNTAX Integer32 (0..86400) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The amount of time to wait before automatically deleting an entry in the lookupTable after the Lookup operation represented by an lookupEntry has completed." DEFVAL { 900 } -- 15 minutes as default ::= { lookupObjects 3 } -- Lookup Table lookupTable OBJECT-TYPE SYNTAX SEQUENCE OF LookupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines the Lookup Table for provide via SNMP the capability of performing a lookup operation, gethostbyname or gethostbyaddr, from a remote host." ::= { lookupObjects 4 } lookupEntry OBJECT-TYPE SYNTAX LookupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines an entry in the lookupTable." INDEX { lookupOwnerIndex } ::= { lookupTable 1 } LookupEntry ::= SEQUENCE { lookupOwnerIndex SnmpAdminString, lookupCtl INTEGER, lookupTimeOut Integer32, lookupOperStatus OperationStatus, lookupAddress HostAddress, lookupDnsName DnsName, lookupRowStatus RowStatus } lookupOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2275, VACM) for tables in which multiple users may need to independently create or modify entries, 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 as defined in VACM, in accordance with a security policy. All entries in that table belonging to a particular user 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." ::= { lookupEntry 1 } lookupCtl OBJECT-TYPE SYNTAX INTEGER { getHostByName(1), getHostByAddr(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object determines whether the getHostByName or the getHostByAddr resolver function will be invoked at a remote host." ::= { lookupEntry 2 } lookupTimeOut OBJECT-TYPE SYNTAX Integer32 (1..600) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the time-out value, in seconds, for the Lookup operation made at a remote host. Valid values for timeout are from 1 to 600 seconds." DEFVAL { 3 } ::= { lookupEntry 3 } lookupOperStatus OBJECT-TYPE SYNTAX OperationStatus MAX-ACCESS read-only STATUS current DESCRIPTION "Reflects the operational state of a Lookup operation." ::= { lookupEntry 4 } lookupAddress OBJECT-TYPE SYNTAX HostAddress MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the address used for a getHostByAddr Lookup operation at a remote host." ::= { lookupEntry 5 } lookupDnsName OBJECT-TYPE SYNTAX DnsName MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the address used for a getHostByName Lookup operation at a remote host." ::= { lookupEntry 6 } lookupRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the lookupTable. A remote DNS Lookup operation is started when an entry in this table is created via an SNMP SET request and the entry is activated. This can occur 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 remote DNS 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 DNS 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 DNS Lookup operation. The operational state of a remote DNS Lookup operation can be determined by examination of it's lookupOperStatus object." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { lookupEntry 7 } --------------------------------------------------------------------- -- Conformance information -- Compliance statements --------------------------------------------------------------------- lookupCompliances OBJECT IDENTIFIER ::= { lookupConformance 1 } lookupGroups OBJECT IDENTIFIER ::= { lookupConformance 2 } --------------------------------------------------------------------- -- Compliance statements --------------------------------------------------------------------- lookupCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for the DISMAN-LOOKUP-MIB." MODULE -- this module MANDATORY-GROUPS { lookupGroup } OBJECT lookupMaxConcurrentRequests MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object." OBJECT lookupPurgeTime MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object." ::= { lookupCompliances 1 } --------------------------------------------------------------------- -- MIB groupings --------------------------------------------------------------------- lookupGroup OBJECT-GROUP OBJECTS { lookupSpinLock, lookupMaxConcurrentRequests, lookupPurgeTime, lookupCtl, lookupTimeOut, lookupOperStatus, lookupAddress, lookupDnsName, lookupRowStatus } STATUS current DESCRIPTION "The group of objects that comprise the remote Lookup operation." ::= { lookupGroups 1 } END -- -- Copyright (C) The Internet Society (1997). All Rights Reserved. -- This document and translations of it may be copied and furnished to -- others, and derivative works that comment on or otherwise explain it or -- assist in its implementation may be prepared, copied, published and -- distributed, in whole or in part, without restriction of any kind, -- provided that the above copyright notice and this paragraph are included -- on all such copies and derivative works. However, this document itself -- may not be modified in any way, such as by removing the copyright notice -- or references to the Internet Society or other Internet organizations, -- except as needed for the purpose of developing Internet standards in -- which case the procedures for copyrights defined in the Internet -- Standards process must be followed, or as required to translate it into -- languages other than English. -- -- The limited permissions granted above are perpetual and will not be -- revoked by the Internet Society or its successors or assigns. -- -- This document and the information contained herein is provided on an "AS -- IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK -- FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT -- LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT -- INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR -- FITNESS FOR A PARTICULAR PURPOSE.