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

# Configuring the Juniper Networks Database

Each C Series Controller contains a Juniper Networks database. The database stores SRC data, sample data, configuration information, and user profiles. You must enable the Juniper Networks database the first time you power on the system. It can operate as a standalone database or as a member of a community of Juniper Networks databases.

| Note: The Juniper Networks database must be running before you start configuring the SRC software.

Typically, you run the database in standalone mode only in testing environments. In standalone mode, the database does not communicate with other Juniper Networks databases; there is no data distribution and no redundancy. In community mode, databases distribute data changes among specified databases. When you have two or more C Series Controllers, enable the Juniper Networks database to run in community mode, and assign a role to each database:

- Primary role—A database that provides read and write access to client applications. It replicates its data and distributes changes to any Juniper Networks databases configured as neighbors.
- Secondary role—A database that provides read access to client applications. If client applications try to write data to this database, the database refers the client to a primary database.

In the following example, a standalone database is enabled. For more information about community mode, see SRC PE Getting Started Guide, Chapter 10, Managing the Juniper Networks Database.

To enable a Juniper Networks database to run in standalone mode:

1. From configuration mode, access the configuration statement that configures the Juniper Networks database.
   `
   user@host# edit system ldap server
   `
2. Enable standalone mode.
   `
   [edit system ldap server]
   user@host# set stand-alone
   `

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