Blade memory error or memory disabled.
When this monitor is in a warning state: This is a non-critical error and should be handled as soon as possible. When this monitor is in an error state: This is a critical error and should be handled immediately. More details on this event are available through the Lenovo Hardware Management Pack in SCOM. NOTE: If you dismiss this PRO Tip, you will need to manually clear the monitor state of the affected machine in the Lenovo HW PRO MP in SCOM. If you implement this PRO Tip, the machine that generated this event will be placed into Maintenance Mode in SCVMM and any VMs on it will be migrated. You will need to manually remove it from Maintenance Mode once the problem is resolved.
State View: SCVMM-Managed Hosts on Lenovo Servers
Exact details of the problem are available in the "State Change Events" tab in Operations Manager's Health Explorer.
Consult the following knowledge article for possible causes, implications, and resolutions.
Blade memory error or memory disabled.
Memory disabled.
Correctable memory error logging limit reached.
Blade memory fault.
Uncorrectable memory error.
When this monitor is in a warning state: 1. At the earliest convenience, migrate virtual machines and put the host in maintenance mode. 2. Look up more details in Lenovo Hardware Management Pack, perform detailed hardware diagnostics, and/or replace faulty parts. 3. Reactivate the host. When this monitor is in an error state: 1. Immediately migrate virtual machines and put the host in maintenance mode. 2. Look up more details in Lenovo Hardware Management Pack, perform detailed hardware diagnostics, and/or replace faulty parts. 3. Reactivate the host.
| Target | IBM.HWPRO.VMHost.BladeSystem | ||
| Parent Monitor | IBM.HWPRO.PhysicalMemoryRollupMonitor | ||
| Category | AvailabilityHealth | ||
| Enabled | False | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | IBM.HWPRO.RegexEventLogManualReset3StateMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default |
Home
ENU <UnitMonitor Accessibility="Internal" ConfirmDelivery="false" Enabled="true" ID="IBM.HWPRO.BladeMemoryEvent" ParentMonitorID="IBM.HWPRO.PhysicalMemoryRollupMonitor" Priority="Normal" Remotable="true" Target="IBM.HWPRO.VMHost.BladeSystem" TypeID="IBM.HWPRO.RegexEventLogManualReset3StateMonitorType">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="IBM.HWPRO.BladeMemoryEvent.AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="System!System.Entity"]/DisplayName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState HealthState="Error" ID="Error" MonitorTypeStateID="ErrorEventRaised"/>
<OperationalState HealthState="Warning" ID="Warning" MonitorTypeStateID="WarningEventRaised"/>
<OperationalState HealthState="Success" ID="Success" MonitorTypeStateID="ManualResetEventRaised"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<EventSourceName>Director Agent</EventSourceName>
<EventDisplayNumber>18</EventDisplayNumber>
<RegexDescription>.*Event ID: (16777356[8-9]|16777357[0-9]|16777358[0-4]|16777318[4-9]|16777319[0-9]|167773200|85983232|16777280[0-9]|16777281[0-6]).*</RegexDescription>
</Configuration>
</UnitMonitor>