Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello everyone, We are working on an ISE deployment for which we have a captive portal configured for users to log with their O365 (Azure / Entra ID) login. The setup is working great at the moment, but I am worried about durability / scalability of...
Hello Everyone, We are working on an ISE deployment with 2 PAN/MNT nodes (located in the cloud) and 5 PSNs located across different physical sites. We are searching for a way to enhance the detection of a failing PSN onsite by the switches to switch ...
Hello Everyone, I tested this extensively in a lab to try and comprehend which command does what and what timers are used. From what I tested, here are my conclusions: automate-tester username <user> ignore-acct-port idle-time <minutes>Tests the radi...
@thomas Yes, I used the probe-on, you can see the configuration I used in my lab in my earlier post: radius server server1address ipv4 1.1.1.1 auth-port 1812 acct-port 1813automate-tester username testuser ignore-acct-port probe-on
In my lab, the server came back up as "alive" after 10 minutes, with no "real" authentication going on, so the probe seemed to be working to mark the server as alive when it answers again after being marked dead. But I thought the automate-tester wou...
@thomas Reading the ISE Secure Wired Access Prescriptive Deployment Guide again, I see that the automate-tester does not behave as I thought it would. The purpose of the automate-tester would only be to bring the server back up again before the deadt...
