VMware Cloud Community
jprevett
Contributor
Contributor

Host Memory Usage alarm stuck

One of the hosts in my VI3 cluster is reporting a yellow alarm for Memory usage. The date on the alarm is from last friday and when you look at the %memory used within VCenter it shows only 48%. I have no doubt that the host may have gone above the threshold of 75% but now that it is back down, it still shows up in alarm state...

I have checked the alarm in question and the values are correct (75% and 90%). I have even tried setting the alarms to 95% and 100% to see if I could get the status to change but it will not.

It acts like it is stuck..... Any ideas?

0 Kudos
13 Replies
admin
Immortal
Immortal

What versions of ESX / VC?

There have been numerous fixes in VCMS Patch 2

0 Kudos
jprevett
Contributor
Contributor

Sorry...

VI 2.0.1 build 40644

ESX 3.0.1, 34176

current usage shows 15.36GB out of 32GB

Cluster host view shows this host at 31%CPU and 48%Mem....

Alarm is set currently at 95% and 100% on memory usage...

Still shows up as yellow.

0 Kudos
mikepodoherty
Expert
Expert

Try clicking on the performance tab. When we've seen the alarms for memory usage, clicking on the performance tab in VC clears the alarm.

0 Kudos
jprevett
Contributor
Contributor

Yeah I tried that, switched to memory real-time, then by week and it shows the data, but the alarm is still there....

0 Kudos
BenConrad
Expert
Expert

Restart the VC service?

0 Kudos
jprevett
Contributor
Contributor

The fix was to disable and enable the alarm. Once enabled, the warning went away.

0 Kudos
chrisbuzby
Enthusiast
Enthusiast

I am (was) having the same problem, I did the same (disabled and renabled the alarm to fix....

Thanks for posting the solution.

0 Kudos
cryptonym
Enthusiast
Enthusiast

This doesn't "fix" it, it just clears it for now. The problem will come back, again and again.

0 Kudos
nobleone
Contributor
Contributor

Was there ever a permanent fix for this issue. I see it is still an issue in 2.5/3.5

0 Kudos
cryptonym
Enthusiast
Enthusiast

The last update I had was:

"As I understand it in VC 2.5 you are having triggers that seem to be "stuck"

or that do not seem to update. There is currently an open PR on this with are

engineering team and this is to be addressed in VC 2.5 U1 (exact release date

yet to be determined)

The PR number of this bug is 204116"

0 Kudos
nobleone
Contributor
Contributor

thanks for the info. I'll have to keep a watch for the update.

I'm surprised they've let this issue slide for so long

0 Kudos
DarrenBolton
Contributor
Contributor

so did U1 for VC2.5 resolve this issue?

0 Kudos
M1NZ
Contributor
Contributor

We are on VC 2.5.0 and we have the same issue with one of the servers seems ok but the alarm is stuck on Memory Usage

0 Kudos