01-23-2018 12:01 PM - edited 02-21-2020 10:43 AM
We are currently running version 2.2.0.470 one primary and two secondary servers at satellite offices. From time to time we cannot log on using https to the primary. So far either restarting the services or rebooting the server has resolved that issue. Today I had the same issue but rebooting has not resolved the issue. The server seems to be authenticating clients just fine. I can log on to my secondary servers without issues as well. Not sure what else to do, possibly reboot my secondary servers? A possible bug with secondary and primary were they have to be rebooted in s specific order? Normally the server is running within 15-20 minutes but it has been initializing for about an hour now.
01-23-2018 02:34 PM
Hi,
It may be a bug or maybe you're running ISE in a virtualized environment and you didn't do any resource reservation.
Regards,
Octavian
01-24-2018 05:17 AM
I let the server run and a few things I have noticed is only a few clients are authenticating, getting alerts for high authentication latency, application server changes from "initializing to "running" every once in while but not often. Also, CPU is staying at 100% usage will probably through more hardware at it but was wondering if there is a bug that could cause high CPU usage?
01-24-2018 02:09 PM - edited 01-24-2018 02:10 PM
Hi,
Is your ISE virtual?
Regards,
Octavian
01-24-2018 02:11 PM
Yes, it is a virtual server. I was able to resolve this by allocating more resources.
Thanks,
Quentin
05-18-2018 04:11 PM
We have the same Issue with High Authentication Latency in this version. Which resources did you increase? Memory or CPU...
05-18-2018 07:08 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide