topic Re: ISE 2.1 - Health Status Unavailable in Network Access Control

ISE 2.1 - Health Status Unavailable

nadeekha — Thu, 12 Jan 2017 22:47:14 GMT

Hi,

My customer has a 2 node ISE 2.1 pilot deployment Primary PAN/MNT/PSN and Secondary PAN/MNT/PSN. Everything was running fine but they now see a large number of Health Status Unavailable Alarms. Description: The M&T Node has not received the health status from ISE nodes.

No firewall between the 2 nodes but nodes are communicating with each other.

The authentication seems to be working but nothing shows up in the live logs. It was all working previously.

Would appreciate input on what area to look at to troubleshoot further.

Thanks

Nadeem

Re: ISE 2.1 - Health Status Unavailable

h0388t — Mon, 16 Jan 2017 07:44:28 GMT

It's regarded as bug which comes under the following condition.

・bonding Interface setting

・backup config file and config restore

ISE retore brake Log Collector's value and Node status on summary

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

Check the LogCollector value.

Administration > Logging > Remote Logging Targets

If IP Address of LogCollector is null, come under bug.

I recommend contact TAC.

Regards

Re: ISE 2.1 - Health Status Unavailable

Craig Hyps — Tue, 17 Jan 2017 22:58:17 GMT

Per above, check Log Target settings for each node. The IP address for Remote Log Collector should be pointing to the node(s) configured for MnT persona. If the node itself runs MnT, then may see loopback address.