Administrator Guide

Figure 120 Publisher and Subscribers in Hub and Spoke Configuration
l The Publisher node functions as the master controller in a cluster. The Publisher is your central point of
configuration, monitoring, and reporting. It is also the central point of database replication. All the
databases are managed through the Publisher.
n There is at most one active Publisher in this model, and a potentially unlimited number of Subscribers.
n The Publisher node has full read/write access to the configuration database. All configuration changes
must be made on the Publisher. The Publisher node sends configuration changes to each Subscriber.
l The Subscriber nodes are worker nodes. All the AAA load, all RADIUSrequests, and the node where policy
decisions are being made are on the Subscriber nodes.
n Subscriber nodes maintain a local copy of the configuration database, and each Subscriber has read-
only access to a local copy of the configuration database.
Network Address Translation (NAT) is not supported between the Publisher and Subscriber nodes.
What Information Is Replicated?
A background replication process handles the task of updating the configuration database based on the
configuration changes received from the Publisher.
Multiple entities exist within a CPPM cluster that must be shared to ensure successful operation of the cluster.
Only the configuration database is replicated.
The Log and Insight databases are not replicated across the cluster.
Dell Networking W-ClearPass Deployment Guide Deploying W-ClearPass Clusters | 133