- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2023 04:24 PM
I have a three nodes ISE 3.2 patch-2 environment:
ISE1: Primary Admin & Primary MNT,
ISE2: PSN,
ISE3: PSN,
I need to add ISE4 into the cluster and mark it Secondary Admin & Secondary MNT.
However, as soon as I add ISE4 into the cluster, both ISE2 and ISE3 restarted and
caused a 20 minutes outage in my production environment. I am 99% certain that
this was not the case with ISE version 3.1.
Is this expected with ISE 3.2 patch 2?
Solved! Go to Solution.
- Labels:
-
Identity Services Engine (ISE)
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2023 03:04 PM
No, that is not expected. Consider calling TAC so they may understand Why this happened.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2023 09:22 AM
- Do you have 'console outputs' from these restarts , if not check show logging system ade/ADE.log , on the involved nodes , however not sure if the older and or needed info is still present after reboot(s) ,
M.
-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2023 03:04 PM
No, that is not expected. Consider calling TAC so they may understand Why this happened.
