The enhanced Server Administrator Storage Management Service component provides expanded options for the omreport and omconfig commands. This chapter only documents commands that are available when the Storage Management Service is installed. See the Dell OpenManage Server Administrator User's Guide for installation information.
CLI Command Syntax
The omreport and omconfig command syntax consists of specifying command "levels." The first command level is the command name: omreport or omconfig. Subsequent command levels provide a greater degree of specificity regarding the type of object on which the command will operate or the information that the command will display.
For example, the following omconfig command syntax has three levels:
omconfig storage adisk
The following table describes these command levels.
Table 11-1. Example Command Levels
Command level 1
Command level 2
Command level 3
Use
omconfig
Specifies the command
storage
Indicates the Server Administrator service (in this case, Storage Management) that implements the command
adisk
Specifies the type of object on which the command operates
Following the command levels, the omreport and omconfig command syntax may require one or more name=value pairs. The name=value pairs specify exact objects (such as a specific array disk) or options (such as "blink" or "unblink") that the command will implement.
For example, the following omconfig command syntax for blinking an array disk has three levels and three name=value pairs:
In some cases, the command syntax enables you to specify more than one target. In this case, the target IDs should be comma-separated without spaces. For example, to blink array disks 1, 2, and 3 on channel 2 and controller 1, you would enter:
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 11-2. Syntax For Name=Value Pairs For Parameters
Syntax
Description
controller=id
Indicates the controller ID as reported by the omreport storage controller command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=id to display the IDs for the array disks attached to the controller.
For example, the controller=id parameter might be specified as controller=1.
channel=id
Indicates the channel 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 channel controller=id to display the IDs for the channels attached to the controller.
For example, the channel=id parameter might be specified as channel=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=id
Indicates the enclosure 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 enclosure controller=id to display the IDs for the enclosures attached to the controller. To display the IDs for the enclosure components, enter omreport storage enclosure controller=id enclosure=id.
For example, the enclosure=id parameter might be specified as enclosure=2.
channelNo:targetID
Indicates a particular array disk by specifying the controller channel that the array disk is attached to and the array disk number.
For example, the channelNo:targetID parameter might be specified as 0:3.
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.
omreport Command
The following sections provide the omreport command syntax required to display the status of various storage components.
omreport High-level Storage Status
The following table provides the omreport command syntax required to display high-level storage status.
Table 11-3. omreport High-Level Storage Status Command
Required command levels (1 and 2)
Use
omreport storage
Displays high-level status for all controllers and attached components such as array disks, virtual disks, enclosures, fans, temperature probes, power supplies, and so on.
omreport Controller Status
Table 11-4. omreport Controller Commands
Required Command Levels (1, 2, 3)
Optional
name=value pairs
Use
omreport storage controller
Displays all controllers attached to the system.
controller=id
where id is the controller number. For example: controller=0
Displays the specified controller and all attached components such as enclosures, virtual disks, array disks, and so on.
omreport Battery Status
Table 11-5. omreport Battery Commands
Required Command Levels (1, 2, 3) and name=value pair
Use
omreport storage battery controller=id
where id is the controller number. For example: controller=0
Displays the battery on the specified controller.
omreport Channel Status
Table 11-6. omreport Channel Commands
Required Command Levels (1, 2, 3) and name=value pair
Use
omreport storage channel controller=id
where id is the controller number. For example: controller=0
Displays all channels on the specified controller.
omreport storage channel controller=id channel=id
where id is the controller number. For example: controller=0
Displays information for the specified channel on the controller.
omreport Enclosure Status
Table 11-7. omreport Enclosure Commands
Required Command Levels (1, 2, 3)
Optional
name=value pairs
Use
omreport storage enclosure
Displays all enclosures and their components such as fans, power supplies, and temperature probes.
controller=id enclosure=id
where id is the controller number and the enclosure number. For example: controller=0 enclosure=2
Displays the specified enclosure and its components.
omreport Array Disk Status
Table 11-8. omreport Array Disk Commands
Required Command Levels (1, 2, 3) and name=value pair
Optional
name=value pairs
Use
omreport storage adisk controller=id
where id is the controller number. For example: controller=0
Displays all array disks attached to the specified controller.
channel=id
where id is the channel number. For example: channel=1
Displays all array disks attached to the specified channel on the controller.
vdisk=id
where id is the virtual disk number. For example: vdisk=1
Displays all array disks included in the specified virtual disk on the controller.
adisk=channelID:targetID
where id is the channel and array disk number. For example: adisk=0:3
Displays the specified array disk on the specified channel on the controller.
omreport Virtual Disk Status
Table 11-9. omreport Virtual Disk Commands
Required Command Levels (1, 2, 3)
Optional
name=value pairs
Use
omreport storage vdisk
Displays all virtual disks on all controllers.
controller=id
where id is the controller number. For example: controller=0.
Displays all virtual disks on the specified controller.
controller=id vdisk=id
where id is the controller number and the virtual disk number. For example: controller=0 vdisk=1.
Displays the specified virtual disk on the controller.
omconfig 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.
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.
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:
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 which RAID levels a controller supports and also for general information about the RAID levels and concatentation. The following table indicates how to specify the raid=n parameter for each RAID level and concatenation.
Table 11-11. 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
size=<number | max | min> Parameter (Required)
The following table indicates how to specify the size=<number | max | min> parameter.
Table 11-12. Size Parameter
size=<number | max | min> Parameter Specification
Description
size=<n>
Use this specification to indicate a specific size for the virtual disk. The virtual disk size may be specified in K (kilobytes) or M (megabytes). For example, size=500m indicates that the virtual disk should be 500MB.
size=max
To create a virtual disk that is the maximum size possible, specify size=max. When creating a RAID 50 virtual disk, this parameter must be specified as size=max.
size=min
To create a virtual disk that is the minimum size possible, specify size=min.
Use this parameter to specify the array disks that will be included in the virtual disk. The channel:targetID element indicates an array disk by specifying the controller channel that the array disk is attached to and the array disk number. Repeat the channel:targetID element as many times as necessary to specify additional array disks. For example:
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 128KB as the stripe size, you would 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.
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.
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>] parameter for each of the write policies.
Use this parameter to specify a name for the virtual disk. For example:
name=VirtualDisk1
[spanlength=<n>] Parameter (Optional)
Use this parameter to specify the number of array disks to be included in each stripe. 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 500MB with a stripe size of 16KB. The name of the virtual disk will be vd1 and it will reside on channel 0 of controller 1. Because the virtual disk will be a RAID 5, it requires at least three array disks. In this example, you specify four array disks. These are array disks 0 through 3.
To create the virtual disk described in this example, you would enter:
The only parameters that require specification are for the controller, RAID level, virtual disk size, and array disk selection. The omconfig command supplies default values for all other unspecified parameters.
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 on controller 1 to 50, you would enter:
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.
By default, the log file is exported to the <install-directory>/sm directory where <install-directory> is the directory where you have installed Server Administrator.
Depending on the controller, the log file name will be either afa_<mmdd>.log or lsi_<mmdd>.log where <mmdd> is the month and date. For more information on the controller log file, see the online help.
NOTE: The Export Log File command is not supported on the PERC 2/SC, 2/DC, and CERC ATA 100/4ch
controllers.
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 11-16. omconfig Manage Virtual Disk Commands
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 blink the array disks in virtual disk 4 on controller 1, you would enter:
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 blink the array disks in virtual disk 4 on controller 1, you would enter:
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, 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 initialize virtual disk 4 on controller 1, you would enter:
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 cancel the initialization of virtual disk 4 on controller 1, you would enter:
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 cancel background initialization on virtual disk 4 on controller 1, you would enter:
Use the following omconfig command syntax to recover data from a RAID-5 virtual disk that has been corrupted. This task attempts to reconstruct data from a corrupt portion of an array disk included in a RAID-5 virtual disk.
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 restore segments on virtual disk 4 on controller 1, you would enter:
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, 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 initiate a split mirror on virtual disk 4 on controller 1, you would enter:
Use the following omconfig command syntax to separate mirrored data and restore one half of the mirror to free space. Unmirroring a RAID 1 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.
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 unmirror virtual disk 4 on controller 1, you would enter:
where id is the controller ID and virtual disk ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreportstorage vdisk controller=ID and omreport storage adisk controller=ID to display the IDs for the virtual disks and array disks attached to the controller.
Example Syntax
For example, to assign array disk 3 on channel 0 of controller 1 to virtual disk 4, you would enter:
You may want to assign more than one array disk as a dedicated hot spare. In this example, you want to assign array disk 3 on channel 0 and array disk 2 on channel 1 as dedicated hot spares:
where id is the controller ID and virtual disk ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID and omreport storage adisk controller=ID to display the IDs for the virtual disks and array disks attached to the controller.
Example Syntax
For example, to unassign array disk 3 on channel 0 of controller 1 to virtual disk 4, you would enter:
You can also unassign more than one array disks that have been assigned as hot spares. In this example, you want to unassign array disk 3 on channel 0 and array disk 2 on channel 1 as dedicated hot spares:
Use the following omconfig command syntax to initiate a check consistency on a virtual disk. The check consistency task verifies the virtual disk's redundant data.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, 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 run a check consistency on virtual disk 4 on controller 1, you would enter:
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 cancel a check consistency on virtual disk 4 on controller 1, you would enter:
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 pause a check consistency on virtual disk 4 on controller 1, you would enter:
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 resume a check consistency on virtual disk 4 on controller 1, you would enter:
Use the following omconfig command syntax to delete a virtual disk.
NOTICE: Deleting a virtual disk destroys all information including file systems and volumes residing on
the virtual disk. You may receive a warning message if you attempt to delete the system or boot partition.
However, this warning message is not generated in all circumstances. You should be certain that you are
not deleting the system or boot partition or other vital data when using this command.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, 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]
Example Syntax
For example, to delete virtual disk 4 on controller 1, you would enter:
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 format virtual disk 4 on controller 1, you would enter:
You can reconfigure a virtual disk in order to change the virtual disk's RAID level or increase its size by adding array disks. On some controllers, you can also remove array disks.
See the online help for information on specifying the parameters.
Example Syntax
For example, you wish to reconfigure virtual disk 4 to a size of 800MB. You will use RAID 5 and array disks 0 through 3 on channel 0 of controller 1. In this example, you would enter:
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 the online help. For information on how to specify these parameters using the omconfig command, see the following:
where id is the controller ID and virtual disk ID as reported by the omreport command and <string> is the new name for the virtual disk. To obtain the values for controller ID and virtual disk ID, 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 rename virtual disk 4 on controller 1 to vd4, you would enter:
You can blink the light (light emitting diode or LED display) on one or more array disks attached to a controller. Use the following omconfig command syntax to blink one or more array disks.
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreportstorage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to blink array disks 0 through 2 on channel 0 of controller 1, you would enter:
You unblink the light (light emitting diode or LED display) on one or more array disks attached to a controller. Use the following omconfig command syntax to unblink one or more array disks.
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to unblink array disks 0 through 2 on channel 0 of controller 1, you would enter:
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to prepare array disk 3 on channel 0 of controller 1 for removal, you would enter:
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to initialize array disk 3 on channel 0 of controller 1, you would enter:
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to offline array disk 3 on channel 0 of controller 1, you would enter:
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to bring array disk 3 on channel 0 of controller 1 back online, you would enter:
Use the following omconfig command syntax to assign an array disk as a global hot spare.
Complete Syntax
omconfig storage adisk action=assignglobalhotspare controller=
id adisk=channelID:targetID assign=yes
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to assign array disk 3 on channel 0 of controller 1 as a global hot spare, you would enter:
Use the following omconfig command syntax to unassign an array disk as a global hot spare.
Complete Syntax
omconfig storage adisk action=assignglobalhotspare controller=
id adisk=channelID:targetID assign=no
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to unassign array disk 3 on channel 0 of controller 1 as a global hot spare, you would enter:
Use the following omconfig command syntax to rebuild a failed array disk. Rebuilding a disk may take several hours. If you need to cancel the rebuild, use the Cancel Rebuild task. For more information, see the online help.
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to rebuild array disk 3 on channel 0 of controller 1, you would enter:
Use the following omconfig command syntax to recover unusable disk space. See the online help for more information.
Complete Syntax
omconfigs storage adisk action=removedeadsegments controller=
id adisk=channelID:targetID
where id is the controller ID and "channelID:targetID" is the channel number and array disk number as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage adisk controller=ID to display the IDs for the array disks attached to the controller.
Example Syntax
For example, to remove dead disk segments on array disk 3 on channel 0 of controller 1, you would enter:
The following sections provide the omconfig command syntax required to execute battery tasks.
Table 11-18. omconfig Battery Commands
Required Command Levels (1, 2, 3)
Optional
name=value pairs
omconfig storage battery
action=recondition controller=id battery=id
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.
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.
Example Syntax
For example, to recondition the battery on controller 1, you would enter:
The following sections provide the omconfig command syntax required to execute channel tasks.
Table 11-19. omconfig Channel Commands
Required Command Levels (1, 2, 3)
Optional
name=value pairs
omconfig storage channel
action=rescan controller=id channel=id
omconfig Rescan Channel
Use the following omconfig command to rescan a controller channel. This command rescans all channels on the controller and is therefore similar to performing a controller rescan.
where id is the controller ID and the channel ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage channel controller=ID to display the IDs for the channels attached to the controller.
Example Syntax
For example, to rescan channel 2 on controller 1, you would enter:
where id is the controller ID and enclosure ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage enclosure controller=ID to display the IDs for the enclosures attached to the controller.
Example Syntax
For example, to enable the alarm on enclosure 2 on controller 1, you would enter:
where id is the controller ID and enclosure ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage enclosure controller=ID to display the IDs for the enclosures attached to the controller.
Example Syntax
For example, to disable the alarm on enclosure 2 on controller 1, you would enter:
By default, the operating system and server shut down when the PV220S and PV221S enclosures reach a critical temperature of 0 or 50 degrees celsius. If you have implemented channel redundancy on the PV220S and PV221S enclosures, however, you can specify that only the enclosure and not the operating system and server be shut down when the enclosure reaches a critical temperature of 0 or 50 degrees celsius. See the online help for more information.
Use the following omconfig command syntax to enable smart thermal shutdown.
Complete Syntax
omconfig storage enclosure 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 enclosure action=enablests
omconfig 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 degrees celsius.
Use the following omconfig command syntax to disable smart thermal shutdown.
Complete Syntax
omconfig storage enclosure 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 enclosure action=disablests
omconfig Set Enclosure Asset Tag
Use the following omconfig command syntax to specify the enclosure's asset tag:
where id is the controller ID and enclosure ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage enclosure controller=ID to display the IDs for the enclosures attached to the controller.
In this syntax, <string> is a user-specified alphanumeric string.
Example Syntax
For example, to specify the asset tag on enclosure 2 on controller 1 to encl20, you would enter:
where id is the controller ID and enclosure ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage enclosure controller=ID to display the IDs for the enclosures attached to the controller.
In this syntax, <string> is a user-specified alphanumeric string.
Example Syntax
For example, to specify the asset name for enclosure 2 on controller 1 to encl43, you would enter:
where id is the controller ID, the enclosure ID, and the temperature probe ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage enclosure controller=ID to display the IDs for the enclosures attached to the controller. To display the IDs for the enclosure components, enter omreport storage enclosure controller=ID enclosure ID.
In this syntax, "n" is a user-specified value for the temperature in celsius.
Example Syntax
For example, you may want to specify the minimum and maximum warning thresholds for temperature probe 3 in enclosure 2 on controller 1. To set these thresholds to 10 celsius and 40 celsius you would enter:
Use the following omconfig command syntax to reset the minimum and maximum warning temperature thresholds back to their default values.
Complete Syntax
omconfig storage enclosure action=resettempprobes controller=
id enclosure=id index=id
where id is the controller ID, the enclosure ID, and the temperature probe ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage enclosure controller=ID to display the IDs for the enclosures attached to the controller. To display the IDs for the enclosure components, enter omreport storage enclosure controller=ID enclosure ID.
Example Syntax
For example, you may want to reset the thresholds for temperature probe 3 in enclosure 2 on controller 1. To reset these thresholds you would enter:
