MADMAN Working Group Glenn Mansfield [glenn@aic.co.jp] INTERNET-DRAFT AIC Systems Laboratory S.E.Hardcastle-Kille [steve@isode.com] ISODE Consortium June 1993 DSA Monitoring MIB Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress." To learn the current status of any Internet-Draft, please check the 1id-abstracts.txt listing contained in the Internet-Drafts Shadow Directories on ds.internic.net, nic.nordu.net, ftp.nisc.sri.com, or munnari.oz.au. Abstract This document defines an MIB for monitoring Directory System Agents [DSA], a component of the OSI Directory. The DSAmib will be used in conjunction with the application-mib for monitoring DSAs. Contents ======== 1.The Network Management Framework. 2 2.Model of the management information base for a DSA Manager. 2 3.The DSA functions and operations. 3 4.MIB design. 4 5.The DSAmib 5 6.Acknowledgements 24 7.References 25 Expires: January 2, 1994 [Page 1] Internet Draft June 1993 1.The Network Management Framework. ================================== The Internet Network Management framework is laid out in the three documents- STD 16/ RFC 1155 [1] defines the generic structure of network management information STD 15/ RFC 1157 [2] defines the protocol for accessing network management information STD 17/ RFC 1213 [3] defines the primary set of managed objects. The framework is adaptable/extensible by defining newer MIBs to suit the requirements of specific applications/protocols/situations. 2.Model of the management information base for a DSA Manager. A DSA-manager[application] will need to monitor several aspects of the the operational DSA. It may want to know the process related aspects- the CPU, memory, .. utilization of the operational DSA; the network service related aspects - inboundAssociations, outboundAssociations, operStatus, ... and finally the information specific to DSA applications. The MIB proposed in this document covers only the portion which is specific to the DSA-application. The network service related part of the MIB, and the host-resources related part, of the MIB , as well other parts of interest to a Manager monitoring the DSA-application, are covered in separate documents [6][7]. The relationship of this MIB with the other MIBs (existing and potential) is shown in the following diagram. Expires: January 2, 1994 [Page 2] Internet Draft June 1993 ------------------------------------------ | HOST RESOURCES mib | | | ------------------------------------------- | | | | O | | | | | | | | T | | |O| | DSA | MTA |FTAM | H | NFS | DNS |T| | mib | mib |mib | E | mib | mib |H| | | | | R | | |E| --------------------------| | |R| | NETWORK APPLN mib | | | | | for CO-AP | | | | ------------------------------------------- | | | Other mibs [MIB-II, ... ] | | | ------------------------------------------- Fig. 1 The manager (application) of a network service application will use the Host-resources-mib to obtain process related information [ resource usage,..] the network service application mib provides the information for the generic objects[peer associations] . The Application specific objects are defined in the corresponding MIB, e.g., the DSA-specific MIB is the one that is being proposed in this Paper. For management information pertaining to the lower layer TCP/UDP/IP/... the MIB-II offers the repertoire of MOs. 3.The DSA functions and operations. ================================== The Directory System Agent [DSA], a component of the OSI-Directory, is an application process. It provides access to the Directory Information Base [DIB] to Directory User Agents [DUA] and/or other DSAs. Functionally , a User [ DUA ] and the Directory are bound together for a period of time at an access point to the Directory [DSA]. A DSA may use information stored in its local data base or interact with other DSAs to service requirements. Alternatively, A DSA may refer the DUA to another DSA. A DSA binds to another DSA at the start of the period of access. Expires: January 2, 1994 [Page 3] Internet Draft June 1993 The core of the DSA is modelled as a process which is internally supported by a set of procedures. The containment/support hierarchy of the procedures are shown below- Operations Dispatcher Name Resolution Find Naming context Local name resolution Evaluation Single Object evaluation Multiple Object evaluation Results Merging The specific operations carried out by the DSA are of following three categories Single-Object operations Read, Compare, AddEntry, ModifyEntry, ModifyRDN, RemoveEntry Multiple-Object operations List, Search Abandon Operations Abandon 4. MIB design. ============= The basic principle has been to keep the MIB as simple as possible. The Managed objects included in the MIB are divided into three tables- the dsaTable, dsaDetailedTable and DSAInfoTable. - The dsaTable provides primary statistics for managing the DSA. it covers the DSA related administrative information, as well as summary data on the accesses, operations and errors. - The dsaDetailedTable provides detailed operations and error statistics. - The DSAInfoTable provides some useful information on the performance of the DSAs with which the monitored DSA interacts. Directory Reference. There are references to the Directory itself for static information pertaining to the DSA. These references are in the form of "Directory Distinguished Name" of the corresponding object. It is intended that DSA management applications will use these references to obtain further related information on the objects of interest. Expires: January 2, 1994 [Page 4] Internet Draft June 1993 Traps. Traps are defined to send alarms in cases of Authorization failures, DSA initialization and DSA stop. [Actually these could very well be put in the "Network Services Monitoring MIB" ... ] 5. The DSAmib ============= DSA-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE FROM RFC1212 Counter, TimeTicks, DisplayString FROM RFC1151-SMI; -- textual conventions -- Distinguished Name- is used to refer to objects in the directory. DistinguishedName::= DisplayString dsaTable OBJECT-TYPE SYNTAX SEQUENCE OF DSAEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The table holding information specific to a DSA" ::= {application-mib 3} dsaEntry OBJECT-TYPE SYNTAX DSAEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Entry associated with each DSA" INDEX { dsaApplicationIndex } ::= {dsaTable 1} DSAEntry ::= SEQUENCE { dsaApplicationIndex INTEGER, dsaContact DisplayString, dsaContactDN DistinguishedName, dsaName Expires: January 2, 1994 [Page 5] Internet Draft June 1993 DisplayString, dsaType DisplayString, dsaDN DistinguishedName, masterEntries INTEGER, copyEntries INTEGER, cacheEntries INTEGER, --bindings anonymousBinds Counter, unauthNameDAPBinds Counter, unauthNameDSPBinds Counter, simpleBinds Counter, protectedBinds Counter, externalBinds Counter, --Ops Dispatcher inOps Counter, loopDetected Counter, securityError Counter, -- nameResolution phase nameErrors Counter, serviceErrors Counter, foundLocalEntry Counter, referrals Counter, aliasDereferences Counter, chainings Counter, Expires: January 2, 1994 [Page 6] Internet Draft June 1993 multicastChainings Counter, -- evaluation phase -- single object evaluation readOps Counter, compareOps Counter, addEntryOps Counter, removeEntryOps Counter, modifyEntryOps Counter, modifyRDNOps Counter, -- multiple-object evaluation listOps Counter, searchOps Counter, oneLevelSearchOps Counter, wholeTreeSearchOps Counter, updateErrors Counter, -- abandon abandonOps Counter, abandonFailed Counter, -- Service Control & Cache performance cacheHits Counter, slaveHits Counters, dontUseCopyOps Counter } Expires: January 2, 1994 [Page 7] Internet Draft June 1993 dsaApplicationIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Reference into application table to allow correlation with general application parameters" ::= {dsaEntry 1} ---- Actually this part should go into the applEntry Table. ---- But since it is missing there I have included it here dsaContact OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "textual identification of the Contact person for this DSA" ::= {dsaEntry 2} dsaContactDN OBJECT-TYPE SYNTAX DistinguishedName ACCESS read-only STATUS mandatory DESCRIPTION "the Distinguished Name of the Contact person for this DSA." ::= {dsaEntry 3} dsaName OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "the Name of this DSA" ::= {dsaEntry 4} dsaType OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "the type of this DSA quipu/..../ " ::= {dsaEntry 5} Expires: January 2, 1994 [Page 8] Internet Draft June 1993 dsaDN OBJECT-TYPE SYNTAX DistinguishedName ACCESS read-only STATUS mandatory DESCRIPTION "the Distinguished Name of the DSA-entry pertaining to this DSA" ::= {dsaEntry 6} ------- Upto here masterEntries OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of Entries mastered in the DSA" ::= {dsaEntry 7} copyEntries OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of Entries with systematic (slave) copies maintained in the DSA" ::= {dsaEntry 8} cacheEntries OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of Entries cached (non-systematic copies) in the DSA" ::= {dsaEntry 9} anonymousBinds OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " Number of anonymous (DAP) binds to this DSA since application start" ::= {dsaEntry 10} unauthNameDAPBinds OBJECT-TYPE SYNTAX INTEGER Expires: January 2, 1994 [Page 9] Internet Draft June 1993 ACCESS read-only STATUS mandatory DESCRIPTION " Number of un-authenticated DAP binds to this DSA , since application start" ::= {dsaEntry 11} unauthNameDSPBinds OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " Number of un-authenticated DSP binds to this DSA , since application start" ::= {dsaEntry 12} simpleBinds OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " Number of binds to this DSA that passed simple authentication, since application start" ::= {dsaEntry 13} protectedBinds OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " Number of binds to this DSA that passed protected authentication, since application start" ::= {dsaEntry 14} externalBinds OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " Number of binds to this DSA that were authenticated using the external authentication procedures, since application start" ::= {dsaEntry 15} inOps OBJECT-TYPE SYNTAX INTEGER Expires: January 2, 1994 [Page 10] Internet Draft June 1993 ACCESS read-only STATUS mandatory DESCRIPTION " Number of operations forwarded to this DSA from DUAs or other DSAs , since application start" ::= {dsaEntry 16} loopDetected OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operation forwarded to this DSA in which a loop was detected. Note that, this check is performed immediately on receipt of the request, and will occur only in cases of requests from other DSAs. A serviceError of type loopDetected is originated at the DSA in such cases." ::= {dsaEntry 17} securityErrors OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations forwarded to this DSA which did not meet the security requirements " ::= {dsaEntry 18} nameErrors OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations nameErrors that originated at this DSA this includes noSuchObject, aliasProblem, aliasDereferencingProblem." ::= {dsaEntry 19} foundLocalEntry OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations forwarded to the DSA for which the pertinent entry is held in the DSA" Expires: January 2, 1994 [Page 11] Internet Draft June 1993 ::= {dsaEntry 20} referrals OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of referrals made by this DSA to other DSAa DUAs" ::= {dsaEntry 21} serviceError OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of serviceErrors that originated at this DSA. These include LoopDetected, invalidReference, unableToProceed, outOfScope, timeLimitExceeded, sizeLimitExceeded, administrativeLimitExceeded, unavailableCriticalExtension" ::= {dsaEntry 22} aliasDereferences OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of aliases dereferenced " ::= {dsaEntry 23} chainings OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations forwarded by this DSA to other DSAs" ::= {dsaEntry 24} multicastChainings OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of parallel multicast chainings that were originated from this DSA since Expires: January 2, 1994 [Page 12] Internet Draft June 1993 application start" ::= {dsaEntry 25} readOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of read operations from DSAs and DUAs that has been received by this DSA since application startup." ::= {dsaEntry 26} compareOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of compare operations since application startup." ::= {dsaEntry 27} addEntryOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of addEntry operations since application startup." ::= {dsaEntry 28} removeEntryOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of removeEntry operations since application startup." ::= {dsaEntry 29} modifyEntryOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of modifyEntry operations since application startup." ::= {dsaEntry 30} Expires: January 2, 1994 [Page 13] Internet Draft June 1993 modifyRDNOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of modifyRDN operations since application startup." ::= {dsaEntry 31} listOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of list operations since application startup." ::= {dsaEntry 32} searchOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of search operations- baseObjectSearches, oneLevelSearches and subTreeSearches, since application startup." ::= {dsaEntry 33} oneLevelSearchOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of oneLevelSearch operations since application startup." ::= {dsaEntry 34} wholeTreeSearchOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of wholeTreeSearch operations since application startup." ::= {dsaEntry 35} abandonOps OBJECT-TYPE SYNTAX INTEGER Expires: January 2, 1994 [Page 14] Internet Draft June 1993 ACCESS read-only STATUS mandatory DESCRIPTION " number of abandon operations forwarded to this DSA since application startup." ::= {dsaEntry 36} abandonFailed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of abandon operations that failed at this DSA since application startup." ::= {dsaEntry 37} cacheHits OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations that were serviced from the locally held cache, since application startup." ::= {dsaEntry 38} slaveHits OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations that were serviced from the locally held object replications [ shadow entries] since application startup." ::= {dsaEntry 39} dontUseCopy OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations that forbid the use of copies, since application startup." ::= {dsaEntry 40} Expires: January 2, 1994 [Page 15] Internet Draft June 1993 -- The DSADetail table contains detailed statistical data -- on the DSA operations and errors. dsaDetailTable OBJECT-TYPE SYNTAX SEQUENCE OF DSADetailEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The table holding information specific to a DSA" ::= {application-mib 4} dsaDetailEntry OBJECT-TYPE SYNTAX DSADetailEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Entry containing details statistics of operations and errors that occurred at the DSA" INDEX { dsaApplicationDetailIndex } ::= {dsaDetailTable 1} DSADetailEntry ::= SEQUENCE { dsaApplicationDetailIndex INTEGER, errorLoopDetected Counter errorSecurityError Counter errorInvalidReferences Counter errorUnableToProceed Counter errorUnwillingToPerform Counter errorOutOfScope Counter errorLoopAvoidance Counter nameErrorNoSuchObject Counter, nameErrorAliasProb Counter, nameErrorAliasDerefProb Counter, chainedReadOps Counter, chainedCompareOps Counter, Expires: January 2, 1994 [Page 16] Internet Draft June 1993 chainedAddEntryOps Counter, chainedRemoveEntryOps Counter, chainedModifyEntryOps Counter, chainedmodifyRDNOps Counter, chainedListOps Counter, chainedSearchOps Counter, chainedOneLevelSearchOps Counter, chainedWholeTreeSearchOps Counter, updateErrorsAffectsMultipleDSAs Counter, errorUnavailableCriticalExtension Counter, timeLimitExceeded Counter, sizeLimitExceeded Counter, adminLimitExceeded Counter } dsaApplicationDetailIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Reference into application table to allow correlation with general application parameters" ::= {dsaDetailEntry 1} errorLoopDetected OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operation forwarded to this DSA in which a loop was detected. Note that, this check is performed immediately on reciept of the request, and will occur only in cases of requests from other DSAs. A serviceError of type loopDetected is originated at the DSA in Expires: January 2, 1994 [Page 17] Internet Draft June 1993 such cases." ::= {dsaDetailEntry 2} errorSecurityError OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations forwarded to this DSA which did not meet the security requirements " ::= {dsaDetailEntry 3} errorInvalidReferences OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of invalid knowledge references made to the DSA. A serviceError of type invalidReference is originated at the DSA in such cases." ::= {dsaDetailEntry 4} errorUnableToProceed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations forwarded to the DSA for which the pertinent information is not held by the DSA. A serviceError of type unableToProceed is originated at the DSA in such cases." ::= {dsaDetailEntry 5} errorOutOfScope OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of cases where referrals were not made as it was outside the scopeOfReferral. A serviceError of type outOfScope is originated at the DSA in such cases. " ::= {dsaDetailEntry 6} errorLoopAvoidance OBJECT-TYPE SYNTAX INTEGER ACCESS read-only Expires: January 2, 1994 [Page 18] Internet Draft June 1993 STATUS mandatory DESCRIPTION " number of chainings that were not carried out to avoid a loop. Note that this is done by the DSA before forwarding the operation to another DSA. A serviceError of type loopDetected is originated at the DSA in such cases. " ::= {dsaDetailEntry 7} nameErrorNoSuchObject OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of operations in which the purported name is determined to be invalid. A nameError of type noSuchObject is originated at the DSA in such cases. " ::= {dsaDetailEntry 8} nameErrorAliasProb OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of instances in which the dereferenced alias names no object.A nameError of type aliasProblem is originated at the DSA in such cases." ::= {dsaDetailEntry 9} nameErrorAliasDerefProb OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of instances in which an alias is encountered in a situation where it is not allowed. A nameError of type aliasDereferen- cingProblem is originated at the DSA in such cases." ::= {dsaDetailEntry 10} chainedReadOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION Expires: January 2, 1994 [Page 19] Internet Draft June 1993 " number of read operations from other DSAs since application startup." ::= {dsaDetailEntry 11} chainedCompareOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of compare operations from other DSAs since application startup." ::= {dsaDetailEntry 12} chainedAddEntryOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of addEntry operations from DSAs since application startup." ::= {dsaDetailEntry 13} chainedRemoveEntryOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of removeEntry operations from DSAs since application startup." ::= {dsaDetailEntry 14} chainedModifyEntryOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of modifyEntry operations from DSAs since application startup." ::= {dsaDetailEntry 15} chainedmodifyRDNOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of modifyRDN operations from DSAs since application startup." ::= {dsaDetailEntry 16} Expires: January 2, 1994 [Page 20] Internet Draft June 1993 chainedListOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of list operations from DSAs since application startup." ::= {dsaDetailEntry 17} chainedSearchOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of search operations from DSAs since application startup." ::= {dsaDetailEntry 18} chainedOneLevelSearchOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of oneLevelSearch operations from DSAs since application startup." ::= {dsaDetailEntry 19} chainedWholeTreeSearchOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of wholeTreeSearch operations from DSAs since application startup." ::= {dsaDetailEntry 20} updateErrorsAffectsMultipleDSAs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of affectsMultipleDSAs updateErrors from DUAs since application startup." ::= {dsaDetailEntry 21} errorUnavailableCriticalExtension OBJECT-TYPE SYNTAX INTEGER ACCESS read-only Expires: January 2, 1994 [Page 21] Internet Draft June 1993 STATUS mandatory DESCRIPTION " number of ServiceErrors of type Unavailable- CriticalExtension originated from this DSA since application startup." ::= {dsaDetailEntry 22} chainedAbandonOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of chainedAbandon operations forwarded to this DSA since application startup." ::= {dsaDetailEntry 23} timeLimitExceeded OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of serviceErrors of type timeLimitExceeded originated at this DSA since application startup." ::= {dsaDetailEntry 24} sizeLimitExceeded OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of serviceErrors of type sizeLimitExceeded originated at this DSA since application startup." ::= {dsaDetailEntry 25} adminLimitExceeded OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION " number of serviceErrors of type adminLimitExceeded originated at this DSA since application startup." ::= {dsaDetailEntry 26} Expires: January 2, 1994 [Page 22] Internet Draft June 1993 -- The DSAInfo table contains statistical data on the DSAs -- with which it [attempts to] interact. This table will -- provide a useful insight into the effect of neighbours -- on the DSA performance. -- Due to resource constraints it may be necessary to -- delete entries. It is suggested that the least recently -- used entries be deleted first. dsaInfoTable OBJECT-TYPE SYNTAX SEQUENCE OF dsaInfoEntry ACCESS read-only STATUS mandatory ::= { application-mib 5 } dsaInfoEntry OBJECT-TYPE SYNTAX DsaInfoEntry ACCESS read-only STATUS mandatory ::= { dsaInfoTable 1 } DsaInfoEntry ::= SEQUENCE { dsaName DistinguishedName, timeOfCreation TimeTicks, timeOfLastAttempt TimeTicks, timeOfLastSuccess TimeTicks, failuresSinceLastSuccess Counter, failures Counter, successes Counter } dsaName OBJECT-TYPE SYNTAX DistinguishedName ACCESS read-only STATUS mandatory DESCRIPTION " distinguished name of the DSA to which this entry pertains." ::= {dsaInfoEntry 1} timeOfCreation OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only Expires: January 2, 1994 [Page 23] Internet Draft June 1993 STATUS mandatory DESCRIPTION " Time at which this entry was created." ::= {dsaInfoEntry 2} timeOfLastAttempt OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION " Time at which the last attempt was made to contact this DSA." ::= {dsaInfoEntry 3} timeOfLastSuccess OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION " Time at which the last attempt made to contact this DSA was successful. If there have been no successful attempts this entry will be 0" ::= {dsaInfoEntry 4} failuresSinceLastSuccess OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION " The number of failures since the last time an attempt to contact this DSA was successful." ::= {dsaInfoEntry 5} failures OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION " cumulative failures since the creation of this entry." ::= {dsaInfoEntry 6} successes OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION Expires: January 2, 1994 [Page 24] Internet Draft June 1993 " cumulative successes since the creation of this entry." ::= {dsaInfoEntry 7} -- Traps for use by DSAs -- Traps are defined using the conventions in RFC 1215 . dsaAuthnTrap TRAP-TYPE ENTERPRISE AIC VARIABLES { dsaName dsaDN } DESCRIPTION "This trap is sent whenever a managed DSA detects an attempted security violation." REFERENCE "Reference X.500 specifications." ::= 1 dsaGoingDown TRAP-TYPE ENTERPRISE AIC VARIABLES { dsaName dsaDN } DESCRIPTION "This trap is sent whenever a managed DSA is going down aborting/restarting/ exiting .." REFERENCE ::= 2 dsaComingUp TRAP-TYPE ENTERPRISE AIC VARIABLES { dsaName dsaDN } DESCRIPTION "This trap is sent whenever a managed DSA is coming up starting/restarting/ .." REFERENCE ::= 3 END 6. Acknowledgements ==================== This draft is the product of discussions and deliberations carried out in the following working groups ietf-madman-wg ietf-madman@innosoft.com wide-isode-wg isode-wg@wide.ad.jp wide-netman-wg netman-wg@wide.ad.jp Expires: January 2, 1994 [Page 25] Internet Draft June 1993 7. References ============== [1] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", STD 16, RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990. [2] Case, J., M. Fedor, M. Schoffstall, and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990. [3] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991. [4] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", STD 16, RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991. [5] The X.500 blue book. [6] Freed, N., Kille, S., The Network Services Monitoring MIB, Internet Draft, May 17, 1993. [7] Austein, R., Saperia J., DNS MIB Extensions, Internet Draft, 12 Nov, 1992. [8] Grillo, P., Waldbusser, S., HostResources MIB, Internet Draft, Dec, 1992. Expires: January 2, 1994 [Page 26]