Administrator Guide

Publisher Deployment Guidance
l In a world-wide large-scale deployment, not all Subscriber nodes are equally busy. To determine the
maximum request rate that must be handled by the Publisher node, examine the cluster's traffic pattern
for busy hours and estimate the traffic load for each Subscriber node, adjusting for time zone differences.
l In a large-scale deployment, isolate the Publisher node, to allow it to handle the maximum amount of
traffic possible.
l To help reduce the maximum amount of traffic possible in a large-scale deployment (ignoring API requests
from Subscribers as well as the outbound replication traffic to Subscribers), the Publisher should not
receive any authentication requests or Guest/Onboard requests directly .
l If the worker traffic sent from the Subscriber nodes is expected to fully saturate the capacity of the
Publisher node, Insight should not be enabled on the Publisher node. If the Publisher node has spare
capacity, it can be used to support the W-ClearPass Insight database. However, take care to carefully
monitor the Publisher node's capacity and performance.
l Table 23 shows the recommended Publisher node disposition that should be deployed given the number
and type of Subscribers in the cluster.
Table 23: Subscriber and Publisher Deployment Matrix
Subscriber Nodes Publisher Disposition
CP-HW-500 Subscriber Nodes
4 or less CP-HW-500 Subscriber nodes Dedicated CP-HW-500 Publisher pair
5 to 20 CP-HW-500 Subscriber nodes
NOTE: Assumes less than 4,000 unique
endpoints.
Dedicated CP-HW-5K Publisher pair
21+ CP-HW-500 Subscriber nodes Dedicated CP-HW-25K Publisher pair
CP-HW-5K Subscriber Nodes
4 or fewer CP-HW-5K Subscriber nodes Dedicated CP-HW-5K Publisher pair
5+ CP-HW-5K Subscriber nodes Dedicated CP-HW-25K Publisher pair
CP-HW-25K Subscriber Nodes
Up to 10 CP-HW-25K Subscriber nodes Dedicated CP-HW-25K Publisher pair
Subscriber Node Guidelines
Using Nearest Subscriber Node
Guests and Onboard clients should be directed to the nearest Subscriber node. From the client’s point of view,
the internal API call to the Publisher is handled transparently. The best response time for static resources is
obtained if the server is nearby.
Dell Networking W-ClearPass Deployment Guide Deploying W-ClearPass Clusters | 137