SRC Repository for Data
The Juniper Networks database, an LDAP directory, on a C Series Controller contains most SRC configuration data, including license information, service definitions, policies, and SAE configurations, as well as user profile data. You use user profiles to categorize groups of users, allowing you to keep your user data separate in your own directory.
We provide sample data to demonstrate how to provision the directory for different application scenarios. You can use the sample data as a starting place when developing or configuring specified applications of the SRC software. The SRC documentation provides references to the sample data to show sample implementations.
Many SRC components, such as the SAE and the policy engine are designed to run nonstop. These components get most of their configuration and provisioning data from the Juniper Networks database. If the data in the directory changes, it is not necessary to manually reload the data into affected components. The SRC directory client running in each of these components detects changes that affect the component, and the appropriate updates are made.
The directory client is configured with a list of directory servers to use: one primary and any number of backups. If connectivity to the primary directory is lost, the directory client switches to an available backup directory server. If connectivity to the primary directory is restored, the directory client detects the connection and switches back to the primary directory. This capability makes it possible to fine tune SRC deployments for added levels of availability and performance.
Juniper Networks Database as a Data Repository on C Series Controllers
The Juniper Networks database is a robust data repository that keeps your data highly available. It supports data distribution to other Juniper Networks databases and redundancy between Juniper Networks databases. Client applications control which database they connect to as their primary database and as their backup database. You can configure particular SRC components, such as SAE and NIC to use a specified database to provide load sharing.
The Juniper Networks database can also be run standalone to use in demonstrations or for testing purposes.
Directory as Repository for Subscriber Data
For environments that have large subscriber databases, the SRC software supports external third-party directories. The SRC software is compatible with any LDAP version 3–compliant directory. Integration work might be necessary, such as schema extension and access control. If you want the SRC software to automatically update existing subscriber sessions when you change your subscriber directory, and to cache subscriber data for performance, use a directory that supports the LDAP virtual list view control.