Promoting a Secondary Database to a Primary Role in a Configuration with One Primary Database with the C-Web Interface
Although all communities should have two databases with a primary role, if a community includes one database assigned a primary role and another database assigned a secondary role, promote the database assigned a secondary role to a primary role.
To promote a Juniper Networks database from a secondary role to a primary role:
- In the Primary Neighbors box, verify whether the other database is listed as a primary neighbor. If it is not, add it.
- In the Role box, select Primary, and click Apply.
- In the side pane, click Commit.
- On the existing database that has a primary role, remove the neighbor as secondary and add it as primary.
- In the Secondary Neighbors box, remove the database listed.
- In the Primary Neighbors box, add the other database in the community, and click Apply.
- In the side pane, click Commit.
- (Optional if you have two databases with a primary role in a community) Switch the role of the database that originally had a secondary role back to secondary.
- In the Primary Neighbors box, remove the database that is to become the secondary database.
- In the Secondary Neighbors box, add the database, and click Apply.
- In the side pane, click Commit.
Related Topics
- SRC-PE Getting Started Guide, Chapter 19, Overview of the Juniper Networks Database
- Configuring the Juniper Networks Database to Run in Community Mode with the C-Web Interface