Dell OpenManage™ Server Administrator Version 2.3 Command Line Interface User's Guide w w w. d e l l . c o m | s u p p o r t . d e l l .
Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2005 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 What's New for Version 2.3 Using CLI Commands from Windows Command Prompts . Primary CLI Commands . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 CLI Error Checking and Error Messages. Success Messages . Failure Messages . . . . . . . . . . . . . . . . . . . . . . 13 . . . . . . . . . . . . . . . . . . . . .
omdiag storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . omdiag storage -? . . . . . . omdiag storage cddvd . . . omdiag storage floppy . . . omdiag storage idedevdiag . omdiag storage raidctrl . . . omdiag storage sasdevdiag omdiag storage scsidevdiag omdiag system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 . . . . . . . . . . . . . . .
omreport chassis pwrsupplies omreport chassis slots . . . . omreport chassis temps . . . omreport chassis volts . . . . omreport system Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 53 53 54 . . . . . . . . . . . . . . . . . . . . . . . . . . 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . omreport system . . . . . . . . . Commands for Viewing Logs . . . omreport system alertaction . . .
. . . . . . . . . . . . . . . . . . . . . . . 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Help With the omconfig Command omconfig about . omconfig chassis omconfig chassis biossetup . . omconfig chassis bmc . . . . . omconfig chassis currents . . . omconfig chassis fans . . . . . omconfig chassis fancontrol . . omconfig chassis frontpanel . . omconfig chassis info. . . . . . omconfig chassis leds . . . . .
Adding Depreciation Information . . . . . . . . . . . . . . . . . . . . . . . Example Commands for Adding Depreciation Information . Adding Extended Warranty Information . 113 . . . . . . . . . . . . . . . . . . . 114 Example Command for Adding Extended Warranty Information . Adding Lease Information . . . . 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 . . . . . . . . . . . . 115 . . . . . . . . . . . . . . . . . . . . . . . 116 . . . . . . . . 116 . . . . . . . . . . . . .
omreport Storage Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . omreport Controller Status . . . . . . . . . . . . . . . . . . . . omreport Global Information (Smart Thermal Shutdown Status) omreport Battery Status . . . . . . . . . . . . . . . . . . . . . omreport Connector Status . . . . . . . . . . . . . . . . . . . . omreport Enclosure Status . . . . . . . . . . . . . . . . . . . . omreport Temperature Probe Status . . . . . . . . . . . . . . . omreport Fan Status . . . . . . . . . . .
omconfig Virtual Disk Commands . . . . . . . . . . . . . . . . . . . . . . . omconfig Blink Virtual Disk . . . . . . . . omconfig Unblink Virtual Disk . . . . . . omconfig Initialize Virtual Disk . . . . . . omconfig Cancel Initialize Virtual Disk . . omconfig Fast Initialize Virtual Disk . . . omconfig Slow Initialize Virtualize Disk . omconfig Cancel Background Initialize . omconfig Restore Dead Segments . . . . omconfig Split Mirror . . . . . . . . . . . omconfig Unmirror . . . . . . . . . . . .
omconfig Battery Commands . . . . . . . . . . . . . . . . . . . . . . . . . omconfig Recondition Battery . . . omconfig Start Battery Learn Cycle omconfig Delay Battery Learn Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 166 166 omconfig Connector Commands . . . . . . . . . . . . . . . . . . . . . . . . 167 omconfig Rescan Connector . . . . . . . . . . . . . . . . . . . . . . . 167 omconfig Enclosure Commands . . . . . . . . . . . . . . . . . . . . . . . .
Introduction Whether you are using the graphical user interface (GUI) or the command line interface (CLI), Server Administrator performs essential systems management tasks. The reporting and viewing features allow retrieval of overall health status for systems on your network. At the component level, you can view information about the voltages, temperatures, current, fan RPM, memory functioning, and many other critical component details.
Primary CLI Commands The commands that carry out the functions of Server Administrator are: • omconfig • omdiag • omhelp • omreport The omconfig command writes values that you assign to an object's properties. You can specify values for warning thresholds on components or prescribe what action your system is to take when a certain warning or failure event occurs.
NOTE: Omupdate commands are no longer supported in Server Administrator and are replaced by Dell Update Package or Server Update Utility commands. To update the different components, download the Dell Update Package and run /s [/f]. See the Dell Update Packages for Microsoft® Windows® Operating Systems User’s Guide, the Dell Update Packages for Red Hat® Enterprise Linux User’s Guide, or the Server Update Utility User’s Guide for more information on corresponding CLI syntax.
Failure Messages CLI failure messages provide reasons why some commands do not succeed. Some common reasons why commands fail include syntax errors and components that are not present. Many error messages provide syntax information that you can use to execute the command successfully. If you try to execute a command for a component or feature that is not present in your system configuration, the error message states that the component is not present.
Scripting and Comparing With the CLI The Server Administrator CLI allows administrators to write batch programs or scripts to be executed by the operating system. For an enterprise with many systems, an administrator could write a configuration script that specified the warning thresholds for each major component of a system and also specified a set of actions that the administrator wants each system to take in case of a warning or failure event.
Some commands have command level 1 and command level 2 and one name=value pair. Consider the following example command that instructs Server Administrator for more details about the environment for Server Administrator: omreport about details=true Command level 1 is omreport, command level 2 is about, and the name=value pair is details=true. Many commands use command level 1, command level 2, and command level 3, but do not require any parameters (name=value pairs). Most omreport commands are of this type.
omhelp: Getting Help With CLI Commands The omhelp command and its equivalent, -?, accesses the CLI's detailed help text interface. You can get help at several levels of detail. Each fully qualified CLI command may have a variable number of distinct parts: the command (command level 1), one or more subcommands (command level 2 and command level 3, if present), and one or more name=value pair(s). By appending -? (space-dash-question mark) to any command, you can get help on the command.
Figure 2-1. Different Levels of Help for a Command You can also parse the omconfig system assetinfo command as follows: [name=value pair 2] where command levels 1, 2, and 3 are represented by omconfig system assetinfo, name=value pair 1 is represented by info=depreciation, and name=value pair 2 is represented by method=straightline.
omdiag: Using the Diagnostic Service The omdiag command allows you to test chassis and storage components such as hard drives, physical memory, communications and printer ports, NICs, CMOS, and more. Most tests described in this section take less than one minute. Some test can take longer depending on the device being tested. You cannot abort tests you start through the command line interface.
Table 3-1. Command level 1 omdiag Command Level 1, Level 2, and Level 3 (continued) Command level 2 Command level 3 system any level 3 command for chassis or storage name=value pair Use Runs the test for specified chassis or storage component. passes= Runs a test n time(s). time= Runs a test for the specified number of minutes . quicktest= Uses a faster algorithm to conduct a specific test if one is available.
Table 3-1. Command level 1 omdiag Command Level 1, Level 2, and Level 3 (continued) Command level 2 Command level 3 name=value pair storage cddvd Runs the CD/DVD drive test. floppy Runs the diskette drive test. raidctrl Runs the RAID control and attached device test. idedevdiag Runs the IDE disk tests. sasdevdiag Runs Serial Attached SCSI (SAS), SAS RAID controller, and attached device tests. scsidevdiag Use Runs the SCSI controller and attached tape and hard drive tests.
omdiag about details=true Use the omdiag about details=true command to see information about all of the Server Administrator programs that are installed. The following is example output from the omdiag about details=true command: Product name : Server Administrator Version : 2.x.x Copyright : Copyright (C) Dell Inc. 1995-2005. All rights reserved. Company : Dell Inc. Contains : Instrumentation Service 5.x.x Storage Management Service 3.x.x Diagnostic Service 3.x.x Sun JRE - OEM Installed Version 1.x.
omdiag chassis memory Use the omdiag chassis memory command to test the system's RAM. The following test is performed: NOTE: Shut down all other programs before running this test. NOTE: Sufficient swap-space (temporary storage space used during a move or reconfiguration) is needed to support the demands of the memory test. NOTE: This test checks only memory seen by the operating system on systems that have redundant memory support (spare bank or mirroring).
– S-Registers Test — Uses the selected range of S-Registers to exercise and diagnose the functionality of the modem. The test saves the current S-register values, sets a new value, verifies that the new value can be read and is correct, and restores the original value. The result codes are verified and displayed either textually or numerically. NOTE: In cases where the Windows registry with modem drivers is corrupted due to bad installs/uninstalls, the modem diagnostic might give unexpected results.
• The following tests are available on Dell supported Broadcom NICs: – BRCMNetwork Control Registers Test — Tests most of the internal registers on the chip. Each chip contains many internal registers. Each register can contain some read-only bits and some read/write bits. This diagnostic tests read-only bits that cannot be overwritten, and tests if read/write bits can be written properly. – BRCMNetwork MII Registers Test — Tests most MII registers on the chip. Each chip contains many MII registers.
NOTE: The following tests are only available on systems running a supported Microsoft Windows operating system. – Intel Control Registers Test — Checks for any conflicts in the I/O address and tests the accessibility of the registers. This test includes all General Registers, Receive Registers, and Transmit Registers. It does not test the EEPROM Control/Data Register. – Intel EEPROM Test — Verifies the integrity of data read from the EEPROM.
– FIFO Test Mode (test mode to determine FIFO depth) – Configuration Mode (cnfgX registers are available) NOTE: The Mode test may disrupt normal operation of a device connected to the parallel port, for example, a printer that is printing. • Parallel Port Register Test — Tests the parallel port registers using a write-read strategy, for example, writing some data into the register, reading the data of the same registry and verifying it against the data written (data-pattern, walking-bit).
omdiag chassis rac Use the omdiag chassis rac command to run the tests on the remote access controller (RAC). The RAC test provides IT administrators with continuous access to their systems, enabling a full range of systems management functions including monitoring, controlling, updating, and recovering. The RAC can be connected to a PCI expansion slot or embedded on the system board. DRAC III and above are enumerated and tested, whereas DRAC II is only enumerated, but not tested.
omdiag chassis usbctrl Use the omdiag chassis usbctrl command to test the USB controller(s). The USB test performs the following test: NOTE: The following test is available on systems running supported Microsoft Windows and Red Hat Enterprise Linux (version 3) and later operating systems. NOTE: On systems running supported Red Hat Enterprise Linux operating systems, connecting or removing a USB device from the server while the diagnostics enumeration is in progress, may cause the system to hang.
The CD/DVD drive test performs the following tests: • Extremity Test — Conducts negative testing on the drive. The drive is requested to execute illegal commands to access particular extreme sectors or play illegal lists. The test is expected to fail. • Driver Mechanism Test — Performs the eject, close, and stop actions to determine if the drive servo mechanism, the door motor, and the spindle motor are operating correctly.
• Extremity Test — Attempts to access sectors beyond the range and confirms the error received. • Read-Write Test — Targets an appropriate number of sectors. The data on each of these sectors is read into a buffer where it is stored until it is restored. The algorithm then writes a stream of roving data onto each sector. It then returns to the first designated sector and reads back the data to confirm the data integrity. After this, the original data is restored.
You must stop an application that reserves the RAID controller before you attempt to run the Adaptec RAID controller diagnostic test or the hard disk diagnostic test. If you do not, the diagnostic reports a failure with the following message: An application or service that manipulates RAID such as Array Manager, FAST, or PERC Console has reserved the controller and must be stopped before running this test.
The diagnostics resume when the hard drive I/O activity has decreased. If the following message appears: Device Inquiry command failed it is likely that the hard drive is not connected properly. Check the cables to ensure that the hard drive is properly connected to the controller. The hard drive may also fail and display the following message: Device failed a send diagnostic command: Check cable connections and termination and run this test again.
omdiag storage scsidevdiag Use the omdiag storage scsidevdiag command to test the SCSI controller, connected hard drives, and tape devices. This test performs the following tests: • SCSI Channel Communication Test — Ensures that the SCSI subsystem between the controller and connected device is intact. This test is only available if the controller has devices connected to it.
• SCSI Tape Library/Changer Tests — Performs several tests on a SCSI tape library or changer, which is connected to a SCSI controller channel using a SCSI cable. Appropriate SCSI controller and tape changer or library drives must be installed for the tape changer or library to be enumerated. The following tests are performed on a SCSI tape library or changer: – Tape Device Self Test — Initially verifies the communication path from the host to the tape drive.
omdiag: Using the Diagnostic Service
omreport: Viewing System Status Using the Instrumentation Service The omreport command allows you to see detailed information about your system components. You can retrieve summaries for many system components at one time, or you can get details about a specific component. This chapter shows you how to get reports with the level of detail that you want. Commands documented in this chapter vary in whether they define the fields that appear in the results of a particular omreport command.
Table 4-1 is a high-level summary of the omreport command. The column titled "Command level 1" shows the omreport command at its most general. "Command level 2" shows the major objects or components that you can view using omreport (about, chassis, storage, system, and rac). "Command level 3" lists the specific objects and components for which you can view reports. "User privilege required" refers to the type of privilege you need to perform the command, where U=User, P=Power User, and A= Administrator.
Table 4-1. Command level 1 omreport Command Level 1, Level 2, and Level 3 (continued) Command Command level 2 level 3 User privilege required Use fru U, P, A Shows the Field Replaceable Unit (FRU) information. info U, P, A Shows a status summary for main system chassis components. intrusion U, P, A Shows the status of the system’s intrusion sensor(s). leds U, P, A Shows the properties you have set for LEDs to flash under various alert conditions.
Table 4-1. Command level 1 omreport Command Level 1, Level 2, and Level 3 (continued) Command Command level 2 level 3 rac 40 User privilege required Use assetinfo U, P, A Shows cost of ownership information for your system. cmdlog U, P, A Allows the administrator to show the command log. esmlog U, P, A Allows the administrator to show the hardware log. events U, P, A Shows the system’s SNMP event settings. operatingsystem U, P, A Shows the name and version of your operating system.
Help With the omreport Command Use the omreport -? command to get a list of the available commands for omreport. Use omreport -? to get help on the level 2 commands about, chassis, and system. The following information on omreport system -? applies equally to getting help for the omreport chassis command.
omreport chassis Commands Use omreport chassis commands to view details for the entire chassis or for a particular component. omreport chassis When you type: omreport chassis Server Administrator displays a general status for your main system chassis components. NOTE: The omreport chassis command does not list the health status of the Diagnostics Service. To view the health of the Diagnostics Service, see the Properties page for the Main System Chassis object on the Server Administrator home page.
omreport chassis acswitch Use the omreport chassis acswitch command if your system has redundant power supplies that are configured in a failover arrangement.
omreport chassis biossetup Use the omreport chassis biossetup command to view BIOS setup parameters that are normally available only during system boot. Type: omreport chassis biossetup Table 4-2 displays the BIOS setup parameters that are available: NOTE: Not all the parameters are displayed. Only those BIOS setup properties that are configured during system boot are displayed. Table 4-2.
Table 4-2. BIOS Setup Parameters (continued) Parameters Description Primary SCSI Displays whether the device is on or off. RAID on motherboard Displays whether RAID-on-motherboard is detected as a RAID device, a SCSI device, or if the device is disabled during system boot. RAID Channel A Displays whether RAID-on-motherboard Channel A is detected as a RAID device or a SCSI device. RAID Channel B Displays whether RAID-on-motherboard Channel B is detected as a RAID device or a SCSI device.
Table 4-3. omreport chassis bmc (continued) name=value pair Description config=nic Reports BMC information for the LAN. config=serial Reports serial port information for BMC. config=serialoverlan Reports BMC information on a serial over LAN connection. config=terminalmode Reports terminal mode settings for the serial port. config=user Reports information on BMC users. omreport chassis currents Use the omreport chassis currents command to view current (amperage) probe status and settings.
omreport chassis frontpanel Use the omreport chassis frontpanel command to view whether the front panel button control settings, such as for the Power button and/or Nonmasking Interrupt (NMI) button (if present on the system), are enabled or disabled. If the Power button override is present on your system, you can see whether the Power button override is enabled or not. If enabled, the Power button turns the power to the system On and Off.
Depending on your configuration, output may resemble the following example: Index : 0 Chassis Name : Main System Chassis Host Name : everglades Baseboard Management Controller Version : 1.80 Primary Backplane Version : 1.01 Sensor Data Record Version : SDR Version 0.
omreport chassis leds Use the omreport chassis leds command to find out whether clear hard drive fault is supported and what severity level lights up the LED. Type: omreport chassis leds index=n The index parameter is optional. If you do not specify the index, Server Administrator displays a summary of LED information for chassis 0. If you specify the index, Server Administrator displays a summary for a specific chassis.
If your system supports redundant memory, the redundancy output may resemble the following: Memory Redundancy Redundancy Status Fail Over State Redundancy Configuration Attributes Memory Array 1 Attributes Memory Array 1 Attributes Memory Array 1 Attributes Memory Array 1 Attributes Memory Array 1 : : : : : : : : : : : : : Full Inactive SpareBank Location Proprietary Add-on Card Use Unknown Installed Capacity 1536 MB Maximum Capacity 12288 MB Slots Available 12 omreport chassis nics Use the omreport chas
Connector Type refers to the type of plug or cable and plug that connects two devices together, in this case, the type of connector that attaches an external device to a system. There are many connector types, each designed to connect a different device type to a system. Examples include DB-9 Male, AT, Access Bus, PS/2, and so on. Maximum Speed is the port speed. Port speed refers to the data transmission rate of an input/output channel, measured in numbers of bits per second.
Fields Reported for Each Cache on a Particular Processor Status reports whether a specific cache on the processor is enabled or disabled. Level refers to primary or secondary cache. Primary-level cache is a memory bank built into the processor. Secondary-level cache is a staging area that feeds the primary cache. A secondary-level cache may be built into the processor or reside in a memory chip set outside the processor. The internal processor cache is referred to as a Level 1 (or L1).
omreport chassis pwrsupplies Use the omreport chassis pwrsupplies command to view properties of your system’s power supplies. Type: omreport chassis pwrsupplies index=n The index parameter is optional. If you do not specify the index, Server Administrator displays properties for all power supplies in your system. If you specify the index, Server Administrator displays properties for a specific processor.
omreport chassis volts Use the omreport chassis volts command to view properties of your system’s voltage probes. When you type: omreport chassis volts index=n The index parameter is optional. If you do not specify the index, Server Administrator displays a summary of status, readings, and thresholds set for any voltage probes that might be present on your system. If you specify the index, Server Administrator displays a summary for a specific voltage probe.
Commands for Viewing Logs You can use the omreport system command to view logs: the alert log, the command log, the hardware or ESM log, and the POST log. NOTE: If the Alert log or Command log displays invalid XML data (such as when XML data generated for the selection is not well-formed), clearing the log by typing "omconfig system alertlog action=clear or omconfig system cmdlog action=clear" resolves the issue.
Components and Events for Which You Can View Alert Actions You can view alert action properties for the following components and the events: • current probe warning • current probe failure • fan warning • fan failure • chassis intrusion • memory pre-failure • memory failure • power supply failure • degraded redundancy • lost redundancy • temperature warning • temperature failure • voltage warning • voltage failure • power supply warning • processor warning • processor failu
omreport system events Use the omreport system events command to view the current enabled or disabled SNMP traps. This command displays a summary of each component in your system for which events can be generated. For each component, the report shows which severities are set to be reported and which severities are set not to be reported.
Table 4-5. System Events by Component Type (continued) name=value pair Description type=log Reports events for logs. type=memory Reports events for memory. type=powersupplies Reports events for power supplies. type=redundancy Reports events for redundancy. type=temps Reports events for temperatures. type=volts Reports events for voltages.
Table 4-6. omreport system pedestinations Output Attributes Description Destination Number: Destination1 destination 1: Displays the first destination. Destination List Destination IP Address: 101.102.103.104 101.102.103.104: IP address of the first destination. Destination Number: Destination 2 destination 2: Displays the second destination. Destination IP Address: 110.120.130.140 110.120.130.140: IP address of the second destination.
omreport system summary Use the omreport system summary command to view a comprehensive summary of software and hardware components currently installed on your system. Example Command Output When you type: omreport system summary the output that appears in your CLI window depends on the systems management software, operating system, and hardware components and options that are installed on your system.
The system summary hardware information includes data values for installed components of the following types that are present in your system: System Attributes • Host name • System location Main System Chassis Chassis • Chassis model • Chassis service tag • Chassis lock • Chassis asset tag Processor The following are listed for each processor in the system: • Processor manufacturer • Processor family • Processor version • Current speed • Maximum speed • External clock speed • Vol
Memory • Total installed capacity • Memory available to the operating system • Total maximum capacity • Memory array count Memory Array The following details are listed for each memory board or module in the system (for example, the system board or the memory module in a given slot number): • Location • Use • Installed capacity • Maximum capacity • Slots available • Slots used • ECC type BIOS • Manufacturer • BIOS version • Release date • BIOS firmware information • Name •
Network Interface Card The following details are listed for each NIC in the system: • IP address • Subnet mask • Default gateway • MAC address Storage Enclosures The following details are listed for each storage enclosure attached to the system: • Name • Product ID omreport system thrmshutdown Use the omreport system thrmshutdown command to view which properties, if any, have been configured for a thermal shutdown action.
omreport system version Use the omreport system version command to list the version numbers of the BIOS, firmware, systems management software, and operating system that are installed on your system. Example Command Output When you type: omreport system version the output that appears in your CLI window depends on the version of the BIOS, RAID controllers, and firmware installed on your system.
omreport storage: Using the Storage Reports Use the omreport storage command to view information about enclosures, volumes, arrays, and disks that are part of your storage system. NOTE: This chapter only documents commands that are available when Array Manager is installed. See "Using the Storage Management Service" for information on using the omreport storage command when the enhanced Storage Management Service is installed.
Table 5-1. omreport storage Command Level 1, Level 2, and Level 3 Command level 1 Command level 2 Command level 3 User privilege Use required omreport storage A Displays a high-level status for all storage components. arraydisks A Displays a high-level status for array disks. arrays A Displays detailed information for an array disk on a particular controller. osdiskinfo A Displays detailed information for a particular operating system disk.
omreport storage arraydisks Use the omreport storage arraydisks controller=ID command (where ID is the ID number for the controller that controls the disks in the array) to view information for all enclosures and disks attached to a specific RAID controller.
omreport storage arrays Use the omreport storage arrays command to view detailed information about the disk controller and the storage subsystems attached to the controller. The following information is provided about the controller: • ID — Assigned ID number for the controller. • Name — Name of the controller. • State — Current state of the controller. • Firmware Version— Version of firmware installed on the controller.
• • Write Cache — Write policies specify whether the controller sends a write-request completion signal as soon as the data is in the cache or after it has been written to disk. The write policies are as follows: – Write-Back Caching — When using write-back caching, the controller sends a write-request completion signal as soon as the data is in the controller cache but has not yet been written to disk.
omreport storage enclosureinfo Use the omreport storage enclosureinfo enclosure=ID command (where ID is the ID number for the enclosure) to view information about a single enclosure.
omreport storage enclosures Use the omreport storage enclosures command to view the enclosures that contain array disks for a particular controller. The following information displays for each enclosure on the controller: • ID — Assigned ID number for the enclosure. • Status — Status of the enclosure. • Name — Name of the enclosure. • Application Version — Version of firmware on the enclosure. • Product ID — Identifying information for the storage enclosure, such as model and short description.
• • • Read Cache — Read policies indicate whether or not the controller should read sequential sectors of the logical drive when seeking data. The read policies are as follows: – Read-Ahead — When using read-ahead policy, the controller reads sequential sectors of the logical drive when seeking data. Read-ahead policy may improve system performance if the data is actually written to sequential sectors of the logical drive.
The omreport storage osdiskinfo command provides the following information about the physical array disks that comprise the operating system disk: • Status — Status of the array disk. • Label — Name of the array disk. If more than one array disk comprises a virtual disk, the name may include the number of the array disk, for example, ArrayDisk0:0, ArrayDisk0:1 means the first and second array disks that make ArrayDisk0. • State — Current state of the array disk.
omreport storage volumes Use the omreport storage volumes command to view information about the volumes on your storage system. The following information displays for each volume: 74 • ID — Assigned ID number for the volume. You can use this number in conjunction with the omreport storage osdisks command to view information about an operating system disk on a specific volume. See "omreport storage osdisks" for more information. • Status — Status of the volume. • Label — Name of the volume.
omconfig: Managing Components Using the Instrumentation Service The omconfig command allows you to provide values that define warning events, configure alert actions, clear logs, and configure system shutdown, as well as allowing you to perform other systems management tasks.
omconfig Command Summary NOTE: Although this section lists all possible omconfig commands, the commands available on your system depend on your system configuration. If you try to get help or execute a command for a component that is not installed on your system, Server Administrator issues a message that the component or feature is not "found on this system." NOTE: For Microsoft® Windows® systems, use Array Manager to configure an external chassis.
Table 6-1. Command level 1 omconfig Command Level 1, Level 2, and Level 3 (continued) Command level 2 Command level 3 User privilege Use required esmlog P, A Allows the administrator to clear the log. events P, A Enables and disables SNMP traps. pedestinations P, A Sets IP addresses for alert destinations. platformevents A Determines the shutdown action, if any, to be taken for a specific platform event. Also, enables and disables platform events filter alert generation.
Table 6-1. Command level 1 omconfig Command Level 1, Level 2, and Level 3 (continued) Command level 2 Command level 3 User privilege Use required memorymode A temps P, A Enables or disables the spare bank and mirroring memory modes, and also specify which mode to use. Sets warning threshold values by default or value. NOTE: You cannot set warning threshold values by default on ESM3 systems. volts P, A Sets warning threshold values by default or value.
To make a file that contains all of the help for the omconfig system alertaction -? command, type: omconfig system alertaction -? -outa alert.txt where -outa directs the output of the command to a file called alert.txt. To read the help for the alertaction command on a Microsoft Windows or Red Hat® Enterprise Linux operating system, type: more alert.txt omconfig about Use the omconfig about command to learn the product name and version number of the systems management application installed on your system.
omconfig chassis Use the omconfig chassis commands to default or to set values for current, fan, voltage, and temperature probes, to configure BIOS behavior during system start up, to clear memory error counts, and to enable or disable power button control features where system configuration permits. Use the omconfig chassis -? command to see a list of all omconfig chassis commands. NOTE: When you issue CLI commands to a server module in a modular system, chassis refers only to the server module.
Table 6-2. BIOS Setup (continued) name=value pair 1 attribute= name=value pair 2 setting= Description attribute=dbs setting=enable | disable enable: Enables Demand Based Power Management (DBS) on the system. disable: Disables DBS on the system. attribute=diskette setting=off | auto | writeprotect off: Disable the diskette drive. auto: Auto enable the diskette drive. writeprotect: Do not allow writes. Make the diskette drive read only.
Table 6-2. BIOS Setup (continued) name=value pair 1 attribute= name=value pair 2 setting= Description attribute=mouse setting=on | off on: Enable the mouse. off: Disable the mouse. attribute=nic setting=enabled | disabled | enablednonepxe enabled: Enable the NIC during system boot (with PXE on if the system has PXE). disabled: Disable the NIC during system boot. enablednonepxe: Enable the NIC during system boot (with PXE off if the system has PXE).
Table 6-2. BIOS Setup (continued) name=value pair 1 attribute= name=value pair 2 setting= Description attribute=primaryscsi setting=on | off force=true NOTICE: If you modify the setting for primary scsi, romb, romba, or rombb, your system becomes inoperable until you reinstall the operating system. on: Enable this device. off: Disable this device. force=true: Verification of setting change.
Table 6-2. BIOS Setup (continued) name=value pair 1 attribute= name=value pair 2 setting= attribute=sataport (0...7) setting=off | auto Description off: Disable the SATA port. auto: Automatically enable the SATA port. attribute=secondaryscsi setting=on | off on: Enable this device. off: Disable this device. attribute=serialport1 setting=off | auto | com1 | com3 | bmcserial | bmcnic | rac off: Disable serial port 1. auto: Map serial port 1 to a COM port. com1: Map serial port 1 to COM port 1.
omconfig chassis bmc Use the omconfig chassis bmc command to configure: • The BMC on a local area network (LAN) • The serial port for BMC • The BMC on a serial over LAN connection • Terminal settings for the serial port • Advanced settings for a serial over LAN connection • Information on a BMC user NOTE: You have to enter the user ID to configure user information. Type: omconfig chassis bmc The output from the omconfig chassis bmc command lists each of the available configurations.
Table 6-3. omconfig chassis bmc (continued) name=value pair 1 config= name=value pair 2 config=nic (continued) ipsource=static | dhcp | systemsoftware Description static: Static if the IP address of the BMC LAN interface is a fixed, assigned IP address. dhcp: DHCP if the source of the IP address of the BMC LAN interface is the dynamic host configuration protocol. systemsoftware: System software if the source of the IP address of the BMC LAN interface is from the system software.
Table 6-3. omconfig chassis bmc (continued) name=value pair 1 config= name=value pair 2 Description config=serial baudrate=9600 | 19200 | 38400 | 57600 9600: Sets connection speed to 9600 bits per second. 19200: Sets connection speed to 19200 bits per second. 38400: Sets connection speed to 38400 bits per second. 57600: Sets connection speed to 57600 bits per second. flowcontrol=none | rtscts none: No control over the flow of communication through the serial port.
Table 6-3. omconfig chassis bmc (continued) name=value pair 1 config= name=value pair 2 Description config=serial (continued) privilegelevel=administrator | operator administrator: Sets the maximum | user privilege level that can be accepted on a serial connection, to Administrator. operator: Sets the maximum privilege level that can be accepted on a serial connection, to Operator. user: Sets the maximum privilege level that can be accepted on a serial connection, to User.
Table 6-3. omconfig chassis bmc (continued) name=value pair 1 config= name=value pair 2 Description config=terminalmode (continued) echocontrol=enabled | disabled enabled: Enables characters to be sent to the screen. disabled: Disables characters to be sent to the screen. handshakingcontrol=enabled | disabled enabled: Directs the BMC to output a character sequence that indicates when its input buffer is ready to accept another command.
Table 6-3. omconfig chassis bmc (continued) name=value pair 1 config= name=value pair 2 Description config=user id=number id=number: ID number of the user being configured. enable=true | false enable=true: Enables user. enable=false: Disables user. id=number name=text number: ID number of the user being configured. name=text: Name of the user. id=number newpw=text confirmnewpw=text number: ID number of the user being configured. newpw=text: New password of the user.
Table 6-3. omconfig chassis bmc (continued) name=value pair 1 config= name=value pair 2 Description config=user id=number lanaccesslevel= administrator | operator | user| none id=number: ID number of the user being configured. (continued) lanaccesslevel=administrator: User with an ID has access privileges of an Administrator for the LAN channel. lanaccesslevel=operator: User with an ID has access privileges of an Operator for the LAN channel.
Default Minimum and Maximum Warning Thresholds If you want to set both the upper and lower current warning threshold values to the recommended default value, type: omconfig chassis currents index=0 warnthresh=default You cannot default one value and set another. In other words, if you default the minimum warning threshold value, you are also selecting the default value for the maximum warning threshold value.
Default Minimum and Maximum Warning Thresholds NOTE: Systems that contain ESM3 capabilities do not allow you to set warning threshold values to default values. If you want to set both the upper and lower fan warning threshold values to the recommended default value, type: omconfig chassis fans index=0 warnthresh=default You cannot default one value and set another.
omconfig chassis frontpanel Use the omconfig chassis frontpanel command to configure the Power button and the Nonmasking Interrupt (NMI) button. NOTE: The Power and NMI buttons can be configured only if present on the system. Table 6-7 shows the valid parameters for the command. Table 6-7. omconfig chassis frontpanel Subcommand name=value pair Description nmibutton enable=true | false true: Enables the NMI button on the system. false: Disables the NMI button on the system.
For some chassis, you can assign a different name. You cannot rename the main system chassis. In the example below, the command renames chassis 2 from storscsi1 to storscsia: omconfig chassis info index=2 name=storscsia As with other commands, the CLI issues an error message if you do not have a chassis 2 (the main chassis=0). The CLI allows you to issue commands only for the system configuration you have.
Mirroring mode switches to a redundant copy of memory when an uncorrectable memory event is detected. After switching to the mirrored memory, the system does not switch back to the original system memory until the next reboot. The operating system does not recognize half of the installed system memory in this mode. Table 6-10 shows the valid parameters for the command. Table 6-10.
Default Minimum and Maximum Warning Thresholds NOTE: The capabilities for managing sensors vary by systems. If you want to set both the upper and lower temperature warning threshold values to the recommended default value, type: omconfig chassis temps index=0 warnthresh=default You cannot default one value and set another. In other words, if you default the minimum warning threshold value, you are also selecting the default value for the maximum warning threshold value.
Default Minimum and Maximum Warning Thresholds NOTE: Systems that contain ESM3, ESM4, and BMC capabilities do not allow you to set warning threshold values to default values. If you want to set both the upper and lower voltage warning threshold values to the recommended default value, type: omconfig chassis voltage index=2 warnthresh=default You cannot default one value and set another.
Therefore, for a computer named "myOmsa" running Server Administrator, the default name would be "myOmsa–omsa". This is the name of Server Administrator defined in Active Directory by using the snap–in tool. This name must match the name for the application object in Active Directory in order to find user privileges. NOTE: This command is applicable only on systems running the Windows operating system. Table 6-13 shows the valid parameters for the command. Table 6-13.
Table 6-14 shows the valid parameters for the command. Table 6-14. SNMP Root Password Parameters name=value pair Description setting=rootpw Required. oldpw= Enter the old SNMP root password. newpw= Sets the new SNMP root password. confirmnewpw= Confirms the new SNMP root password. When you type omconfig preferences snmp setting=rootpw, the system prompts you to supply values for the required parameters.
omconfig system Use the omconfig system commands to clear logs, determine how various shutdown actions occur, set initial values or edit values for cost of ownership information, and determine how to respond to a hung operating system. omconfig system alertaction You can use the omconfig system alertaction command to determine how Server Administrator responds when a component has a warning or failure event.
Available Alert Actions Table 6-16 shows the alert actions for each component that allows you to configure an alert action. Table 6-16. Alert Actions You Can Set for Warning and Failure Events Alert Action Setting Description beep=true | false true: Enables your system's beep speaker. When enabled, the speaker on the system from which you are running Server Administrator beeps. false: Disables your system's beep speaker. alert=true | false true: Enables your system's console alert.
Table 6-17. Events for Which You Can Set Alert Actions (continued) Event Name Description event=powersupply Sets actions when a power supply probe detects a failure value. event=powersupplywarn Sets actions when a power supply probe detects a warning value. event=processorwarn Sets actions when a processor probe detects a warning value. event=processorfail Sets actions when a processor probe detects a failure value.
Example Chassis Intrusion Actions To clear all alert actions for chassis intrusion, type: omconfig system alertaction event=intrusion clearall=true Commands for Clearing Logs NOTE: For more information about alert messages, see the Dell OpenManage Server Administrator Messages Reference Guide. You can use the omconfig system command to clear three logs: the alert log, the command log, and the hardware, or ESM, log.
omconfig system platformevents Use the omconfig system platformevents command to configure shutdown action, if any, to be taken for a specific platform event. You can also enable or disable platform event filter alert generation. NOTICE: If you set a platform event shutdown action to anything other than "none", your system will forcefully shutdown when the specified event occurs.
Table 6-20. 106 omconfig system platformevents (continued) Event Name Description event=intrusion Sets action or enables/disables alert generation when a chassis has been opened. event=powerwarn Sets action or enables/disables alert generation when a power device probe detects that the power supply, voltage regulator module, or DC to DC converter is pending a failure condition.
omconfig system events Use the omconfig system events command to enable and disable SNMP traps for components on your system. NOTE: Not all event types may be present on your system. There are four parameters in the name=value pair component of the omconfig system events command: • source • type • severity • index Source At present, source=snmptraps is a required name=value pair because SNMP is currently the only supported source of event notification for your system’s components.
Severity In the context of configuring events, severity determines how severe an event must be before Server Administrator notifies you of the event for a component type. When there are multiple components of the same type in the same system chassis, you can also specify whether you want to be notified for event severity according to the number of the component by using the index= parameter. Table 6-22 shows the valid severity parameters. Table 6-22.
omconfig system recovery Use the omconfig system recovery command to set the action that is to be taken when the operating system has hung or crashed. You can also set the number of seconds that must pass before the system is considered to have a hung operating system. Table 6-24 shows the valid parameters for the command. NOTE: Upper and lower limits for the timer are dependent on your system model and configuration. Table 6-24.
Table 6-25. Shutdown Parameters (continued) name=value pair Description action=powercycle Turns the electrical power to the system off, pauses, turns the power on, and reboots the system. Power cycling is useful when you want to reinitialize system components such as hard drives. osfirst=true | false true: Closes the file system and exits the operating system before shutting down the system. false: Does not close the file system or shut down the operating system before shutting down the system.
omconfig system assetinfo: Editing Cost of Ownership Values omconfig System Asset Info Overview The omconfig system assetinfo command helps you to edit a comprehensive set of parameters that make up your system's total cost of ownership. This section explains the parameters that can be reported and configured under the omconfig system assetinfo command. Using the omconfig system assetinfo command, you can set governing values for configurable objects.
Table 7-1. omconfig system assetinfo info=acquisition (continued) Command Command Command name=value pair 1 name=value pair 2 level 1 level 2 level 3 Use expensed=yes | no Whether the system is charged to a specific purpose or department such as research and development or sales. installdate= Date the system was put into service. ponum= Number of the document that authorized payment for the system. purchasecost= Price the owner paid for the system.
Adding Depreciation Information Depreciation is a set of methods for computing the devaluation of your asset over time. For example, the depreciation of a system that is expected to have a useful life of 5 years would be 20 percent. Use the omconfig system assetinfo=depreciation command to add details about how your system's depreciation is to be computed. Table 7-2 shows the valid parameters for the command. Table 7-2.
Adding Extended Warranty Information Use the omconfig system extwarranty command to assign values for extended warranty information. A warranty is a contract between the manufacturer or dealer and the purchaser of a system. The warranty identifies the components that are covered for repair or replacement for a specified length of time or usage. The extended warranty comes into force after the original warranty expires. For details on how to edit warranty values, see "Adding Warranty Information.
Adding Lease Information A lease is an agreement to pay for the use of a system for a specified period of time. The lessor retains ownership of the system. Table 7-4 shows the valid parameters for the command. Table 7-4. omconfig system assetinfo info=lease Command Command Command name=value pair 1 name=value pair 2 level 1 level 2 level 3 Use omconfig system assetinfo info=lease buyout= Amount of money paid to purchase a system from a lessor.
Adding Maintenance Information Maintenance refers to activities required to keep the system in good working order. Table 7-5 shows the valid parameters for adding maintenance information. Table 7-5. omconfig system assetinfo info=maintenance Command Command Command name=value pair 1 level 1 level 2 level 3 name=value pair 2 Use enddate= Date the extended warranty agreement ends. provider= Business entity providing the maintenance service.
Adding Outsource Information Outsourcing is the practice of contracting with another business to maintain the system in good working order. Table 7-6 shows the valid parameters for adding outsource information. Table 7-6. omconfig system assetinfo info=outsource Command Command Command name=value pair 1 name=value pair 2 level 1 level 2 level 3 Use omconfig system assetinfo info=outsource levels= Levels of service offered by the provider.
Adding Owner Information The owner is the party that holds legal property title to the system. Table 7-7 shows the valid parameters for adding owner information. Table 7-7. omconfig system assetinfo info=owner Command Command Command name=value pair 1 name=value pair 2 level 1 level 2 level 3 Use omconfig system assetinfo info=owner insuranceco= Name of the insurance company that insures the system. ownername= Business entity that owns the system.
Adding Service Contract Information A service contract is an agreement that specifies fees for preventive maintenance and repair of the system. Table 7-8 shows the valid parameters for adding contract information. Table 7-8. omconfig system assetinfo info=service Command Command Command name=value pair 1 name=value pair 2 level 1 level 2 level 3 Use omconfig system assetinfo info=service renewed=true | false Whether the service agreement has been renewed.
Adding Support Information Support refers to technical assistance that the system user can seek when the user desires guidance on the proper use of a system to perform tasks. Table 7-9 shows the valid parameters for adding support information. Table 7-9. omconfig system assetinfo info=support Command Command Command name=value pair 1 name=value pair 2 Use level 1 level 2 level 3 omconfig system assetinfo info=support automaticfix= Name of any application used to fix a problem automatically.
Adding System Information System information includes the primary user of the system, the phone number for the primary user, and the system location. Table 7-10 shows the valid parameters for adding system information. Table 7-10. omconfig system assetinfo info=system Command Command Command level 1 level 2 level 3 name=value pair 1 name=value pair 2 Use location= Location of the system. primaryphone= Phone number of the system's primary user.
Adding Warranty Information Use the omconfig system warranty command to assign values for warranty information. A warranty is a contract between the manufacturer or dealer and the purchaser of a system. The warranty identifies the components that are covered for repair or replacement for a specified length of time or usage. For details on how to edit extended warranty values, see "Adding Extended Warranty Information." Table 7-11 shows the valid parameters for adding warranty information. Table 7-11.
Using the Storage Management Service 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.
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.
Table 8-2. Syntax For Name=Value Pairs For Parameters (continued) Syntax Description adisk= Indicates a particular array disk by specifying either connector:targetID or connector:enclosureID:portID. To obtain the values for the connector, enclosure, and array disk (targetID or portID), 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.
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 Controller Status Table 8-4. omreport Controller Commands Required Command Levels (1, 2, 3) Optional name=value pairs Use omreport storage controller Displays property information for all controllers attached to the system. controller=id Displays the specified controller where id is the controller number. and all attached components such as enclosures, virtual disks, array For example: controller=0 disks, and so on. omreport Global Information (Smart Thermal Shutdown Status) Table 8-5.
omreport Connector Status Table 8-7. omreport Connector Commands Required Command Levels (1, 2, 3) Optional name=value pairs Use omreport storage connector Displays all connectors present on all controllers on the system. controller=id where id is the controller number. For example: controller=0 controller=id where id is the controller number. For example: controller=0 Displays the connector on the specified controller. Displays information for the specified connector on the controller.
omreport Temperature Probe Status Table 8-9. omreport Temperature Probe Commands Required Command Levels (1, 2, 3) Optional name=value pairs and name=value pair Use omreport storage enclosure Displays property information for all enclosures attached to the system. controller=id enclosure=id info=temps Displays the temperature probes for the specified enclosure. where id is the controller number and the enclosure number.
omreport Power Supply Status Table 8-11. omreport Power Supply Commands Required Command Levels (1, 2, 3) Optional name=value pairs and name=value pair Use omreport storage enclosure Displays property information for all enclosures attached to the system. controller=id enclosure=id info=pwrsupplies Displays the power supplies for the specified enclosure. where id is the controller number and the enclosure number.
Table 8-12. omreport EMM Commands (continued) Required Command Levels (1, 2, 3) Optional name=value pairs and name=value pair Use controller=id enclosure=id info=emms index=n Displays the specified EMMs. where id is the controller number and the enclosure number and “n” is the number of an EMM. For example: controller=0 enclosure=2 info=emms index=1 omreport Array Disk Status Table 8-13.
omreport Virtual Disk Status Table 8-14. omreport Virtual Disk Commands Required Command Levels (1, 2, 3) Optional name=value pairs Use omreport storage vdisk Displays property information for all virtual disks on all controllers. controller=id where id is the controller number. For example: controller=0. controller=id vdisk=id where id is the controller number and the virtual disk number. For example: controller=0 vdisk=1. Displays all virtual disks on the specified controller.
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.
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.
Table 8-16. omconfig Controller Commands (continued) Required Command Levels (1, 2, 3) Optional name=value pairs action=setpatrolreadmode controller=id mode=manual | auto | disable action=startpatrolread controller=id action=stoppatrolread controller=id omconfig Rescan Controller Use the following omconfig command syntax to rescan a controller. See the online help for more information about using this 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 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.
Complete Syntax omconfig storage controller action=createvdisk controller=id raid= size= adisk= [stripesize=< 2kb| 4kb| 8kb| 16kb| 32kb| 64kb| 128kb>] [cachepolicy=] [readpolicy=] [writepolicy=] [name=] [spanlength=] Parameter Specification for Create and Reconfigure Virtual Disk The following sections indicate how to specify the omconfig storage controller action=createvdisk parame
Table 8-17. Raid Level and Concatenation (continued) RAID Level or Concatenation raid=n Parameter Specification RAID 10 raid=r10 RAID 50 raid=r50 RAID 1-concatenated raid=r1c Concatenation raid=c size= Parameter (Required) The following table indicates how to specify the size= parameter. Table 8-18.
[cachepolicy=] Parameter (Optional) Different controllers support different cache policies. See the online help for more information. The following table indicates how to specify the [cachepolicy=] parameter for each of the cache policies. Table 8-19.
[name=] 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=] Parameter (Required for RAID 50) Use this parameter to specify the number of array disks to be included in each stripe. This parameter only applies to RAID 50 virtual disks.
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 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.
omconfig Clear Foreign Configuration Use the following omconfig command syntax to clear or delete all virtual disks that reside on array 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.
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.
Table 8-22.
Example Syntax For example, to blink the array 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.
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.
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 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 array 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 adisk= assign=no where id is the controller ID and virtual disk ID. The variable specifies the array disk.
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.
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.
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.
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= | writepolicy= | cachepolicy=] where id is the controller ID and virtual disk ID as reported by the omreport command.
omconfig Array Disk Commands The following sections provide the omconfig command syntax required to execute array disk tasks. Table 8-23.
Example for SAS Controllers: To blink the array disks described in this example, enter: omconfig storage adisk action=blink controller=1 adisk= 0:2:0,0:2:1,0:2:2 omconfig Unblink Array Disk 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. Complete Syntax omconfig storage adisk action=unblink controller=id adisk= where id is the controller ID.
Example Syntax In this example, you want to prepare array disk 3 on connector 0 of controller 1 for removal. On a SAS controller, the array disk resides in enclosure 2.
omconfig Offline Array Disk Use the following omconfig command syntax to offline an array disk: Complete Syntax omconfig storage adisk action=offline controller=id adisk= connectorID:targetID where id is the controller ID and connectorID:targetID is the connector number and array disk number as reported by the omreport command.
omconfig Online Array Disk Use the following omconfig command syntax to bring an offline array disk back online. Complete Syntax omconfig storage adisk action=online controller=id adisk= where id is the controller ID. The variable specifies the array disk. 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 for SCSI, SATA, and ATA Controllers: To assign the array disk described in this example as a global hot spare, enter: omconfig storage adisk action=assignglobalhotspare controller=1 adisk=0:3 assign=yes Example for SAS Controllers: To assign the array disk described in this example as a global hot spare, enter: omconfig storage adisk action=assignglobalhotspare controller=1 adisk=0:2:3 assign=yes omconfig Unassign Global Hot Spare Use the following omconfig command syntax to unassign an array dis
omconfig Rebuild Array Disk 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. Complete Syntax omconfig storage adisk action=rebuild controller=id adisk= where id is the controller ID. The variable specifies the array disk.
Example Syntax In this example, you want to cancel the rebuild or array disk 3 on connector 0 of controller 1. On a SAS controller, the array disk resides in enclosure 2.
omconfig Clear Array Disk Use the following omconfig command to clear data or a configuration from an array disk. Complete Syntax omconfig storage adisk action=clear controller=id adisk= where id is the controller ID. The variable specifies the array disk. To obtain these values, 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 In this example, you want to cancel the clear of array disk 3 on connector 0 of controller 1. On a SAS controller, the array disk resides in enclosure 2.
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.
omconfig Connector Commands The following sections provide the omconfig command syntax required to execute connector tasks. Table 8-25. omconfig Connector Commands Required Command Levels (1, 2, 3) Optional name=value pairs omconfig storage connector action=rescan controller=id connector=id omconfig Rescan Connector Use the following omconfig command to rescan a controller connector. This command rescans all connectors on the controller and is therefore similar to performing a controller rescan.
Table 8-26.
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= where id is the controller ID. The variable specifies the enclosure.
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= assettag= where id is the controller ID. The variable specifies the enclosure. In this syntax, is a user-specified alphanumeric string.
Example for SAS Controllers: For example, to specify the asset name for enclosure 3 attached to connector 2 on controller 1 to encl43, enter: omconfig storage enclosure action=setassetname controller=1 enclosure=2:3 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.
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. Complete Syntax omconfig storage enclosure action=resettempprobes controller=id enclosure= index=id where id is the controller ID and the temperature probe ID. The 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 degrees celsius. Example for SCSI, SATA, and ATA Controllers In this example, the temperature probes reside in the enclosure attached to connector 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= where id is the controller ID.
Working With CLI Command Results Server Administrator Command Line Interface (CLI) users can use command output in various ways. This section explains how to save command output to a file and how to select a format for your command results that fits different objectives. Output Options for Command Results CLI command output displays to standard output on your system in a command window, in an Xterminal, or on a screen, depending on your operating system type.
Save Command Results to a File That Can Be Overwritten Use the -outc option when you want to overwrite data that is stored in previously written files. For example, at 11:00 A.M. you capture fan probe RPM readings for fan probe 0 on your system and write the results to a file called fans.txt. You type: omreport chassis fans index=0 -outc fans.
Type: omreport chassis fans index=0 -outa fans.txt Fans.
Syntax for the formatting option is: -fmt For example, type: omreport system summary -fmt tbl where -fmt tbl specifies table format. You can combine the formatting option with the option to direct output to a file. For example, type: omreport system summary -fmt tbl -outa summary.txt where -fmt tbl specifies table format and -outa specifies that you append the command results to a file called summary.txt. List (lst) The default format is lst or list format.
The example output displays as follows: -----------------------------Network Interface Card 0 Data -----------------------------| | | | | ATTRIBUTE IP Address Subnet Mask Default Gateway MAC Address | | | | | VALUE 143.166.152.108 255.255.255.0 143.166.152.1 00-02-b3-23-d2-ca Semicolon-separated Values (ssv) Use the ssv formatting option to deliver output formatted in semicolon-separated Value format.
Custom Delimited Format (cdv) Use the cdv formatting option to report exported data in custom delimited format. You can specify this option with any omreport command. For example, to generate a system summary in custom delimited format, type: omreport system summary -fmt cdv You can also set preferences for the custom delimited format with the omconfig command. The valid values for delimiters are: exclamation, semicolon, at, hash, dollar, percent, caret, asterisk, tilde, question, colon, comma, and pipe.
Glossary The following list defines or identifies technical terms, abbreviations, and acronyms used in Dell user documents. editor, such as Notepad in Microsoft® Windows®) is called an ASCII file. A ASIC Abbreviation for ampere(s). Acronym for application-specific integrated circuit. AC ASPI Abbreviation for alternating current. Advanced SCSI programming interface.
administrators who do not want define one set of privileges for users in the operating system and a separate set of users and accounts for the RAC. If you enable local operating system authentication for the RAC, you enable any user with Administrator status on the operating system to log into the RAC. autoexec.bat file The autoexec.bat file is executed when you boot your computer (after executing any commands in the config.sys file).
bus An information pathway between the components of a computer. Your computer contains an expansion bus that allows the microprocessor to communicate with controllers for all the various peripheral devices connected to the computer. Your computer also contains an address bus and a data bus for communications between the microprocessor and RAM. CDs are read-only storage devices; you cannot write new data to a CD with standard CD drives.
CMOS Acronym for complementary metal-oxide semiconductor. In computers, CMOS memory chips are often used for NVRAM storage. designed, MS-DOS® programs are limited to running in conventional memory. COO Acronym for cost of ownership. COMn The device names for the first through fourth serial ports on your computer are COM1, COM2, COM3, and COM4. The default interrupt for COM1 and COM3 is IRQ4, and the default interrupt for COM2 and COM4 is IRQ3.
cursor A marker, such as a block, underscore, or pointer that represents the position at which the next keyboard or mouse action will occur. DAT Acronym for digital audio tape. dB are used widely in personal computers. For example, the keyboard connector for PCs is a DIN connector. DIP Acronym for dual in-line package. A circuit board, such as a system board or expansion card, may contain DIP switches for configuring the circuit board.
DPMS ECP Abbreviation for Display Power Management Signaling. A standard developed by the Video Electronics Standards Association (VESA®) that defines the hardware signals sent by a video controller to activate power management states in a monitor. A monitor is said to be DPMS-compliant when it is designed to enter a power management state after receiving the appropriate signal from a computer's video controller. Abbreviation for Extended Capabilities Port.
Abbreviation for electromagnetic interference. for peripheral devices, such as a network card or an internal modem. EMM expansion-card connector Abbreviation for expanded memory manager. A utility that uses extended memory to emulate expanded memory on computers with an Intel386™ or higher microprocessor. A connector on the computer's system board or riser board for plugging in an expansion card. EMI extended memory Abbreviation for Expanded Memory Specification. RAM above 1 MB.
flash bios group A PC BIOS that is stored in flash memory rather than in a ROM. A flash BIOS chip can be updated in place, whereas a ROM BIOS must be replaced with a newer chip. As it relates to DMI, a group is a data structure that defines common information, or attributes, about a manageable component.
HPFS interlacing Abbreviation for the High Performance File System option in the Windows NT and later Windows operating systems. A technique for increasing video resolution by only updating alternate horizontal lines on the screen. Because interlacing can result in noticeable screen flicker, most users prefer noninterlaced video adapter resolutions. HTTPS Abbreviation for HyperText Transmission Protocol, Secure. HTTPS is a variant of HTTP used by Web browsers for handling secure transactions.
ISA kHz Acronym for Industry-Standard Architecture. A 16-bit expansion bus design. The expansion-card connectors in an ISA computer are also compatible with 8-bit ISA expansion cards. Abbreviation for kilohertz, 1,000 hertz. LAN Abbreviation for information technology equipment. Acronym for local area network. A LAN system is usually confined to the same building or a few nearby buildings, with all equipment linked by wiring dedicated specifically to the LAN.
LS drive A drive that uses laser servo technology to read LS 120 diskettes that hold up to 120 MB of data as well as standard 3.5-inch diskettes. LSI Acronym for large-scale integration. LUN Acronym for logical unit number, a code used to select a specific device among several that share a SCSI ID. EISA or XT bus architecture, so older cards cannot be used with it. memory A computer can contain several different forms of memory, such as RAM, ROM, and video memory.
MIF mV Acronym for management information format. A MIF file contains information, status, and links to component instrumentation. MIF files are installed into the MIF database by the DMI service layer. The content of a MIF is defined by a DTMF working committee and is published in the form of a MIF definition document. This document identifies the groups and attributes that are relevant to DMI-manageable components. Abbreviation for millivolt(s).
NVRAM PCMCIA Acronym for nonvolatile random-access memory. Memory that does not lose its contents when you turn off your computer. NVRAM is used for maintaining the date, time, and system configuration information. Personal Computer Memory Card International Association. An international trade association that has developed standards for devices, such as modems and external hard drives, that can be plugged into portable computers. OEM Abbreviation for original equipment manufacturer.
PLCC Acronym for plastic leaded chip carrier. The probes provide a snapshot of the measured quantity (such as the temperature at a particular place and time) or state (a chassis intrusion has or has not occurred). Plug and Play An industry-standard specification that makes it easier to add hardware devices to personal computers. Plug and Play provides automatic installation and configuration, compatibility with existing hardware, and dynamic support of mobile computing environments.
QFP read-only file Acronym for quad flat pack. A read-only file is one that you are prohibited from editing or deleting. A file can have read-only status if: RAC Acronym for remote access controller. Dell OpenManage Server Administrator supports all RACs. These include the DRAC II, DRAC III, DRAC III/XT, ERA, and ERA/O. • Its read-only attribute is enabled. • It resides on a physically write-protected diskette or on a diskette in a write-protected drive.
ROM SDMS Acronym for read-only memory. Your computer contains some programs essential to its operation in ROM code. Unlike RAM, a ROM chip retains its contents even after you turn off your computer. Examples of code in ROM include the program that initiates your computer's boot routine and the POST. Abbreviation for SCSI device management system. sec Abbreviation for second(s). SEC Abbreviation for single-edge contact. ROMB Acronym for RAID on motherboard.
SIMM SRAM Acronym for single in-line memory module. A small circuit board containing DRAM chips that connects to the system board. Abbreviation for static random-access memory. Because SRAM chips do not require continual refreshing, they are substantially faster than DRAM chips. SIP state Acronym for single in-line package, which is a type of housing for electronic components in which the connecting pins protrude from one side. A SIP is also called a Single In-line Pin Package (SIPP).
system board As the main circuit board, the system board usually contains most of your computer's integral components, such as the following: • Microprocessor • RAM • Controllers for standard peripheral devices, such as the keyboard • Various ROM chips Frequently used synonyms for system board are motherboard and logic board. system configuration information Data stored in memory that tells a computer what hardware is installed and how the computer should be configured for operation.
• LowerThresholdNon-critical unicode • LowerThresholdCritical • LowerThresholdFatal A fixed width, 16-bit world wide character encoding, developed and maintained by the Unicode Consortium. time-out A specified period of system inactivity that must occur before an energy conservation feature is activated. upper memory area Abbreviation for tracks per inch. The 384 KB of RAM located between 640 KB and 1 MB.
that uniquely identifies an enterprise, as well as the formula for specifying a unique identifier for the objects defined in that enterprise's MIB. variable A component of a managed object. A temperature probe, for example, has a variable to describe its capabilities, its health or status, and certain indexes that you can use to help you in locating the right temperature probe. VCCI video adapter The logical circuitry that provides—in combination with the monitor—your computer's video capabilities.
video resolution VRAM Video resolution—800 x 600, for example—is expressed as the number of pixels across by the number of pixels up and down. To display a program at a specific graphics resolution, you must install the appropriate video drivers and your monitor must support the resolution. Acronym for video random-access memory. Some video adapters use VRAM chips (or a combination of VRAM and DRAM) to improve video performance.
write-protected Read-only files are said to be write-protected. You can write-protect a 3.5-inch diskette by sliding its writeprotect tab to the open position or by setting the write-protect feature in the System Setup program. XMM Abbreviation for extended memory manager, a utility that allows application programs and operating systems to use extended memory in accordance with the XMS. XMS Abbreviation for eXtended Memory Specification. ZIF Acronym for zero insertion force.
Index Symbols -? omconfig, 78 omconfig chassis, 80 omdiag chassis, 22 omdiag storage, 29 omdiag system, 35 omreport, 41 request for help, 17 A about omconfig, 79 omdiag, 21 acquisition information, 111 optional parameters, 18 acquisition information adding, 111 acswitch omreport chassis, 43 omreport command level 3, 43 Adaptec and LSI array disk test omdiag storage raidctrl, 32 Adaptec and LSI blink disk light omdiag storage raidctrl, 33 Adaptec RAID controller hardware test device scan test, 31 global ca
Index baud rate test omdiag chassis serialport, 28 bios omreport chassis, 43 biossetup omconfig chassis, 80 omreport chassis, 44 blink omconfig, 174 blink array disk omconfig, 156 blink disk light omdiag storage scsidevdiag, 34 bmc omconfig chassis, 85 omreport chassis, 45 BRCMNetwork ASF test Broadcom network diagnostic test, 25 BRCMNetwork control registers test Broadcom network diagnostic test, 25 BRCMNetwork EEPROM test broadcom network diagnostic test, 25 BRCMNetwork internal memory test Broadcom
cancel clear array disk omconfig, 164 clear foreign configuration omconfig, 144 commands for clearing logs, 104 cancel initialize disk omconfig, 147 CLI clearing logs, 104 error messages, error checking, 13 commands for viewing logs, 55 cancel rebuild array disk omconfig, 162 CD drive diagnostics, 29 cddvd, 29 cdvformat omconfig preferences, 98 change virtual disk policy omconfig, 155 chassis omconfig, 80 omdiag, 22 chassis fault LED, 95 chassis identification LED, 95 chassis information summary, 47 c
Index connector name omreport chassis processors, 51 default minimum warning threshold, 93 connector status omreport, 128 delay battery learn cycle omconfig, 166 controller battery, 127-128 BMC, 38, 45, 59, 77 display IDs, 124 omconfig storage, 134 omreport storage, 127 RAID, 29, 32 SATA, 83 SCSI, 21, 34 tests, 28-29 USB, 20, 29 delete virtual disk omconfig, 153 controlling CLI command output, 175 diagnostic test, 23 conventions for command parameter tables, 37 defining alert actions, 101 de
external clock speed omreport chassis processors, 51 formatting CLI command output, 177 help, levels of, 18 hot spare, 150 external name omreport chassis ports, 50 frontpanel omconfig chassis, 94 omreport chassis, 47 I extremity seek test omdiag storage floppy, 31 fru omreport chassis, 47 identify connected disks omdiag storage raidctrl, 32 extremity test omdiag storage cddvd, 30 funnel seek test omdiag storage floppy, 30 import foreign configuration omconfig, 143 extwarranty omconfig system, 11
Index L lease information, 115 leds omconfig chassis, 95 omreport chassis, 49 levels of help for a CLI command, 18 memorymode omconfig chassis, 95 minimum warning threshold, 92, 97 modem diagnostics, 23 modem test, 23 linear seek test omdiag storage floppy, 30 N LSI RAID controller battery test omdiag storage raidctrl, 32 name=value pairs omconfig chassis biossetup, 80 omconfig chassis bmc, 85 omconfig chassis currents, 91 LSI RAID controller hardware test configuration test, 32 timer test, 32
omconfig (continued) offline array disk, 159 online array disk, 160 pause check consistency, 152 prepare to remove array disk, 157 quiet controller alarm, 136 rebuild array disk, 162 recondition battery, 165 reconfiguring virtual disks, 154 remove dead segments, 163 rename virtual disk, 155 rescan connector, 167 rescan controller, 135 reset controller configuration, 137 reset temperature probe thresholds, 172-173 restore dead segments, 148 resume check consistency, 153 set controller rebuild rate, 141 set e
Index omconfig storage adisk, 123, 156 battery, 165 connector, 167 controller, 134 enclosure, 167 globalinfo, 132 vdisk, 145 omconfig system alertaction, 101 alertlog, 17, 76, 104 assetinfo, 111 cmdlog, 104 esmlog, 104 events, 107 extwarranty, 114 name=value pairs, parameters, 107 pedestinations, 104 platformevents, 105 recovery, 109 shutdown, 109 thrmshutdown, 110 webserver, 108 omconfig system assetinfo info=acquisition, 111-112 info=depreciation, 113 info=extwarranty, 114 info=lease, 115 info=maint
omdiag chassis usbctrl USB node detection test, 29 omdiag storage, 29 -?, 29 cddvd, 29 floppy, 30 idedevdiag, 31 raidctrl, 31 scsidevdiag, 34 omdiag storage cddvd driver mechanism test, 30 extremity test, 30 read exerciser test, 30 omdiag storage floppy extremity seek test, 31 funnel seek test, 30 linear seek test, 30 read-write test, 31 omdiag storage idedevdiag, 31 omdiag storage raidctrl, 31 Adaptec and LSI array disk test, 32 Adaptec and LSI blink disk light, 33 Adaptec RAID controller hardware test, 31
Index omreport chassis processors cache properties, 51 connector name, 51 core count, 51 current speed, 51 external clock speed, 51 manufacturer, 51 processor family, 51 processor version, 51 state, 51 omreport storage commands, 66 omreport system commands, 54 omreport storage osdisks ID, 73 name, 73 state, 73 status, 73 type, 73 unallocated space, 73 vendor, 73 omreport system events name=value pairs, 57 omreport chassis slots adapter, 53 data bus width, 53 index, 53 slot ID, 53 omreport storag
PCI diagnostics, 27 R pedestinations omconfig system, 104 omreport system, 58 raidctrl omdiag storage, 31 platformevents omconfig system, 105 omreport system, 59 port type omreport chassis ports, 50 ports omreport chassis, 50 POST result test omdiag chassis rac, 28 postlog omreport system, 55 prepare to remove array disk, 157 primary CLI command omconfig, 12 omdiag, 12, 19 omhelp, 12, 17 omreport, 12 primary CLI commands, 12 processor family omreport chassis processors, 51 read exerciser test omdiag st
Index service contract information, 119 adding, 119 state omreport chassis processors, 51 set enclosure asset name omconfig, 170 storage diagnostics, 29 set enclosure asset tag omconfig, 170 storage management CLI, 123 set temperature probe thresholds omconfig, 171-173 summary omreport system, 60 shutdown omconfig system, 109 omreport system, 59 shutdown action omconfig system platformevents, 105 slot ID omreport chassis slots, 53 storage management, 123 successful commands, 13 support infor
thrmshutdown omconfig system, 110 omreport system, 63 timer test LSI RAID controller hardware test, 32 U unassign dedicated hot spare omconfig, 150 unassign global hot spare omconfig, 161 unblink array disk omconfig, 157 unmirror omconfig, 149 USB node detection test omdiag chassis usbctrl, 29 user access to Server Administrator administrators only, 100 determining, 100 least restrictive, 100 most restrictive, 100 power users and administrators only, 100 useraccess omconfig preferences, 100 V W vdisk om
Index 216 Index
