Cisco Identity Services Engine Upgrade Guide, Release 1.1.x
Recovering from Upgrade Failures
Downloads: This chapterpdf (PDF - 70.0KB) The complete bookPDF (PDF - 890.0KB) | Feedback

Recovering from Upgrade Failures

Table Of Contents

Recovering from Upgrade Failures

Recovering from Upgrade Failures on a Standalone Node

Scenario 1: Upgrade Fails During Database Schema or Datamodel Upgrade

Scenario 2: Upgrade Fails During Binary Install

Recovering the Appliance if the SSH Session Quits During Upgrade


Recovering from Upgrade Failures


This chapter contains the following topics:

Recovering from Upgrade Failures on a Standalone Node

Recovering the Appliance if the SSH Session Quits During Upgrade

Recovering from Upgrade Failures on a Standalone Node

Before attempting any rollback or recovery on the node where an upgrade has failed, you must generate an application bundle by using the backup-logs CLI command and place it in a remote repository.

Scenario 1: Upgrade Fails During Database Schema or Datamodel Upgrade

Detection: One of the following messages is shown in the console and ADE.log:

ISE Database schema upgrade failed!

ISE Global data upgrade failed!

ISE data upgrade for node specific data failed!

How to Roll back: Restore from the last backup to roll back.

How to retry the upgrade:

Analyze the logs.

To identify and resolve the problem, submit the application bundle that you generated to the Cisco Technical Assistance Center (TAC).

You need a new application bundle each time you retry an upgrade.

Scenario 2: Upgrade Fails During Binary Install

Detection: An application binary upgrade occurs after the database upgrade. If a binary upgrade failure happens, the following message displays in the console and ADE.log:

% Application install/upgrade failed with system removing the corrupted install

How to Roll back: Reimage the Cisco ISE Appliance by using the previous ISO image and restore from the backup.

How to retry the upgrade:

Analyze the logs.

To identify and resolve the problem, submit the application bundle that you generated to the Cisco Technical Assistance Center (TAC).

You need a new application bundle each time you retry an upgrade.

Recovering the Appliance if the SSH Session Quits During Upgrade

Detection: The SSH session or console was disconnected or quit during an upgrade.

How to Rollback: Reimage the Cisco ISE Appliance by using the previous ISO image and restore from the backup.

How to retry the upgrade: Continue with the upgrade again. If your appliance is used as a secondary node in the new Cisco ISE, Release 1.1.x, directly install the new ISO version, and register it to the new primary Administration ISE node.