07-16-2024 03:05 PM
I’m facing a strange behavior with ISE 3.3 patch 2.
The Live Logs webpage very often become unresponsive and need to refresh the full page few times to see events.
No issue on messaging certificate and already tried unchecking the UDP flag in settings, without success.
Someone is having the same behavior? The logs seems to report o a kong error
kong-error [error] 25#0: *30 upstream timed out (110: Operation timed out) while connecting to upstream, client: x.x.x.x, server: kong, request: "PUT /admin/API/mnt/Session/LiveLogSessionData HTTP/1.1", upstream: https://xxxx:9443/admin/API/mnt/Session/LiveLogSessionData
07-16-2024 04:06 PM
Hello @CiscoU9834,
Does your ISE node(s) have the required resources allocated? Is your ISE deployment the appropriate size for your environment?
I cant see a bug-id that matches with this. But if your nodes aren't struggling with resources this sounds like an issue for TAC as requests to your Mnt node(s) are timing out.
09-27-2024 07:17 AM
Hi @Torbjørn ,
beyond Live Logs, any issue on Authentications Summary or RADIUS Authentications (both at Operations > Reports > Reports > Endpoints and Users) ?
07-19-2024 10:48 PM
Hi @CiscoU9834 ,
the only bug that I remembered is CSCwi06794 Live log delay (RADIUS) - Regression for CSCwe00424.
Note: what is your last version/patch before 3.3 P2 ?
Hope this helps !!!
09-27-2024 05:40 AM - edited 09-27-2024 05:42 AM
Same issue here but higher version, we have what Cisco called in the past Super MNT, in our case 3795 with all the specs.
This is a deployment that was upgraded from 2.7 p10 --- > 3.1 last patch --- > 3.3 p2.
We did not have this issue on 2.7.
09-27-2024 07:32 AM - edited 09-27-2024 07:33 AM
In my case te fix with the support was:
-regenerate the ISE root CA of both Nodes
-reboot both nodes
Rebooting only primary node didn't work for us, needed to rebooth both
02-03-2025 02:26 AM
I was facing a similar issue where logs would not populate after a version upgrade. I have tried replacing Cisco ISE messaging service certs, regenerate ISE root CA , rebooting to no avail. But eventually i got the logs fixed by resetting the monitoring database on the Administration node over cli. It is option 4 "Reset MnT database" when using the the following command:
application configure ise
Just putting this out there in case it helps anybody.
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