Refresh Deployment Details option after the Secondary Administration node is upgraded.
The Secondary Administration node is upgraded and moved to the upgraded deployment. The Secondary Administration node is down. There is no Secondary Administration node in the deployment. You will get a error message No Secondary Administration Node in the Deployment under the following circumstances: Secondary Administration/Secondary Monitoring Node, Policy Service Nodes, Primary Monitoring Node, Primary Administration Secondary Administration/Primary Monitoring Node, Policy Service Nodes, Secondary Monitoring Node, Primary Administration Secondary Administration Node, Secondary Monitoring Node, Policy Service Nodes, Primary Administration/Primary Monitoring Secondary Administration Node, Primary Monitoring Node, Policy Service Nodes, Primary Administration/Secondary Monitoring Primary Administration/Primary Monitoring Node Secondary Administration/Secondary Monitoring Node Secondary Administration/Secondary Monitoring Node, Policy Service Nodes, Primary Administration/Primary Monitoring Node Primary Administration/Secondary Monitoring Node Secondary Administration/Primary Monitoring Node Secondary Administration/Primary Monitoring Node, Policy Service Nodes, Primary Administration/Secondary Monitoring Node If the Administration Nodes also assume the Monitoring persona, then follow the sequence given in the table below: In the Edit Node window, click Promote to Primary to promote the SecondaryĪdministration Node as the Primary Administration Node (as in your old deployment), if necessary. Node becomes the Secondary Administration Node. Register the node to the new deployment as a Secondary Administration node.Īfter the upgrade, the Secondary Administration Node becomes the Primary Administration Node, and the original Primary Administration
From the CLI, upgrade the node as a standalone To be upgraded), the upgrade is rolled back and the node becomes a standalone node.
If upgrade fails during the registration of the Primary Administration node (the last node from the old deployment that has
Rerun the upgrade verification and network tests after you upgrade the Primary Administration Node. Secondary Monitoring Node or Primary Monitoring Node You can upgrade the next set of Policy Service nodes. Node of your existing Cisco ISE deployment.Īfter you upgrade a set of Policy Service nodes, verify whether the upgrade is successful (see Verify the Upgrade Process)Īnd run the necessary network tests to ensure that the new deployment is functioning as expected. If you have a distributed deployment, upgrade all the nodes that are available in the site that has Secondary Administration Primary Monitoring Node or Secondary Monitoring Node This task should be done before initiating upgrade in order to ensure that youĬan easily roll back manually, if necessary.Īt this point, the Primary Administration Node remains at the previous version and can be used for rollback if the upgrade This will help you to reduce downtime while providing maximum resiliency and ability to roll back.īackup all configuration and monitoring data. However, we recommend that you follow the below provided order of the nodes for upgarding yourĭeployment. In case you are using GUI to upgrade you can choose the You can upgrade Cisco ISE using GUI, Backup and Restore, or CLI.