---
title: Mirroring configuration changes
description: Configure cluster names to mirror configuration changes automatically across servers in the same topology.
component: pingdirectory
version: 11.1
page_id: pingdirectory:pingdirectory_server_administration_guide:pd_ds_topology_mirror_config
canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/pingdirectory_server_administration_guide/pd_ds_topology_mirror_config.html
llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: July 23, 2026
section_ids:
  before-you-begin: Before you begin
  steps: Steps
  choose-from: Choose from:
---

# Mirroring configuration changes

By default, each server is assigned a unique cluster name during installation. In this mode, configuration changes made using `dsconfig` or the admin console apply only to the server where the change is made, and must be repeated on every server in the topology. This is the recommended approach in a DevOps model, where server profiles and automation manage configuration.

For on-premise deployments, you can assign all servers in the topology the same cluster name so that configuration changes propagate automatically. Configuration objects that are mirrored across the topology are marked with a cluster (![An icon showing computers in a clustered topology.](_images/admin-console-cluster-icon.png)) icon on the **Configuration** page in the admin console. You can also find these configuration objects by running `bin/dsconfig` in [Expert mode](pd_ds_change_dsconfig_object_menu.html) and viewing the `Cluster-Wide Configuration` section.

## Before you begin

The servers must already be members of the same topology, but data replication isn't required. To confirm topology membership, go to **Configuration** > **Server Instances**. This page lists every server currently in the topology and its cluster name.

Servers join a topology using `dsreplication enable`, `manage-topology`, or at setup time. Learn more in steps 1 - 14 of [Deploying a basic replication topology](pd_ds_deploy_basic_replication_topology.html).

## Steps

* To enable configuration change mirroring, set the `cluster-name` property to the same value on every server in the topology:

  ### Choose from:

  * Using the CLI:

    1. Run the following command against each server in the topology:

       ```shell
       $ bin/dsconfig set-server-instance-prop \
         --instance-name <server-instance-name> \
         --set cluster-name:<shared-cluster-name> \
         --no-prompt
       ```

       The CLI displays the following message after each successful command execution:

       ```
       The mirrored operation was applied on the topology

       The Directory Server Instance was modified successfully
       ```

    2. Verify that the value of `cluster-name` matches across all topology instances by running the following command on any server in the topology:

       ```shell
       $ bin/dsconfig list-server-instances
       ```

       Here's a sample view of a successfully clustered topology:

       ```
       Server Instance : Type      : server-instance-name : cluster-name
       ----------------:-----------:----------------------:-------------
       DS1             : directory : DS1                  : CoS_cluster
       DS2             : directory : DS2                  : CoS_cluster
       ```

  * Using the admin console (from any server in the topology):

    1. In the sidebar, click **Configuration**.

    2. Enable the **Show all configuration** toggle.

    3. In the **Topology** list, select **Server Instances**.

    4. On the **Server Instances** page, select the server name.

    5. Update the **Cluster Name** field and click **Save**.

    6. Repeat steps 4 - 5 for each server in the topology. The value of **Cluster Name** should match across all servers in the topology, as shown in the following image:

       ![A screenshot of the PingDirectory admin console with matching Cluster Name values for all three server instances in the topology.](_images/admin-console-cluster-name.png)