You can upgrade to Cisco ISE,
Release 1.2, only from the Cisco ISE command-line interface (CLI). For
instructions on upgrading standalone or two-node deployments, see "Chapter 2, Upgrading
Standalone and Two-Node Deployments to Release 1.2". For instructions on
upgrading a distributed deployment, see "Chapter 3, Upgrading a Distributed Deployment to Cisco ISE,
The upgrade process
for a standalone node is different than the one for upgrading nodes in a
deployment. When you run the application upgrade command from the Cisco ISE
CLI, the following tasks are performed in the background in each of the nodes:
Downloads the upgrade bundle
and extracts it.
Performs a backup of the
configuration database (for automatic rollback in case of recoverable
Upgrades the configuration
database or downloads a dump of the upgraded configuration database (in the
case of a standalone node).
operating system and application binary files.
database from a 32-bit to a 64-bit system.
After a successful upgrade,
prompts the user to log in to Cisco ISE, Release 1.2.
deployments, the upgrade process follows a Split Deployment model. After you
upgrade the secondary Administration node to the new release, Cisco ISE creates
a new deployment. The secondary Administration node from the old deployment
becomes the primary Administration node in the new deployment. When you upgrade
the rest of the nodes in the old deployment, they join the new deployment.
When you upgrade the
secondary Administration node from the old deployment, it saves the old
deployment configuration and also notifies the primary Administration node of
the upgrade. The primary Administration node in the old deployment notifies the
other nodes about the upgrade. After upgrade, the nodes from the old deployment
join the primary Administration node in the new deployment. The upgrade process
retains licenses and certificates. You do not have to reinstall or reimport
them. Cisco ISE, Release 1.2, supports license files with two-node unique
device identifiers (UDIs). You can request for a new license with the UDI of
both the primary and secondary Administration nodes. See the
Services Engine Hardware Installation Guide for details.
To upgrade to Cisco
ISE, Release 1.2, you do not have to deregister the nodes from the deployment
and register them to the new deployment as was the case in previous releases.
When you run the
command from the CLI, the upgrade software deregisters the node and
registers it to the new deployment automatically.
The upgrade fails if
you make any node persona changes in the old deployment after you start the
upgrade on the secondary Administration node.
You must first upgrade
the secondary Administration node. Then, upgrade the primary Monitoring node,
followed by the Policy Service nodes and Inline Posture nodes, respectively.
Next, upgrade the secondary Monitoring node (if you have one in your old
deployment). Finally, upgrade the primary Administration node from your old
deployment. For Policy Service nodes, the database schema is not upgraded.
Instead, the Policy Service nodes get a copy of the new database from the
primary Administration node in the new deployment.