This failover is configurable by the polling interval and the count. When it not happening as expected, please analyze the timeline based on the debug logs and verify whether the monitoring node(s) not detecting the events fast enough. Please engage Cisco TAC, if needed.
This failover is configurable by the polling interval and the count. When it not happening as expected, please analyze the timeline based on the debug logs and verify whether the monitoring node(s) not detecting the events fast enough. Please engage Cisco TAC, if needed.
I usually see 30 minutes or so in my deployments. Remember that not only is there time to detect the primary PAN went down but the bulk of the time is the service restart on the secondary PAN to make it the primary. An ISE service restart takes 15 minutes at a minimum.
PAN failover should have nothing to do with profiling. That is a PSN function. In order to do PAN failover you must be in at least a 4 node deployment so I am assuming you have separated your PSN function from your PAN/M&T functions. If that is the case the status of the PANs and who is primary/secondary is completely irrelevant to the functioning of the PSNs. Both PANs could be dead and the PSNs will happily continue on doing their job.
