
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2018 06:01 AM
Hi everyone,
what are the expected consequences of a ISE MNT node failure in an ISE distributed deployment (Version 2.x)? To my understanding this should not impact PAN or PSN behaviour. Is this correct? Are there other factors to take into account?
Thanks,
Jonathan
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
04-30-2018 06:17 AM
You’re correct
Just logging will stop and you won’t be able to see reports and logs via the PAN since it’s a cross launch
Would recommend having HA and promote the secondary

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2018 06:17 AM
You’re correct
Just logging will stop and you won’t be able to see reports and logs via the PAN since it’s a cross launch
Would recommend having HA and promote the secondary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2018 06:53 AM
Certain ISE features, such as PassiveID and license counts, rely on a working M&T node. Best to have a standby M&T, as Jason suggested.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2018 06:14 AM
Also remember the pxGrid side of things. Several of the integrations with ISE use a combination of pxGrid and ISE REST API calls. For example, FMC gets data from pxGrid as well as session data from API calls to the MNT node I believe. Correct me if I am wrong on that.
