Cisco Identity Services Engine Upgrade Guide, Release 1.1.x
Upgrading a Two-Node Deployment
Downloads: This chapterpdf (PDF - 127.0KB) The complete bookPDF (PDF - 890.0KB) | Feedback

Upgrading a Two-Admin Node Deployment

Table Of Contents

Upgrading a Two-Admin Node Deployment

Performing a Two-Admin Node Deployment Upgrade


Upgrading a Two-Admin Node Deployment


Performing a Two-Admin Node Deployment Upgrade

When upgrading to a higher release, you should initially upgrade only the secondary Administration ISE node to the higher version.

For example, if you have a deployment set up as shown in Figure 3-1, with one primary Administration node (Node A) and one secondary Administration node (Node B), you can proceed with the following upgrade procedure.

Figure 3-1 Cisco ISE, Release 1.1 Two-Node Administrative Deployment

This supports an upgrade of Cisco ISE, Release 1.0 or 1.1 to Cisco ISE, Release 1.1.x with split domain upgrade only, so that the secondary ISE node has to be deregistered individually from the deployment before upgrade.


Warning This warning is not applicable if you are upgrading from Cisco ISE, Release 1.1 patch 3.

If your secondary Admin node has been operational for more than 90 days, its license will be lost after it has been deregistered. In this case, you must obtain a valid license for the secondary Cisco ISE Administration node (ISE Node B) based on its UDI: Serial Number, Version ID, and Product ID. See "Obtaining a Valid License" section for more information.

To perform a two-adminnode deployment upgrade, complete the following procedure:


Step 1 Perform an on-demand backup (manually) of the Primary Administration ISE node from the admin user interface or CLI and an on-demand backup of the Monitoring node from the admin user interface, before upgrading to Cisco ISE, Release 1.1.x.

For more information on how perform an on-demand backup, see the "Performing an On-Demand Backup" section.

Step 2 Deregister the secondary node (Node B) from the deployment setup. After deregistration, this node becomes a standalone node.

Step 3 Upgrade this standalone node to Cisco ISE, Release 1.1.x.

When you log in to Node B after the upgrade, if the system prompts you for a license, you must install a valid license for the secondary node based on its UDI. See Obtaining a Valid License for more information.

Step 4 Convert the primary node of the previous deployment (Node A) to a standalone node.

Step 5 Make Node B as the primary node in the new deployment.

Step 6 Upgrade Node A to Cisco ISE, Release 1.1.x and register to Node B in the Cisco ISE, Release 1.1.x deployment setup as the secondary node.

After you upgrade your deployment, all the policies and other data of the previous deployment will be retained in your new deployment.