Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All
Related Documentation
- C Series
- Recovering Data in a Community with One Primary Database and One Secondary Database (C-Web Interface)
- Promoting a Secondary Database to a Primary Role in a Configuration with One Primary Database (SRC CLI)
- Troubleshooting Data Synchronization for Juniper Networks Databases (SRC CLI)
- Juniper Networks Database Overview
Recovering Data in a Community with One Primary Database and One Secondary Database (SRC CLI)
In an environment in which a community includes one database assigned a primary role and another database assigned a secondary role, and the primary database is not operative, you must promote the secondary database to primary and reconfigure the inoperative primary database.
- On the database that has a secondary role, set the role
to primary.
For example, if the database on C2 has a secondary role:
user@C2# edit system ldap server community [edit system ldap server community] user@C2# set role primary user@C2# commitC2 already has C1 configured as primary neighbor.
- On the existing database that has a primary role, remove
the neighbor as secondary and add it as primary.
For example, to configure C1 as a primary database with C2 as a primary neighbor:
user@C1# edit system ldap server community [edit system ldap server community] user@C1# set role primary user@C1# delete secondary-neighbors C2 user@C1# set primary-neighbors C2 user@C1# commit
Related Documentation
- C Series
- Recovering Data in a Community with One Primary Database and One Secondary Database (C-Web Interface)
- Promoting a Secondary Database to a Primary Role in a Configuration with One Primary Database (SRC CLI)
- Troubleshooting Data Synchronization for Juniper Networks Databases (SRC CLI)
- Juniper Networks Database Overview
