Dell CMC SNMP Trap : Storage Virtual disk information

Dell.ModularChassis.CMC4355 (Rule)

Dell CMC has generated Storage Virtual disk information event.

Knowledge Base article:

Summary

Dell CMC has generated Storage Virtual disk information event

Causes

Probable causes and corresponding resolutions for this condition are:

Cause	Resolutions
Background initialization has completed for <virtual disk>.	No response action is required.
<VD Name> initialization is in-progress <progresspercent>.	No response action is required.
Dead disk segments are restored on <VD Name>. Disk space that was formerly "dead" or inaccessible to a redundant virtual disk has been restored. This alert is provided for informational purposes.	No response action is required.
<VD Name> is renamed.	No response action is required.
The check consistency has made corrections and completed for <VD Name>. The virtual disk check consistency has identified errors and made corrections. For example, the check consistency may have encountered a bad disk block and remapped the disk block to restore data consistency.	This Alert is for informational purposes only and no additional action is required. As a precaution, monitor the Alert Log for other errors related to this virtual disk. If problems persist, contact Dell Technical Support.
<virtual disk> was created. This message is generated after a virtual disk was created on a controller.	No response action is required.
The reconfiguration of <virtual disk> has resumed. This message is generated after the reconfiguration of a virtual disk resumes.	No response action is required.
<VD Name> read policy has changed.	No response action is required.
Dedicated hot spare assigned physical disk <args>.	No response action is required.
Dedicated hot spare unassigned physical disk <args>.	No response action is required.
<VD Name> disk cache policy has changed.	No response action is required.
<VD Name> blink has been initiated.	No response action is required.
<VD Name> blink has ceased.	No response action is required.
A disk media error was corrected on <virtual disk>. A disk media error was detected while the controller was completing a background task. A bad disk block was identified. The disk block was remapped.	Check the Lifecycle log for information related to members of this virtual disk.
<VD Name> has inconsistent data.	No response action is required.
<VD Name> is permanently degraded. A redundant virtual disk has lost redundancy. This may occur when the virtual disk suffers the failure of more than one physical disk. In this case, both the source physical disk and the target disk with redundant data have failed. A rebuild is not possible because there is no longer redundancy.	Replace the failed disks and restore from backup.
<virtual disk> was deleted. The controller removed a virtual disk. This is due to a delete virtual disk operation, a reset configuration operation, or the removal of every physical disk that was a member of the virtual disk.	No response action is required.
<virtual disk> has started initializing.	No response action is required.
<virtual disk> reconfiguration has started.	No response action is required.
The consistency check on <virtual disk> was cancelled. A user cancelled the consistency check operation for a virtual disk.	No response action is required.
Initialization of <virtual disk> was cancelled.	If a physical disk failed, then replace the physical disk. Restart the virtual disk initialization.
<virtual disk> returned to optimal state.	No response action is required.
Consistency check for <virtual disk> has completed.	No response action is required.
Initialization of <virtual disk> has completed.	No response action is required.
Reconfiguration of <virtual disk> has completed.	No response action is required.
<virtual disk> write policy has changed.	This alert is provided for informational purposes.
Background initialization has started for <virtual disk>. Background initialization of a virtual disk has started. This is an automated process that writes the parity or mirror data on newly created virtual disks.	No response action is required.
Background initialization was cancelled for <virtual disk>. Background initialization of a virtual disk was cancelled. This may be due to user action. This operation may automatically restart.	No response action is required.
The check consistency has made corrections and completed for <VD Name>.	No response action is required.
The consistency check process made corrections and completed on <virtual disk>.	No response action is required.
Redundancy of <virtual disk> has been degraded. This message occurs when a physical disk in the disk group was removed or when a physical disk included in a redundant virtual disk fails. Because the virtual disk is redundant (uses mirrored or parity information) and only one physical disk has failed, the virtual disk can be rebuilt. Typically, the virtual disk (E.g. RAID 6) has multiple redundant disks and there is a problem with one of them.	Replace the missing or failed physical disk.
Background Initialization in <VD Name> corrected medium error. A disk media error was detected while the controller was completing a background task. A bad disk block was identified. The disk block has been remapped.	Consider replacing the disk. If you receive this alert frequently, ensure to replace the disk. It is recommended to routinely back up your data.
<VD Name> security has failed.	No response action is required.
<virtual disk> consistency check has started.	No response action is required.
<VD Name> bad block medium error is cleared.	No response action is required.
Controller preserved cache was recovered for <virtual disk>.	No response action is required.
Unable to log block <arg>.Bad block table on <VD Name> is full.	Replace the disk in the Virtual disk, generating this alert and restore from backup. You may have lost data.
<VD Name> rebuild has started.	No response action is required.
<VD Name> rebuild failed.	Replace the failed or corrupt disk. You can identify a disk that has failed by locating the disk that has a red "X" for its status. Restart the virtual disk rebuild.
Formatting the <VD Name> is completed.	No response action is required.
Bad block table on <virtual disk> is 80 percent full.	Replace the disk in the Virtual disk, generating this message.

Resolutions

Launch the CMC Console to debug further.

Element properties:

Target

Dell.ModularChassis.CMC

Category

AvailabilityHealth

Enabled

True

Alert Generate

True

Alert Severity

Information

Alert Priority

Normal

Remotable

True

Alert Message

Dell Chassis Management Controller trap : Storage Virtual disk information

Dell CMC has generated Storage Virtual disk information event.

Member Modules:

ID	Module Type	TypeId	RunAs
DS	DataSource	Dell.SNMPTrap.DSMT	Default
Alert	WriteAction	System.Health.GenerateAlert	Default

Source Code:

<Rule ID="Dell.ModularChassis.CMC4355" Enabled="true" Target="DAD!Dell.ModularChassis.CMC" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>AvailabilityHealth</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Dell.SNMPTrap.DSMT">

      <IP>$Target/Property[Type="DAD!Dell.ModularChassis.CMC"]/IPAddress$</IP>

      <ServiceTag>$Target/Property[Type="DAD!Dell.ModularChassis.CMC"]/ServiceTag$</ServiceTag>

      <Status>Informational</Status>

      <Severity>0</Severity>

      <AllTraps>false</AllTraps>

      <OIDProps>

        <OIDProp>.1.3.6.1.4.1.674.10892.2.21.0.4355</OIDProp>

      </OIDProps>

      <EventOriginId>$Target/Id$</EventOriginId>

      <PublisherId>$Target/Id$</PublisherId>

      <PublisherName>Snmp Event</PublisherName>

      <Channel>SnmpEvent</Channel>

      <LoggingComputer/>

      <EventNumber>4355</EventNumber>

      <EventCategory>5</EventCategory>

      <EventLevel>10</EventLevel>

      <UserName/>

      <Params/>

    </DataSource>

  </DataSources>

  <WriteActions>

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

      <Priority>1</Priority>

      <Severity>0</Severity>

      <AlertMessageId>$MPElement[Name="Dell.ModularChassis.CMC.Rule4355"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventData/DataItem/Property[@Name="Status"]$</AlertParameter1>

        <AlertParameter2>$Data/EventData/DataItem/Property[@Name="EventNumber"]$</AlertParameter2>

      </AlertParameters>

      <Suppression>

        <SuppressionValue>$Data/EventData/DataItem/Property[@Name="EventNumber"]$</SuppressionValue>

        <SuppressionValue>$Data/EventData/DataItem/Property[@Name="ServiceTag"]$</SuppressionValue>

        <SuppressionValue>$Data/EventData/DataItem/Property[@Name="Severity"]$</SuppressionValue>

        <SuppressionValue>$Data/EventData/DataItem/Property[@Name="drsCA2MessageID"]$</SuppressionValue>

        <SuppressionValue>$Data/EventData/DataItem/Property[@Name="drsCA2Message"]$</SuppressionValue>

        <SuppressionValue>$Data/EventData/DataItem/Property[@Name="drsCA2FQDD"]$</SuppressionValue>

        <SuppressionValue>$Data/EventData/DataItem/Property[@Name="drsChassisServiceTag"]$</SuppressionValue>

      </Suppression>

      <Custom1>Alert Message ID = $Data/EventData/DataItem/Property[@Name="drsCA2MessageID"]$</Custom1>

      <Custom2>Alert Message = $Data/EventData/DataItem/Property[@Name="drsCA2Message"]$</Custom2>

      <Custom3>Alert FQDD = $Data/EventData/DataItem/Property[@Name="drsCA2FQDD"]$</Custom3>

      <Custom4>Alert Chassis Service Tag = $Data/EventData/DataItem/Property[@Name="drsChassisServiceTag"]$</Custom4>

      <Custom5>Alert Status = $Data/EventData/DataItem/Property[@Name="drsCA2AlertStatus"]$</Custom5>

      <Custom6>Alert Global Status = $Data/EventData/DataItem/Property[@Name="drsGlobalCurrStatus"]$</Custom6>

      <Custom7>Alert Chassis Location = $Data/EventData/DataItem/Property[@Name="drsProductChassisLocation"]$</Custom7>

      <Custom8>Alert Chassis Name = $Data/EventData/DataItem/Property[@Name="drsProductChassisName"]$</Custom8>

      <Custom9/>

      <Custom10/>

    </WriteAction>

  </WriteActions>

</Rule>