Dell OpenManage Server Administrator Version 7.1.
Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ____________________ Information in this publication is subject to change without notice. © 2013 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . Overview . . . . . . . . . . . . . . . . . . . . . . 17 . . . . . . . . . . . . . . . . . . . . . . . . 17 What's New in This Release . . . . . . . . . . . . . . Accessing the Windows Command Prompt to Run CLI Commands . . . . . . . . . . . . . . . . . . . . Primary CLI Commands . . 19 . . . . . . . . . . . . . . . . . 19 . . . . . . . . 21 . . . . . . . . . . . . . . . . 21 . . . . . . . . . . . . . . . . .
omreport modularenclosure . omreport about . . . . . . . . . . . . . . 39 . . . . . . . . . . . . . . . . . . . . . 40 omreport chassis or omreport mainsystem Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 omreport chassis acswitch or omreport mainsystem acswitch . . . . . . . . . . . . . . . 42 omreport chassis batteries or omreport mainsystem batteries . . . . . . . . . . . . . . . . 43 . . . . . . . .
omreport chassis nics or omreport mainsystem nics . . . . . . . . . . . . . . . . . . 56 omreport chassis ports or omreport mainsystem ports . . . . . . . . . . . . . . . . . . 57 omreport chassis processors or omreport mainsystem processors . . . . . . . . . . omreport chassis pwrmanagement or omreport mainsystem pwrmanagement . . . . 58 . . . . . . 62 omreport chassis pwrmonitoring or omreport mainsystem pwrmonitoring . . . . . . . . . .
omreport system recovery or omreport servermodule recovery . . . . . . . . . . . . . . . 80 omreport system shutdown or omreport servermodule shutdown . . . . . . . . . . . . . . 80 omreport system summary or omreport servermodule summary . . . . . . . . . . . . . . 80 omreport system thrmshutdown or omreport servermodule thrmshutdown . . . . . . 88 . . . . . . . 88 . . . . . . . . . . . 90 omreport system version or omreport servermodule version . . . . . . . .
omconfig chassis memorymode or omconfig mainsystem memorymode . . . . . . . . omconfig chassis pwrmanagement or omconfig mainsystem pwrmanagement 129 . . . . . . 132 omconfig chassis pwrmonitoring or omconfig mainsystem pwrmonitoring . . . . . . . 134 omconfig chassis remoteaccess or omconfig mainsystem remoteaccess . . . . . . . 136 omconfig chassis temps or omconfig mainsystem temps . . . . . . . . . . . . . . . . . 150 . . . . . . . . 152 . . . . . . . . . . . . . . . . .
omconfig system thrmshutdown or omconfig servermodule thrmshutdown . . . . . . . . . 5 omconfig system or servermodule assetinfo: Editing Cost of Ownership Values . . . . . . . . . . . . . . . . . . . . . . . . User Level Required for Adding Asset Information . . . . . . . . . . . . . . Adding Acquisition Information . . . . . . . . . . . . . 177 . . . . 179 . . . . . . . . . . . . 180 Adding Extended Warranty Information . . . 181 . . . . . . . .
Adding Service Contract Information . Example Command for Adding Service Information . . . . . . . . . . . . . . . Adding Support Information . . . . . . . 190 . . . . . . . . . . . . . . 190 Example Command for Adding Support Information . . . . . . . . . . . . . . . Adding System Information . . . . . . 191 . . . . . . . . . . . . . . . 192 Example Command for Adding System Information . . . . . . . . . . . . . . . Adding Warranty Information . . . . . . 193 . . . . . . . . . . . . . .
omreport Fan Status . . . . . . . . . . . . . . . . omreport Power Supply Status . omreport EMM Status . . . . . . . . . . 209 . . . . . . . . . . . . . . . 210 omreport Enclosure Slot Occupancy Report . omreport Battery Status . . . 211 . . . . . . . . . . . . . . . . . 211 omreport Global Information (Smart Thermal Shutdown Status, Hot Spare Protection Policy) omreport Connector Status . . . . 212 . . . . . . . . . . . . . . . 213 omreport Cachecade Status . omreport PCIe SSD Status .
omconfig Cancel Rebuild Physical Disk . . . . . . 226 . . . . . . . . 226 . . . . . . . . . . . 227 omconfig Cancel Replace Member omconfig Clear Physical Disk omconfig Cancel Clear Physical Disk . . . . . . . 227 omconfig Enable Device Write Cache . . . . . . . 228 . . . . . . 229 . . . . . . . . . . 229 omconfig Disable Device Write Cache omconfig Export Reliability Log omconfig Convert RAID to Non-RAID . . . . . . . 230 omconfig Convert Non-RAID to RAID . . . . . . .
omconfig Reactivate Fluid Cache on Virtual Disk . . . . . . . . . . . . . . . . . . . . . 249 omconfig Controller Commands . . . . . . . . . . . . . 249 omconfig Rescan Controller . . . . . . . . . . . . 252 omconfig Enable Controller Alarm . . . . . . . . . 252 . . . . . . . . 253 omconfig Quiet Controller Alarm . . . . . . . . . . 253 omconfig Test Controller Alarm . . . . . . . . . .
omconfig Convert Multiple RAID to Non-RAID . . . . . . . . . . . . . . . . . . . . . omconfig Convert Multiple Non-RAID to RAID . . . . . . . . . . . . . . . . . . . Omconfig Enclosure Commands 273 . . . . . 273 . . . . . . . . . . . . 274 . . . . . . . . . 275 omconfig Disable Enclosure Alarm . . . . . . . . 275 omconfig Set Enclosure Asset Tag . . . . . . . . 276 omconfig Enable Enclosure Alarm omconfig Set Enclosure Asset Name omconfig Set Temperature Probe Thresholds . . . . . . . . . .
omconfig Unblink Cachecade . . . . . . . . . . . 288 omconfig Delete Cachecade . . . . . . . . . . . . 288 omconfig Resize Cachecade . . . . . . . . . . . . 289 omconfig Rename Cachecade omconfig PCIe SSD Commands . . . . . . . . . . . 290 . . . . . . . . . . . . . 290 omconfig Add PCIe SSD Device to Cachepool . . . . . . . . . . . . . . . . . . . . . omconfig Remove PCIe SSD Device From Cachepool . . . . . . . . . . . . . . . . . . . . . 291 . . . . . . 292 . . . . . . . . . . .
Table (tbl) Semicolon-separated Values (ssv) Custom Delimited Format (cdv) Index 300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 . . . . . . . . . . 301 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
1 Introduction Overview Dell OpenManage Server Administrator (OMSA) provides a comprehensive, one-to-one systems management solution through either an integrated Web browser-based graphical user interface (GUI) or a command line interface (CLI). Server Administrator is designed for system administrators to manage systems locally and remotely on a network. It allows system administrators to focus on managing their entire network by providing a comprehensive one-toone systems management.
The reporting and viewing features enable retrieval of the overall health status for systems on the network. You can view information about voltage, temperature, fan's revolutions per minute (RPM), memory functioning, and many other critical details at the component level. You can also see a detailed account of the cost of ownership (COO) about the system, retrieve version information about the BIOS, firmware, operating system, and all installed software.
• – Red Hat Enterprise Linux 6 SP2 (64-bit) – Red Hat Enterprise Linux 6 SP3 (64-bit) – Novell SUSE Linux Enterprise Server 11 SP2 (64-bit) Added support for the following platforms: – • Dell PowerEdge R720, R820, R620, and T620 Added support for the following browsers: – Internet Explorer 10 – Mozilla Firefox 10, 11, and 12 NOTE: For the supported operating systems list, see the Dell Systems Software Support Matrix at dell.com/support/manuals.
The omconfig command writes values that you assign to an object's properties. You can specify values for warning thresholds on components or prescribe action that the system must perform when a certain warning or failure event occurs. You can also use the omconfig command to assign specific values to the system's asset information parameters, such as the purchase price of the system, the system's asset tag, or the system's location. The omhelp command displays short text help for CLI commands.
corresponding CLI syntax, see the Dell Update Packages for Operating Systems User’s Guide or the Dell OpenManage Server Update Utility User’s Guide at dell.com/support/manuals. Additional useful topic about the CLI include: • "Working With CLI Command Results" on page 295 CLI Error Checking and Error Messages When you type CLI commands, the CLI checks these commands for correct 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 required to execute the command successfully. If you execute a command for a component or feature that is not present in the system configuration, the error message states that the component is not present. Command: omconfig chassis volts index=3 minwarnthresh= 3.
Scripting and Comparing Using CLI The Server Administrator CLI allows administrators to write batch programs for 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.
Command Syntax Overview Commands vary in complexity. The simplest command has only command level 1. The omhelp command is a simple command. When you type omhelp, a list of the main CLI commands is displayed. The next level of complexity includes commands that contain command levels 1 and 2. All of the about commands are examples of command level 2 complexity. The omconfig about and omreport about commands display a very brief summary.
In each chapter of this document, command syntax and other information about the commands are formatted using any of the following fields as appropriate: command level 1 command level 2 command level 3 name=value pair 1 name=value pair 2 Introduction 25
Introduction
Using the omhelp Command 2 The omhelp command and its equivalent, -?, accesses the detailed help text interface of command line interface (CLI). 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.
• recovery • shutdown • thrmshutdown • webserver Figure 2-1 shows the levels of help for a command. Figure 2-1. Different Levels of Help for a Command 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.
For one info value, specify one or more optional parameter(s.) Table 2-1 lists the optional parameters for info=acquisition: Table 2-1.
Using the omhelp Command
3 omreport: Viewing System Status Using the Instrumentation Service The omreport command allows you to see detailed information about the system components. You can also retrieve summaries for many system components at one time, or 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.
Conventions for Parameter Tables When listing the parameters for a command, the parameters are listed in alphabetical order instead of the order in which they appear in the command line interface (CLI). The symbol |, often called pipe, is the logical exclusive or operator. For example, enable | disable means enable or disable the component or feature.
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport Command Command Level 2 Level 1 Command Level 3 User Use Privilege Required omreport modularenclosure U, P, A Displays the information for all the modular chassis. about U, P, A Displays the version number and properties for Server Administrator. U, P, A Displays the information for all the Server Administrator programs installed. U, P, A Displays the general status of all the main components.
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport (continued) Command Command Level 2 Level 1 34 Command Level 3 User Use Privilege Required fans U, P, A Displays the status and thresholds for system fans. firmware U, P, A Displays the name and version of the firmware. frontpanel U, P, A Displays whether the front panel button settings, such as the Power button and/or Nonmasking Interrupt (NMI) button (if present on the system), are enabled or disabled.
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport (continued) Command Command Level 2 Level 1 Command Level 3 User Use Privilege Required leds U, P, A Displays the properties you have set for light-emitting diodes to flash under various alert conditions. memory U, P, A Displays properties of the system's memory arrays. nics U, P, A Displays the NIC and Team interface properties.
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport (continued) Command Level 3 User Use Privilege Required remoteaccess U, P, A Displays general information on remote access. slots U, P, A Displays the properties of the system’s expansion slots and other slot types. temps U, P, A Displays the status and thresholds for the system temperature sensors. volts U, P, A Displays the status and thresholds for the system voltage sensors.
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport (continued) Command Command Level 2 Level 1 Command Level 3 User Use Privilege Required alertlog U, P, A Allows the administrator to display the alert log. assetinfo U, P, A Displays the cost of ownership information for the system. cmdlog U, P, A Allows the administrator to display the command log. esmlog U, P, A Allows the administrator to display the hardware log.
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport (continued) Command Command Level 2 Level 1 preferences 38 Command Level 3 User Use Privilege Required summary U, P, A Displays the key facts for all system components, including main system chassis, software, and storage. thrmshutdown P, A Displays how to perform the shutdown action, if any, when a temperature warning or failure condition is detected. version U, P, A Displays a summary for all updatable components on the 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 about, chassis, and system commands. The following information on omreport system -? also applies to get help for the omreport chassis command. To see a list of valid commands for omreport system, type: omreport system -? | more omreport modularenclosure Use the omreport modularenclosure command to view details of the Blade system.
CMC Information Attribute : Product Value : Chassis Management Controller (CMC) Attribute : Description Value : The system component provides a complete set of remote management functions for Dell systems. Attribute : Version Value : 3.20 Attribute : IP Address Value : 101.102.103.
Server Administrator includes a number of services, each of which has a version number of its own. The Contains field reports version numbers for the services as well as other useful details. The following output is an example, and can change depending on the system’s configuration and the version of Server Administrator installed on the system: Contains: Instrumentation Service 7.x.x Storage Management 4.x.x Sun Java Runtime Environment 1.x.x_xx Secure Port Server 7.x.x Server Administrator Core Files 7.x.
Server Administrator displays a general status for the main system chassis or main system components. Health Main System Chassis SEVERITY Ok Critical Ok Ok Ok Ok : COMPONENT : Fans : Intrusion : Memory : Power Supplies : Temperatures : Voltages omreport chassis acswitch or omreport mainsystem acswitch Use the omreport chassis acswitch or omreport mainsystem acswitch command if the system has redundant AC power lines that are configured in a failover arrangement.
AC Present Active Source Status Location AC Present Active Source : : : : : : Power Present Active Ok AC Power Line 2 Power Present Not Active Server Administrator reports values for the Redundancy Status and Redundancy Mode fields. omreport chassis batteries or omreport mainsystem batteries Use the omreport chassis batteries or omreport mainsystem batteries command to view battery properties.
omreport chassis biossetup or omreport mainsystem biossetup Use the omreport chassis biossetup or omreport mainsystem biossetup command to view BIOS setup parameters that are normally available only during system boot. Type: omreport chassis biossetup or omreport mainsystem biossetup NOTE: To maintain consistency across the commands, the output format of this command has changed. Change the user scripts as applicable.
Table 3-3. BIOS Setup Parameters on Systems Prior to Dell PowerEdge yx2x System (continued) Parameters Description User accessible USB Ports Displays whether the user-accessible USB port is enabled or disabled. CPU Virtualization Technology Displays the additional hardware capabilities provided by Virtualization Technology. AC Power Recovery Mode Displays the system state when input power is restored after an outage.
Table 3-3. BIOS Setup Parameters on Systems Prior to Dell PowerEdge yx2x System (continued) Parameters Description Operating System Watchdog Timer Displays whether the operating system watchdog timer is enabled or disabled. HT Assist Displays the status of the probe filter chipset option. Internal SD Card Displays whether the internal SD card is enabled or disabled. Bezel Displays whether the bezel removal intrusion check during system reboot is enabled or disabled.
Table 3-3. BIOS Setup Parameters on Systems Prior to Dell PowerEdge yx2x System (continued) Parameters Description 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 3-4 lists the available groups of the BIOS setup parameters on PowerEdge yx2x systems. NOTE: Based on the hardware configuration, the attributes may vary in a specific group. Table 3-4. BIOS Setup Groups on PowerEdge yx2x Systems Group Description BIOS Boot Settings Controls the system boot settings when bootmode is set to bios. Boot Settings Controls the system boot settings when bootmode is set to bios. Embedded Server Management Sets up the Embedded Server Management options.
omreport chassis removableflashmedia or omreport mainsystem removableflashmedia Use the omreport chassis removableflashmedia or omreport mainsystem removableflashmedia to view the removable flash media details on the system along with its health status. Type: omreport chassis removableflashmedia or omreport mainsystem removableflashmedia Server Administrator displays a summary of the system’s removable flash media information.
Status : OK Connector Name : System Board SD Status 2 State : Present Storage Size : 512 MB VFlash Media Details Connector Name : System Board SD Status 1 Type : vFlash SD Card State : Present Available Size : 472 MB Storage Size : 512 MB omreport chassis fans or omreport mainsystem fans Use the omreport chassis fans or omreport mainsystem fans command to view the fan probe status and settings.
Server Administrator displays a summary of the system’s firmware properties. NOTE: To maintain consistency across the commands, the output format of this command has changed. Change the user scripts as applicable. NOTE: If iDRAC is installed, Server Administrator displays the Life Cycle Controller (LCC) version. If BMC is installed, Server Administrator displays the Unified Server Configurator (USC) version.
omreport chassis hwperformance or omreport mainsystem hwperformance Use the omreport chassis hwperformance or omreport mainsystem hwperformance command to view the status and cause for the system’s performance degradation. When you type: omreport chassis hwperformance or omreport mainsystem hwperformance Server Administrator displays a summary of the system’s hardware performance degradation information. NOTE: This command is applicable only to selected Dell yx0x systems that support PMBus.
The index parameter specifies a chassis number and is optional. If you do not specify the index, Server Administrator displays summary chassis information for each chassis. If you specify the index, Server Administrator displays summary information for a specific chassis. NOTE: If iDRAC is installed, Server Administrator displays the LCC version. If BMC is installed, Server Administrator displays the USC version.
A message that resembles the following is displayed: Intrusion Information Health : Ok Index : 0 Status : OK Probe Name : Intrusion State : Chassis is closed omreport chassis leds or omreport mainsystem leds Use the omreport chassis leds or omreport mainsystem 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 or omreport mainsystem leds index=n The index parameter is optional.
omreport chassis memory or omreport mainsystem memory Use the omreport chassis memory or omreport mainsystem memory to view details for each memory module slot in the system. If the system supports redundant memory, this command also displays the status, state, and type of memory redundancy implemented on the system. Type: omreport chassis memory index=n or omreport mainsystem index=n The index parameter is optional.
If the system supports redundant memory, the redundancy output may resemble the following: Memory Redundancy Redundancy Status Fail Over State Redundancy Configuration Attributes of Memory Array(s) Attributes Memory Array 1 Attributes Memory Array 1 Attributes Memory Array 1 Attributes Memory Array 1 Attributes Memory Array 1 Attributes Memory Array 1 Attributes Memory Array 1 : Full : Inactive : DDDC : : : : : : : : : : : : : : Location System Board or Motherboard Use System memory Installed Capacity 13
The index parameter is optional. If you do not specify the index, Server Administrator displays properties of all NICs on the system and the values for the following fields: Index (NIC card number), Interface Name, Vendor, Description, Connection Status, and Slot.
Port Type is the detailed type of each system port, from the more general serial, parallel, and USB ports to the names of ports by device type connected to it, for example, pointing device or keyboard. External Name is the name of the port, such as serial or parallel, USB, mouse, keyboard, and so on. Base I/O Address is the starting I/O address expressed in hexadecimal. IRQ Level is a hardware interrupt on a system.
Current Speed is the actual processor speed in MegaHertz at system boot time. State is whether the processor slot is enabled or disabled. Core Count is the number of processors integrated into one chip. Capabilities and Cache Properties of a Specific Processor To view the cache properties of a processor on a given connector, type: omreport chassis processors index=n or omreport mainsystem processors index=n The index parameter is optional.
The following fields are defined for a cache present on a particular microprocessor. If the cache is internal to the processor, the fields do not appear in the cache report: • Speed • Cache Device Supported Type • Cache Device Current Type • External Socket Name NOTE: Due to the limitations of certain operating systems (for example, VMware ESXi), certain features are not available with this release of OpenManage Server Administrator.
A Write Policy describes how the cache deals with a write cycle. In a write-back policy, the cache acts like a buffer. When the processor starts a write cycle, the cache receives the data and stops the cycle. The cache then writes the data back to the main memory when the system bus is available. In a write-through policy, the processor writes through the cache to the main memory. The write cycle does not complete until the data is stored into the main memory.
omreport chassis pwrmanagement or omreport mainsystem pwrmanagement Use the omreport chassis pwrmanagement or omreport mainsystem pwrmanagement command to view the power budget cap and power management profiles of the system. The values display either in Watts or BTU/Hr based on the configuration. Type: omreport chassis pwrmanagement or omreport mainsystem pwrmanagement NOTE: To maintain consistency across the commands, the output format of this command has changed. Change the user scripts as applicable.
The following is an example output: Power Inventory and Budget Power Inventory System Idle Power : 0 W System Maximum Potential Power : 0 W Attribute Values : : Enable Power Cap Enabled Attribute Values : : Power Cap 400 W (56%) Power Budget NOTE: Power budget requires license to report the details. If the appropriate license is not installed or has expired, the system does not display the power budget details. For more information, see The Dell Licensing Management Guide at dell.
• Failure Threshold • Amperage: Location and Reading • Power Tracking Statistics • Energy Consumption • Measurement Start Time • Measurement Finish Time • Reading • System Peak Power • System Peak Amperage NOTE: The omreport chassis pwrmonitoring or omreport mainsystem pwrmonitoring command is applicable from PowerEdge yx0x system onwards that support PMBus and that have hot-swappable power supplies and not systems that have a fixed, non-redundant power supply installed.
The following is an example output: Power Consumption Information Power Consumption Index : 1 Status : Ok Probe Name : System Board Pwr Consumption Reading : 539W Warning Threshold : 994W Failure Threshold : 1400 W Amperage PS1 Current 1 : 1.
Power Tracking Statistics Statistic : Energy consumption Measurement Start Time : Thu May 28 11:03:20 2011 Measurement Finish Time : Fri May 28 11:05:46 2011 Reading : 5.9 KWH Statistics : System Peak Power Measurement Start Time : Mon May 18 16:03:20 2011 Peak Time : Wed May 27 00:23:46 2011 Peak Reading : 630 W Statistics : System Peak Amperage Measured Since : Mon May 18 16:03:20 2011 Read Time : Tue May 19 04:06:32 2011 Peak Reading : 2.
omreport chassis pwrsupplies or omreport mainsystem pwrsupplies Use the omreport chassis pwrsupplies or omreport mainsystem pwrsupplies command to view properties of the system’s power supplies. Type: omreport chassis pwrsupplies or omreport mainsystem pwrsupplies NOTE: To maintain consistency across the commands, the output format of this command has changed. Change the user scripts as applicable.
The output of the omreport chassis remoteaccess or omreport mainsystem remoteaccess command lists each of the valid parameters. Table 3-6 lists the available settings. Table 3-6. Valid parameters of omreport chassis remoteaccess or omreport mainsystem remoteaccess name=value pair Description config=additional Reports the current state of IPv4 and IPv6 addresses on iDRAC. config=advsol Reports advanced BMC/iDRAC or remote access information on a serial over local area network (LAN) connection.
For each slot in the system, values display for the following fields: Index, Slot ID, Adapter, and Data Bus Width. Index is the number of the slot in the system. Slot ID is the silk screen name printed on the system's motherboard next to the slot. Alphanumeric text uniquely identifies each slot in the system. Adapter refers to the name and/or type of the card that fits into the slot, for example, a storage array controller, SCSI adapter, iDRAC Enterprise, or HBA.
omreport system Commands or omreport servermodule Commands Use the omreport system or omreport servermodule command to view logs, threshold values, cost of ownership information, and information about how shutdown actions and recovery actions are configured. omreport system or omreport servermodule Use the omreport system or omreport servermodule command to see a general status of the components of the system.
Commands for Viewing Logs Use the omreport system or omreport servermodule command to view logs: the alert log, the command log, and the hardware or ESM 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), you must clear the log and resolve the issue. To clear the log, type: omconfig system alertlog action=clear or omconfig system cmdlog action=clear.
Overall Health Status of the ESM Log When you run the omreport system esmlog or omreport servermodule esmlog command, the ESM log is displayed. The first line of the report reflects the overall health of the system hardware. For example, Health: OK means that less than 80 percent of the space allotted for the ESM log is occupied by messages.
• Current Probe Warning • Current Probe Failure • Fan Warning • Fan Failure • Memory Pre-failure • Memory Failure • System Power Probe Warning • System Power Probe Detects a Failure • System Peak Power • Power Supply Warning • Power Supply Failure • Degraded Redundancy • Lost Redundancy • Temperature Warning • Temperature Failure • Voltage Warning • Voltage Failure • Processor Warning • Processor Failure • Hardware Log Warning • Hardware Log Full • Watchdog Asr •
• Enclosure Warning • Enclosure Failure • Storage Controller Battery Warning • Storage Controller Battery Failure • Removable Flash Media Present • Removable Flash Media Removed • Removable Flash Media Failure NOTE: Storage Controller Battery Warning and Storage Controller Battery Failure events are not available on Blade systems. NOTE: System Power Probe Warning is not applicable to Blade systems.
The following is an example output for a few components: Current SNMP Trap Configuration ----------System ----------Settings Enable: Informational, Warning and Critical Disable: None --------------Power Supplies ---------------Settings Enable: Informational, Warning and Critical Disable: None ----------Fans ----------Settings Enable: Critical Disable: Informational, Warning, and Critical --------------------Removable Flash Media --------------------Settings Enable: Informational, Warning and Critical Disabl
Table 3-7.
----------Fans Group ---------Settings Enable: Informational, Warning, and Critical Disable: None ----------Individual Objects ----------System Board Fan1 RPM Settings Index:0 Enable: Informational, Warning, and Critical Disable: None System Board Fan2 RPM Settings Index:1 Enable: Informational, Warning, and Critical Disable: None omreport system operatingsystem or omreport servermodule operatingsystem Use the omreport system operatingsystem or omreport servermodule operatingsystem command to display infor
Type: omreport system pedestinations or omreport servermodule pedestinations The output of the omreport system pedestinations or omreport servermodule pedestinations command lists each of the valid parameters. NOTE: To maintain consistency across the commands, the output format of this command has changed. Change the user scripts as applicable. NOTE: The actual number of destinations you can configure on the system may differ. Table 3-8 lists the available settings. Table 3-8.
Table 3-8. Settings for the omreport system pedestinations or omreport servermodule pedestinations (continued) Output Attributes Description Destination Number: Destination 4 destination 4: Displays the fourth destination. Example: 210.211.212.213: IPv4 address of the fourth destination. Destination Number: Destination 5 destination 5: Displays the fifth destination. Example: 2001:0db8:85a3:0000:0000:8a2e:0370:7 334: IPv6 address of the fifth destination.
omreport system platformevents or omreport servermodule platformevents Use the omreport system platformevents or omreport servermodule platformevents command to view how the system responds for each listed platform event. NOTE: To maintain consistency across the commands, the output format of this command has changed. Change the user scripts as applicable.
The output that is displayed in the CLI window depends on the systems management software, operating system, and hardware components and options installed on the system. The following partial command results are unique and may not resemble the hardware and software configuration of the system: System Summary ----------------Software Profile ----------------Systems Management Name : Dell OpenManage Server Administrator Version : x.x.
: Server Administrator Core files 7.x.x : Storage Management 4.x.x : Sun Java Runtime Environment 1.x.x Operating System Name : Microsoft Windows Server 2008 R2, Enterprise x64 Edition Version : Version 6.
Express Service Code : 15608862073 Chassis Lock : Present Chassis Asset Tag : c Remote Access Information Remote Access Device : iDRAC7 Express vFlash Media : Absent Processor 1 Processor Brand : Genuine Intel (R) CPU @ 1.
Maximum Capacity : 786432 MB Slots Available : 24 Slots Used :1 Slot PCI1 Adapter : [Not Occupied] Type : PCI E Gen 3 X16 Data Bus Width : 8x or x8 Speed : [Not obtained, see card documentation] Slot Length : Long Voltage Supply : 3.3 Volts Slot PCI2 Adapter : [Not Occupied] Type : PCI E Gen 3 X16 Data Bus Width : 8x or x8 Speed : [Not obtained, see card documentation] Slot Length : Long Voltage Supply : 3.3 Volts BIOS Information Manufacturer : Dell Inc. Version : 0.3.
Firmware Information Name : iDRAC7 Version : 1.00 --------------Network Data --------------Network Interface 0 IP Address : 10.94.22.111 Subnet Mask : 255.255.254.0 Default Gateway : 10.94.22.
----------------Storage Enclosure ----------------Storage Enclosure Name : Backplane The system summary hardware information includes data values for installed components of the following types present in the system: System Attributes • Host Name • System Location • Life Cycle Controller Main System Chassis or Main System Chassis • Chassis Model • Chassis Service Tag • Express Service Code • Chassis Lock • Chassis Asset Tag Remote Access Information • Remote Access Device • vFlash M
• Current Speed • Maximum Speed • External Clock Speed • Voltage 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 •
Network Data The following details are listed for each NIC and Team interface, if Team interface is configured 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 • Service Tag omreport system thrmshutdown or omreport servermodule thrmshutdown Use the omreport system thrmshutdown or omreport servermodule thrmshutdown command to view the properties configured for a
Example Command Output Type: omreport system version or omreport servermodule version NOTE: If iDRAC is installed, Server Administrator displays the LCC version. If BMC is installed, Server Administrator displays the USC version. The output that is displayed in the CLI window depends on the version of the BIOS, RAID controllers, and firmware installed on the system.
-----------------------------------Storage Controller Firmware -----------------------------------Name: PERC H310 Mini Version: 20.10.1-0025 omreport preferences Commands Use the omreport preferences command to view the URL information of the Server Administrator Web server. Table 3-9 lists the available attributes. Table 3-9. Attributes of omreport preferences webserver name=value pair Description attribute=geturl Reports the URL information of the Web server.
4 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 perform other systems management tasks.
Table 4-1. System Availability for the omconfig Command Command Level 1 Command Level 2 Applicable to omconfig servermodule mainsystem system chassis Blade systems Blade systems Rack and Tower systems Rack and Tower systems Conventions for Parameter Tables When listing the parameters that a command can take, the parameters are listed in alphabetical order instead of the order in which they appear in the command line interface (CLI).
Table 4-2. omconfig Command Level 1, Level 2, and Level 3 Command Level 1 Command Level 2 User Privilege Required Use U, P, A Shows version number and properties for the Server Administrator program. details=true U, P, A Displays information for all of the Server Administrator programs that are installed. cdvformat A Specifies the delimiter for separating data fields reported in custom delimited format (cdv). dirservice A Configures the Microsoft Active Directory service.
Table 4-2. omconfig Command Level 1, Level 2, and Level 3 (continued) Command Level 1 94 Command Level 2 Command Level 3 User Privilege Required Use alertaction P, A Determines in advance the actions taken for warning or failure events on intrusion, fans, temperatures, voltages, power supplies, memory, and redundancy. alertlog P, A Allows the administrator to clear the alert log.
Table 4-2. omconfig Command Level 1, Level 2, and Level 3 (continued) Command Level 1 Command Level 2 Command Level 3 User Privilege Required Use shutdown A Allows the administrator to select from several options when shutting down the system. thrmshutdown A Sets the severity level at which a thermal event triggers a system shutdown. webserver A Starts or stops the Web server. biossetup A Configures the behavior of specific system components controlled by the BIOS.
Table 4-2. omconfig Command Level 1, Level 2, and Level 3 (continued) Command Level 1 Command Level 2 Command Level 3 User Privilege Required Use leds P, A Specifies when to flash a chassis fault LED or chassis identification LED, and allows you to clear the LED for the system's hard drive. memorymode A Enables or disables the spare bank, mirroring, raid, and Double Device Data Correction (DDDC) memory modes, and also specify which mode to use.
Table 4-2. omconfig Command Level 1, Level 2, and Level 3 (continued) Command Level 1 Command Level 2 Command Level 3 User Privilege Required Use volts P, A Sets warning threshold values default or a specific value. NOTE: You cannot change threshold values on ESM3 and PowerEdge x8xx systems. storage See "Using the Storage Management Service" on page 197. Help With the omconfig Command Use the omconfig -? command to get a list of the available commands for omconfig.
Use a command of the form omconfig system -? to get a list of the parameters you must use to execute a particular omconfig system command. For example, the following commands produce a list of valid parameters for omconfig system alertaction and omconfig system shutdown: omconfig system alertaction -? omconfig system shutdown -? In case of the omconfig system alertaction command, you can use various options to prevent all of the CLI help from scrolling, before you can read it.
For more details about the environment for Server Administrator, type: omconfig about details=true Server Administrator includes a number of services, each having a version number of its own. The Contains field reports version numbers for the services and provides other useful details. The following is an example output of the omconfig about command. The output may change depending on the configuration of the system and the version of Server Administrator. Contains: Broadcom SNMP Agent 10.xx.
omconfig chassis or omconfig mainsystem Use the omconfig chassis or omconfig mainsystem command to: • Set to default or assign specific values for fan, voltage, and temperature probes • Configure BIOS behavior during system start up • Clear memory error counts • Enable or disable power button control features if system configuration permits Use the omconfig chassis -? or omconfig mainsystem -? command to view a list of all omconfig chassis or omconfig mainsystem commands.
Table 4-3 lists the name=value pairs you can use with this command on systems prior to PowerEdge yx2x systems. Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems name=value pair 1 name=value pair 2 attribute= setting= attribute= acpwrrecovery Description setting=off | last| on off: System is turned off. last: System returns to the previous state. on: System is turned on. delay=random | random: System is turned on with immediate | timedelay random delay.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= attribute= bootorder Description sequence=aliasname1, Configures the boot sequence according aliasname2,..... to the set aliasnames. To view the set aliasnameN alias names, run the command omreport chassis biossetup attribute= bootorder.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute= conredirect enabled: Redirects the BIOS screen output over serial port 1. Keyboard and text output are redirected over serial port 2. setting=enabled | disabled disabled: Turns off the BIOS console redirection. attribute=crab setting=enabled | disabled enabled: Enables BIOS console redirection after system reboot.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute= cpuxdsupport enabled: Enables Execute Disable (XD) support on the system. setting=enabled | disabled disabled: Disables XD support on the system. attribute=cpucore setting=1 | 2 | 4 | 6 | 1: Enables one core per processor. 8 | 10 | 12 |all 2: Enables two cores per processor. 4: Enables four cores per processor.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute=dualnic setting=off | on | pxeboth | nic1pxe |nic2pxe | isciboth | nic1isci | nic2isci | nic1pxenic2isci | nic1iscinic2pxe | onpxeboth | onpxenone | off: Disables the Network Interface Controllers (NICs). on: Enables the network interface (PXE or iSCSI is not enabled on either of the NICs). pxeboth: Enables PXE on both NICs.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute= embhypvisor enabled: Enables the embedded hypervisor. setting=enabled | disabled disabled: Disables the embedded hypervisor. attribute= embvideoctrl setting=enabled | disabled enabled: Enables the embedded video controller as the primary video device. disabled: Disables the embedded video controller as the primary video device.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute=htassist setting=enabled | disabled enabled: Enables the probe filter chipset option. disabled: Disables the probe filter chipset option. NOTE: Certain applications do not function fully if you enable or disable this option. attribute=ide setting=on | off force=true on: Enables IDE. off: Disables IDE.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute=nic1 enabled: Enables the first NIC during system boot. setting=enabled | enabledwithpxe | disabled | enabledonly | enablednonepxe | enabledwithiscsi enabledwithpxe: Enables the first NIC during system boot (with PXE on if the system has PXE). disabled: Disables the first NIC during system boot.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute=nic3 enabled: Enables the third NIC during system boot. setting=enabled | enabledwithpxe | disabled | enabledonly | enablednonepxe | enabledwithiscsi enabledwithpxe: Enables the third NIC during system boot (with PXE on if the system has PXE). disabled: Disables the third NIC during system boot.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute= numlock setting=on | off on: Uses the keypad as number keys. attribute=numa setting=enabled | disabled enabled: Enables Node Interleaving. setting=off | lpt1 | lpt2 | lpt3 off: Disables the parallel port address. attribute= ppaddress off: Uses the keypad as arrow keys. disabled: Disables Node Interleaving.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute=romb raid: Instructs the BIOS to detect RAID-on-motherboard as a RAID device. setting=raid | off | scsi force=true off: Disables RAID-on-motherboard during system boot. scsi: Instructs the BIOS to detect the RAID-on-motherboard device as a SCSI device. force=true: Verification of setting change.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute=sataport setting=off | auto (0...7) or (a...h) off: Disables the SATA port. attribute= secondaryscsi setting=on | off on: Enables secondary SCSI. attribute= serialportaddr setting=default | alternate | com1 | com2 auto: Automatically enable the SATA port. off: Disables secondary SCSI.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= Description attribute= serialport1 off: Disables serial port 1. setting=off | auto | com1 | com3 | bmcserial | bmcnic | rac | com1bmc auto: Maps serial port 1 to a COM port. com1: Maps serial port 1 to COM port 1. com3: Maps serial port 1 to COM port 3. bmcserial: Maps serial port 1 to BMC Serial.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge yx2x Systems (continued) name=value pair 1 name=value pair 2 attribute= setting= attribute=uausb Description setting=on | backonly on: Enables the user-accessible | off USB port(s.) backonly: Enables only the useraccessible USB port(s) located at the back of the system. off: Disables the user-accessible USB port(s.) attribute=usb setting=enabled | disabled enabled: Enables the USB port(s.) disabled: Disables the USB port(s.
Table 4-4 displays the BIOS setup attributes supported on PowerEdge yx2x systems. On PowerEdge yx2x systems, the attributes are grouped. Based on the hardware configuration, the possible attributes may vary in a specific group. The omconfig chassis biossetup command does not display the readonly attributes. NOTE: If you have configured the setup password, then, always set the same when you configure any BIOS settings. Table 4-4.
Table 4-4.
Table 4-4. BIOS Setup Settings on PowerEdge yx2x Systems (continued) Group name=value pair 1 attribute= name=value pair 2 setting= Miscellaneous Settings (continued) attribute=SystemUefiShell setting=Enabled | Disabled One-Time Boot attribute= OneTimeBootMode setting=Disabled | OneTimeBootSeq | OneTimeHddSeq | OneTimeUefiBootSeq | OneTimeCustomBootSeqStr | OneTimeCustomHddSeqStr | OneTimeCustomUefiBootSeqStr attribute= OneTimeBootSeqDev sequence=aliasname1, aliasname2,.....
Table 4-4.
Table 4-4.
Table 4-4.
Table 4-4.
Table 4-4.
Table 4-4.
Table 4-4. BIOS Setup Settings on PowerEdge yx2x Systems (continued) Group name=value pair 1 attribute= UEFI Boot Settings attribute=UefiBootSeq name=value pair 2 setting= sequence=aliasname1, aliasname2,..... aliasnameN omconfig chassis currents or omconfig mainsystem currents NOTE: This command is no longer available through Server Administrator. omconfig chassis fans or omconfig mainsystem fans Use the omconfig chassis fans or omconfig mainsystem fans command to set fan probe warning thresholds.
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. To set both the upper and lower fan warning threshold values to the recommended default value, type: omconfig chassis fans index=0 warnthresh=default or omconfig mainsystem fans index=0 warnthresh= default NOTE: You cannot default one value and set another.
When you issue the command and the system sets the values you specify, the following message is displayed: Fan probe warning threshold(s) set successfully. NOTE: You cannot set the minimum and maximum warning thresholds for the fan probe on PowerEdge x8xx and x9xx systems.
Table 4-6 lists the valid parameters for the command. Table 4-6.
omconfig chassis info or omconfig mainsystem info Use the omconfig chassis info or omconfig mainsystem info command to enter an asset tag name and a chassis name for the system. For a Blade systems, enter asset tag names for modular components as well. Table 4-7 lists the valid parameters for the command. Table 4-7. Parameters of omconfig chassis info or omconfig mainsystem info name=value pair Description index= tag= Number of the chassis whose asset tag or name you are setting.
For some chassis, you can assign a different name. You cannot rename the main system chassis. In the following example, the command renames chassis 2 from storscsi1 to storscsia: omconfig chassis info index=2 name=storscsia or omconfig mainsystem info index=2 name=storscsia As with other commands, the CLI displays 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.
Redundant memory enables a system to switch to other available memory modules if unacceptable errors are detected in the modules that the system is currently using. The omconfig chassis memorymode or omconfig mainsystem memorymode command allows you to disable redundancy; when you disable redundancy, you instruct the system not to switch to other available memory modules when the module the system is using begins to encounter errors. To enable redundancy, choose among spare, mirror, RAID, and DDDC.
Table 4-9 lists the valid parameters for the command. Table 4-9. Parameters of omconfig chassis memorymode or omconfig mainsystem memorymode name=value pair 1 index= Description Number of the chassis where the memory module resides (the default is chassis 0, the main system chassis). redundancy=spare spare: Disables the memory module that has a correctable | mirror | disabled memory event and copies the failing module’s data to a spare | raid5 | dddc bank.
omconfig chassis pwrmanagement or omconfig mainsystem pwrmanagement Use the omconfig chassis pwrmanagement or omconfig mainsystem pwrmanagement command to configure power cap and manage profiles that control power utilization. NOTE: This command is valid only on systems prior to PowerEdge yx2x systems. Table 4-10 lists the valid parameters for the command. Table 4-10.
Table 4-10. Parameters of omconfig chassis pwrmanagement or omconfig mainsystem pwrmanagement (continued) name=value pair 1 name=value pair 2 config=profile profile= maxperformance: Sets the processor maxperformance| apc to the highest supported processor | osctrl | custom state. It offers maximum performance mode with minimal power economy. NOTE: This option is supported on systems prior to PowerEdge yx2x systems.
Table 4-10. Parameters of omconfig chassis pwrmanagement or omconfig mainsystem pwrmanagement (continued) name=value pair 1 name=value pair 2 Description memorypowermode= min: Sets the mode to minimum min | 800 | 1067 | power utilization. 1333 | max 800 | 1067 | 1333: Set the mode to 800, 1067, or 1333 MHz. max: Sets the mode to maximum performance. NOTE: These options are applicable fanmode=min | max only when a custom profile is selected. min: Sets the mode to minimum power utilization.
Table 4-11. Parameters of omconfig chassis pwrmonitoring or omconfig mainsystem pwrmonitoring (continued) name=value pair 1 name=value pair 2 config=resetreading type=energy | peakpower Description energy: Resets the system energy reading. peakpower: Resets the system peak power. NOTE: This command is applicable to selected Dell yx0x systems that support PMBus only. NOTE: Power monitoring requires license to configure the power budget information.
Specify a Value for Warning Thresholds If you prefer to specify values for the power consumption probe warning thresholds, you must specify the number of the probe you are configuring and the warning threshold value. Configure the values to display either in BTU/hr or Watts.
The output of the omconfig chassis remoteaccess or omconfig mainsystem remoteaccess command lists each of the available configurations. The following table lists the valid parameters: Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess name=value pair 1 name=value pair 2 config= Description config= additional ipv4=enable | disable enable: IPv4 stack to load on iDRAC. ipv6=enable | disable disable: IPv4 stack to flush on iDRAC.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= Description nicselection= sharedwithfailoveronall: Configures the sharedwithfailoveronall | new NIC selection option. nic1 |teamednic1nic2 | nic1: Enables NIC 1. dracnic teamednic1nic2: Enables NIC teaming functionality. dracnic: Enables DRAC NIC if DRAC 5 is installed.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= Description failovernw=none | lom1 | none: Configures the failover network to lom2 | lom3 | lom4 | all none. lom 1:Configures the failover network to lom 1. lom 2: Configures the failover network to lom 2. lom 3: Configures the failover network to lom 3. lom 4: Configures the failover network to lom 4. all: Configures the failover network to all loms.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= Description ipsource=static | dhcp | static: Static if the IP address of the systemsoftware 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.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= config=nic (continued) Description privilegelevel= administrator: Sets the maximum administrator | operator | privilege level that is accepted on a LAN user channel to Administrator. operator: Sets the maximum privilege level that is accepted on a LAN channel to Operator.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= config=serial Description baudrate=9600 | 19200 | 9600: Sets the connection speed to 9600 38400 | 57600 | 115200 bits per second. 19200: Sets the connection speed to 19200 bits per second. 38400: Sets the volatile and non-volatile connection speed to 38400 bits per second. 57600: Sets the volatile and non-volatile connection speed to 57600 bits per second.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= Description config=serial (continued) directbasic: Type of messaging used for IPMI messaging over a serial connection.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= Description config= serialoverlan true: Enables serial over LAN for the BMC. enable=true | false false: Disables serial over LAN for the BMC. baudrate=9600 | 19200 | 9600: Sets the volatile and non-volatile 38400 | 57600 | 115200 connection speed to 9600 bits per second. 19200: Sets the volatile and non-volatile connection speed to 19200 bits per second.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= Description privilegelevel= administrator: Sets the maximum administrator | operator | privilege level that is accepted on a serial user over LAN channel, to Administrator. operator: Sets the maximum privilege level that is accepted on a serial over LAN channel, to Operator.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= Description newlinesequence=none| none: BMC does not use a crlf | null | cr | lfcr | lf termination sequence. crlf: BMC uses as a new line sequence when the BMC writes a new line to the console. null: BMC uses as a new line sequence when the BMC writes a new line to the console.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= Description id=number newpw=text id=number: ID (in numeric format) of the user being configured. confirmnewpw=text newpw=text: New password of the user. confirmnewpw=text: Confirm the new password. id=number: ID (in numeric format) of the user being configured.
Table 4-12. Parameters of omconfig chassis remoteaccess or omconfig mainsystem remoteaccess (continued) name=value pair 1 name=value pair 2 config= id=user id dracusergroup=admin | poweruser | guest | custom | none Description id=user id: User ID of the user being configured. dracusergroup=admin: Enables the Administrator user privileges. dracusergroup=poweruser: Enables the Power User privileges. dracusergroup=guest: Enables the Guest User privileges.
Usage of dracusergroup=custom The following table displays the usage of dracusergroup=custom: Table 4-13. Parameters of omconfig chassis remoteaccess config=user id= dracusergroup=custom or omconfig mainsystem remoteaccess config=user id= dracusergroup=custom name=value pair 1 name=value pair 2 config=user name=value pair 3 id=user id logindrac= true | dracusergroup= false custom configuredrac= true | false Description true or false: Enables or disables logging into DRAC.
Usage of extipmiusergroup=custom The following table displays the usage of extipmiusergroup=custom: Table 4-14. Parameters of omconfig chassis remoteaccess config=user id= extipmiusergroup=custom or omconfig mainsystem remoteaccess config= user id= extipmiusergroup=custom name=value pair 1 name=value pair 2 name=value pair 3 config=user loginidrac= true | true or false: Enables false or disables logging configureidrac= into iDRAC.
Setting the Minimum and Maximum Warning Threshold Values to Default To set both the maximum and minimum temperature warning threshold values to the recommended default value, type: omconfig chassis temps index=0 warnthresh=default or omconfig mainsystem temps index=0 warnthresh= default NOTE: You cannot default one value and set another. In other words, if you set the minimum warning threshold value to the default value, you are also selecting the default value for the maximum warning threshold value.
omconfig chassis volts or omconfig mainsystem volts Use the omconfig chassis volts or omconfig mainsystem volts command to set voltage probe warning thresholds. As with the other components, you can view both the warning and failure threshold values, but you cannot set the failure threshold values. The system manufacturer sets the minimum and maximum values for the failure thresholds.
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. NOTE: Systems that contain ESM3 capabilities do not allow you to set warning threshold values to default values.
The following example shows how to set the delimiter for separating data fields to asterisk: omconfig preferences cdvformat delimiter=asterisk omconfig preferences dirservice Use the omconfig preferences dirservice command to configure the Active Directory service. The oem.ini file is modified to reflect these changes. If the "adproductname" is not present in the oem.ini file then a - default value is used.
omconfig preferences snmp Setting the SNMP root password allows administrators to restrict access to SNMP set operations that allow important systems management interventions. You can configure the SNMP root password normally (by typing all of the parameters in one command line) or interactively. Using the omconfig preferences snmp command, you can also configure SNMP set operations.
Table 4-19. SNMP Set Operations Parameters name=value pair setting=snmpset enable=true enable=false Description Required Enables SNMP set operations Disables SNMP set operations For example, to disable SNMP set operations use the following command: omconfig preferences snmp setting=snmpset enable= false NOTE: After executing the command to enable or disable SNMP set operations, restart services for the change to take effect.
omconfig preferences webserver Use the omconfig preferences webserver command to set the encryption levels of the Server Administrator Web server and configure the URL launch point in the Server Administrator Web server environment. Table 4-21 lists the parameters you can use with this command. Table 4-21.
omconfig system or omconfig servermodule Use the omconfig system or omconfig servermodule 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.
The event is a power supply failure and the action is to broadcast a message to all Server Administrator users. Available Alert Actions Table 4-22 lists the alert actions for each component that allows you to configure an alert action. Table 4-22. Alert Actions You Can Set for Warning and Failure Events Alert Action Setting Description alert=true | false true: Enables the system's console alert.
Table 4-23. Events for Which You Can Set Alert Actions Event Name Description event=batterywarn Sets actions when a battery probe detects a warning value. Sets actions when a battery probe detects a failure value. Sets actions when a fan probe detects a warning value. Sets actions when a fan probe detects a failure value. Sets actions when a hardware log detects a warning value. Sets actions when a hardware log is full. Sets actions when a chassis intrusion event is detected.
Table 4-23. Events for Which You Can Set Alert Actions (continued) Event Name Description event=tempwarn Sets actions when a temperature probe detects a warning value. event=tempfail Sets actions when a temperature probe detects a failure value. event=voltwarn Sets actions when a voltage probe detects a warning value. event=voltfail Sets actions when a voltage probe detects a failure value.
Table 4-23. Events for Which You Can Set Alert Actions (continued) Event Name Description event=storagectrlbatteryfail Sets actions when a storage controller battery detects a failure value. NOTE: This event is not available on Blade systems. Example Set Alert Action Commands The following examples are valid example commands. For each successful command issued, the following message is displayed: Alert action(s) configured successfully.
• For Chassis Intrusion Actions To clear all alert actions for chassis intrusion, type: omconfig system alertaction event=intrusion clearall=true or omconfig servermodule 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 at dell.com/support/manuals.
omconfig system pedestinations or omconfig servermodule pedestinations Use the omconfig system pedestinations or omconfig servermodule pedestinations command to set IP addresses for alert destinations. Table 4-24 lists the valid parameters for the command. NOTE: You can either specify the index and IP address as parameters together or you can set the community string alone as a parameter. NOTE: Index 1 to 4 accepts an IPv4 address and index 5 to 8 accepts an IPv6 address. Table 4-24.
Table 4-25 lists the valid parameters for the command. NOTE: Alert settings are mutually exclusive and you can set one at a time only. The action settings are also mutually exclusive and you can set one at a time only. However, alert and action settings are not mutually exclusive of each other. Table 4-25. Parameters for Alert Action Command Action Description action=disable action=enable action=none action=powercycle Disables the SNMP alert. Enables the SNMP alert.
Table 4-26. Parameters of omconfig system platformevents Event Name Description alertsenable=true | false true: Enables generation of platform event filter alerts. false: Disables generation of platform event filter alerts. NOTE: This setting is independent of the individual platform event filter alert settings. For a platform event filter to generate an alert, both the individual alert and the global event alert are enabled.
Table 4-26. Parameters of omconfig system platformevents (continued) Event Name Description event=powerfail Sets action or enables or disables alert generation when a power device probe detects that the power supply, voltage regulator module, or DC to DC converter has failed. event=processorwarn Sets action or enables or disables alert generation when a processor probe detects that the processor is running at less than peak performance or speed.
Table 4-26. Parameters of omconfig system platformevents (continued) Event Name Description event= removableflashmediafail Sets actions that Server Administrator performs when a removable flash media fails. event=tempfail Sets action or enables or disables alert generation when a temperature probe detects that the temperature is either too high or low for proper operation.
Source At present, source=snmptraps is a required name=value pair because SNMP is currently the only supported source of event notification for the system’s components. omconfig system events source=snmptraps or omconfig servermodule events source=snmptraps Type Type refers to the name of the component(s) involved in the event. Table 4-27 lists the valid parameters for system event types. Table 4-27.
Severity In the context of configuring events, severity determines how severe an event is, 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 specify whether you want notification for event severity according to the number of the component by using the index= parameter. Table 4-28 lists the valid severity parameters. Table 4-28.
Index Index refers to the number of an event for a particular component. Index is an optional parameter. When you omit the index parameter, events are configured for all components of the specified type, such as all fans. For example, when a system contains more than one fan, you can enable or disable event notification for a particular fan.
Table 4-30. Recovery Parameters name=value pair Description action=none Takes no action when the operating system is hung or has crashed. action=reboot Shuts down the operating system and initiates system startup, performing BIOS checks, and reloading the operating system. action=poweroff Turns off electrical power to the system. action=powercycle Turns off electrical power to the system, pauses, turns the power on, and reboots the system.
omconfig system shutdown or omconfig servermodule shutdown Use the omconfig system shutdown or omconfig servermodule shutdown command to determine the way in which the system shuts down. During system shutdown, the default is to shut down the operating system before powering off the system. Shutting down the operating system first closes down the file system before powering the system down. If you do not want to shut down the operating system first, use the osfirst=false parameter.
To bypass operating system shutdown before the system is powered off, type: omconfig system shutdown action=reboot osfirst= false or omconfig servermodule shutdown action=reboot osfirst=false omconfig system thrmshutdown or omconfig servermodule thrmshutdown Use the omconfig system thrmshutdown or omconfig servermodule thrmshutdown command to configure a thermal shutdown action.
Example Thermal Shutdown Commands To trigger a thermal shutdown when a temperature probe detects a failure event, type: omconfig system thrmshutdown severity=failure or omconfig servermodule thrmshutdown severity= failure To disable thermal shutdown so that an administrator has to initiate an omconfig system shutdown, type: omconfig system thrmshutdown severity=disabled or omconfig servermodule thrmshutdown severity= disabled omconfig: Managing Components Using the Instrumentation Service 175
omconfig: Managing Components Using the Instrumentation Service
5 omconfig system or servermodule assetinfo: Editing Cost of Ownership Values The omconfig system assetinfo or omconfig servermodule assetinfo command helps you to edit a comprehensive set of parameters that make up the total cost of ownership of the system. This section explains the parameters that are reported and configured under the omconfig system assetinfo or omconfig servermodule assetinfo command.
Table 5-2. Parameters of omconfig system assetinfo info=acquisition or omconfig servermodule assetinfo info=acquisition Command Command Level 1 Level 2 Command Name= Name= Value Level 3 Value Pair 1 Pair 2 Description omconfig system or servermodule assetinfo info= acquisition costcenter= expensed=yes | no installdate= ponum= purchasecost= purchasedate= signauth= waybill= 178 The name or code for the business entity that acquired the system.
Example Commands for Adding Acquisition Information To provide a value for an acquisition parameter, type a command of the form: omconfig system assetinfo info=acquisition or omconfig servermodule assetinfo info=acquisition . For example, type: omconfig system assetinfo info=acquisition purchasedate=122101 or omconfig servermodule assetinfo info=acquisition purchasedate=122101 The following message is displayed: Asset information set successfully.
Adding Depreciation Information Depreciation is a set of methods for computing the devaluation of the asset over time. For example, the depreciation of a system that is expected to have a useful life of 5 years is 20 percent. Use the omconfig system assetinfo info= depreciation or omconfig servermodule assetinfo info=depreciation command to add details about how the system's depreciation is computed. Table 5-3 lists the valid parameters for the command. Table 5-3.
Example Commands for Adding Depreciation Information To provide a value for a depreciation parameter, type a command of the form: omconfig system assetinfo info=depreciation or omconfig servermodule assetinfo info=depreciation . For example, type: omconfig system assetinfo info=depreciation method=straightline or omconfig servermodule assetinfo info=depreciation method=straightline The following message is displayed: Asset information set successfully.
Table 5-4 lists the valid parameters for the command. Table 5-4. Parameters of omconfig system assetinfo info=extwarranty or omconfig servermodule assetinfo info=extwarranty Command Level 1 Command Level Command 2 Level 3 Name= Value Name= Value Description Pair 1 Pair 2 omconfig system or servermodule assetinfo info= extwarranty cost= enddate= Cost of the extended warranty service. Date the extended warranty agreement ends.
You can type more than one omconfig system assetinfo or omconfig servermodule assetinfo command at the same time, as long as all the parameters for name=value pair 2 belong to name=value pair 1. For an example, see "Example Commands for Adding Acquisition Information" on page 179. 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 5-5 lists the valid parameters for the command. Table 5-5.
Example Command for Adding Lease Information To provide a value for a lease parameter, type a command of the form: omconfig system assetinfo info=lease or omconfig servermodule assetinfo info=lease . For example, type: omconfig system assetinfo info=lease value=4500 or omconfig servermodule assetinfo info=lease value= 4500 The following message is displayed: Asset information set successfully.
Table 5-6. Parameters of omconfig system assetinfo info=maintenance or omconfig servermodule assetinfo info=maintenance (continued) Command Command Level 1 Level 2 Command Name= Value Level 3 Pair 1 Name= Value Pair 2 Description provider= Business entity providing the maintenance service. startdate= Date the maintenance begins. restrictions= Activities not covered by the maintenance contract.
Adding Outsource Information Outsourcing is the practice of contracting with another business to maintain the system in good working order. Table 5-7 lists the valid parameters for adding outsource information. Table 5-7.
Example Command for Adding Outsource Information To provide a value for an outsource parameter, type a command of the form: omconfig system assetinfo info=outsource or omconfig servermodule assetinfo info=outsource . For example, type: omconfig system assetinfo info=outsource providerfee=75 or omconfig servermodule assetinfo info=outsource providerfee=75 The following message is displayed: Asset information set successfully.
Adding Owner Information The owner is the party that holds legal property title to the system. Table 5-8 lists the valid parameters for adding owner information. Table 5-8.
You can type more than one omconfig system assetinfo or omconfig servermodule assetinfo command at the same time, as long as all the parameters for name=value pair 2 belong to name=value pair 1. For an example, see "Example Commands for Adding Acquisition Information" on page 179. Adding Service Contract Information A service contract is an agreement that specifies fees for preventive maintenance and repair of the system. Table 5-9 lists the valid parameters for adding contract information. Table 5-9.
Example Command for Adding Service Information To provide a value for a service parameter, type a command of the form: omconfig system assetinfo info=service or omconfig system assetinfo info=service . For example, type: omconfig system assetinfo info=service vendor= fixsystemco or omconfig servermodule assetinfo info=service vendor=fixsystemco The following message is displayed: Asset information set successfully.
Table 5-10. Parameters of omconfig system assetinfo info=support or omconfig servermodule assetinfo info=support (continued) Command Command Level Command Name= Name= Value Pair 2 Description Level 1 2 Level 3 Value Pair 1 automaticfix= Name of any application used to fix a problem automatically. helpdesk= The help desk name or contact information such as a phone number, e-mail address, or website address.
The following message is displayed: Asset information set successfully. You can type more than one omconfig system assetinfo or omconfig servermodule assetinfo command at the same time, as long as all the parameters for name=value pair 2 belong to name=value pair 1. For an example, see "Example Commands for Adding Acquisition Information" on page 179. Adding System Information System information includes the primary user of the system, the phone number for the primary user, and the location of the system.
Example Command for Adding System Information To provide a value for a system parameter, type a command of the form: omconfig system assetinfo info=system or omconfig servermodule assetinfo info=system . For example, type: omconfig system assetinfo info=system location= firstfloor or omconfig servermodule assetinfo info=system location=firstfloor The following message is displayed: Asset information set successfully.
Table 5-12. Parameters of omconfig system assetinfo info=warranty or omconfig servermodule assetinfo info=warranty Command Command Level 1 Level 2 Command Name= Value Level 3 Pair 1 Name= Value Description Pair 2 omconfig system or servermodule assetinfo info= warranty cost= duration= Cost of the warranty service. Number of days or months that the warranty is in force. enddate= Date the warranty agreement ends.
You can type more than one omconfig system assetinfo or omconfig servermodule assetinfo command at the same time, as long as all the parameters for name=value pair 2 belong to name=value pair 1. For an example, see "Example Commands for Adding Acquisition Information" on page 179.
omconfig system or servermodule assetinfo: Editing Cost of Ownership Values
Using the Storage Management Service 6 The Storage Management command line interface (CLI) enables you to perform reporting, configuration, and management functions of Storage Management 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.
Table 6-1 describes these command levels. Table 6-1. Example Command Levels Command level 1 Command level 2 Command level 3 Use omconfig storage pdisk Specifies the command Indicates the Server Administrator service (in this case, storage management) that implements the command 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.
Table 6-2. Syntax For of Parameters Syntax Description controller=id Indicates the controller ID as reported by the omreport storage controller command. To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage pdisk controller=id to display the IDs for the physical disks attached to the controller. connector=id vdisk=id For example, the controller=id parameter is specified as controller=1.
Table 6-2. Syntax For of Parameters (continued) Syntax Description battery=id Indicates the battery ID as reported by the omreport command. To obtain this value, type omreport storage controller to display the controller IDs and then type 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= parameter is specified as name=VirtualDisk1.
omreport storage Commands 7 The omreport command allows you to view storage component information for disks, controllers, enclosures, batteries, global storage properties, connectors, cachecades, fluid cache, and partitions that are part of the storage system. This chapter explains 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 7-1. Syntax for omreport storage help (continued) Command Level 1 Command Level 2 Command Level 3 Use Displays a list of the omreport storage battery parameters for displaying battery information. globalinfo Displays a list of the omreport storage globalinfo parameters for displaying global storage property information. connector Displays a list of the omreport storage connector parameters for displaying connector information.
Table 7-2. omreport Physical Disk Commands Optional name=value pairs Required Command Levels (1, 2, 3) and name= value pair Use omreport storage pdisk Displays all physical disks attached to the specified controller. controller=id where id is the controller number. For example: controller=0 NOTE: If a physical disk was replaced by another disk as part of the replace member operation, the state of the physical disk is displayed as Replacing.
omreport Virtual Disk Status Table 7-3 describes the syntax for the omreport virtual disk commands. Table 7-3. omreport Virtual Disk Commands Required Command Levels (1, 2, 3) Optional name=value pairs omreport storage vdisk 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.
omreport Controller Status Table 7-4 describes the syntax for the omreport controller commands. Table 7-4. omreport Controller Commands Optional name=value pairs Use Required Command Levels (1, 2, 3) omreport storage controller Displays property information for all controllers attached to the system. controller=id Displays the specified controller and all attached components such as enclosures, where id is the controller number. For virtual disks, physical disks, and so on.
omreport Enclosure Status Table 7-5 describes the syntax for the omreport enclosure commands. Table 7-5. omreport Enclosure Commands Optional name=value pairs Required Command Levels (1, 2, 3) Use omreport storage enclosure Displays property information for all enclosures attached to the system. Displays all enclosures connected to the controller. Displays the specified enclosure and its components.
The following sections provide the omreport storage enclosure command syntax required to execute the enclosure commands. omreport Temperature Probe Status Table 7-6 describes the syntax for the omreport probe commands. Table 7-6. omreport Temperature Probe Commands Required Command Levels Optional name=value pairs (1, 2, 3) and name=value pair Use omreport storage enclosure Displays property information for all enclosures attached to the system.
omreport Fan Status Table 7-7 describes the syntax for the omreport fan commands. Table 7-7. omreport Fan Status Commands Required Command Levels Optional name=value pairs (1, 2, 3) and name=value pair Use omreport storage enclosure Displays property information for all enclosures attached to the system. Displays the information about the fans for the specific enclosure. controller=id enclosure= info=fans where id is the controller number and ENCLOSUREID is the enclosure number.
omreport Power Supply Status Table 7-8 describes the syntax for the omreport power supply commands. Table 7-8. omreport Power Supply Commands Required Command Levels (1, Optional name=value pairs 2, 3) and name=value pair Use omreport storage enclosure Displays property information for all enclosures attached to the system. Displays the information about the power supplies for the specific enclosure.
omreport EMM Status NOTE: The status of the EMMs is displayed as degraded if there is a mismatch between the EMM firmware. Table 7-9 describes the syntax for the omreport EMM commands. Table 7-9. omreport EMM Commands Required Command Levels Optional name=value pairs Use (1, 2, 3) and name=value pair omreport storage enclosure Displays property information for all enclosures attached to the system.
omreport Enclosure Slot Occupancy Report Table 7-10 describes the syntax for the omreport enclosure slot occupancy report commands. Table 7-10. omreport Enclosure Slot Occupancy Report Commands Required Command Optional name=value pairs Levels (1, 2, 3) and name=value pair omreport storage enclosure Use Displays property information for all enclosures attached to the system.
omreport Global Information (Smart Thermal Shutdown Status, Hot Spare Protection Policy) Table 7-12 describes the syntax for the omreport global information command. Table 7-12. omreport Global Information Commands Required Command Optional name= Levels (1, 2, 3) value pairs Use omreport storage globalinfo Displays whether smart thermal shutdown is enabled or disabled. For more information, see the "omconfig Global Enable Smart Thermal Shutdown" on page 283.
omreport Connector Status Table 7-13 describes the syntax for the omreport connector commands. Table 7-13. omreport Connector Commands Required Command Optional name= Levels (1, 2, 3) value pairs Use omreport storage connector Displays all connectors present on all controllers on the system. NOTE: This command works only when the controller=id where id is the controller number. For example: controller=0 controller =id connector=id where id is the connector number.
omreport Cachecade Status Table 7-14 describes the syntax for the omreport cachecade commands. Table 7-14. omreport Cachecade Commands Required Command Levels (1, 2, 3) Optional name=value pairs omreport storage cachecade controller=id where id is the controller number. For example: controller=0. controller=id cachecade=id where id is the controller number and the cachecade number. For example: controller=0 cachecade=1. Use Displays property information for all cachecades on all controllers.
Table 7-16. omreport Fluid Cache Command Required Command Levels (1, 2, 3) Use omreport storage fluidcache Displays fluid cache properties and the associated fluid cache disks. omreport Fluid Cache Pool Status Table 7-14 describes the syntax for the omreport fluidcachepool command. Table 7-17. omreport Fluid Cache Pool Command Required Command Levels (1, 2, 3) Use omreport storage fluidcachepool Displays the properties of the fluid cache pool.
omreport Partition Status Table 7-14 describes the syntax for the omreport partition commands. Table 7-18. omreport Partition Commands Required Command Levels (1, 2, 3) Optional name=value pairs Use controller=id vdisk=id Displays the partition details of the specified virtual disk. Displays all the partitions in the specified virtual disk on the controller. omreport storage partition where id is the controller number and the virtual disk number. For example: controller=0 vdisk=1.
omconfig storage Commands 8 The omconfig commands allows you to configure physical disks, virtual disks, controllers, enclosures, batteries, global information, connectors, and cachecades. The following sections provide the omconfig command syntax required to display the status of various storage components. To see a list of valid commands for omconfig storage, type: omconfig storage -? Table 8-1 provides the omconfig storage command syntax. Table 8-1.
Table 8-1. Syntax of omconfig storage help (continued) Command Level 1 Command Level 2 Command Level 3 Use Displays a list of the omconfig storage connector parameters for configuring connectors. cachecade Displays a list of the omconfig storage cachecade parameters for configuring cachecades. pciessed Displays PCIe SSD configuration commands. fluidcache Displays the fluid cache properties and the associated fluid cache disks. fluidcachepool Displays the fluid cache pool properties.
Table 8-2.
omconfig storage pdisk action=blink controller=1 pdisk=0:0 • For SAS controllers: omconfig storage pdisk action=blink controller=1 pdisk=0:2:0 NOTE: On a SAS controller, the physical disk resides in enclosure 2. omconfig Unblink Physical Disk You can disable the light (light emitting diode or LED display) on one or more physical disks attached to a controller. Use the following omconfig command syntax to unblink one or more physical disks.
omconfig Prepare to Remove Physical Disk Use the following omconfig command syntax to prepare a physical disk for removal: Complete Syntax omconfig storage pdisk action=remove controller=id pdisk= where id is the controller ID. The variable specifies the physical disk. To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
omconfig Offline Physical Disk Use the following omconfig command syntax to make a physical disk offline: Complete Syntax omconfig storage pdisk action=offline controller= id pdisk= where id is the controller ID. The variable specifies the physical disk. To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
• For SAS controllers: omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk=0:2:3 assign=yes NOTE: On a SAS controller, the physical disk resides in enclosure 2. omconfig Rebuild Physical Disk Use the following omconfig command syntax to rebuild a failed physical disk. Rebuilding a disk may take several hours. If you need to cancel the rebuild, use the Cancel Rebuild task. See the Dell OpenManage Online Help for more information about Rebuild Physical Disk.
omconfig Cancel Rebuild Physical Disk Use the following omconfig command syntax to cancel a rebuild that is in progress. If you cancel a rebuild, the virtual disk remains in a degraded state. See the Dell OpenManage Online Help for more information about Cancel Rebuild Physical Disk. Complete Syntax omconfig storage pdisk action=cancelrebuild controller=id pdisk= where id is the controller ID. The variable specifies the physical disk.
To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller. Example Syntax To cancel replace member operation on disk 0:0:1 which is connected to controller 0, type: omconfig storage pdisk action=cancelreplacemember controller=0 pdisk=0:0:1 omconfig Clear Physical Disk Use the following omconfig command to clear data or a configuration from a physical disk.
Complete Syntax omconfig storage pdisk action=cancelclear controller=id pdisk= where id is the controller ID. The variable specifies the physical disk. To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller. Example Syntax In this example, you want to cancel the clear of physical disk 3 on connector 0 of controller 1.
Example Syntax To enable write cache on physical disk 3 on connector 0 of controller 1: • For SAS controllers: omconfig storage pdisk action= enabledevicewritecache controller=1 pdisk=0:2:3 NOTE: On a SAS controller, the physical disk resides in enclosure 2. omconfig Disable Device Write Cache Use the following omconfig command to disable write cache on a physical disk for the PCIe SSD controller.
Complete Syntax omconfig storage pdisk action=exportlog controller=id pdisk= where id is the controller ID. The variable specifies the physical disk. To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Example Syntax To convert RAID to non-RAID on physical disk 3 on connector 0 of controller 1: • For SAS controllers: omconfig storage pdisk action=raidtononraid controller=1 pdisk=0:2:3 NOTE: On a SAS controller, the physical disk resides in enclosure 2. omconfig Convert Non-RAID to RAID Use the following omconfig command to convert non-RAID to RAID on a physical disk. Complete Syntax omconfig storage pdisk action=convertnonraidtoraid controller=id pdisk= where id is the controller ID.
omconfig Virtual Disk Commands The following sections provide the omconfig command syntax required to execute virtual disk tasks. CAUTION: The omconfig storage vdisk action=deletevdisk controller=id vdisk=id command deletes a virtual disk. Deleting a virtual disk destroys all information including file systems and volumes residing on the virtual disk. Table 8-3.
Table 8-3.
Complete Syntax omconfig storage vdisk action= cancelcheckconsistency controller=id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
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 Unblink Virtual Disk Use the following omconfig command syntax to unblink the physical disks included in a virtual disk. Complete Syntax omconfig storage vdisk action=unblink controller= id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
omconfig Fast Initialize Virtual Disk Use the following omconfig command syntax to fast initialize a virtual disk. CAUTION: You may receive a warning message if you attempt to delete the system or boot partition. However, this warning message is not generated always. Ensure that you do not delete the system or boot partition or other vital data when using this command.
Complete Syntax omconfig storage vdisk action=slowinit controller= id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, type omreport storage controller to display the controller IDs and then type 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 this command deletes the system or boot partition.
omconfig Cancel Background Initialize Use the following omconfig command syntax to cancel the background initialization process on a virtual disk. Complete Syntax omconfig storage vdisk action=cancelbginitialize controller=id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command.
Example Syntax To assign physical disk 3 on connector 0 of controller 1 as a dedicated hot spare to virtual disk 4: • For SCSI, SATA, and ATA controllers: omconfig storage vdisk action= assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:3 assign=yes • For SAS controllers: omconfig storage vdisk action= assigndedicatedhotspare controller=1 vdisk=4 pdisk=0:2:3 assign=yes NOTE: On a SAS controller, the physical disk resides in enclosure 2.
Example Syntax To delete virtual disk 4 on controller 1, type: omconfig storage vdisk action=deletevdisk controller=1 vdisk=4 omconfig Format Virtual Disk Use the following omconfig command syntax to format a virtual disk. Complete Syntax omconfig storage vdisk action=format controller=id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command.
Example Syntax To reconfigure virtual disk 4 to a size of 800 MB, use RAID-5 and physical disks 0 through 3 on connector 0 of controller 1: • For SCSI, SATA, and ATA controllers: omconfig storage vdisk action=reconfigure controller=1 vdisk=4 raid=r5 size=800m pdisk= 0:0,0:1,0:2,0:3 • For SAS controllers: omconfig storage vdisk action=reconfigure controller=1 vdisk=4 raid=r5 pdisk= 0:2:0,0:2:1,0:2:2,0:2:3 NOTE: On a SAS controller, the physical disk resides in enclosure 2.
omconfig Secure Virtual Disk Use the following omconfig command syntax to encrypt a virtual disk. Complete Syntax omconfig storage vdisk action=securevd controller= id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, type omreport storage controller to display the controller IDs and then type 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 [diskcachepolicy= | readpolicy= | writepolicy= | fwb> cachepolicy=] where id is the controller ID and virtual disk ID as reported by the omreport command.
omconfig Replace Member Virtual Disk Use the following omconfig command syntax to replace the member of a given virtual disk with the destination disk. Complete Syntax omconfig storage vdisk action=replacememberdisk controller=id vdisk=id source= destination= where id is the controller ID and virtual disk ID. The variable specifies the physical disk.
omconfig Rename Virtual Disk Use the following omconfig command syntax to rename a virtual disk. Complete Syntax omconfig storage vdisk action=rename controller=id vdisk=id name= where id is the controller ID and virtual disk ID as reported by the omreport command and is the new name for the virtual disk.
omconfig Enable Fluid Cache on Virtual Disk Use the following omconfig command syntax to enable fluid cache for the specified virtual disk. NOTE: Enabling fluid cache creates a new fluid cache disk. You must use only the new fluid cache disk for all future data access. Data access to any of the corresponding virtual disk or caching its partitions may lead to data corruption.
omconfig Disable Fluid Cache on Virtual Disk Use the following omconfig command syntax to disable fluid cache for the specified virtual disk. Complete Syntax omconfig storage vdisk action=disablefluidcache controller=id vdisk=id devicename= where id is the controller ID and virtual disk ID as reported by the omreport command, and is the device name of the virtual disk.
omconfig Reactivate Fluid Cache on Virtual Disk Use the following omconfig command syntax to reactivate the fluid cache for the specified virtual disk. Complete Syntax omconfig storage vdisk action=reactivate controller=id vdisk=id devicename= where id is the controller ID and virtual disk ID as reported by the omreport command, and is the device name of the virtual disk.
Table 8-4.
Table 8-4.
Table 8-4. omconfig Controller Commands (continued) Required Command Levels Optional name=value pairs (1, 2, 3) action=switchtolkm controller=id keyid= passphrase= [escrow=yes] [filepath= ] NOTE: If you set escrow=yes, specify the escrow file path.
Complete Syntax omconfig storage controller action=enablealarm controller=id where id is the controller ID as reported by the omreport storage controller command. Example Syntax To enable the alarm on controller 1, type: omconfig storage controller action=enablealarm controller=1 omconfig Disable Controller Alarm Use the following omconfig command syntax to disable the controller alarm. See the Dell OpenManage Online Help for more information about Disable Controller Alarm.
Complete Syntax omconfig storage controller action=quietalarm controller=id where id is the controller ID as reported by the omreport storage controller command. Example Syntax To quiet the alarm on controller 1, type: omconfig storage controller action=quietalarm controller=1 omconfig Test Controller Alarm Use the following omconfig command syntax to test the functionality of the controller alarm. The alarm sounds for about two seconds.
omconfig Reset Controller Configuration Use the following omconfig command syntax to reset the controller configuration. CAUTION: Resetting a configuration permanently destroys all data on all virtual disks attached to the controller. System or boot partition residing on these virtual disks is destroyed. You may receive a warning message if this command results in deleting the system or boot partition. However, this warning message is not generated always.
Physical disk is specified as either: • For SCSI, SATA, and ATA controllers: pdisk=connector:enclosureID:targetID where connector:enclosureID:targetID is the connector number, enclosure number, and slot number. For example pdisk=0:1:2 • For SAS controllers: pdisk=connector:targetID where connectorID:targetID is the connector number and the slot number. For example: pdisk=0:2 Storage Management supplies default values for any of the other parameters that you do not specify.
size= parameter (required) pdisk=
size= Parameter (Required) Table 8-6 indicates how to specify the size= parameter. Table 8-6. Size Parameter size= Description Parameter Specification size= size=max size=min Use this specification to indicate a specific size for the virtual disk. The virtual disk size is specified in b (bytes), m (megabytes), or g (gigabytes). For example, size=500m indicates that the virtual disk is 500 MB.
[cachepolicy=] Parameter (Optional) Different controllers support different cache policies. Table 8-7 indicates how to specify the [cachepolicy=] parameter for each of the cache policies. Table 8-7. Cache Policy Parameters Cache Policy Direct I/O Cache I/O cachepolicy=d | c Parameter Specification cachepolicy=d cachepolicy=c [diskcachepolicy=] Parameter (Optional) Different controllers support different disk cache policies.
[writepolicy=] Parameter (Optional) Different controllers support different write policies. Table 8-10 indicates how to specify the [writepolicy=] parameter for each of the write policies. Table 8-10.
Example Syntax You can create a RAID-5 virtual disk of 500MB with a stripe size of 16 KB on a PERC 3/QC controller. The name of the virtual disk is vd1 and it resides on connector 0 of controller 1. Because the virtual disk is a RAID-5, it requires at least three physical disks. In this example, you specify four physical disks. These are physical disks 0 through 3. The virtual disk has read-ahead, write–through caching, and cache I/O policies.
omconfig Change Controller Properties Use the following omconfig command to change any or all of the following controller properties.
Example Syntax To discard the preserved cache, type: omconfig storage controller action= discardpreservedcache controller=1 force=enabled CAUTION: Discarding the preserved cache can result in data loss. It is recommended that you run this command using the force=disabled option. NOTE: If a foreign configuration is detected, then the preceding command using force=disabled option fails. To avoid data loss, import the foreign configuration and flush the preserved cache to disk.
Complete Syntax omconfig storage controller action= changesecuritykey controller=id keyid= passphrase= oldpassphrase=[escrow=yes] [filepath=] Example Syntax To change the encryption key for the controller, type: omconfig storage controller action= changesecuritykey controller=1 keyid=Dell_123 passphrase=Dell_123 oldpassphrase=Dell_321 escrow= yes filepath=C:/escrow.
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 To set the background initialization rate to 50 on controller 1, type: omconfig storage controller action=setbgirate controller=1 rate=50 omconfig Set Reconstruct Rate Use the following omconfig command syntax to set the reconstruct rate.
Complete Syntax omconfig storage controller action= setcheckconsistencyrate controller=id rate=<0 to 100> where id is the controller ID as reported by the omreport storage controller command. Example Syntax To set the check consistency rate to 50 on controller 1, type: omconfig storage controller action= setcheckconsistencyrate controller=1 rate=50 omconfig Export the Controller Log Use the following omconfig command syntax to export the controller log to a text file.
Depending on the controller, the log file name is afa_.log or lsi_.log where is the month and date. See the Dell OpenManage Online Help for more information on the controller log file. NOTE: The export log file command is not supported on the 4/IM, CERC ATA, and 100/4ch controllers. omconfig Import Secure Foreign Configuration Use the following omconfig command syntax to unlock the encrypted Local Key Management (LKM) foreign configuration drives.
Example Syntax To import foreign configurations on controller 1, type: omconfig storage controller action= importforeignconfig controller=1 omconfig Import or Recover Foreign Configuration Use the following omconfig command syntax to import and recover all virtual disks that reside on physical disks newly attached to the controller.
Example Syntax To clear foreign configurations on controller 1, type: omconfig storage controller action= clearforeignconfig controller=1 omconfig Physical Disk Power Management Use the following omconfig command syntax for managing the power of physical disks in a controller by spinning down hot spares, configured drives, and unconfigured drives.
omconfig Set Patrol Read Mode Use the following omconfig command syntax to set the patrol read mode for the controller. Complete Syntax omconfig storage controller action= setpatrolreadmode controller=id mode= manual|auto|disable where id is the controller ID as reported by the omreport storage controller command.
omconfig Stop Patrol Read Use the following omconfig command syntax to stop the patrol read task on the controller. Complete Syntax omconfig storage controller action=stoppatrolread controller=id where id is the controller ID as reported by the omreport storage controller command. Example Syntax To stop the patrol read task on controller 1, type: omconfig storage controller action=stoppatrolread controller=1 NOTE: To stop patrol read, the current patrol read mode is set to Manual.
omconfig Enable LKM Controller Use the following omconfig storage command syntax to enable the LKM mode and create the encryption key for the controller. Complete Syntax omconfig storage controller action=enablelkm controller=id keyid= passphrase= [escrow=yes] [filepath= ] where id is the controller ID as reported by the omreport storage controller command.
omconfig Convert Multiple RAID to Non-RAID Use the following omconfig storage command syntax to convert multiple RAID to non-RAID on the given controller.
Omconfig Enclosure Commands The following sections provide the omconfig command syntax required to execute enclosure tasks. Table 8-11.
omconfig Enable Enclosure Alarm Use the following omconfig command syntax to enable the enclosure alarm: Complete Syntax omconfig storage enclosure action=enablealarm controller=id enclosure= where id is the controller ID. The variable specifies the enclosure.
Example Syntax To disable the alarm on enclosure 2 attached to connector 1 on controller 1: • For SCSI, SATA, and ATA controllers: omconfig storage enclosure action=disablealarm controller=1 enclosure=2 • For SAS controllers: omconfig storage enclosure action=disablealarm controller=1 enclosure=1:2 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=
omconfig Set Enclosure Asset Name Use the following omconfig command syntax to specify the asset name for an enclosure. Complete Syntax omconfig storage enclosure action=setassetname controller=id enclosure= assetname= where id is the controller ID. The variable specifies the enclosure. In this syntax, is a user-specified alphanumeric string.
Complete Syntax omconfig storage enclosure action=settempprobes controller=id enclosure= index=id minwarn=n maxwarn=n where id is the controller ID and the temperature probe ID. The variable specifies the enclosure. In this syntax, n is a user-specified value for the temperature in Celsius.
Example Syntax To reset the thresholds for temperature probe 3, residing in the enclosure attached to connector 2 on controller 1, to the default values: • For SCSI, SATA, and ATA controllers: omconfig storage enclosure action=resettempprobes controller=1 enclosure=2 index=3 NOTE: Here, temperature probe 3 resides in the enclosure attached to connector 2 on controller 1.
omconfig Reset All Temperature Probe Thresholds Use the following omconfig command syntax to reset the minimum and maximum warning temperature thresholds back to their default value for all temperature probes in the enclosure. NOTE: This command is not supported on SCSI RAID controllers. Complete Syntax omconfig storage enclosure action= resetalltempprobes controller=id enclosure= where id is the controller ID. The variable specifies the enclosure.
Example Syntax To blink the LEDs for enclosure 3 attached to connector 2 on controller 1: • For SCSI, SATA, and ATA controllers: omconfig storage enclosure action=blink controller=1 enclosure=2 • For SAS controllers: omconfig storage enclosure action=blink controller=1 enclosure=2:3 omconfig Battery Commands The following sections provide the omconfig command syntax required to execute battery tasks. Table 8-12.
Example Syntax To start the learn cycle on controller 1, type: omconfig storage battery action=startlearn controller=1 battery=0 omconfig Delay Battery Learn Cycle Use the following omconfig command to delay the battery learn cycle for a specified period of time. You can delay the battery learn cycle for a maximum of seven days or 168 hours.
Table 8-13. omconfig Global Commands Required Command Levels (1, 2, 3) Optional name=value pairs omconfig storage globalinfo action=enablests action=disablests action=globalrescan action=setprotectionpolicies type=ghs or dhs omconfig Global Enable Smart Thermal Shutdown By default, the operating system and server shut down when the PV220S and PV221S enclosures reach a critical temperature of 0 or 50 degree Celsius.
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, type 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 (GUI).
omconfig Global Rescan Controller Use the following omconfig command syntax to rescan all controllers on the system. See the Dell OpenManage Online Help for more information about Global Rescan Controller. Complete Syntax omconfig storage globalinfo action=globalrescan Example Syntax The omconfig command syntax for rescanning all controllers on the system does not require that you specify a controller ID.
For global hot spare protection policy, type: omconfig storage globalinfo action= setprotectionpolicies type=ghs hscount=<1-16> warnlevel=<0-3> includeghsinvdstate= where hscount is the number of hot spares assigned to the virtual disk and warnlevel is the severity level you want to assign to the generated alert, if this policy is violated. Use hscount=0 warnlevel=0 to reset the global hot spare protection policy for the RAID level.
Example Syntax To rescan connector 2 on controller 1, type: omconfig storage connector action=rescan controller=1 connector=2 omconfig Cachecade Commands The following sections provide the omconfig command syntax required to execute cachecade tasks. Table 8-15.
Example Syntax To blink the physical disk in cachecade 4 on controller 1, type: omconfig storage cachecade action=blink controller=1 cachecade=4 omconfig Unblink Cachecade Use the following omconfig command syntax to unblink the physical disks included in a cachecade. Complete Syntax omconfig storage cachecade action=unblink controller=id cachecade=id where id is the controller ID and cachecade ID as reported by the omreport command.
In some circumstances, you may receive a warning message. You can override this warning by using the force=yes parameter.
omconfig Rename Cachecade Use the following omconfig command syntax to rename a cachecade. Complete Syntax omconfig storage cachecade action=rename controller=id cachecade=id name= where id is the controller ID and cachecade ID as reported by the omreport command. To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage cachecade controller=ID to display the IDs for the cachecades of the controller.
Complete Syntax omconfig storage pciessd action=addtocachepool subsystem=id pciedevice= where id is the subsystem ID and variable specifies the physical disk. To obtain these values, type omreport storage controller to display the controller IDs and then type omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
omconfig Reactivate PCIe SSD Device Use the following omconfig command syntax to reactivate the specified PCIe SSD device that was part of the cache pool. Complete Syntax omconfig storage pciessd action=reactivate subsystem=id pciedevice= where id is the subsystem ID and variable specifies the physical disk.
Complete Syntax omconfig storage fluidcache action=applylicense licensefile= Example Syntax omconfig storage fluidcache action=applylicense licensefile=/root/key/licensefile.xml omconfig Conecting to the Fluid Cache Use the following omconfig command syntax to connect to the fluid cache system and update the cache configuration details of the storage subsystem.
Table 8-19. omconfig Fluid Cache Disk Command Required Command Levels (1, 2, 3) Optional name=value pairs omconfig storage fluidcachedisk action=disablewithdiscard fluidcachedisk= omconfig Discarding Data and Disabling Caching Use the following omconfig command syntax to discard the data on the cache and disable caching on the specified fluid cache disk.
9 Working With CLI Command Results Server Administrator Command Line Interface (CLI) users can use the command output in various ways. This section explains how to save command output to a file and how to select a format for the command results that fits different objectives. Table 9-1.
Linux Enterprise Server terminal. To display command output with control over scrolling, type the CLI command and append the pipe symbol followed by more. For example, type: omreport system summary | more or omreport servermodule summary | more The multiscreen system summary displays the first screen. When you want to see the next screen of command output, press the spacebar.
Partial results written to the file are: Index : 0 Status : OK Probe Name : System Board Fan 1 RPM Reading : 2380RPM Minimum Warning Threshold : 600RPM Maximum Warning Threshold : 5700RPM Minimum Failure Threshold : 500RPM Maximum Failure Threshold : 6000RPM Four hours later, you repeat the command. You have no interest in the 11:00 A.M. snapshot as written to fans.txt. You type the same command: omreport chassis fans index=0 -outc fans.txt or omreport mainsystem fans index=0 -outc fans.
file called fans.txt. To compare these results with output for the same probe obtained four hours later, you can use the -outa command to append the new output to fans.txt. Type: omreport chassis fans index=0 -outa fans.txt or omreport mainsystem fans index=0 -outa fans.txt Fans.
Selecting a Format for the CLI Command Output You can specify a format for the CLI command results. The format determines how the command output is displayed. If the command results are directed to a file, the format is captured by the file to which you write the command results.
To see the following example command output in lst format, type: omreport system summary or omreport servermodule summary No special formatting option is required because list format is the default display format. The network data part of the example system summary is displayed as follows: -------------Network Data -------------Network Interface 0 IP Address: 143.166.152.108 Subnet Mask: 255.255.255.0 Default Gateway: 143.166.152.
Semicolon-separated Values (ssv) Use the ssv formatting option to deliver output formatted in semicolonseparated value format. This format also allows you to import the command output results into a spreadsheet program such as Microsoft Excel, or into a database program.
Working With CLI Command Results
Index Symbols -? omconfig, 97 omconfig chassis, 100 omreport, 39 request for help, 27 alertlog clearing logs, 163 omconfig system, 27, 94 omreport system, 71 arrays memory, 35, 87 asset information, 177 A about omconfig, 98 acquisition information, 177 optional parameters, 29 assetinfo acquisition, 74 omreport system, 74 assign dedicated hot spare omconfig, 239 assign global hot spare omconfig, 224 acquisition information adding, 177 available alert actions, 159 acswitch omreport chassis, 42 omreport
omconfig chassis, 100 omreport chassis, 44 blink omconfig, 280 blink physical disk omconfig, 219 bmc omconfig chassis, 136 omreport chassis, 67 chassis identification LED, 129 chassis information summary, 52 check consistency omconfig, 233 check consistency rate omconfig, 265 clear foreign configuration omconfig, 268 clear physical disk omconfig, 227 C cache policy parameters, 259 cache properties omreport chassis processors, 59 cancel background initialize omconfig, 239 cancel check consistency omconfig,
omreport chassis processors, 58 omconfig, 93 command levels 1,2,3 omreport, 33 connector status omreport, 212 command syntax overview, 24 controller battery, 211, 213 BMC, 67, 79, 96 display IDs, 199 omconfig storage, 249 omreport storage, 205 SATA, 111 commands for clearing logs, 163 commands for viewing logs, 71 components alert actions, 159 events, 74-75 failure messages, 22 instrumentation service, 91 omreport, 31-32 omreport system, 70 omreport system summary, 38 omreport system version, 38 SNMP t
omconfig, 282 delete virtual disk omconfig, 240, 288-289 delimiters data fields, 153 depreciation information about, 180 adding, 180 dirservice omconfig preferences, 154 disable enclosure alarm omconfig, 275 display IDs, 199-200 event notification configuring, 168 index, 171 severity, 170 source, 169 type, 169 events alert actions, 159-160 classified by component type, 76 omconfig system, 168 omreport system, 74 SNMP, 37, 94, 168 example help commands, 27 extended warranty information, 181 E external nam
formatting CLI command output, 299 intrusion omreport chassis, 53 frontpanel omconfig chassis, 126 omreport chassis, 51 IP address alert destinations, 164 IRQ level omreport chassis ports, 58 G globalinfo omconfig storage, 283 omreport storage, 212 H help, levels of, 28 hot spare, 239 I import foreign configuration omconfig, 267-268 import secure foreign configuration omconfig, 267 index omreport chassis slots, 69 info omconfig chassis, 128 omreport chassis, 52 initialize virtual disk omconfig, 222, 2
N name=value pairs omconfig chassis biossetup, 101 omconfig chassis bmc, 137 nics omreport chassis, 56 NMI button, 51 O omconfg cancel initialize virtual disk, 238 omconfig -?, 97 about, 98-99 assign dedicated hot spare, 239 assign global hot spare, 224 background initialization rate, 264 blink physical disk, 219 blink virtual disk, 235, 287 cancel background initialize, 239 cancel check consistency, 233 cancel rebuild physical disk, 226 Change Controller Properties, 262 change controller properties, 262 c
reset temperature probe thresholds, 278-280 resume check consistency, 235 secure virtual disk, 243 set controller rebuild rate, 261 set enclosure asset name, 277 set enclosure asset tag, 276 set temperature probe thresholds, 277 system, 158 test controller alarm, 254 unblink physical disk, 220 unblink virtual disk, 236, 288 omconfig about details=true, 99 omconfig battery commands, 281 omconfig channel commands, 286 omconfig chassis, 100 -?, 100 biossetup, 100 bmc, 136 currents, 124 fancontrol, 126 fans, 12
omconfig offline physical disk, 223 omconfig storage battery, 281 connector, 286 controller, 249 enclosure, 274, 287, 290, 292-294 globalinfo, 283 pdisk, 198, 218 vdisk, 232-233 omconfig physical disk commands, 218 omconfig switch to LKM controller, 272 omconfig physical disk power management, 269 omconfig system alertaction, 158 alertlog, 27, 94, 163 assetinfo, 177 cmdlog, 163 esmlog, 163 events, 168 extwarranty, 181 name=value pairs, parameters, 169 pedestinations, 164 platformevents, 164 recovery, 1
info=service, 190 info=support, 191 info=system, 193 info=warranty, 194 omconfig system events, 168 omconfig system extwarranty, 181 omconfig system pedestinations name=value pairs, parameters, 164 omconfig system recovery name=value pairs, parameters, 172 omconfig system shutdown name=value pairs, parameters, 173 omconfig system warranty, 193 omconfig system webserver name=value pairs, parameters, 171 omconfig virtual disk commands, 232 omhelp, 19, 27 omreport -?, 39 about, 40 battery status, 211 chassis,
esmlog, 71 events, 74 operatingsystem, 77 pedestinations, 77 platformevents, 80 recovery, 80 shutdown, 80 summary, 80 thrmshutdown, 88 version, 88 maximum speed, 58 port type, 58 omreport chassis processors cache properties, 59 connector name, 58 core count, 59 current speed, 59 external clock speed, 59 manufacturer, 58 processor family, 58 processor version, 58 state, 59 omreport chassis slots adapter, 69 data bus width, 69 index, 69 slot ID, 69 omreport modularchassis, 39 omreport preferences commands, 9
pdisk, 218 omconfig storage, 197-198 omconfig virtual disk, 256-257 omreport physical disk, 203 omreport storage, 203 R pedestinations omconfig system, 164 omreport system, 77 reconfiguring virtual disks omconfig, 241 read policy parameters, 259 rebuild physical disk omconfig, 225 Physical disks in each stripe, 260 reconstruct rate omconfig, 265 platformevents omconfig system, 164 omreport system, 80 recovery omconfig system, 171 omreport system, 80 port type omreport chassis ports, 58 recovery fr
service contract information, 189 adding, 189 set enclosure asset name omconfig, 277 set enclosure asset tag omconfig, 276 set temperature probe thresholds omconfig, 277-280 shutdown omconfig system, 173 omreport system, 80 shutdown action omconfig system platformevents, 165 slot ID omreport chassis slots, 69 slots omreport chassis, 68 smart thermal shutdown status, 212 summary omreport system, 80 support information adding, 190 syntax overview CLI commands, 24 system, 177 system information adding, 192 T
user access to Server Administrator administrators only, 156 determining, 156 least restrictive, 156 most restrictive, 156 power users and administrators only, 156 useraccess omconfig preferences, 156 W warranty adding, 193 components, 181, 193 omconfig system, 193 webserver omconfig system, 171 starting and stopping, 171 what’s new, 18 write policy parameters, 260 V vdisk omconfig storage, 232-233 omreport storage, 204, 214-216 version omreport system, 88 viewing alert actions for specific components and
Index 316
