> - Downloads
> - Promoting a Secondary Database to a Primary Role in a Configuration with One Primary Database with the C-Web Interface
> - Related Topics
> - Promoting a Secondary Database to a Primary Role in a Configuration with One Primary Database (SRC CLI)
> - Adding a Juniper Networks Database to an Established Community (SRC CLI)
> - Configuring the Juniper Networks Database to Run in Community Mode with the C-Web Interface
> - Updating Data on a Juniper Networks Database with the C-Web Interface
> - Recovering Data in a Community with One Primary Database and One Secondary Database with the C-Web Interface

> # 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:

> 1. On the database that has a secondary role, set the role to primary.
>    1. Click Configure, expand System LDAP>Server, and then click Community.

>       The Community pane appears.

>    2. In the Primary Neighbors box, verify whether the other database is listed as a primary neighbor. If it is not, add it.
>    3. In the Role box, select Primary, and click Apply.
>    4. In the side pane, click Commit.
> 2. On the existing database that has a primary role, remove the neighbor as secondary and add it as primary.
>    1. Click Configure, expand System LDAP>Server, and then click Community.

>       The Community pane appears.

>    2. In the Secondary Neighbors box, remove the database listed.
>    3. In the Primary Neighbors box, add the other database in the community, and click Apply.
>    4. In the side pane, click Commit.
> 3. (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.
>    1. Click Configure, expand System LDAP>Server, and then click Community.

>       The Community pane appears.

>    2. In the Primary Neighbors box, remove the database that is to become the secondary database.
>    3. In the Secondary Neighbors box, add the database, and click Apply.
>    4. In the side pane, click Commit.

> #### Published: 2009-09-18

> Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.