CLI Command SyntaxGo to Table of Contents for Storage Management Online Help
Dell OpenManage™ Storage Management User's Guide
Syntax for Required, Optional, and Variable Command Elements
User Privileges for omreport storage and omconfig storage
omconfig Virtual Disk Commands
Storage Management has a fully-featured command line interface (CLI) that 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. When using the Storage Management CLI, you should be familiar with the Dell OpenManage Server Administrator CLI options documented in the Dell OpenManage Server Administrator Command Line Interface User's Guide. This Storage Management chapter only documents the omreport and omconfig options that apply to Storage Management. The Dell OpenManage Server Administrator Command Line Interface User's Guide provides extensive Server Administrator CLI information not provided in this Storage Management chapter.
Like all of the Dell OpenManage 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 specificity regarding the type of object on which the command will operate or the information that the command will display.
For example, the following omconfig command syntax has three levels:
omconfig storage adisk
The following table describes these command levels.
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 array disk) or options (such as "blink" or "unblink") that the command will implement.
For example, the following omconfig command syntax for blinking an array disk has three levels and three name=value pairs:
omconfig storage adisk action=blink controller=id adisk=<channelNo:targetID>
where "id" indicates the controller, channel, and array disk number. For example, to blink array disk 1 on channel 2 and controller 1, you would enter:
omconfig storage adisk action=blink controller=1 adisk=2:1
In some cases, the command syntax enables you to specify more than one target. In this case, the target IDs should be comma-separated without spaces. For example, to blink array disks 1, 2, and 3 on channel 2 and controller 1, you would enter:
omconfig storage adisk action=blink controller=1 adisk=2:1,2,3
The omreport and omconfig commands have multiple name=value pairs. These name=value pairs may include required, optional, and variable parameters. The following table describes the syntax used to indicate these parameters.
Storage Management requires Administrator privileges to use the omconfig storage command. User and Power User privileges are sufficient to use the omreport storage command. See User Privileges for more information.
The following sections provide the omreport command syntax required to display the status of various storage components.
The following table provides the omreport command syntax required to display high-level storage status.
The following sections provide the omconfig command syntax required to execute controller tasks.
|
Caution: 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. If the system or boot partition resides on these virtual disks, it will be destroyed. |
Required Command Levels (1, 2, 3) | Optional name=value Pairs | Documentation Section |
|---|---|---|
omconfig storage controller | ||
action=rescan controller=id | ||
action=globalrescan | ||
action=enablealarm controller=id | ||
action=disablealarm controller=id | ||
action=quietalarm controller=id | ||
action=testalarm controller=id | ||
action=resetconfig controller=id [force=yes] | ||
action=createvdisk controller=id raid=<c| r0| r1| r1c| r5| r10| r50> size=<number | max | min> adisk=<channel:targetID> [stripesize=< 2kb| 4kb| 8kb| 16kb| 32kb| 64kb| 128kb>] [cachepolicy=<d | c>] [readpolicy=<ra| nra| ara| rc| nrc>] [writepolicy=<wb| wt| wc| nwc>] [name=<string>] [spanlength=<n>] | ||
action=setrebuildrate controller=id rate=<0 to 100> | ||
action=exportlog controller=id |
Use the following omconfig command syntax to rescan a controller. See Rescan Controller and Rescan to Update Storage Configuration Changes for more information about using this command.
omconfig storage controller action=rescan controller=id
where "id" is the controller ID as reported by the omreport storage controller command.
For example, to rescan controller 1, you would enter:
omconfig storage controller action=globalrescan controller=1
Use the following omconfig command syntax to rescan all controllers. See Rescan Controller and Rescan to Update Storage Configuration Changes for more information about using this command.
omconfig storage controller action=globalrescan
There are no optional or variable elements in this syntax. To execute a global rescan, enter:
omconfig storage controller action=globalrescan
Use the following omconfig command syntax to enable the controller alarm.
omconfig storage controller action=enablealarm controller=id
where "id" is the controller ID as reported by the omreport storage controller command.
For example, to enable the alarm on controller 1, you would enter:
omconfig storage controller action=enablealarm controller=1
Use the following omconfig command syntax to disable the controller alarm:
omconfig storage controller action=disablealarm controller=id
where "id" is the controller ID as reported by the omreport storage controller command.
For example, to disable the alarm on controller 1, you would enter:
omconfig storage controller action=disablealarm controller=1
Use the following omconfig command syntax to quiet the controller alarm once it is sounding:
omconfig storage controller action=quietalarm controller=id
where "id" is the controller ID as reported by the omreport storage controller command.
For example, to quiet the alarm on controller 1, you would enter:
omconfig storage controller action=quietalarm controller=1
Use the following omconfig command syntax to test whether the controller alarm is functional. The alarm will sound for about two seconds.
 |
Note: This command is only available on the CERC SATA1.5/6ch controller. |
omconfig storage controller action=testalarm controller=id
where "id" is the controller ID as reported by the omreport storage controller command.
For example, to test the alarm on controller 1, you would enter:
omconfig storage controller action=testalarm controller=1
Use the following omconfig command syntax to reset the controller configuration.
|
|
Caution: Resetting a configuration permanently destroys all data on all virtual disks attached to the controller. If the system or boot partition resides on these virtual disks, it will be destroyed. You may receive a warning message if this command will result in deleting the system or boot partition. However, this warning message is not generated in all circumstances. You should be certain that you are not deleting the system or boot partition or other vital data when using this command. |
omconfig storage controller action=resetconfig controller=id
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 will delete the system or boot partition. You can override this warning by using the [force=yes] parameter. In this case, the syntax is as follows:
omconfig storage controller action=resetconfig controller=id [force=yes]
For example, to reset the configuration on controller 1, you would enter:
omconfig storage controller action=resetconfig controller=1
Before creating a virtual disk, you should be familiar with the information in the Considerations Before Creating Virtual Disks section.
The omconfig syntax for creating a virtual disk has several parameters. You must specify the following parameters:
The omconfig command supplies default values for any of the other parameters that you do not specify.
omconfig storage controller action=createvdisk controller=id raid=<c| r0| r1| r1c| r5| r10| r50> size=<number | max | min> adisk=<channel:targetID,channel:targetID,.....> [stripesize=< 2kb| 4kb| 8kb| 16kb| 32kb| 64kb| 128kb>] [cachepolicy=<d | c>] [readpolicy=<ra| nra| ara| rc| nrc>] [writepolicy=<wb| wt| wc| nwc>] [name=<string>] [spanlength=<n>]
The following sections indicate how to specify the omconfig storage controller action=createvdisk parameters.
Specify the controller ID as reported by the omreport storage controller command. For example:
controller=2
Use the raid=<c| r0| r1| r1c| r5| r10| r50> parameter to specify concatenation or a RAID level for a virtual disk. Different controllers support different RAID levels. See Controller-supported RAID Levels for information on which RAID levels a controller supports. See Choosing RAID Levels and Concatenation for general information about the RAID levels and concatenation. The following table indicates how to specify the raid=n parameter for each 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 50 | raid=r50 |
RAID 10 | raid=r10 |
RAID 1-concatenated | raid=r1c |
Concatenation | raid=c |
The following table indicates how to specify the size=<number | max | min> parameter.
Use this parameter to specify the array disks that will be included in the virtual disk.
When reconfiguring a virtual disk, be sure to specify all array disks, including those that were in the original, as well as the new, virtual disk. Some controllers allow you to remove an array disk from a virtual disk. In this case, you would not specify the array disk to be removed.
The channel:targetID element indicates an array disk by specifying the controller channel that the array disk is attached to and the array disk number. Repeat the channel:targetID element as many times as necessary to specify the array disks. For example:
adisk=1:0,1:1,1:2
Different controllers support different stripe sizes. See Controller-supported Stripe Sizes for information on which stripe sizes are supported for a controller. All stripe sizes are specified in kilobytes. For example, when specifying 128KB as the stripe size, you would enter:
stripesize=128kb
Different controllers support different cache policies. See Cache Policy for more information. The following table indicates how to specify the [cachepolicy=<d | c>] parameter for each of the cache policies.
|
Read Policy |
cachepolicy=d | c Parameter Specification |
|---|---|
Direct I/O | cachepolicy=d |
Cache I/O | cachepolicy=c |
Different controllers support different read policies. See Read Policy for more information. The following table indicates how to specify the [readpolicy=<ra| nra| ara| rc| nrc>] parameter for each of the read policies.
Different controllers support different write policies. See Write Policy for more information. The following table indicates how to specify the [writepolicy=<wb| wt| wc| nwc>] parameter for each of the write policies.
|
Read Policy |
writepolicy=wb | wt | wc | nwc Parameter Specification |
|---|---|
Write-back cache | writepolicy=wb |
Write-through cache | writepolicy=wt |
Write cache | writepolicy=wc |
No write cache | writepolicy=nwc |
Use this parameter to specify a name for the virtual disk. For example:
name=VirtualDisk1
|
Note: The CERC SATA1.5/2s controller does not allow you to specify a virtual disk name. The virtual disk will be created with a default name. |
Use this parameter to specify the number of array 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
For example, you may want to create a RAID 5 virtual disk on a PERC 3/QC controller. To understand which read, write, and cache policies are supported by this controller, you would refer to the RAID Controller Read, Write, and Cache Policy section. In this example, you decide to create a virtual disk with the following read, write, and cache policy:
The virtual disk will be 500MB with a stripe size of 16KB. The name of the virtual disk will be vd1 and it will reside on channel 0 of controller 1. Because the virtual disk will be a RAID 5, it requires at least three array disks. In this example, you specify four array disks. These are array disks 0 through 3.
To create the virtual disk described in this example, you would enter:
omconfig storage controller action=createvdisk controller=1 raid=r5 size=500m adisk=0:0,0:1,0:2,0:3 stripesize=16kb cachepolicy=c readpolicy=ra writepolicy=wt
The only parameters that require specification are for the controller, RAID level, virtual disk size, and array disk selection. The omconfig command supplies default values for all other unspecified parameters.
Use the following omconfig command syntax to set the controller rebuild rate. See Set Rebuild Rate for more information.
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.
For example, to set the rebuild rate on controller 1 to 50, you would enter:
omconfig storage controller action=setrebuildrate controller=1 rate=50
Use the following omconfig command syntax to export the controller log to a text file. For more information about the exported log file, see Export Log.
omconfig storage controller action=exportlog controller=id
where "id" is the controller ID as reported by the omreport storage controller command.
For example, to export the log on controller 1, you would enter:
omconfig storage controller action=exportlog controller=1
By default, the log file is exported to the <install-directory>/sm directory where <install-directory> is the directory where you have installed Server Administrator.
Depending on the controller, the log file name will be either afa_<mmdd>.log or lsi_<mmdd>.log where <mmdd> is the month and date. For more information on the controller log file, see Export Log.
|
Note: The Export Log File command is not supported on the PERC 2/SC, 2/DC, 4/IM, CERC ATA100/4ch, and CERC SATA1.5/2s controllers. |
The following sections provide the omconfig command syntax required to execute virtual disk tasks.
|
|
Caution: 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. |
|
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Documentation Section |
|---|---|---|
|
omconfig storage vdisk |
|
|
action=checkconsistency controller=id vdisk=id | ||
action=cancelcheckconsistency controller=id vdisk=id | ||
action=pausecheckconsistency controller=id vdisk=id | ||
action=resumecheckconsistency controller=id vdisk=id | ||
action=blink controller=id vdisk=id | ||
action=unblink controller=id vdisk=id | ||
action=initialize controller=id vdisk=id | ||
action=cancelinitialize controller=id vdisk=id | ||
action=cancelbginitialize controller=id vdisk=id | ||
action=restoresegments controller=id vdisk=id | ||
action=splitmirror controller=id vdisk=id | ||
action=unmirror controller=id vdisk=id | ||
action=assigndedicatedhotspare controller=id vdisk=id adisk=<channelNo:targetID> assign=<yes|no> | omconfig Assign Dedicated Hot Spare and omconfig Unassign Dedicated Hot Spare | |
action=deletevdisk controller=id vdisk=id [force=yes] | ||
action=format controller=id vdisk=id | ||
action=reconfigure controller=id vdisk=id raid=<c| r0| r1| r1c| r5| r10> size=<size> adisk=<channel:targetID,channel:targetID,.....> | ||
action=changepolicy controller=id vdisk=id [readpolicy=<ra| nra| ara| rc| nrc> | writepolicy=<wb| wt| wc| nwc> | cachepolicy=<d | c>] | ||
action=rename controller=id vdisk=id name=<string> |
Use the following omconfig command syntax to blink the array disks included in a virtual disk.
omconfig storage vdisk action=blink controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to blink the array disks in virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=blink controller=1 vdisk=4
Use the following omconfig command syntax to unblink the array disks included in a virtual disk.
omconfig storage vdisk action=unblink controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to blink the array disks in virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=unblink controller=1 vdisk=4
Use the following omconfig command syntax to initialize a virtual disk.
omconfig storage vdisk action=initialize controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to initialize virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=initialize controller=1 vdisk=4
Use the following omconfig command syntax to cancel the initialization of a virtual disk.
omconfig storage vdisk action=cancelinitialize controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to cancel the initialization of virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=cancelinitialize controller=1 vdisk=4
Use the following omconfig command syntax to cancel the background initialization process on a virtual disk. See Cancel Background Initialization and Background Initialization on PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch Controllers for more information.
omconfig storage vdisk action=cancelbginitialize controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to cancel background initialization on virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=cancelbginitialize controller=1 vdisk=4
Use the following omconfig 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 an array disk included in a RAID-5 virtual disk. See Restore Dead Segments for more information.
omconfig storage vdisk action=restoresegments controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to restore segments on virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=restoresegments controller=1 vdisk=4
Use the following omconfig command syntax to separate mirrored data originally configured as a RAID 1, RAID 1-concatenated, or RAID 10 virtual disk. Splitting a RAID 1 or RAID 1-concatenated 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. See Split Mirror for more information.
omconfig storage vdisk action=splitmirror controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to initiate a split mirror on virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=splitmirror controller=1 vdisk=4
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 1-concatenated 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.
|
Note: This operation is not supported when using a dynamic virtual disk with a PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, or CERC SATA1.5/2s controller. |
omconfig storage vdisk action=unmirror controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to unmirror virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=unmirror controller=1 vdisk=4
Use the following omconfig command syntax to assign one or more array disks to a virtual disk as a dedicated hot spare.
For more information on hot spares including size requirements, see Protecting Your Virtual Disk with a Hot Spare. For considerations regarding RAID 10 and RAID 50 virtual disks created using the controller BIOS, see Dedicated Hot Spare Considerations for RAID 10 and RAID 50 on PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch Controllers.
|
Note: The PERC 2/SC, 2/DC, and CERC SATA1.5/2s controllers do not support dedicated hot spares. |
omconfig storage vdisk action=assigndedicatedhotspare controller=id vdisk=id [adisk=channelID:targetID,channelID:targetID,...] assign=yes
where "id" is the controller ID and virtual disk ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID and omreport storage adisk controller=ID to display the IDs for the virtual disks and array disks attached to the controller.
For example, to assign array disk 3 on channel 0 of controller 1 to virtual disk 4, you would enter:
omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 adisk=0:3 assign=yes
You may want to assign more than one array disk as a dedicated hot spare. In this example, you want to assign array disk 3 on channel 0 and array disk 2 on channel 1 as dedicated hot spares:
omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 adisk=0:3,1:2 assign=yes
Use the following omconfig command syntax to unassign one or more array disks that were previously assigned as a hot spare to a virtual disk.
omconfig storage vdisk action=assigndedicatedhotspare controller=id vdisk=id [adisk=channelID:targetID,channelID:targetID,...] assign=no
where "id" is the controller ID and virtual disk ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID and omreport storage adisk controller=ID to display the IDs for the virtual disks and array disks attached to the controller.
For example, to unassign array disk 3 on channel 0 of controller 1 to virtual disk 4, you would enter:
omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 adisk=0:3 assign=no
You can also unassign more than one array disks that have been assigned as hot spares. In this example, you want to unassign array disk 3 on channel 0 and array disk 2 on channel 1 as dedicated hot spares:
omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 adisk=0:3,1:2 assign=no
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.
omconfig storage vdisk action=checkconsistency controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to run a check consistency on virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=checkconsistency controller=1 vdisk=4
Use the following omconfig command syntax to cancel a check consistency while it is in progress.
omconfig storage vdisk action=cancelcheckconsistency controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to cancel a check consistency on virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=cancelcheckconsistency controller=1 vdisk=4
Use the following omconfig command syntax to pause a check consistency while it is in progress.
omconfig storage vdisk action=pausecheckconsistency controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to pause a check consistency on virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=pausecheckconsistency controller=1 vdisk=4
Use the following omconfig command syntax to resume a check consistency after it has been paused.
omconfig storage vdisk action=resumecheckconsistency controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to resume a check consistency on virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=resumecheckconsistency controller=1 vdisk=4
Use the following omconfig command syntax to delete a virtual disk.
|
|
Caution: 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. You should be certain that you are not deleting the system or boot partition or other vital data when using this command. |
omconfig storage vdisk action=deletevdisk controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
In some circumstances, you may receive a warning message if you attempt to delete a virtual disk containing the system or boot partition. You can override this warning by using the [force=yes] parameter. In this case, the syntax is as follows:
omconfig storage vdisk action=deletevdisk controller=id vdisk=id [force=yes]
For example, to delete virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=deletevdisk controller=1 vdisk=4
Use the following omconfig command syntax to format a virtual disk.
omconfig storage vdisk action=format controller=id vdisk=id
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For example, to format virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=format controller=1 vdisk=4
You can reconfigure a virtual disk in order to change the virtual disk's RAID level or increase its size by adding array disks. On some controllers, you can also remove array disks.
Before continuing with the virtual disk reconfiguration, you should be familiar with the information in Starting and Target RAID Levels for Virtual Disk Reconfiguration and Choosing RAID Levels and Concatenation.
omconfig storage vdisk action=reconfigure controller=id vdisk=id raid=<c| r0| r1| r1c| r5| r10> size=<size> adisk=<channel:targetID,channel:targetID,.....>
See Parameter Specification for Create and Reconfigure Virtual Disk for information on specifying the parameters.
For example, you wish to reconfigure virtual disk 4 to a size of 800MB. You will use RAID 5 and array disks 0 through 3 on channel 0 of controller 1. In this example, you would enter:
omconfig storage vdisk action=reconfigure controller=1 vdisk=4 raid=r5 size=800m adisk=0:0,0:1,0:2,0:3
Use the following omconfig command syntax to change a virtual disk's read, write, or cache policy.
omconfig storage vdisk action=changepolicy controller=id vdisk=id [readpolicy=<ra| nra| ara| rc| nrc> | writepolicy=<wb| wt| wc| nwc> | cachepolicy=<d | c>]
where "id" is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would 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.
For information on the controller-specific read, write, and cache policy, see RAID Controller Read, Write, and Cache Policy. For information on how to specify these parameters using the omconfig command, see the following:
For example, to change the read policy of virtual disk 4 on controller 1 to no-read-ahead, you would enter:
omconfig storage vdisk action=changepolicy controller=1 vdisk=4 readpolicy=nra
Use the following omconfig command syntax to rename a virtual disk.
|
Note: On a CERC SATA1.5/2s controller, you cannot change the default name of a virtual disk. |
action=rename controller=id vdisk=id name=<string>
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, you would 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.
For example, to rename virtual disk 4 on controller 1 to vd4, you would enter:
omconfig storage vdisk action=rename controller=1 vdisk=4 name=vd4
The following sections provide the omconfig command syntax required to execute array disk tasks.
|
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Documentation Section |
|---|---|---|
|
omconfig storage adisk |
|
|
action=blink controller=id adisk=<channelNo:targetID> | ||
action=unblink controller=id adisk=<channelNo:targetID> | ||
action=remove controller=id adisk=<channelNo:targetID> | ||
action=initialize controller=id adisk=<channelNo:targetID> | ||
action=offline controller=id adisk=<channelNo:targetID> | ||
action=online controller=id adisk=<channelNo:targetID> | ||
action=assignglobalhotspare controller=id adisk=<channelNo:targetID> assign=<yes|no> | omconfig Assign Global Hot Spare and omconfig Unassign Global Hot Spare | |
action=rebuild controller=id adisk=<channelNo:targetID> | ||
action=cancelrebuild controller=id adisk=channelID:targetID | ||
action=removedeadsegments controller=id adisk=<channelNo:targetID> |
You can blink the light (light emitting diode or LED display) on one or more array disks attached to a controller. Use the following omconfig command syntax to blink one or more array disks.
action=blink controller=ID action=blink controller=id adisk=<channelNo:targetID>
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to blink array disks 0 through 2 on channel 0 of controller 1, you would enter:
omconfig storage adisk action=blink controller=1 adisk=0:0,0:1,0:2
You unblink the light (light emitting diode or LED display) on one or more array disks attached to a controller. Use the following omconfig command syntax to unblink one or more array disks.
omconfig storage adisk action=unblink controller=id adisk=channelID:targetID, channelID:targetId, channelID:targetID
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to unblink array disks 0 through 2 on channel 0 of controller 1, you would enter:
omconfig storage adisk action=unblink controller=1 adisk=0:0,0:1,0:2
Use the following omconfig command syntax to prepare an array disk for removal. See Prepare to Remove for more information.
omconfig storage adisk action=remove controller=id adisk=channelID:targetID
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to prepare array disk 3 on channel 0 of controller 1 for removal, you would enter:
omconfig storage adisk action=remove controller=1 adisk=0:3
Use the following omconfig command syntax to initialize an array disk.
omconfig storage adisk action=initialize controller=id adisk=channelID:targetID
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to initialize array disk 3 on channel 0 of controller 1, you would enter:
omconfig storage adisk action=initialize controller=1 adisk=0:3
Use the following omconfig command syntax to offline an array disk:
omconfig storage adisk action=offline controller=id adisk=channelID:targetID
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to offline array disk 3 on channel 0 of controller 1, you would enter:
omconfig storage adisk action=offline controller=1 adisk=0:3
Use the following omconfig command syntax to bring an offline array disk back online.
omconfig storage adisk action=online controller=id adisk=channelID:targetID
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to bring array disk 3 on channel 0 of controller 1 back online, you would enter:
omconfig storage adisk action=online controller=1 adisk=0:3
Use the following omconfig command syntax to assign an array disk as a global hot spare.
omconfig storage adisk action=assignglobalhotspare controller=id adisk=channelID:targetID assign=yes
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to assign array disk 3 on channel 0 of controller 1 as a global hot spare, you would enter:
omconfig storage adisk action=assignglobalhotspare controller=1 adisk=0:3 assign=yes
Use the following omconfig command syntax to unassign an array disk as a global hot spare.
omconfig storage adisk action=assignglobalhotspare controller=id adisk=channelID:targetID assign=no
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to unassign array disk 3 on channel 0 of controller 1 as a global hot spare, you would enter:
omconfig storage adisk action=assignglobalhotspare controller=1 adisk=0:3 assign=no
Use the following omconfig command syntax to rebuild a failed array disk. Rebuilding a disk may take several hours. If you need to cancel the rebuild, use the Cancel Rebuild task. For more information, see Rebuild.
omconfig storage adisk action=rebuild controller=id adisk=channelID:targetID
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to rebuild array disk 3 on channel 0 of controller 1, you would enter:
omconfig storage adisk action=rebuild controller=1 adisk=0:3
Use the following omconfig command syntax to cancel a rebuild that is in progress. If you cancel a rebuild, the virtual disk remains in a degraded state. For more information, see Cancel Rebuild.
omconfig storage adisk action=cancelrebuild controller=id adisk=channelID:targetID
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to cancel the rebuild of array disk 3 on channel 0 of controller 1, you would enter:
omconfig storage adisk action=cancelrebuild controller=1 adisk=0:3
Use the following omconfig command syntax to recover unusable disk space. See Remove Dead Segments for more information.
omconfig storage adisk action=removedeadsegments controller=id adisk=channelID:targetID
where "id" is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
For example, to remove dead disk segments on array disk 3 on channel 0 of controller 1, you would enter:
omconfig storage adisk action=removedeadsegments controller=1 adisk=0:3
The following sections provide the omconfig command syntax required to execute battery tasks.
|
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Documentation Section |
|---|---|---|
|
omconfig storage battery |
|
|
action=recondition controller=id battery=id |
Use the following omconfig command to recondition a controller battery. For more information on batteries and the recondition process, see RAID Controller Batteries and Battery Tasks: Recondition Battery.
omconfig storage battery action=recondition controller=id battery=id
where "id" is the controller ID and battery ID as reported by the omreport command. To obtain this value, you would 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.
For example, to recondition the battery on controller 1, you would enter:
omconfig storage battery action=recondition controller=1
The following sections provide the omconfig command syntax required to execute channel tasks.
|
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Documentation Section |
|---|---|---|
|
omconfig storage channel |
|
|
action=rescan controller=id channel=id |
Use the following omconfig command to rescan a controller channel. This command rescans all channels on the controller and is therefore similar to performing a controller rescan.
omconfig storage channel action=rescan controller=id channel=id
where "id" is the controller ID and the channel ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage channel controller=ID to display the IDs for the channels attached to the controller.
For example, to rescan channel 2 on controller 1, you would enter:
omconfig storage channel action=rescan controller=1 channel=2
The following sections provide the omconfig command syntax required to execute enclosure tasks.
Use the following omconfig command syntax to enable the enclosure alarm:
omconfig storage enclosure action=enablealarm controller=id enclosure=id
where "id" is the controller ID and enclosure ID as reported by the omreport command. To obtain these values, you would 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.
For example, to enable the alarm on enclosure 2 on controller 1, you would enter:
omconfig storage enclosure action=enablealarm controller=1 enclosure=2
Use the following omconfig command syntax to disable the enclosure alarm.
omconfig storage enclosure action=disablealarm controller=id enclosure=id
where "id" is the controller ID and enclosure ID as reported by the omreport command. To obtain these values, you would 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.
For example, to disable the alarm on enclosure 2 on controller 1, you would enter:
omconfig storage enclosure action=disablealarm controller=1 enclosure=2
By default, the operating system and server shut down when the PV220S and PV221S enclosures reach a critical temperature of 0 or 50 degrees celsius. If you have implemented channel redundancy on the PV220S and PV221S enclosures, however, 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 degrees celsius. See the Channel Redundancy and Thermal Shutdown section for more information.
|
Note: The omreport storage enclosure command does not display whether smart thermal shutdown is enabled or disabled. The status of smart thermal shutdown is displayed by the Server Administrator graphical user interface. To locate this status, select the Storage object and the Information/Configuration tab. See Storage Information and Global Tasks for more information. |
Use the following omconfig command syntax to enable smart thermal shutdown.
omconfig storage enclosure action=enablests
The omconfig command 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 enclosure action=enablests
If you have previously enabled smart thermal shutdown using the omconfig command, 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 will shut down when the PV220S and PV221S enclosures reach a critical temperature of 0 or 50 degrees celsius.
Use the following omconfig command syntax to disable smart thermal shutdown.
omconfig storage enclosure action=disablests
The omconfig command 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 enclosure action=disablests
|
Note: The omreport storage enclosure command does not display whether smart thermal shutdown is enabled or disabled. The status of smart thermal shutdown is displayed by the Server Administrator graphical user interface. To locate this status, select the Storage object and the Information/Configuration tab. See Storage Information and Global Tasks for more information. |
Use the following omconfig command syntax to specify the enclosure's asset tag:
omconfig storage enclosure action=setassettag controller=id enclosure=id assettag=<string>
where "id" is the controller ID and enclosure ID as reported by the omreport command. To obtain these values, you would 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.
In this syntax, <string> is a user-specified alphanumeric string.
For example, to specify the asset tag on enclosure 2 on controller 1 to encl20, you would enter:
omconfig storage enclosure action=setassettag controller=1 enclosure=2 assettag=encl20
Use the following omconfig command syntax to specify the asset name for an enclosure.
omconfig storage enclosure action=setassetname controller=id enclosure=id assetname=<string>
where "id" is the controller ID and enclosure ID as reported by the omreport command. To obtain these values, you would 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.
In this syntax, <string> is a user-specified alphanumeric string.
For example, to specify the asset name for enclosure 2 on controller 1 to encl43, you would enter:
omconfig storage enclosure action=setassetname controller=1 enclosure=2 assetname=encl43
Use the following omconfig command syntax to set the minimum and maximum warning temperature thresholds for a specified temperature probe.
omconfig storage enclosure action=settempprobes controller=id enclosure=id index=id minwarn=n maxwarn=n
where "id" is the controller ID, the enclosure ID, and the temperature probe ID as reported by the omreport command. To obtain these values, you would 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. To display the IDs for the enclosure components, enter omreport storage enclosure controller=ID enclosure ID.
In this syntax, "n" is a user-specified value for the temperature in celsius.
For example, you may want to specify the minimum and maximum warning thresholds for temperature probe 3 in enclosure 2 on controller 1. To set these thresholds to 10 celsius and 40 celsius you would enter:
omconfig storage enclosure action=settempprobes controller=1 enclosure=2 index=3 minwarn=10 maxwarn=40
Use the following omconfig command syntax to reset the minimum and maximum warning temperature thresholds back to their default values.
omconfig storage enclosure action=resettempprobes controller=id enclosure=id index=id
where "id" is the controller ID, the enclosure ID, and the temperature probe ID as reported by the omreport command. To obtain these values, you would 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. To display the IDs for the enclosure components, enter omreport storage enclosure controller=ID enclosure ID.
For example, you may want to reset the thresholds for temperature probe 3 in enclosure 2 on controller 1. To reset these thresholds you would enter:
omconfig storage enclosure action=reset controller=1 enclosure=2 index=3
Go to Table of Contents for Storage Management Online Help