Back to Contents Page

Using the Storage Management Service

Dell™ OpenManage™ Server Administrator Version 5.2 Command Line Interface User's Guide

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. This chapter only documents the omreport and omconfig commands that apply to Storage Management. See the Dell OpenManage Installation and Security User's Guide for installation information. See the Storage Management online help and Dell OpenManage Server Administrator Storage Management User's Guide for more information on Storage Management.

CLI Command Syntax

Like all the 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.

Table 8-1. Example 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.

Syntax for Required, Optional, and Variable Command Elements

The omreport and omconfig commands have multiple name=value pairs. These name=value pairs may include required, optional, and variable parameters. The following table describes the syntax used to indicate these parameters.

Table 8-2. Syntax For Name=Value Pairs For Parameters 

User Privileges for omreport storage and omconfig storage

Storage Management requires Administrator privileges to use the omconfig storage command. User and Power User privileges are sufficient to use the omreport storage command.

omreport Command

The following sections provide the omreport command syntax required to display the status of various storage components.

omreport Storage Help

The following table provides the omreport storage command syntax.

Table 8-3. omreport storage help 

omreport Controller Status

Table 8-4. omreport Controller Commands 

omreport Global Information (Smart Thermal Shutdown Status)

Table 8-5. omreport Global Information Commands

omreport Battery Status

Table 8-6. omreport Battery Commands 

omreport Connector Status

Table 8-7. omreport Connector Commands 

omreport Enclosure Status

Table 8-8. omreport Enclosure Commands 

omreport Temperature Probe Status

Table 8-9. omreport Temperature Probe Commands

omreport Fan Status

Table 8-10. omreport Fan Status 

omreport Power Supply Status

Table 8-11. omreport Power Supply Commands 

omreport EMM Status

Table 8-12. omreport EMM Commands 

omreport Physical Disk Status

Table 8-13. omreport Physical Disk Commands 

omreport Virtual Disk Status

Table 8-14. omreport Virtual Disk Commands 

omconfig Global Commands

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.

Table 8-15. omconfig Global Commands 

omconfig Global Enable Smart Thermal Shutdown

By default, the operating system and server shut down when the PV220S and PV221S enclosures reach a critical temperature of 0 or 50° Celsius. If you have implemented connector 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° Celsius. Specifying that only the enclosure be shutdown during excessive temperatures is known as Smart Thermal Shutdown. See the online help for more information.

Use the following omconfig command syntax to enable smart thermal shutdown.

Complete Syntax

omconfig storage globalinfo action=enablests

Example Syntax

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.

omconfig Global Disable Smart Thermal Shutdown

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° Celsius.

Use the following omconfig command syntax to disable smart thermal shutdown. This command will disable smart thermal shutdown for all controllers.

Complete Syntax

omconfig storage globalinfo action=disablests

Example Syntax

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.

omconfig Global Rescan Controller

Use the following omconfig command syntax to rescan all controllers on the system. See the online help for more information about using this command.

Complete Syntax

omconfig storage globalinfo action=globalrescan

Example Syntax

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 and SAS controllers. You must reboot the system before Storage Management can see configuration changes on non-RAID SCSI controllers.

omconfig Controller Commands

The following sections provide the omconfig command syntax required to execute controller tasks.

NOTICE: The omconfig storage controller action=resetconfig controller=id resets the controller configuration. Resetting the controller configuration permanently destroys all data on all virtual disks attached to the controller. If the system or boot partition resides on these virtual disks, it will be destroyed.

Table 8-16. omconfig Controller Commands 

omconfig Rescan Controller

Use the following omconfig command syntax to rescan a controller. See the online help for more information about using this command.

Complete Syntax

omconfig storage controller action=rescan controller=id

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to rescan controller 1, enter:

omconfig storage controller action=rescan controller=1

NOTE: The rescan controller is not supported on non–RAID SCSI and SAS controllers. You must reboot the system before Storage Management can see configuration changes on non-RAID SCSI controllers.

omconfig Global Rescan Controller

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 the online help for more information about using this command.

omconfig Enable Controller Alarm

Use the following omconfig command syntax to enable the controller alarm. See the online help for more information about using this command.

Complete Syntax

omconfig storage controller action=enablealarm controller=id

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to enable the alarm on controller 1, enter:

omconfig storage controller action=enablealarm controller=1

omconfig Disable Controller Alarm

Use the following omconfig command syntax to disable the controller alarm. See the online help for more information about using this command.

Complete Syntax

omconfig storage controller action=disablealarm controller=id

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to disable the alarm on controller 1, enter:

omconfig storage controller action=disablealarm controller=1

omconfig Quiet Controller Alarm

Use the following omconfig command syntax to silence an activated controller alarm. See the online help for more information about using this command.

Complete Syntax

omconfig storage controller action=quietalarm controller=id

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to quiet the alarm on controller 1, enter:

omconfig storage controller action=quietalarm controller=1

omconfig Test Controller Alarm

Use the following omconfig command syntax to test the functionality of the controller alarm. The alarm will sound for about two seconds. See the online help for more information about using this command.

Complete Syntax

omconfig storage controller action=testalarm controller=id

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to test the alarm on controller 1, enter:

omconfig storage controller action=testalarm controller=1

omconfig Reset Controller Configuration

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.

Complete Syntax

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

Example Syntax

For example, to reset the configuration on controller 1, enter:

omconfig storage controller action=resetconfig controller=1

omconfig Create Virtual Disk

The online help provides additional information about creating virtual disks.

The omconfig syntax for creating a virtual disk has several parameters. You must specify the following parameters:

• Controller (controller=id)
  
  
• RAID level (raid=<c| r0| r1| r1c| r5| r10| r50>)
  
  
• Size (size=<number | max | min>)
  
  
• Physical disk is specified as either:
  
  

pdisk=connector:enclosureID:portID

or

pdisk=connector:targetID

Storage Management supplies default values for any of the other parameters that you do not specify.

Complete Syntax

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>]

Parameter Specification for Create and Reconfigure Virtual Disk

The following sections indicate how to specify the omconfig storage controller action=createvdisk parameters.

controller=id Parameter (Required)

raid=<c| r0| r1| r1c| r5| r10| r50> Parameter (Required)

size=<number | max | min> Parameter (Required)

pdisk=<connector:targetID,connector:targetID,.....> Parameter (Required)

[stripesize=< 2kb| 4kb| 8kb| 16kb| 32kb| 64kb| 128kb>] Parameter (Optional)

[cachepolicy=<d | c>] Parameter (Optional)

[readpolicy=<ra| nra| ara| rc| nrc>] Parameter (Optional)

[writepolicy=<wb| wt| wc| nwc | fwb>] Parameter (Optional)

[name=<string>] Parameter (Optional)

[spanlength=<n>] Parameter (Optional)

controller=id Parameter (Required)

Specify the controller ID as reported by the omreport storage controller command. For example:

controller=2

raid=<c| r0| r1| r1c| r5| r10| r50> Parameter (Required)

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 the online help for information on the RAID levels a controller supports and for general information about RAID levels and concatenation. The following table indicates how to specify the raid=n parameter for each RAID level and concatenation.

Table 8-17. Raid Level and Concatenation 

size=<number | max | min> Parameter (Required)

The following table indicates how to specify the size=<number | max | min> parameter.

Table 8-18. Size Parameter

PDISKID=<connector:enclosureID:portID | connector:targetID>

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.

stripesize=< 2kb| 4kb| 8kb| 16kb| 32kb| 64kb| 128kb>] Parameter (Optional)

Different controllers support different stripe sizes. See the online help for information on which stripe sizes are supported for a controller. All stripe sizes are specified in kilobytes. For example, when specifying 128 KB as the stripe size, enter:

stripesize=128kb

[cachepolicy=<d | c>] Parameter (Optional)

Different controllers support different cache policies. See the online help for more information. The following table indicates how to specify the [cachepolicy=<d | c>] parameter for each of the cache policies.

Table 8-19. Cache Policy Parameters 

[readpolicy=<ra| nra| ara| rc| nrc>] Parameter (Optional)

Different controllers support different read policies. See the online help for more information. The following table indicates how to specify the [readpolicy=<ra| nra| ara| rc| nrc>] parameter for each of the read policies.

Table 8-20. Read Policy Paramaters 

[writepolicy=<wb| wt| wc| nwc>] Parameter (Optional)

Different controllers support different write policies. See the online help for more information. The following table indicates how to specify the [writepolicy=<wb| wt| wc| nwc | fwb>] parameter for each of the write policies.

Table 8-21. Write Policy Parameters 

[name=<string>] Parameter (Optional)

Use this parameter to specify a name for the virtual disk. For example:

name=VirtualDisk1

NOTE: The CERC SATA 1.5/2s controller does not allow you to specify a virtual disk name. The virtual disk will be created with a default name.

[spanlength=<n>] Parameter (Required for RAID 50)

Use this parameter to specify the number of physical disks to be included in each stripe. This parameter only applies to RAID 50 virtual disks. If you are not creating a RAID 50 virtual disk, do not specify this parameter. For example:

spanlength=3

Example Syntax

For example, you may want to create a RAID 5 virtual disk on a PERC 3/QC controller. The online help will help you understand which read, write, and cache policies are supported by this controller. In this example, you decide to create a virtual disk with the following read, write, and cache policy:

• Read-ahead
  
  
• Write–through caching
  
  
• Cache I/O
  
  

The virtual disk will be 500 MB with a stripe size of 16 KB. The name of the virtual disk will be vd1 and it will reside on connector 0 of controller 1. Because the virtual disk will be a RAID 5, it requires at least three physical disks. In this example, you specify four physical disks. These are physical disks 0 through 3.

To create the virtual disk described in this example, enter:

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

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.

omconfig Set Controller Rebuild Rate

Use the following omconfig command syntax to set the controller rebuild rate:

Complete Syntax

omconfig storage controller action=setrebuildrate controller=id rate=<0 to 100>

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to set the rebuild rate to 50 on controller 1, enter:

omconfig storage controller action=setrebuildrate controller=1 rate=50

omconfig Set Background Initialization Rate

Use the following omconfig command syntax to set the background initialization rate.

Complete Syntax

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.

Example Syntax

For example, to set the background initialization rate to 50 on controller 1, enter:

omconfig storage controller action=setbgirate controller=1 rate=50

omconfig Set Reconstruct Rate

Use the following omconfig command syntax to set the reconstruct rate.

Complete Syntax

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.

Example Syntax

For example, to set the reconstruct rate to 50 on controller 1, enter:

omconfig storage controller action=setreconstructrate controller=1

rate=50

omconfig Set Check Consistency Rate

Use the following omconfig command syntax to set the check consistency rate.

Complete Syntax

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.

Example Syntax

For example, to set the check consistency rate to 50 on controller 1, enter:

omconfig storage controller action=setcheckconsistency controller=1

rate=50

omconfig Export the Controller Log

Use the following omconfig command syntax to export the controller log to a text file. For more information about the exported log file, see the online help.

Complete Syntax

omconfig storage controller action=exportlog controller=id

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to export the log on controller 1, enter:

omconfig storage controller action=exportlog controller=1

By default, the log file is exported to C:\WinNt or C:\Windows for Microsoft® Windows® systems (based on the Windows version used) and /var/log on all Linux systems.

Depending on the controller, the log file name will 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 the online help.

NOTE: The export log file command is not supported on the PERC 2/SC, 2/DC, 4/IM, CERC ATA 100/4ch, and CERC SATA 1.5/2s controllers.

omconfig Import Foreign Configuration

Use the following omconfig command syntax to import all virtual disks that reside on physical disks newly attached to the controller.

Complete Syntax

omconfig storage controller action=importforeignconfig controller=id

where id is the controller ID as reported by the omreport storage controller command.

NOTE: This command is supported only in firmware version 5.0.x.

Example Syntax

For example, to import foreign configurations on controller 1, enter:

omconfig storage controller action=importforeignconfig controller=1

omconfig Import/Recover Foreign Configuration

Use the following omconfig command syntax to import and recover all virtual disks that reside on physical disks newly attached to the controller.

Complete Syntax

omconfig storage controller action=importrecoverforeignconfig controller=id

where id is the controller ID as reported by the omreport storage controller command.

NOTE: This command is supported only in firmware version 5.1.1.

Example Syntax

For example, to import and recover foreign configurations on controller 1, enter:

omconfig storage controller action=importrecoverforeignconfig controller=1

omconfig Clear Foreign Configuration

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.

Complete Syntax

omconfig storage controller action=clearforeignconfig controller=id

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to clear foreign configurations on controller 1, enter:

omconfig storage controller action=clearforeignconfig controller=1

omconfig Set Patrol Read Mode

Use the following omconfig command syntax to set the patrol read mode for the controller.

Complete Syntax

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.

Example Syntax

For example, to set the patrol read on controller 1 to manual mode, enter:

omconfig storage controller action=setpatrolreadmode controller=1

mode=manual

omconfig Start Patrol Read

Use the following omconfig command syntax to start the patrol read task on the controller.

Complete Syntax

omconfig storage controller action=startpatrolread controller=id

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to start the patrol read task on controller 1, enter:

omconfig storage controller action=startpatrolread controller=1

NOTE: To be able to start patrol read, the current patrol read mode should be set to "Manual."

omconfig Stop Patrol Read

Use the following omconfig command syntax to stop the patrol read task on the controller.

Complete Syntax

omconfig storage controller action=stoppatrolread controller=id

where id is the controller ID as reported by the omreport storage controller command.

Example Syntax

For example, to stop the patrol read task on controller 1, enter:

omconfig storage controller action=stoppatrolread controller=1

NOTE: To be able to stop patrol read, the current patrol read mode should be set to "Manual."

omconfig Virtual Disk Commands

The following sections provide the omconfig command syntax required to execute virtual disk tasks.

NOTICE: The omconfig storage vdisk action=deletevdisk controller=id vdisk=id command deletes a virtual disk. Deleting a virtual disk destroys all information including file systems and volumes residing on the virtual disk.

Table 8-22. omconfig Manage Virtual Disk Commands 

omconfig Blink Virtual Disk

Use the following omconfig command syntax to blink the physical disks included in a virtual disk.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to blink the physical disks in virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=blink controller=1 vdisk=4

omconfig Unblink Virtual Disk

Use the following omconfig command syntax to unblink the physical disks included in a virtual disk.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to blink the physical disks in virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=unblink controller=1 vdisk=4

omconfig Initialize Virtual Disk

Use the following omconfig command syntax to initialize a virtual disk.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to initialize virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=initialize controller=1 vdisk=4

omconfig Cancel Initialize Virtual Disk

Use the following omconfig command syntax to cancel the initialization of a virtual disk.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to cancel the initialization of virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=cancelinitialize controller=1 vdisk=4

omconfig Fast Initialize Virtual Disk

Use the following omconfig command syntax to fast initialize a virtual disk.

Complete Syntax

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.

Example Syntax

For example, to fast initialize virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=fastinit controller=1 vdisk=4

omconfig Slow Initialize Virtualize Disk

Use the following omconfig command syntax to slow initialize a virtual disk.

Complete Syntax

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.

Example Syntax

For example, to slow initialize virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=slowinit controller=1 vdisk=4

omconfig Cancel Background Initialize

Use the following omconfig command syntax to cancel the background initialization process on a virtual disk.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to cancel background initialization on virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=cancelbginitialize controller=1 vdisk=4

omconfig Restore Dead Segments

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.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to restore segments on virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=restoresegments controller=1 vdisk=4

omconfig Split Mirror

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.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to initiate a split mirror on virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=splitmirror controller=1 vdisk=4

omconfig Unmirror

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 the online help for more information about using this command.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to unmirror virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=unmirror controller=1 vdisk=4

omconfig Assign Dedicated Hot Spare

Use the following omconfig command syntax to assign one or more physical disks to a virtual disk as a dedicated hot spare.

NOTE: The PERC 2/SC, 2/DC, and CERC SATA 1.5/2s controllers do not support dedicated hot spares.

Complete Syntax

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.

To obtain the values for the controller, virtual disk, and physical disk, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID and omreport storage pdisk controller=ID to display the IDs for the virtual disks and physical disks attached to the controller.

Example Syntax

In this example, you are assigning physical disk 3 on connector 0 of controller 1 as a dedicated hot spare to virtual disk 4. On a Serial Attached SCSI (SAS) controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To assign the dedicated hot spare described in this example, enter:

omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:3 assign=yes

Example for SAS Controllers:

To assign the dedicated hot spare described in this example, enter:

omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:2:3 assign=yes

omconfig Unassign Dedicated Hot Spare

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.

Complete Syntax

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.

To obtain the values for the controller, virtual disk, and physical disk, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID and omreport storage pdisk controller=ID to display the IDs for the virtual disks and physical disks attached to the controller.

Example Syntax

In this example, you are unassigning physical disk 3 on connector 0 of controller 1 as a dedicated hot spare to virtual disk 4. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To unassign the dedicated hot spare described in this example, enter:

omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:3 assign=no

Example for SAS Controllers:

To unassign the dedicated hot spare described in this example, enter:

omconfig storage vdisk action=assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:2:3 assign=no

omconfig Check Consistency

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.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to run a check consistency on virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=checkconsistency controller=1 vdisk=4

omconfig Cancel Check Consistency

Use the following omconfig command syntax to cancel a check consistency while it is in progress.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to cancel a check consistency on virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=cancelcheckconsistency controller=1 vdisk=4

omconfig Pause Check Consistency

Use the following omconfig command syntax to pause a check consistency while it is in progress. See the online help for more information.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to pause a check consistency on virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=pausecheckconsistency controller=1 vdisk=4

omconfig Resume Check Consistency

Use the following omconfig command syntax to resume a check consistency after it has been paused.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to resume a check consistency on virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=resumecheckconsistency controller=1 vdisk=4

omconfig Delete Virtual Disk

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.

Complete Syntax

omconfig storage vdisk action=deletevdisk controller=id vdisk=id

wwon=deletevdisk controller=1 vdisk=4

omconfig Format Virtual Disk

Use the following omconfig command syntax to format a virtual disk.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to format virtual disk 4 on controller 1, enter:

omconfig storage vdisk action=format controller=1 vdisk=4

omconfig Reconfiguring Virtual Disks

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.

Complete Syntax

omconfig storage vdisk action=reconfigure controller=id vdisk=id raid=<c| r0| r1| r1c| r5| r10> size=<size> pdisk=<PDISK>

Example Syntax

For example, to reconfigure virtual disk 4 to a size of 800 MB, use RAID 5 and physical disks 0 through 3 on connector 0 of controller 1. On a SAS controller, the physical disks reside in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

In this example, enter:

omconfig storage vdisk action=reconfigure controller=1 vdisk=4 raid=r5 size=800m pdisk=0:0,0:1,0:2,0:3

Example for SAS Controllers:

In this example, 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

omconfig Change Virtual Disk Policy

Use the following omconfig command syntax to change a virtual disk's read, write, or cache policy.

Complete Syntax

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, 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 the online help. For information on how to specify these parameters using the omconfig command, see the following:

• [readpolicy=<ra| nra| ara| rc| nrc>] Parameter (Optional)
  
  
• [writepolicy=<wb| wt| wc| nwc | fwb>] Parameter (Optional)
  
  
• [cachepolicy=<d | c>] Parameter (Optional)
  
  

Example Syntax

For example, to change the read policy of virtual disk 4 on controller 1 to no-read-ahead, enter:

omconfig storage vdisk action=changepolicy controller=1 vdisk=4 readpolicy=nra

omconfig Rename Virtual Disk

Use the following omconfig command syntax to rename a virtual disk.

NOTE: On a CERC SATA 1.5/2s controller, you cannot change the default name of a virtual disk.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.

Example Syntax

For example, to rename virtual disk 4 on controller 1 to vd4, enter:

omconfig storage vdisk action=rename controller=1 vdisk=4 name=vd4

omconfig Physical Disk Commands

The following sections provide the omconfig command syntax required to execute physical disk tasks.

Table 8-23. omconfig Physical Disk Commands 

omconfig Blink Physical Disk

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.

Complete Syntax

action=blink controller=ID action=blink controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to blink physical disk 0 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To blink the physical disk described in this example, enter:

omconfig storage pdisk action=blink controller=1 pdisk=0:0

Example for SAS Controllers:

To blink the physical disk described in this example, enter:

omconfig storage pdisk action=blink controller=1 pdisk=0:2:0

omconfig Unblink Physical Disk

You can unblink the light (light emitting diode or LED display) on one or more physical disks attached to a controller. Use the following omconfig command syntax to unblink one or more physical disks.

Complete Syntax

omconfig storage pdisk action=unblink controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to unblink physical disk 0 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To unblink the physical disk described in this example, enter:

omconfig storage pdisk action=unblink controller=1 pdisk=0:0

Example for SAS Controllers:

To unblink the physical disk described in this example, enter:

omconfig storage pdisk action=unblink controller=1 pdisk=0:2:0

omconfig Prepare to Remove Physical Disk

Use the following omconfig command syntax to prepare a physical disk for removal:

Complete Syntax

omconfig storage pdisk action=remove controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to prepare physical disk 3 on connector 0 of controller 1 for removal. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To prepare to remove the physical disk described in this example, enter:

omconfig storage pdisk action=remove controller=1 pdisk=0:3

Example for SAS Controllers:

To prepare to remove the physical disk described in this example, enter:

omconfig storage pdisk action=remove controller=1 pdisk=0:2:3

omconfig Initialize Physical Disk

Use the following omconfig command syntax to initialize a physical disk.

Complete Syntax

omconfig storage pdisk action=initialize controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to initialize physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To initialize the physical disk described in this example, enter:

omconfig storage pdisk action=initialize controller=1 pdisk=0:3

Example for SAS Controllers:

To initialize the physical disk described in this example, enter:

omconfig storage pdisk action=initialize controller=1 pdisk=0:2:3

omconfig Offline Physical Disk

Use the following omconfig command syntax to offline a physical disk:

Complete Syntax

omconfig storage pdisk action=offline controller=id pdisk=connectorID:targetID

where id is the controller ID and connectorID:targetID is the connector number and physical disk number as reported by the omreport command. To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

For example, to offline physical disk 3 on connector 0 of controller 1, enter:

omconfig storage pdisk action=offline controller=1 pdisk=0:3

omconfig Offline Physical Disk

Use the following omconfig command syntax to offline a physical disk:

Complete Syntax

omconfig storage pdisk action=offline controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to offline physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To offline the physical disk described in this example, enter:

omconfig storage pdisk action=offline controller=1 pdisk=0:3

Example for SAS Controllers:

To offline the physical disk described in this example, enter:

omconfig storage pdisk action=offline controller=1 pdisk=0:2:3

omconfig Online Physical Disk

Use the following omconfig command syntax to bring an offline physical disk back online.

Complete Syntax

omconfig storage pdisk action=online controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

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.

Example Syntax

In this example, you want to bring physical disk 3 on connector 0 of controller 1 back online. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To bring the physical disk described in this example back online, enter:

omconfig storage pdisk action=online controller=1 pdisk=0:3

Example for SAS Controllers:

To bring the physical disk described in this example back online, enter:

omconfig storage pdisk action=online controller=1 pdisk=0:2:3

omconfig Assign Global Hot Spare

Use the following omconfig command syntax to assign a physical disk as a global hot spare.

Complete Syntax

omconfig storage pdisk action=assignglobalhotspare controller=id pdisk=<PDISKID> assign=yes

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to assign physical disk 3 on connector 0 of controller 1 as a global hot spare. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To assign the physical disk described in this example as a global hot spare, enter:

omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk=0:3 assign=yes

Example for SAS Controllers:

To assign the physical disk described in this example as a global hot spare, enter:

omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk=0:2:3 assign=yes

omconfig Unassign Global Hot Spare

Use the following omconfig command syntax to unassign a physical disk as a global hot spare.

Complete Syntax

omconfig storage pdisk action=assignglobalhotspare controller=id pdisk=<PDISKID> assign=no

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to unassign physical disk 3 on connector 0 of controller 1 as a global hot spare. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To unassign the physical disk described in this example as a global hot spare, enter:

omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk=0:3 assign=no

Example for SAS Controllers:

To unassign the physical disk described in this example as a global hot spare, enter:

omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk=0:2:3 assign=no

omconfig Rebuild Physical Disk

Use the following omconfig command syntax to rebuild a failed physical disk. Rebuilding a disk may take several hours. If you need to cancel the rebuild, use the Cancel Rebuild task. For more information, see the online help.

Complete Syntax

omconfig storage pdisk action=rebuild controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to rebuild physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To rebuild the physical disk described in this example, enter:

omconfig storage pdisk action=rebuild controller=1 pdisk=0:3

Example for SAS Controllers:

To rebuild the physical disk described in this example, enter:

omconfig storage pdisk action=rebuild controller=1 pdisk=0:2:3

omconfig Cancel Rebuild Physical Disk

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. See the online help for more information.

Complete Syntax

omconfig storage pdisk action=cancelrebuild controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to cancel the rebuild or physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To cancel the rebuild of the physical disk described in this example, enter:

omconfig storage pdisk action=cancelrebuild controller=1 pdisk=0:3

Example for SAS Controllers:

To cancel the rebuild of the physical disk described in this example, enter:

omconfig storage pdisk action=cancelrebuild controller=1 pdisk=0:2:3

omconfig Remove Dead Segments

Use the following omconfig command syntax to recover unusable disk space. See the online help for more information.

Complete Syntax

omconfig storage pdisk action=removedeadsegments controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to remove dead disk segments on physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.

Example for SCSI, SATA, and ATA Controllers:

To remove dead segments on the physical disk described in this example, enter:

omconfig storage pdisk action=removedeadsegments controller=1 pdisk=0:3

Example for SAS Controllers:

To remove dead segments on the physical disk described in this example, enter:

omconfig storage pdisk action=removedeadsegments controller=1 pdisk=0:2:3

omconfig Clear Physical Disk

Use the following omconfig command to clear data or a configuration from a physical disk.

Complete Syntax

omconfig storage pdisk action=clear controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to clear physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.

Example for SAS Controllers:

To clear the physical disk described in this example, you would enter:

omconfig storage pdisk action=clear controller=1 pdisk=0:2:3

omconfig Cancel Clear Physical Disk

Use the following omconfig command to cancel a clear operation that is in progress on a physical disk.

Complete Syntax

omconfig storage pdisk action=cancelclear controller=id pdisk=<PDISKID>

where id is the controller ID. The <PDISK> variable specifies the physical disk.

To obtain these values, enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.

Example Syntax

In this example, you want to cancel the clear of physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.

Example for SAS Controllers:

To cancel the clear of the physical disk described in this example, enter:

omconfig storage pdisk action=cancelclear controller=1 pdisk=0:2:3

omconfig Battery Commands

The following sections provide the omconfig command syntax required to execute battery tasks.

Table 8-24. omconfig Battery Commands 

omconfig Recondition Battery

Use the following omconfig command to recondition a controller battery. For more information on batteries and the recondition process, see the online help.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage battery controller=ID to display the ID for the controller battery.

Example Syntax

For example, to recondition the battery on controller 1, enter:

omconfig storage battery action=recondition controller=1 battery=0

omconfig Start Battery Learn Cycle

Use the following omconfig command to start the battery learn cycle.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage battery controller=ID to display the ID for the controller battery.

Example Syntax

For example, to start the learn cycle on controller 1, enter:

omconfig storage battery action=startlearn controller=1 battery=0

omconfig Delay Battery Learn Cycle

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.

Complete Syntax

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, enter omreport storage controller to display the controller IDs and then enter omreport storage battery controller=ID to display the ID for the controller battery.

Example Syntax

For example, to delay the learn cycle for three days and 12 hours on controller 1, enter:

omconfig storage battery action=delaylearn controller=1 battery=0

days=3 hours=12

omconfig Connector Commands

The following sections provide the omconfig command syntax required to execute connector tasks.

Table 8-25. omconfig Connector Commands 

omconfig Rescan Connector

Use the following omconfig command to rescan a controller connector. This command rescans all connectors on the controller and is therefore similar to performing a controller rescan.

NOTE: This command is not supported on SAS controllers.

Complete Syntax

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, 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.

Example Syntax

For example, to rescan connector 2 on controller 1, enter:

omconfig storage connector action=rescan controller=1 connector=2

omconfig Enclosure Commands

The following sections provide the omconfig command syntax required to execute enclosure tasks.

Table 8-26. omconfig Enclosure Commands 

omconfig Enable Enclosure Alarm

Use the following omconfig command syntax to enable the enclosure alarm:

Complete Syntax

omconfig storage enclosure action=enablealarm controller=id enclosure=<ENCLOSUREID>

where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure.

Example for SCSI, SATA, and ATA Controllers:

For example, to enable the alarm on the enclosure attached to connector 2 on controller 1, enter:

omconfig storage enclosure action=enablealarm controller=1 enclosure=2

Example for SAS Controllers:

For example, to enable the alarm on enclosure 2 attached to connector 1 on controller 1, enter:

omconfig storage enclosure action=enablealarm controller=1 enclosure=1:2

omconfig Disable Enclosure Alarm

Use the following omconfig command syntax to disable the enclosure alarm.

Complete Syntax

omconfig storage enclosure action=disablealarm controller=id enclosure=<ENCLOSUREID>

where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure.

Example for SCSI, SATA, and ATA Controllers:

For example, to disable the alarm on the enclosure attached to connector 2 on controller 1, enter:

omconfig storage enclosure action=disablealarm controller=1 enclosure=2

Example for SAS Controllers:

For example, to disable the alarm on enclosure 2 attached to connector 1 on controller 1, enter:

omconfig storage enclosure action=disablealarm controller=1 enclosure=1:2

omconfig Enable Smart Thermal Shutdown

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 the "omconfig Global Enable Smart Thermal Shutdown" command for more information.

omconfig Disable Smart Thermal Shutdown

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 the "omconfig Global Disable Smart Thermal Shutdown" command for more information.

omconfig Set Enclosure Asset Tag

Use the following omconfig command syntax to specify the enclosure's asset tag:

Complete Syntax

omconfig storage enclosure action=setassettag controller=id enclosure=<ENCLOSUREID> assettag=<string>

where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure.

In this syntax, <string> is a user-specified alphanumeric string.

Example for SCSI, SATA, and ATA Controllers:

For example, to specify the asset tag to encl20 on the enclosure attached to connector 2 on controller 1, enter:

omconfig storage enclosure action=setassettag controller=1 enclosure=2 assettag=encl20

Example for SAS Controllers:

For example, to specify the asset tag to encl20 on enclosure 2 attached to connector 1 on controller 1, enter:

omconfig storage enclosure action=setassettag controller=1 enclosure=1:2 assettag=encl20

omconfig Set Enclosure Asset Name

Use the following omconfig command syntax to specify the asset name for an enclosure.

Complete Syntax

omconfig storage enclosure action=setassetname controller=id enclosure=<ENCLOSUREID> assetname=<string>

where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure.

In this syntax, <string> is a user-specified alphanumeric string.

Example for SCSI, SATA, and ATA Controllers:

For example, to specify the asset name to encl43 for the enclosure attached to connector 2 on controller 1, enter:

omconfig storage enclosure action=setassetname controller=1 enclosure=2 assetname=encl43

Example for SAS Controllers:

For example, to specify the asset name to encl43 for enclosure 2 attached to connector 1 on controller 1, enter:

omconfig storage enclosure action=setassetname controller=1 enclosure=1:2 assetname=encl43

omconfig Set Temperature Probe Thresholds

Use the following omconfig command syntax to set the minimum and maximum warning temperature thresholds for a specified temperature probe.

NOTE: This command is not supported on SAS controllers.

Complete Syntax

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.

In this syntax, "n" is a user-specified value for the temperature in Celsius.

Example Syntax

For example, you may want to specify the minimum and maximum warning thresholds for temperature probe 3 to 10 and 40° Celsius.

Example for SCSI, SATA, and ATA Controllers:

In this example, temperature probe 3 resides in the enclosure attached to connector 2 on controller 1. To set the temperature probe thresholds to 10 and 40° Celsius, enter:

omconfig storage enclosure action=settempprobes controller=1 enclosure=2 index=3 minwarn=10 maxwarn=40

omconfig Reset Temperature Probe Thresholds

Use the following omconfig command syntax to reset the minimum and maximum warning temperature thresholds back to their default values.

NOTE: This command is not supported on SAS controllers.

Complete Syntax

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.

Example Syntax

For example, you may want to reset the thresholds for temperature probe 3 to the default values.

Example for SCSI, SATA, and ATA Controllers:

In this example, temperature probe 3 resides in the enclosure attached to connector 2 on controller 1. To reset the thresholds for temperature probe 3 to the default values, enter:

omconfig storage enclosure action=resettempprobes controller=1 enclosure=2 index=3

omconfig Set All Temperature Probe Thresholds

Use the following omconfig command syntax to set the minimum and maximum warning temperature thresholds for all temperature probes in the enclosure.

NOTE: This command is not supported on SCSI RAID controllers.

Complete Syntax

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.

Example Syntax

For example, you may want to specify the minimum and maximum warning thresholds for all temperature probes to 10 and 40° Celsius.

Example for SAS Controllers

In this example, the temperature probes reside in enclosure 3 attached to connector 2 on controller 1. To set the thresholds for all temperature probes to 10 and 40° Celsius, enter:

omconfig storage enclosure action=setalltempprobes controller=1 enclosure=2:3 minwarn=10 maxwarn=40

omconfig Reset All Temperature Probe Thresholds

Use the following omconfig command syntax to reset the minimum and maximum warning temperature thresholds back to their default value for all temperature probes in the enclosure.

NOTE: This command is not supported on SCSI RAID controllers.

Complete Syntax

omconfig storage enclosure action=resetalltempprobes controller=id enclosure=<ENCLOSUREID>

where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure.

Example Syntax

For example, you may want to reset the thresholds for all temperature probes in enclosure 2 on controller 1.

Example for SAS Controllers

In this example, the temperature probes reside in enclosure 3 attached to connector 2 on controller 1. To reset the thresholds for all temperature probes, enter:

omconfig storage enclosure action=resetalltempprobes controller=1 enclosure=2:3

omconfig Blink

Use the following omconfig command to blink the light-emitting diodes (LEDs) on the enclosure.

Complete Syntax

omconfig storage enclosure action=blink controller=id enclosure=<ENCLOSUREID>

where id is the controller ID. The <ENCLOSUREID> variable specifies the enclosure.

Example for SCSI, SATA, and ATA Controllers:

For example, to blink the LEDs for the enclosure attached to connector 2 on controller 1, enter:

omconfig storage enclosure action=blink controller=1 enclosure=2

Example for SAS Controllers:

For example, to blink the LEDs for enclosure 3 attached to connector 2 on controller 1, enter:

omconfig storage enclosure action=blink controller=1 enclosure=2:3

Back to Contents Page