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


SRC Repository for Data

The Juniper Networks database on a C-series Controller or a Solaris platform 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. If you run the SRC software on a Solaris platform, you can configure it to use a third-party directory rather than the Juniper Networks database.

We provide sample data in LDAP Data Interchange Format (LDIF) 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 directory. 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, NIC, and SAE to use a specified database to provide load sharing.

The Juniper Networks database also can also be run standalone to use in demonstrations or for testing purposes.

Directory as Repository for SRC Data

For the SRC software running on a Solaris platform to work with a third-party directory, all the information must be provisioned in the directory. We provide tools, such as the SRC CLI, SDX Admin, and Policy Editor, to help provision the information into the directory. An external OSS can also provision all or part of the information directly through the LDAP interface.

LDAP Version 3

The SRC software on Solaris platforms employs LDAP version 3 to interact with third-party directories. The SRC software is compatible with any LDAP version 3-compliant directory, but some integration work might be necessary, such as for the following requirements:

Prepackaged Integration

For SRC software installed on Solaris platforms, we provide prepackaged integration for:

Third-Party Directory Servers

For information about the directory servers that you can integrate with the SRC software running on a Solaris platform, see the SRC-PE Release Notes. The SRC software is designed to work with directory servers that are robust, scalable, and suitable for the carrier market.


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