Back to Storage Management Contents Page
Dell OpenManage Server Administrator 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
omconfig Physical 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.
When using the omreport and omconfig commands, you should understand how these commands are constructed. In particular you, you need to understand the following:
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 pdisk
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 physical disk) or options (such as blink or unblink) that the command will implement.
For example, the following omconfig command syntax for blinking a physical disk has three levels and three name=value pairs:
omconfig storage pdisk action=blink controller=id pdisk=<PDISKID>
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.
The omconfig syntax for specifying a physical disk includes the pdisk= parameter followed by the <PDISKID> variable. How you specify the <PDISKID> variable depends on whether the controller is using SCSI, SATA, ATA, or SAS technology.
On a SAS controller, the pdisk=<PDISKID> parameter is specified as follows. See "SAS RAID Controllers" for a list of the controllers using SAS technology.
pdisk=connector:enclosureID:portID
where connector is the number of the controller connector. The enclosureID variable is the number of the enclosure and portID variable is the number of the physical disk.
For example, assume that controller 1 is a SAS controller. To blink physical disk 1 in enclosure 3 on connector 2 and controller 1, you would enter:
omconfig storage pdisk action=blink controller=1 pdisk=2:3:1
On a SCSI, SATA, or ATA controller, the pdisk=<PDISKID> parameter is specified as follows. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
pdisk=connector:targetID
where connector is the number of the controller connector and targetID is the number of the physical disk.
For example, assume that controller 1 is a SCSI, SATA, or ATA controller. To blink physical disk 1 on connector 2 and controller 1, you would enter:
omconfig storage pdisk action=blink controller=1 pdisk=2:1
The omconfig syntax for specifying an enclosure includes the enclosure= parameter followed by the <ENCLOSUREID> variable. How you specify the <ENCLOSUREID> variable depends on whether the controller is using SCSI, SATA, ATA, or SAS technology.
On a SAS controller, the enclosure=<ENCLOSUREID> parameter is specified as follows. See "SAS RAID Controllers" for a list of the controllers using SAS technology.
enclosure=connector:enclosureID
where connector is the number of the controller connector and enclosureID is the number of the enclosure.
For example, assume that controller 1 is a SAS controller. To enable the alarm on enclosure 3 on connector 2, you would enter:
omconfig storage enclosure action=enablealarm controller=1 enclosure=2:3
On a SCSI, SATA, or ATA controller, the enclosure=<ENCLOSUREID> parameter is specified as follows. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
enclosure=connector
where connector is the number of the controller connector.
For example, assume that controller 1 is a SCSI, SATA, or ATA controller. To enable the alarm on the enclosure attached to connector 2, you would enter:
omconfig storage enclosure action=enablealarm controller=1 enclosure=2
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, if controller 1 is a SCSI, SATA, or ATA controller, then to blink physical disks 1, 2, and 3 on connector 2 you would enter:
omconfig storage pdisk action=blink controller=1 pdisk=2:1,2:2,2:3
If controller 1 is a SAS controller, then to blink physical disks 1, 2, and 3 on enclosure 3 and connector 2 you would enter:
omconfig storage pdisk action=blink controller=1 pdisk=2:3:1,2:3:2, 2:3:3
See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
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.
Syntax |
Description |
---|---|
controller=id | Indicates the controller ID as reported by the omreport storage controller command. 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, you would 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, 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 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, 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. See "enclosure=<ENCLOSUREID> Parameter" for more information. |
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), you would 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. See "pdisk=<PDISKID> Parameter" for more information. |
battery=id | Indicates the 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. |
< > | 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 to specify or not. 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. |
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.
Required Command Levels (1, 2, 3) |
Use |
---|---|
omreport storage -? | Displays a list of storage components for which omreport commands are available. |
omreport storage pdisk -? | Displays a list of the omreport storage pdisk parameters for displaying physical disk information. See "omreport Physical Disk Status" for more information. |
omreport storage vdisk -? | Displays a list of the omreport storage vdisk parameters for displaying virtual disk information. See "omreport Virtual Disk Status" for more information. |
omreport storage controller -? | Displays a list of the omreport storage controller parameters for displaying controller information. See "omreport Controller Status" for more information. |
omreport storage enclosure -? | Displays a list of the omreport storage enclosure parameters for displaying enclosure information. See "omreport Enclosure Status" for more information. |
omreport storage connector -? | Displays a list of the omreport storage connector parameters for displaying connector information. See "omreport Connector Status" for more information. |
omreport storage battery -? | Displays a list of the omreport storage battery parameters for displaying battery information. See "omreport Battery Status" for more information. |
omreport storage globalinfo -? | Displays a list of the omreport storage globalinfo parameters for displaying global storage property information. See "omreport Global Information (Smart Thermal Shutdown Status)" for more information. |
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Use |
---|---|---|
omreport storage globalinfo | Displays whether smart thermal shutdown is enabled or disabled. See "Channel Redundancy and Thermal Shutdown" and "omconfig Global Enable Smart Thermal Shutdown" for more information. |
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Use |
---|---|---|
omreport storage enclosure | Displays property information for all enclosures attached to the system. | |
controller=id enclosure=<ENCLOSUREID> where id is the controller number and <ENCLOSUREID> is the enclosure ID. Example for SCSI controllers: controller=0 enclosure=2. Example for SAS controllers: controller=0 enclosure=1:2. | Displays the specified enclosure and its components. See "enclosure=<ENCLOSUREID> Parameter" for more information on specifying enclosures. |
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Use |
---|---|---|
omreport storage enclosure | Displays property information for all enclosures attached to the system. | |
controller=id enclosure=<ENCLOSUREID> info=temps where id is the controller number and <ENCLOSUREID> is the enclosure ID. Example for SCSI controllers: controller=0 enclosure=2 info=temps. Example for SAS controllers: controller=0 enclosure=1:2 info=temps. | Displays the temperature probes for the specified enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information on specifying enclosures. | |
controller=id enclosure=<ENCLOSUREID> info=temps index=n where id is the controller number and <ENCLOSUREID> is the enclosure ID and n is the number of a temperature probe. Example for SCSI controllers: controller=0 enclosure=2 info=temps index=1. Example for SAS controllers: controller=0 enclosure=1:2 info=temps index=1. | Displays the specified temperature probe. See "enclosure=<ENCLOSUREID> Parameter" for more information on specifying enclosures. |
Required Command Levels (1, 2, 3) |
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 ID. Example for SCSI controllers: controller=0 enclosure=2 info=fans. Example for SAS controllers: controller=0 enclosure=1:2 info=fans. | Displays the fans for the specified enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information on specifying enclosures. | |
controller=id enclosure=<ENCLOSUREID> info=fans index=n where id is the controller number and <ENCLOSUREID> is the enclosure ID and n is the number of a fan. Example for SCSI controllers: controller=0 enclosure=2 info=fans index=1. Example for SAS controllers: controller=0 enclosure=1:2 info=fans index=1. | Displays the specified fan. See "enclosure=<ENCLOSUREID> Parameter" for more information on specifying enclosures. |
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Use |
---|---|---|
omreport storage enclosure | Displays property information for all enclosures attached to the system. | |
controller=id enclosure=<ENCLOSUREID> info=pwrsupplies where id is the controller number and <ENCLOSUREID> is the enclosure ID. Example for SCSI controllers: controller=0 enclosure=2 info=pwrsupplies. Example for SAS controllers: controller=0 enclosure=1:2 info=pwrsupplies. | Displays the power supplies for the specified enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information on specifying enclosures. | |
controller=id enclosure=<ENCLOSUREID> info=pwrsupplies index=n where id is the controller number and <ENCLOSUREID> is the enclosure ID and n is the number of a power supply. Example for SCSI controllers: controller=0 enclosure=2 info=pwrsupplies index=1. Example for SAS controllers: controller=0 enclosure=1:2 info=pwrsupplies index=1. | Displays the specified power supply. See "enclosure=<ENCLOSUREID> Parameter" for more information on specifying enclosures. |
Required Command Levels (1, 2, 3) |
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 ID. Example for SCSI controllers: controller=0 enclosure=2 info=emms. Example for SAS controllers: controller=0 enclosure=1:2 info=emms. | Displays the enclosure management modules (EMMs) for the specified enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information on specifying enclosures. | |
controller=id enclosure=<ENCLOSUREID> info=emms index=n where id is the controller number and <ENCLOSUREID> is the enclosure ID and n is the number of an EMM. Example for SCSI controllers: controller=0 enclosure=2 info=emms index=1. Example for SAS controllers: controller=0 enclosure=1:2 info=emms index=1. | Displays the specified EMM. See "enclosure=<ENCLOSUREID> Parameter" for more information on specifying enclosures. |
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. | |
pdisk=connector:targetID where connector is the connector number and targetID is the physical disk number. For example: pdisk=0:3 | Displays the specified physical disk on the specified connector on a SCSI, SATA, or ATA controller. | |
pdisk=connectorID:targetID|connectorID:enclosureID:slotID 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 and enclosure on a SAS controller. |
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. |
The following sections provide the omconfig command 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. See "Global Tasks" for more information.
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Documentation Section |
---|---|---|
omconfig storage globalinfo | ||
action=enablests | ||
action=disablests | ||
action=globalrescan |
By default, the operating system and server shut down when the PowerVault 220S and PowerVault 221S enclosures reach a critical temperature of 0 or 50 degrees Celsius. If you have implemented connector redundancy on the PowerVault 220S and PowerVault 221S 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. Specifying that only the enclosure be shutdown during excessive temperatures is known as smart thermal shutdown. See "Channel Redundancy and Thermal Shutdown" for more information.
Use the following omconfig command syntax to enable smart thermal shutdown.
omconfig storage globalinfo 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 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. To locate this status, select the Storage object and the Information/Configuration tab. See "Storage Information and Global Tasks" for more information. |
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 PowerVault 220S and PowerVault 221S enclosures reach a critical temperature of 0 or 50 degrees Celsius.
Use the following omconfig command syntax to disable smart thermal shutdown. This command will disable smart thermal shutdown for all controllers.
omconfig storage globalinfo 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 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 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 rescan all controllers on the system. See "Rescan Controller" and "Rescan to Update Storage Configuration Changes" for more information about using this command.
omconfig storage globalinfo action=globalrescan
The omconfig command 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 or SAS controllers. On non-RAID controllers, you must reboot the system before Storage Management can see configuration changes. |
The following sections provide the omconfig command syntax required to execute controller tasks.
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=rescan controller=1
![]() |
NOTE: Rescan Controller is not supported on non-RAID SCSI or SAS controllers. You must reboot the system before Storage Management can see configuration changes on non-RAID SCSI or SAS controllers. |
The omconfig storage controller action=globalrescan command was supported in previous releases of Storage Management. This command has been replaced by the omconfig storage globalinfo action=globalrescan command. When rescanning all controllers on the system and creating CLI scripts, it is preferable to use the omconfig storage globalinfo action=globalrescan command.
See "omconfig Global Rescan Controller" for more information.
Use the following omconfig command syntax to enable the controller alarm. See "Enable Alarm (Controller)" for more information.
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. See "Disable Alarm (Controller)" for more information.
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 when it is sounding. See "Quiet Alarm (Controller)" for more information.
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. See "Test Alarm (Controller)" for more information.
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.
![]() |
NOTICE: 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. |
![]() |
NOTE: Resetting the controller configuration does not remove a foreign configuration. To remove a foreign configuration, use the "omconfig Clear Foreign Configuration" command. See "Clear Foreign Configuration" for more information. |
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 "Considerations Before Creating Virtual Disks".
The omconfig syntax for creating a virtual disk has several parameters. You must specify the following parameters:
pdisk=connector:enclosureID:portID
or
pdisk=connector:targetID
See "pdisk=<PDISKID> Parameter" and "Multiple Targets" for more information on specifying physical disks.
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> pdisk=<PDISKID> [stripesize=< 2kb| 4kb| 8kb| 16kb| 32kb| 64kb| 128kb>] [cachepolicy=<d | c>] [readpolicy=<ra | nra | ara | rc| nrc>] [writepolicy=<wb| wt| wc| nwc | fwb>] [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.
where:
Use this parameter to specify the physical disks that will be 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 that were 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, you would 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. See "pdisk=<PDISKID> Parameter" and "Multiple Targets" for more information on specifying physical disks.
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.
Cache 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 | 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 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 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
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 "RAID Controller Read, Write, and Cache Policy". 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 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. On a SAS controller, the physical disks reside in enclosure 2.
The only parameters that require specification are for the controller, RAID level, virtual disk size, and physical disk selection. Storage Management supplies default values for all other unspecified parameters.
To create the virtual disk described in this example, you would enter:
omconfig storage controller action=createvdisk controller=1 raid=r5 size=500m pdisk=0:0,0:1,0:2,0:3 stripesize=16kb cachepolicy=c readpolicy=ra writepolicy=wt
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To create the virtual disk described in this example, you would enter:
omconfig storage controller action=createvdisk controller=1 raid=r5 size=500m pdisk=0:2:0,0:2:1,0:2:2,0:2:3 stripesize=16kb cachepolicy=c readpolicy=ra writepolicy=wt
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
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 set the background initialization rate. See "Set Background Initialization Rate" for more information.
omconfig storage controller action=setbgirate 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 background initialization rate on controller 1 to 50, you would enter:
omconfig storage controller action=setbgirate controller=1 rate=50
Use the following omconfig command syntax to set the reconstruct rate. See "Set Reconstruct Rate" for more information.
omconfig storage controller action=setreconstructrate 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 reconstruct rate on controller 1 to 50, you would enter:
omconfig storage controller action=setreconstructrate controller=1 rate= 50
Use the following omconfig command syntax to set the check consistency rate. See "Set Check Consistency Rate" for more information.
omconfig storage controller action=setcheckconsistency 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 check consistency rate on controller 1 to 50, you would enter:
omconfig storage controller action=setcheckconsistency 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
On a Microsoft® Windows® system, the log file is exported to the windows or winnt directory. On a Linux system, the log file is exported to the /var/log directory.
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 4/IM, CERC ATA100/4ch, and CERC SATA1.5/2s controllers. |
Use the following omconfig command syntax to import all virtual disks that reside on physical disks newly attached to the controller. See "Import Foreign Configuration" for more information.
omconfig storage controller action=importforeignconfig controller=id
where id is the controller ID as reported by the omreport storage controller command.
For example, to import foreign configurations on controller 1, you would enter:
omconfig storage controller action=importforeignconfig controller=1
Use the following omconfig command syntax to clear or delete all virtual disks that reside on physical disks that are newly attached to the controller. See "Clear Foreign Configuration" for more information.
omconfig storage controller action=clearforeignconfig controller=id
where id is the controller ID as reported by the omreport storage controller command.
For example, to clear foreign configurations on controller 1, you would enter:
omconfig storage controller action=clearforeignconfig controller=1
Use the following omconfig command syntax to set the patrol read mode for the controller. See "Set Patrol Read Mode" for more information.
omconfig storage controller action=setpatrolreadmode controller=id mode= manual|auto|disable
where id is the controller ID as reported by the omreport storage controller command.
For example, to set the patrol read on controller 1 to manual mode, you would enter:
omconfig storage controller action=setpatrolreadmode controller=1 mode= manual
Use the following omconfig command syntax to start the patrol read task on the controller. See "Start and Stop Patrol Read" for more information.
![]() |
NOTE: In order to start or stop the patrol read task, the patrol read mode should be set to Manual. See "Set Patrol Read Mode" for more information. |
omconfig storage controller action=startpatrolread controller=id
where id is the controller ID as reported by the omreport storage controller command.
For example, to start the patrol read task on controller 1, you would enter:
omconfig storage controller action=startpatrolread controller=1
Use the following omconfig command syntax to stop the patrol read task on the controller. See "Start and Stop Patrol Read" for more information.
omconfig storage controller action=stoppatrolread controller=id
where id is the controller ID as reported by the omreport storage controller command.
For example, to stop the patrol read task on controller 1, you would enter:
omconfig storage controller action=stoppatrolread controller=1
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. |
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=fastinit controller=id vdisk=id | ||
action=slowinit 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 pdisk=<PDISKID> 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> pdisk=<PDISKID> | ||
action=changepolicy controller=id vdisk=id [readpolicy=<ra | nra | ara | rc | nrc> | writepolicy=<wb | wt | wc | nwc | fwb> | cachepolicy=<d | c>] | ||
action=rename controller=id vdisk=id name=<string> |
Use the following omconfig command syntax to blink the physical 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 physical 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 physical 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 physical 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. See "Format and Initialize; Slow and Fast Initialize" for more information.
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 fast initialize a virtual disk. See "Format and Initialize; Slow and Fast Initialize" for more information.
omconfig storage vdisk action=fastinit 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 fast initialize virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=fastinit controller=1 vdisk=4
Use the following omconfig command syntax to slow initialize a virtual disk. See "Format and Initialize; Slow and Fast Initialize" for more information.
omconfig storage vdisk action=slowinit 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 slow initialize virtual disk 4 on controller 1, you would enter:
omconfig storage vdisk action=slowinit 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, and 4e/Di 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 a physical 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 nonredundant virtual disks. Splitting a RAID 10 mirror creates two RAID 0 (striped) nonredundant 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, nonredundant concatenated virtual disk. Unmirroring a RAID 10 virtual disk results in a single, nonredundant RAID 0 (striped) virtual disk. Data is not lost during this operation. See "Unmirror" for more information.
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 physical 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".
![]() |
NOTE: The CERC SATA1.5/2s controller does not support dedicated hot spares. |
omconfig storage vdisk action=assigndedicatedhotspare controller=id vdisk=id pdisk=<PDISKID> assign=yes
where id is the controller ID and virtual disk ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain the values for the controller, virtual disk and physical disk, you would 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.
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 SAS controller, the physical disk resides in enclosure 2.
To assign the dedicated hot spare described in this example, you would enter:
omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:3 assign=yes
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To assign the dedicated hot spare described in this example, you would enter:
omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:2:3 assign=yes
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command syntax to unassign one or more physical disks that were previously assigned as a hot spare to a virtual disk.
omconfig storage vdisk action=assigndedicatedhotspare controller=id vdisk=id pdisk=<PDISKID> assign=no
where id is the controller ID and virtual disk ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain the values for the controller, virtual disk and physical disk, you would 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.
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.
To unassign the dedicated hot spare described in this example, you would enter:
omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:3 assign=no
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To unassign the dedicated hot spare described in this example, you would enter:
omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:2:3 assign=no
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
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. See "Pause Check Consistency" for more information.
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.
![]() |
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. 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 physical disks. On some controllers, you can also remove physical 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> pdisk=<PDISK>
See "Parameter Specification for Create and Reconfigure Virtual Disk" for information on specifying the parameters. See "pdisk=<PDISKID> Parameter" and "Multiple Targets" for more information on specifying physical disks.
For example, you want to reconfigure virtual disk 4 to a size of 800MB. You will 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.
In this example, you would enter:
omconfig storage vdisk action=reconfigure controller=1 vdisk=4 raid=r5 size=800m pdisk=0:0,0:1,0:2,0:3
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
In this example, you would enter:
omconfig storage vdisk action=reconfigure controller=1 vdisk=4 raid=r5 pdisk=0:2:0,0:2:1,0:2:2,0:2:3
![]() |
NOTE: When using a SAS controller, the size parameter is not required. |
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
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 | fwb> | 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 physical disk tasks.
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Documentation Section |
---|---|---|
omconfig storage pdisk | ||
action=blink controller=id pdisk=<PDISKID> | ||
action=unblink controller=id pdisk=<PDISKID> | ||
action=remove controller=id pdisk=<PDISKID> | ||
action=initialize controller=id pdisk=<PDISKID> | ||
action=offline controller=id pdisk=<PDISKID> | ||
action=online controller=id pdisk=<PDISKID> | ||
action=assignglobalhotspare controller=id pdisk=<PDISKID> assign=<yes|no> | "omconfig Assign Global Hot Spare" and "omconfig Unassign Global Hot Spare" | |
action=rebuild controller=id pdisk=<PDISKID> | ||
action=cancelrebuild controller=id pdisk=<PDISKID> | ||
action=removedeadsegments controller=id pdisk=<PDISKID> | ||
action=clear controller=id pdisk=<PDISKID> | ||
action=cancelclear controller=id pdisk=<PDISKID> |
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.
omconfig storage pdisk action=blink controller=id pdisk=<PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
In this example, you want to blink physical disk 2 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
To blink the physical disk described in this example, you would enter:
omconfig storage pdisk action=blink controller=1 pdisk=0:2
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To blink the physical disk described in this example, you would enter:
omconfig storage pdisk action=blink controller=1 pdisk=0:2:2
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
You 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.
omconfig storage pdisk action=unblink controller=id pdisk=<PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
In this example, you want to unblink physical disk 2 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
To unblink the physical disk described in this example, you would enter:
omconfig storage pdisk action=unblink controller=1 pdisk=0:2
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To unblink the physical disk described in this example, you would enter:
omconfig storage pdisk action=unblink controller=1 pdisk=0:2:2
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command syntax to prepare a physical disk for removal. See "Prepare to Remove" for more information.
omconfig storage pdisk action=remove controller=id pdisk=<PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
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.
To prepare to remove the physical disk described in this example, you would enter:
omconfig storage pdisk action=remove controller=1 pdisk=0:3
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To prepare to remove the physical disk described in this example, you would enter:
omconfig storage pdisk action=remove controller=1 pdisk=0:2:3
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command syntax to initialize a physical disk.
omconfig storage pdisk action=initialize controller=id pdisk=<PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
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.
To initialize the physical disk described in this example, you would enter:
omconfig storage pdisk action=initialize controller=1 pdisk=0:3
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To initialize the physical disk described in this example, you would enter:
omconfig storage pdisk action=initialize controller=1 pdisk=0:2:3
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command syntax to offline a physical disk:
omconfig storage pdisk action=offline controller=id pdisk=<PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
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.
To offline the physical disk described in this example, you would enter:
omconfig storage pdisk action=offline controller=1 pdisk=0:3
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To offline the physical disk described in this example, you would enter:
omconfig storage pdisk action=offline controller=1 pdisk=0:2:3
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command syntax to bring an offline physical disk back online.
omconfig storage pdisk action=online controller=id pdisk=<PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
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.
To online the physical disk described in this example, you would enter:
omconfig storage pdisk action=online controller=1 pdisk=0:3
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To online the physical disk described in this example, you would enter:
omconfig storage pdisk action=online controller=1 pdisk=0:2:3
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command syntax to assign a physical disk as a global hot spare.
omconfig storage pdisk action=assignglobalhotspare controller=id pdisk= <PDISKID> assign=yes
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
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.
To assign the physical disk described in this example as a global hot spare, you would enter:
omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk= 0:3 assign=yes
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To assign the physical disk described in this example as a global hot spare, you would enter:
omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk= 0:2:3 assign=yes
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command syntax to unassign a physical disk as a global hot spare.
omconfig storage pdisk action=assignglobalhotspare controller=id pdisk= <PDISKID> assign=no
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
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.
To unassign the physical disk described in this example as a global hot spare, you would enter:
omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk= 0:3 assign=no
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To unassign the physical disk described in this example as a global hot spare, you would enter:
omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk= 0:2:3 assign=no
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
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 "omconfig Cancel Rebuild Physical Disk" task. For more information, see "Rebuild".
omconfig storage pdisk action=rebuild controller=id pdisk=<PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
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.
To rebuild the physical disk described in this example, you would enter:
omconfig storage pdisk action=rebuild controller=1 pdisk=0:3
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To rebuild the physical disk described in this example, you would enter:
omconfig storage pdisk action=rebuild controller=1 pdisk=0:2:3
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
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 pdisk action=cancelrebuild controller=id pdisk= <PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
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.
To cancel the rebuild of the physical disk described in this example, you would enter:
omconfig storage pdisk action=cancelrebuild controller=1 pdisk=0:3
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To cancel the rebuild of the physical disk described in this example, you would enter:
omconfig storage pdisk action=cancelrebuild controller=1 pdisk=0:2:3
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command syntax to recover unusable disk space. See "Remove Dead Segments" for more information.
omconfig storage pdisk action=removedeadsegments controller=id pdisk= <PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
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.
To remove dead segments on the physical disk described in this example, you would enter:
omconfig storage pdisk action=removedeadsegments controller=1 pdisk=0:3
See "pdisk=<PDISKID> Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To remove dead segments on the physical disk described in this example, you would enter:
omconfig storage pdisk action=removedeadsegments controller=1 pdisk= 0:2:3
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command to clear data or a configuration from a physical disk.
omconfig storage pdisk action=clear controller=id pdisk=<PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
In this example, you want to clear physical disk 3 on connector 0 of controller 1. The physical disk resides in enclosure 2. To clear the physical disk described in this example, you would enter:
omconfig storage pdisk action=clear controller=1 pdisk=0:2:3
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
Use the following omconfig command to cancel a clear operation that is in progress on a physical disk.
omconfig storage pdisk action=cancelclear controller=id pdisk=<PDISKID>
where id is the controller ID. The <PDISK> variable specifies the physical disk. See "pdisk=<PDISKID> Parameter" for more information.
To obtain these values, you would 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.
In this example, you want to cancel the clear of physical disk 3 on connector 0 of controller 1. The physical disk resides in enclosure 2. To cancel the clear of the physical disk described in this example, you would enter:
omconfig storage pdisk action=cancelclear controller=1 pdisk=0:2:3
See "pdisk=<PDISKID> Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
The following sections provide the omconfig command syntax required to execute battery tasks.
Use the following omconfig command to recondition a controller battery. For more information on batteries and the recondition process, see "RAID Controller Batteries" and "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 battery 0 on controller 1, you would enter:
omconfig storage battery action=recondition controller=1 battery=0
Use the following omconfig command to start the battery learn cycle.
omconfig storage battery action=startlearn 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 start the learn cycle on controller 1, you would enter:
omconfig storage battery action=startlearn controller=1 battery=0
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. See "Battery Delay Learn Cycle" for more information.
omconfig storage battery action=delaylearn controller=id battery=id days=d hours=h
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 delay the learn cycle for three days and 12 hours on controller 1, you would enter:
omconfig storage battery action=delaylearn controller=1 battery=0 days=3 hours=12
The following sections provide the omconfig command syntax required to execute connector tasks.
Required Command Levels (1, 2, 3) |
Optional name=value Pairs |
Documentation Section |
---|---|---|
omconfig storage connector | ||
action=rescan controller=id connector=id |
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.
omconfig storage connector action=rescan controller=id connector=id
where id is the controller ID and the connector 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 connector controller=ID to display the IDs for the connectors attached to the controller.
For example, to rescan connector 2 on controller 1, you would enter:
omconfig storage connector action=rescan controller=1 connector=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= <ENCLOSUREID>
where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information.
For example, to enable the alarm on the enclosure attached to connector 2 on controller 1, you would enter:
omconfig storage enclosure action=enablealarm controller=1 enclosure=2
See "enclosure=<ENCLOSUREID> Parameter on SCSI, SATA, and ATA Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
For example, to enable the alarm on enclosure 3 attached to connector 0 on controller 1, you would enter:
omconfig storage enclosure action=enablealarm controller=1 enclosure=0:3
See "enclosure=<ENCLOSUREID> Parameter on SAS Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
Use the following omconfig command syntax to disable the enclosure alarm.
omconfig storage enclosure action=disablealarm controller=id enclosure= <ENCLOSUREID>
where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information.
For example, to disable the alarm on the enclosure attached to connector 2 on controller 1, you would enter:
omconfig storage enclosure action=disablealarm controller=1 enclosure=2
See "enclosure=<ENCLOSUREID> Parameter on SCSI, SATA, and ATA Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
For example, to disable the alarm on enclosure 3 attached to connector 0 on controller 1, you would enter:
omconfig storage enclosure action=disablealarm controller=1 enclosure= 0:3
See "enclosure=<ENCLOSUREID> Parameter on SAS Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
The omconfig storage enclosure action=enablests command was supported in previous releases of Storage Management. This command has been replaced by the omconfig storage globalinfo action=enablests command. When enabling smart thermal shutdown and creating CLI scripts, it is preferable to use the omconfig storage globalinfo action=enablests command.
See "omconfig Global Enable Smart Thermal Shutdown" and "Channel Redundancy and Thermal Shutdown" for more information.
The omconfig storage enclosure action=disablests command was supported in previous releases of Storage Management. This command has been replaced by the omconfig storage globalinfo action=disablests command. When disabling smart thermal shutdown and creating CLI scripts, it is preferable to use the omconfig storage globalinfo action=disablests command.
See "omconfig Global Disable Smart Thermal Shutdown" and "Channel Redundancy and Thermal Shutdown" for more information.
Use the following omconfig command syntax to specify the enclosure's asset tag:
omconfig storage enclosure action=setassettag controller=id enclosure= <ENCLOSUREID> assettag=<string>
where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information.
In this syntax, <string> is a user-specified alphanumeric string.
For example, to specify the asset tag on the enclosure attached to connector 2 on controller 1 to encl20, you would enter:
omconfig storage enclosure action=setassettag controller=1 enclosure=2 assettag=encl20
See "enclosure=<ENCLOSUREID> Parameter on SCSI, SATA, and ATA Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
For example, to specify the asset tag on enclosure 3 attached to connector 0 on controller 1 to encl20, you would enter:
omconfig storage enclosure action=setassettag controller=1 enclosure=0:3 assettag=encl20
See "enclosure=<ENCLOSUREID> Parameter on SAS Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
Use the following omconfig command syntax to specify the asset name for an enclosure.
omconfig storage enclosure action=setassetname controller=id enclosure= <ENCLOSUREID> assetname=<string>
where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information.
In this syntax, <string> is a user-specified alphanumeric string.
For example, to specify the asset name for the enclosure attached to connector 2 on controller 1 to encl43, you would enter:
omconfig storage enclosure action=setassetname controller=1 enclosure=2 assetname=encl43
See "enclosure=<ENCLOSUREID> Parameter on SCSI, SATA, and ATA Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
For example, to specify the asset name for enclosure 3 attached to connector 0 on controller 1 to encl43, you would enter:
omconfig storage enclosure action=setassetname controller=1 enclosure= 0:3 assetname=encl43
See "enclosure=<ENCLOSUREID> Parameter on SAS Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
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= <ENCLOSUREID> index=id minwarn=n maxwarn=n
where id is the controller ID and the temperature probe ID. The <ENCLOSUREID> variable specifies the enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information.
In this syntax, n is a user-specified value for the temperature in Celsius.
In this example, you want to set the thresholds for temperature probe 3. Temperature probe 3 resides in the enclosure attached to connector 2 on controller 1. To set the temperature probe 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
See "enclosure=<ENCLOSUREID> Parameter on SCSI, SATA, and ATA Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
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=<ENCLOSUREID> index=id
where id is the controller ID and the temperature probe ID. The <ENCLOSUREID> variable specifies the enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information.
In this example, you want to reset the thresholds for temperature probe 3 to the default values. 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, you would enter:
omconfig storage enclosure action=resettempprobes controller=1 enclosure=2 index=3
See "enclosure=<ENCLOSUREID> Parameter on SCSI, SATA, and ATA Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
Use the following omconfig command syntax to set the minimum and maximum warning temperature thresholds for all temperature probes in the enclosure.
omconfig storage enclosure action=setalltempprobes controller=id enclosure=<ENCLOSUREID> minwarn=n maxwarn=n
where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information.
In this example, the temperature probes reside in enclosure 3 attached to connector 0 on controller 1. To set the thresholds for all temperature probes to 10 Celsius and 40, you would enter:
omconfig storage enclosure action=setalltempprobes controller=1 enclosure=0:3 minwarn=10 maxwarn=40
See "enclosure=<ENCLOSUREID> Parameter on SAS Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
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.
omconfig storage enclosure action=resetalltempprobes controller=id enclosure=<ENCLOSUREID>
where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information.
For example, you may want to reset the thresholds for all temperature probes in enclosure 2 on controller 1.
In this example, the temperature probes reside in enclosure 3 attached to connector 0 on controller 1. To reset the thresholds for all temperature probes, you would enter:
omconfig storage enclosure action=resetalltempprobes controller=1 enclosure=0:3
See "enclosure=<ENCLOSUREID> Parameter on SAS Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
Use the following omconfig command to blink the light-emitting diodes (LEDs) on the enclosure.
omconfig storage enclosure action=blink controller=id enclosure= <ENCLOSUREID>
where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure. See "enclosure=<ENCLOSUREID> Parameter" for more information.
For example, to blink the LEDs for the enclosure attached to connector 2 on controller 1, you would enter:
omconfig storage enclosure action=blink controller=1 enclosure=2
See "enclosure=<ENCLOSUREID> Parameter on SCSI, SATA, and ATA Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
For example, to blink the LEDs for enclosure 3 attached to connector 0 on controller 1, you would enter:
omconfig storage enclosure action=blink controller=1 enclosure=0:3
See "enclosure=<ENCLOSUREID> Parameter on SAS Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
Back to Storage Management Contents Page