The CLI of Storage Management enables you to perform all of Storage Management's reporting, configuration, and management functions from an operating system command shell. The Storage Management CLI also enables you to script command sequences.
The Storage Management CLI provides expanded options for the Dell OpenManage Server Administrator omreport and omconfig commands. This chapter only documents the omreport and omconfig commands that apply to Storage Management. For more information, see the Dell OpenManage Installation and Security User's Guide. See the Storage Management online Help and Dell OpenManage Server Administrator Storage Management User's Guide for more information on Storage Management.
CLI Command Syntax
Like all Server Administrator commands, the omreport and omconfig command syntax consists of specifying command "levels." The first command level is the command name: omreport or omconfig. Subsequent command levels provide a greater degree of specification regarding the type of object on which the command operates or the information that the command will displays.
For example, the following omconfig command syntax has three levels:
Indicates the Server Administrator service (in this case, Storage Management) that implements the command
pdisk
Specifies the type of object on which the command operates
Following the command levels, the omreport and omconfig command syntax may require one or more name=value pairs. The name=value pairs specify exact objects (such as a specific physical disk) or options (such as "blink" or "unblink") that the command implements.
For example, the following omconfig command syntax for blinking a physical disk has three levels and three name=value pairs:
where PDISKID=<connector:enclosureID:portID | connector:targetID>
In this example, the id in controller=id is the controller number such that controller 1 would be specified as controller=1.
Syntax for Required, Optional, and Variable
Command Elements
The omreport and omconfig commands have multiple name=value pairs. These name=value pairs may include required, optional, and variable parameters. Table 6-2 describes the syntax used to indicate these parameters.
Table 6-2. Syntax For Name=Value Pairs For Parameters
Syntax
Description
controller=id
Indicates the controller ID as reported by the omreport storage controller command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=id to display the IDs for the physical disks attached to the controller.
For example, the controller=id parameter might be specified as controller=1.
connector=id
Indicates the connector ID as reported by the omreport command. To obtain this value, enter omreport storage controller to display the controller IDs and then enter omreport storage connector controller=id to display the IDs for the connectors attached to the controller.
For example, the connector=id parameter might be specified as connector=2.
vdisk=id
Indicates the virtual disk ID as reported by the omreport command. To obtain this value, enteromreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=id to display the IDs for the virtual disks on the controller.
For example, the vdisk=id parameter might be specified as vdisk=3.
enclosure=<ENCLOSUREID>
Indicates a particular enclosure by specifying either enclosure=connector or enclosure=connector:enclosureID.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage enclosure controller=id to display the IDs for the enclosures attached to the controller.
pdisk=<PDISKID>
Indicates a particular physical disk by specifying either connector:targetID or connector:enclosureID:portID.
To obtain the values for the connector, enclosure, and physical disk (targetID or portID), enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=id to display the IDs for the physical disks attached to the controller.
battery=id
Indicates the battery ID as reported by the omreport command. To obtain this value, enter omreport storage controller to display the controller IDs and then enter omreport storage battery controller=id to display the ID for the controller battery.
< >
The caret symbols (< >) enclose variable elements that you must specify.
For example, the name=<string> parameter might be specified as name=VirtualDisk1.
[ ]
The bracket symbols ([ ]) indicate optional elements that you can choose whether or not to specify.
For example, when creating a virtual disk, the [name=<string>] parameter indicates that you have the option of specifying the virtual disk name. If you omit this parameter from the syntax, then a default name for the virtual disk is chosen for you.
|
The pipe symbol (|) separates two or more options from which one only must be selected.
For example, when creating a virtual disk, the cachepolicy=d|c indicates that the cache policy must be specified as either cachepolicy=d or cachepolicy=c.
User Privileges for omreport storage and
omconfig storage
Storage Management requires Administrator privileges to use the omconfig storage command. User and Power User privileges are sufficient to use the omreport storagecommand.
omreport Command
The following sections provide the omreport command syntax required to display the status of various storage components.
omreport Storage Help
Table 6-3 provides the omreport storage command syntax.
Table 6-3. omreport storage help
Command Level 1
Command Level 2
Command Level 3
Use
omreport
storage
Displays a list of storage components for which omreport commands are available.
pdisk
Displays a list of the omreport storage pdisk parameters for displaying physical disk information.
vdisk
Displays a list of omreport storage vdisk parameters for displaying virtual disk information.
controller
Displays a list of the omreport storage controller parameters for displaying controller information.
enclosure
Displays a list of the omreport storage enclosure parameters for displaying enclosure information.
connector
Displays a list of the omreport storage connector parameters for displaying connector information.
battery
Displays a list of the omreport storage battery parameters for displaying battery information.
globalinfo
Displays a list of the omreport storage globalinfo parameters for displaying global storage property information.
omreport Controller Status
Table 6-4 describes the syntax for the omreport Controller Commands.
Table 6-4. omreport Controller Commands
Required Command Levels (1, 2, 3)
Optional name=value pairs
Use
omreport storage controller
Displays property information for all controllers attached to the system.
controller=id
where id is the controller number. For example: controller=0
Displays the specified controller and all attached components such as enclosures, virtual disks, physical disks, and so on.
omreport Global Information (Smart Thermal Shutdown Status)
Table 6-5 describes the syntax for the omreport Global Information Commands.
where id is the controller number and ENCLOSUREID is the enclosure number and "n" is the number of a temperature probe. For example: controller=0 enclosure=2 info=temps index=1
Displays the specified temperature probe.
omreport Fan Status
Table 6-10 describes the syntax for the omreport Fan Commands
Table 6-10. omreport Fan Status
Required Command Levels (1, 2, 3) and name=value pair
Optional name=value pairs
Use
omreport storage enclosure
Displays property information for all enclosures attached to the system.
controller=id enclosure=<ENCLOSUREID> info=fans
where id is the controller number and ENCLOSUREID is the enclosure number. For example: controller=0 enclosure=2
NOTE: For SCSI controllers, the ID specified in enclosure=<ENCLOSUREID> is the connector number and for Serial Attached SCSI (SAS) controllers, ID is the connectorNumber:EnclosureIndex.
where id is the controller number and ENCLOSUREID is the enclosure number and "n" is the number of a fan. For example: controller=0 enclosure=2 info=fans index=1
Displays the specified fan.
omreport Power Supply Status
Table 6-11 describes the syntax for the omreport Power Supply Commands
Table 6-11. omreport Power Supply Commands
Required Command Levels (1, 2, 3) and name=value pair
Optional name=value pairs
Use
omreport storage enclosure
Displays property information for all enclosures attached to the system.
where id is the controller number and ENCLOSUREID is the enclosure number and "n" is the number of a power supply. For example: controller=0 enclosure=2 info=pwrsupplies index=1
Displays the specified power supply.
omreport EMM Status
Table 6-12 describes the syntax for the omreport EMM Commands
Table 6-12. omreport EMM Commands
Required Command Levels (1, 2, 3) and name=value pair
Optional name=value pairs
Use
omreport storage enclosure
Displays property information for all enclosures attached to the system.
controller=id enclosure=<ENCLOSUREID> info=emms
where id is the controller number and ENCLOSUREID is the enclosure number. For example: controller=0 enclosure=2
Displays the enclosure management modules (EMMs) for the specified enclosure.
where id is the controller number and ENCLOSUREID is the enclosure number and "n" is the number of an EMM. For example: controller=0 enclosure=2 info=emms index=1
Displays the specified EMMs.
omreport Physical Disk Status
Table 6-13 describes the syntax for the omreport Physical Disk Commands
Table 6-13. omreport Physical Disk Commands
Required Command Levels (1, 2, 3) and name=value pair
Optional name=value pairs
Use
omreport storage pdisk
controller=id
where id is the controller number. For example: controller=0
Displays all physical disks attached to the specified controller.
connector=id
where id is the connector number. For example: connector=1
Displays all physical disks attached to the specified connector on the controller.
vdisk=id
where id is the virtual disk number. For example: vdisk=1
Displays all physical disks included in the specified virtual disk on the controller.
where connectorID:targetID is the connector number and the physical disk number and connectorID:enclosureID:slotID is the connector number, enclosure number, and slot number.
For example: pdisk=0:2 or pdisk=0:1:2
Displays the specified physical disk on the specified connector on the controller.
omreport Virtual Disk Status
Table 6-14 describes the syntax for the omreport Virtual Disk Commands
Table 6-14. omreport Virtual Disk Commands
Required Command Levels (1, 2, 3)
Optional name=value pairs
Use
omreport storage vdisk
Displays property information for all virtual disks on all controllers.
controller=id
where id is the controller number. For example: controller=0.
Displays all virtual disks on the specified controller.
controller=id vdisk=id
where id is the controller number and the virtual disk number. For example: controller=0 vdisk=1.
Displays the specified virtual disk on the controller.
omconfig Global Commands
The following sections provide the omconfigcommand syntax required to execute the global commands. When executed, these commands apply to all controllers. These global commands also correspond to the global tasks provided by the Storage tree view object's Information/Configuration subtab.
Table 6-15. omconfig Global Commands
Required Command Levels (1, 2, 3)
Optional name=value pairs
omconfig storage globalinfo
action=enablests
action=disablests
action=globalrescan
omconfig Global Enable Smart Thermal Shutdown
By default, the operating system and server shut down when the PV220S and PV221S enclosures reach a critical temperature of 0 or 50° Celsius. However, if you have implemented connector redundancy on the PV220S and PV221S enclosures you can specify that only the enclosure and not the operating system and server be shut down when the enclosure reaches a critical temperature of 0 or 50° Celsius. Specifying that only the enclosure be shut down during excessive temperatures is known as Smart Thermal Shutdown. See Dell OpenManage Online Help for more information about Smart Thermal Shutdown.
Use the following omconfigcommand syntax to enable smart thermal shutdown.
Complete Syntax
omconfig storage globalinfo action=enablests
Example Syntax
The omconfigcommand syntax for enabling thermal shutdown does not require that you specify a controller or enclosure ID. To enable thermal shutdown, enter the following:
omconfig storage globalinfo action=enablests
NOTE: You can use the omreport storage globalinfo command to determine whether smart thermal shutdown is currently enabled or disabled. The status of smart thermal shutdown is also displayed by the Server Administrator graphical user interface (GUI). To locate this status, select the Storage object and the Information/Configuration tab.
omconfig Global Disable Smart Thermal Shutdown
If you have previously enabled smart thermal shutdown using the omconfigcommand, you can disable smart thermal shutdown and return the system to its default setting. When smart thermal shutdown is disabled, the operating system and the server shuts down when the PV220S and PV221S enclosures reach a critical temperature of 0 or 50° Celsius.
Use the following omconfigcommand syntax to disable smart thermal shutdown for all controllers.
Complete Syntax
omconfig storage globalinfo action=disablests
Example Syntax
The omconfigcommand syntax for disabling thermal shutdown does not require that you specify a controller or enclosure ID. To disable thermal shutdown, enter the following:
omconfig storage globalinfo action=disablests
NOTE: You can use the omreport storage globalinfo command to determine whether smart thermal shutdown is currently enabled or disabled. The status of smart thermal shutdown is also displayed in the GUI of Server Administrator. To locate this status, select the Storage object and the Information/Configuration tab.
omconfig Global Rescan Controller
Use the following omconfigcommand syntax to rescan all controllers on the system. See Dell OpenManage Online Help for more information about Global Rescan Controller.
Complete Syntax
omconfig storage globalinfo action=globalrescan
Example Syntax
The omconfigcommand syntax for rescanning all controllers on the system does not require that you specify a controller ID. To do a global rescan of all controllers, enter the following:
omconfig storage globalinfo action=globalrescan
NOTE: Global rescan is not supported on non-RAID SCSI and SAS controllers. Reboot the system for the configuration changes on non-RAID SCSI controllers to be visible.
omconfig Controller Commands
The following sections provide the omconfig command syntax required to execute controller tasks.
NOTICE: The omconfig storage controller action=resetconfig controller=id resets the controller configuration. Resetting the controller configuration permanently destroys all data on all virtual disks attached to the controller. System or boot partition residing on these virtual disks will be destroyed.
NOTE: The rescan controller is not supported on nonRAID SCSI and SAS controllers. Reboot the system for the configuration changes on non-RAID SCSI controllers to be visible.
omconfig Enable Controller Alarm
Use the following omconfig command syntax to enable the controller alarm. See Dell OpenManage Online Help for more information about Enable Controller Alarm.
Use the following omconfig command syntax to disable the controller alarm. See Dell OpenManage Online Help for more information about Disable Controller Alarm.
Use the following omconfig command syntax to silence an activated controller alarm. See Dell OpenManage Online Help for more information about Quite Controller Alarm.
Use the following omconfig command syntax to test the functionality of the controller alarm. The alarm will sound for about two seconds. See Dell OpenManage Online Help for more information about Test Controller Alarm.
Use the following omconfig command syntax to reset the controller configuration.
NOTICE: Resetting a configuration permanently destroys all data on all virtual disks attached to the controller. System or boot partition residing on these virtual disks will be destroyed. You may receive a warning message if this command results in deleting the system or boot partition. However, this warning message is not generated in all circumstances. Ensure that you are not deleting the system or boot partition or other vital data when using this command.
where id is the controller ID as reported by the omreport storage controller command.
In some circumstances, you may receive a warning message if this command deletes the system or boot partition. You can override this warning by using the force=yes parameter. In this case, the syntax is as follows:
Use the raid=<c| r0| r1| r1c| r5| r6 | r10| r50| r60>parameter to specify concatenation or a RAID level for a virtual disk. Different controllers support different RAID levels. See Dell OpenManage Online Help for more information about RAID levels a controller supports and for general information about RAID levels and concatenation. Table 6-17 indicates how to specify the raid=n parameter for each RAID level and concatenation.
Table 6-17. Raid Level and Concatenation
RAID Level or Concatenation
raid=n Parameter Specification
RAID-0
raid=r0
RAID-1
raid=r1
RAID-5
raid=r5
RAID-6
raid=r6
RAID-10
raid=r10
RAID-50
raid=r50
RAID-60
raid=r60
RAID-1-concatenated
raid=r1c
Concatenation
raid=c
size=<number | max | min> Parameter (Required)
Table 6-18 indicates how to specify the size=<number | max | min> parameter.
Table 6-18. Size Parameter
size=<number | max | min> Parameter Specification
Description
size=<n>
Use this specification to indicate a specific size for the virtual disk. The virtual disk size may be specified in b (bytes), m (megabytes), or g (gigabytes). For example, size=500m indicates that the virtual disk should be 500 MB.
size=max
To create a virtual disk that is the maximum size possible, specify size=max. When creating a RAID-50 virtual disk, this parameter must be specified as size=max.
size=min
To create a virtual disk that is the minimum size possible, specify size=min.
Use this parameter to specify the physical disks to included in the virtual disk.
When reconfiguring a virtual disk, you must specify all physical disks to be included in the reconfigured virtual disk. The physical disk specification applies to physical disks in the original virtual disk and will continue to be in the reconfigured virtual disk and to any new physical disks being added to the reconfigured virtual disk. Some controllers allow you to remove a physical disk from a virtual disk. In this case, do not specify the physical disk to be removed.
The pdisk=<PDISKID> parameter indicates a physical disk by specifying either connector:enclosureID:portID or connector:targetID.
Different controllers support different stripe sizes. See Dell OpenManage Online Help for more information on stripe sizes supported for a controller. All stripe sizes are specified in kilobytes. For example, when specifying 128 KB as the stripe size, enter:
stripesize=128kb
[cachepolicy=<d | c>] Parameter (Optional)
Different controllers support different cache policies. Table 6-19 indicates how to specify the[cachepolicy=<d | c>]parameter for each of the cache policies.
Different controllers support different read policies. Table 6-20 indicates how to specify the [readpolicy=<ra| nra| ara| rc| nrc>]parameter for each of the read policies.
Different controllers support different write policies. Table 6-21 indicates how to specify the [writepolicy=<wb| wt| wc| nwc | fwb>]parameter for each of the write policies.
Use this parameter to specify a name for the virtual disk. For example:
name=VirtualDisk1
NOTE: The CERC SATA 1.5/2s controller does not allow you to specify a virtual disk name. The virtual disk will be created with a default name.
[spanlength=<n>] Parameter (Required for RAID-50)
Use this parameter to specify the number of physical disks to be included in each stripe. This parameter only applies to RAID-50 virtual disks. If you are not creating a RAID-50 virtual disk, do not specify this parameter. For example:
spanlength=3
Example Syntax
For example, you may want to create a RAID-5 virtual disk on a PERC 3/QC controller. See Dell OpenManage Online Help for information on read, write, and cache policies are supported by this controller. For example, to create a virtual disk with the following read, write, and cache policy:
Read-ahead
Writethrough caching
Cache I/O
The virtual disk will be 500 MB with a stripe size of 16 KB. The name of the virtual disk will be vd1 and it will reside on connector 0 of controller 1. Because the virtual disk will be a RAID-5, it requires at least three physical disks. In this example, you specify four physical disks. These are physical disks 0 through 3.
To create the virtual disk described in this example, enter:
The only parameters that require specification are for the controller, RAID level, virtual disk size, and physical disk selection. Storage Managementsupplies default values for all other unspecified parameters.
omconfig Set Controller Rebuild Rate
Use the following omconfig command syntax to set the controller rebuild rate:
Complete Syntax
omconfig storage controller action=setrebuildrate controller=id rate=<0 to 100>
where id is the controller ID as reported by the omreport storage controller command.
Example Syntax
To set the rebuild rate to 50 on controller 1, enter:
Use the following omconfig command syntax to export the controller log to a text file. See Dell OpenManage Online Help for more information about the exported log file.
By default, the log file is exported to C:\WINNT or C:\Windows on Microsoft® Windows® systems (based on the Windows version used) and /var/log on all Linux systems.
Depending on the controller, the log file name will either be afa_<mmdd>.log or lsi_<mmdd>.log where <mmdd> is the month and date. See Dell OpenManage Online Help for more information on the controller log file.
NOTE: The export log file command is not supported on the PERC 2/SC, 2/DC, 4/IM, CERC ATA 100/4ch, and CERC SATA 1.5/2s controllers.
omconfig Import Foreign Configuration
Use the following omconfig command syntax to import all virtual disks that reside on physical disks newly attached to the controller.
NOTE: To be able to stop patrol read, the current patrol read mode should be set to Manual.
omconfig Virtual Disk Commands
The following sections provide the omconfig command syntax required to execute virtual disk tasks.
NOTICE: The omconfig storage vdisk action=deletevdisk controller=id vdisk=id command deletes a virtual disk. Deleting a virtual disk destroys all information including file systems and volumes residing on the virtual disk.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To blink the physical disks in virtual disk 4 on controller 1, enter:
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To blink the physical disks in virtual disk 4 on controller 1, enter:
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To initialize virtual disk 4 on controller 1, enter:
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To cancel the initialization of virtual disk 4 on controller 1, enter:
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To fast initialize virtual disk 4 on controller 1, enter:
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To slow initialize virtual disk 4 on controller 1, enter:
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To cancel background initialization on virtual disk 4 on controller 1, enter:
Use the followingomconfig command syntax to recover data from a RAID-5 virtual disk that has been corrupted. This task attempts to reconstruct data from a corrupt portion of a physical disk included in a RAID-5 virtual disk.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To restore segments on virtual disk 4 on controller 1, enter:
Use the following omconfig command syntax to separate mirrored data originally configured as a RAID 1, RAID-1concatenated, or RAID-10 virtual disk. Splitting a RAID-1 or RAID-1concatenated mirror creates two concatenated non-redundant virtual disks. Splitting a RAID-10 mirror creates two RAID-0 (striped) non-redundant virtual disks. Data is not lost during this operation.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To initiate a split mirror on virtual disk 4 on controller 1, enter:
Use the following omconfig command syntax to separate mirrored data and restore one half of the mirror to free space. Unmirroring a RAID-1 or RAID-1concatenated virtual disk results in a single, non-redundant concatenated virtual disk. Unmirroring a RAID-10 virtual disk results in a single, non-redundant RAID-0 (striped) virtual disk. Data is not lost during this operation. See Dell OpenManage Online Help for more information about Unmirror.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To unmirror virtual disk 4 on controller 1, enter:
where id is the controller ID and virtual disk ID. The <PDISK> variable specifies the physical disk.
To obtain the values for the controller, virtual disk, and physical disk, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID and omreport storage pdisk controller=ID to display the IDs for the virtual disks and physical disks attached to the controller.
Example Syntax
In this example, you are assigning physical disk 3 on connector 0 of controller 1 as a dedicated hot spare to virtual disk 4. On a Serial Attached SCSI (SAS) controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To assign the dedicated hot spare described in this example, enter:
where id is the controller ID and virtual disk ID. The <PDISK> variable specifies the physical disk.
To obtain the values for the controller, virtual disk, and physical disk, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID and omreport storage pdisk controller=ID to display the IDs for the virtual disks and physical disks attached to the controller.
Example Syntax
In this example, you are unassigning physical disk 3 on connector 0 of controller 1 as a dedicated hot spare to virtual disk 4. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To unassign the dedicated hot spare described in this example, enter:
Use the following omconfig command syntax to initiate a check consistency on a virtual disk. The check consistency task verifies the virtual disk's redundant data.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To run a check consistency on virtual disk 4 on controller 1, enter:
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To cancel a check consistency on virtual disk 4 on controller 1, enter:
Use the following omconfig command syntax to pause a check consistency while in progress. See Dell OpenManage Online Help for more information about Pause Check Consistency.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To pause a check consistency on virtual disk 4 on controller 1, enter:
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To resume a check consistency on virtual disk 4 on controller 1, enter:
Use the following omconfig command syntax to delete a virtual disk.
NOTICE: Deleting a virtual disk destroys all information including file systems and volumes residing on the virtual disk. You may receive a warning message if you attempt to delete the system or boot partition. However, this warning message is not generated in all circumstances. Ensure that you are not deleting the system or boot partition or other vital data when using this command.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
You can reconfigure a virtual disk to change the virtual disk's RAID level or increase its size by adding physical disks. On some controllers, you can also remove physical disks.
To reconfigure virtual disk 4 to a size of 800 MB, use RAID-5 and physical disks 0 through 3 on connector 0 of controller 1. On a SAS controller, the physical disks reside in enclosure 2.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
See Dell OpenManage Online Help for more information about the controller-specific read, write, and cache policy. For information on specifying these parameters using the omconfig command, see the following:
where id is the controller ID and virtual disk ID as reported by the omreport command and <string> is the new name for the virtual disk. To obtain the values for controller ID and virtual disk ID, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
Example Syntax
To rename virtual disk 4 on controller 1 to vd4, enter:
You can blink the light (light emitting diode or LED display) on one or more physical disks attached to a controller. Use the following omconfig command syntax to blink one or more physical disks.
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to blink physical disk 0 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To blink the physical disk described in this example, enter:
You can unblink the light (light emitting diode or LED display) on one or more physical disks attached to a controller. Use the following omconfig command syntax to unblink one or more physical disks.
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to unblink physical disk 0 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To unblink the physical disk described in this example, enter:
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to prepare physical disk 3 on connector 0 of controller 1 for removal. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To prepare to remove the physical disk described in this example, enter:
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to initialize physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To initialize the physical disk described in this example, enter:
where id is the controller ID and connectorID:targetID is the connector number and physical disk number as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
To offline physical disk 3 on connector 0 of controller 1, enter:
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to offline physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To offline the physical disk described in this example, enter:
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to bring physical disk 3 on connector 0 of controller 1 back online. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To bring the physical disk described in this example back online, enter:
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to assign physical disk 3 on connector 0 of controller 1 as a global hot spare. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To assign the physical disk described in this example as a global hot spare, enter:
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to unassign physical disk 3 on connector 0 of controller 1 as a global hot spare. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To unassign the physical disk described in this example as a global hot spare, enter:
Use the following omconfig command syntax to rebuild a failed physical disk. Rebuilding a disk may take several hours. If you need to cancel the rebuild, use the Cancel Rebuild task. See Dell OpenManage Online Help for more information about Rebuild Physical Disk.
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to rebuild physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To rebuild the physical disk described in this example, enter:
Use the following omconfigcommand syntax to cancel a rebuild that is in progress. If you cancel a rebuild, the virtual disk remains in a degraded state. See Dell OpenManage Online Help for more information about Cancel Rebuild Physical Disk.
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to cancel the rebuild or physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To cancel the rebuild of the physical disk described in this example, enter:
Use the following omconfig command syntax to recover unusable disk space. See Dell OpenManage Online Help for more information about Removing Dead Segments.
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to remove dead disk segments on physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers
To remove dead segments on the physical disk described in this example, enter:
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to clear physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SAS Controllers
To clear the physical disk described in this example, enter:
where id is the controller ID. The <PDISK> variable specifies the physical disk.
To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax
In this example, you want to cancel the clear of physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SAS Controllers
To cancel the clear of the physical disk described in this example, enter:
The following sections provide the omconfig command syntax required to execute battery tasks.
Table 6-24. omconfig Battery Commands
Required Command Levels (1, 2, 3)
Optional name=value pairs
omconfig storage battery
action=recondition controller=id battery=id
action=startlearn controller=id battery=id
action=delaylearn controller=id battery=id
days=d hours=h
omconfig Recondition Battery
Use the following omconfig command to recondition a controller battery. See Dell OpenManage Online Help for more information on batteries and the recondition process.
where id is the controller ID and battery ID as reported by the omreport command. To obtain this value, enter omreport storage controller to display the controller IDs and then enter omreport storage battery controller=ID to display the ID for the controller battery.
Example Syntax
To recondition the battery on controller 1, enter:
where id is the controller ID and battery ID as reported by the omreport command. To obtain this value, enter omreport storage controller to display the controller IDs and then enter omreport storage battery controller=ID to display the ID for the controller battery.
Use the following omconfig command to delay the battery learn cycle for a specified period of time. The battery learn cycle can be delayed for a maximum of seven days or 168 hours.
where id is the controller ID and battery ID as reported by the omreport command. To obtain this value, enter omreport storage controller to display the controller IDs and then enter omreport storage battery controller=ID to display the ID for the controller battery.
Example Syntax
To delay the learn cycle for three days and 12 hours on controller 1, enter:
The following sections provide the omconfig command syntax required to execute connector tasks.
Table 6-25. omconfig Connector Commands
Required Command Levels (1, 2, 3)
Optional name=value pairs
omconfig storage connector
action=rescan controller=id connector=id
omconfig Rescan Connector
Use the following omconfig command to rescan a controller connector. This command rescans all connectors on the controller and is therefore similar to performing a controller rescan.
NOTE: This command is not supported on SAS controllers.
where id is the controller ID and the connector ID as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage connector controller=ID to display the IDs for the connectors attached to the controller.
where id is the controller ID and the temperature probe ID. The <ENCLOSUREID> variable specifies the enclosure.
In this syntax, "n" is a user-specified value for the temperature in Celsius.
Example Syntax
For example, you may want to specify the minimum and maximum warning thresholds for temperature probe 3 to 10 and 40° Celsius.
Example for SCSI, SATA, and ATA Controllers
In this example, temperature probe 3 resides in the enclosure attached to connector 2 on controller 1. To set the temperature probe thresholds to 10 and 40° Celsius, enter:
where id is the controller ID and the temperature probe ID. The <ENCLOSUREID> variable specifies the enclosure.
Example Syntax
For example, you may want to reset the thresholds for temperature probe 3 to the default values.
Example for SCSI, SATA, and ATA Controllers
In this example, temperature probe 3 resides in the enclosure attached to connector 2 on controller 1. To reset the thresholds for temperature probe 3 to the default values, enter:
where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure.
Example Syntax
For example, you may want to specify the minimum and maximum warning thresholds for all temperature probes to 10 and 40° Celsius.
Example for SAS Controllers
In this example, the temperature probes reside in enclosure 3 attached to connector 2 on controller 1. To set the thresholds for all temperature probes to 10 and 40° Celsius, enter:
Use the following omconfig command syntax to reset the minimum and maximum warning temperature thresholds back to their default value for all temperature probes in the enclosure.
NOTE: This command is not supported on SCSI RAID controllers.
where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure.
Example Syntax
For example, you may want to reset the thresholds for all temperature probes in enclosure 2 on controller 1.
Example for SAS Controllers
In this example, the temperature probes reside in enclosure 3 attached to connector 2 on controller 1. To reset the thresholds for all temperature probes, enter: