Juniper Networks Database Overview

Each C Series Controller 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.

The Juniper Networks database is designed to store a limited number of subscriber entries that may be shared among your subscribers. If you need to have dedicated entries for each subscriber, you can configure the SRC software to use an external directory. We recommend that an external directory store the subscriber data in environments that have more than 1000 subscribers with an average of 3 subscriptions per subscriber.

You can also set a limit on the maximum number of search results that the server returns to a client in response to a search operation. You must set the size limit on the basis of the total number of available entries in the Juniper Networks Database.

When the C Series Controller starts for the first time, you must enable the Juniper Networks database. After the database is operational, you can load sample data and perform other configuration activities that use this 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 Controllers, enable the Juniper Networks database to run in community mode, and assign a role to each 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:

When you configure neighbors for the databases, keep in mind the following guidelines:

To share processing load, you can configure 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.

Redundancy for a Juniper Networks Database

Protect SRC data by setting up a redundancy scheme for your Juniper Networks databases. Client applications control which database they connect to as their primary database and as their backup database.

Use the following guidelines to plan which databases are assigned primary or secondary roles, and which databases are primary or secondary neighbors:

Security for a Juniper Networks Database

You can secure connections to a Juniper Networks database by:

The type of secure connection you configure determines which ports are open to a Juniper Networks database:

You can also increase the security of your Juniper Networks database by changing the passwords that SRC components use to communicate with the database.

For information about configuring the SAE to access subscriber data, see Configuring LDAP Access to Directory Data (SRC CLI).

Related Documentation