Administrator Guide

4. The Publisher is the first to be upgraded and rebooted. Configuration database and Insight database
migration is performed on reboot.
5. When the Publisher upgrade is complete, you can use the Cluster Upgrade Utility page to review log
messages.
6. When the Publisher upgrade is complete, upgrade is initiated on each selected Subscriber node. When
possible, multiple Subscribers are upgraded in parallel. When each Subscriber node is complete, the
Subscriber is rebooted.
7. During the parallel upgrade process, upgrade of the first Subscriber node begins five minutes after the
Publisher upgrade is completed.
8. Upgrade of the second Subscriber node begins five minutes after the upgrade of the first Subscriber
begins. This pattern continues sequentially for all Subscriber nodes in the cluster, with a five-minute
delay between each start time.
9. When each Subscriber is rebooted, it is added back into the cluster. Insight data is migrated and
restored.
10.When all selected Subscriber nodes have been upgraded, you can select and trigger the upgrade
operation for any additional Subscribe nodes.
11.When all the Subscriber nodes in the cluster have been upgraded, the Standby Publisher settings are
restored.
Detailed information for each of these steps is available in the Logs window during and after upgrade.
Sample Times Required for Upgrade
To help you estimate how much time the upgrade might take, Table 366 shows representative numbers for
upgrade times under test conditions. Keep in mind that the figures here are only examples. The actual time
required for your upgrade depends on several factors:
l Your hardware or virtual appliance model. In the case of virtual machine installations, upgrade times
vary significantly based on the IOPS performance of your virtual machine infrastructure.
l The size of the configuration database to be migrated.
l For W-ClearPass Insight nodes, the size of the Insight database.
l For Subscriber nodes, the bandwidth and latency of the network link between the Subscriber and the
Publisher.
Hardware
Model
Config DB
Size
Insight
DB Size
Publisher
Upgrade
Time
Subscriber
Upgrade Time
Insight Restoration
Time in Publisher or
Subscriber
CP-500 100 MB 5 GB 50 minutes 50 minutes
20 minutes
200 MB 5 GB 60 minutes 60 minutes
20 minutes
CP-5K 100 MB 5 GB 50 minutes 50 minutes
15 minutes
200 MB 5 GB 60 minutes 60 minutes
15 minutes
CP-25K 200 MB 5 GB 30 minutes 30 minutes
15 minutes
500 MB 10 GB 40 minutes 40 minutes
20 minutes
Table 366: Sample Times Required for Upgrade
Dell Networking W-ClearPass Policy Manager 6.6 | User Guide Cluster Upgrade/Update Tool | 675