Fujitsu PRIMERGY ESXi Server Processor Component Count Monitor

Fujitsu.Servers.PRIMERGY.ESXi.Processors.CountMonitor (UnitMonitor)

Unit Monitor runs a script to retrieve Processors component count

Knowledge Base article:

Summary

This component count monitor runs a script on the target system to check the number of PRIMERGY Processors.

Causes

PRIMERGY Processors represent the individual processors of the server. Further information can be obtained to look through State Change Events tab in the Health Explorer, Alerts on Active Alerts View and Fujitsu ServerView System Monitor task.

Resolutions

If this monitor is in Warning or Critical state, please look for related alerts to this server/component. First check the running status of the ServerView CIM Provider. Also launch Fujitsu ServerView System Monitor or ServerView Remote Management iRMC Console task for more information and further diagnostic.

Element properties:

TargetFujitsu.Servers.PRIMERGY.ESXi.Processors
Parent MonitorSystem.Health.AvailabilityState
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeFujitsu.Servers.PRIMERGY.ESXi.PRIMERGYHealthState
RemotableTrue
AccessibilityPublic
Alert Message
{0}: One ore more components of the 'Processors' subsystem of a Fujitsu PRIMERGY ESXi Server are missing.
{0}: One or more instances of the PRIMERGY subsystem 'Processors' are missing. Check the running status of the ServerView CIM Provider.
RunAsDefault

Source Code:

<UnitMonitor ID="Fujitsu.Servers.PRIMERGY.ESXi.Processors.CountMonitor" Accessibility="Public" Enabled="true" Target="Fujitsu.Servers.PRIMERGY.ESXi.Processors" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Fujitsu.Servers.PRIMERGY.ESXi.PRIMERGYHealthState" ConfirmDelivery="false">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="Fujitsu.Servers.PRIMERGY.ESXi.Processors.CountMonitor.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="Fujitsu.Servers.PRIMERGY.ESXi.HealthCollection"]/NetworkName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="OK" MonitorTypeStateID="HealthSuccess" HealthState="Success"/>
<OperationalState ID="Degraded" MonitorTypeStateID="HealthWarning" HealthState="Warning"/>
<OperationalState ID="Error" MonitorTypeStateID="HealthError" HealthState="Error"/>
</OperationalStates>
<Configuration>
<IntervalSeconds>480</IntervalSeconds>
<PrincipalName>$Target/Host/Host/Host/Property[Type="FTSESXSEED!Fujitsu.Servers.PRIMERGY.ESXiSeed.HostServer"]/PrincipalName$</PrincipalName>
<TargetName>$Target/Host/Host/Property[Type="FTSESXSEED!Fujitsu.Servers.PRIMERGY.ESXiSeed.Server"]/PrincipalName$</TargetName>
<IPAddress>$Target/Host/Host/Property[Type="FTSESXSEED!Fujitsu.Servers.PRIMERGY.ESXiSeed.Server"]/IPAddress$</IPAddress>
<CIMPort>$Target/Host/Host/Property[Type="FTSESXSEED!Fujitsu.Servers.PRIMERGY.ESXiSeed.Server"]/CIMPort$</CIMPort>
<NoCertCheck>$Target/Host/Host/Property[Type="FTSESXSEED!Fujitsu.Servers.PRIMERGY.ESXiSeed.Server"]/NoCertCheck$</NoCertCheck>
<Component>Processors</Component>
<Type>InstanceCount</Type>
</Configuration>
</UnitMonitor>