ISE 3.3 Patch 2 - Stuck Live Logs page

[CiscoU9834]

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

[Torbjørn]

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.

[Marcelo Morais]

Hi @Torbjørn ,

 beyond Live Logs, any issue on Authentications Summary or RADIUS Authentications (both at Operations > Reports > Reports > Endpoints and Users) ?

[Marcelo Morais]

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 !!!

[ajc]

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.

[CiscoU9834]

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