Command Line Interface Version 10.2 – Supports the 9750, 9690SA, and 9650SE Models PN: 45413-00, Rev.
Document Description Document 45413-01, Rev. A. May 2010. This document will remain the official reference source for all revisions and releases of this product until rescinded by an update. Disclaimer It is the policy of LSI Corporation to improve products as new technology, components, software, and firmware become available. LSI reserves the right to make changes to any products herein at any time without notice.
Table of Contents About this CLI Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Chapter 1. Introduction to the 3ware Command Line Interface. . . . . . . . . . . . . . . . . .1 Features of the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Installing the 3ware CLI . . . . . . . . . . . . . .
/cx show carvesize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /cx show ctlbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /cx show driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /cx show dpmstat [type=inst|ra|ext] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /cx show drivestatus . . . . . . . . . . . . . . . . . . . . . . . . . . .
/cx set selftest=enable|disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /cx set spinup=nn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /cx set stagger=nn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /cx set autocarve=on|off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /cx set carvesize=<1024..32768> . . . . . . . . . . . .
/cx/px show serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 /cx/px show smart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 /cx/px show status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 /cx/px show all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
/cx/ex/almx set alarm=mute|unmute|off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /cx/ex update fw=filename_with_path [sep=n] [force] . . . . . . . . . . . . . . . . . . . . . /cx/ex show firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help with specific commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this CLI Guide This manual, the 3ware SATA+SAS RAID Controller Card CLI Guide, Version 10.2, provides instructions for configuring and maintaining your 3ware® controller card using the 3ware command line interface (CLI). This manual describes CLI support for the LSI 3ware 9750, 9690SA, and 9650SE with Release 9.5.2 or newer. If you have an earlier LSI™ 3ware controller (9590SE, 9550SX(U), 9500S or a legacy 7000/8000 series board), refer to the CLI guide for your controller.
1 Introduction to the 3ware Command Line Interface The 3ware SATA+SAS Controller Card Command Line Interface (CLI) manages multiple 9750, 9690SA, and 9650SE 3ware RAID controllers. Important! For all of the functions of the 3ware CLI to work properly, you must install the proper CLI, firmware, and driver versions. For the latest versions and upgrade instructions, check http://www.lsi.com/channel/ChannelDownloads.
Chapter 1. Introduction to the 3ware Command Line Interface Supported Operating Systems 3ware 9750 RAID controllers may be used with the following operating systems for Intel and AMD 32-bit and 64-bit x86 based motherboards: • Microsoft Windows Server 2003 (SP2 or newer) and 2008 • Microsoft Windows Vista and Windows 7 • • Red Hat Enterprise Linux® openSUSE Linux • • • • • • • SUSE® Linux Enterprise Server Fedora Core Linux Other Linux distributions based on open source Linux 2.
Installing the 3ware CLI • Copy the file from the 3ware CD. Copy the file tw_cli.exe to the directory from which you want to run the program. CLI is located on the 3ware CD in the directory \packages\cli\windows Note: CLI comes in both 32-bit and 64-bit versions. If you are copying the file directly, be sure to copy the correct version for your operating system.
Chapter 1. Introduction to the 3ware Command Line Interface To install 3ware CLI on Linux, FreeBSD, OpenSolaris, or VMWare do one of the following: • Copy the file. CLI binary and executable files are located on the 3ware CD in the following directory: /packages/cli Navigate to the appropriate folder under /packages/cli for your OS. Coy the file tw_cli to an appropriate location on your system where you can easily access the file.
Installing the 3ware CLI c Respond to each screen as the script walks you through the installation. d After the installation is complete, check that the software was installed correctly. For OpenSolaris a Navigate to the following directory on the 3ware CD: /packages/installers/tools/OpenSolaris b Type: ./setupSolaris_x86.bin c Press Enter to begin installation. d After the installation is complete, check that the software was installed correctly.
Chapter 1. Introduction to the 3ware Command Line Interface Installing the 3ware CLI on Mac OS X 3ware CLI can be installed from the 3ware software CD, or the latest version can be downloaded from the LSI web site, http://www.lsi.com/channel/ ChannelDownloads. To install 3ware CLI on Mac OS X • Run the installer and select CLI as the software to be installed.
Working with 3ware CLI Using the command interface interactively You can use the CLI interactively by entering commands at the main prompt and observing the results on the screen. To use the CLI interactively 1 If necessary, change to the directory that contains CLI. 2 Type the following command: tw_cli (Under Mac OS X, Linux, FreeBSD, and OpenSolaris, if the directory containing the CLI is not in your path, you might need to type .
Chapter 1. Introduction to the 3ware Command Line Interface Using an input file to execute a script You can operate 3ware CLI scripts by executing a file. The file is a text file containing a list of CLI commands that you have entered in advance. Each command must be on a separate line. Syntax tw_cli -f Where is the name of the text file you want to execute. Example tw_cli -f clicommand.txt This example describes execution of the file clicommand.
Understanding RAID Levels and Concepts Outputting the CLI to a Text File You can send the output of the 3ware CLI, including errors, to a text file by adding 2>&1 to the end of the line. Outputting to a text file can be useful, for example, if you want to email the output to LSI Technical Support. Examples tw_cli /c2/p0 show >> controller2port0info.txt 2>&1 or tw_cli /c0 show diag >> Logfile.
Chapter 1. Introduction to the 3ware Command Line Interface • “Available RAID Configurations” on page 11 • “Determining Which RAID Level to Use” on page 16 RAID Concepts The following concepts are important to understand when working with a RAID controller: • Arrays and Units. In the storage industry, an array refers to two or more disk drives that appear to the operating system as a single unit.
Understanding RAID Levels and Concepts Available RAID Configurations RAID is a method of combining several hard drives into one unit. It can offer fault tolerance and higher throughput levels than a single hard drive or group of independent hard drives. LSI's 3ware controllers support RAID 0, 1, 5, 6, 10, 50, and Single Disk. The following information explains the different RAID levels. RAID 0 RAID 0 provides improved performance, but no fault tolerance.
Chapter 1. Introduction to the 3ware Command Line Interface technology, read performance during a sequential read operation is twice the speed of a single drive. The adaptive algorithms in TwinStor technology boost performance by distinguishing between random read request and sequential read requests. For the sequential read requests generated when accessing large files, both drives are used with the drive heads simultaneously reading alternating sections of the file.
Understanding RAID Levels and Concepts RAID 6 RAID 6 provides greater redundancy and fault tolerance than RAID 5. It is similar to RAID 5 but, instead of a single block, RAID 6 has two blocks of parity information (P+Q) distributed across all the drives of a unit (see Figure 4). Due to the two parities, a RAID 6 unit can tolerate two hard drives failing simultaneously. This also means that a RAID 6 unit can be in two different states at the same time.
Chapter 1. Introduction to the 3ware Command Line Interface structure. Higher data transfer rates are achieved by leveraging TwinStor technology and striping the arrays. In addition, RAID 10 arrays offer a higher degree of fault tolerance than RAID 1 and RAID 5 because the array can sustain multiple drive failures without data loss. For example, in a 12-drive RAID 10 array, up to 6 drives can fail (half of each mirrored pair) and the array continues to function.
Understanding RAID Levels and Concepts Figure 6. RAID 50 Configuration Example (960 GB - 480 GB for mirror) (600 GB - 120 GB for parity) (600 GB - 120 GB for parity) Single Disk You can configure a single drive as a unit through 3ware software. (3BM, 3DM2, or CLI). Similar to disks in other RAID configurations, single disks contain 3ware Disk Control Block (DCB) information and the OS addresses them as available units.
Chapter 1. Introduction to the 3ware Command Line Interface Hot Spare A hot spare is a single drive, available online, so that a redundant unit is automatically rebuilt without human intervention in case of drive failure. Determining Which RAID Level to Use The type of RAID unit (array) that you create depends on your needs. You might want to maximize speed of access, total amount of storage, or redundant protection of data. Each type of RAID unit offers a different blend of these characteristics.
Understanding RAID Levels and Concepts Table 3: Possible Configurations Based on Number of Drives Number of Drives Possible RAID Configurations 3 RAID 0 RAID 1 with hot spare RAID 5 4 RAID 5 with hot spare RAID 10 Combination of RAID 0, RAID 1, single disk 5 RAID 6 RAID 5 with hot spare RAID 10 with hot spare Combination of RAID 0, RAID 1, hot spare, single disk 6 or more RAID 6 RAID 6 with hot spare RAID 50 Combination of RAID 0, 1, 5, 6,10, hot spare, single disk Using Drive Capacity Efficientl
Chapter 1. Introduction to the 3ware Command Line Interface Through drive coercion, the capacity used for each drive is rounded down to improve the likelihood that you can use drives from differing manufactures as spares for each other. The capacity used for each drive is rounded down to the nearest GB for drives under 45 GB (45,000,000,000 bytes), and rounded down to the nearest 5 GB for drives over 45 GB. For example, a 44.3-GB drive is rounded down to 44 GB, and a 123-GB drive is rounded down to 120 GB.
2 CLI Syntax Reference This chapter provides detailed information about using the command syntax for the 3ware CLI. Throughout this chapter, the examples shown use the interactive mode of using the 3ware CLI. Common Tasks Mapped to CLI Commands The table below lists many of the tasks that you can use to manage your RAID controllers and units, and also lists the primary CLI command associated with those tasks.
Chapter 2.
Common Tasks Mapped to CLI Commands Table 5: Common Tasks Mapped to CLI Commands (Continued) Task CLI Command Page Set the storsave profile /cx/ux set storsave 84 Unit Configuration Changes Change RAID level /cx/ux migrate 86 Change stripe size /cx/ux migrate 86 Expand unit capacity /cx/ux migrate 86 Delete a unit /cx/ux del 79 Remove a unit (export) /cx/ux remove 78 Name a unit /cx/ux set name 83 Unit Maintenance Tasks Start a rebuild /cx/ux start rebuild 79 Start a verify /cx/
Chapter 2.
Syntax Overview Phy. Phys are transceivers that transmit and receive the serial data stream that flows between the controller and the drives. 3ware 9750 and 9690SA controllers have four or more phys. These controller phys are associated with virtual ports (vports) by 3ware software to establish up to 128 potential connections with SAS or SATA hard drives. You can connect each controller phy directly to a single drive, or you can connect it through an expander to additional drives. VPort.
Chapter 2. CLI Syntax Reference Example: When adding (creating) a unit to the controller by using the following command string, /c1 add type=raid1 disk=0-1 c1 is the object, add is the command, type (for type of array) is an attribute with raid1 as the value of the attribute, and disk is another attribute with 0-1 as the value (ports 0 through 1). Commands act on different objects, for example shell objects, controller objects, unit objects, and other objects.
Shell Object Commands Help Commands. Help commands allow you to get help information for all commands and attributes. For details, see “Help Commands” on page 122. Shell Object Commands Shell object commands either apply to all the controllers in the system (such as show, rescan, flush, commit), or they redirect the focused object.
Chapter 2. CLI Syntax Reference • specifies a relative path with respect to the current focused hostname. /c0/bbu Example: //localhost> focus /c0/u0 //localhost/c0/u0> //localhost/c0/u0> focus.. //localhost/c0> //localhost> focus u0 //localhost/c0/u0> //localhost/c0> focus / //localhost> commit The commit command sends a commit command to all 3ware controllers in the system. For more information, see “/cx commit” on page 58.
Shell Object Commands Example for 9750-8i controller without an enclosure and expander: Typical output of the Show command for a controller is similar to the following: //localhost> show Ctl Model (V)Ports Drives Units NotOpt RRate VRate BBU -----------------------------------------------------------------------c0 9750-8i 8 8 2 0 1 1 - The output above indicates that Controller 0 is a 9750-8i with eight (V)ports, eight drives detected, two units, both in optimal state, with rebuild rate set to 1 and veri
Chapter 2. CLI Syntax Reference show events [reverse] The show events command is the same as “show alarms [reverse]”. Please see above for details. show AENs [reverse] The show AENS command is the same as “show alarms [reverse]”. Please see above for details. show diag The show diag command shows the diagnostic information for all controllers in the system. The enclosure diagnostic log might be requested by 3ware Customer Support to troubleshoot problems on your controller.
Shell Object Commands show selftest The show selftest command shows all selftest schedules for the 3ware RAID controllers in the system.
Chapter 2.
Controller Object Commands /cx /cx /cx /cx /cx /cx /cx show show show show show show show rebuildmode rebuildrate verify verifymode verifyrate selftest phy (9750 and 9690SA only) /cx add type= (RaidType={raid0,raid1,raid5,raid6,raid10,raid50,single, spare}) disk=
Chapter 2. CLI Syntax Reference /cx show The /cx show command shows summary information on the specified controller /cx. This information is organized into a report containing two or three parts: • A Unit summary section listing all present units • A Port summary section listing of all ports (or virtual ports) and disks attached to them. • A BBU summary section listing, if a BBU is installed on the controller.
Controller Object Commands ( if direct attached), the enclosure and slot (if expander attached), and model number of the drive. Note: If a drive is not present, that port entry is not listed. Consequently, the port numbers in the list might not be sequential. Moreover, if there are no drives present for the specified controller, the output of its Port summary shows an empty summary consisting of only the header The BBU summary lists details about the BBU, if one is installed.
Chapter 2. CLI Syntax Reference /cx show achip The /cx show achip command shows the SAS+SATA I/O controller (IOC) version of the specified controller /cx. Example: //localhost> /c0 show achip /c0 ACHIP Version = 3.x /cx show allunitstatus The /cx show allunitstatus command presents a count of total and Not Optimal units managed by the specified controller /cx.
Controller Object Commands 3. Smallest usable failed drive. If the policy is disabled, only spare drives are used for an automatic rebuild operation. Example: //localhost> /c0 show autorebuild /c0 Auto-Rebuild Policy = on /cx show bios The /cx show bios command shows the BIOS version of controller /cx. Example: //localhost> /c0 show bios /c0 BIOS Version = BG9X 2.
Chapter 2. CLI Syntax Reference /cx show dpmstat [type=inst|ra|ext] The /cx show dpmstat command shows the configuration and setting of the Drive Performance Monitor and a summary of statistics for drives attached to the controller. The optional type attribute specifies which statistics are reported. The available options are: inst for Instantaneous, ra for Running Average, and ext for Extended Drive Statistics.
Controller Object Commands Queue Xfer Resp Port Status Unit Depth IOPs Rate(MB/s) Time(ms) -------------------------------------------------------------p0 NOT-PRESENT p1 NOT-PRESENT p2 OK p3 OK u0 10 93 2.907 85 p4 OK u1 10 84 2.640 95 p5 OK p6 NOT-PRESENT p7 NOT-PRESENT - Example of running average (ra) drive statistics: To view a summary of the running average data for the set of drives attached to the controller, use command /cx show dpmstat type=ra.
Chapter 2. CLI Syntax Reference p6 0 0 0 0 0 0 0 Note: Depending on the amount of I/O and the rate or duration of the data transfer, overflow of the buffers containing this data can occur. In this case, the overflow is marked with “#######”, as shown in the example below. If overflow occurs, you might want to return the counters to zero by using the clear command, “/cx/px set dpmstat=clear [type=ra|lct|ext]” on page 101.
Controller Object Commands p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 OK OK OK OK OK OK OK OK OK OK OK OK OK OK u0 u0 u0 u0 u0 u0 - 34.18 34.18 34.18 34.18 34.25 34.25 34.25 34.25 34.18 34.18 34.18 34.18 34.25 34.
Chapter 2. CLI Syntax Reference /cx show monitor The /cx show monitor command shows the monitor (firmware boot-loader) version of controller /cx. Example: //localhost> /c0 show monitor /c0 Monitor Version = BLDR 2.x /cx show numdrives The /cx show numdrives command shows the number of drives currently managed by the specified controller /cx. This report does not include (logically) removed or exported drives.
Controller Object Commands /cx show pchip The /cx show pchip command shows the PCI Interface Chip (PCHIP) version of the specified controller /cx. Example: //localhost> /c0 show pchip /c0 PCHIP Version = 1.x /cx show serial The /cx show serial command shows the serial number of the specified controller /cx.
Chapter 2. CLI Syntax Reference available in the 3ware SATA+SAS RAID Controller Card Software User Guide, Version 10.2.) Note: If an asterisk (*) appears next to the status of a unit, there is an error on one of the drives in the unit. This feature provides a diagnostic capability for potential problem drives. The error might not be a repeated error, and can be caused by an ECC error, SMART failure, or a device error.
Controller Object Commands /c1 /c1 /c1 /c1 /c1 Verify Mode = Adaptive Verify Rate = 1 Controller Bus Type = PCIe Controller Bus Width = 8 lanes Controller Bus Speed = 2.5 Gbps/lane Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy --------------------------------------------------------------------------u0 RAID-6 OK 256K 1923.11 RiW ON u1 RAID-5 OK 256K 167.588 RiW ON u2 RAID-1 OK 65.
Chapter 2. CLI Syntax Reference oldest event messages appear at the top, and the most recent event messages appear at the bottom. You can use the [reverse] attribute to list the most recent event message at the top.
Controller Object Commands /cx show phy The /cx show phy command shows a list of the phys with related information for the specified controller. In the following example, the column Device Type indicates whether the connected device is an enclosure, or a SATA or SAS drive. The Device column is the device ID or handle. There are three Link Speed columns: Supported denotes the link speed capability of the phy/device, Enable denotes the current link speed setting, and Control denotes the link control setting.
Chapter 2. CLI Syntax Reference /cx show rebuild Background tasks can be scheduled to run at times that are most convenient for your organization. Rebuild is one of the supported background tasks. Migrate and initialize are other background tasks that follow the same schedule as rebuild. Other background tasks for which there are separate schedules are verify and selftest. For each background task, up to seven time periods can be registered, known as slots 1 through 7.
Controller Object Commands Example for 9750 controller: If a unit is in the initialization state at noon on Wednesday, the rebuild schedule shown above is in use (with schedules disabled), and you use the show command, you see the following status: /c0 show Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy --------------------------------------------------------------------------u0 RAID-50 INITIALIZING 62% 256K 469.
Chapter 2. CLI Syntax Reference p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK u0 u0 u0 u0 u0 u0 u0 u0 u0 u0 u0 u0 u0 u0 u0 34.18 34.18 34.18 34.18 34.18 34.18 34.18 34.18 34.18 34.18 34.18 34.18 34.18 34.18 34.
Controller Object Commands /cx show rebuildrate The /cx show rebuildrate command shows the current rebuild task rate of the specified controller. The rebuild task rate sets the rebuild execution priority relative to I/O operations. This task rate is in the range of [1..
Chapter 2. CLI Syntax Reference The show selftest command shows the current selftest background task schedule as illustrated below. Selftests do not have a time duration since they are completed momentarily.
Controller Object Commands doing a media scan and reporting an unreadable sectors. (For information about the initialization process, see the user guide that came with your 3ware RAID controller.
Chapter 2. CLI Syntax Reference For a more complete discussion of background task modes, see “Working with the Background Task Mode” in the 3ware SATA+SAS RAID Controller Card Software User Guide, Version 10.2 Example: //localhost> /c1 show verifymode /c1 Verify background task mode = Low Latency Related commands: /cx set verifymode= /cx set verifyrate=<1..
Controller Object Commands /cx add type= disk= [stripe=size] [noscan] [group=<3|4|5|6|7|8|9|10|11|12|13|14|15|16>] [nowrcache] [nordcache| rdcachebasic] [autoverify] [noqpolicy] [ignoreECC] [name=string] [storsave=] [rapidrecovery=all|rebuild|disable] [v0=n|vol=a:b:c:d] The /cx add command allows you to create a unit on the specified controller. You specify RAIDType, disks, and optional stripe size.
Chapter 2. CLI Syntax Reference stripe=size consists of the stripe size to be used. The following table illustrates the supported and applicable stripes on unit types. Stripe size units are in KB (kilobytes). If no stripe size is specified, 256K is used by default, if applicable. If you need to change the stripe size after the unit is created, you can do so by either migrating or recreating the unit.
Controller Object Commands newly created unit to Basic. By default (if you do not set a read cache attribute), the read cache mode is set to Intelligent. For more information, see “/cx/ux set rdcache=basic|intelligent|off” on page 82. autoverify attribute enables the autoverify attribute on the unit that is to be created. For more details on this feature, see “/cx/ux set autoverify=on|off” on page 81. Autoverify is set to on by default for a new unit.
Chapter 2. CLI Syntax Reference v0=n can be used if you only want two volumes, in which case v0=n is used to define the size of the first volume, and the second volume uses the remaining space. One way in which this can be useful is if you want to create a special volume to function as a boot volume, with a separate volume for data. vol=a:b:c:d can be used to specify sizes for up to four volumes. Use values that are positive integers in units of gigabytes (GB), with a maximum of 32 TB.
Controller Object Commands Volumes 0 through 3 are carved using the first four sizes, as specified. Volumes 4, 5, and 6 are the autocarved volumes (1024 GB each). Volume 6 is the remainder of the carve size. //localhost> /c2 add type=raid0 disk=0:1:2:4:5:6: 7 vol=2000:500:1024:700 Creating new unit on controller /c2 ... Done. The new unit is / c2/u0. Setting default Command Queuing Policy for unit /c2/u0 to [on] ... Done. Setting write cache=ON for the new unit ... Done.
Chapter 2. CLI Syntax Reference Rescanning controller /c1 for units and drives ...Done Found following unit(s): [/c1/u3] Found following drive(s): [/c1/p7, /c1/p8] /cx commit The /cx commit command applies only to the Windows operating system. It commits all changes if a faster shutdown method is needed when running certain database applications. This command has no effect and is not required with other operating systems such as Linux and FreeBSD.
Controller Object Commands Reboot the system so that the new firmware image takes effect. Note: The prom image number vary for different controllers. Prom0006.img is for the 9650SE, prom0008.img is for the 9690SA, and prom0011.img is for the 9750. Example: //localhost> /c0 update fw=/tmp/prom0006.img Warning: Updating the firmware can render the device driver and/or management tools incompatible. Before you update the firmware, it is recommended that you: 1) Back up your data.
Chapter 2. CLI Syntax Reference Setting Up a Rebuild Schedule Setting up a rebuild schedule requires several steps, and several different CLI commands in addition to /cx add rebuild. To set up the rebuild schedule, follow this process: 1 Use the /cx show rebuild command to show the current schedule for rebuild tasks. 2 If any of the scheduled tasks do not match your desired schedule, use the /cx del rebuild command to remove them.
Controller Object Commands 2 Use the /cx del verify command to remove any of the scheduled tasks which do not match your desired schedule. 3 Use the /cx add verify command to create the verify schedule slots you want (described above.) 4 Use the /cx set verify=enable command or the /cx set verify=advanced to enable the schedule (this enables all rebuild schedule slots). 5 Use the /cx/ux set autoverify=on command to turn on autoverify for each unit you want to follow the schedule.
Chapter 2. CLI Syntax Reference 2 Use the /cx del selftest command to remove any of the scheduled tasks which do not match your desired schedule. 3 Use the /cx add selftest command to create the selftest schedule slots you want (described above.) 4 Use the /cx set selftest=enable command to enable the schedule (this enables all selftest schedule slots). /cx del rebuild=slot_id The /cx del rebuild command removes the rebuild background task slot slot_id from the Rebuild Task Schedule.
Controller Object Commands You can see whether the Performance Monitor is currently running and also see a statistics summary by using the command “/cx show dpmstat [type=inst|ra|ext]” on page 36. For a description of each of the statistics that can be gathered and viewed, see “/cx/px show dpmstat type=inst|ra|lct|histdata|ext” on page 98. DPM is disabled by default since there is overhead in maintaining the statistics. DPM is also disabled following a reboot or powerup.
Chapter 2. CLI Syntax Reference The Adaptive setting is the default rebuild mode. It allows the firmware to adjust the interaction of rebuild tasks with host I/Os to maximize the speed of both host I/O and rebuild tasks. When a rebuild background task is active, if the task rate is set to a fast rebuild rate (i.e., low I/O rate), the system latency increases and performance can be negatively affected, especially for applications such as video server applications and audio applications.
Controller Object Commands Example: //localhost> /c1 set rebuildrate=2 Setting Rebuild background task rate on /c1 to [2] (faster I/O) ... Done. Related Commands /cx show rebuildmode /cx set rebuildmode= /cx show rebuildmode /cx set verify=enable|disable|1..5 The /cx set verify command enables or disables the advanced Verify Task Schedule defined for controller /cx and (when enabled) sets the priority of verification versus I/O operations.
Chapter 2. CLI Syntax Reference /cx set verify=advanced|basic|1..5 The /cx set verify=advanced|basic|1..5 command is effectively the same as the set verify=enabled|disabled command. Setting verify to advanced enables the advanced Verify Task Schedule, which can include a series of up to seven days and times. Setting verify to basic creates a weekly schedule with one specific day and time, and disables the series of scheduling slots associated with the advanced Verify Task Schedule.
Controller Object Commands When a verify background task is active, if the task rate is set to a fast verify rate (i.e., low I/O rate), the system latency increases and performance can be negatively affected, especially for applications such as video server applications and audio applications. The Low Latency setting minimizes the latency (delay) in reading data from the RAID unit by slowing down the rebuild task, which allows host Reads to complete, thus improving performance.
Chapter 2. CLI Syntax Reference Related commands: /cx show verifyrate /cx set verifymode= /cx show verifymode /cx set selftest=enable|disable The /cx set self-test command enables or disables the specified controller's SMART self test.. Example: //localhost> /c0 selftest=enable enables the selftest on controller c0. /cx set spinup=nn The /cx set spinup command allows you to set a controller-based Disk Spinup Policy that specifies how many drives can spin up at one time.
Controller Object Commands volume. Each volume can then be treated as an individual disk with its own file system. The default carvesize is 2 TB. This command is useful for operating systems limited to 2-TB file systems. For example, using the 2-TB default carvesize, a 3-TB unit is configured into one 2-TB volume and one 1-TB volume. A 5-TB unit is configured into two 2-TB volumes and one 1-TB volume. When autocarve policy is set to off, all new units are created as a single large volume.
Chapter 2. CLI Syntax Reference disconnect a drive (causing the controller to respond to it as a failed drive) and then reconnect it, the controller automatically tries to use it again. If the policy is off, spares are the only candidates for rebuild operations. Example: //localhost> /c0 set autorebuild=enable Setting Auto-Rebuild Policy on /c0 to enable ... Done.
Unit Object Commands Usage Scenario: If you are hot-plugging a large number of drives at the same time and are concerned that you might overload the power supply, you can use this command as follows: 1 Issue the command (set autodetect=off) to disable automatic detection of the ports for staggered spinup. 2 Remove the drives from the specified ports if the ports are not empty. 3 Insert (or replace) the drives at the ports specified.
Chapter 2. CLI Syntax Reference /cx/ux set storsave=protect|balance|perform [quiet] /cx/ux migrate type=RaidType [disk=p:-p] [group=3|4|5|6|7|8|9|10|11|12|13|14|15|16] [stripe=size] [noscan] [nocache] [autoverify] RaidType = {raid0, raid1, raid5, raid6, raid10, raid50, single} /cx/ux remove [noscan] [quiet] /cx/ux show The /cx/ux show command shows summary information for the specified unit. If the unit consists of subunits, as in the case of RAID 10 and RAID 50, then each subunit is further presented.
Unit Object Commands completion of the active process and (P) denotes that the percentage completion of the paused process. Example: /localhost> /c0 show unitstatus Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy --------------------------------------------------------------------------u0 RAID-6 REBUILD-VERIFY 50%(A) 70%(P) 256k 298.22 RiW OFF In the preceding example, the RAID 6 unit (u0) is in the Rebuild-Verify state.
Chapter 2. CLI Syntax Reference /cx/ux show attribute [attribute ...] The /cx/ux show attribute command shows the current setting of one or more specified attributes. If you specify an invalid attribute, the loop terminates. Possible attributes are: initializestatus, name, autoverify, rdcache, wrcache, ignoreECC, identify, qpolicy, parity, rapidrecovery, rebuildstatus, serial, status, storsave, verifystatus, and volumes.
Unit Object Commands /cx/ux show ignoreECC The /cx/ux show ignoreECC command shows the current setting of the ignoreECC policy for the specified unit. Example: //localhost> /c0/u0 show ignoreECC /c0/u0 Ignore ECC policy = off /cx/ux show initializestatus The /cx/ux show initialize status command shows the initializestatus (if any) of the specified unit.
Chapter 2. CLI Syntax Reference /cx/ux show rapidrecovery The /cx/ux show rapidrecovery command shows the Rapid RAID Recovery policy for the specified unit. This policy can be all, rebuild, or disable. For information about the policy settings, see the description about the rapidrecovery attribute for the /cx add command here on page 53. Example: //localhost> /c0/u0 show rapidrecovery /c1/u0 Rapid RAID Recovery policy setting = disable.
Unit Object Commands /cx/ux show storsave The /cx/ux show storsave command shows the storsave policy on the unit. For more information see, “/cx/ux set storsave=protect|balance|perform [quiet]” on page 84. Example: //localhost> /c0/u5 show storsave /c0/u5 Command Storsave Policy = protect /cx/ux show verifystatus The /cx/ux show verifystatus command shows the verifystatus (if any) of the specified unit.
Chapter 2. CLI Syntax Reference Unit UnitType Status %RCmpl %V/I/M VPort Stripe Size(GB) -----------------------------------------------------------------------u1 RAID-0 OK 64K 3576.06 u1-0 DISK OK p0 298.01 u1-1 DISK OK p1 298.01 u1-2 DISK OK p2 298.01 u1-3 DISK OK p3 298.01 u1-4 DISK OK p4 298.01 u1-5 DISK OK p5 298.01 u1-6 DISK OK p6 298.01 u1-7 DISK OK p7 298.01 u1-8 DISK OK p8 298.01 u1-9 DISK OK p9 298.01 u1-10 DISK OK p10 298.01 u1-11 DISK OK p11 298.01 u1/v0 Volume 2047.00 u1/v1 Volume 1529.
Unit Object Commands /cx/ux del [noscan] [quiet] The /cx/ux del command allows you to delete a unit. Deleting a unit not only removes the specified unit from the controller's list of managed units, but also eliminates the Disk Configuration Block (DCB) metadata. After you delete a unit, ports (or disks) associated with the unit become part of the free pool of managed disks. Warning: This is a destructive command and you must use it with care.
Chapter 2. CLI Syntax Reference When you issue this command, the specified rebuild begins if the rebuild schedule is disabled; otherwise, the rebuild pauses until the next scheduled rebuild. A file system check is recommended following rebuild when using the ignoreECC option. /cx/ux start verify Also referred to as a manual verify, the /cx/ux start verify command starts a background verification process on the specified unit /cx/ux.
Unit Object Commands /cx/ux set autoverify=on|off The /cx/ux set autoverify command allows you to turn on and turn off the autoverify operation on a specified unit /cx/ux. By default, autoverify is on. When autoverify is on and the basic verify schedule is used (verify=basic), a verify automatically runs at the basic verify time (Friday at midnight, by default). If the system is not on at that time, verification starts the next time the system is powered up.
Chapter 2. CLI Syntax Reference /cx/ux set rdcache=basic|intelligent|off The /cx/ux set rdcache command allows you to set the read cache to either Basic, Intelligent, or Off on a specified unit. Setting this to Intelligent enables both Intelligent Mode features and Basic Mode features. Setting it to Off disables both. Read Cache Basic Mode is used to store data that has been written recently to media and is likely to be frequently accessed, to the read cache on the controller.
Unit Object Commands /cx/ux set identify=on|off This command requires a supported enclosure. For additional information about enclosure-related commands, see “Enclosure Object and Element Commands” on page 109. The /cx/ux set identify command allows you to identify a unit within an enclosure by blinking the LEDs associated with the drive slots of the specified unit. Example: //localhost> /c0/u0 set identify=on Sending Identify request for unit /c0/u0 to [on] ... Done.
Chapter 2. CLI Syntax Reference /cx/ux set qpolicy=on|off The /cx/ux set qpolicy command sets the queue policy for the drives on the unit. If the queue policy is on, the firmware utilizes the drive’s queueing policy. However, the /cx/ux set qpolicy command has no effect on drives that do not support a queueing policy. By default, qpolicy is on. This setting is only applicable for SATA drives that support native command queueing (NCQ) and has no effect on SAS units.
Unit Object Commands settings. The following description about the settings can help you to decide which one is suitable to your application. For more information, refer to the discussion of this setting in the 3ware SATA+SAS RAID Controller Card Software User Guide, Version 10.2, under “About StorSave Profile Levels”. protect provides the maximum data protection among the controller settings.
Chapter 2. CLI Syntax Reference /cx/ux migrate type=RaidType [disk=p:-p] [group=3|4|5|6|7|8|9|10|11|12|13|14|15|16] [stripe=size] [noscan] [nocache] [autoverify] The /cx/ux migrate command allows you to change the existing configuration of a unit by using type=RaidType.
Unit Object Commands Note: You can only migrate a unit to a RAID level that has the same or more capacity as the existing one. You can migrate a four-drive RAID 5 unit to a four-drive RAID 0, but you cannot migrate a four-drive RAID 0 unit to a four-drive RAID 5 unless you add another drive, due to the need for additional storage capacity for parity bits.
Chapter 2. CLI Syntax Reference Note: You can have a maximum of four subunits in a RAID 50 unit Note that a sufficient number of disks are required for a given pattern or disk group. For example, given 6 disks, specifying 3 creates two RAID 5 arrays. With 12 disks, specifying 3 creates four RAID 5 arrays under the RAID 0 level. With only 6 disks, a grouping of 6 is not allowed, because you are basically creating a RAID 5. The default RAID 50 grouping varies based on number of disks.
Unit Object Commands on your operating system, you might need to first unmount the unit, then use CLI commands to remove and rescan the unit so that the operating system can determine the new capacity, and then remount the unit. For details see “/cx/ux remove [noscan] [quiet]” on page 78 and “/cx rescan [noscan]” on page 57. If necessary, you can resize the file system or add a new partition. For instructions, consult the documentation for your operating system.
Chapter 2. CLI Syntax Reference 3ware CLI> /c0 show Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy --------------------------------------------------------------------------u0 RAID-5 OK 64K 596.004 RiW OFF u2 SPARE OK 149.042 OFF u3 Migrator MIGRATING 39 149.001 RiW OFF VPort Status Unit Size Blocks Serial ----------------------------------------------------------------------p0 OK u0 149.05 GB 312581808 WD-WCANM1771318 p1 OK u0 149.05 GB 312581808 WD-WCANM1757592 p2 OK u0 149.
Unit Object Commands Note the difference in UnitType and Status of u0 and u1, even though they are both migrating units. 3ware CLI> /c0 show Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy -------------------------------------------------------------------------u0 Migrator MIGRATING 26 298.002 RiW OFF u1 RAID-1 REBUILD-PAUSED 0 372.519 OFF OFF Port Status Unit Size Blocks Serial ----------------------------------------------------------------------p0 OK u0 149.
Chapter 2. CLI Syntax Reference Port Object Commands Port object messages are commands that provide information and perform actions related to a specific disk that is attached to a port (or virtual port), such as /c0/p0. You use port object commands for such tasks as viewing information about the status, model, or serial number of the drive. Note that all references to port also apply to VPort for the commands in this section. Syntax /cx/px show /cx/px show attribute [attribute ...
Port Object Commands /cx/px show attribute [attribute ...] The /cx/px show attribute command shows the current setting of the given attributes on the specified port or drive. You can request one or many attributes. If you specify an invalid attribute, the loop terminates. Possible attributes are: capacity, firmware, identify, lspeed, model, ncq, serial, smart (SATA only), and status.
Chapter 2. CLI Syntax Reference /cx/px show identify The /cx/px show identify command requires a supported enclosure. The /cx/px show identify command shows whether the LED of the drive attached to the specified port is set to on or off. For details, see “/cx/px set identify=on|off” on page 101.
Port Object Commands /cx/px show serial The /cx/px show serial command shows the serial number of the drive attached to the specified port. Example: //localhost> /c0/p5 show serial /c0/p5 Serial = WD-WMACK140649 /cx/px show smart The /cx/px show smart command extracts SMART data from a specified SATA disk. This command will output drive attributes in hex format without any decoding. (For additional information, please refer to AT Attachment standard.
Chapter 2.
Port Object Commands /c3/p3 /c3/p3 /c3/p3 /c3/p3 /c3/p3 /c3/p3 /c3/p3 /c3/p3 /c3/p3 /c3/p3 /c3/p3 /c3/p3 /c3/p3 Interface Type = Direct Drive Ports = 1 Drive Connections = 1 Link Speed Supported = 1.5 Gbps Link Speed = 1.
Chapter 2. CLI Syntax Reference /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 /c1/p2 Status = OK Model = SEAGATE ST936701SS Firmware Version = 0002 Serial = 3LC0DB25 Capacity = 34.18 GB (71687371 Blocks) WWN = 5000c500003ac760 Drive Type = SAS Interface Type = Direct Drive Ports = 2 Drive Connections = 1 Reallocated Sectors = 0 Power On Hours = 0 Temperature = 44 deg C Spindle Speed = 10000 RPM Link Speed Supported = 1.
Port Object Commands Monitoring” in the 3ware SATA+SAS RAID Controller Card Software User Guide, Version 10.2. Example of running average (RA) statistics //localhost> /c0/p3 show dpmstat type=ra Queue Xfer Resp Port Status Unit Depth IOPs Rate(MB/s) Time(ms) -------------------------------------------------------------p3 OK u0 0 435 25.
Chapter 2.
Port Object Commands /cx/px remove [quiet] The /cx/px remove command allows you to remove (or export) a port (or drive) /cx/px. The command instructs the firmware to remove the specified port from its pool of managed ports. When the drive is removed, the DCB (Disk Configuration Block) metadata remains on the attached disk. You can import (or re-introduce) the port by rescanning the controller. quiet is for noninteractive mode.
Chapter 2. CLI Syntax Reference This command allows you to clear the statistics counters of the Drive Performance Monitor. The optional type attribute specifies which statistics should be cleared. The options are: ra for Running Average, lct for Long Command Times, and ext for Extended Drive Statistics. For more about these statistics, see “/cx/px show dpmstat type=inst|ra|lct|histdata|ext” on page 98. Please note that if type=ra, both the Running Average and Histogram data are cleared.
BBU Object Commands Supported, Enabled, and Control. The Supported and Enabled values are set for the phy and are not changeable. The Control value is the link speed that can be set with the /cx/phyx set link=auto|1.5|3.0|6.0 command. The default is auto. Example: //localhost> /c3/phy0 show Device --- Link Speed (Gbps) --Phy SAS Address Type Device Supported Enabled Control -------------------------------------------------------------------------phy0 2007020800153811 SATA /c3/p1 1.5-3.0 3.0 1.
Chapter 2. CLI Syntax Reference /cx/bbu show attribute [attribute ...] where attributes are: batinst|bootloader|cap|fw|lasttest|pcb|ready|serial| status|temp|tempstat|tempval|volt /cx/bbu show all /cx/bbu test [quiet] Warning: Can take up to 24 hours to complete. Write cache will be disabled during the test. /cx/bbu enable /cx/bbu disable [quiet] /cx/bbu show The /cx/bbu show command presents a summary report on the specified BBU object.
BBU Object Commands /cx/bbu show bootloader The /cx/bbu show bootloader command shows the BBU's boot loader version. Note that the BBU bootloader version is not applicable for 9750 models. /cx/bbu show cap The /cx/bbu show cap command shows the battery capacity in hours. Note: A battery test should be run every four weeks in order to get a reliable estimate of battery capacity, and to determine when it needs to be replaced (an AEN is also issued as a reminder).
Chapter 2. CLI Syntax Reference /cx/bbu show status The /cx/bbu show status command shows the status of the BBU. Possible values are as follows: Testing. A battery test is currently in progress. This test can take up to 24 hours to complete. During the test, the BBU is not capable of backup operation and the write cache might be disabled, deending on the unit’s Storsave setting.
BBU Object Commands /cx/bbu show temp The /cx/bbu show temp command shows the temperature status of the battery. The status can be OK, HIGH, LOW, TOO-HIGH, and TOO-LOW. The HIGH and LOW are in warning range. TOO-HIGH and TOO-LOW are out of the operating range and indicate the need to replace the battery. (Contact LSI to obtain a replacement battery.) This command is equivalent to the command /cx/bbu show tempstat.
Chapter 2. CLI Syntax Reference /c1/bbu /c1/bbu /c1/bbu /c1/bbu /c1/bbu /c1/bbu /c1/bbu Battery Temperature Status = OK Battery Temperature Value = 25 deg C Estimated Backup Capacity = 241 Hours Last Capacity Test = 22-Jun-2008 Battery Installation Date = 20-Jun-2008 Bootloader Version = BBU 0.02.00.002 PCB Revision = 65 /cx/bbu test [quiet] The /cx/bbu test command starts the battery capacity test. The test can take up to 24 hours to complete.
Enclosure Object and Element Commands Enclosure Object and Element Commands Enclosure object commands provide information and perform actions related to a specific enclosure, such as /c0/e0 and its elements, for example, /c0/e0/ slot0. Enclosure object elements include slot, fan, temperature sensor, power supply, and alarm elements. Note: The command descriptions of this section show the syntax of enclosure commands for 9750 and 9690SA controllers, which specify the controller ID and the enclosure ID.
Chapter 2. CLI Syntax Reference /cx/ex/fanx set identify=on|off /cx/ex/fanx set speed=<0|1|2|3|4|5|6|7> /cx/ex/pwrsx show /cx/ex/pwrsx show identify /cx/ex/pwrsx set identify=on|off /cx/ex/tempx show /cx/ex/tempx show identify /cx/ex/tempx set identify=on|off /cx/ex/almx show /cx/ex/almx set alarm=mute|unmute|off /cx/ex show The /cx/ex show command applies to 9750 and 9690SA controllers. For the 9650SE and CCU enclosure, simply drop the prepended controller name in the command and use /ex.
Enclosure Object and Element Commands pwrs0 pwrs1 OK OK on on OK OK OK OK Off Off Slot Status VPort Identify -------------------------------------------------slot0 OK /c0/p0 Off slot1 NO-DEVICE Off slot2 OK /c0/p1 Off slot3 OK /c0/p2 Off slot4 OK /c0/p3 Off slot5 OK /c0/p4 Off slot6 OK /c0/p5 Off slot7 OK /c0/p6 Off slot8 OK /c0/p7 Off slot9 OK /c0/p8 Off slot10 OK /c0/p9 Off slot11 NO-DEVICE Off Alarm Status State Audibility -------------------------------------------------alm0 OK OFF UNMUTE /cx/ex
Chapter 2. CLI Syntax Reference /cx/ex/ show diag=helptext The /cx/ex show diag=helptext command applies only to 9750 and 9690SA controllers. For the 9650SE, simply drop the prepended controller name in the command and use /ex. The /cx/ex show diag=helptext command allows you to view the enclosure diagnostic log. What is reported by this log varies depending upon the manufacturer of the enclosure.
Enclosure Object and Element Commands 2 - Low 3 - Medium-low 4 - Medium 5 - Medium-high 6 - High 7 - Highest The Identify column lists the Identify setting of the fans.
Chapter 2. CLI Syntax Reference /cx/ex show pwrs The /cx/ex show pwrs command applies only to 9750 and 9690SA controllers. For the 9650SE, simply drop the prepended controller name in the command and use /ex. The /cx/ex show pwrs command shows a summary of power supplies with their respective information for the specified enclosure.
Enclosure Object and Element Commands /cx/ex show all The /cx/ex/show all command applies only to 9750 and 9690SA controllers. For the 9650SE, simply drop the prepended controller name in the command and use /ex. The /cx/ex/show all command shows the current settings of all attributes for enclosure /cx/ex. /cx/ex/slotx show The /cx/ex/slotx show command applies only to 9750 and 9690SA controllers. For the 9650SE, simply drop the prepended controller name in the command and use /ex.
Chapter 2. CLI Syntax Reference /cx/ex/slotx set identify=on|off The /cx/ex/slotx set identify command applies only to 9750 and 9690SA controllers. For the 9650SE, simply drop the prepended controller name in the command and use /ex. If the enclosure supports Slot Identify, this command identifies the specified slot by blinking the LED associated with it, or turns off identification of the LED for this slot. Setting identify to on causes the LED associated with that slot to blink.
Enclosure Object and Element Commands /cx/ex/fanx set identify=on|off The /cx/ex/fanx set identify command applies only to 9750 and 9690SA controllers. For the 9650SE, simply drop the prepended controller name in the command and use /ex. If the enclosure supports Fan Identify and there is an LED associated with the fan, this command causes the LED associated with the fan to blink, or turns off identification of the LED for this fan.
Chapter 2. CLI Syntax Reference are OK and OVER-CURRENT. In either case, OVER means over the set threshold of the voltage or current. If a power supply is on and no fault has been detected, the status indicates OK. Example: //localhost> /c0/e0/pwrs0 show PowerSupply Status State Voltage Current Identify -----------------------------------------------------------pwrs0 OK on OK OK Off /cx/ex/pwrsx show identify The /cx/ex/pwrsx show identify command applies only to 9750 and 9690SA controllers.
Enclosure Object and Element Commands /cx/ex/tempx show The /cx/ex/tempx show command applies only to 9750 and 9690SA controllers. For the 9650SE, simply drop the prepended controller name in the command and use /ex. The /cx/ex/tempx show command shows the information about the specified temperature sensor element /tempx in the specified enclosure cx/ex.
Chapter 2. CLI Syntax Reference /cx/ex/almx show The /cx/ex/almx show command applies only to 9750 and 9690SA controllers. For the 9650SE, simply drop the prepended controller name in the command and use /ex. The /cx/ex/almx show command shows information about the specified enclosure alarm. The possible status values are OK, FAIL, NOTINSTALLED, and ACTIVATED. The status values are described below. The possible values for State are ON and OFF. The possible values for Audibility are UNMUTE and MUTED.
Enclosure Object and Element Commands Note: Some enclosures support alarms but not the mute/unmute function. For these enclosures, using this command to set the alarm to mute returns an error message indicating that the feature is not supported. For these enclosures, the alarm is not mutable; however, it can be turned off. If you set this command to unmute for an enclosure that does not support mute, the command appear to complete and does not report an error.
Chapter 2. CLI Syntax Reference Help Commands The Help commands provides brief on-line help. You can get overview help by typing Help at the top-level prompt. This lists a brief definition of commands. (For an example, see the discussion of the command “help” on page 124.) You can also get help with specific commands, by typing help before an object name, or by typing a question mark (?) at the point in a command where you are uncertain of the attributes.
Help Commands (group=13-16 9750/9690SA)[name=string (9000 series)] [ignoreECC][autoverify][noqpolicy][v0=n|vol=a:b:c:d] (n,a,b,c,d = size of volume in GB) (9000 series) [storsave=(9KSX/SE/SA) [rapidrecovery=(all|rebuild|disable)] (9KSE/SA only) RaidType={raid0, raid1, raid5, raid10, raid50, single, spare, raid6 (9750, 9690SA, and 9650SE)} /cx add rebuild=ddd:hh:duration (9000 series) /cx add verify=ddd:hh:duration (9000 series) /cx add selftest=ddd:hh (9000 series) /cx del rebuild=
Chapter 2. CLI Syntax Reference bios|carvesize(9000series)| driver|drivestatus|firmware|memory|model| monitor|numdrives|numports|numunits|ctlbus(9000 series SX/SE/SA only)|serial|pcb| pchip|spinup|stagger|unitstatus| /cx show all where all means attributes and configurations.
Help Commands help show The help show command provides specific show-related help, illustrating various ways to use the show command. It provides reports on Controllers, Units, and Drives. See the section “Shell Object Commands” on page 25 for more information. help flush The help flush command provides specific flush-related help, illustrating various ways to use the flush command. See the section “Shell Object Commands” on page 25 for more information.
Chapter 2. CLI Syntax Reference help /cx/ux The help /cx/ux command provides specific unit /cx/ux-related help, illustrating various commands to use on a unit /cx/ux. See the section “Unit Object Commands” on page 71 for more information. help /cx/px The help /cx/px command provides specific /cx/px-related help, illustrating various ways to use the /cx/px command. See the section “Port Object Commands” on page 92 for more information.
Command Logging help /cx/ex/tempx help /cx/ex/tempx command provides specific temperature sensor cx/ex/ tempx-related help, illustrating various ways to use the cx/ex/tempx command. See the section “Enclosure Object and Element Commands” on page 109 for more information. help /cx/ex/pwrsx help /cx/ex/pwrsx command provides specific power supply /cx/ex/pwrsxrelated help, illustrating various ways to use the /cx/ex/pwrsx command.
Chapter 2. CLI Syntax Reference Window. To make the folder permanently visible, select Organize > Folder and Search Options from the Explorer menu, choose the View tab, and select the Show hidden files and folders option in Advance settings. For all previous versions of Windows (XP, Server 2003, etc.
Return Code Note: Setting the environment variable according to the preceding description is not persistent across reboot, because the the shell terminates when you power down the system, and defaults are reset on powerup. To set an environment variable that persists, set a global variable in a login config file (such as .rc or .cshrc) that sets the variable to the desired state when the system powers up. For details, see the manpage for the shell you are using.
Chapter 2. CLI Syntax Reference If you type the following tw_cli /c7 show error: (CLI003) specified controller does not exist. echo $? 1 This example fails (returns 1) because there is no controller 7. To view the return code for Windows, in a command window type: tw_cli /c0 show (c0 info shown here) if errorlevel 0 echo 0 0 tw_cli /c7 show error.... if errorlevel 1 echo 1 1 This example fails (returns 1) because there is no controller 7. 130 3ware SATA+SAS RAID Controller Card CLI Guide, Version 10.
