For ISE 2.4 with External RADIUS server. As per this document - https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/213239-configure-external-radius-servers-on-ise.html
Does ISE mark External RADIUS as dead based on the request send by ISE or ISE has a dedicated heartbeat to monitor External RADIUS server?
In a test environment, Duo Auth Proxy is configured as external RADIUS server with NO communication issue between both server, Duo Push works fine and user able to approve push as expected. Issue is when user deliberately ignoring "Push" and Duo Push will timeout as expected. During testing if user deliberately ignore Duo Push and timeout, ISE mark Duo as dead and 5 mins dead timer kicks in. Is this an expected behaviour and how to avoid ISE marking Duo as dead in this very likely test case?
Thanks
Wing Churn
