cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
 
ISE 2.3 Patch 7 has been posted. This will be the last patch for the ISE 2.3 release!
Choose one of the topics below to view our ISE Resources to help you on your journey with ISE

This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.

160
Views
5
Helpful
2
Replies
Cisco Employee

Post-Upgrade step for ISE version 2.4

Hi experts!
There is a Post-Upgrade step for ISE version 2.4 in the documentation:
"With the operational data backup of MnT data that you created before update, restore the backup.
Failing to perform backup and restore could trigger a High RADIUS Disk Usage Alarm.
The maximum size for an MnT database file does not get updated correctly while upgrading, and the database file fills up."
https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/upgrade_guide/b_ise_upgrade_guide_24/b_ise_upgrade_guide_24_chapter_0100.html#id_87319

Is there real need to restore the backup after the upgrade is done if upgrade is completed successfully?

 

BR, Nikolay.

1 ACCEPTED SOLUTION

Accepted Solutions
VIP Engager

Re: Post-Upgrade step for ISE version 2.4

That's not something I have ever done and I have never had an issue. I believe this could be a carry over of documentation steps from earlier releases, but Cisco has since fixed the issue.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvk31784

2 REPLIES 2
Highlighted
VIP Advisor

Re: Post-Upgrade step for ISE version 2.4

yes to avoid the risk of having this alarm. I did upgrade without facing
this issue but restored the backup to avoid risks.
VIP Engager

Re: Post-Upgrade step for ISE version 2.4

That's not something I have ever done and I have never had an issue. I believe this could be a carry over of documentation steps from earlier releases, but Cisco has since fixed the issue.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvk31784