DELL 34XX User Manual
Assigning Global Hot Spares
Hot spare physical disks can replace any failed physical disk in the storage array. The hot spare must be
the same type of physical disk as the physical disk that failed and must have capacity greater than or
equal to any physical disk that can fail. If a hot spare is smaller than a failed physical disk, the hot spare
cannot be used to rebuild the data from the failed physical disk. Hot spares are available only for RAID
levels 1 or 5.
You can assign or unassign global hot spares by using the set physicalDisk command. To use this
command, you must perform these steps:
the same type of physical disk as the physical disk that failed and must have capacity greater than or
equal to any physical disk that can fail. If a hot spare is smaller than a failed physical disk, the hot spare
cannot be used to rebuild the data from the failed physical disk. Hot spares are available only for RAID
levels 1 or 5.
You can assign or unassign global hot spares by using the set physicalDisk command. To use this
command, you must perform these steps:
1.
Identify the location of the physical disks by enclosure ID and slot ID.
2.
Set the hotSpare parameter to TRUE to enable the hot spare or FALSE to disable an existing hot
spare.
The following syntax is the general form of the command:
set (physicalDisk [enclosureID,slotID] |
set (physicalDisk [enclosureID,slotID] |
physicalDisks [enclosureID0,slotID0 ...
enclosureIDn,slotIDn] hotSpare=(TRUE | FALSE)
The following example shows how to use this command to set hot spare physical disks:
client>smcli 123.45.67.89 -c "set physicalDisks
client>smcli 123.45.67.89 -c "set physicalDisks
[0,2 0,3] hotSpare=TRUE;"
Enter the enclosure ID and slot ID of each physical disk that you want to use. You must put brackets ([ ])
around the list. Separate the enclosure ID and slot ID of a physical disk by a comma. Separate each
enclosure ID and slot ID pair by a space.
around the list. Separate the enclosure ID and slot ID of a physical disk by a comma. Separate each
enclosure ID and slot ID pair by a space.
Selecting The Event Levels For Alert Notifications
The MD storage management software has four event levels: Critical, Informational, Warning, and Debug.
You can configure the MD storage management software to send alert notifications for all of these event
levels or only for certain event levels.
A background task called the persistent monitor runs independently of the MD storage management
software and monitors the occurrence of events on all of the managed storage arrays. The persistent
monitor is installed automatically with the MD storage management software. When an event occurs,
alert notifications in the form of emails and SNMP trap messages are sent to the destination addresses
that are specified in the Configure Alerts dialog. For more information about how to specify the
destination addresses, refer to the Configuring the Email and SNMP Alert Notification Settings online help
topic in the Enterprise Management Window (EMW).
A background task called the persistent monitor runs independently of the MD storage management
software and monitors the occurrence of events on all of the managed storage arrays. The persistent
monitor is installed automatically with the MD storage management software. When an event occurs,
alert notifications in the form of emails and SNMP trap messages are sent to the destination addresses
that are specified in the Configure Alerts dialog. For more information about how to specify the
destination addresses, refer to the Configuring the Email and SNMP Alert Notification Settings online help
topic in the Enterprise Management Window (EMW).
When the persistent monitor starts for the first time, a properties file is created in the directory where the
MD storage management software files are located. The properties file can be configured to enable or
disable local logging in the Windows and UNIX operating systems. By default, local logging is enabled in
the properties file.
MD storage management software files are located. The properties file can be configured to enable or
disable local logging in the Windows and UNIX operating systems. By default, local logging is enabled in
the properties file.
When local logging is enabled in the Windows operating system, the persistent monitor logs the event
information in the Windows Event Log file. When local logging is enabled in the UNIX operating system,
the persistent monitor logs the event information in the syslog file. The properties file can also be
configured to enable or disable remote syslog notification. You must restart the persistent monitor
service after configuring the properties file for the changes to take effect.
information in the Windows Event Log file. When local logging is enabled in the UNIX operating system,
the persistent monitor logs the event information in the syslog file. The properties file can also be
configured to enable or disable remote syslog notification. You must restart the persistent monitor
service after configuring the properties file for the changes to take effect.
50