Quantcast
Channel: VMware Communities : Discussion List - ESXi
Viewing all articles
Browse latest Browse all 8132

Query on memoryStatusInfo

$
0
0

Hi

 

 

 

ESXI 5.5.0 2068190 on IBM x3650 M3, 48GB RAM, Dual x5650 - Only Three VMs: 2012R2, Zabbix Appliance, Centos

 

 

 

This is just a query as the system is working fine (for now).

 

 

 

I have recently started using VEEAM ONE (Free) to monitor this ESXI Server and am getting an alarm alert for Host Hardware Status : Sensor "Memory" equal Alert. 

 

This seems to correspond to the following VMware (so I dont think its a VEEAM ONE issue) MOB: content -> rootFolder -> childEntity -> hostFolder -> childEntity -> host -> runtime -> healthSystemRuntime -> hardwareStatusInfo -> memoryStatusInfo

 

 

 

This is showing: Key = "Red", label = "Red", summary = "The physical element is failing"

 

 

 

My question is what does this mean? What checks is it making for this value?

 

 

 

I have shut the machine down and ran extensive hardware tests using the built in IBM System Diagnostics and it found nothing (that it reported).  I ran its dedicated memory check and that was good.  The light path is not showing any error codes.

 

 

 

The VMs are working, and I cannot see this error in the VSphere Client - I may not be looking in the right place, the "Health Status" screen shows all Green Ticks and Normal status.  I really only became aware of the issue due to VEEAM ONE.

 

 

 

I did try to search the documentation but this page: https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.host.HardwareStatusInfo.html was the best I could find and it just says "Status of the physical memory" which I don't understand.

 

 

 

I have another IBM machine (M2) which VEEAM is connected to and MOB is green for this one.

 

 

 

Thanks is advance for any help or pointers

 

 

Pete


Viewing all articles
Browse latest Browse all 8132

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>