As per Relevance of the word monitoring, we have this rfc below:
Network Working Group G.
Request for Comments: 1567 AIC Systems
Category: Standards Track S.
ISODE
January 1994
X.500 Directory Monitoring
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
This document defines a portion of the Management Information
(MIB). It defines the MIB for monitoring Directory System
(DSA), a component of the OSI Directory. This MIB will be used
conjunction with the APPLICATION-MIB for monitoring DSAs
Table of
1. The SNMPv2 Network Management Framework ....................... 1
2. MIB Model for DSA Management ................................. 2
3. The DSA functions and operations .............................. 2
4. MIB design .................................................... 3
5. The Directory Monitoring MIB .................................. 3
6. Acknowledgements ..............................................17
7. References ....................................................17
Security Considerations ...........................................18
Authors' Addresses ................................................18
1. The SNMPv2 Network Management
The major components of the SNMPv2 Network Management framework
described in the documents listed below
o RFC 1442 [1] defines the Structure of Management
(SMI), the mechanisms used for describing and naming
for the purpose of management
o STD 17, RFC 1213 [2] defines MIB-II, the core set of
objects (MO) for the Internet suite of protocols
Mansfield & Kille [Page 1]
RFC 1567 X.500 Directory Monitoring MIB January 1994
o RFC 1445 [3] defines the administrative and
architectural aspects of the management framework
o RFC 1448 [4] defines the protocol used for network access
managed objects
The framework is adaptable/extensible by defining new MIBs to
the requirements of specific applications/protocols/situations
Managed objects are accessed via a virtual information store,
MIB. Objects in the MIB are defined using the subset of
Syntax Notation One (ASN.1) defined in the SMI. In particular,
object type is named by an OBJECT IDENTIFIER, which is
administratively assigned name. The object type together with
object instance serves to uniquely identify a specific
of the object. For human convenience, often a textual string,
the descriptor, is used to refer to the object type
2. MIB Model for DSA
A DSA-manager may wish to monitor several aspects of the
DSA. He/she may want to know the process related aspects-
resource utilization of the operational DSA; the network
related aspects e.g., inbound-associations, outbound-associations
operational status, and finally the information specific to the
application - its operations and performance
The MIB defined in this document covers the portion which is
to the DSA-application. The network service related part of the MIB
and the host-resources related part of the MIB, as well other
of interest to a Manager monitoring the DSA-application, are
in separate documents [6] [7].
3. The DSA functions and
The Directory System Agent [DSA], a component of the OSI-
[5] [9], is an application process. It provides access to
Directory Information Base [DIB] to Directory User Agents [DUA
and/or other DSAs. Functionally , a User [DUA] and the Directory
bound together for a period of time at an access point to
Directory [DSA]. A DSA may use information stored in its
database or interact with (chain the request to) other DSAs
service requirements. Alternatively, a DSA may return a reference
another DSA
The local database of a DSA consists of the part of the DIT that
mastered by the DSA, the part of the DIT for which it keeps
copies and cached information that is gathered during the
Mansfield & Kille [Page 2]
RFC 1567 X.500 Directory Monitoring MIB January 1994
of the DSA
The specific operations carried out by the DSA are: Read, Compare
AddEntry, ModifyEntry, ModifyRDN, RemoveEntry, List, Search. There
also the special operation Abandon. In response to requests
and/or errors are returned by the DSA
4. MIB
The basic principle has been to keep the MIB as simple as possible
The Managed objects included in the MIB are divided into three
- dsaOpsTable, dsaEntryTable and dsaIntTable
- The dsaOpsTable provides summary statistics on the accesses
operations and errors
- The dsaEntriesTable provides summary statistics on the
held by the DSA and on cache performance
- The dsaIntTable provides some useful information on
interaction of the monitored DSA with peer DSAs
There are references to the Directory itself for static
pertaining to the DSA. These references are in the form of "
Distinguished Name" [8] of the corresponding object. It is
that DSA management applications will use these references to
further related information on the objects of interest
5. The Directory Monitoring
DSA-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE
NOTIFICATION-
FROM SNMPv2-
DisplayString, TimeStamp
TEXTUAL-
FROM SNMPv2-
mib-2
FROM RFC1213-
applIndex,
FROM APPLICATION-MIB
dsaMIB MODULE-
LAST-UPDATED "9311250000Z
ORGANIZATION "IETF Mail and Directory Management
Group
Mansfield & Kille [Page 3]
RFC 1567 X.500 Directory Monitoring MIB January 1994
CONTACT-
" Glenn
Postal: AIC Systems
6-6-3, Minami
Aoba-ku, Sendai, 989-32
Tel: +81 22 279 3310
Fax: +81 22 279 3640
E-Mail: glenn@aic.co.jp
" The MIB module for monitoring Directory System Agents."
::= { mib-2 29 }
dsaOpsTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
" The table holding information related to
DSA operations."
::= {dsaMIB 1}
dsaOpsEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
" Entry containing operations related
for a DSA."
INDEX { applIndex }
::= {dsaOpsTable 1}
DsaOpsEntry ::= SEQUENCE {
--
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Mansfield & Kille [Page 4]
RFC 1567 X.500 Directory Monitoring MIB January 1994
-- In-coming
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
-- Out going
Counter32,
Counter32,
--
Counter32,
Counter32
}
dsaAnonymousBinds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of anonymous binds to this DSA from
since application start."
::= {dsaOpsEntry 1}
Mansfield & Kille [Page 5]
RFC 1567 X.500 Directory Monitoring MIB January 1994
dsaUnauthBinds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of un-authenticated binds to
DSA since application start."
::= {dsaOpsEntry 2}
dsaSimpleAuthBinds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of binds to this DSA that were
using simple authentication procedures
application start."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 8.1.2.1.1."
::= {dsaOpsEntry 3}
dsaStrongAuthBinds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of binds to this DSA that were
using the strong authentication procedures
application start. This includes the binds that
authenticated using external authentication procedures."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Sections 8.1.2.1.2 & 8.1.2.1.3."
::= {dsaOpsEntry 4}
dsaBindSecurityErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of bind operations that have been
by this DSA due to inappropriateAuthentication
invalidCredentials."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 12.7.2"
Mansfield & Kille [Page 6]
RFC 1567 X.500 Directory Monitoring MIB January 1994
::= {dsaOpsEntry 5}
dsaInOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of operations forwarded to this
from DUAs or other DSAs since
start up."
::= {dsaOpsEntry 6}
dsaReadOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of read operations serviced
this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 9.1."
::= {dsaOpsEntry 7}
dsaCompareOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of compare operations serviced
this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 9.2."
::= {dsaOpsEntry 8}
dsaAddEntryOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of addEntry operations serviced
this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 11.1."
::= {dsaOpsEntry 9}
Mansfield & Kille [Page 7]
RFC 1567 X.500 Directory Monitoring MIB January 1994
dsaRemoveEntryOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of removeEntry operations serviced
this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 11.2."
::= {dsaOpsEntry 10}
dsaModifyEntryOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of modifyEntry operations serviced
this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 11.3."
::= {dsaOpsEntry 11}
dsaModifyRDNOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of modifyRDN operations serviced
this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 11.4."
::= {dsaOpsEntry 12}
dsaListOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of list operations serviced
this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 10.1."
::= {dsaOpsEntry 13}
Mansfield & Kille [Page 8]
RFC 1567 X.500 Directory Monitoring MIB January 1994
dsaSearchOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of search operations- baseObjectSearches
oneLevelSearches and subTreeSearches,
by this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 10.2."
::= {dsaOpsEntry 14}
dsaOneLevelSearchOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of oneLevelSearch operations
by this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 10.2.2.2."
::= {dsaOpsEntry 15}
dsaWholeTreeSearchOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of wholeTreeSearch operations
by this DSA since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 10.2.2.2."
::= {dsaOpsEntry 16}
dsaReferrals OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of referrals returned by this DSA in
to requests for operations since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 12.6."
::= {dsaOpsEntry 17}
Mansfield & Kille [Page 9]
RFC 1567 X.500 Directory Monitoring MIB January 1994
dsaChainings OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of operations forwarded by this
to other DSAs since application startup."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.518, 1988:
Section 14."
::= {dsaOpsEntry 18}
dsaSecurityErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of operations forwarded to this
which did not meet the security requirements. "
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Section 12.7."
::= {dsaOpsEntry 19}
dsaErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of operations that could not be
due to errors other than security errors,
referrals
A partially serviced operation will not be
as an error
The errors include NameErrors, UpdateErrors,
errors and ServiceErrors."
" CCITT Blue Book Fascicle VIII.8 - Rec. X.511, 1988:
Sections 12.4, 12.5, 12.8 & 12.9."
::= {dsaOpsEntry 20}
-- Entry statistics/Cache
dsaEntriesTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
" The table holding information related to
Mansfield & Kille [Page 10]
RFC 1567 X.500 Directory Monitoring MIB January 1994
entry statistics and cache performance of the DSAs."
::= {dsaMIB 2}
dsaEntriesEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
" Entry containing statistics pertaining to
held by a DSA."
INDEX { applIndex }
::= {dsaEntriesTable 1}
DsaEntriesEntry ::= SEQUENCE {
Gauge32,
Gauge32,
Gauge32,
Counter32,
Counter32
}
dsaMasterEntries OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
" Number of entries mastered in the DSA."
::= {dsaEntriesEntry 1}
dsaCopyEntries OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
" Number of entries for which systematic (slave
copies are maintained in the DSA."
::= {dsaEntriesEntry 2}
dsaCacheEntries OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
Mansfield & Kille [Page 11]
RFC 1567 X.500 Directory Monitoring MIB January 1994
" Number of entries cached (non-systematic copies)
the DSA. This will include the entries that
cached partially. The negative cache is not counted."
::= {dsaEntriesEntry 3}
dsaCacheHits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of operations that were serviced
the locally held cache since
startup."
::= {dsaEntriesEntry 4}
dsaSlaveHits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Number of operations that were serviced
the locally held object replications [
entries] since application startup."
::= {dsaEntriesEntry 5}
-- The dsaIntTable contains statistical data on the peer
-- with which the monitored DSAs [attempt to] interact.
-- table will provide a useful insight into the effect
-- neighbours on the DSA performance
-- The table keeps track of the last "N" DSAs with which
-- monitored DSAs has interacted [attempted to interact],
-- where "N" is a locally-defined constant
dsaIntTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
" Each row of this table contains some
related to the history of the
of the monitored DSAs with their
peer DSAs."
::= { dsaMIB 3 }
dsaIntEntry OBJECT-
SYNTAX
MAX-ACCESS not-
Mansfield & Kille [Page 12]
RFC 1567 X.500 Directory Monitoring MIB January 1994
STATUS
" Entry containing interaction details of a
with a peer DSA."
INDEX { applIndex,dsaIntIndex }
::= { dsaIntTable 1 }
DsaIntEntry ::= SEQUENCE {
INTEGER
DistinguishedName
TimeStamp
TimeStamp
TimeStamp
Counter32,
Counter32,
Counter32
}
dsaIntIndex OBJECT-
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-
STATUS
" Together with applIndex it forms the unique key
identify the conceptual row which contains useful
on the (attempted) interaction between the DSA (
to by applIndex) and a peer DSA."
::= {dsaIntEntry 1}
dsaName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
" Distinguished Name of the peer DSA to which
entry pertains."
::= {dsaIntEntry 2}
dsaTimeOfCreation OBJECT-
SYNTAX
Mansfield & Kille [Page 13]
RFC 1567 X.500 Directory Monitoring MIB January 1994
MAX-ACCESS read-
STATUS
" The value of sysUpTime when this row was created
If the entry was created before the network
subsystem was initialized, this object will
a value of zero."
::= {dsaIntEntry 3}
dsaTimeOfLastAttempt OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
" The value of sysUpTime when the last attempt was
to contact this DSA. If the last attempt was made
the network management subsystem was initialized,
object will contain a value of zero."
::= {dsaIntEntry 4}
dsaTimeOfLastSuccess OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
" The value of sysUpTime when the last attempt made
contact this DSA was successful. If there
been no successful attempts this entry will have a
of zero. If the last successful attempt was made
the network management subsystem was initialized,
object will contain a value of zero."
::= {dsaIntEntry 5}
dsaFailuresSinceLastSuccess OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" The number of failures since the last time
attempt to contact this DSA was successful.
there has been no successful attempts, this
will contain the number of failures since this
was created."
::= {dsaIntEntry 6}
dsaFailures OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
Mansfield & Kille [Page 14]
RFC 1567 X.500 Directory Monitoring MIB January 1994
STATUS
" Cumulative failures since the creation
this entry."
::= {dsaIntEntry 7}
dsaSuccesses OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
" Cumulative successes since the creation
this entry."
::= {dsaIntEntry 8}
-- Conformance
dsaConformance OBJECT IDENTIFIER ::= { dsaMIB 4 }
dsaGroups OBJECT IDENTIFIER ::= { dsaConformance 1 }
dsaCompliances OBJECT IDENTIFIER ::= { dsaConformance 2 }
-- Compliance
dsaOpsCompliance MODULE-
STATUS
"The compliance statement for SNMPv2
which implement the DSA-MIB for
DSA operations."
MODULE -- this
MANDATORY-GROUPS { dsaOpsGroup }
::= { dsaCompliances 1 }
dsaEntryCompliance MODULE-
STATUS
"The compliance statement for SNMPv2
which implement the DSA-MIB for
DSA operations, entry statistics and
performance."
MODULE -- this
MANDATORY-GROUPS { dsaOpsGroup,dsaEntryGroup }
Mansfield & Kille [Page 15]
RFC 1567 X.500 Directory Monitoring MIB January 1994
::= { dsaCompliances 2 }
dsaIntCompliance MODULE-
STATUS
" The compliance statement for SNMPv2
which implement the DSA-MIB for monitoring
operations and the interaction of the DSA
peer DSAs."
MODULE -- this
MANDATORY-GROUPS { dsaOpsGroup, dsaIntGroup }
::= { dsaCompliances 3 }
-- Units of
dsaOpsGroup OBJECT-
OBJECTS {
dsaAnonymousBinds, dsaUnauthBinds, dsaSimpleAuthBinds
dsaStrongAuthBinds, dsaBindSecurityErrors,dsaInOps
dsaReadOps, dsaCompareOps, dsaAddEntryOps
dsaRemoveEntryOps, dsaModifyEntryOps, dsaModifyRDNOps
dsaListOps, dsaSearchOps, dsaOneLevelSearchOps
dsaWholeTreeSearchOps,dsaReferrals, dsaChainings
dsaSecurityErrors, dsaErrors
STATUS
" A collection of objects for monitoring the
operations."
::= { dsaGroups 1 }
dsaEntryGroup OBJECT-
OBJECTS {dsaMasterEntries, dsaCopyEntries, dsaCacheEntries
dsaCacheHits, dsaSlaveHits
STATUS
" A collection of objects for monitoring the
entry statistics and cache performance."
::= { dsaGroups 2 }
dsaIntGroup OBJECT-
OBJECTS {
dsaName, dsaTimeOfCreation, dsaTimeOfLastAttempt
dsaTimeOfLastSuccess,dsaFailuresSinceLastSuccess,dsaFailures
dsaSuccesses
STATUS
Mansfield & Kille [Page 16]
RFC 1567 X.500 Directory Monitoring MIB January 1994
" A collection of objects for monitoring the DSA'
interaction with peer DSAs."
::= { dsaGroups 3 }
6.
This draft is the product of discussions and deliberations
out in the following working groups
ietf-madman-wg ietf-madman@innosoft.
wide-isode-wg isode-wg@wide.ad.
wide-netman-wg netman-wg@wide.ad.
7.
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "
of Management Information for version 2 of the Simple
Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc.,
Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie
University, April 1993.
[2] McCloghrie, K., and M. Rose, Editors, "Management
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, Hughes LAN Systems, Performance
International, March 1991.
[3] Galvin, J., and K. McCloghrie, "Administrative Model for
2 of the Simple Network Management Protocol (SNMPv2)", RFC 1445,
Trusted Information Systems, Hughes LAN Systems, April 1993.
[4] Case, J., McCloghrie, K., Rose, M., and S, Waldbusser, "
Operations for version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes
Systems, Dover Beach Consulting, Inc., Carnegie
University, April 1993.
[5] CCITT Blue Book, "Data Communication Networks: Directory",
Recommendations X.500-X.521, December 1988.
[6] Kille, S., WG Chair, and N. Freed, Editor, "The Network
Monitoring MIB", RFC 1565, ISODE Consortium, Innosoft,
1994.
Mansfield & Kille [Page 17]
RFC 1567 X.500 Directory Monitoring MIB January 1994
[7] Grillo, P., and S. Waldbusser, "Host Resources MIB", RFC 1514,
Network Innovations, Intel Corporation, Carnegie
University, September 1993.
[8] Kille, S., "A String Representation of Distinguished Names (OSI
DS 23 (v5))", RFC 1485, ISODE Consortium, July 1993.
[9] Kille, S., Huizer, E., Cerf, V., Hobby, R., and S. Kent, "
Strategic Plan for Deploying an Internet X.500
Service", RFC 1430, ISODE Consortium, SURFnet bv, Corporation
National Research Initiatives, University of California, Davis
Bolt, Beranek and Newman, February 1993.
Security
Security issues are not discussed in this memo
Authors'
Glenn
AIC Systems
6-6-3 Minami
Aoba-ku, Sendai 989-32
Phone: +81-22-279-3310
EMail: glenn@aic.co.
Steve E.
ISODE
The Dome, The
Richmond TW9 1
Phone: +44-81-332-9091
EMail: S.Kille@isode.
Mansfield & Kille [Page 18]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
