Se ha producido un evento de temperatura de Blade; exceso/falta de temperatura de CPU u otro componente.
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 IBM 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 IBM 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 IBM 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.
A blade temperature event occurred; CPU or other component over/under temperature.
CPU over temperature.
CPU temperature fault.
Power Module temperature fault.
Insufficient chassis cooling to support blade operations. Blades will be shutdown.
System under recommended ambient temperature.
Chassis ambient over temperature fault.
System ambient under temperature fault.
BEM temperature fault.
I/O Module temperature fault.
Power Module has exceeded the warning temperature.
Reduced chassis cooling capacity. Loss of an additional Chassis Cooling Device will cause blade(s) to shutdown.
Storage Module may power down due to multiple cooling device failures.
System under recommended ambient temperature.
Chassis over recommended ambient temperature.
CPU temperature warning.
CPU over recommended temperature.
BEM over recommended temperature.
I/O Module over recommended temperature.
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 IBM 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 IBM 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.TemperatureRollupMonitor | ||
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 |
<UnitMonitor Accessibility="Internal" ConfirmDelivery="false" Enabled="true" ID="IBM.HWPRO.BladeTemp.TempEvent" ParentMonitorID="IBM.HWPRO.TemperatureRollupMonitor" Priority="Normal" Remotable="true" Target="IBM.HWPRO.VMHost.BladeSystem" TypeID="IBM.HWPRO.RegexEventLogManualReset3StateMonitorType">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="IBM.HWPRO.BladeTemp.TempEvent.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: (6932083[3-4]|69324929|6932493[0-2]|6932185[7-9]|69321860|13642969[7-9]|136429700|167931904|1165568|115842|116736|102876289|24548249[7-9]|24548250[0-6]|136429569|13642957[0-2]|167932160|187066112[1-2]|120832|120066|6932582[5-6]|6932608[1-4]|102880385|24548659[3-9]|24548660[0-2]).*</RegexDescription>
</Configuration>
</UnitMonitor>