Fault Rule : ServiceProfile.F0327 (configuration-failure)

Cisco.Ucsm.ServiceProfile.F0327.Rule (Rule)

Fault Rule : ServiceProfile.F0327 (configuration-failure)Description

Knowledge Base article:

Summary

Service profile [name] configuration failed due to [serverConfigIssues],[networkConfigIssues],[storageConfigIssues],[vnicConfigIssues],[iscsiConfigIssues]

Cause

configuration-failure

Fault Detail

Description

Fault Name

Ls Server Config Failure

Fault Code

F0327

Explanation

The named configuration qualifier is not available. This fault typically occurs because Cisco UCS Manager cannot successfully deploy the service profile due to a lack of resources that meet the named qualifier. For example, this fault can occur if the following occurs:

  • The service profile is configured for a server adapter with vHBAs, and the adapter on the server does not support vHBAs.

  • The service profile is created from a template which includes a server pool, and the server pool is empty.

  • The local disk configuration policy in the service profile specifies the No Local Storage mode, but the server contains local disks.

Recommended Actions

If you see this fault, take the following actions:

  • Check the status of the server pool associated with the service profile. If the pool is empty, add more blade servers to it.

  • Check the state of the server and ensure that it is in either the discovered or unassociated state.

  • If the server is associated or undiscovered, do one of the following: Discover the server.Disassociate the server from the current service profile.Select another server to associate with the service profile.

  • Discover the server.

  • Disassociate the server from the current service profile.

  • Select another server to associate with the service profile.

  • Review each policy in the service profile and verify that the selected server meets the requirements in the policy.

  • If the server does not meet the requirements of the service profile, do one of the following: Modify the service profile to match the server.Select another server that does meet the requirements to associate with the service profile.

  • Modify the service profile to match the server.

  • Select another server that does meet the requirements to associate with the service profile.

  • If you can verify that the server meets the requirements of the service profile, create a show tech support file and contact Cisco TAC. Click Here

Related Links

Get more details on Cisco UCS faults:

Cisco UCS Faults and Error Messages Reference

Management Pack Information

Cisco UCS Manager Management Pack

Element properties:

TargetCisco.Ucs.ServiceProfile
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityHigh
RemotableTrue
Alert Message
ServiceProfile.F0327: configuration-failure

[Instance Name:{1}; DN:{2}]
Description: {0}
Event LogCisco UCS Monitoring Service

Member Modules:

ID Module Type TypeId RunAs 
EventProviderDS DataSource Microsoft.Windows.EventProvider Default
GenerateAlert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Cisco.Ucsm.ServiceProfile.F0327.Rule" Enabled="true" Target="Cisco.Ucs.ServiceProfile">
<Category>Alert</Category>
<DataSources>
<DataSource ID="EventProviderDS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Property[Type="Cisco.Ucs.Object"]/MonitoringServer$</ComputerName>
<LogName>Cisco UCS Monitoring Service</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">17101</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">FaultData</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[2]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">$Target/Property[Type="Cisco.Ucs.Object"]/TypeId$</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[7]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">F0327</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[3]</XPathQuery>
</ValueExpression>
<Operator>ContainsSubstring</Operator>
<Pattern>$Target/Property[Type="Cisco.Ucs.Entity"]/Moniker$</Pattern>
</RegExExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[10]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">$Target/Property[Type="Cisco.Ucs.Object"]/ClassName$</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[15]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">AlertGenerated</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="Health!System.Health.GenerateAlert">
<Priority>2</Priority>
<Severity>2</Severity>
<AlertMessageId>$MPElement[Name="Cisco.Ucsm.ServiceProfile.F0327.Rule.StringResource"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/Params/Param[1]$</AlertParameter1>
<AlertParameter2>$Data/Params/Param[24]$</AlertParameter2>
<AlertParameter3>$Data/Params/Param[3]$</AlertParameter3>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/Params/Param[2]$</SuppressionValue>
<SuppressionValue>$Data/Params/Param[3]$</SuppressionValue>
<SuppressionValue>$Data/Params/Param[7]$</SuppressionValue>
<SuppressionValue>$Data/Params/Param[9]$</SuppressionValue>
<SuppressionValue>$Data/Params/Param[11]$</SuppressionValue>
</Suppression>
<Custom1>$Data/Params/Param[2]$</Custom1>
<Custom2>$Data/Params/Param[5]$</Custom2>
<Custom3>$Data/Params/Param[14]$</Custom3>
<Custom4>$Data/Params/Param[7]$</Custom4>
<Custom5>$Data/Params/Param[8]$</Custom5>
<Custom6>$Data/Params/Param[9]$</Custom6>
<Custom7>$Data/Params/Param[24]$</Custom7>
<Custom8>$Data/Params/Param[11]$</Custom8>
<!--<Custom9>$Data/Params/Param[12]$</Custom9>-->
<Custom9>$Data/Params/Param[23]$</Custom9>
<Custom10>$Data/Params/Param[3]$</Custom10>
</WriteAction>
</WriteActions>
</Rule>