Overview of the Juniper Networks Database
Each C-series platform contains a Juniper Networks database. The database can store SRC data, SRC sample data, SRC configuration information, and a number of user profiles. You store subscriber data in another database. For information about configuring the SAE to access subscriber data, see the SRC-PE Network Guide, Chapter 2, Configuring the SAE with the SRC CLI.
You must enable the database for it to be operational on the system. After the database is operational, you can load sample data and perform other configuration activities that use this database.
When the C-series platform starts for the first time, you must enable the Juniper Networks database.You can operate this database as a standalone database or as a member of a community of Juniper Networks databases. 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 platforms, 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.
We recommend that you configure at least two databases to have a primary role.
- 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.
Neighbors are Juniper Networks databases that receive data from another Juniper Networks database. When you configure a database to be a neighbor, you configure it as one of the following types:
- Primary neighbor—A database that propagates changes that it receives to other Juniper Networks databases configured as neighbors. A primary neighbor must be assigned a primary role.
We recommend that you configure at least two databases as primary neighbors.
- Secondary neighbor—A database that only receives database changes. A secondary neighbor must be assigned a secondary role.
When you configure neighbors for the databases, keep in mind the following guidelines:
- A database assigned a primary role can have primary and secondary neighbors.
- A database assigned a secondary role must have at least one primary neighbor, but no secondary neighbors. Because a secondary database cannot distribute changes to its neighbors, if you do configure a secondary neighbor for a secondary database, the software does not use the configuration for the secondary neighbor.
To share processing load, you can configure SRC components, such as SRC-ACP, NIC, or SAE to use a specified database. In the local configuration for SRC components, you configure the URL of the directory.