Fujitsu PRIMERGY PRO temperature monitoring degraded

Fujitsu.PRIMERGY.PRO.TemperatureMonitoringDegraded (UnitMonitor)

Knowledge Base article:

Summary

Temperature monitoring degraded

Causes

System is degraded because the indicated temperature sensor is broken.

Resolutions

Fujitsu recommends to exclude the server temporarily from placement of new virtual machines. This is the default behavior when you press "Implement" in the VMM PRO Tip window. If you have overridden the default behavior in SCOM please refer to your customized settings for the behavior of the "Implement" button.

Further Resolutions:

1) Verify that all air flow channels are correctly installed, that the housing is closed and that the louvers are not blocked.

2) Verify whether the temperature within your environment did not increase above 35C.

3) Verify that latest BIOS revision and BMC firmware is installed.

4) If the problem persists call your local Fujitsu Helpdesk.

Element properties:

TargetFujitsu.PRIMERGY.PRO.FujitsuManagedHost
Parent MonitorSystem.Health.AvailabilityState
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.2SingleEventLog2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Temperature monitoring degraded
Warning PRO alert, source: ServerView agents
RunAsDefault

Source Code:

<UnitMonitor ID="Fujitsu.PRIMERGY.PRO.TemperatureMonitoringDegraded" Accessibility="Public" Enabled="true" Target="Fujitsu.PRIMERGY.PRO.FujitsuManagedHost" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.2SingleEventLog2StateMonitorType" ConfirmDelivery="false">
<Category>Custom</Category>
<AlertSettings AlertMessage="Fujitsu.PRIMERGY.PRO.TemperatureMonitoringDegraded_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
</AlertSettings>
<OperationalStates>
<OperationalState ID="FirstEventRaised" MonitorTypeStateID="FirstEventRaised" HealthState="Warning"/>
<OperationalState ID="SecondEventRaised" MonitorTypeStateID="SecondEventRaised" HealthState="Success"/>
</OperationalStates>
<Configuration>
<FirstComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>
<FirstLogName>Application</FirstLogName>
<FirstExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">12024</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>MatchesRegularExpression</Operator>
<Pattern>^ServerView Agents$</Pattern>
</RegExExpression>
</Expression>
</And>
</FirstExpression>
<SecondComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>
<SecondLogName>Application</SecondLogName>
<SecondExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">1</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">ServerView Agents</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</SecondExpression>
</Configuration>
</UnitMonitor>