04-03-2017 03:05 AM
Does anyone know when patch 1 for Cisco ISE 2.2 is comming?
This bug CSCvc34766 hold me against to upgrade to ISE 2.2.
Solved! Go to Solution.
04-03-2017 10:10 AM
We do not publish any ISE patch contents nor release dates in order to prevent setting expectations of the exact date/time and content of the patch release. It is supposed to be coming in April but the Engineering team has not given a specific date or final bug list.
04-03-2017 03:29 AM
The release notes for 2.2 recommends upgrading to the latest patch in your current version before you upgrade to 2.2 to avoid the bug you mention.
04-03-2017 10:10 AM
We do not publish any ISE patch contents nor release dates in order to prevent setting expectations of the exact date/time and content of the patch release. It is supposed to be coming in April but the Engineering team has not given a specific date or final bug list.
04-24-2017 08:43 AM
Hello,
I upgraded today a two ISE 2.2 in distributed deployment (one primary, one secondary), using GUI....
And I have serious issues:
- ISE 1 upgraded, after restarted it indicated an error due to timeout to restart (???)
In CLI I can see the patch (sh ver) but not in GUI.
- ISE 2 didn't upgrade > so the deployment is unable to sync...
After different tests and issues, I broke the deployment, delete ISE 2, restart ISE 2.
I rolled back patch 1 on ISE.
As it is alone, I just upgraded it by GUI > same issue: patch appears in CLI but not GUI.
For the moment I'm resinstalling ise-2, I will install patch 1 before to make the deployment primary/secondary
Screenshot: patch 1 ok in CLI, no ok in GUI
04-28-2017 01:33 AM
Hi All,
I have the same issue.My step is follow,
1.Install 2 ISE
2.Register secondary ISE
3.Install patch 1 in Primary ISE via GUI.
After 1 hour,I can check the patch level at cli on Primary ISE ,but I cannot check the patch level at Administration>System >Maintenance >Patch Management. (In GUI ,about ISE can show the patch level)
The second issue,the secondary didnt install the patch after 2 hours.
Duncan
04-28-2017 06:13 PM
For your future reference, please start a new discussion thread, as this one was on patch release date but not patching issue.
I tried the patch in my lab but not seeing the issue as you described. Some potential as RBAC issue so I would suggest to try using an internal admin user in super admin group only. If you still have problem, then it's best to open a Cisco TAC case.
On the primary ISE node, you may the following CLI to get some clue why the patching (via admin web UI) not getting to the secondary ISE nodes.
show logging application patch.log
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide