SSR Node Types
An SSR cluster has both a physical and logical organization. A C Series Controller that is a member of the cluster is called a node. A process that runs on a node and is part of the cluster is called a component. These terms are not interchangeable.
Three types of nodes are included in an SSR cluster, each with a specific role within the cluster:
A data node is a C Series Controller residing in the back end of the cluster. It runs the data storage engine component, which cooperatively manages, replicates, and stores data in the SSR storage engine with other data nodes. Each data node has its own memory and permanent storage, and maintains both a portion of the working copy of the SSR database and a portion of one or more replicas of the SSR database. A cluster can contain either two or four data nodes.
A client node is a C Series Controller that resides in the front end of the SSR cluster. Client nodes are responsible for several functions, including hosting SSR client components, hosting the SSR database front-end component, and optionally hosting the management server component.
The client components are the SRC components such as the Subscriber Information Collector (SIC), the Network Information Collector (NIC), the Service Activation Engine (SAE), the IMS Services Gateway, Dynamic Service Activator and other SRC components.
In addition to hosting the SSR client components, each client node hosts a front-end database component that reads and writes data into the SSR database and manipulates the cluster’s shared data which is hosted by the data nodes.
At least one client node must host a management server. The management server controls itself and all data nodes in the cluster. So that there is no single point of failure, you should configure a minimum of two client nodes to host management servers.
A data-client-node is a C Series Controller that hosts a data node component, a client node component, and a management server. Data-client nodes are used only for small-scale deployments using the two-shared-data-node cluster geometry, or for demonstration purposes when the cluster geometry is set to all-in-one.
To uniquely identify the various components running in the cluster, the SRC software assigns a node ID number to each component in the node. Node IDs are generated automatically by the SRC software and cannot be modified.