Distributing the SSR Cluster Configuration and Enabling SSR Client Components
The SSR is a distributed system. Multiple C Series Controllers participate in the SSR cluster, and each system has a different role and hosts a different type of cluster node. Instead of configuring each C Series Controller individually by its role in the SSR cluster, the configuration is stored in the centralized Juniper Networks database. You can configure the SSR cluster from any C Series Controller. The SSR driver in a C Series Controller distributes the configuration to each node in the cluster. When you enable the SSR component in the system, the SSR driver loads the configuration from Juniper Networks database and finds the role of the system in SSR. Then it loads the relevant configuration for the specific role of the node. Finally, it starts the SSR components corresponding to the role of the node.
Enabling, Restarting and Disabling the SSR Component Database
Although the configuration is distributed to all nodes in the SSR cluster, enabling, disabling and restarting the SSR component database is a local function, which must be performed on each node in the cluster. Enabling or restarting the component database on a node starts or restarts the processes for all SSR components in the node. Disabling the component database on a node stops all processes for all SSR components in the node. After initially configuring your cluster, you must enable the component database on each node in the cluster one by one. In addition, certain configuration changes require you to disable, enable, or restart the component database on each node in the cluster one by one. Be sure to review and carefully follow the procedures described in Configuring the Initial SSR Cluster (SRC CLI). When making changes to an active cluster, be sure to review each maintenance procedure beforehand and follow the steps carefully.