Serial ATA RAID Controller Command Line Interface Supports the 9590SE-4ME for the Power Mac® G5 PN: 720-0140-00 September 2006 CLI Guide for the Power Mac G5 3ware®
Copyright ©2003-2006 Applied Micro Circuits Corporation (AMCC). All rights reserved. This publication may be copied or reproduced for reference purposes only. All other purposes require the express written consent of AMCC, 215 Moffett Park Drive, Sunnyvale, CA 94089. AMCC shall not be responsible or liable for, and shall be held harmless against, any and all damages, claims, and/or disputes that arise from the copying or reproduction of this publication.
Table of Contents Chapter 1. Introduction to the 3ware Command Line Interface . . . . . . .3 Features of the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Installing the 3ware CLI on Mac OS X . . . . . . . . . . . . . . . . . . . .
/cx show numdrives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 /cx show numports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 /cx show numunits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 /cx show ctlbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 /cx show exportjbod . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
/cx/ux show name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 /cx/ux show serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 /cx/ux show qpolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 /cx/ux show storsave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 /cx/ux show identify . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
/cx/bbu show pcb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 /cx/bbu show bootloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 /cx/bbu show all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 /cx/bbu test [quiet] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 /cx/bbu enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this CLI Guide 3ware Serial ATA RAID Controller CLI Guide for the Power Mac G5 provides instructions for configuring and maintaining your 3ware controller using 3ware’s command line interface (CLI). Note: This guide assumes that you have already installed your 3ware RAID controller in your system and set up your 3ware Sidecar. If you have not yet done so, see the installation guide that came with your 3ware RAID controller for instructions.
2 3ware Serial ATA RAID Controller CLI Guide for the Power Mac G5
1 Introduction to the 3ware Command Line Interface 3ware RAID controllers can be managed using the CLI via a command line or script. Important! For all of the functions of the 3ware CLI to work properly, you must have the proper CLI, firmware, and driver versions installed. Check http://www.3ware.com for the latest versions and upgrade instructions.
Chapter 1. Introduction to the 3ware Command Line Interface Supported Operating Systems The 3ware CLI is supported under the following operating systems: • Mac OS X, running in a Power Mac® G5 (PowerPC™-based) with PCI Express®. • Windows®. Windows 2000, Windows XP, and Windows Server 2003, both 32-bit and 64-bit. • Linux®. Redhat, SuSE, both 32-bit and 64-bit. • FreeBSD®, both 32-bit and 64-bit.
Installing the 3ware CLI on Mac OS X 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 3ware web site, http://www.3ware.com/support/ download.asp. To install 3ware CLI on Mac OS X • Run the installer and select CLI as the software to be installed.
Chapter 1. Introduction to the 3ware Command Line Interface Using the command interface interactively You can use 3ware CLI interactively, entering commands at the main prompt and observing the results on the screen. To use the CLI interactively 1 Enter the following command: ./tw_cli The main prompt is displayed, indicating that the program is awaiting a command. //localhost> 2 At the CLI prompt, you can enter commands to show or act on 3ware controllers, units, and drives.
Working with 3ware CLI 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 which 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 executes the file clicommand.txt, and runs the CLI commands included in that file.
Chapter 1. Introduction to the 3ware Command Line Interface Conventions The following conventions are used through this guide: • In text, monospace font is used for code and for things you type. • In descriptions and explanations of commands, a bold font indicates the name of commands and parameters, for example, /c0/p0 show all.
Understanding RAID Levels and Concepts RAID Concepts The following concepts are important to understand when working with a RAID controller: • Arrays and Units. In the storage industry, the term “array” is used to describe two or more disk drives that appear to the operating system as a single unit. When you work with 3ware software, “unit” is the term used to refer to an array of disks that is configured and managed through the 3ware software.
Chapter 1. Introduction to the 3ware Command Line Interface Available RAID Configurations The following RAID levels and configurations are available for drives attached to a 9590SE-4ME 3ware RAID controller: • RAID 0 • RAID 1 • RAID 5 • RAID 10 • Single Disk • Hot Spare Note: You may notice mention of RAID 50 in the Command Syntax sections of the CLI Guide. RAID 50 requires six or more drives, and so is not available using the 9590SE-4ME.
Understanding RAID Levels and Concepts Figure 1. RAID 0 Configuration Example RAID 1 RAID 1 provides fault tolerance and a speed advantage over non-RAID disks. Also known as a mirrored array. Mirroring is done on pairs of drives. Mirrored disk arrays write the same data to two different drives using RAID 1 algorithms (see Figure 2). This gives your system fault tolerance by preserving the data on one drive if the other drive fails.
Chapter 1. Introduction to the 3ware Command Line Interface Figure 3. RAID 5 Configuration Example RAID 10 RAID 10 is a combination of striped and mirrored arrays for fault tolerance and high performance. When drives are configured as a striped mirrored array, the disks are configured using both RAID 0 and RAID 1 techniques, thus the name RAID 10 (see Figure 4). A minimum of four drives are required to use this technique. The first two drives are mirrored as a fault tolerant array using RAID 1.
Understanding RAID Levels and Concepts Single Disk A single drive can be configured as a unit through 3ware software. (3DM 2 or CLI). Like disks in other RAID configurations, single disks contain 3ware Disk Control Block (DCB) information and are seen by the OS as available units. Single drives are not fault tolerant and therefore not recommended for high availability systems unless additional precautions are taken to prevent system hangs and data loss.
Chapter 1. Introduction to the 3ware Command Line Interface Using Drive Capacity Efficiently To make the most efficient use of drive capacity, it is advisable to use drives of the same capacity. This is because the capacity of each drive is limited to the capacity of the smallest drive in the unit.
2 CLI Syntax Reference Note: The 3ware controller used for the Power Mac G5 is the 9590SE-4ME. AMCC makes a number of other 3ware controller models, including 9000-series (9500S, 9550SX, and 9590SE), and earlier 7000/8000 series boards, that work on other platforms. The command syntax described in this document supports all of those boards, however some features are only supported on specific 3ware controller models. We have tried to indicate the controller model in the Syntax description.
Chapter 2.
Common Tasks Mapped to CLI Commands Table 4: Common Tasks Mapped to CLI Commands Task CLI Command Page Add a time slot to a verify schedule /cx add verify 46 Add a time slot to a selftest schedule /cx add selftest 47 Enable/disable the rebuild/migrate schedule and set the task rate /cx set rebuild 48 Enable/disable the verify schedule and set the task rate /cx set verify 49 Enable/disable the selftest schedule /cx set selftest 49 View Alarms /cx show alarms 40 Start a rebuild /cx/ux s
Chapter 2. CLI Syntax Reference Syntax Overview The command syntax uses the general form: Object Command Attributes Objects are shell commands, controllers, units, ports (drives), BBUs (battery backup units), and enclosures. Commands can either select (show, get, present, read) attributes or alter (add, change, set, write) attributes. Attributes are either Boolean Attributes or Name-Value Attributes.
Shell Object Commands Port Object Commands. Port object commands provide information and perform actions related to a drive on a specific port. For example, you use port object commands for such tasks as seeing the status, model, or serial number of the drive. For details, see “Port Object Commands” on page 69. BBU Object Commands. BBU object commands provide information and perform actions related to a Battery Backup Unit on a specific controller. For details, see “BBU Object Commands” on page 74.
Chapter 2. CLI Syntax Reference if you set the focus to //hostname/c0/u0, the prompt changes to reflect that, and you only have to type show. The concept is similar to being in a particular location in a file system and requesting a listing of the current directory. object can have the following forms: specifies the fully qualified URI (Universal Resource Identifier) of an object on host hostname, controller cx, unit ux. //hostname/cx/ux //hostname specifies the root of host hostname. ..
Shell Object Commands (Not Optimal) state, RRate (Rebuild Rate) of 2, VRate (Verify Rate) of 5, BBU of '-' (Not Applicable). Not Optimal refers to any state except OK and VERIFYING. Other states include VERIFY-PAUSED, INITIALIZING, INITPAUSED, REBUILDING, REBUILD-PAUSED, DEGRADED, MIGRATING, MIGRATE-PAUSED, RECOVERY, INOPERABLE, and UNKNOWN. RRate also applies to initializing, migrating, and recovery background tasks.
Chapter 2. CLI Syntax Reference show alarms [reverse] This command shows the alarms or AEN messages of all controllers in the system. The default is to display the most recent message first. The reverse attribute displays the most recent message last. show diag This command shows the diagnostic information of all controllers in the system. show rebuild This command displays all rebuild schedules for the 9000 controllers in the system.
Shell Object Commands show verify This command displays all verify schedules for the 9000 controllers in the system.
Chapter 2. CLI Syntax Reference flush This command sends a flush command to all 3ware controllers in the system. For more information, see “/cx flush” on page 39. rescan This command sends a rescan command to all 3ware controllers in the system. For more information, see “/cx rescan [noscan]” on page 38. commit This command sends a commit command to all 3ware controllers in the system. For more information, see “/cx commit” on page 39.
Controller Object Commands Controller Object Commands Controller object commands provide information and perform actions related to a specific controller, such as /c0. For example, you use controller object commands to see alarms specific to a controller, to create schedules for when background tasks are run, and to set policies for the controller. You also use the controller object command /cx add type to create RAID arrays. Syntax /cx show /cx show attribute [attribute ...
Chapter 2. CLI Syntax Reference /cx set verify=enable|disable|1..5 (9000 only) /cx set selftest=enable|disable [task=UDMA|SMART](9000 only) /cx /cx /cx /cx /cx /cx flush update filename_with_path [force] (9000 only) commit (Windows only. Also known as shutdown) start mediascan (7000/8000 only) stop mediascan (7000/8000 only) rescan [noscan] (Does not import non-JBOD on 7000/8000 models. /cx show This command shows summary information on the specified controller /cx.
Controller Object Commands Typical output looks like: //localhost> /c0 show Unit UnitType Status %Cmpl Stripe Size(GB) Cache AVerify IgnECC -------------------------------------------------------------------------u0 RAID-1 OK 149.05 ON OFF OFF u1 RAID-5 OK 64k 298.22 ON OFF OFF u2 SPARE OK 149.05 ON OFF Port Status Unit Size Blocks Serial --------------------------------------------------------------p0 OK u0 149.05 GB 312581808 3JS0TF14 p1 OK u0 149.05 GB 312581808 3JS0TETZ p2 OK u1 149.
Chapter 2. CLI Syntax Reference /cx show driver This command reports the device driver version associated with controller /cx. Example: //localhost> /c0 show driver /c0 Driver Version = 2.x /cx show model This command reports the controller model of controller /cx. Example: //localhost> /c0 show model /c0 Model = 9500-x /cx show firmware This command reports the firmware version of controller /cx. Example: //localhost> /c0 show firmware /c0 Firmware Version = FGXX 2.
Controller Object Commands /cx show serial This command reports the serial number of the specified controller /cx. Example: //localhost> /c0 show serial /c0 Serial Number = F12705A3240009 /cx show pcb This command reports the PCB (Printed Circuit Board) version of the specified controller /cx. Example: //localhost> /c0 show pcb /c0 PCB Version = RevX /cx show pchip This command reports the PCHIP (PCI Interface Chip) version of the specified controller /cx.
Chapter 2. CLI Syntax Reference /cx show numports This command reports the port capacity (number of physical ports) of the specified controller /cx. Example: //localhost> /c0 show numports /c0 Number of Ports = 12 /cx show numunits This command reports the number of units currently managed by the specified controller /cx. This report does not include off-line units (or removed units).
Controller Object Commands /cx show spinup This feature only applies to 9000 series controllers. This command reports the number of concurrent disks that will spin up when the system is powered on, after waiting for the number of seconds specified with the set stagger command. Example: //localhost> /c0 show spinup /c0 Disk Spinup Policy = 1 /cx show stagger This feature only applies to 9000 series controllers. This command reports the time delay between each group of spinups at the power on.
Chapter 2. CLI Syntax Reference For operating systems that support units larger than 2TB, there is no need to set the policy to on unless you want the operating system to have multiple smaller volumes. If you use a 32-bit operating system, it is recommended that you keep the policy on unless you know that your operating system supports disks that are larger than 2 TB. When the autocarve policy is off, all newly created units will consist of one single volume.
Controller Object Commands /cx show autorebuild This feature only applies to 9550SX and 9590SE model controllers. This command shows the Auto-Rebuild policy. If the policy is enabled, the firmware will select drives to use for rebuilding a degraded unit using the following priority order. For more information, see “/cx set autorebuild=on|off” on page 51. 1. Smallest usable spare. 2. Smallest usable unconfigured (available) drive. 3. Smallest usable failed drive.
Chapter 2. CLI Syntax Reference /cx show allunitstatus This command presents a count of total and Not Optimal units managed by the specified controller /cx. For more about the meaning of Not Optimal, see “Shell Object Commands” on page 19.
Controller Object Commands /cx show all This command shows the current setting of all of the following attributes on the specified controller: driver, model, firmware, memory, bios, monitor, serial, pcb, pchip, achip, numports, numunits, numdrives, unitstatus, drivestatus, allunitstatus, exportjbod, ondegrade, spinup, autocarve, and stagger. Example: (where x represents the actual version number) //localhost> /c0 show all /c0 Driver Version = 3.
Chapter 2. CLI Syntax Reference /cx add type= disk= [stripe=Stripe] [noscan] [group=<3|4|5|6>] [nocache] [autoverify] [ignoreECC] [name=string] [storsave=] This command allows you to create a new unit on the specified controller. You specify type, disks, and optional stripe size. By default the host operating system will be informed of the new block device, write cache will be enabled, and a storsave policy of protect will be set.
Controller Object Commands group=3|4|5|6 indicates the number of disks per group for a RAID 50 type. (This attribute can only be used when type=raid50.) Recall that a RAID 50 is a multi-tier array. At the bottom-most layer, N number of disks per group are used to form the RAID 5 layer. These RAID 5 arrays are then integrated into a RAID 0. This attribute allows you to specify the number of disks in the RAID 5 level. Valid values are 3, 4, 5 and 6.
Chapter 2. CLI Syntax Reference Table 6: Supported Model-Unit Types for ignoreECC Model R-0 R-1 R-5 R-10 R-50 Single JBOD Spare 7K/8K No No No No No No No No 9K No Yes Yes Yes Yes No No No name=string attribute allows you to name the new unit. (This feature is for 9000 series and above controllers.) The string can be up to 21 characters and cannot contain spaces. In order to use reserved characters (‘<‘, ‘>’, ‘!’, ‘&’, etc.) put double quotes (" ") around the name string.
Controller Object Commands /cx commit This command only applies to the Windows operating system. It commits all changes if a faster shutdown method is needed when running certain database applications. Linux and FreeBSD file systems do not require this command since they have their own ways of notifying the controller to do clean up for shut down. /cx flush This command forces the controller to write all cached data to disk for the specified controller.
Chapter 2. CLI Syntax Reference Recommendation: No need to update. Given the above recommendation... Do you want to continue ? Y|N [N]: y Downloading the firmware from file /tmp/prom0006.img ... Done. The new image will take effect after reboot. force attribute is optional. If you include it, the compatibility checks are bypassed. /cx show alarms [reverse] Asynchronous events (also referred to as AENs or alarms) are originated by firmware and captured by their respective device drivers.
Controller Object Commands In order to redirect the output you must run the following command from a command line, not from within the tw_cli shell. tw_cli /c0 show diag > diag.txt /cx show rebuild 9000 series controllers support background tasks and allow you to schedule a regular time when they occur. Rebuild is one of the supported background tasks. Migrate and initialize are other background tasks that follow the same schedule as rebuild.
Chapter 2. CLI Syntax Reference If the rebuild schedule is enabled while a rebuild process is underway, the rebuild will pause until a scheduled time slot.
Controller Object Commands p9 p10 p11 OK OK OK u0 u0 u0 74.53 GB 74.53 GB 74.53 GB 156301488 156301488 156301488 3JV3WRHC 3JV3WQLQ 3JV3WQLZ /cx show verify 9000 series controllers support background tasks and allow you to schedule a regular time when they occur. Verify is one of the supported background tasks. Rebuild and selftest are other background tasks for which there are separate schedules. Migrate and initialize are additional background tasks that follow the same schedule as rebuild.
Chapter 2. CLI Syntax Reference /cx show selftest 9000 series controllers support background tasks and allow you to schedule a regular time when they occur. Selftest is one of the supported background tasks. Rebuild and verify are other background tasks for which there are separate schedules. Migrate and initialize are additional background tasks that follow the same schedule as rebuild. For each background task, up to 7 time periods can be registered, known as slots 1 through 7.
Controller Object Commands /cx add rebuild=ddd:hh:duration This command adds a new background rebuild task to be executed on the day ddd (where ddd is Sun, Mon, Tue, Wed, Thu, Fri, and Sat), at the hour hh (range 0 .. 23), for a duration of duration (range 1 .. 24) hours. A maximum of seven rebuild tasks can be scheduled. This command will fail if no (empty) task slot is available.
Chapter 2. CLI Syntax Reference /cx add verify=ddd:hh:duration This command adds a new background verify task to be executed on the day ddd (where ddd is Sun, Mon, Tue, Wed, Thu, Fri, and Sat), at hour hh (range 0 .. 23), for a duration of duration (range 1 .. 24) hours. A maximum of seven verify tasks can be scheduled. This command will fail if no (empty) task slot is available.
Controller Object Commands /cx add selftest=ddd:hh This command adds a new background selftest task to be executed on the day ddd (where ddd is Sun, Mon, Tue, Wed, Thu, Fri, and Sat), at hour hh (range 0 .. 23). Notice that selftest runs to completion and as such no duration is provided. A maximum of seven selftest tasks can be scheduled. This command will fail if no (empty) task slot is available.
Chapter 2. CLI Syntax Reference /cx del verify=slot_id This command removes the verify background task in slot slot_id. Example: //localhost> /c1 del verify=3 removes verify background task in slot 3. Warning: If all time slots are removed, be sure to also disable the schedule. Otherwise the applicable background task will never occur /cx del selftest=slot_id This command removes (or unregisters) the selftest background task in slot slot_id.
Controller Object Commands /cx set verify=enable|disable|1..5 This command enables or disables all verify background task slots on controller /cx and (when enabled) sets the priority of verification versus I/O operations. When enabled, verify tasks will only be run during the time slots scheduled for verifies. If a verify is taking place when the schedule is enabloed, it will be paused until the next scheduled time. The priority of verify versus I/O operations is specified with 1..
Chapter 2. CLI Syntax Reference /cx set ondegrade=cacheoff|follow This command is only for 9500S controllers. This command allows you to set a controller-based write cache policy. If the policy is set to cacheoff and a unit degrades, the firmware will disable the write-cache on the degraded unit, regardless of what the unit-based write cache policy is. If the policy is set to follow and a unit degrades, firmware will follow whatever cache policy has been set for that unit.
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 feature is useful for operating systems limited to 2TB file systems. For example, using the 2 TB default carvesize, a 3 TB unit will be configured into one 2 TB volume and one 1 TB volume. A 5 TB unit will be configured into two 2 TB volumes and one 1 TB volume. When auto-carve policy is set to off, all new units are created as a single large volume.
Chapter 2. CLI Syntax Reference having to specify it as a spare. It also means that if you accidentally disconnect a drive (causing the controller to see it as a failed drive) and then reconnect it, the controller will automatically try 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. /cx start mediascan This command applies only to 7000/8000 controllers.
Unit Object Commands Unit Object Commands Unit Object commands provide information and perform actions related to a specific unit, such as /c0/u1 (unit 1 on controller 0). For example, you use logical disk object commands for such tasks as seeing the rebuild, verify, or initialize status of a unit, starting, stopping, and resuming rebuilds and verifies, and setting policies for the unit. Syntax /cx/ux show /cx/ux show attribute [attribute ...
Chapter 2. CLI Syntax Reference One application of the /cx/ux show command is to see which sub-unit of a degraded unit has caused the unit to degrade and which disk within that subunit is the source of degradation. Another application is to see the source and destination units during a migration. Example: //localhost> /c0/u1 show Unit UnitType Status %Cmpl Port Stripe Size(GB) Blocks ---------------------------------------------------------------------u1 RAID-0 OK 64K 3576.
Unit Object Commands /cx/ux show rebuildstatus This command reports the rebuildstatus (if any) of the specified unit. Example: //localhost> /c0/u5 show rebuildstatus /c0/u5 is not rebuilding, its current state is OK If the unit is in the process of migrating, the command will return the following: //localhost> /c0/u5 show rebuildstatus /c0/u5 is not rebuilding, its current state is MIGRATING /cx/ux show verifystatus This command reports the verifystatus (if any) of the specified unit.
Chapter 2. CLI Syntax Reference /cx/ux show qpolicy This feature only applies to 9550SX and 9590SE model controllers. This command reports the queue policy of the firmware. If the queue policy is on, the firmware utilizes the drive queueing policy. If some drives in the unit do not support a queueing policy, this policy will have no effect on those drives. Note that currently only NCQ will be enabled, not tag-queueing.
Unit Object Commands /cx/ux show cache This command shows the current write cache state of the specified unit. Example: //localhost> /c0/u0 show cache /c0/u0 Cache State = on /cx/ux show ignoreECC This feature only applies to 9000 series controllers. This 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 volumes This feature only applies to 9000 series controllers.
Chapter 2. CLI Syntax Reference u1-2 u1-3 u1-4 u1-5 u1-6 u1-7 u1-8 u1-9 u1-10 u1-11 u1/v0 u1/v1 DISK DISK DISK DISK DISK DISK DISK DISK DISK DISK VOLUME VOLUME OK OK OK OK OK OK OK OK OK OK - - - p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 - - 298.20 298.20 298.20 298.20 298.20 298.20 298.20 298.20 298.20 298.20 500.00 3078.40 /cx/ux remove [noscan] [quiet] This command allows you to remove (or export) a unit.
Unit Object Commands noscan is used to not inform the operating system of this change. The default is to inform the operating system. quiet is used for non-interactive mode. No confirmation is given and the command is executed immediately. This is useful for scripting purposes. Example of interactive mode: //localhost> /c0/u0 del Are you sure you want to delete the unit /c0/u0? Enter Y to continue. /cx/ux start rebuild disk=p
Chapter 2. CLI Syntax Reference Table 7: Supported RAID (Logical Unit) Types for Verification Model R0 R1 R5 R10 Single Spare 7K/8K No Yes Yes Yes N/A No 9K Yes Yes Yes Yes Yes Yes When you issue this command, the specified verify will begin if schedules are disabled; otherwise it will pause until the next scheduled verify. Verify will also pause if a rebuild or initialization is currently in progress.
Unit Object Commands /cx/ux flush This command allows you to flush the write cache on the specified unit /ux associated with controller /cx. Note that this command does not apply to spare unit types. /cx/ux set autoverify=on|off This feature only applies to 9000 series controllers. This command allows you to turn on and off the autoverify operation on a specified unit /cx/ux during allocated schedule windows. You can use the show verify command to display the existing schedule windows.
Chapter 2. CLI Syntax Reference /cx/ux set identify=on|off This feature only applies to 9550SX and 9590SE model controllers. This command allows you to identify a unit within an enclosure. When that the EPCT (Enclosure Port Configuration Table) equates identify with blinking, as it does in the 3ware Sidecar Enclosure, the LEDs associated with the drive slots of the specified unit blink. Example: //localhost> /c0/u0 set identify=on Sending Identify request for unit /c0/u0 to [on] ... Done.
Unit Object Commands By default, qpolicy is off. Example: //localhost> /c0/u5 set qpolicy = on Setting Command Queuing Policy for unit /c0/u5 to [on] ... Done. /cx/ux set storsave=protect|balance|perform [quiet] This command applies only to 9550SX and 9590SE model controllers. This command sets the storsave policy to be either protect, balance, or perform when the unit write cache is enabled. The default setting is protect.
Chapter 2. CLI Syntax Reference • Write journaling is disabled, if no BBU is present, and is enabled, if a BBU is present. All data flushing from controller cache will be flushed to media if a BBU is installed and enabled. Otherwise, data will be flushed to disk only. • Incoming FUA (Force Unit Access) host requests will be honored unless a BBU is installed and enabled, in which case, they will be ignored.
Unit Object Commands Warning: Do not split a RAID 1 unit if you are booted from the drives or if the unit is mounted. Once the unit is split, any pending writes cannot be written to the second drive. In addition, the file system on the drive will not be clean. type=RaidType specifies the RAID type of the destination unit. Possible unit types include raid0, raid1, raid5, raid10, raid50, or single. For example, type=raid5 indicates the destination unit is RAID-5.
Chapter 2. CLI Syntax Reference group=3|4|5|6 indicates the number of disks per group for a RAID 50 type. (This attribute can only be used when type=raid50.) Recall that a RAID 50 is a multi-tier array. At the bottom-most layer, N number of disks per group are used to form the RAID 5 layer. These RAID 5 arrays are then integrated into a RAID 0. This attribute allows you to specify the number of disks in the RAID 5 level. Valid values are 3, 4, 5 and 6.
Unit Object Commands autoverify attribute enables the autoverify attribute on the unit that is to be migrated. For more details on this feature, see “/cx/ux set autoverify=on|off” on page 61. Migration Process In all cases of migration, the background migration process must be completed before the newly sized unit is available for use. You can continue using the original unit during this time. Once the migration is finished, a reboot will be required if you are booted from the unit.
Chapter 2. CLI Syntax Reference //localhost> /c0/u0 migrate type=raid10 disk=2-3 stripe=16 Sending migration message to /c0/u0 ... Done. 3ware CLI> /c0 show Unit UnitType Status %Cmpl Stripe Size(GB) Cache AVerify IgnECC --------------------------------------------------------------------------u0 Migrator MIGRATING 67% 74.4951 ON OFF OFF Port Status Unit Size Blocks Serial --------------------------------------------------------------p0 OK u0 74.53 GB 156301488 3JV2Q1VA p1 OK u0 232.
Port Object Commands Port Object Commands Port Object Messages are commands that provide information and perform actions related to a specific disk, attached to a port, such as /c0/p0. You use port object commands for such tasks as seeing the status, model, or serial number of the drive. Syntax /cx/px show /cx/px show attribute [attribute ...
Chapter 2. CLI Syntax Reference /cx/px show status This command displays the status of the drive attached to the specified port. (Definitions of the drive statuses are available in the 3ware Serial ATA RAID Controller User Guide.) Example: //localhost> /c0/p5 show status /c0/p5 Status = OK /cx/px show model This command displays the model of the drive attached to the specified port.
Port Object Commands /cx/px show ncq This command applies only to 9550SX and 9590SE model controllers. This command displays the NCQ (Native Command Queueing) information for the drive attached to the specified port, including whether NCQ is supported by the drive, and whether it is enabled at the drive. For queuing to be used, it must be enabled for the unit and supported by the drive.
Chapter 2. CLI Syntax Reference Example: //localhost> /c0/p5 Drive 10 00 01 0B 00 9A 96 BC 00 00 00 00 ... 00 00 00 00 /c0/p5 show SMART Data: 00 C8 C8 00 14 00 00 00 00 00 05 33 smart 00 00 00 00 00 00 03 07 00 00 04 32 00 64 64 7A 00 C8 C8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2C Note: The SMART data is not decoded. If the drive attached to the specified port is not present or if there are cabling problems reaching the drive, CLI will return an error.
Port Object Commands /cx/px remove [noscan] [quiet] This command allows you to remove (or export) a port (or drive) /cx/px. Exporting a port instructs the firmware to remove the specified port from its pool of managed ports, but does not retain the DCB (Disk Configuration Block) metadata on the attached disk. You can import (or re-introduce) the port by rescanning the controller. noscan is used to not inform the operating system of this change. The default is to inform the operating system.
Chapter 2. CLI Syntax Reference BBU Object Commands BBU (Battery Backup Unit) Object Commands are commands that provide information and perform actions related to a specific BBU installed on a specific controller, such as /c0/bbu. This object is only available on 9000 series controllers on which a BBU is actually installed. (The BBU is not supported on 9590SE-4ME.) Syntax /cx/bbu show (9000 only) /cx/bbu show attribute [attribute ...
BBU Object Commands /cx/bbu show attribute [attribute ...] This command shows the current setting of the given attribute(s) on the BBU board. One or many attributes can be specified. Specifying an invalid attribute will terminate the loop. Possible attributes are: batinst, bootloader, cap, fw, lasttest, pcb, ready, status, serial, temp, volt. /cx/bbu show status This command shows the status of the BBU. Possible values are: Testing. A battery test is currently in progress.
Chapter 2. CLI Syntax Reference /cx/bbu show batinst This command shows the date when the current battery was installed. /cx/bbu show lasttest This command shows the date the battery capacity was last measured. If the battery capacity test has never been run, then 'xx-xxx-xxxx' will be displayed. Note: The estimated BBU capacity hours displayed is based on the measurement taken during the last test. If you have not run the BBU test command for some time, this number can be misleading.
BBU Object Commands /cx/bbu show serial This command shows the BBU serial number. /cx/bbu show fw This command shows the BBU firmware version number. /cx/bbu show pcb This command shows the PCB revision number on the BBU. /cx/bbu show bootloader This command shows the BBU's boot loader version. /cx/bbu show all This command shows the current settings of all BBU-related attributes: ready, status, batinst, lasttest, volt, temp, cap, serial, fw, pcb, bootloader.
Chapter 2. CLI Syntax Reference Note: Once started, the test can not be terminated before it completes. Write cache cannot be enabled until the test completes. AEN (Asynchronous Event Notification) messages are also generated by controllers to notify the user of the command status. Check for AENs with the alarms command /cx show alarms [reverse]. Using the “reverse” attribute displays the most recent AEN message at the bottom of the list.
Enclosure Object Commands Enclosure Object Commands Enclosure object commands provide information and perform actions related to a specific enclosure, such as /e0 and its elements, such as /e0/slot0. Enclosure object elements include slot, fan, and temperature sensor elements. These commands support the 9550SX and 9590SE controllers.
Chapter 2. CLI Syntax Reference TempSensor Temperature ------------------------------temp0 24~C(75~F) Slot Status Port Identify ---------------------------------------------------slot0 OK /c0/p0 No slot1 OK /c0/p1 Yes slot2 NO-DEVICE No slot3 NO-DEVICE No /ex show attribute [attribute ...] This command shows the current setting of the given attribute(s). One or many attributes can be requested. An invalid attribute will terminate the loop.
Enclosure Object Commands /ex show fans This command lists the fans in enclosure /ex and shows their status. Possible statuses are OK and Unknown. Example: //localhost> /e0 show fans Fan Status ---------------------fan0 OK /ex show temp This command lists the temperature sensors in enclosure /ex and the current temperature. The maximum temperature for successful use of a drive should be noted in the documentation for the drive.
Chapter 2. CLI Syntax Reference /ex/slotx show identify This command shows the identify status of the specified slot. The status can be either on or off. Example: //localhost> /e0/slot1 show identify /e0/slot1 Identify status = on /ex/slotx set identify=on|off This command causes the slot to be identified by blinking the LED associated with it, or turns off identification of the LED for this slot.
Help Commands Help Commands The Help commands provides brief on-line help. You can get overview help by typing Help at the top-level prompt. This displays a brief definition of commands in both the new syntax and the legacy syntax. (For an example, see the discussion of the command “help” on page 85.) You can also get help with specific commands, by entering help before an object name, or by typing a question mark (?) at the point in a command where you are uncertain what the attributes are.
Chapter 2. CLI Syntax Reference /cx del selftest=slot_id (9000 only) /cx /cx /cx /cx /cx /cx set exportjbod=on|off (9000 only) set ondegrade=cacheoff|follow (9500S only) set spinup=nn (9000 only) set stagger=nn (9000 only) set autocarve=on|off (9000 only) set rebuild=enable|disable|<1..5> enable|disable for 9000 only) /cx set verify=enable|disable|<1..
Help Commands help This help command provide a table of contents, providing help with the overall navigation of the CLI commands. Typical output looks like the following. //localhost> help Copyright(c) 2004, 2005 Applied Micro Circuits Corporation (AMCC). All rights reserved. AMCC/3ware CLI (version 2.
Chapter 2. CLI Syntax Reference help rescan This command provides specific rescan related help, illustrating various ways to use the rescan command. See the section “Shell Object Commands” on page 19 for more information. help update This command provides specific update-related help. See “Shell Object Commands” on page 19 for more information. help commit This command provides specific commit related help, illustrating various ways to use the commit command.
Return Code help /cx/bbu This command provides specific /cx/bbu related help, illustrating various ways to use the /cx/bbu command. See the section “BBU Object Commands” on page 74 for more information. help /ex This command provides specific enclosure /ex related help, illustrating various commands associated with the enclosure /ex. See the section “Enclosure Object Commands” on page 79 for more information.
