Counter attributes provide statistical information concerning the
activities of the DSA. Typical counters show the number of reads
and modifies that the DSA has processed and the number of errors
reported by the DSA.
All counters are listed below and each described individually.
All the counters are read-only. You can use the SHOW directive
to display counters. For example:
SHOW DSA <counter>
You can specify a list of counters to display. For example:
SHOW DSA <counter1>, <counter2>
You can use the ALL COUNTERS keyword to display all counter
attributes with one directive. For example:
SHOW DSA ALL COUNTERS
1 – Abandon Failures
This counter displays the number of Abandon Failed Errors generated by the DSA. The Abandon service enables a user to indicate that they are no longer interested in the request that they sent to the DSA, perhaps because the request is taking too long. Syntax: SHOW DSA ABANDON FAILURES
2 – Abandon Operations
This counter displays the number of directory ABANDON operations performed by the DSA. A directory ABANDON operation is used only to cancel a Read, Compare, List or Search operation. Syntax: SHOW DSA ABANDON OPERATIONS
3 – Accounting Disabled
This counter displays the number of Accounting Disabled events generated by the DSA. Syntax: SHOW DSA ACCOUNTING DISABLED
4 – Accounting Enabled
This counter displays the number of Accounting Enabled events generated by the DSA. Syntax: SHOW DSA ACCOUNTING ENABLED
5 – Accounting File Access Failures
This counter displays the number of Accounting File Access Failure events generated by the DSA. The Accounting File Access Failure event indicates why the DSA could not access the accounting file, and what type of access the DSA was trying to gain. Syntax: SHOW DSA ACCOUNTING FILE ACCESS FAILURES
6 – Accounting File Rollover
This counter displays the number of Accounting File Rollover events generated by the DSA. Each rollover can be either scheduled or unscheduled. Accounting file rollover involves closing the current accounting file and creating a new accounting file. Syntax: SHOW DSA ACCOUNTING FILE ROLLOVER
7 – Accounting Records Discarded
This counter displays the total number of accounting records that have been discarded by the DSA accounting facility. Syntax: SHOW DSA ACCOUNTING RECORDS DISCARDED
8 – Accounting Start Failures
This counter displays the number of Accounting Start Failure events generated by the DSA. The Accounting Start Failure event indicates that the DSA could not start the accounting facility when requested. Syntax: SHOW DSA ACCOUNTING START FAILURES
9 – Add Entry Operations
This counter displays the number of directory add entry operations requested of the DSA. A directory add entry operation is used to add a new entry to the directory information base. For example, this counter increases with each DXIM CREATE ENTRY command. The counter does not distinguish between operations performed by this DSA, and operations that this DSA passed on to another DSA for processing. Syntax: SHOW DSA ADD ENTRY OPERATIONS
10 – Attribute Errors
This counter displays the number of Attribute Errors generated by the DSA. This counter increases when, for example, a user attempts to violate an attribute constraint, or attempts to show an attribute that does not exist. Syntax: SHOW DSA ATTRIBUTE ERRORS
11 – Authentication Failures
This counter displays the number of Authentication Failure events (see EVENTS) generated by the DSA. Syntax: SHOW DSA AUTHENTICATION FAILURES An Authentication Failure event is issued when the DSA fails to authenticate the originator of a Bind request. This typically means that the originator specified the wrong password, or the password could not be verified by the DSA.
12 – Chained Abandon Operations
This counter displays the number of CHAINED ABANDON operations requested of the DSA. A CHAINED ABANDON requests the DSA to cancel a CHAINED READ, CHAINED SEARCH, CHAINED COMPARE or CHAINED LIST operation that was requested of it previously. Syntax: SHOW DSA CHAINED ABANDON OPERATIONS
13 – Chained Add Entry Operations
This counter displays the number of CHAINED ADD ENTRY operations requested of the DSA. A CHAINED ADD ENTRY operation involves the local DSA receiving an ADD ENTRY operation from another DSA. See Add_Entry_Operations for a description of the ADD ENTRY operation. Syntax: SHOW DSA CHAINED ADD ENTRY OPERATIONS
14 – Chained Binds Accepted
This counter displays the number of bind requests from other DSAs that have been accepted by the DSA. A chained bind enables communication between two DSAs. Syntax: SHOW DSA CHAINED BINDS ACCEPTED
15 – Chained Binds Rejected
This counter displays the number of Bind requests from other DSAs that have been rejected by the DSA. A chained bind enables communication between two DSAs. A DSA can reject a chained bind if it is not ready for communication. Syntax: SHOW DSA CHAINED BINDS REJECTED
16 – Chained Compare Operations
This counter displays the number of CHAINED COMPARE operations requested of the DSA. A CHAINED COMPARE operation involves the local DSA receiving a COMPARE operation from another DSA. See Compare_Operations for a description of the COMPARE operation. Syntax: SHOW DSA CHAINED COMPARE OPERATIONS
17 – Chained List Operations
This counter displays the number of CHAINED LIST operations requested the DSA. A CHAINED LIST operation involves the local DSA receiving a LIST operation from another DSA. See List_Operations for a description of the LIST operation. Syntax: SHOW DSA CHAINED LIST OPERATIONS
18 – Chained Modify Entry Operations
This counter displays the number of CHAINED MODIFY ENTRY operations requested of the DSA. A CHAINED MODIFY ENTRY operation involves the local DSA receiving a MODIFY ENTRY operation from another DSA. See Modify_Entry_Operations for a description of the MODIFY ENTRY operation. Syntax: SHOW DSA CHAINED MODIFY ENTRY OPERATIONS
19 – Chained Modify RDN Operations
This counter displays the number of CHAINED MODIFY RDN operations requested of the DSA. A CHAINED MODIFY RDN operation involves the local DSA receiving a MODIFY RDN operation from another DSA. See Modify_RDN_Operations for a description of the MODIFY RDN operation. Syntax: SHOW DSA CHAINED MODIFY RDN OPERATIONS
20 – Chained Operation Referrals
This counter displays the number of times the DSA has sent a referral to another DSA. The referral contains information about one or more DSAs that might have the information that satisfies a user request. Syntax: SHOW DSA CHAINED OPERATION REFERRALS
21 – Chained Read Operations
This counter displays the number of CHAINED READ operations requested of the DSA. A CHAINED READ operation involves the local DSA receiving a READ operation from another DSA. See Read_Operations for a description of the READ operation. Syntax: SHOW DSA CHAINED READ OPERATIONS
22 – Chained Remove Entry Operations
This counter displays the number of CHAINED REMOVE ENTRY operations requested of the DSA. A CHAINED REMOVE ENTRY operation involves the local DSA receiving a REMOVE ENTRY operation, from another DSA. See Remove_Entry_Operations for a description of the REMOVE ENTRY operation. Syntax: SHOW DSA CHAINED REMOVE ENTRY OPERATIONS
23 – Chained Search Operations
This counter displays the number of CHAINED SEARCH operations requested the DSA. A CHAINED SEARCH operation involves the local DSA receiving a SEARCH operation from another DSA. See Search_Operations for a description of the SEARCH operation. Syntax: SHOW DSA CHAINED SEARCH OPERATIONS
24 – Changes of State
This counter displays the number of State Change events (see EVENTS)
generated by the DSA. The event is generated when, for example,
you use the ENABLE DSA directive. In this case, the DSA changes
from state OFF to state ENABLING and then to state ON, causing two
State Change events.
Syntax:
SHOW DSA CHANGES OF STATE
25 – Compare Operations
This counter displays the number of directory COMPARE operations performed by the DSA. A directory COMPARE operation is used to compare a given entry with a specified directory entry. Syntax: SHOW DSA COMPARE OPERATIONS
26 – Communication Failures
This counter displays the number of communication failures since the DSA was created. Syntax: SHOW DSA COMMUNICATION FAILURES
27 – Create Failures
This counter displays the number of Create Failure events (see EVENTS) generated by the DSA. A Create Failure event is generated when the DSA fails to create the DSA entity. However, because a successful creation is required before you can see the counter, the value of this counter is always 0. Syntax: SHOW DSA CREATE FAILURES
28 – Creation Time
This counter displays the time and date at which the DSA was created. Syntax: SHOW DSA CREATION TIME
29 – DISP Binds Accepted
This counter displays the number of DISP binds the DSA has
accepted from other DSAs. The DISP protocol is used by DSAs
to replicate information.
Syntax:
SHOW DSA DISP BINDS ACCEPTED
30 – DISP Binds Rejected
This counter displays the number of DISP binds the DSA has
rejected. The DISP protocol is used by DSAs to replicate
information. A DISP bind can be rejected due to, for
example, authentication failure.
Syntax:
SHOW DSA DISP BINDS REJECTED
31 – DOP Binds Accepted
This counter displays the number of DOP binds the DSA has
accepted from other DSAs. The DOP protocol is used by the
DSAs to manage shadowing agreements.
Syntax:
SHOW DSA DOP BINDS ACCEPTED
32 – DOP Binds Rejected
This counter displays the number of DOP binds the DSA has
rejected from other DSAs. The DOP protocol is used by the
DSAs to manage shadowing agreements. A DOP bind can be
rejected due to, for example, authentication failure.
Syntax:
SHOW DSA DOP BINDS REJECTED
33 – DUA Binds Accepted
This counter displays the number of Bind requests from directory applications that have been accepted by the DSA. For example, each successful DXIM BIND command causes this counter to increase by one. Syntax: SHOW DSA DUA BINDS ACCEPTED
34 – DUA Binds Rejected
This counter displays the number of Bind requests from directory user applications (DUAs) that have been rejected by the DSA. For example, each unsuccessful DXIM BIND command causes this counter to increase by one. A DSA can reject a Bind request if, for example, it cannot authenticate the user of the application. Syntax: SHOW DSA DUA BINDS REJECTED
35 – Distributed Operation Failures
This counter displays the number of Distributed Operation Failure events (see EVENTS) generated by the DSA. A DSA generates a Distributed Operation Failure event when it fails to establish communication with another DSA for any reason. For example, network problems or authentication problems might cause the DSA to generate this event. Syntax: SHOW DSA DISTRIBUTED OPERATION FAILURES
36 – LDAP Binds Accepted
This counter displays the number of LDAP Binds that the DSA has accepted. Syntax: SHOW DSA LDAP BINDS ACCEPTED
37 – LDAP Binds Rejected
This counter displays the number of LDAP Binds that the DSA has rejected. Syntax: SHOW DSA LDAP BINDS REJECTED
38 – Examples
> SHOW DSA CHAINED BINDS
This command displays the current value of the
CHAINED BIND counter.
> SHOW DSA CHAINED BINDS ACCEPTED, CHAINED BINDS REJECTED
This command displays the current values of the
CHAINED BINDS ACCEPTED and the CHAINED BINDS REJECTED counters.
> SHOW DSA ALL COUNTERS
This command displays the current value of all DSA counters.
39 – Exhausted Resource
This counter displays the number of Resource Exhausted events (see EVENTS) generated by the DSA. A Resource Exhausted event is generated when a DSA detects that a critical resource is exhausted, preventing it from processing a requested operation. Syntax: SHOW DSA EXHAUSTED RESOURCE
40 – Internal Errors
This counter displays the number of Internal Error events (see EVENTS) generated by the DSA. An Internal Error event is generated when the DSA detects an internal error. Syntax: SHOW DSA INTERNAL ERRORS
41 – List Operations
This counter displays the number of directory LIST operations performed by the DSA. A directory LIST operation is used to obtain a list of the immediate subordinates of a specified directory entry. For example, this counter increases with each DXIM SHOW SUBORDINATES command. Syntax: SHOW DSA LIST OPERATIONS
42 – Listen Failures
This counter displays the number of Listen Failure events (see EVENTS) generated by the DSA. The DSA generates this event when something prevents it from setting up its own presentation access point for receiving communications. Syntax: SHOW DSA LISTEN FAILURES
43 – Modify Entry Operations
This counter displays the number of directory modify entry operations performed by the DSA. A directory modify entry operation is used to amend an existing directory entry. For example, this command increases with each DXIM MODIFY ENTRY and DXIM SET ENTRY command. The counter does not distinguish between operations performed by this DSA, and operations that this DSA passed on to another DSA for processing. Syntax: SHOW DSA MODIFY ENTRY OPERATIONS
44 – Modify RDN Operations
This counter displays the number of directory modify RDN operations requested of the DSA. A directory modify RDN operation is used to modify the relative distinguished name (RDN) of a directory entry. For example, this counter increases with each DXIM RENAME ENTRY command. The counter does not distinguish between operations performed by this DSA, and operations that this DSA passed on to another DSA for processing. Syntax: SHOW DSA MODIFY RDN OPERATIONS
45 – Name Errors
This counter displays the number of Name Errors generated by the DSA. This counter increases when, for example, a user specifies a name which is not the name of an entry. Syntax: SHOW DSA NAME ERRORS
46 – Read Operations
This counter displays the number of directory READ operations performed by the DSA. A directory READ operation is used to extract information from a specified directory entry. For example, this counter increases with each DXIM SHOW ENTRY command. Syntax: SHOW DSA READ OPERATIONS
47 – Referrals
This counter displays the number of Referrals generated by the DSA. A referral occurs when a DSA cannot satisfy an operation itself and therefore returns to the application, a reference to another DSA which it believes can process the operation. Syntax: SHOW DSA REFERRALS
48 – Remove Entry Operations
This counter displays the number of directory remove entry operations requested of the DSA. A directory remove entry operation is used to remove a specified entry from the directory information base. For example, this counter increases with each DXIM DELETE ENTRY command. The counter does not distinguish between operations performed by this DSA, and operations that this DSA passed on to another DSA for processing. Syntax: SHOW DSA REMOVE ENTRY OPERATIONS
49 – Results
This counter displays the number of results generated by the DSA. A result is the successful completion of a directory operation. Syntax: SHOW DSA RESULTS
50 – Search Operations
This counter displays the number of directory SEARCH operations performed by the DSA. A directory SEARCH operation is used to search a section of the directory information base for specific information. Syntax: SHOW DSA SEARCH OPERATIONS
51 – Security Errors
This counter displays the number of security errors detected by the DSA. A security error occurs when for example, an end user tries to perform an operation for which they are not authorized. Syntax: SHOW DSA SECURITY ERRORS
52 – Service Errors
This counter displays the number of Service Errors generated by the DSA. A Service Error is issued when an error occurs related to the provision of a service (Read, Compare, and so on). Syntax: SHOW DSA SERVICE ERRORS
53 – Shadow Agreement Update Failures
This counter displays the number of Shadow Agreement Update
Failure events generated by the DSA. The event is generated
when a DSA fails to create, modify, or delete a shadowing
agreement.
Syntax:
SHOW DSA SHADOW AGREEMENT UPDATE FAILURES
54 – Shadow Agreement Updates Completed
This counter displays the number of Shadow Agreement Update
Complete events generated by the DSA. The event is generated
every time a DSA successfully creates, modifies, or deletes
a shadowing agreement.
Syntax:
SHOW DSA SHADOW AGREEMENT UPDATES COMPLETED
55 – Shadow Update Failures
This counter displays the number of Shadow Update Failure events (see EVENTS) generated by the DSA. The Shadow Update Failure event is generated when the DSA fails to update its copy of a naming context. If the DSA fails to copy two or more naming contexts from another DSA, then the failure to copy each naming context causes an event. Syntax: SHOW DSA SHADOW UPDATE FAILURES
56 – Shadow Updates Completed
This counter displays the number of Shadow Update Complete events (see EVENTS) generated by the DSA. The DSA generates the Shadow Update Complete event when it succeeds in copying or updating a naming context from another DSA. If the DSA copies two or more naming contexts from another DSA, then the successful copying of each naming context causes an event. Syntax: SHOW DSA SHADOW UPDATES COMPLETED
57 – Update Errors
This counter displays the number of Update Errors generated by the DSA. This counter increase when, for example, a user attempts to create an entry that already exists. Syntax: SHOW DSA UPDATE ERRORS