Back to Contents Page

Event Monitoring

Dell OpenManage™ Array Manager User's Guide Version 3.6

  Event Monitoring and Logging

  Viewing Event Listings

  Managing the Event Log

  Event Type or Severity Levels

  Event Source

  Variable Substitution in the Event Messages

  Event Messages

  SNMP Support

Array Manager's event management features let you monitor the health of storage resources such as controllers, channels, array disks, virtual disks, and volumes.


Event Monitoring and Logging

The Disk Management Service performs event monitoring and logging on Array Manager managed systems. By default, the Disk Management Service starts when the managed system starts up. If you stop the Disk Management Service, then event monitoring and logging stops.

Note A critical error will cause a pop-up "critical event" message to display even if the console is not running.
Note Array Manager does not log events regarding the data I/O path. These events are logged by the respective RAID drivers in the system event log.

Viewing Event Listings

Array Manager generates events that are added to the Windows application event log. You can view these events in the Array Manager Events tab or in the Microsoft Windows Event Viewer.

In the right pane of the Array Manager console, click the Events tab to display the events listings. All events that have been logged appear on this tab. You can also display the Events tab by clicking the View Events button on the Quick Access Window.

Every event consists of the following:

Note The Array Manager Event Log file cannot be viewed through a text editor.
Note If you are receiving an error message on your Windows system stating that the event log is full, you may need to clear the event log in order for incoming events to be displayed in the event log. See "Clearing Events" for information on clearing the Array Manager event log. For information on the Windows event log settings, see your Windows documentation.

Events Tab

Viewing Event Details

You can view specific information on each event listed on the Events tab by double-clicking the event to display the Event Details dialog box. The Event Details dialog box displays the same information as the Events tab, as well as additional information such as the computer on which the event was generated.

Viewing SNMP Traps

SNMP traps that are generated by Array Manager can be viewed in any standard SNMP-compatible enterprise management console. These traps are defined in the Array Manager management information base (MIB). These traps correspond to the events documented in the "Event Messages" section. For more information on the MIB and its structure, as well as a change history of the SNMP traps, see the PDF document titled Dell OpenManage Array Manager MIB Structure. The file name for this document is amMIBstructure.pdf. The default location for this file is in the Program Files\Dell\OpenManage\Array Manager\MIB directory.

For more information on configuring SNMP, see "SNMP Support."

Viewing Traps with HP OpenView Network Node Manager

To view trap events with strings inserted with HP OpenView Network Node Manager (NNM), perform the following steps:

  1. Load the Array Manager MIB (arymgr.mib) into the HP OpenView NNM. The arymgr.mib file is located in the Management Information Base (MIB) directory of your Array Manager installation directory.

  2. Select OK When prompted to Load a TRAP-TYPE/NOTIFICATION-TYPE macro. The system loads all of the trap definitions into HP OpenView.

For more information on loading MIBs into HP OpenView, see the HP OpenView documentation.


Managing the Event Log

This section describes how you can manage the Array Manager Event Log.

Note If you uninstall Array Manager or modify, repair, or remove installation components, you may notice that events generated before the uninstall, modify, repair, or remove no longer display an event description. This situation occurs when the component that generated the event is no longer installed on the system. If you wish to preserve the events and their descriptions, you should back up or export the event log before you uninstall Array Manager, or modify, repair, or remove installation components.

Backing Up and Restoring Events

You can choose to back up the Array Manager Event Log. Backing up saves the file to a specific, predefined location that is not user-selectable. This file cannot be viewed through a text editor.

To Back Up Events
  1. Right-click in the Events tab and select Backup Event Log from the context menu that appears.

  2. The Event Log is stored locally.

To Restore Events

You can restore the most recently saved Event Log.

  1. Right-click in the Events tab area and select Restore Event Log from the context menu that comes up.

  2. The saved events reappear in the Events tab view.

Clearing Events

You can clear all Array Manager events stored in the Event Log. This will remove all entries displayed under the Events tab. You can restore the entries by using the Restore Event Log option (if the Event Log was backed up). This restores the most recently backed-up Event Log entries.

To Clear Events
  1. Right-click in the Events tab area and select Clear All Events from the context menu that comes up.

  2. Click Yes to confirm. This clears the Event Log.

Exporting Events to a Text File

You can export the events in the Array Manager Event Log to a text file. You might do this for archival purposes before clearing the event log. Exporting to a text file also lets you search the events using a text editor.

To Export Events to a Text File
  1. Right-click in the Events tab area and select Export All Events to Text File from the context menu.

  2. Specify the text file name and location in the Save As dialog box and click Save.

Setting the Event Log Size

You can set the size of the Array Manager Event Log to a specific value, so that it will take only a certain amount of space on the disk. The default log size is 10 MB.

If the Event Log is full, every new system event generates a pop-up message indicating that the log file is full. The message also requests that you clear the log file.

You can clear the Event Log or you can continue to let events be written into it. This file will take log entries as long as there is writable space on the disk. Therefore, clearing the file is not required unless your disk space is extremely limited. You may wish to increase the size of your Event Log file to eliminate the error messages that are generated each time a log entry appears.

To Set the Event Log Size
  1. Right-click in the Events tab area and select Set Event Log Size from the context menu that comes up.

  2. The Set Event Log Size dialog box appears, showing the current size of the log.

  3. Enter a new size for the file and press OK. The Set Event Log Size dialog box closes automatically.


Event Type or Severity Levels

Each event message in the Array Manager event log has a severity level. The severity level is displayed in the Alert field of the event message. The severity level indicates the nature of the event.

The event severity levels are as follows:


Event Source

Each event message in the event log displays the source of the event. The following table shows the subsystem terminology (Array Manager console) and the event source names as displayed in the Array Manager event log and the Windows event log. The subsystem terminology does not apply to events that have fsys as their source.

Array Manager Console

Array Manager Event Log

Windows
Event Log

PERC Subsystem 1

PercPro

VxSvc_PercPro

PERC Subsystem 2

Perc2Pro

VxSvc_Perc2Pro

SCSI Subsystem

AspiPro

VxSvc_AspiPro

N/A

fsys

VxSvc_fsys

PV660F SubSystem

Mylex

VxSvc_Mylex


Variable Substitution in the Event Messages

When you view an event in the Array Manager event log, the event identifies the specific components such as the controller name or the virtual disk name to which the event applies. In an actual operating environment, a storage system can have many combinations of controllers and disks as well as user-defined names for virtual disks and other components. Because each environment is unique in its storage configuration and user-defined names, an accurate event message requires that Array Manager be able to insert the environment-specific names of storage components into an event message.

In order to provide environment-specific information in the event message, Array Manager uses variables for the event message text. When a controller or other component generates an event, Array Manager substitutes each variable with the controller name and other specifics. The modified event containing the environment-specific information is then displayed in the Array Manager event log.

This online help provides a definition of each event. When defining the event message, this online help indicates which portion of the message is constructed from a variable, and which components are substituted for the variable when Array Manager applies the environment-specific information. In the event definition, variables are represented by the % character (for example, %s, %1, %2, and so forth). The SNMP trap variables indicate how the % is substituted to provide environment-specific information.

Consider the following example event:

Description: Virtual Disk check consistency started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_CHECK_CONSISTENCY

Severity: Information

Source: PercPro (PERC Subsystem 1)

Text: %1, Virtual Disk (%2) consistency check started.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

In this example, the Text field indicates that two variables (%1, %2) are used to construct the event message displayed in the Array Manager event log. The SNMP Trap Variables field indicates that a controller name (controllerNameEv) and a virtual disk name (virtualDiskNameEv) substitute for the %1 and %2 variables. Therefore, if a PERC 3/Di controller number zero generated the event because a virtual disk number one with a user-defined name of HRdata has started a consistency check, then the resulting event message displayed in the event log is as follows:

PERC 3/Di Controller 0, Virtual Disk (HRdata 1) consistency check started.


Event Messages

The following sections describe events generated by the fibre channel RAID controllers in the PowerVault 660F storage system. The events are displayed in the Events tab of the Array Manager console or through Windows Event Viewer. These events can also be forwarded as SNMP traps to other applications.

SNMP traps are generated for the events listed in the following sections. These traps are included in the Array Manager management information base (MIB). For more information on the MIB and its structure, as well as a change history of the SNMP traps, see the PDF document titled Dell OpenManage Array Manager MIB Structure. The file name for this document is amMIBstructure.pdf. The default location for this file is in the Program Files\Dell\OpenManage\Array Manager\MIB directory. For more information on Array Manager's SNMP support, see "SNMP Support."

Select one of the following to view controller specific events:

Events Generated by the PERC 2/SC, 3/SC, 2/DC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4/Di, 4/IM, 4e/DC, 4e/Si, 4e/Di, CERC ATA100/4ch and the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s Controllers

The following sections describe events generated by the following controllers:

To locate an event, scroll through these sections to find the event number displayed on the Events tab of the Array Manager console or use the Search function in this online help file to search for the event message text.

500

Description: Array Disk Failed

Cause: A physical disk in the array failed. The failed disk may have been identified by the controller or channel. Performing a consistency check can also identify a failed disk.

Action: Replace the failed array disk. You can identify which disk has failed by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing the disk.

Name: PERC_ALERT_ARRAY_DISK_FAILURE or PERC2_ALERT_ARRAY_DISK_FAILURE or ASPI_ALERT_ARRAY_DISK_FAILURE

Severity: ErrorPercPro (PERC Subsystem 1)

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %s, %s failed. ),

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

Note In certain circumstances, this event is not generated when an array disk fails. See Array Disk State, Event Messages and Hot Spares on PERC Subsystem 1 Controllers for more information.

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

501

Description: Array Disk removed

Cause: A physical disk has been removed from the array. This event can also be caused by loose or defective cables or by problems with the enclosure.

Action: If a physical disk was removed from the array, either replace the disk or restore the original disk. You can identify which disk has been removed by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing or restoring the disk. If a disk has not been removed from the array, then check for problems with the cables. See the "Cables attached correctly" section for more information on checking the cables. Make sure that the enclosure is powered on. If the problem persists, check the enclosure documentation for further diagnostic information.

Name: PERC_ALERT_ARRAY_DISK_REMOVED or PERC2_ALERT_ARRAY_DISK_REMOVED or ASPI_ALERT_ARRAY_DISK_REMOVED

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %s, %s removed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

502

Description: Array Disk offline

Cause: A physical disk in the array is offline. A disk can be made offline during a Prepare to Remove operation or because a user manually put the disk offline.

Action: Perform a rescan. You can also select the offline disk and perform a Make Online operation.

Name: PERC_ALERT_ARRAY_DISK_OFFLINE or PERC2_ALERT_ARRAY_DISK_OFFLINE or ASPI_ALERT_ARRAY_DISK_OFFLINE

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %s, %s offline.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

503

Description: Array Disk degraded

Cause: A physical disk in the array is degraded. The degraded disk may have been identified by the controller or channel. Performing a consistency check can also identify a degraded disk.

Action: Replace the degraded array disk. You can identify which disk is degraded by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing the disk.

Name: PERC_ALERT_ARRAY_DISK_DEGRADED or PERC2_ALERT_ARRAY_DISK_DEGRADED or ASPI_ALERT_ARRAY_DISK_DEGRADED

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %s, %s degraded.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

504

Description: Array Disk inserted

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_NEW_DISK_INSERTED or PERC2_ALERT_NEW_DISK_INSERTED or ASPI_ALERT_NEW_DISK_INSERTED

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %s, %s inserted.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

505

Description: Virtual Disk created

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_VIRTUAL_DISK_CREATED or PERC2_ALERT_VIRTUAL_DISK_CREATED

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %s, virtual disk (%s) created.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

506

Description: Virtual Disk deleted

Cause: A virtual disk has been deleted. Performing a Reset Configuration may detect that a virtual disk has been deleted and generate this event.

Action: None.

Name: PERC_ALERT_VIRTUAL_DISK_DELETED or PERC2_ALERT_VIRTUAL_DISK_DELETED

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %s, virtual disk (%s) deleted.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

507

Description: Virtual Disk created

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_VIRTUAL_DISK_CONFIGURATION_CHANGED or PERC2_ALERT_VIRTUAL_DISK_CONFIGURATION_CHANGED

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) configuration changed from %3 to %4.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv, oldVDConfigEv, newVDConfigEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

508

Description: Virtual Disk failed

Cause: One or more physical disks included in the virtual disk have failed. If the virtual disk is non-redundant (does not use mirrored or parity data), then the failure of a single physical disk can cause the virtual disk to fail. If the virtual disk is redundant, then more physical disks have failed than can be rebuilt using mirrored or parity information.

Action: Create a new virtual disk and restore from a backup.

Name: PERC_ALERT_VIRTUAL_DISK_FAILED or PERC2_ALERT_VIRTUAL_DISK_FAILED

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) failed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

509

Description: Virtual Disk degraded

Cause 1: This event message occurs 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.

Action 1: Configure a hot spare for the virtual disk if one is not already configured. Rebuild the virtual disk. When using a PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, or CERC ATA100/4ch controller, rebuild the virtual disk by first configuring a hot spare for the disk, and then initiating a write operation to the disk. The write operation will initiate a rebuild of the disk.

Cause 2: A physical disk in the array has been removed.

Action 2: If a physical disk was removed from the array, either replace the disk or restore the original disk. You can identify which disk has been removed by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing the disk.

Name: PERC_ALERT_VIRTUAL_DISK_DEGRADED or PERC2_ALERT_VIRTUAL_DISK_DEGRADED

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) degraded.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

510

Description: Virtual disk is no longer redundant

Cause: A physical disk included in a redundant virtual disk has failed. Due to the failed drive or drives, the virtual disk is no longer maintaining redundant (mirrored or parity) data. The failure of an additional drive will result in lost data.

Action: Replace the failed drives and rebuild the virtual disk.

Name: PERC2_ALERT_VIRTUAL_DISK_FAILED_REDUNDANCY

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) failed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

520

Description: Virtual Disk check consistency started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_CHECK_CONSISTENCY or PERC2_ALERT_TASK_CHECK_CONSISTENCY

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) consistency check started.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

521

Description: Virtual Disk format started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_VD_FORMAT or PERC2_ALERT_TASK_VD_FORMAT

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) format started.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

522

Description: Array Disk format started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_DISK_FORMAT or PERC2_ALERT_TASK_DISK_FORMAT or ASPI_ALERT_TASK_DISK_FORMAT

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 format started.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

523

Description: Virtual Disk initialization started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_VD_INITIALIZE or PERC2_ALERT_TASK_VD_INITIALIZE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) initialization started.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

524

Description: Array Disk initialize started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_DISK_INITIALIZE or PERC2_ALERT_TASK_DISK_INITIALIZE or ASPI_ALERT_TASK_DISK_INITIALIZE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 initialization started.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

525

Description: Virtual Disk Reconfiguration started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_RECONFIGURATION or PERC2_ALERT_TASK_RECONFIGURATION

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) reconfiguration from %3 stripe size to %4 stripe size started.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv, oldVDConfigEv, newVDConfigEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

526

Description: Virtual Disk rebuild started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_VD_REBUILD or PERC2_ALERT_TASK_VD_REBUILD

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) rebuild started.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

527

Description: Array Disk rebuild started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_DISK_REBUILD or PERC2_ALERT_TASK_DISK_REBUILD or ASPI_ALERT_TASK_DISK_REBUILD

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 rebuild started.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

528

Description: Array Disk diagnostics started

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_TASK_DIAGNOSE or PERC2_ALERT_TASK_DIAGNOSE or ASPI_ALERT_TASK_DIAGNOSE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 diagnostics started.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

529

Description: Virtual Disk check consistency cancelled

Cause: The check consistency operation cancelled because a physical disk in the array has failed or because a user cancelled the check consistency operation.

Action: If the physical disk failed, then replace the physical disk. You can identify which disk failed by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing the disk. When performing a consistency check, be aware that the consistency check can take a long time. The time it takes depends on the size of the physical disk or the virtual disk.

Name: PERC_ALERT_CANCEL_CHECK_CONSISTENCY or PERC2_ALERT_CANCEL_CHECK_CONSISTENCY

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) consistency check cancelled.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

530

Description: Virtual Disk format cancelled

Cause: The format virtual disk operation cancelled because a physical disk included in the virtual disk has failed or because a user cancelled the format virtual disk operation.

Action: If a physical disk failed, then replace the physical disk. You can identify which disk has failed by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing the disk. Restart the format virtual disk operation.

Name: PERC_ALERT_CANCEL_VD_FORMAT or PERC2_ALERT_CANCEL_VD_FORMAT

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) format cancelled.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

531

Description: Array Disk format cancelled

Cause: The format array disk operation cancelled because a physical disk in the array has failed or because a user cancelled the format array disk operation.

Action: If a physical disk failed, then replace the physical disk. You can identify which disk has failed by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing the disk. Restart the format array disk operation.

Name: PERC_ALERT_CANCEL_DISK_FORMAT or PERC2_ALERT_CANCEL_DISK_FORMAT or ASPI_ALERT_CANCEL_DISK_FORMAT

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 format cancelled.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

532

Description: Virtual Disk initialization cancelled

Cause: The virtual disk initialization cancelled because a physical disk included in the virtual disk has failed or because a user cancelled the virtual disk initialization.

Action: If a physical disk failed, then replace the physical disk. You can identify which disk has failed by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing the disk. Restart the format array disk operation. Restart the virtual disk initialization.

Name: PERC_ALERT_CANCEL_VD_INITIALIZE or PERC2_ALERT_CANCEL_VD_INITIALIZE

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) initialization cancelled.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

533

Description: Array Disk initialize cancelled

Cause: The array disk initialization cancelled because a physical disk in the array has failed or because a user cancelled the array disk initialization.

Action: If a physical disk failed, then replace the physical disk. You can identify which disk has failed by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing the disk. Restart the array disk initialization.

Name: PERC_ALERT_CANCEL_DISK_INITIALIZE or PERC2_ALERT_CANCEL_DISK_INITIALIZE or ASPI_ALERT_CANCEL_DISK_INITIALIZE

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 initialization cancelled.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

534

Description: Virtual Disk Reconfiguration cancelled

Cause: A physical disk in the array has failed. A Transform Type, Add Member, or Reconfigure operation can identify that a disk has failed and generate this event.

Action: Replace the failed array disk. You can identify which disk has failed by locating the disk with a red "X" in the Array Manager console's tree view. Perform a rescan after replacing the disk. Restart the Transform Type, Add Member, or the Reconfigure operation.

Name: PERC_ALERT_CANCEL_RECONFIGURATION or PERC2_ALERT_CANCEL_RECONFIGURATION

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) reconfiguration cancelled.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

535

Description: Virtual Disk rebuild cancelled

Cause: A user has cancelled the rebuild operation.

Action: Restart the rebuild operation.

Name: PERC_ALERT_CANCEL_VD_REBUILD or PERC2_ALERT_CANCEL_VD_REBUILD

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) rebuild cancelled.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

536

Description: Array Disk rebuild cancelled

Cause: A user has cancelled the rebuild operation.

Action: Restart the rebuild operation.

Name: PERC_ALERT_CANCEL_DISK_REBUILD or PERC2_ALERT_CANCEL_DISK_REBUILD or ASPI_ALERT_CANCEL_DISK_REBUILD

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 rebuild cancelled.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

537

Description: Array Disk diagnostics cancelled

Cause: A user cancelled the array disk diagnostics operation.

Action: Restart the array disk diagnostics operation.

Name: PERC_ALERT_CANCEL_DIAGNOSE or PERC2_ALERT_CANCEL_DIAGNOSE or ASPI_ALERT_CANCEL_DIAGNOSE

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 diagnostics cancelled.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

538

Description: Virtual Disk check consistency failed

Cause: An array disk included in the virtual disk failed or there is an error in the parity information. A failed array disk can cause errors in parity information.

Action: Replace the failed array disk. You can identify which disk has failed by locating the disk with a red "X" in the Array Manager console's tree view. Rebuild the array disk. When finished, restart the check consistency operation.

Name: PERC_ALERT_FAIL_CHECK_CONSISTENCY or PERC2_ALERT_FAIL_CHECK_CONSISTENCY

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) consistency check failed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

539

Description: Virtual Disk format failed

Cause: An array disk included in the virtual disk failed.

Action: Replace the failed array disk. You can identify which disk has failed by locating the disk with a red "X" in the Array Manager console's tree view. Rebuild the array disk. When finished, restart the format operation.

Name: PERC_ALERT_FAIL_VD_FORMAT or PERC2_ALERT_FAIL_VD_FORMAT

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) format failed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

540

Description: Array Disk format failed

Cause: The array disk has failed.

Action: Replace the failed array disk. You can identify which disk has failed by locating the disk with a red "X" in the Array Manager console's tree view. If the array disk is part of a redundant array, then rebuild the array disk.

Name: PERC_ALERT_FAIL_DISK_FORMAT or PERC2_ALERT_FAIL_DISK_FORMAT or ASPI_ALERT_FAIL_DISK_FORMAT

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 format failed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

541

Description: Virtual Disk initialization Failed

Cause: An array disk included in the virtual disk has failed or a user has cancelled the initialization.

Action: If an array disk has failed, then replace the array disk.

Name: PERC_ALERT_FAIL_VD_INITIALIZE or PERC2_ALERT_FAIL_VD_INITIALIZE

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) initialization failed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

542

Description: Array Disk initialize failed

Cause: The array disk has failed or is corrupt.

Action: Replace the failed or corrupt disk. You can identify a disk that has failed by locating the disk with a red "X" in the Array Manager console's tree view. Restart the initialization.

Name: PERC_ALERT_FAIL_DISK_INITIALIZE or PERC2_ALERT_FAIL_DISK_INITIALIZE or ASPI_ALERT_FAIL_DISK_INITIALIZE

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 initialization failed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

543

Description: Virtual Disk Reconfiguration failed

Cause: An array disk included in the virtual disk has failed or is corrupt. A user may also have cancelled the reconfiguration.

Action: Replace the failed or corrupt disk. You can identify a disk that has failed by locating the disk with a red "X" in the Array Manager console's tree view. If the array disk is part of a redundant array, then rebuild the array disk. When finished, restart the reconfiguration.

Name: PERC_ALERT_FAIL_RECONFIGURATION or PERC2_ALERT_FAIL_RECONFIGURATION

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) reconfiguration failed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

544

Description: Virtual Disk rebuild failed

Cause: An array disk included in the virtual disk has failed or is corrupt. A user may also have cancelled the rebuild.

Action: Replace the failed or corrupt disk. You can identify a disk that has failed by locating the disk with a red "X" in the Array Manager console's tree view. Restart the virtual disk rebuild.

Name: PERC_ALERT_FAIL_VD_REBUILD or PERC2_ALERT_FAIL_VD_REBUILD

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) rebuild failed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

545

Description: Rebuild failed.

Cause: A rebuild was initiated and it failed to successfully complete.

Action: The array disk that was rebuilding should be replaced so that another rebuild can occur.

Name: PERC_ALERT_FAIL_DISK_REBUILD or PERC2_ALERT_FAIL_DISK_REBUILD

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, %2 rebuild failed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

546

Description: Array Disk diagnostics failed

Cause: The array disk disk has failed or is corrupt. A user may also have cancelled the diagnostics operation.

Action: Replace the failed or corrupt disk. You can identify a disk that has failed by locating the disk with a red "X" in the Array Manager console's tree view. If the disk is part of a redundant array, then rebuild the disk. Restart the diagnostics operation.

Name: PERC_ALERT_FAIL_DIAGNOSE or PERC2_ALERT_FAIL_DIAGNOSE or ASPI_ALERT_FAIL_DIAGNOSE

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 diagnostics failed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

547

Description: Virtual Disk check consistency completed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_COMPLETE_CHECK_CONSISTENCY or PERC2_ALERT_COMPLETE_CHECK_CONSISTENCY

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) consistency check completed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

548

Description: Virtual Disk format completed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_COMPLETE_VD_FORMAT or PERC2_ALERT_COMPLETE_VD_FORMAT

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) format completed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

549

Description: Array Disk format completed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_COMPLETE_DISK_FORMAT or PERC2_ALERT_COMPLETE_DISK_FORMAT or ASPI_ALERT_COMPLETE_DISK_FORMAT

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 format completed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

550

Description: Virtual Disk initialization completed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_COMPLETE_VD_INITIALIZE or PERC2_ALERT_COMPLETE_VD_INITIALIZE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) initialization completed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

551

Description: Array Disk initialize completed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_COMPLETE_DISK_INITIALIZE or PERC2_ALERT_COMPLETE_DISK_INITIALIZE or ASPI_ALERT_COMPLETE_DISK_INITIALIZE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 initialization completed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

552

Description: Virtual Disk Reconfiguration completed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_COMPLETE_RECONFIGURATION or PERC2_ALERT_COMPLETE_RECONFIGURATION

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) reconfiguration completed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

553

Description: Virtual Disk rebuild completed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_COMPLETE_VD_REBUILD or PERC2_ALERT_COMPLETE_VD_REBUILD

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) rebuild completed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

554

Description: Array Disk rebuild completed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_COMPLETE_DISK_REBUILD or PERC2_ALERT_COMPLETE_DISK_REBUILD ASPI_ALERT_COMPLETE_DISK_REBUILD

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 rebuild completed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

555

Description: Array Disk diagnostics completed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_COMPLETE_DIAGNOSE or PERC2_ALERT_COMPLETE_DIAGNOSE or ASPI_ALERT_COMPLETE_DIAGNOSE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 diagnostics completed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

570

Description: Predictive Failure reported. If this disk is part of a redundant virtual disk, select the `Offline' option and then replace the disk. Then configure a hot spare and it will start the rebuild automatically. If this disk is a hot spare, select the `Prepare to Remove' option and then replace the disk. If this disk is part of a non-redundant disk, you should back up your data immediately. If the disk fails, you will not be able to recover the data.

Cause: The array disk is predicted to fail. Many array disks contain Self Monitoring Analysis and Reporting Technology (S.M.A.R.T.). When enabled, SMART monitors the health of the disk based on indications such as the number of write operations that have been performed on the disk.

Action: Replace the array disk. Even though the disk may not have failed yet, it is strongly recommended that you replace the disk. Review the message text for additional information.

Name: PERC_ALERT_PREDICTIVE_FAILURE or ASPI_ALERT_PREDICTIVE_FAILURE

Severity: Warning

Source: PercPro (PERC Subsystem 1), AspiPro (SCSI Subsystem)

Text: %1, %2 reported predictive failure.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

571

Description: Sense Key = X, Sense Code = X, Sense Qualifier = X. Please refer to the Array Manager Documentation for details.

Cause: This event indicates that a SCSI device has reported a condition requiring user attention.

Action: Drives experiencing valid failures will normally report status information to the system logs. Refer to the tables below to aid in response to the reported conditions. Table A should be used as a guideline on when to replace a drive without the need for additional troubleshooting. Drives reporting the errors in Table A should be scheduled for replacement. Error codes reported in Table B may require drive reseating or additional troubleshooting.

Sense Key (SK)

Sense Code (ASC)

Qualifier (ASCQ)

Comments

02

04

00

Drive not ready. For ASC and ASCQ other than "04-00", additional trouble shooting should be performed.

03

XX

XX

Medium error. See notes.

04

XX

XX

Unrecovered hardware error.

09

XX

XX

Vendor-specific error.

XX

5D

XX

Predictive error reported. (SMART error.)

Table A: Sense data to justify replacing the SCSI HDD.

Note Message SK 03, ASC 11, ASCQ 00 indicates medium error was encountered. The RAID controllers will reassign the defective media block when encountered. Replacement should not be performed unless excessive defects are identified on a single drive.
Note Message SK 03, ASC 31 indicates the low level drive format has been corrupted. If a format via SCSI controller is not possible, drive replacement is recommended.

Sense Key (SK)

Sense Code (ASC)

Qualifier (ASCQ)

Comments

01

XX

XX

Recovered error.

02

XX

XX

Drive not ready. Replace only if 02-04-00.

05

XX

XX

Illegal request.

06

XX

XX

Unit Attention.

08

5D

XX

Aborted command.

Table B: Sense data to justify additional troubleshooting/reseating required.

Name: PERC_ALERT_SCSI_SENSE_DATA or ASPI_ALERT_SCSI_SENSE_DATA

Severity: Warning

Source: PercPro (PERC Subsystem 1),AspiPro (SCSI Subsystem)

Text: %1, %2 Sense Key = %3, Sense Code = %4, Sense Qualifier = %5.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. (When forwarded as an SNMP trap, this event only has two variables.) For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

572

Description: I/O paused. I/O will automatically resume after the allotted time.

Cause: I/O operations are paused due to a user action. The I/O operations will automatically resume after the indicated period of time.

Action: Wait for the I/O operations to resume automatically.

Name: PERC_ALERT_PAUSE_IO or ASPI_ALERT_PAUSE_IO

Severity: Warning

Source: PercPro (PERC Subsystem 1), AspiPro (SCSI Subsystem)

Text: %1, Channel %2 I/O paused, I/O will automatically resume after the allotted time (%3 seconds).

SNMP Trap Variables: controllerNameEv, channelNumberEv, timeEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

573

Description: I/O resumed

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_RESUME_IO or ASPI_ALERT_RESUME_IO

Severity: Information

Source: PercPro (PERC Subsystem 1), AspiPro (SCSI Subsystem)

Text: %1, Channel %2 I/O resumed.

SNMP Trap Variables: controllerNameEv, channelNumberEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

574

Description: Hot spare assigned

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_HOTSPARE_ASSIGN or PERC2_ALERT_HOTSPARE_ASSIGN

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, assigned %2 as Hot Spare.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

575

Description: Hot spare unassigned

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_HOTSPARE_UNASSIGN or PERC2_ALERT_HOTSPARE_UNASSIGN

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, unassigned %2 as Hot Spare.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

579

Description: Controller battery needs reconditioning.

Cause: The controller battery charge is low.

Action: Recondition the controller battery.

Name: PERC2_ALERT_BATTERY_NEEDS_RECONDITIONING

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, battery needs reconditioning.

SNMP Trap Variables: controllerNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

580

Description: Controller battery low.

Cause: The controller battery charge is low.

Action: Recondition the battery.

Name: PERC2_ALERT_BATTERY_NEEDS_RECONDITIONING

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, battery low.

SNMP Trap Variables: controllerNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

581

Description: Controller battery is reconditioning.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC2_ALERT_TASK_BATTERY_RECONDITION

Severity: Information

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, battery is reconditioning.

SNMP Trap Variables: controllerNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

582

Description: Controller battery recondition is completed.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC2_ALERT_COMPLETE_BATTERY_RECONDITION

Severity: Information

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, battery recondition completed.

SNMP Trap Variables: controllerNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

583

Description: Controller I/O paused.

Cause: The controller I/O operations are paused due to a user action. The controller I/O will automatically resume after the indicated period of time.

Action: None.

Name: PERC2_ALERT_PAUSE_IO

Severity: Warning.

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, I/O paused, I/O will automatically resume after the allotted time (%2 seconds).

SNMP Trap Variables: controllerNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

584

Description: Controller I/O resumed.

Cause: The controller I/O has resumed.

Action: None.

Name: PERC2_ALERT_RESUME_IO

Severity: Information.

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, I/O resumed.

SNMP Trap Variables: controllerNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

585

Description: Smart FPT exceeded.

Cause: A disk on the specified controller has received a SMART alert (predictive failure) indicating that the disk is likely to fail in the near future.

Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss.

Name: PERC2_ALERT_SMART_FPT_EXCEEDED

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, SMART:FPT_EXCEEDED on %2.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

586

Description: Smart configuration change.

Cause: A disk has received a SMART alert (predictive failure) after a configuration change. The disk is likely to fail in the near future.

Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss.

Name: PERC2_ALERT_SMART_CONFIG_CHANGE

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, SMART_CONFIG_CHANGE on %2.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

587

Description: Smart warning.

Cause: A disk has received a SMART alert (predictive failure). The disk is likely to fail in the near future.

Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss.

Name: PERC2_ALERT_SMART_WARNING

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, SMART_WARNING on %2.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

588

Description: Smart warning temperature.

Cause: A disk has reached an unacceptable temperature and received a SMART alert (predictive failure). The disk is likely to fail in the near future.

First Action: Determine why the array disk has reached an unacceptable temperature. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot or cold. Verify that the fans in the server or enclosure are working. If the array disk is in an enclosure, you should check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot. Refer to the enclosure documentation for more diagnostic information.

Second Action: If you cannot identify why the disk has reached an unacceptable temperature, then replace the disk. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss.

Name: PERC2_ALERT_SMART_WARNING_TEMPERATURE

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, SMART_WARNING_TEMPERATURE on %2.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

589

Description: Smart warning degraded.

Cause: A disk is degraded and has received a SMART alert (predictive failure). The disk is likely to fail in the near future.

Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk. Removing an array disk that is included in a non-redundant virtual disk will cause the virtual disk to fail and may cause data loss.

Name: PERC2_ALERT_SMART_WARNING_DEGRADED

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, SMART_WARNING_DEGRADED on %2.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

590

Description: Failure prediction threshold exceeded due to test - No action needed.

Cause: A disk has received a SMART alert (predictive failure) due to test conditions.

Action: None.

Name: PERC2_ALERT_SMART_FPT_EXCEEDED_TEST

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, On %2 the failure prediction threshold exceeded due to test-No action needed.

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

591

Description: Temperature exceeded the maximum warning threshold.

Cause: The array disk enclosure is too hot. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot.

Action: Check for factors that may cause overheating. For example, verify that the enclosure fan is working. You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot. Refer to the enclosure documentation for more diagnostic information.

Name: PERC_ALERT_TEMP_WARN_MAX or PERC2_ALERT_TEMP_WARN_MAX or ASPI_ALERT_TEMP_WARN_MAX

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 has exceded the maximum warning threshold.

SNMP Trap Variables: enclosureNameEv, unitNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

592

Description: Temperature dropped below the minimum warning threshold.

Cause: The array disk enclosure is too cool.

Action: Check whether the thermostat setting is too low and whether the room temperature is too cool.

Name: PERC_ALERT_TEMP_WARN_MIN or PERC2_ALERT_TEMP_WARN_MIN or ASPI_ALERT_TEMP_WARN_MIN

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 has exceded the minimum warning threshold.

SNMP Trap Variables: enclosureNameEv, unitNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

593

Description: Temperature exceeded the maximum error threshold.

Cause: The array disk enclosure is too hot. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot.

Action: Check for factors that may cause overheating. For example, verify that the enclosure fan is working. You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot. Refer to the enclosure documentation for more diagnostic information.

Name: PERC_ALERT_TEMP_ERR_MAX or PERC2_ALERT_TEMP_ERR_MAX or ASPI_ALERT_TEMP_ERR_MAX

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 has exceded the maximum error threshold.

SNMP Trap Variables: enclosureNameEv, unitNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

594

Description: Temperature dropped below the minimum error threshold.

Cause: The array disk enclosure is too cool.

Action: Check whether the thermostat setting is too low and whether the room temperature is too cool.

Name: PERC_ALERT_TEMP_ERR_MIN or PERC2_ALERT_TEMP_ERR_MIN or ASPI_ALERT_TEMP_ERR_MIN

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 has exceded the minimum error threshold.

SNMP Trap Variables: enclosureNameEv, unitNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

595

Description: Enclosure failed.

Cause: The enclosure, or any component within the enclosure, has failed.

Action: Identify and replace the failed component. To identify the failed component, expand the enclosure object in the Array Manager tree view to display the components (such as fans, disks, and so forth) contained in the enclosure. Any failed component will be identified with a red X. See the enclosure documentation for information on replacing enclosure components and for other diagnostic information.

Name: PERC_E_GENERIC_FAILED or PERC2_E_GENERIC_FAILED or ASPI_E_GENERIC_FAILED

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 Failed.

SNMP Trap Variables: enclosureNameEv, unitNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

596

Description: Enclosure is offline.

Cause: The enclosure, or any component within the enclosure, has been removed.

Action: Identify and replace the removed component. To identify the removed component, expand the enclosure object in the Array Manager tree view to display the components (such as fans, disks, and so forth) contained in the enclosure. Any removed component will be identified with a yellow exclamation point. See the enclosure documentation for information on replacing enclosure components and for other diagnostic information.

Name: PERC_E_GENERIC_OFFLINE or PERC2_E_GENERIC_OFFLINE or ASPI_E_GENERIC_OFFLINE

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 is Offline.

SNMP Trap Variables: enclosureNameEv, unitNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

597

Description: Enclosure is in an unknown state.

Cause: There is an error in the enclosure firmware.

Action: Upgrade the enclosure firmware.

Name: PERC_E_GENERIC_UNKNOWN or PERC2_E_GENERIC_UNKNOWN or ASPI_E_GENERIC_UNKNOWN

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 is in an unknown state.

SNMP Trap Variables: enclosureNameEv, unitNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

598

Description: Enclosure is in a warning state.

Cause: The array disk enclosure is either hotter or cooler than the desired temperature range.

Action: Check for factors that may cause overheating or excessive cooling. For example, verify that the enclosure fan is working. You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot or too cold. Refer to the enclosure documentation for more diagnostic information.

Name: PERC2_E_GENERIC_WARNING

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, %2 is in a warning state.

SNMP Trap Variables: enclosureNameEv, unitNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

600

Description: Enclosure is in a degraded state.

Cause: The enclosure, or any component within the enclosure, is in a degraded state.

Action: Identify and replace the degraded component. To identify the degraded component, expand the enclosure object in the Array Manager tree view to display the components (such as fans, disks, and so forth) contained in the enclosure. Any degraded component will be identified with a yellow exclamation point. See the enclosure documentation for information on replacing enclosure components and for other diagnostic information.

Name: PERC_E_GENERIC_DEGRADED or PERC2_E_GENERIC_DEGRADED or ASPI_E_GENERIC_DEGRADED

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 is degraded.

SNMP Trap Variables: controllerNameEv, enclosureUnitNamesEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

602

Description: Enclosure was shut down.

Cause: The array disk enclosure is either hotter or cooler than the maximum allowable temperature range.

Action: Check for factors that may cause overheating or excessive cooling. For example, verify that the enclosure fan is working. You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot or too cold. Refer to the enclosure documentation for more diagnostic information.

Name: PERC_ALERT_SHUTDOWN_ENCLOSURE or PERC2_ALERT_SHUTDOWN_ENCLOSURE or ASPI_ALERT_SHUTDOWN_ENCLOSURE

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 Shutting down.

SNMP Trap Variables: controllerNameEv, enclosureNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

603

Description: Server was shut down.

Cause: The array disk enclosure is either hotter or cooler than the maximum allowable temperature range.

Action: Check for factors that may cause overheating or excessive cooling. For example, verify that the enclosure fan is working. You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot or too cold. Refer to the enclosure documentation for more diagnostic information.

Name: PERC_ALERT_SHUTDOWN_SERVER or PERC2_ALERT_SHUTDOWN_SERVER or ASPI_ALERT_SHUTDOWN_SERVER

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 Shutting down the server.

SNMP Trap Variables: controllerNameEv, enclosureNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

604

Description: A consistency check on a virtual disk has been paused (suspended).

Cause: The check consistency operation on a virtual disk was paused by a user.

Action: To resume the check consistency operation, right-click the virtual disk in the Array Manager tree view and select Resume Check Consistency.

Name: PERC2_ALERT_PAUSED_CHECK_CONSISTENCY

Severity: Warning

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) consistency check paused.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

605

Description: A consistency check on a virtual disk has been resumed.

Cause: The check consistency operation on a virtual disk has resumed processing after being paused by a user.

Action: This event is provided for informational purposes.

Name: PERC2_ALERT_RESUMED_CHECK_CONSISTENCY

Severity: Information

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) consistency check resumed.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

606

Description: A virtual disk and its mirror have been split.

Cause: A user has caused a mirrored virtual disk to be split. When a virtual disk is mirrored, its data is copied to another virtual disk in order to maintain redundancy. After being split, both virtual disks retain a copy of the data, although because the mirror is no longer intact, updates to the data are no longer copied to the mirror.

Action: This event is provided for informational purposes.

Name: PERC2_ALERT_VIRTUAL_DISK_SPLIT_MIRROR

Severity: Information

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) split mirror.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

607

Description: A mirrored virtual disk has been unmirrored.

Cause: A user has caused a mirrored virtual disk to be unmirrored. When a virtual disk is mirrored, its data is copied to another virtual disk in order to maintain redundancy. After being unmirrored, the disk formerly used as the mirror returns to being an array disk and becomes available for inclusion in another virtual disk.

Action: This event is provided for informational purposes.

Name: PERC2_ALERT_VIRTUAL_DISK_UNMIRROR

Severity: Information

Source: Perc2Pro (PERC Subsystem 2)

Text: %1, Virtual Disk (%2) unmirrored.

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

608

Description: A virtual disk has been renamed.

Cause: A user has changed the name of a virtual disk.

Action: This event is provided for informational purposes.

Name: PERC_ALERT_RENAME_VD or PERC2_ALERT_RENAME_VD

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, %2 renamed to "%3"

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv, virtualDiskNameNewEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

609

Description: An object is in a ready state.

Cause: This event is generated when an object transitions to ready state.

Action: No action needed. This is an informational message.

Name: PERC_E_GENERIC_READY or PERC2_E_GENERIC_READY or ASPI_E_GENERIC_READY

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 is in a ready state.

SNMP Trap Variables: controllerNameEv, device1NameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

610

Description: Communication has timed out.

Cause: The controller cannot communicate with an attached device.

Action: Make sure that the device is powered on and that the cables are securely attached. See the "Cables attached correctly" section for more information on checking the cables. If communication is not restored, replace the SCSI cables.

Name: PERC_ALERT_COMM_TIMEOUT or PERC2_ALERT_COMM_TIMEOUT or ASPI_ALERT_COMM_TIMEOUT

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 SES communication timeout

SNMP Trap Variables: controllerNameEv, device1NameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

611

Description: Communication is lost.

Cause: The controller cannot communicate with an attached device.

Action: Make sure that the device is powered on and that the cables are securely attached. See the "Cables attached correctly" section for more information on checking the cables. If communication is not restored, replace the SCSI cables.

Name: PERC_ALERT_COMM_FAILURE or PERC2_ALERT_COMM_FAILURE or ASPI_ALERT_COMM_FAILURE

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 SES communication lost

SNMP Trap Variables: controllerNameEv, device1NameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

612

Description: Communication restored.

Cause: The controller has restored communication with an attached device.

Action: This event is provided for informational purposes.

Name: PERC_ALERT_COMM_FAILURE or PERC2_ALERT_COMM_FAILURE ASPI_ALERT_COMM_FAILURE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 SES communication restored

SNMP Trap Variables: controllerNameEv, device1NameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

668

Description: Array Manager has lost communication with this RAID controller and subsystem. A reboot is STRONGLY suggested at this point to avoid further problems. If this reboot does not resolve the problem, then this may be an indication of hardware failure.

Cause: Array Manager has lost communication with a device. There may be faulty hardware or loose or defective cables.

Action: Reboot the system. If the problem is not resolved, check for hardware failures. Array Manager identifies failed components with a red "X" in the tree view. Any failed component must be replaced. Make sure the cables are attached securely. See the "Cables attached correctly" section for more information on checking the cables. Refer to the hardware documentation for more diagnostics information.

Name: PERC_ALERT_MEGALIB_TIMEOUT

Severity: Error

Source: PercPro (PERC Subsystem 1)

Text: %1, Array Manager has lost communication with this RAID controller and subsystem. A reboot is STRONGLY suggested at this point to avoid further problems. If this reboot does not resolve the problem, then this may be an indication of hardware failure.

SNMP Trap Variables: controllerNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on event source(s), see "Event Source."

670

Description: A format unit operation was interrupted prior to completion. This will require a format unit operation to be run until completion for recovery of this disk.

Cause: A low-level disk format operation was interrupted. The disk is currently in an unusable state.

Action: Run a full low-level format on the disk. The format operation must run to completion.

Name: PERC_ALERT_SCSI_SENSE_FORMAT_FAIL

Severity: Warning

Source: PercPro (PERC Subsystem 1)

Text: %1, %2 Sense Key = %3, Sense Code = %4, Sense Qualifier = %5. A format unit operation was interrupted prior to completion. This will require a format unit operation to be run until completion for recovery of this disk.

SNMP Trap Variables: controllerNameEv, diskNameEv, senseKeyEv, senseCodeEv, senseQualifierEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

671

Description: If this disk is part of a non-redundant virtual disk, the data for this block cannot be recovered. The disk will require replacement and data restore. If this disk is part of a redundant virtual disk, the data in this block will be reallocated.

Cause: A sector of the disk is corrupted and data cannot be maintained on this portion of the disk.

Action: If the disk is not part of a redundant virtual disk, then replace the disk. Any data residing on the corrupt portion of the disk may be lost and you may need to restore from backup. If the disk is part of a redundant virtual disk, then any data residing on the corrupt portion of the disk will be reallocated elsewhere in the virtual disk.

Name: PERC_ALERT_SCSI_SENSE_SECTOR_REASSIGN

Severity: Warning

Source: PercPro (PERC Subsystem 1)

Text: %1, %2 Sense Key = %3, Sense Code = %4, Sense Qualifier = %5. If this disk is part of a non-redundant virtual disk, the data for this block cannot be recovered. The disk will require replacement and data restore. If this disk is part of a redundant virtual disk, the data in this block will be reallocated.

SNMP Trap Variables: controllerNameEv, diskNameEv, senseKeyEv, senseCodeEv, senseQualifierEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

672

Description: EMM firmware mismatch. This is an unsupported configuration. Please download the firmware to this enclosure again to correct this condition.

Cause: The firmware on the EMM modules is not the same version. It is required that both modules have the same version of the firmware.

Action: Download the same version of the firmware to both EMM modules. For more information on downloading firmware, see "Download Firmware."

Name: PERC_ALERT_EMM_FW_MISMATCH, or PERC2_ALERT_EMM_FW_MISMATCH or ASPI_ALERT_EMM_FW_MISMATCH

Severity: Warning

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 EMM firmware mismatch (%3 / %4). This is an unsupported configuration. Please download the firmware to this enclosure again to correct this condition.

SNMP Trap Variables: controllerNameEv, enclosureNameEv, eMMFWVersion0Ev, eMMFWVersion1Ev

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

673

Description: Conservative cache mode enabled.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_CONSERVE_CACHE_MODE_ENABLE or PERC2_ALERT_CONSERVE_CACHE_MODE_ENABLE or ASPI_ALERT_CONSERVE_CACHE_MODE_ENABLE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 conservative cache mode enabled.

Event Variables: Controller name, enclosure name

SNMP Trap Variables: controllerNameEv, enclosureNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

674

Description: Conservative cache mode disabled.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_CONSERVE_CACHE_MODE_DISABLE or PERC2_ALERT_CONSERVE_CACHE_MODE_DISABLE or ASPI_ALERT_CONSERVE_CACHE_MODE_DISABLE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 conservative cache mode disabled.

Event Variables: Controller name, enclosure name

SNMP Trap Variables: controllerNameEv, enclosureNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

675

Description: Firmware downloaded successfully.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_ENCLOSURE_FW_DOWNLOAD or PERC2_ALERT_ENCLOSURE_FW_DOWNLOAD or ASPI_ALERT_ENCLOSURE_FW_DOWNLOAD

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 firmware version %3 downloaded successfully.

Event Variables: Controller name, enclosure name, firmware version

SNMP Trap Variables: controllerNameEv, enclosureNameEv, eMMFWVersion0Ev

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

676

Description: Enclosure alarm enabled.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_ENCLOSURE_ALARM_ENABLE or PERC2_ALERT_ENCLOSURE_ALARM_ENABLE or ASPI_ALERT_ENCLOSURE_ALARM_ENABLE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 alarm enabled.

Event Variables: Controller name, enclosure name

SNMP Trap Variables: controllerNameEv, enclosureNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

677

Description: Enclosure alarm disabled.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_ENCLOSURE_ALARM_DISABLE or PERC2_ALERT_ENCLOSURE_ALARM_DISABLE or ASPI_ALERT_ENCLOSURE_ALARM_DISABLE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 alarm disabled.

Event Variables: Controller name, enclosure name

SNMP Trap Variables: controllerNameEv, enclosureNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

678

Description: Controller alarm enabled.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_CONTROLLER_ALARM_ENABLE or PERC2_ALERT_CONTROLLER_ALARM_ENABLE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, alarm enabled.

Event Variables: Controller name

SNMP Trap Variables: controllerNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

679

Description: Controller alarm disabled.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_CONTROLLER_ALARM_DISABLE or PERC2_ALERT_CONTROLLER_ALARM_DISABLE

Severity: Information

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1, alarm disabled.

Event Variables: Controller name

SNMP Trap Variables: controllerNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

680

Description: Controller rebuild rate has changed.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_CONTROLLER_REBUILD_RATE

Severity: Information

Source: PercPro (PERC Subsystem 1)

Text: %1, rebuild rate changed to %2.

Event Variables: Controller name, new rebuild rate

SNMP Trap Variables: controllerNameEv, rebuildRateEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

681

Description: Array disk forced online.

Cause: This event is provided for informational purposes.

Action: None.

Name: PERC_ALERT_ARRAY_DISK_FORCE_ONLINE

Severity: Information

Source: PercPro (PERC Subsystem 1)

Text: %1, %2 forced online.

Event Variables: Controller name, array disk name

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

682

Description: Array disk forced offline.

Cause: A user has manually forced a physical disk in the array offline.

Action: If the array disk is part of a non-redundant virtual disk, force the array disk online. Right-click the array disk in the Array Manager tree view and select the Online option. Be aware that if data was written to the non-redundant virtual disk while the array disk was offline, this data may be corrupt. If the array disk is part of a redundant virtual disk, then manually remove the array disk and reinsert it. Removing and reinserting the array disk causes the controller to automatically rebuild data from the redundant virtual disk. In this case, any data written to the redundant virtual disk while the array disk was offline will be restored. If the array disk is not displayed in the tree view after making it online, perform an I/O operation or a rescan.

Name: PERC_ALERT_ARRAY_DISK_FORCE_OFFLINE

Severity: Warning

Source: PercPro (PERC Subsystem 1)

Text: %1, %2 forced offline.

Event Variables: Controller name, array disk name

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

683

Description: Virtual Disk background initialization started.

Cause: Controllers in the PERC subystem 1 family support background initialization. This event indicates that background initialization has started for this virtual disk object.

Action: No action needed. This is an informational message.

Name: PERC_ALERT_TASK_BGI

Severity: Information

Source: PercPro (PERC Subsystem 1)

Text: %1, Virtual Disk (%2) background initialization started.

Event Variables:

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

684

Description: Virtual disk background initialization cancelled.

Cause: The background initialization that was previously started has been cancelled. This can happen manually—upon user request, or automatically by initiating certain commands, like Create Virtual Disk.

Action: The controller firmware automatically restarts the background initialization within approximately five minutes.

Name: PERC_ALERT_CANCEL_BGI

Severity: Warning

Source: PercPro (PERC Subsystem 1)

Text: %1, Virtual Disk (%2) background initialization cancelled.

Event Variables: Controller name, virtual disk name

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

685

Description: Virtual disk background initialization failed.

Cause: The background initialization that was previously started has abruptly ended unsuccessfully.

Action: The controller firmware automatically restarts the background initialization within approximately five minutes. If the background initialization fails repeatedly, check the event log to identify error conditions that may cause this failure. For example, an array disk with bad disk sectors may cause background initialization to fail. Refer to the controller documentation for more diagnostic information.

Name: PERC_ALERT_FAIL_BGI

Severity: Error

Source: PercPro (PERC Subsystem 1)

Text: %1, Virtual Disk (%2) background initialization failed.

Event Variables: Controller name, virtual disk name

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

686

Description: Virtual disk background initialization completed.

Cause: The background initialization that was previously started has successfully completed.

Action: No action needed. This is an informational message.

Name: PERC_ALERT_COMPLETE_BGI

Severity: Information

Source: PercPro (PERC Subsystem 1)

Text: %1, Virtual Disk (%2) background initialization completed.

Event Variables: Controller name, virtual disk name

SNMP Trap Variables: controllerNameEv, virtualDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

687

Description: An enclosure or one of its components is not installed

Cause: The system has attempted an operation on an enclosure or an enclosure component that is not installed. For example, the enclosure may not have a fan or temperature probe.

Action: This event is provided for informational purposes.

Name: PERC_E_GENERIC_NOT_INSTALLED or PERC2_E_GENERIC_NOT_INSTALLED or ASPI_E_GENERIC_NOT_INSTALLED

Severity: Information.

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2), AspiPro (SCSI Subsystem)

Text: %1, %2 is not installed.

Event Variables: Controller name, enclosure name and enclosure component name

SNMP Trap Variables: controllerNameEv, enclosureUnitNamesEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

688

Communication timeout.

Cause: Array Manager is unable to Perc2Pro (Perc2Pro (PERC Subsystem 2))communicate with an enclosure. The communication failure can be due to any faulty component that connects Array Manager to the enclosure. These components can include drivers, firmware, cables, or the enclosure.

Action: Examine all components that connect Array Manager to the enclosure. You may need to upgrade the firmware or drivers. Use the Array Manager Utilities to verify that the drivers and firmware are at a supported level. See "Array Manager Utilities" for more information. You can download drivers and firmware from http://support.dell.com. For information on checking the cables, see "Cables attached correctly." Make sure that the enclosure is powered on and functioning properly. You may need to check the enclosure documentation for further diagnostic information.

Name: PERC_ALERT_GENERIC_COMM_TIMEOUT

Severity: Warning

Source: PercPro (PERC Subsystem 1)

Text: %1, %2, %3 communication timeout. rc = %4, scsi_stat = %5

Event Variables: Controller name, enclosure name, type of communication problem, return code, SCSI status

SNMP Trap Variables: controllerNameEv, enclosureNameEv, commErrorTypeEv, returnCodeEv, scsiStatusEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

689

Communication lost.

Cause: Array Manager is unable to communicate with an enclosure. The communication failure can be due to any faulty component that connects Array Manager to the enclosure. These components can include drivers, firmware, cables, or the enclosure.

Action: Examine all components that connect Array Manager to the enclosure. You may need to upgrade the firmware or drivers. Use the Array Manager Utilities to verify that the drivers and firmware are at a supported level. See "Array Manager Utilities" for more information. You can download drivers and firmware from http://support.dell.com. For information on checking the cables, see "Cables attached correctly." Make sure that the enclosure is powered on and functioning properly. You may need to check the enclosure documentation for further diagnostic information.

Name: PERC_ALERT_GENERIC_COMM_LOST

Severity: Warning

Source: PercPro (PERC Subsystem 1)

Text: %1, %2, %3 communication lost. rc = %4, scsi_stat = %5

Event Variables: Controller name, enclosure name, type of communication problem, return code, SCSI status

SNMP Trap Variables: controllerNameEv, enclosureNameEv, commErrorTypeEv, returnCodeEv, scsiStatusEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

690

Rebuild completed with error(s).

Cause: See A Rebuild Completes with Errors on PERC Subsystem 1 Controllers for more information.

Action: See A Rebuild Completes with Errors on PERC Subsystem 1 Controllers for more information.

Name: PERC_ALERT_COMPLETE_W_ERROR_DISK_REBUILD

Severity: Error

Source: PercPro (PERC Subsystem 1)

Text: %1, %2 rebuild completed with error(s)

Event Variables: Controller name, array disk name

SNMP Trap Variables: controllerNameEv, arrayDiskNameEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

691

"BBR Error" or "Error with Sense," or "Medium Error"

Cause: See Receive Event 691 with "BBR Error" or "Error with Sense," or "Medium Error" Message for more information.

Action: See Receive Event 691 with "BBR Error" or "Error with Sense," or "Medium Error" Message for more information.

Name: PERC2_ALERT_ADAPTER_MISC_ERROR

Severity: Error

Source: PercPro (PERC Subsystem 1), Perc2Pro (PERC Subsystem 2)

Text: %1; %2 "BBR Error" or "Error with Sense" or "Medium Error" followed by message text provided by the controller followed by "Please see the Array Manager documentation for diagnostic procedure."

Event Variables: Controller name, additional messages

SNMP Trap Variables: controllerNameEv, additionalInfoEv

The event message text displayed in the event log is constructed from environment-specific information which is substituted for the variables shown in the Text field and the SNMP Trap Variables field. For an explanation of how a readable event message is constructed from these variables, see "Variable Substitution in the Event Messages."

For information on the event type or severity level, see "Event Type or Severity Levels."

For information on event source(s), see "Event Source."

Events Generated by the PowerVault 660F Storage System

The following sections describe events generated by the fibre channel RAID controller in the PowerVault 660F storage system.

To locate an event, scroll through these sections to find the event number displayed on the Events tab of the Array Manager console or use the Search function in this online help file to search for the event message text.

700

Description: A physical disk has been placed online.

Cause: One of the following has occurred: 1) A rebuild was completed 2) A physical disk was configured 3) a manual online was done.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_ONLINE

For information on event source(s), see "Event Source."

702

Description: Physical disk error found.

Cause: A bad sector was found on the physical disk. Mechanical failure on the physical disk. Host SCSI device detected illegal instruction. Target device generated unknown phase sequence.

Action: If the problem occurs frequently, replace the physical disk. If the problem does not improve, contact your service representative.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_HARD_ERROR

For more information on resolving this event, see "Event 702, Hard disk error found."

For information on event source(s), see "Event Source."

703

Description: Physical disk PFA condition found; this disk may fail soon.

Cause: Physical disk predicted some future failure. External RAID logical device may have become critical.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_PFA

For more information on resolving this event, see "Event 703, Hard disk PFA condition found."

For information on event source(s), see "Event Source."

704

Description: An automatic rebuild has started.

Cause: A physical disk failed and a spare was available. A physical disk failed and no spare was available. A spare was added.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_AUTO_REBUILD_START

For information on event source(s), see "Event Source."

705

Description: A rebuild has started.

Cause: Client started the rebuild on user's request. User replaced the failed device and the controller started a rebuild.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_MANUAL_REBUILD_START

For information on event source(s), see "Event Source."

706

Description: Rebuild is over.

Cause: Rebuild completed successfully.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_REBUILD_DONE

For information on event source(s), see "Event Source."

707

Description: Rebuild is cancelled.

Cause: User cancelled the rebuild.

Action: Restart the rebuild if required.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_REBUILD_CANCELED

For more information on resolving this event, see "Event 707, Rebuild is cancelled."

For information on event source(s), see "Event Source."

708

Description: Rebuild stopped with error.

Cause: Due to some unknown error on the controller, rebuild failed.

Action: Try rebuild again.

Address: ctl: 0 chn: 1 tgt: 2

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_REBUILD_ERROR

For more information on resolving this event, see "Event 708, Rebuild stopped with error."

For information on event source(s), see "Event Source."

709

Description: Rebuild stopped with error. New physical disk failed.

Cause: New physical disk failed. New physical disk may not be compatible with MDAC hardware/firmware.

Action: Replace the physical disk.

Address: ctl: 0 chn: 1 tgt: 2

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_REBUILD_NEWDEV_FAILED

For more information on resolving this event, see "Event 709, Rebuild stopped with error: New device failed."

For information on event source(s), see "Event Source."

710

Description: Rebuild stopped because logical drive failed.

Cause: At least one or more physical disks failed in the array. Bad data table overflow.

Action: It may not be possible to recover from this error. Contact your service representative.

Address: ctl: 0 chn: 1 tgt: 2

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_REBUILD_SYSDEV_FAILED

For more information on resolving this event, see "Event 710, Rebuild stopped because logical drive failed."

For information on event source(s), see "Event Source."

711

Description: A physical disk has failed.

Cause: A physical disk failed. A user action caused the physical disk to fail.

Action: Replace the physical disk.

Address: ctl: 0 chn: 1 tgt: 2

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_DEAD

For more information on resolving this event, see "Event 711, A hard disk has failed."

For information on event source(s), see "Event Source."

712

Description: A new physical disk has been found.

Cause: A new physical disk has been added to the enclosure. A PowerVault 660F controller was added to the enclosure. The PowerVault 660F array was rebooted.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_FOUND

For information on event source(s), see "Event Source."

713

Description: A physical disk has been removed.

Cause: User removed an unconfigured physical disk. An unconfigured physical disk failed. A controller was removed. A controller powered off.

Action: Replace the device if needed.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_GONE

For information on event source(s), see "Event Source."

718

Description: SCSI command timeout on physical device.

Cause: Physical device has been removed. Physical device failed. Command time out value is not correct.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_COMMAND_TIMEOUT

For more information on resolving this event, see "Event 718, SCSI command timeout on hard device."

For information on event source(s), see "Event Source."

719

Description: SCSI command abort on physical disk.

Cause: User may have requested to abort the command. Firmware may have aborted the command to recover from error. The physical disk may have aborted the command.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: CRITICAL

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_COMMAND_ABORT

For information on event source(s), see "Event Source."

720

Description: SCSI command retried on physical disk.

Cause: The command may have timed out. Internal bus reset may have occurred. Device reset may have occurred.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_COMMAND_RETRIED

For information on event source(s), see "Event Source."

721

Description: Parity error found.

Cause: A physical device did not generate proper parity. The controller failed or did not check parity properly. Another physical device interfered. Some outside environment affected the data on the cable (for example, a radio frequency signal). Terminator is not connected. Improper termination.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_PARITY_ERROR

For more information on resolving this event, see "Event 721, Parity error found."

For information on event source(s), see "Event Source."

722

Description: Soft error found.

Cause: An error was detected by physical device and data was recovered.

Action: Run consistency check. If problem occurs frequently, replace the physical device.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_SOFT_ERROR

For information on event source(s), see "Event Source."

723

Description: Misc error found.

Cause: A physical device reported some error which does not fit in any category. Read/Write command time out. Data over run. Physical device was busy when host attempted to send command.

Action: If problem occurs frequently, replace the physical device.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_MISC_ERROR

For information on event source(s), see "Event Source."

724

Description: SCSI device reset.

Cause: Firmware has done a reset to recover from an error. User has done a reset.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_RESET

For information on event source(s), see "Event Source."

725

Description: Active spare found.

Cause: Physical disk was configured. Manual active spare was done. Automatic active spare was done.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_ACTIVESPARE

For information on event source(s), see "Event Source."

726

Description: Warm spare found.

Cause: Physical disk was configured. Manual warm spare was done. Automatic warm spare was done.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_WARMSPARE

For information on event source(s), see "Event Source."

731

Description: Initialization canceled.

Cause: User cancelled the operation

Action: Physical disk must be initialized again or the physical disk cannot be used.

Address: ctl: 0 chn: 1 tgt: 2

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_INIT_CANCELED

For information on event source(s), see "Event Source."

749

Description: Physical disk status changed to offline.

Cause: A user has made an array disk offline or an array disk has failed.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_OFFLINE

For more information on resolving this event, see "Event 749, Physical device status changed to Offline."

For information on event source(s), see "Event Source."

750

Description: Physical disk status changed to hot spare.

Cause: A user has assigned an array disk as a hot spare.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_STANDBY

For information on event source(s), see "Event Source."

751

Description: Physical disk status changed to rebuild.

Cause: A hot spare has started to rebuild.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_REBUILD

For information on event source(s), see "Event Source."

752

Description: Physical device ID did not match.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_ID_MISMATCH

For information on event source(s), see "Event Source."

753

Description: Physical disk failed to start.

Cause: An array disk is not properly seated, properly inserted, or has been removed.

Action: Reseat or reinsert the array disk.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_FAILED_START

For more information on resolving this event, see "Event 753, Physical device failed to start."

For information on event source(s), see "Event Source."

754

Description: Physical disk negotiated different offset than config.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_OFFSET_SET

For information on event source(s), see "Event Source."

755

Description: Physical disk negotiated different bus width than config.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: MLXEV_PHYSDEV_SET_BUS_WIDTH

For information on event source(s), see "Event Source."

756

Description: Physical disk missing on startup.

Cause: Physical disk missing.

Action: Replace the physical disk or power on all enclosures.

Address: ctl: 0 chn: 1 tgt: 2

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_MISSING_ONSTARTUP

For more information on resolving this event, see "Event 756, Physical drive missing on startup."

For information on event source(s), see "Event Source."

758

Description: Physical disk is switching from one channel to the other channel.

Cause: Physical disk removed or channel failed.

Action: Check FC loop; replace physical disk if necessary.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_MOVING_TO_OTHER_CHN

For more information on resolving this event, see "Event 758, Physical drive is switching from one channel to another."

For information on event source(s), see "Event Source."

761

Description: Device loop ID conflict (soft addressing) detected.

Cause: Device loop ID conflict detected on disk channel resulting in soft addressing. Potential data corruption.

Action: Change index selector to enable hard addressing per enclosure manufacturer's specification.

Address: ctl: 0 chn: 1

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_FIBREDEV_LOOPID_SOFTADDR_OCCURRED

For information on event source(s), see "Event Source."

762

Description: Consistency check is started.

Cause: User started a consistency check. The controller started a consistency check.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_CHECK_START

For information on event source(s), see "Event Source."

763

Description: Consistency check is finished.

Cause: Consistency check completed successfully without detecting any errors.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_CHECK_DONE

For information on event source(s), see "Event Source."

764

Description: Consistency check is cancelled.

Cause: User cancelled the consistency check.

Action: Restart consistency check, if required.

Address: ctl: 0 logdrv: 1

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_CHECK_CANCELED

For information on event source(s), see "Event Source."

765

Description: Consistency check on logical drive error.

Cause: Inconsistent data was found. Bad sectors were found. A physical disk reliability problem.

Action: See bad block and request sense table for more information.

Address: ctl: 0 logdrv: 1

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_CHECK_ERROR

For more information on resolving this event, see "Event 765, Consistency check on logical drive error."

For information on event source(s), see "Event Source."

766

Description: Consistency check on logical drive failed.

Cause: A logical device became critical. A logical device failed.

Action: See request sense data for more information.

Address: ctl: 0 logdrv: 1

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_CHECK_SYSDEV_FAILED

For more information on resolving this event, see "Event 766, Consistency check on logical drive failed."

For information on event source(s), see "Event Source."

767

Description: Consistency check failed due to physical disk failure.

Cause: A physical disk failed.

Action: See request sense data for more information.

Address: ctl: 0 logdrv: 1

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_CHECK_PHYSDEV_FAILED

For more information on resolving this event, see "Event 767, Consistency check failed due to physical device failure."

For information on event source(s), see "Event Source."

768

Description: Logical drive has been made offline.

Cause: One/multiple physical disk(s) failed.

Action: It may not be possible to recover from this error. Contact your service representative.

Address: ctl: 0 logdrv: 1

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_OFFLINE

For more information on resolving this event, see "Event 768, Logical drive has been made offline."

For information on event source(s), see "Event Source."

769

Description: Logical drive is critical.

Cause: One physical device failed.

Action: Replace the physical device. Start the rebuild, if required.

Address: ctl: 0 logdrv: 1

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_CRITICAL

For more information on resolving this event, see "Event 769, Logical drive is Critical."

For information on event source(s), see "Event Source."

770

Description: Logical drive has been placed online.

Cause: Rebuild completed. User set the physical disk online. New configuration was added.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_ONLINE

For information on event source(s), see "Event Source."

778

Description: Logical drive initialization started.

Cause: User started the initialization. Any previous data is lost.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_INIT_STARTED

For information on event source(s), see "Event Source."

779

Description: Logical drive initialization done.

Cause: Initialize operation completed successfully.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_INIT_DONE

For information on event source(s), see "Event Source."

780

Description: Logical drive initialization canceled.

Cause: User cancelled the initialization.

Action: Restart initialization if required.

Address: ctl: 0 logdrv: 1

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_INIT_CANCELED

For information on event source(s), see "Event Source."

781

Description: Logical drive initialization failed.

Cause: One/multiple physical device(s) failed. Controller has been removed. Controller has been powered off.

Action: Refer to the device failure event.

Address: ctl: 0 logdrv: 1

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_INIT_FAILED

For more information on resolving this event, see "Event 781, Logical drive initialization failed."

For information on event source(s), see "Event Source."

784

Description: Expand capacity started.

Cause: User started either an Expand Capacity or Add Virtual Disk operation on a disk group.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_EXPANDCAPACITY_START

For information on event source(s), see "Event Source."

785

Description: Expand capacity completed.

Cause: An Expand Capacity or Add Virtual Disk operation on a disk group completed.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_EXPANDCAPACITY_DONE

For information on event source(s), see "Event Source."

786

Description: Expand capacity stopped with error.

Cause: Multiple physical disks failed during an Expand Capacity or Add Virtual Disk operation.

Action: It may not be possible to recover from this error. Contact your service representative.

Address: ctl: 0 logdrv: 1

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_EXPANDCAPACITY_ERROR

For more information on resolving this event, see "Event 786, Expand Capacity stopped with error."

For information on event source(s), see "Event Source."

787

Description: Bad Blocks found.

Cause: Bad sector was found on an array disk during a Consistency Check, Rebuild, Expand Capacity or Add Virtual Disk operation.

Action: Run a consistency check with the restore option. Restore data from a back up.

Address: ctl: 0 logdrv: 1

Severity: CRITICAL

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_BADBLOCK

For more information on resolving this event, see "Event 787, Bad blocks found."

For information on event source(s), see "Event Source."

788

Description: Logical drive size changed.

Cause: A new configuration has been added. Expand Capacity has added extra capacity to the virtual disk.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_SIZECHANGED

For information on event source(s), see "Event Source."

789

Description: Logical drive type changed.

Cause: A new configuration has been added. RAID migration completed. Expand Capacity or Add Virtual Disk was completed on RAID 1.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_TYPECHANGED

For information on event source(s), see "Event Source."

791

Description: Logical drive LUN mapping has been written to config.

Cause: A new virtual disk was created and made available to a server. This could occur either during the creation of virtual disk, or when the virtual disk is assigned to a server by way of Dell OpenManage Storage Consolidation.

Action: This is a normal operation when a virtual disk is created or assigned.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_WR_LUN_MAP

For information on event source(s), see "Event Source."

792

Description: Attempt to read data from block that is marked in Bad Data Table.

Cause: Attempt to read from block that is already marked bad in Bad Data Table. Potential data loss.

Action: Restore data from a back up.

Address: ctl: 0 logdrv: 1

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_DATAREAD_FROM_BLOCK_IN_BDT

For information on event source(s), see "Event Source."

793

Description: Data for Disk Block has been lost due to Logical Drive problem.

Cause: Data retained in RAID Cache for a Write-back Logical Drive cannot be stored to the physical medium beCause: of Logical Drive problem. The Logical Drive problem could be beCause: of multiple physical medium error or multiple physical devices offline or other reasons.

Action: Insure that all the physical disks related to the Logical Drive, disk channel, enclosure or cabling are functional and accessible. Repair or replace as necessary.

Address: ctl: 0 logdrv: 1

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_DATA_FOR_BLOCK_LOST

For information on event source(s), see "Event Source."

799

Description: Fan failure.

Cause: Cable connection is broken. Fan failure.

Action: Replace fan.

Address: ctl: 0 chn: 1 tgt: 2 Fan: 3

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_AEMI_FAN_FAILED

For information on event source(s), see "Event Source."

803

Description: Power supply failure.

Cause: Cable connection is broken. Power supply failure.

Action: Replace power supply.

Address: ctl: 0 chn: 1 tgt: 2 Power Supply: 3

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_AEMI_PWR_SUPPLY_FAILED

For information on event source(s), see "Event Source."

804

Refer to volume management event "10804."

805

Refer to volume management event "10805."

808

Description: Over temperature.

Cause: Room temperature is too high. Fan failure.

Action: Turn off the system and allow it to cool down. Adjust the room temperature.

Address: ctl: 0 chn: 1 tgt: 2 Heat Sensor: 3

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_AEMI_OVER_TEMPERATURE

For information on event source(s), see "Event Source."

818

Description: Fan failure.

Cause: Cable connection is broken. Fan failure.

Action: Replace fan.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLFAN_FAILED

For more information on resolving this event, see "Event 818 and 820, Fan failure or Fan is not present."

For information on event source(s), see "Event Source."

819

Description: Fan has been restored.

Cause: Faulty fan has been replaced. Cable is connected properly.

Action: None.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLFAN_OK

For information on event source(s), see "Event Source."

820

Description: Fan is not present.

Cause: Enclosure management connection is broken. Management hardware failure. Fan is not present.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLFAN_NOTPRESENT

For more information on resolving this event, see "Event 818 and 820, Fan failure or Fan is not present."

For information on event source(s), see "Event Source."

821

Description: Power supply failure.

Cause: Cable connection is broken. Power supply failure.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLPOWER_FAILED

For more information on resolving this event, see "Event 821 and 823, Power supply failure or Power supply is not present."

For information on event source(s), see "Event Source."

822

Description: Power supply has been restored.

Cause: Faulty power supply has been replaced.

Action: None.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

For information on event source(s), see "Event Source."

Name: DAM_MLXEV_ENCLPOWER_OK

823

Description: Power supply is not present.

Cause: Management connection is broken. Management hardware failure. Power supply is not present.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLPOWER_NOTPRESENT

For more information on resolving this event, see "Event 821 and 823, Power supply failure or Power supply is not present."

For information on event source(s), see "Event Source."

824

Description: Temperature is over safe limit. Failure imminent.

Cause: Room temperature is too high. Fan failure. Sensor failure.

Action: Turn off the system and allow it to cool down. Adjust the room temperature.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLHEAT_BAD

For information on event source(s), see "Event Source."

825

Description: Temperature is above working limit.

Cause: Room temperature is too high. Fan failure.

Action: Adjust the room temperature. Replace fan.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLHEAT_CRITICAL

For more information on resolving this event, see "Event 825, Temperature is above working limit."

For information on event source(s), see "Event Source."

826

Description: Normal temperature has been restored.

Cause: Faulty fan has been replaced. Room temperature was reduced.

Action: None.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLHEAT_OK

For information on event source(s), see "Event Source."

827

Description: Temperature sensor is not present.

Cause: Enclosure management connection is broken. Management hardware failure. Sensor is not present.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLHEAT_NOTPRESENT

For information on event source(s), see "Event Source."

828

Description: Enclosure access critical.

Cause: Problems were encountered. Internal communication to enclosure management module was not successful. Possible enclosure management hardware failure.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 enclosure: 1

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLACCESS_CRITICAL

For more information on resolving this event, see "Event 828, Enclosure access is Critical."

For information on event source(s), see "Event Source."

829

Description: Enclosure access has been restored.

Cause: Enclosure has been fixed or replaced.

Action: None.

Address: ctl: 0 enclosure: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLACCESS_OK

For information on event source(s), see "Event Source."

830

Description: Enclosure access is offline.

Cause: Problems were encountered with internal communication to the enclosure management module.

Action: Follow enclosure management vendor's diagnostics and repair procedures.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLACCESS_OFFLINE

For information on event source(s), see "Event Source."

831

Description: Enclosure soft addressing detected.

Cause: Enclosure has duplicate loop IDs (soft addressing). Potential data corruption.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 enclosure: 1

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLSES_SOFTADDR_OCCURRED

For more information on resolving this event, see "Event 831, Enclosure Soft Addressing detected."

For information on event source(s), see "Event Source."

832

Description: Enclosure services ready.

Cause: The enclosure is available for management. This event usually occurs after reboot or bootup of the PowerVault 660F.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLACCESS_READY

For information on event source(s), see "Event Source."

833

Description: Access to temperature sensor has been lost.

Cause: Module containing temperature sensor has been removed.

Action: None.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLHEAT_UNKNOWN

For information on event source(s), see "Event Source."

834

Description: Access to power supply status information has been lost.

Cause: Module establishing connectivity has been removed.

Action: None.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLPOWER_UNKNOWN

For information on event source(s), see "Event Source."

835

Description: Access to fan status information has been lost.

Cause: Module establishing connectivity has been removed.

Action: None.

Address: ctl: 0 enclosure: 1 unit: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_ENCLFAN_UNKNOWN

For information on event source(s), see "Event Source."

836

Description: Array management server software started successfully.

Cause: The server system (or array management utility server) started.

Action: If you did not expect a system reboot, investigate.

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSTEM_STARTED

For information on event source(s), see "Event Source."

837

Description: Write back error.

Cause: Data cache write failed.

Action: The data may have been lost. Restore the data from a backup.

Address: ctl: 0

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_WRITEBACK_ERROR

For information on event source(s), see "Event Source."

839

Description: Controller is dead. System is disconnecting from this controller.

Cause: Hardware failure.

Action: Contact your service representative.

Address: ctl: 0

Severity: CRITICAL

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_DEAD

For information on event source(s), see "Event Source."

840

Description: Controller has been reset.

Cause: Controller received a reset command.

Action: If this was an unexpected event, refer to the enclosure hardware documentation.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_RESET

For more information on resolving this event, see "Event 840, Controller has been reset."

For information on event source(s), see "Event Source."

841

Description: Controller is found.

Cause: New controller has been installed. Management software has restarted. System has rebooted.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_FOUND

For information on event source(s), see "Event Source."

842

Description: Controller is gone. System is disconnecting from this controller.

Cause: Controller has been powered off or has been reset. Controller has been removed from the system.

Action: None.

Address: ctl: 0

Severity: CRITICAL

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_GONE

For information on event source(s), see "Event Source."

843

Description: Battery present.

Cause: A battery module has been detected and is now operational.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_FOUND

For information on event source(s), see "Event Source."

844

Description: Battery power low.

Cause: Battery power is low. This normally happens during a battery calibration or recondition cycle. If this is not the reason, then investigate further.

Action: If this message occurs without a power failure or battery recondition/calibration, replace the battery.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_POWER_LOW

Note While the battery is low, the controller write cache will be disabled.

For more information on resolving this event, see "Event 844, BBU power low."

For information on event source(s), see "Event Source."

845

Description: Battery power OK.

Cause: Battery has enough power to enable the write data cache.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_POWER_OK

For information on event source(s), see "Event Source."

846

Description: Controller is gone. System is disconnecting from this controller.

Cause: The connection to the controller has been lost.

Action: None.

Address: ctl: 0

Severity: CRITICAL

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_POWER_OFF

For information on event source(s), see "Event Source."

847

Description: Controller powered on

Cause: Controller was removed from the system. Controller has been powered off.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_POWER_ON

For information on event source(s), see "Event Source."

848

Description: Controller is online.

Cause: New controller has been installed.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_ONLINE

For information on event source(s), see "Event Source."

849

Description: Controller is gone. System is disconnecting from this controller.

Cause: Controller was set online.

Action: None.

Address: ctl: 0

Severity: CRITICAL

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_OFFLINE

For information on event source(s), see "Event Source."

850

Description: Controller's partner is gone, controller is in failover mode now.

Cause: Controller was set offline.

Action: If you did not expect this, investigate.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_CRITICAL

For information on event source(s), see "Event Source."

851

Description: Battery reconditioning is started.

Cause: User started a battery reconditioning.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_RECOND_START

For information on event source(s), see "Event Source."

852

Description: Battery reconditioning is finished.

Cause: Battery reconditioning completed successfully.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_RECOND_DONE

For information on event source(s), see "Event Source."

853

Description: Battery reconditioning is canceled.

Cause: User cancelled the battery reconditioning.

Action: Restart the battery reconditioning, if required.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_RECOND_ABORT

For information on event source(s), see "Event Source."

855

Description: Controller firmware mismatch.

Cause: Replacement controller with downlevel firmware installed.

Action: Reload controller firmware.

Address: ctl: 0 chn: 1 tgt: 2

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_FIRMWARE_MISMATCH

For information on event source(s), see "Event Source."

856

Description: Battery removed.

Cause: Battery physically removed.

Action: Reinstall the battery.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_NORESPONSE

For information on event source(s), see "Event Source."

857

Description: WARM BOOT failed.

Cause: Memory error detected during WARM boot scan. Possible data loss.

Action: Restore data from a back up.

Address: ctl: 0

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_WARM_BOOT_ERROR

For more information on resolving this event, see "Event 857, Warm boot failed."

For information on event source(s), see "Event Source."

858

Description: Controller entered conservative cache mode.

Cause: User changed the setting. Controller preparing for shutdown. Battery low. RAID expansion in process. Over-temp condition. No redundant power. Power supply failure. UPS ac failed. UPS battery low.

Action: If this was an unexpected event, refer to the enclosure hardware documentation.

Address: ctl: 0 param: 0x0001

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_CONSERV_CACHE_MODE

Paramtype bitfield

Params

1: Name: _FAULT_MANAGEMENT: "Fault Management"

2: Name: _INPUT_SIG: "Hardware Input Signal"

4: Name: _SHUT_DOWN: "Controller Shut Down"

8: Name: _BBU_LOW: "BBU Battery Low"

16: Name: _MORE: "More Active"

32: Name: _OVER_TEMP: "Over Temperature"

64: Name: _NON_REDUN_POWER: "Non-redundant Power"

128: Name: _POWER_SUPPLY_FAIL: "Power Supply Failed"

For more information on resolving this event, see "Event 858, Controller entered Conservative Cache mode."

For information on event source(s), see "Event Source."

859

Description: Controller entered normal cache mode.

Cause: Controller operation occurred which could have changed the cache mode. This may or may not indicate a change in controller cache mode.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_NORMAL_CACHE_MODE

For information on event source(s), see "Event Source."

860

Description: Controller device start complete.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_DEV_START_CMPLT

For information on event source(s), see "Event Source."

861

Description: Soft ECC error corrected.

Cause: Faulty memory module.

Action: Replace memory module.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_SOFT_ECC_CORRECTED

For information on event source(s), see "Event Source."

862

Description: Hard ECC error corrected.

Cause: Faulty memory module.

Action: Replace memory module.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_HARD_ECC_CORRECTED

For information on event source(s), see "Event Source."

863

Description: Battery recondition suggested.

Cause: The battery in the BBU may need to be reconditioned to improve full capacity accuracy.

Action: Recondition the battery backup unit. See "Recondition" for more information.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_RECOND_NEEDED

For more information on resolving this event, see "Event 863, BBU Recondition suggested."

For information on event source(s), see "Event Source."

864

Description: Controller's partner has been removed.

Cause: The controller's partner has been disabled. This may occur when performing an expand capacity operation.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_REMOVED_PTNR

For information on event source(s), see "Event Source."

866

Description: Updated partner's status.

Cause: The controller's partner has changed its operational state.

Action: If the new state is unexpected, view earlier events to determine why it changed state.

Address: ctl: 0 param: 0x0001

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_UPDATE_PTNR_STATUS

Paramtype enum

Params

0x0000: Name: _UNKNOWN: "Unknown"

0x0100: Name: _BOOTING: "Booting"

0x0200: Name: _ACTIVE: "Active"

0x0300: Name: _FAILED: "Failed"

0x0400: Name: _REMOVED: "Removed"

0x0500: Name: _INSERTED: "Inserted"

For information on event source(s), see "Event Source."

867

Description: Relinquished partner.

Cause: A user has enabled the controller's partner.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_RELINQUISH_PTNR

For information on event source(s), see "Event Source."

868

Description: Inserted partner.

Cause: A user has inserted a partner controller into the enclosure.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_INSERTED_PTNR

For information on event source(s), see "Event Source."

869

Description: Dual controllers enabled.

Cause: The controller has entered duplex mode.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_DUAL_ENABLED

For information on event source(s), see "Event Source."

870

Description: Disabled partner.

Cause: The partner controller has been manually disabled by way of Array Manager. A failure occured causing one of the controllers to terminate. See param code for details on cause.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 param: 0x0001

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_KILL_PTNR

Paramtype enum

Params

0x0300: Name: _PING_TIMEOUT: "ping timeout"

0x0301: Name: _NEGOTIATE_GETCHUNK: "couldn't allocate chunk of memory"

0x0302: Name: _NEGOTIATE_CABLE: "SCSI communication failed or cables are wrong"

0x0303: Name: _NEGOTIATE_HOSTID: "host ID jumper mismatch"

0x0304: Name: _NEGOTIATE_JUMPERS: "SLIP/DIFFL/FBR jumper mismatch"

0x0305: Name: _NEGOTIATE_DISKCHNS: "number of disk channels present mismatch"

0x0306: Name: _NEGOTIATE_HOSTCHNS: "number of host channels present mismatch"

0x0307: Name: _NEGOTIATE_FWVER: "FW version mismatch"

0x0302: Name: _NEGOTIATE_FWTYPE: "FW header type mismatch"

0x0309: Name: _NEGOTIATE_MEMSIZE: "memory size mismatch"

0x030a: Name: _NEGOTIATE_MEMRD: "memory read of partner failed"

0x030b: Name: _NEGOTIATE_CACHEMEMSIZE: "Cache memory size mismatch"

0x030c: Name: _COMMAND: "received Kill partner command"

0x030d: Name: _DURING_FAILBACK: "failure handing over TID"

0x030e: Name: _ENTERING_NEXUS: "negotiation finished, but nexus not entered in time"

0x030f: Name: _UNKNOWN: "failed for unknown reason"

0x0310: Name: _WBSYNC_CHAN0: "write-back sync to partner - chan 0"

0x0311: Name: _WBSYNC_CHAN1: "write-back sync to partner - chan 1"

0x0312: Name: _WBSYNC_CHAN2: "write-back sync to partner - chan 2"

0x0313: Name: _WBSYNC_CHAN3: "write-back sync to partner - chan 3"

0x0314: Name: _WBSYNC_CHAN4: "write-back sync to partner - chan 4"

0x0315: Name: _WBSYNC_CHAN5: "write-back sync to partner - chan 5"

0x0316: Name: _NEGOTIATE_FWBUILD: "FW build mismatch"

0x0317: Name: _NEGOTIATE_CABLE_CROSS: "device cables are crossed"

0x0320: Name: _FAILED_HOTPULL: "partner removal detect while nexus active"

0x0321: Name: _ABSENT_AT_BOOT: "partner missing at negotiation time"

0x0322: Name: _POWERFAIL_DURING_FAIL: "BBU - we power failed before fail-over finished"

0x0323: Name: _POWERFAIL_DURING_RELINQ: "BBU - we power failed before relinquish finished"

0x0340: Name: _LOCK_TIMEOUT: "Lock Timeout"

0x0341: Name: _LOCK_SCSI_FAIL: "Lock SCSI Failed"

0x0342: Name: _FOR_SIMPLEX_MIGRATION: "kill partner so we can do migrate recovery"

0x0343: Name: _FAILED_CTOC: "General ctoc message failure"

For more information on resolving this event, see "Event 870, Killed partner."

For information on event source(s), see "Event Source."

871

Description: Dual controllers entered nexus.

Cause: The array was booted up. This event means that the two controllers in a PowerVault 660F are now in sync with each other.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_NEXUS

For information on event source(s), see "Event Source."

872

Description: Controller boot ROM image needs to be reloaded.

Cause: Wrong firmware image file downloaded. MAC address changed.

Action: Contact your service representative to determine the failure.

Address: ctl: 0

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BAD_BOOTROM_IMAGE

For more information on resolving this event, see "Event 872, Controller boot ROM image needs to be reloaded."

For information on event source(s), see "Event Source."

873

Description: Controller is using default non-unique world-wide Name.

Cause: MAC

Address: lost or not set.

Action: Contact your service representative to determine the failure.

Address: ctl: 0

Severity: CRITICAL

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BAD_MAC_ADDRESS

For more information on resolving this event, see "Event 873, Controller is using default nonunique world-wide name."

For information on event source(s), see "Event Source."

881

Description: Lost connection to server, or server is down.

Cause: Lost network connection to server. Server shutdown.

Action: None.

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSTEM_DEAD

For information on event source(s), see "Event Source."

882

Description: Automatic reboot count has changed.

Cause: Controller has rebooted. Automatic reboot has rearmed itself or was reconfigured.

Action: None.

Address: ctl: 0 param: 0x0001

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_AUTOBOOT_CHANGED

Paramtype value

For information on event source(s), see "Event Source."

883

Description: Channel Failed.

Cause: Cable disconnected.

Action: Plug in cable.

Address: ctl: 0 chn: 1

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CHANNEL_FAILED

For information on event source(s), see "Event Source."

884

Description: Channel Online.

Cause: Cable reconnected.

Action: None.

Address: ctl: 0 chn: 1

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CHANNEL_OK

For information on event source(s), see "Event Source."

887

Description: Back end fibre dead.

Cause: Lost access to data on Fibre Channel.

Action: Refer to the enclosure hardware documentation.

Address: ctl: 0 chn: 1

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CHANNEL_FIBER_DEAD

For more information on resolving this event, see "Event 887, Back End Fibre Dead."

For information on event source(s), see "Event Source."

888

Description: Back end fibre alive.

Cause: Regained access to data on internal fibre channel.

Action: None.

Address: ctl: 0 chn: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CHANNEL_FIBER_ALIVE

For information on event source(s), see "Event Source."

889

Description: Event log empty.

Cause: Tried to read past last entry of controller's event log.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_LOG_EMPTY

For information on event source(s), see "Event Source."

890

Description: Event log entries lost.

Cause: Tried to read an entry that does not exist in the event log from the controller.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_LOG_OUT_SYNC

For information on event source(s), see "Event Source."

891

Description: Request Sense

Cause: A physical disk has generated an error.

Action: Interpret the Key/ASC/ASCQ and take appropriate action.

Address: ctl: 0 chn: 1 tgt: 2

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_LOG_REQUEST_SENSE

For information on event source(s), see "Event Source."

892

Description: Set real time clock.

Cause: Real time clock was set.

Action: None.

Address: ctl: 0 chn: 1

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_LOG_SET_RTC

For information on event source(s), see "Event Source."

893

Description: New configuration received.

Cause: The configuration on the controller changed. Deleting or creating a virtual disk can cause this event to be logged.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CFG_NEW

For information on event source(s), see "Event Source."

894

Description: Configuration cleared.

Cause: The controller configuration was cleared. All virtual disks and hot spares were removed. This is logged when the clear configuration operation is done.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CFG_CLEAR

For information on event source(s), see "Event Source."

895

Description: Configuration invalid.

Cause: The controller found an invalid configuration.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CFG_INVALID

For information on event source(s), see "Event Source."

896

Description: Configuration on disk access error.

Cause: The controller could not read the configuration off of the disk.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CFG_COD_ACCESS_ERROR

For information on event source(s), see "Event Source."

897

Description: Configuration on disk converted.

Cause: The controller converted a down level configuration on disk.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CFG_COD_CONVERTED

For information on event source(s), see "Event Source."

898

Description: Configuration on disk import failed.

Cause: The controller could not import the configuration.

Action: None.

Address: ctl: 0

Severity: WARNING

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CFG_COD_IMPORT_FAILED

For information on event source(s), see "Event Source."

900

Description: A debug dump exists on this system.

Cause: The partner controller aborted and created debug dump information.

Action: Contact field support for assistance in retrieving the data.

Address: ctl: 0 Abort Code: 0x0102

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_DEBUG_DUMP_GENERATED_PARTNER

For information on event source(s), see "Event Source."

905

Description: Logical drive background initialization started.

Cause: User may have started background initialization. Firmware may have automatically started background initialization.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_BG_INIT_STARTED

For information on event source(s), see "Event Source."

906

Description: Logical drive background initialization stopped.

Cause: User may have stopped background initialization. Firmware may have automatically stopped background initialization.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_BG_INIT_STOPPED

For information on event source(s), see "Event Source."

907

Description: Logical drive background initialization paused.

Cause: Background initialization paused due to higher priority operation.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_BG_INIT_PAUSED

For information on event source(s), see "Event Source."

908

Description: Logical drive background initialization restarted.

Cause: Background initialization restarted after being paused.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_BG_INIT_RESTARTED

For information on event source(s), see "Event Source."

909

Description: Logical drive background initialization failed.

Cause: Background initialization failed.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_BG_INIT_FAILED

For information on event source(s), see "Event Source."

910

Description: Logical drive background initialization completed.

Cause: Background initialization completed successfully.

Action: None.

Address: ctl: 0 logdrv: 1

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SYSDEV_BG_INIT_COMPLETED

For information on event source(s), see "Event Source."

911

Description: Battery calibration cycle started.

Cause: New battery detected.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_CALIBRATE_START

For information on event source(s), see "Event Source."

912

Description: Battery calibration cycle finished.

Cause: Battery calibration completed successfully.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_CALIBRATE_DONE

For information on event source(s), see "Event Source."

913

Description: Battery calibration cycle was cancelled.

Cause: User cancelled the battery calibration cycle.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_CALIBRATE_ABORT

For information on event source(s), see "Event Source."

914

Description: Battery is not present.

Cause: The battery electronics are present but a battery was not detected.

Action: Install or connect the battery.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_BBU_NO_BATTERY

For information on event source(s), see "Event Source."

919

Description: Dual-active automatic flash of replacement controller.

Cause: Replacement controller is being flashed with survivor's firmware.

Action: None.

Address: ctl: 0

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_AUTOMATIC_FLASH_STARTED

For information on event source(s), see "Event Source."

920

Description: Dual-active negotiation failed jumpers.

Cause: Jumper settings do not match.

Action: Replace, adjust or add components so that the controllers have the same jumper settings.

Address: ctl: 0

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_NEGOTIATION_FAILED_JUMPERS

For information on event source(s), see "Event Source."

921

Description: Dual-active negotiation failed IDs.

Cause: Controller IDs not unique. Both controllers have same ID.

Action: Replace, adjust or add components so that the controllers have the correct IDs.

Address: ctl: 0

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_NEGOTIATION_SAME_ID

For information on event source(s), see "Event Source."

922

Description: Dual-active negotiation failed board types.

Cause: Board types differ. Both controllers must be of the same type.

Action: Replace appropriate controller so that the board types are the same.

Address: ctl: 0

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_NEGOTIATION_BOARD_TYPE

For information on event source(s), see "Event Source."

923

Description: Dual-active negotiation failed disk channels.

Cause: Number of disk channels differ. Both controllers must have same number of disk channels.

Action: Replace, adjust or add components so that the controllers have the same number of disk channels.

Address: ctl: 0

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_NEGOTIATION_DISK_CHANNELS

For information on event source(s), see "Event Source."

924

Description: Dual-active negotiation failed host ports.

Cause: Host ports differ. Both controllers must have same number of host ports.

Action: Replace, adjust or add components so that the controllers have the same number of host ports.

Address: ctl: 0

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_NEGOTIATION_HOST_CHANNELS

For information on event source(s), see "Event Source."

925

Description: Dual-active negotiation failed memory size.

Cause: Memory sizes differ. Both controllers must have same control store size.

Action: Replace, adjust or add components so that the controllers have the same control store size.

Address: ctl: 0

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_NEGOTIATION_MEMORY_SIZE

For information on event source(s), see "Event Source."

926

Description: Dual-active negotiation failed cache memory size.

Cause: Cache memory sizes differ. Both controllers must have same cache memory size.

Action: Replace, adjust or add components so that the controllers have the same cache memory size.

Address: ctl: 0

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_CTLDEV_NEGOTIATION_CACHE_SIZE

For information on event source(s), see "Event Source."

927

Description: Hot spare replaced with a smaller capacity physical disk.

Cause: The new hot spare may have a smaller physical capacity than the physical disk it replaced. The controller's coercion setting may have reduced the configurable size of the new hot spare.

Action: None.

Address: ctl: 0 chn: 1 tgt: 2

Severity: INFORMATION

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_PHYSDEV_HOT_SPARE_SMALLER

For information on event source(s), see "Event Source."

980

Description: Controller failed, SES not operational. Try a rescan....

Cause: When Array Manager scanned the fibre channel loop/fabic, it found a PowerVault 660F array that wasn't fully initialized (may be still booting up). Therefore, Array Manager wasn't able to obtain configuration data from the array. This array will not be included in the Array Manager console for management.

Action: Wait a few minutes, and then do a Rescan from the PowerVault 660F folder object. If the array was booting up when the error occurred, it may be fully initialized during this rescan.

Address: None

Severity: ERROR

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SES_ERR

For information on event source(s), see "Event Source."

981

Description: Unable to get enclosure status. Doing a Mylex (PV660F SubSystem) rescan may resolve this problem.

Cause: When Array Manager scanned the fibre channel loop/fabic, it found a PowerVault 660F array that wasn't fully initialized (may be still booting up). Therefore, Array Manager wasn't able to obtain configuration data from the array. This array will not be included in the Array Manager console for management.

Action: Wait a few minutes, and then do a Rescan from the PowerVault 660F folder object. If the array was booting up when the error occurred, it may be fully initialized during this rescan.

Address: ctl: 0

Severity: SERIOUS

Source: Mylex (PV660F SubSystem)

Name: DAM_MLXEV_SES_ERR

For information on event source(s), see "Event Source."

Volume Management Events

The following sections describe events related to volume management.

To locate an event, scroll through these sections to find the event number displayed on the Events tab of the Array Manager console or use the Search function in this online help file to search for the event message text.

10804

Description: Free disk space has reached warning threshold on volume C:

Cause: The amount of used disk space has reached the warning threshold set in the Windows registry. Array Manager generates this event when capacity monitoring is turned on and the used disk space reaches a threshold.

Action: Either remove non-critical files to free up disk space or extend the volume to provide additional space.

Severity: Information

Source: fsys

Event and SNMP Trap Number: This event is listed as event 804 in the Array Manager event log. The SNMP trap number is 10804.

For more information on volume capacity monitoring, see "Volume Capacity Monitoring."

For information on event source(s), see "Event Source."

10805

Description: Free disk space has reached error threshold on volume C:

Cause: The amount of used disk space has reached the error threshold set in the Windows registry. Array Manager generates this event when capacity monitoring is turned on and the used disk space reaches a threshold.

Action: Either remove non-critical files to free up disk space or extend the volume to provide additional space.

Severity: Information

Source: fsys

Event and SNMP Trap Number: This event is listed as event 805 in the Array Manager event log. The SNMP trap number is 10805.

For more information on volume capacity monitoring, see "Volume Capacity Monitoring."

For information on event source(s), see "Event Source."


SNMP Support

By default, Array Manager installs SNMP trap forwarding support. For this support to function, you should have SNMP installed on the managed system prior to installing Array Manager. (For a full description of Array Manager installation requirements, see "Installation Requirements." )

The events displayed in the Array Manager event log are forwarded to the Windows application event log. If you have SNMP installed on the managed system (and the SNMP service is running), the Array Manager events in the Windows application event log will be forwarded as SNMP traps. In order for these traps to be viewable, however, a target system or application must be configured to receive these traps. SNMP traps that are generated by Array Manager can be viewed in any standard SNMP-compatible enterprise management console.

Microsoft Windows and NetWare SNMP services must be configured to forward the SNMP traps to the target system or application. When forwarding to an application, the application should also be configured to receive the SNMP traps. The IT Assistant application is already configured to receive the SNMP traps generated by Array Manager.

Refer to your Windows or NetWare operating system documentation for information on configuring the operating system to forward SNMP traps. This information may be located under such topics as "setting up SNMP" or "SNMP traps." When configuring SNMP for Windows, be sure that the SNMP traps are forwarded to the correct server. For information on configuring an application to receive SNMP traps, refer to the documentation for that application.

The Array Manager management information base (MIB) defines the SNMP traps that Array Manager generates. These traps correspond to the events documented in the "Event Messages" section. The MIB is located in the Array Manager installation directory. The default location for the MIB is Program Files\Dell\OpenManage\Array Manager\MIB. For more information on the MIB and its structure, as well as a change history of the SNMP traps, see the PDF document titled Dell OpenManage Array Manager MIB Structure. The file name for this document is amMIBstructure.pdf. The default location for this file is in the Program Files\Dell\OpenManage\Array Manager\MIB directory.

Note Array Manager supports trap forwarding on both 32-bit and 64-bit operating systems.


Back to Contents Page