[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Updating Juniper Networks Database Configuration for an Established Community with One Primary Database

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.

Promoting a Secondary Database 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.

For example, if the database on C20 has a secondary role:

user@C20# edit system ldap server community
[edit system ldap server community]
user@C20# set role primary
user@C20# commit

C20 already has C10 configured as primary neighbor.

  1. On the existing database that has a primary role, remove the neighbor as secondary and add it as primary.

For example, to remove C20 as a secondary neighbor and add it as a primary neighbor for the database on C10:

user@C10# edit system ldap server community
[edit system ldap server community]
user@C10# set primary-neighbors C20
user@C10# commit

  1. (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:
  2. [edit system ldap server community]
    
    user@C20# set role secondary
    
    user@C20# commit
    
    
    

Recovering Data in a Community with One Primary Database and One Secondary Database

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.

  1. On the database that has a secondary role, set the role to primary.

For example, if the database on C20 has a secondary role:

user@C20# edit system ldap server community
[edit system ldap server community]
user@C20# set role primary
user@C20# commit

C20 already has C10 configured as primary neighbor.

  1. On the existing database that has a primary role, remove the neighbor as secondary and add it as primary.

For example, to configure C10 as a primary database with C20 as a primary neighbor:

user@C10# edit system ldap server community
[edit system ldap server community] 
user@C10# set role primary
user@C10# delete secondary-neighbors C20 
user@C10# set primary-neighbors C20
user@C10# commit

[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]