Summary of the Remote Replication Server Monitor information
Use this topic as a reference for Remote Replication Server Monitor attribute information.
The following is the distinguished name (DN) for the Remote Replication Server monitor entry.
dn: cn=Remote Repl Server <baseDN> <host name:replPort> <serverID>,cn=monitor
The following table provides a description of the attributes in the cn=Remote Repl Server
monitor entry.
Monitor Attribute | Description | ||
---|---|---|---|
|
Host name and replication port number of the Replication Server. |
||
|
Server ID for the Replication Server. |
||
|
Indicates if the remote replication server is available or not. Values: |
||
|
Indicates if sending is paused. Values: |
||
|
Indicates if receiving is paused. Values: |
||
|
Specifies the WAN Gateway priority of the remote replication server. |
||
|
Indicates if the remote replication server is a WAN Gateway. Values: true or false. |
||
|
Indicates if the remote replication server is a desired gateway. Values:
Indicates another server with a higher gateway priority exists or the gateway priority is set to disabled.
Indicates that the remote replication server wants to be a WAN gateway.
Indicates that the remote replication server wants to give up its role as a WAN gateway.
Indicates the remote replication server wants to remain as a gateway server. |
||
|
base DN |
||
|
Flag to indicate if SSL encryption is in use. |
||
|
Replication protocol version. |
||
|
Generation ID for this suffix on this remote replication server. |
||
|
Indicates that remote replication server is in an entry-balancing deployment. |
||
|
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 the remote replication server. A done message indicates an end of online initialization session. |
||
|
Number of done messages received from the remote replication server. A done message indicates an end of online initialization session. |
||
|
Number of entry messages sent to the remote replication server. Entry messages carry replicated data to initialize replicas over the replication protocol. |
||
|
Number of entry messages received from the remote replication server. Entry messages carry replicated data to initialize replicas over the replication protocol. |
||
|
Number of error messages sent to the remote replication server. |
||
|
Number of error messages received from the remote replication server. |
||
|
Number of heartbeat messages sent to the remote replication server. |
||
|
Number of heartbeat messages received from the remote replication server. |
||
|
Number of initialize-request messages sent to the remote replication server. This message is used during online initialization from one replica to another. |
||
|
Number of initialize-request messages received from the remote replication server. This message is used during online initialization from one replica to another. |
||
|
Number of initialize-target messages sent to the remote replication server. This message is used before online initialization from one replica to another. |
||
|
Number of initialize-target messages received from the remote replication server. This message is used before online initialization from one replica to another. |
||
|
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 monitor messages sent to the remote replication server. This message is used when communicating with PingDirectory servers running an earlier release. |
||
|
Number of monitor messages received from the remote replication server. This message is primarily used when communicating with a PingDirectory server running an earlier release. |
||
|
Number of monitor requests sent to the remote replication server. The receiving server responds with a monitor message that includes server’s information about the state of the topology. |
||
|
Number of monitor requests received from the remote replication server. This server responds with a monitor message that includes server’s information about the state of the topology. |
||
|
Number of monitor messages sent to the remote server.
|
||
|
Number of monitor messages received from the remote server.
|
||
|
Number of pause-sending-updates messages sent to the remote server. The remote server must stop sending update messages to this server when receiving this message. |
||
|
Number of |
||
|
Number of
|
||
|
Number of
|
||
|
Number of reset generation ID messages received from the remote replication server. This message is sent before and after the data is initialized in the topology. |
||
|
Number of reset generation ID messages sent to the remote replication server. This message is sent before and after the data is initialized in the topology. |
||
|
Number of replication server information messages sent to the remote replication server. This message tells other replication servers about the replicas directly connected to the sending server. This message is also used to distribute information about the location of replicas. |
||
|
Number of replication server information messages received from the remote replication server. This message tells other replication servers about the replicas directly connected to the sending server. This message is also used to distribute information about the location of replicas. |
||
|
Number of |
||
|
Number of |
||
|
Number of |
||
|
Number of |
||
|
Number of window messages sent to the remote replication server. Window messages are used for cumulative acknowledgment in the replication protocol. |
||
|
Number of window messages received from the remote replication server. Window messages are used for cumulative acknowledgment in the replication protocol. |
||
|
Total number of messages sent. |
||
|
Total number of messages received. |
||
|
Total number of updates sent. |
||
|
Total number of updates received. |
||
|
Displays the server state of the remote replication server. It displays the last change seen on the remote replication server. |
||
|
Rate that the connected PingDirectory server is consuming updates sent by this replication server, expressed as the number of updates per second and measured over the last 5 seconds. |
||
|
Highest rate that the connected PingDirectory server has consumed updates sent by this replication server, measured over a 5 second period from the time the replication server was started. |
||
|
Rate that the connected PingDirectory 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 PingDirectory server has sent updates to this replication server, measured over a 5 second period since the replication server was started. |
||
|
Maximum number of changes that can be sent to the remote replication server before requiring an ACK. |
||
|
Number of changes remaining to be sent to the remote replication server before requiring an ACK. |
||
|
Maximum number of changes that can be received from the remote replication server before sending an ACK. |
||
|
Number of changes remaining to be received from the remote replication server before sending an ACK. |
||
|
Indicates that the generation ID of the replica does not match the generation ID of the remote replication server. This is a temporary state when loading data into the topology or the replica has not been initialized.
|