Cisco ISE upgrade Failing from 1.4 to 2.0

Nishad Dadhaniya — Wed, 19 Sep 2018 18:31:15 GMT

Trying to upgrade ISE 1.4 stand alone mode to 2.0 upgrade, seems hitting bug https://quickview.cloudapps.cisco.com/quickview/bug/CSCux72726

but as stated in bug condition in our environment we are not using external (AD) password for admin user

Cisco ISE upgrade Failing from 1.4 to 2.0

Does anyone know how to recover from this?

ISE/admin# application upgrade proceed

Initiating Application Upgrade...

% Warning: Do not use Ctrl-C or close this terminal window until upgrade completes.

STEP 1: Stopping ISE application...

STEP 2: Verifying files in bundle...

-Internal hash verification passed for bundle

STEP 3: Validating data before upgrade...

STEP 4: Taking backup of the configuration data...

STEP 5: Running ISE configuration database schema upgrade...

- Running db sanity check to fix index corruption, if any...

- Upgrading Schema for UPS Model...

- Upgrading Schema completed for UPS Model.

ISE database schema upgrade completed.

STEP 6: Running ISE configuration data upgrade...

- Data upgrade step 1/51, RBACUpgradeService(1.5.0.111)... ..Done in 124 seconds.

- Data upgrade step 2/51, UPSUpgradeHandler(1.5.0.136)... Done in 6 seconds.

- Data upgrade step 3/51, UPSUpgradeHandler(1.5.0.139)... Done in 0 seconds.

- Data upgrade step 4/51, ANCRegistration(1.5.0.140)... Done in 0 seconds.

- Data upgrade step 5/51, NSFUpgradeService(1.5.0.149)... Done in 12 seconds.

- Data upgrade step 6/51, UPSUpgradeHandler(1.5.0.150)... Done in 6 seconds.

- Data upgrade step 7/51, NetworkAccessUpgrade(1.5.0.151)... Done in 0 seconds.

- Data upgrade step 8/51, UPSUpgradeHandler(1.5.0.156)... Done in 0 seconds.

- Data upgrade step 9/51, NetworkAccessUpgrade(1.5.0.159)... Done in 0 seconds.

- Data upgrade step 10/51, NetworkAccessUpgrade(1.5.0.162)... Done in 2 seconds.

- Data upgrade step 11/51, NSFUpgradeService(1.5.0.180)... Done in 0 seconds.

- Data upgrade step 12/51, NetworkAccessUpgrade(1.5.0.180)... Done in 0 seconds.

- Data upgrade step 13/51, NetworkAccessUpgrade(1.5.0.181)... Done in 4 seconds.

- Data upgrade step 14/51, UPSUpgradeHandler(1.5.0.183)... Done in 0 seconds.

- Data upgrade step 15/51, NSFUpgradeService(1.5.0.184)... Done in 0 seconds.

- Data upgrade step 16/51, UPSUpgradeHandler(1.5.0.187)... Done in 1 seconds.

- Data upgrade step 17/51, RBACUpgradeService(1.5.0.195)... ....Done in 289 seconds.

- Data upgrade step 18/51, NSFUpgradeService(1.5.0.199)... Failed.

% Error: ISE Global data upgrade failed!

Attempting to rollback: Rolling back the configuration database...

Starting application after rollback...

./isedbupgrade-newmodel.sh: illegal option -- 1

Invalid option: -

Rollback completed: The node has been reverted back to its pre-upgrade state.

% Application install or upgrade cancelled.

attached ADE.log

Re: Cisco ISE upgrade Failing from 1.4 to 2.0

Jason Kunst — Wed, 19 Sep 2018 18:39:18 GMT

Please troubleshoot and investigate issue thru TAC so they can fix the upgrade process

Re: Cisco ISE upgrade Failing from 1.4 to 2.0

James Davies — Tue, 29 Jan 2019 20:13:09 GMT

This is not helpful at all! I am having the same issue, and I am not using external AD, I broke the conneciton to AD before the upgrade, To simplt say "raise a TAC" does not help the community.

Does anyone have any suggestions please?

Re: Cisco ISE upgrade Failing from 1.4 to 2.0

Jason Kunst — Wed, 30 Jan 2019 00:35:44 GMT

Unfortunately not everything can be fixed In the community. This is a free best effort model. There are times like this one that require a case to be open.

Your other option is to build a new deployment parallel on ise 2.4 which is our new long term golden release . This will save hassle and time investigating

Re: Cisco ISE upgrade Failing from 1.4 to 2.0

Peter Koltl — Wed, 30 Jan 2019 21:33:57 GMT

You should definitely not upgrade to 2.0.

Upgrade from 1.4 to 2.0.1 directly to get better results.

topic Re: Cisco ISE upgrade Failing from 1.4 to 2.0 in Network Access Control

Cisco ISE upgrade Failing from 1.4 to 2.0