The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco ICFPP enables you to upgrade standalone appliances and multiple-node clusters for bug fixes and updated adapters. For more information, see the following topics:
Cisco ICFPP 2.3.1 supports the following upgrade paths:
Beginning with version 2.3.1, Cisco ICFPP includes a feature that automatically restarts Infra services when you upgrade Cisco ICFPP.
The first time that you upgrade Cisco ICFPP from 2.2.1 or 2.2.1a to 2.3.1 or higher, you must manually restart services. After you restart Infra services, the automatic service restart feature is enabled and you do not need to restart Infra services when you next upgrade Cisco ICFPP.
This procedure enables you to apply Cisco bug fixes and upgrade adapters on a standalone node. To upgrade a multiple-node cluster, see Upgrading a Multiple-Node Cluster.
Use this procedure to upgrade a multiple-node cluster for bug fixes and updated adapters. To upgrade a standalone Cisco ICFPP virtual appliance, see Upgrading a Standalone Node.
This procedure applies to multiple-node clusters with the following components and configuration:
An HA pair consisting of two Cisco ICFPP virtual appliances that are configured as primary nodes.
The HA pair is configured with one active node and one standby node.
Additional Cisco ICFPP virtual appliances are configured as service nodes.
The workflow for upgrading a cluster includes the following high-level tasks:
Stop the virtual IP (VIP) service on the HA active node.
Monitor status while services fail over to the HA standby node.
Upgrade the current HA active node (originally the standby node).
Start the VIP service on the current HA standby node (originally the active node).
Stop the VIP service on the upgraded HA active node.
Monitor status while services fail over to the current HA standby node, making it the active node again.
Upgrade the current HA active node.
Start the VIP service on the current HA standby node.
Upgrade each service node.
The following procedure describes how to perform these tasks.
Obtain the Cisco ICFPP upgrade file (icfpp-upgrade-2.3.1.tar.gz) from Cisco.com. For assistance, contact your Cisco representative.
Confirm that HA has been configured on two Cisco ICFPP virtual appliances that are configured with the Primary Node role.
Step 1 | Stop the VIP service on the HA active node as follows: | ||
Step 2 | Log in to the ShellAdmin console for the HA standby node. | ||
Step 3 | In the
ShellAdmin console for the standby node, choose
Display
Services Status to monitor the following events as they occur:
| ||
Step 4 | Upgrade the
currently active node of the HA pair as follows:
| ||
Step 5 | Do one of the
following, depending on the
Cisco ICFPP
version:
| ||
Step 6 | Verify that
the HA active node was successfully upgraded as follows:
| ||
Step 7 | Restart the VIP service on the current HA standby node as follows: | ||
Step 8 | Stop the VIP service on the currently active node that was upgraded in Step 4 as follows: | ||
Step 9 | Log in to the ShellAdmin console for the standby node in the HA pair. | ||
Step 10 | In the
ShellAdmin console for the standby node, choose
Display Services Status to monitor the following
events as they occur:
| ||
Step 11 | Upgrade the HA active node as follows: | ||
Step 12 | Restart the VIP service on the HA standby node as follows: | ||
Step 13 | Upgrade each
service node in the cluster as follows:
| ||
Step 14 | Verify that
each service node upgraded successfully as follows:
|