Data Centers

Modifying the host memory usage alarm in vSphere

The vSphere host memory usage alarm is a good indicator of when the host starts to swap memory on disk. If the alarm needs to be dismissed automatically, learn how to do so for a lab or development environment.

I run vSphere in my personal lab, and I am constantly pushing my memory configuration to the max. To try to keep up with this moving target, I add more memory to the ESXi hosts every few months, yet I still find myself pushing the limits of my lab's capabilities.

One of the little irritations of this configuration is the host memory usage alarm; this kicks in when the host crosses 90% usage of memory to warning state and to alert state at 95% usage, sustained for five minutes in both cases. I would definitely keep this alarm active in production environments, but for lab or development environments, this value can be tweaked upward to reduce potentially unnecessary alarms for non-critical systems.

Figure A shows the host memory alarm's default configuration. Figure A

Click the image to enlarge.
If you enter a new number in the warning limit, it will identify when the alarm condition will engage again. In my lab environment, I am happy with using 98% for warning and 99% for alert levels. This new configuration is shown in Figure B. Figure B

Click the image to enlarge.

The magic here is that these values can be applied in a hierarchical fashion. The default values are stored in the parent container of the vCenter Server. Individual hosts or clusters can have their own values for alarms, so a development cluster can have a relaxed alarm threshold, while the production environment in the same vSphere data center can have the default arrangement.

Do you modify the alarm levels for some of the built-in vSphere alarms? If so, share your tweaks in the discussion.

About

Rick Vanover is a software strategy specialist for Veeam Software, based in Columbus, Ohio. Rick has years of IT experience and focuses on virtualization, Windows-based server administration, and system hardware.

3 comments
David.R
David.R

I'm using vSphere 4.1 and I don't seem to be able to do this. Tweaking the alarm definitions in a child is not allowed. Seems like I can only view the Alarm definitions from the child. When viewing an alarm definition there's some text at the bottom of the dialog that says.. "This alarm was defined in . Alarm Settings are read-only except when accessed through the object they were defined." I also tried creating a new alarm definition at the child level with higher thresholds but the parent alarm still gets triggered. Am I missing something ? How are you able to override things as you described ?

David.R
David.R

I'm using vSphere 4.1 and I don't seem to be able to do this. Tweaking the alarm definitions in a child is not allowed. Seems like I can only view the Alarm definitions from the child. When viewing an alarm definition there's some text at the bottom of the dialog that says.. "This alarm was defined in . Alarm Settings are read-only except when accessed through the object they were defined." I also tried creating a new alarm definition at the child level with higher thresholds but the parent alarm still gets triggered. Am I missing something ? How are you able to override things as you described ?

cxdbfxcgvbc
cxdbfxcgvbc

========== (w w w).( better wholesaler).u s ====== BEST QUALITY GUARANTEE!! Great convenience to online shopping lower p r i c e fast shi p p m e n t with higher q u a l i t y , ??? good web believe you will love it.??? ---Something unexpected surprise--

Editor's Picks