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 starts when an Array Manager managed node starts up. If you stop the Manage Node service in Microsoft Windows NT/2000 or the Array Manager Service on NetWare®, then event monitoring and logging stops. When Array Manager captures a storage event, it does the following.
Updates the status of the storage object that generated the event.
Propagates the storage object's status to all the related higher objects in the storage hierarchy. For example, if the tree view is collapsed, the computer object will show the alert icon.
Logs an event into the Array Manager log and Microsoft® Windows NT® or Windows® 2000 application event log.
Sends an SNMP trap if the operating system's SNMP service is installed and enabled.
Changes the color of the Array Manager taskbar icon (displayed in the upper-left corner of the Array Manager window) to red. The taskbar icon remains red until the alerting event displayed on the Events tab is opened.
Note A critical error will cause a pop-up "critical event" message to display even if the
console is not running.
Array Manager generates events that are added to the Microsoft Windows NT/2000 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 in this section.
Every event consists of the following:
Alert — Shows the severity of alert.
Date — Date when Array Manager logged the event.
Time — Time when Array Manager logged the event.
Source — Array Manager component that logged the event.
Event — Displays the event ID or number. You can use this number when locating the event descriptions in the "Event Messages" section.
Description — A brief description of the event.
Note The Array Manager Event Log file cannot be viewed through a text editor.
You can view specific information on each event by double-clicking on it to display the Event Details dialog box. This shows, in addition to the information displayed in the Events tab, the Event ID, Type, Category, User, Source, Date, Time, and Computer name. The dialog box provides an easier way to read the description of the event.
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, see the document titled Dell OpenManage Array Manager 3.1 MIB Structure. This document is in the amMIBStructure.html file. The default location for this file is Program Files\Dell\OpenManage\Array Manager\MIB\amMIBStructure.html.
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.
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.
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.
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.
Each event message in the Array Manager event log severity level. The severity level is displayed in the Type field of the event message. The severity level indicates the nature of the event.
The event severity levels are as follows:
Information — The event is provided for informational purposes and does not indicate an error condition. An Information event indicates the normal start or stop of an operation. For example, an information event may indicate that an operation such as a consistency check has started or come to completion.
Warning — A Warning event indicates a potential problem, but does not necessarily mean that the system has currently lost data or is nonfunctional. For example, a Warning event may indicate that a component (such as a temperature probe in an enclosure) has crossed a warning threshold.
Error — An Error event indicates a serious problem such as a loss of data or a loss of function. For example, an Error event may indicate that an array disk has failed.
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.
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.
The following sections describe events generated by the PowerVault 660F controller. The events are displayed in the Events tab of the Array Manager console or through Windows NT Event Viewer or Windows 2000 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, see the document titled Dell OpenManage Array Manager 3.1 MIB Structure. This document is in the amMIBStructure.html file. The default location for this file is Program Files\Dell\OpenManage\Array Manager\MIB\amMIBStructure.html.
Select one of the following to view controller specific events:
The following sections describe events generated by the following controllers:
PERC 2/SC
PERC 3/SC
PERC 2/DC
PERC 3/DCL
PERC 3/DC
PERC 3/QC
PERC 2
PERC 2/Si
PERC 3/Si
PERC 3/Di
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.
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
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."
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
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."
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
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."
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
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."
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."
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."
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."
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."
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
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."
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 an PERC 2/SC, 3/SC, 2/DC, 3/DCL, 3/DC, or 3/QC 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
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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
Text: %1, Virtual Disk (%2) consistency check cancelled.
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."
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
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."
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
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."
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
Text: %1, Virtual Disk (%2) initialization cancelled.
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."
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
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."
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
Text: %1, Virtual Disk (%2) reconfiguration cancelled.
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."
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."
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."
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."
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
Text: %1, Virtual Disk (%2) consistency check failed.
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."
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
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."
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
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."
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."
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
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."
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
Text: %1, Virtual Disk (%2) reconfiguration failed.
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."
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. Rebuild the virtual disk rebuild.
Name: PERC_ALERT_FAIL_VD_REBUILD or PERC2_ALERT_FAIL_VD_REBUILD
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."
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
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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.
Name: PERC_ALERT_PREDICTIVE_FAILURE or PERC2_ALERT_PREDICTIVE_FAILURE
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."
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."
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 PERC2_ALERT_PAUSE_IO
Severity: Warning
Text: %1, Channel %2 I/O paused, I/O will automatically resume after the allotted time (%3 seconds).
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."
Cause: This event is provided for informational purposes.
Action: None.
Name: PERC_ALERT_RESUME_IO or PERC2_ALERT_RESUME_IO
Severity: Information
Text: %1, Channel %2 I/O resumed.
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."
Cause: This event is provided for informational purposes.
Action: None.
Name: PERC_ALERT_HOTSPARE_ASSIGN or PERC2_ALERT_HOTSPARE_ASSIGN
Severity: Information
Text: %1, assigned %2 as Hot Spare.
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."
Cause: This event is provided for informational purposes.
Action: None.
Name: PERC_ALERT_HOTSPARE_UNASSIGN or PERC2_ALERT_HOTSPARE_UNASSIGN
Severity: Information
Text: %1, unassigned %2 as Hot Spare.
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."
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
Severity: Warning
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."
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
Severity: Warning
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."
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
Severity: Error
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."
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
Severity: Error
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."
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
Severity: Error
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."
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
Severity: Warning
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."
Cause: There is an error in the enclosure firmware.
Action: Upgrade the enclosure firmware.
Name: PERC_E_GENERIC_UNKNOWN or PERC2_E_GENERIC_UNKNOWN
Severity: Error
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."
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: PERC_E_GENERIC_WARNING or PERC2_E_GENERIC_WARNING
The following sections describe events generated by the PowerVault 660F controller.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
Name: DAM_MLXEV_CTLDEV_BBU_POWER_LOW
Note While the battery is low, the controller write cache will be disabled.
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.
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.
Cause: The controller configuration was cleared. All virtual disks and hot spares were removed. This is logged when the clear configuration operation is done.
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.
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 Subsystem folder object. If the array was booting up when the error occurred, it may be fully initialized during this rescan.
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.
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.
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.
By default, Array Manager installs SNMP trap forwarding support. For this support to function, you should have SNMP installed on the managed node 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 node (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 NT/2000 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 NT/2000, 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, see the document titled Dell OpenManage Array Manager 3.1 MIB Structure. This document is in the amMIBStructure.html file. The default location for this file is Program Files\Dell\OpenManage\Array Manager\MIB\amMIBStructure.html.
Note Array Manager does not provide SNMP support on the Microsoft Windows
Advanced Server Limited Edition 64-bit operating system. For more information on
the Microsoft Windows Advanced Server Limited Edition operating system, see the
README file.
