Dell OM : Auto Discovery Informational Alert

Dell.ManagedServer.Alert.10635 (Rule)

Knowledge Base article:

Summary

Dell iDRAC Autodiscovery Trap alert

Causes

The Dell iDRAC generated a Autodiscovery trap alert. Probable causes and corresponding resolutions for this condition are:

Cause	Resolutions
The AutoConfig operation is successful.	No response action is required.
The execution of AutoConfig operation is started.	No response action is required.
Unable to start the AutoConfig import operation, because the AutoConfig import file is not available.	Update the sharename or location in the DHCP scope option field where the VendorID=iDRAC, make sure the AutoConfig import file is available, and then retry the operation.
The AutoConfig operation is unable to access a network share folder, because incorrect credentials are specified in the DHCP scope option field where the VendorID=iDRAC.	Verify whether or not the following are correctly entered in the DHCP scope option field where the VendorID=iDRAC, and then retry the operation: 1) Network share name. 2) The IP address of the network share folder. 3) The username and password (-u <username> and -p <password>)
The AutoConfig operation is unable to access the network share folder, because an invalid filename is specified in the DHCP scope option field where the VendorID=iDRAC.	Specify a valid file name in the DHCP scope option field where the VendorID=iDRAC using the (-f <filename>).
The AutoConfig operation is unable to access the network share folder, because an invalid sharetype value is specified in the DHCP scope option field where the VendorID=iDRAC.	Enter a valid sharetype in DHCP scope option field where the VendorID=iDRAC using (-s <0 or="" 1="">) where 0 = NFS, 1 = CIFS.
Unable to start the AutoConfig file import operation, because an invalid shutdown type was specified in the DHCP scope option field where the VendorID=iDRAC.	Enter a valid shutdown type in the DHCP scope option field where the VendorID=iDRAC using (-d <0 or="" 1="">) where 0 = Graceful shutdown and 1 = Forced shutdown.
Unable to start the AutoConfig file import operation, because an invalid AutoConfig time-to-wait value is specified in the DHCP scope option field where the VendorID=iDRAC.	In the DHCP scope option field where VendorID=iDRAC, enter a time-to-wait (-t) value more than 300 seconds and less than 3600 seconds and then retry the operation.
Unable to start the AutoConfig import operation, because Lifecycle Controller is not enabled.	Verify that the Lifecycle Controller firmware on the server being configured is installed and enabled, then restart the iDRAC by pressing the System ID button for 15 seconds. For more information about Lifecycle Controller, see the Lifecycle Controller User Guide available at dell.com/support/manuals.
Unable to start the AutoConfig file import operation, because an invalid End Host Power State value is specified in the DHCP scope option field where the VendorID=iDRAC.	In the DHCP scope option field where VendorID=iDRAC, enter a end-host-power-state (-e <0 or="" 1="">) where 0 = Powered Off and = Powered On, and then retry the operation.
The AutoConfig operation is completed.	No response action is required.
The AutoConfig operation is started.	No response action is required.
The AutoConfig operation is using the <file name> file.	No response action is required.
Unable to start the AutoConfig file import operation, because no options were specified in the DHCP scope option field where the VendorID=iDRAC.	Make sure that the following are correctly entered in the DHCP scope option field where the VendorID=iDRAC, and then retry the operation: 1) Filename -f <filename>). 2) The IP address of the network share folder (-i <ip-address>). 3) Network share name (-n <share-name>). 4) The share type (-s <0 or 2>) where 0 = NFS, 2 = CIFS. 5) The username and password (-u <username> and -p <password>) 6) Shutdown type (-d <0 or 1>) where 0 = Graceful shutdown and 1 = Forced shutdown. 7) Time to wait (-t <value>) where value is more than 300 seconds and less than 3600 seconds.
The AutoConfig feature timed out while waiting for Remote Services to be ready.	Retry the operation. If the issue persists, reset iDRAC. To reset iDRAC by using RACADM command, run the racadm racreset command at the command line interface (CLI). For more information about resetting iDRAC, see iDRAC Users Guide available at the support site.
Unable to start the AutoConfig file import operation, because no options were specified in the DHCP scope option field where the VendorID=iDRAC.	Make sure that the following are correctly entered in the DHCP scope option field where the VendorID=iDRAC, and then retry the operation: 1) Filename -f <filename>). 2) The IP address of the server containing the filename (-i <ip-address>). 3) The share type (-s <0, 2, 4 or 5>) where 0 = NFS, 2 = CIFS, 4 = HTTP, 5 = HTTPS. 4) For share type CIFS and NFS, provide the network share name (-n <share-name>). 5) For share type CIFS, provide the username and password (-u <username> and -p <password>).
Unable to complete the AutoConfig operation because the parameter <parameter name> is not of flag type, which is causing a syntax error.	Enter an appropriate parameter of flag type and retry the operation. For example, -u is a flag indicating the username that has access to network share of CIFS type. For a list of recommended flags, see the Zero-Touch Bare Metal Server Provisioning using Dell iDRAC with Lifecycle Controller Auto Config white paper available at Dell TechCenter website.
Unable to complete the AutoConfig operation because the flag <flag name> is not recognized, which is causing a syntax error.	Enter an appropriate flag and retry the operation. For example, -u is a flag indicating the username that has access to network share of CIFS type. For a list of recommended flags, see the Zero-Touch Bare Metal Server Provisioning using Dell iDRAC with Lifecycle Controller Auto Config white paper available at Dell TechCenter.

Resolutions

Additional information on this issue may be available. Launch the iDRAC Console to debug further.

Element properties:

Target

Dell.ManagedServer

Category

Alert

Enabled

True

Event_ID

10635

Event Source

LifeCycle Controller Log

Alert Generate

True

Alert Severity

Information

Alert Priority

Normal

Remotable

True

Alert Message

Dell OM : Auto Discovery Informational Alert

Event Description: {0}

Event Log

System

Member Modules:

ID	Module Type	TypeId	RunAs
DS	DataSource	Microsoft.Windows.EventProvider	Default
Alert	WriteAction	System.Health.GenerateAlert	Default
WriteToDW	WriteAction	Microsoft.SystemCenter.DataWarehouse.PublishEventData	Default

Source Code:

<Rule ID="Dell.ManagedServer.Alert.10635" Enabled="true" Target="DellManagedServer!Dell.ManagedServer" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>Alert</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Property[Type="DellManagedServer!Dell.ManagedServer"]/HostName$</ComputerName>

      <LogName>System</LogName>

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="UnsignedInteger">10635</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="String">PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="String">LifeCycle Controller Log</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>0</Severity>

      <AlertMessageId>$MPElement[Name="Dell.ManagedServer.Alert.10635.Rule"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue>$Data/EventDisplayNumber$</SuppressionValue>

        <SuppressionValue>$Data/Channel$</SuppressionValue>

        <SuppressionValue>$Data/PublisherName$</SuppressionValue>

        <SuppressionValue>$Data/LoggingComputer$</SuppressionValue>

        <SuppressionValue>$Data/EventCategory$</SuppressionValue>

        <SuppressionValue>$Data/EventLevel$</SuppressionValue>

        <SuppressionValue>$Data/UserName$</SuppressionValue>

        <SuppressionValue>$Data/EventNumber$</SuppressionValue>

        <SuppressionValue>$Data/EventDescription$</SuppressionValue>

      </Suppression>

      <Custom1/>

      <Custom2/>

      <Custom3/>

      <Custom4/>

      <Custom5/>

      <Custom6/>

      <Custom7/>

      <Custom8/>

      <Custom9/>

      <Custom10/>

    </WriteAction>

    <WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>

  </WriteActions>

</Rule>