Upgrading the Cluster

To upgrade the Policy Manager cluster:

1. From the publisher, navigate to Administration > Agents and Software Updates > Software Updates.

2. Click the Cluster Upgrade link.

The Cluster Upgrade page opens.

Figure 1  Cluster Upgrade Page

This page includes the information described below in Table 1.

Table 1: Information on the Cluster Upgrade Page

Field	Description
Upgrade Info	Describes the upgrade image's name and size, and includes release-specific comments.
Database Info	Shows the size of the configuration database.
Publisher Details	Provides information for the publisher and for all Subscribers in the cluster. Information includes the management IP address, version number, zone, Insight database size, last upgrade step completed, and upgrade status.
Upgrade Steps	During the cluster upgrade, this area displays the status of each stage in the process. As each stage completes, it displays how long it took to complete. Prepare subscribers Copy upgrade image to subscribers Upgrade Publisher Reboot + Onboot Publisher Upgrade selected subscribers Reboot + Onboot selected subscribers
View Logs	In each publisher and Subscriber row, clicking this button opens the Logs page which provides detailed status and log messages for each upgrade stage.

When you open the Cluster Upgrade page, it immediately prepares the subscriber nodes for upgrade by automatically installing the required additional API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software. support.

This is a background process and does not require any actions from the user. A progress indicator is displayed during this stage.

To install the patch for API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software. support on subscribers, these subscribers must be able to access the publisher over HTTP Hypertext Transfer Protocol. The HTTP is an application protocol to transfer data over the web. The HTTP protocol defines how messages are formatted and transmitted, and the actions that the w servers and browsers should take in response to various commands., or they must be able to access the publisher over HTTPS Hypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. using its host name and validate the certificate that is presented (that is, trust the issuer and match the host name in the certificate Common Name (CN Common Name. CN is the primary name used to identify a certificate. )).

When the 6.10 upgrade image is available locally and all subscribers have been patched, the Start Upgrade link is available.

3. Click Start Upgrade.

The Start Cluster Upgrade page opens.

Figure 2  The Start Cluster Upgrade Page

You can upgrade the entire cluster or just a subset of Subscribers.

4. In the Start Cluster Upgrade window, use the check boxes to select the Subscribers to upgrade.

5. In the LogDB backup and restore options drop-down list, select one of these options:

a. Access tracker records are backed up but will not be restored: Select if you need a backup of the access tracker records to potentially restore after upgrade.

This option increases the overall upgrade time.

b. Do not backup access tracker records: Select if you do not need a backup of the access tracker records.

6. The reboot interval determines the interval of time after the last subscriber reboots before the next subscriber can reboot. Available intervals are 5, 10, or 15 minutes. Five minutes is the default.

7. Click Upgrade.

The Cluster Upgrade begins the automated upgrade process.

No further manual steps are required until all selected Subscribers have been upgraded. For information on the automated process, see Steps in the Cluster Upgrade Automated Workflow.

The publisher is always upgraded and rebooted first. The Cluster Upgrade page is not available while the publisher is rebooted and data migration is in progress.

8. When the publisher upgrade is complete, navigate to the Cluster Upgrade page to monitor upgrade progress, as described in Viewing Upgrade Status.

9. After a successful upgrade, confirm that all the subscriber nodes in the cluster are back in sync and all the services are accessible.

10. Verify that any preexisting standby publisher settings are restored:

Navigate to Administration > Server Manager > Server Configuration > Cluster-Wide Parameters link >  Standby Publisher tab.