• Download PDF: Enabling the Juniper Networks Database to Run in Community Mode (SRC CLI) 

• Related Topics
• Overview of the Juniper Networks Database
• Configuring the Juniper Networks Database to Run in Community Mode with the C-Web Interface
• Enabling the Juniper Networks Database to Run in Standalone Mode (SRC CLI)
• Securing the Juniper Networks Database (SRC CLI)
• Viewing Information About the Juniper Networks Database in Community Mode
• Configuration Statements for the Juniper Networks Database (SRC CLI)
• Example: Configuration for a Database Community

Enabling the Juniper Networks Database to Run in Community Mode (SRC CLI)

If you are adding a Juniper Networks database to an existing community, see Adding a Juniper Networks Database to an Established Community(SRC CLI) .

Use the following configuration statements to enable the Juniper Networks database on a C-series Controller in community mode:

system ldap server community {

role (primary | secondary);

primary-neighbors [primary-neighbor...];

secondary-neighbors [secondary-neighbor...];

}

To enable the Juniper Networks database to run in community mode:

1. From configuration mode, access the configuration statement that configures the Juniper Networks database in community mode:

   user@host# edit system ldap server community

2. Specify the role of the database as primary or secondary:

   [edit system ldap server community]

   user@host# set role primary

   or

   [edit system ldap server community]

   user@host# set role secondary

3. Configure primary neighbors. Specify each neighbor by IP address, fully qualified hostname, or a hostname that can be resolved through the domain name system:

   [edit system ldap server community]

   user@host# set primary-neighbors neighbor ...

   For example, set C1 and C2 as primary neighbors:

   [edit system ldap server community]

   user@host# set primary-neighbors C1 C2

4. Configure secondary neighbors. Specify each neighbor by IP address, fully qualified hostname, or a hostname that can be resolved through the domain name system:

   [edit system ldap server community]

   user@host# set secondary-neighbors neighbor ...

   For example, set C3 and C4 as secondary neighbors:

   [edit system ldap server community]

   user@host# set secondary-neighbors C3 C4