|
Each instance of the MS_HW_MEMORY module represents a memory module in the server.
The Status parameter will raise an "on the fly" alert on servers that can dynamically handle failed memory modules or, most often, for modules that have been disabled by the BIOS upon reboot (the module is then flagged as "missing").
The ErrorCount parameter represents the number of errors that have been fixed by ECC-enabled memory modules. Sometime the number of detected errors cannot be shown and the ErrorStatus parameter is used instead to raise an alert when too many errors have been detected and corrected, meaning that the memory module is about to fail.
In some case, the PredictedFailure parameter is used to alert administrators that the memory module is about to fail. The use of the ErrorCount, ErrorStatus or PredictedFailure parameter highly depends on the technology being used to report the health of memory modules.
Icon
Parameters
|
|
|
|
|
|
ErrorCount
|
Number of detected (and possibly, corrected) errors.
Value set by memoryColl every 2 minutes.
|
errors
|
1 = Warning (*)
|
Statistics
|
ErrorStatus
|
This parameter will trigger an alert if the number of memory errors reaches a threshold set by the manufacturer’s agent.
Value set by memoryColl every 2 minutes.
|
{0 = No Errors ; 1 = Detected Errors ; 2 = Too Many Errors}
|
1 = Warning
2 = Alarm
|
Availability
|
Missing (**)
|
When the memory module is no longer discovered, the parameter goes into alarm
|
{0 = Present ; 1 = Missing}
|
1 = Alarm
|
Availability
|
PredictedFailure
|
This parameter will trigger a warning if a memory failure is predicted to happen.
Value set by memoryColl every 2 minutes.
|
{0 = OK ; 1 = Failure Predicted}
|
1 = Alarm
|
Availability
|
Status
|
Memory Status.
Value set by memoryColl every 2 minutes.
|
{0 = OK; 1 = Degraded; 2 = Failed}
|
1 = Warning
2 = Alarm
|
Availability
|
StatusInformation
|
Additional (textual) information about the current status of the memory.
|
n/a
|
None
|
--
|
| (*) | These thresholds are automatically set by Hardware Sentry KM according to your environment and the recommendation of the system manufacturer during each discovery (by default, every hour). To customize these thresholds and prevent Hardware Sentry KM from overwriting your settings, you will need to use the “Modify Thresholds” KM Command.
It is not recommended to modify these thresholds. |
| (**) | The “Missing” parameter is dynamically activated only when the monitored component goes missing. As long as the monitored component is properly discovered and monitored, the “Missing” parameter cannot be displayed in the console. When the “Missing” parameter is activated, its value is always ‘1’, which triggers an alarm. You can disable the missing device detection mechanism in the settings of the KM. |
 | Depending on your system, all parameters may not be used. Only one of the parameters may be visible. This will not affect the proper monitoring of the device. |
InfoBox
|
|
|
ID
|
Memory module’s PATROL internal identifier. This ID is used for PATROL event reporting etc.
|
Connector Display Name
|
Display name of the Connector currently used to monitor the Memory module.
|
Connector File Name
|
File name of the Connector currently used to monitor the Memory module.
|
Menu Commands
See Also
Component monitoring
Memory module monitoring
|
