IBM Support

Enabling replication with primary_cluster_addr and primary_api_addr as needed

Troubleshooting


Problem

Introduction

The article will focus on enabling replication on the primary and secondary vault clusters using the primary_cluster_addr and primary_api_addr respectively.

When the primary's cluster address is not directly accessible and must be accessed via an alternate path/address, such as through a TCP-based load balancer, primary_cluster_addr is specified when enabling replication on the primary cluster.

When enabling replication in primary mode:

primary_cluster_addr (string: "") – Specifies the cluster address that the primary gives to secondary nodes. If not set, uses vault's configured cluster address.

  • To enable replication on a DR primary cluster using primary_cluster_addr :
vault write -f sys/replication/dr/primary/enable primary_cluster_addr=https://vault-c7f79654cd-478f28491.elb.us-west-1.amazonaws.com:8201

where primary_cluster_addr is the address of the loadbalancer for the primary cluster pointing to port 8201.

  • To enable replication on a Performance primary cluster using primary_cluster_addr :
vault write -f sys/replication/performance/primary/enable primary_cluster_addr=https://vault-c7f79654cd-478f28491.elb.us-west-1.amazonaws.com:8201

When the primary's redirect address is not directly accessible and must be accessed via an alternate path/address, such as through a load balancer, primary_api_addr is specified when enabling replication on the secondary cluster.

When enabling replication in secondary mode:

primary_api_addr (string: "") – Set this to the API address (normal Vault address) to override the value embedded in the token.

  • To enable DR replication on a secondary using a secondary bootstrap token and specifying primary_api_addr :
vault write -f sys/replication/dr/secondary/enable token=$SECONDARY_BOOTSTRAP_TOKEN primary_api_addr=https://vault-c7f79654cd-478f28491.elb.us-west-1.amazonaws.com:8200

where primary_api_addr is the loadbalancer address of the primary vault cluster pointing to port 8200.

  • To enable Perf replication on a secondary using a secondary activation token and specifying primary_api_addr :
vault write -f sys/replication/performance/secondary/enable token=$SECONDARY_BOOTSTRAP_TOKEN primary_api_addr=https://vault-c7f79654cd-478f28491.elb.us-west-1.amazonaws.com:8200

Expected Outcome

Replication should be successfully established between the primary and secondary clusters after enabling

Prerequisites (if applicable)

  • Primary vault cluster address is not directly accessible from the secondary cluster
  • Primary vault cluster redirect address is not directly accessible from the secondary cluster

Use Case

When trying to establish DR or Performance replication between clusters where the cluster address and redirect address of the primary cluster is not directly accessible by the secondary cluster but can be accessed via a TCP-based load balancer

Useful links:

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLC9Y2","label":"IBM Vault Self-Managed"},"ARM Category":[{"code":"a8mgJ0000000E4iQAE","label":"Vault-\u003ECore"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.14.12;1.14.13;1.15.0;1.15.1;1.15.10;1.15.11;1.15.12;1.15.13;1.15.14;1.15.15;1.15.16;1.15.2;1.15.3;1.15.4;1.15.5;1.15.6;1.15.7;1.15.8;1.15.9;1.16.0;1.16.1;1.16.10;1.16.11;1.16.12;1.16.13;1.16.14;1.16.15;1.16.16;1.16.17;1.16.18;1.16.19;1.16.2;1.16.20;1.16.21;1.16.22;1.16.23;1.16.24;1.16.25;1.16.26;1.16.27;1.16.28;1.16.29;1.16.3;1.16.30;1.16.31;1.16.4;1.16.5;1.16.6;1.16.7;1.16.8;1.16.9;1.17.0;1.17.1;1.17.10;1.17.11;1.17.12;1.17.13;1.17.14;1.17.15;1.17.16;1.17.17;1.17.18;1.17.2;1.17.3;1.17.4;1.17.5;1.17.6;1.17.7;1.17.8;1.17.9;1.18.0;1.18.1;1.18.10;1.18.11;1.18.12;1.18.13;1.18.14;1.18.15;1.18.2;1.18.3;1.18.4;1.18.5;1.18.6;1.18.7;1.18.8;1.18.9;1.19.0;1.19.1;1.19.10;1.19.11;1.19.12;1.19.13;1.19.14;1.19.15;1.19.16;1.19.17;1.19.18;1.19.19;1.19.2;1.19.3;1.19.4;1.19.5;1.19.6;1.19.7;1.19.8;1.19.9;1.20.0;1.20.1;1.20.10;1.20.11;1.20.12;1.20.13;1.20.2;1.20.3;1.20.4;1.20.5;1.20.6;1.20.7;1.20.8;1.20.9;1.21.0;1.21.1;1.21.2;1.21.3;1.21.4;1.21.5;1.21.6;1.21.7;1.21.8;2.0.0;2.0.1;2.0.2;2.0.3;4.2.0-5.4.0"}]

Historical Number

7910559648275

Document Information

Modified date:
06 July 2026

UID

ibm17264746