ISE dashboard not showing CPU RAM usage for Admin/monitor and PSN

[Gustavo Novais]

Hello,

I have a distributed deployment in pilot with one node dedicated to Admin/Monitoring and another dedicated to PSN.

On the dashboard, (httping to the admin node) neither of the nodes show their CPU and RAM stats (appear as grey icon).

logging to 20514 is pointing to the primary admin node.

Does anybody have any insight?

Have already resynched deployment with no success.

Thanks

Gustavo.

[shekharmore003]

Are you mean to say that, you are login to admin node and you are even not able to see CPU and Memory status for admin node.

Could you please paste the screenshot.

[Gustavo Novais]

Yes I did mean to say that. no CPU info on admin own node.

Screen shot attached

Thanks

[shekharmore003]

Login through CLI and check following commands. And I am not able to see the screenshot, could you please upload it again.

sh memory

sh cpu statistics

[Gustavo Novais]

Hi shekharmore003

Here's the info (please check the screenshot I've just uploaded)

hqbusxam03/adminet# sh cpu statistics

user time:            4017788

kernel time:           561260

idle time:          424602418

i/o wait time:        2737451

irq time:               61331

hqbusxam03/adminet# sh memory

total memory:    3997824 kB

free memory:      573840 kB

cached:          1756508 kB

swap-cached:           0 kB

[shekharmore003]

Its working. I think there must be a problem with browser. I dont know where you uploaded the screenshot but I am not able find it.

[Gustavo Novais]

I've uploaded it into the post where I said screenshot attached.

I know that the boxes are working. What is bugging me is the fact that the common operator will not be able to see cpu and ram stats on the nodes.

HAve you experienced it?

[Gustavo Novais]

Just to add, that it appears that since the 27Feb the system status/process status is not synched across both nodes.

The system reports show this.

the change that happened at this time is that due to bad timezone choice, we had to reset the application ise status, and reconfigure the nodes.

If anybody has seen this please let me know. Is there any solution except reinstalling the nodes?