Home
  •  

Fault Rule : F0832 (config-error)

Cisco.Ucsm.F0832.Rule (Rule)

Fault Rule : F0832 (config-error) Description

Knowledge Base article:

Summary

Port constraint violation on switch [id]: [confQual]

Cause

config-error

Fault Detail

Description

Fault Name

Fabric Ep Mgr Ep Trans Mode Fail

Fault Code

F0832

Explanation

This fault occurs when at least one logical interface is misconfigured. This can happen when upgrading to a different type or series of fabric interconnect or when importing a configuration. The configuration must meet the following constraints: <ul> <li>The first Fibre Channel port must be an odd port number. This constraint cannot be violated when upgrading from a Cisco UCS 6100 series fabric interconnect to a Cisco UCS 6200 series fabric interconnect.</li> <li>All FC ports must be configured contiguously with intervening unconfigured FC ports. This can happen during an upgrade from a Cisco UCS 6100 series fabric interconnect when you import the configuration from a Cisco UCS 6100 series fabric interconnect configuration into a Cisco UCS 6200 series fabric interconnect. For example, the Cisco UCS 6100 series fabric interconnect has an FC expansion module with ports FC2/1 through FC2/6 configured. When you import that configuration into a Cisco UCS 6200 series fabric interconnect, FC ports 2/7 through 2/16 remain unconfigured. You can correct this problem by configuring the missing FC ports.</li> <li>Ethernet and FC port ranges cannot overlap. This can happen when upgrading from a Cisco UCS 6100 series fabric interconnect to a Cisco UCS 6200 series fabric interconnect. For example, some Cisco UCS 6100 expansion modules have FC and Ethernet ports with the same ID, such as FC port 2/1 and Ethernet port 2/1.</li> <li>There must be at most one logical port per fabric interconnect ID/module ID/port ID. For example, a port cannot be configured as both Ethernet and FC. This can happen during an upgrade from a Cisco UCS 6100 series fabric interconnect. For example, some Cisco UCS 6100 expansion modules have FC and Ethernet ports with the same ID, such as FC port 2/1 and Ethernet port 2/1.</li> <li>Within a module, the port IDs of Ethernet ports must be lower than the smallest FC port ID. This means that all Ethernet ports must be on the left and all FC ports on the right. This can happen during an upgrade from a Cisco UCS 6140 fabric interconnect with 40 ports on the fixed module to a Cisco UCS 6248 fabric interconnect with 32 ports on the fixed module. For example, if the Cisco UCS 6248 is initially configured with Ethernet ports 1/1 through 1/16 and FC ports 1/17 through 1/32, and you import a a configuration from the Cisco UCS 6140 with Ethernet ports 1/1 through 1/32 unconfigured and Ethernet ports 1/33 through 1/40, the resulting configuration is Ethernet 1/1 through 1/16, FC 1/17 through 1/32, and Ethernet 1/33 through 1/40. This is not a valid configuration. You must delete ports 1/33 through 1/40 to correct the configuration.</li> <li>A non unified Ethernet port cannot be configured as an FC port. Please note the following: </ul><ul> <li>This constraint cannot be violated when upgrading from a Cisco UCS 6100 series fabric interconnect to a Cisco UCS 6200 series fabric interconnect.</li> <li>This constraint can be violated when downgrading from a Cisco UCS 6200 series fabric interconnect to a Cisco UCS 6100 series fabric interconnect. </li> <li>This constraint can be violated when pre provisioning a port on a Cisco UCS 6100 series fabric interconnect and then inserting an expansion module that does not match the requirement.</li> </ul></li> <li>A non unified FC port cannot be configured as an Ethernet port. Please note the following: <ul> <li>This constraint cannot be violated when upgrading from a Cisco UCS 6100 series fabric interconnect to a Cisco UCS 6200 series fabric interconnect.</li> <li>This constraint can be violated when downgrading from a Cisco UCS 6200 series fabric interconnect to a Cisco UCS 6100 series fabric interconnect. </li> <li>This constraint can be violated when pre provisioning a port on a Cisco UCS 6100 series fabric interconnect and then inserting an expansion module that does not match the requirement.</li> </ul></li> <li>On a Cisco UCS 6100 series fabric interconnect, server ports cannot be configured on expansion modules. This constraint can be violated when downgrading from a Cisco UCS 6200 series fabric interconnect to a Cisco UCS 6100 series fabric interconnect.</li> </ul>

Recommended Actions

If you see this fault, take the following action:

  • Create a list of all logical interfaces that are misconfigured and have caused an 'error misconfigured' fault.

  • For each logical interface, note the reason listed in the fault for the misconfiguration.

  • Log into Cisco UCS Manager and correct each misconfigured logical interface. If you used the Cisco UCS Manager CLI, commit all changes.

  • Review any faults or error messages that describe additional misconfigurations and correct those errors.

  • If the above actions did not resolve the issue, 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.Proxy
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityHigh
RemotableTrue
Alert Message
F0832: config-error

[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.F0832.Rule" Enabled="true" Target="Cisco.Ucs.Proxy">

  <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">F0832</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <Or>

              <Expression>

                <SimpleExpression>

                  <ValueExpression>

                    <XPathQuery Type="String">Params/Param[10]</XPathQuery>

                  </ValueExpression>

                  <Operator>Equal</Operator>

                  <ValueExpression>

                    <Value Type="String">Miscellaneous</Value>

                  </ValueExpression>

                </SimpleExpression>

              </Expression>

              <Expression>

                <And>

                  <Expression>

                    <SimpleExpression>

                      <ValueExpression>

                        <XPathQuery Type="String">Params/Param[10]</XPathQuery>

                      </ValueExpression>

                      <Operator>Equal</Operator>

                      <ValueExpression>

                        <Value Type="String">ComputeSystem</Value>

                      </ValueExpression>

                    </SimpleExpression>

                  </Expression>

                  <Expression>

                    <RegExExpression>

                      <ValueExpression>

                        <XPathQuery Type="String">Params/Param[3]</XPathQuery>

                      </ValueExpression>

                      <Operator>ContainsSubstring</Operator>

                      <Pattern>$Target/Property[Type="Cisco.Ucs.Proxy"]/Id$</Pattern>

                    </RegExExpression>

                  </Expression>

                </And>

              </Expression>

            </Or>

          </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.Proxy.F0832.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>