The following table provides a description of the attributes in the cn=Direct LDAP Server monitor entry.
The following is the distinguished name (DN) for the monitor entry.
dn: cn=Direct LDAP Server <baseDN> <host name:ldapPort> <serverID>,cn=monitor
Monitor Attribute | Description |
---|---|
|
Replica ID number. |
|
Number of changes that the replication server has not seen from the server. |
|
Number of missing changes. |
|
Difference between the time of the last change that the replication server has seen from the LDAP server and the most current timestamp on the latest change on the server. |
|
Base DN |
|
Flag to indicate if SSL encryption is in use. |
|
Displays the replication protocol version. |
|
Generation ID for the base DN on the Directory Server. |
|
Boolean that indicates whether the replication domain is restricted in an Entry Balancing Configuration with the Directory Proxy Server. |
|
Number of acknowledgment messages sent to this replica not currently used. |
|
Number of acknowledgment messages received from this replica not currently used. |
|
Number of protocol messages with an |
|
Number of protocol messages with an |
|
Number of protocol messages with an |
|
Number of protocol messages with an |
|
Number of done messages sent to this replica. A done message indicates an end of an online initialization session. If the value is non-zero, then this replica has been initialized over the replication protocol. |
|
Number of done messages received from this replica. A done message indicates an end of online initialization session. If the value is non-zero, then this replica has completed the initialization of other replicas over the replication protocol. |
|
Number of entry messages sent to this replica. Entry messages carry replicated data to initialize replicas over the replication protocol. |
|
Number of entry messages received from this replica. Entry messages carry replicated data to initialize replicas over the replication protocol. |
|
Number of error messages sent to this replica. |
|
Number of error messages received from this replica. |
|
Number of heartbeat messages sent to this replica. |
|
Number of heartbeat messages received from this replica. Note:
The number of messages should always be 0 because the replica never sends a heartbeat message to the server. |
|
Number of initialize-request messages sent to this replica. This message is sent when another replica requested initialization of its data using the replication protocol. |
|
Number of initialize-request messages received from this replica. This message is sent when this replica requested initialization of its data using the replication protocol from another replica. |
|
Number of initialize-target messages sent to this replica. This message is sent before another replica has started the initialization of this replica. |
|
Number of initialize-target messages received from this replica. This message is sent before this replica starts the initialization of one or more replicas. |
|
The host name and port of the local replication server. |
|
Number of protocol messages with an |
|
Number of protocol messages with an |
|
Number of protocol messages with an |
|
Number of protocol messages with an |
|
Number of replication-server-start messages sent to this replica. The Replication Server responds with this message to the start message received from the replica. Note:
The number of messages should never be more than 1. |
|
Number of replication-server-start messages received from this replica. Note:
The number of messages should always be 0. |
|
Number of reset generation ID messages received from this replica. |
|
Number of reset generation ID messages sent to this replica. Note:
The number of messages should always be 0. |
|
Number of server-start messages sent to this replica. Note:
The number of messages should always be 0. |
|
Number of server-start messages received from this replica. Server-start
is the first message the replica sends after establishing a replication
connection. Note:
The number of messages should never be more than 1. |
|
Number of window messages sent to this replica. Window messages are used for cumulative acknowledgment in the replication protocol. |
|
Number of window messages received from this replica. Window messages are used for cumulative acknowledgment in the replication protocol. |
|
Number of window probe messages sent to this replica. Note:
The number of messages should always be 0. |
|
Number of window probe messages received from this replica. The replica sends a window probe message to the server if the send window in the replica is closed and the replica is unable to publish updates to the server. |
|
Number of changes sent to this server. |
|
Number of changes received from this server. |
|
Indicates if the replica is in the same process as the replication server. |
|
Displays the state of the replica. Displays the latest change number that the replica has seen from all the other replicas including itself. |
|
Rate that the connected Directory Server is consuming updates sent by this replication server, expressed as the number of updates per second and measured over the last five seconds. |
|
Highest rate that the connected Directory Server has consumed updates sent by this replication server, measured over a 5 second period from the start of the replication server. |
|
Rate that the connected Directory Server has sent updates to this replication server, expressed as the number of updates per second and measured over the last 5 seconds. |
|
Highest rate that the connected Directory Server has sent updates to this replication server, measured over a 5 second period from the start of the replication server. |
|
Maximum number of changes that can send to the LDAP server before requiring an ACK. |
|
Current number of changes remaining to be sent to the LDAP server before requiring an ACK. |
|
Maximum number of changes that can be received by the LDAP server before sending an ACK. |
|
Number of changes remaining to be received by the LDAP server before sending an ACK. |
|
Indicates that the generation ID of the replica does not match the
generation ID of the server. When loading data into the topology, this is
a temporary state. If this is not a temporary state, the replica has not
been initialized.
Note:
The |