3ware HTML Bookshelf



3ware® CLI Guide > CLI Syntax Reference > Controller Object Commands > /cx show attribute [attribute ...]

/cx show attribute [attribute ...]
This command shows the current setting of the specified attributes on the specified controller. One or many attributes can be specified. Specifying an invalid attribute will terminate the loop. Possible attributes are: achip, allunitstatus, autocarve (9000 series SX/SE/SA only), autorebuild (9000 series SX/SE/SA only), bios, carvesize (9000 series SX/SE/SA only), driver, drivestatus, firmware, memory, model, monitor, numdrives, numports, numunits, ctlbus (9000 series SX/SE/SA only), ondegrade (9500S), pcb, pchip, qpolicy, serial, spinup (9000 series), stagger (9000 series), and unitstatus.
Example: To see the driver and firmware installed on controller 0, enter the following:
//localhost> /c0 show driver firmware
/c0 Driver Version = 2.x
/c0 Firmware Version = FE9X 3.x
(In the sample output above, “x” will be replaced with the actual version number.)
/cx show achip
This command reports the ACHIP (ATA Interface Chip) version of the specified controller /cx.
Example:
 //localhost> /c0 show achip
 /c0 ACHIP Version = 3.x
/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.
Example:
 //localhost> /c0 show allunitstatus
 /c0 Total Optimal Units = 2
 /c0 Not Optimal Units = 0
/cx show autocarve
This feature only applies to 9000 series SX/SE/SA controllers.
This command reports the Auto-Carve policy. If the policy is on, all newly created or migrated units larger than the carvesize will be automatically carved into multiples of carvesize volumes plus one remainder volume. Each volume can be treated as an individual drive with its own file system. The default carvesize is 2TB. For more information see, /cx show memory, below.
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.
Example:
 //localhost> /c0 show autocarve
 /c0 Auto-Carving Policy = on
/cx show autorebuild
This feature only applies to 9000 series SX/SE/SA 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.
1. Smallest usable spare.
2. Smallest usable unconfigured (available) drive.
3. Smallest usable failed drive.
If the policy is disabled, only spare drives will be used for an automatic rebuild operation.
Example:
//localhost> /c0 show autorebuild
/c0 Auto-Rebuild Policy = on
/cx show bios
This command reports the BIOS version of controller /cx.
Example:
 //localhost> /c0 show bios
 /c0 BIOS Version = BG9X 2.x
/cx show carvesize
This feature only applies to 9000 series SX/SE/SA model controllers.
This command shows the maximum size of the volumes that will be created if the autocarve policy is set to on. The carvesize can be set between 1024 GB and 32768 GB (1 TB to 32 TB). Default carvesize is 2048 GB (2 TB). For more information see, /cx show autocarve above.
Example:
 //localhost> /c0 show carvesize
 /c0 Auto-Carving Size = 2000 GB
/cx show ctlbus
This feature only applies to 9000 series SX/SE/SA model controllers.
This command reports the controller host bus type, bus speed, and bus width.
Example for 9690SA:
 //localhost> /c2 show ctlbus
 /c2 Controller Bus Type = PCIe
 /c2 Controller Bus Width = 8 lanes
 /c2 Controller Bus Speed = 2.5 Gbps/lane
/cx show driver
This command reports the device driver version associated with controller
/cx.
Example:
 //localhost> /c0 show driver
 /c0 Driver Version = 3.x
/cx show dpmstat [type=inst|ra|ext]
This feature only applies to 9000 series SX/SE/SA model controller. The type=ext feature is only for SE/SA controllers.
This 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 will be displayed. The available options are: inst for Instantaneous, ra for Running Average, and ext for Extended Drive Statistics. If you do not specify a type, the display will show the default set of drive statistics, which is the type inst.
inst (Instantaneous). This measurement provides a short duration average.
ra (Running Average). Running average is a measure of long-term averages that smooth out the data, and results in older results fading from the average over time.
ext (Extended Drive Statistics). The extended drive statistics refers to statistics of a drive's read commands, write commands, write commands with FUA (Force Unit Access), flush commands, and a drive sectors's read, write, and write commands with FUA.
Additional statistics are available for drives at specific ports. For details, see /cx/px show dpmstat type=inst|ra|lct|histdata|ext.
Drive Performance Monitoring can be turned on and off using the command /cx set dpmstat=on|off.
Example of inst drive statistics:
To display a summary of instantaneous data for the set of drives attached to the controller, use command /cx show dpmstat. (since inst is the default, you do not have to explicitly enter it in the command).
Since this is a controller-level command, the output provides summary information for the set of drives attached to the controller. For statistics about a drive attached to a specific port, see /cx/px show dpmstat type=inst|ra|lct|histdata|ext.
In the configuration information displayed below, the Performance Monitor is shown to be On, “Version” refers to the firmware version of the Performance Monitor, “Max commands for averaging” refers to the maximum number of commands that can be saved and used for calculating the average, and “Max latency commands to save” refers to the maximum number of commands with high latency that are saved. The amount of statistics data in the buffer is determined by these configurations and the memory constraints of the system. These configuration settings cannot be changed.
 
//localhost> /c0 show dmpstat
 Drive Performance Monitor Configuration for /c0 ... 
 Performance Monitor: ON 
 Version: 1 
 Max commands for averaging: 100 
 Max latency commands to save: 10 
 Requested data: Instantaneous Drive Statistics
 
                            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 display a summary of the running average data for the set of drives attached to the controller, use command /cx show dpmstat type=ra.
Notice that in this case, the Performance Monitor is turned off.
 //localhost> /c0 show dpmstat type=ra 
 
 Drive Performance Monitor Configuration for /c0 ... 
 Performance Monitor: OFF 
 Version: 1
 Max commands for averaging: 100
 Max latency commands to save: 10
 Requested data: Running Average Drive Statistics
 
                                Queue           Xfer         Resp
 Port   Status           Unit   Depth   IOPs    Rate(MB/s)   Time(ms)
 ------------------------------------------------------------------------
 p0     NOT-PRESENT      -      -       -       -            -
 p1     NOT-PRESENT      -      -       -       -            -
 p2     OK               -      -       -       -            -
 p3     OK               u0     0       435     25.249       2
 p4     OK               u1     0       366     21.630       3
 p5     OK               -      -       -       -            -
 p6     NOT-PRESENT      -      -       -       -            -
 p7     NOT-PRESENT      -      -       -       -            -
 
Example of extended drive statistics (ext):
To display a summary of the extended drive statistics associated with the specified controller, use command /cx show dpmstat type=ext.
 //localhost> /c3 show dpmstat type=ext
 Extended Drive Statistics for /c3 ...
 
                   Sectors                            Commands
 -----------------------------  ---------------------------------------
 Port   Read      Write     Write-FUA  Read      Write     Write-FUA  Flush
 ------------------------------------------------------------------------
 p0     28704384  0         28704384   28704448  0         0          0
 p2     28704384  28704448  0          0         0         0          0
 p3     28704704  0         0          0         0         0          0
 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 this occurs, you may want to zero out the counters by using the clear command, /cx/px set dpmstat=clear [type=ra|lct|ext].
Example of drive statistics overflow:
 
//localhost> /c3 show dpmstat type=ext
 Extended Drive Statistics for /c3 ...
 
                   Sectors                            Commands
 -----------------------------  --------------------------------------
 Port   Read     Write     Write-FUA  Read     Write     Write-FUA  Flush
 -----------------------------------------------------------------------
 p0    ########  0         158838656  158838720 0         0          0
 p2     ########  ########  ########   ########  ########  ########   ########
 p3    ########  0         0          0         0         0          0
 p6    0         0         0          0         0         0          0
 
/cx show drivestatus
This command reports a list of drives and their port assignment, status, the unit with which they are associated, their size in gigabytes and blocks, and the serial number assigned by the drive manufacturer. (Definitions of the drive statuses are available under Unit Statuses in the 3ware SAS/SATA RAID Software User Guide, Version 9.5.1.)
Example for 9650SE and earlier controllers:
 //localhost> /c0 show drivestatus
 
 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.05 GB   312581808     3JS0VG85
 p3     OK               u1     149.05 GB   312581808     3JS0VGCY
 p4     OK               u1     149.05 GB   312581808     3JS0VGGQ
 p5     OK               u2     149.05 GB   312581808     3JS0VH1P
 p6     OK               -      149.05 GB   312581808     3JS0TF0P
 p7     OK               -      149.05 GB   312581808     3JS0VF43
 p8     OK               -      149.05 GB   312581808     3JS0VG8D
 p9     NOT-PRESENT      -      -           -             -
 p10    NOT-PRESENT      -      -           -             -
 p11    NOT-PRESENT      -      -           -             -
 
Example for 9690SA controller:
 //localhost> /c2 show drivestatus
VPort Status     Unit Size      Type  Phy Encl-Slot    Model
--------------------------------------------------------------------------
p0    OK         u0   34.25 GB  SAS   -   /c2/e0/slt0  MAXTOR ATLAS15K2_36 
p1    OK         u0   34.25 GB  SAS   -   /c2/e0/slt1  MAXTOR ATLAS15K2_36 
p2    OK         u0   34.25 GB  SAS   -   /c2/e0/slt2  MAXTOR ATLAS15K2_36 
p3    OK         u0   34.18 GB  SAS   -   /c2/e1/slt0  HITACHI HUS151436VL 
p4    OK         u0   34.18 GB  SAS   -   /c2/e1/slt1  HITACHI HUS151436VL 
p5    OK         u0   34.18 GB  SAS   -   /c2/e1/slt2  HITACHI HUS151436VL 
p6    OK         u0   34.25 GB  SAS   -   /c2/e0/slt3  MAXTOR ATLAS15K2_36 
p7    OK         u0   34.25 GB  SAS   -   /c2/e0/slt4  MAXTOR ATLAS15K2_36 
p8    OK         u0   34.25 GB  SAS   -   /c2/e0/slt5  MAXTOR ATLAS15K2_36 
p9    OK         u0   34.25 GB  SAS   -   /c2/e0/slt6  MAXTOR ATLAS15K2_36 
p10   OK         u0   34.18 GB  SAS   -   /c2/e1/slt3  HITACHI HUS151436VL 
p11   OK         u0   34.18 GB  SAS   -   /c2/e1/slt4  HITACHI HUS151436VL 
p12   OK         u0   34.18 GB  SAS   -   /c2/e1/slt5  HITACHI HUS151436VL 
p13   OK         u0   34.18 GB  SAS   -   /c2/e1/slt6  HITACHI HUS151436VL 
p14   OK         u0   34.25 GB  SAS   -   /c2/e0/slt7  MAXTOR ATLAS15K2_36 
p15   OK         u0   34.25 GB  SAS   -   /c2/e0/slt8  MAXTOR ATLAS15K2_36 
p16   OK         u0   34.25 GB  SAS   -   /c2/e0/slt9  MAXTOR ATLAS15K2_36 
p17   OK         u0   34.25 GB  SAS   -   /c2/e0/slt10 MAXTOR ATLAS15K2_36 
p18   OK         u0   34.18 GB  SAS   -   /c2/e1/slt7  HITACHI HUS151436VL 
p19   OK         u0   34.18 GB  SAS   -   /c2/e1/slt8  HITACHI HUS151436VL 
p20   OK         u0   34.18 GB  SAS   -   /c2/e1/slt9  HITACHI HUS151436VL 
p21   OK         u0   34.18 GB  SAS   -   /c2/e1/slt10 HITACHI HUS151436VL 
p22   OK         u0   34.25 GB  SAS   -   /c2/e0/slt11 MAXTOR ATLAS15K2_36 
p23   OK         u0   34.25 GB  SAS   -   /c2/e0/slt12 MAXTOR ATLAS15K2_36 
p24   OK         -    34.25 GB  SAS   -   /c2/e0/slt13 MAXTOR ATLAS15K2_36 
p25   OK         -    34.25 GB  SAS   -   /c2/e0/slt14 MAXTOR ATLAS15K2_36 
p26   OK         -    34.18 GB  SAS   -   /c2/e1/slt11 HITACHI HUS151436VL 
p27   OK         -    34.18 GB  SAS   -   /c2/e1/slt12 HITACHI HUS151436VL 
p28   OK         -    34.18 GB  SAS   -   /c2/e1/slt13 HITACHI HUS151436VL 
p29   OK         -    34.18 GB  SAS   -   /c2/e1/slt14 HITACHI HUS151436VL 
p30   OK         -    34.25 GB  SAS   -   /c2/e0/slt15 MAXTOR ATLAS15K2_36 
p31   OK         -    34.18 GB  SAS   -   /c2/e1/slt15 HITACHI HUS151436VL 
//cx show exportjbod
This feature only applies to 9000 series controllers.
This command reports the current JBOD Export Policy: on, off, or Not Supported.
Example:
 //localhost> /c0 show exportjbod
 /c0 JBOD Export Policy = Not Supported.
 //localhost> /c1 show exportjbod
 /c1 JBOD Export Policy = on
/cx show firmware
This command reports the firmware version of controller /cx.
Example:
 //localhost> /c0 show firmware
 /c0 Firmware Version = FE9X 3.03.06.X03
/cx show memory
This command reports the available memory on the controller.
 
Note: Some memory is reserved for use by the controller, so the amount of memory available will be less than the controller actually has installed. The 9690SA controller has 512MB of memory of which 448MB is available.
Example:
 //localhost> /c2 show memory
 /c2 Available Memory = 448MB
/cx show model
This command reports the controller model of controller /cx.
Example:
 //localhost> /c0 show model
 /c0 Model = 9690SA-8E
/cx show monitor
This command reports the monitor (firmware boot-loader) version of controller /cx.
Example:
 //localhost> /c0 show monitor
 /c0 Monitor Version = BLDR 2.x
cx show numdrives
This command reports the number of drives currently managed by the specified controller /cx. This report does not include (logically) removed or exported drives.
On 9500S and earlier controllers, physically-removed disk(s) will still be counted. For a workaround, see /cx/px show smart.
Example:
 //localhost> /c0 show numdrives
 /c0 Number of Drives = 5
/cx show numports
This command reports how many physical connections are made to the controller and the total number of physical ports possible for the controller.
Example for a 9650SE-16ML with no drives attached:
 //localhost> /c0 show numports
/c0 Number of Ports = 16
Example for 9690SA-8E with 8 dual-port SAS drives:
 //localhost> /c3 show numports
 /c3 Connections = 16 of 128
/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).
Example:
 //localhost> /c0 show numunits
 /c0 Number of Units = 1
/cx show ondegrade
This feature only applies to 9500S controllers.
This command reports the cache policy for degraded units. If the ondegrade policy is “Follow Unit Policy,” a unit cache policy stays the same when the unit becomes degraded. If the ondegrade policy is off, a unit cache policy will be forced to “off” when the unit becomes degraded.
Example:
 //localhost> /c0 show ondegrade
 /c0 Cache on Degraded Policy = Follow Unit Policy
/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.
Example:
 //localhost> /c0 show pchip
 /c0 PCHIP Version = 1.x
/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 spinup
This feature only applies to 9000 series controllers.
This command reports the number of concurrent SAS and SATA disks that will spin up when the system is powered on, after waiting for the number of seconds specified with the set stagger command. Spinup does not work with SAS or SATA disks attached to an expander.
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. Spinup does not work with SAS or SATA disks attached to an expander.
Example:
 //localhost> /c0 show stagger
 /c0 Spinup Stagger Time Policy (sec) = 2
/cx show unitstatus
This command presents a list of units currently managed by the specified controller /cx, and shows their types, capacity, status, and unit policies.
Possible statuses include: OK, VERIFYING, VERIFY-PAUSED, INITIALIZING, INIT-PAUSED, REBUILDING, REBUILD-PAUSED, DEGRADED, MIGRATING, MIGRATE-PAUSED, RECOVERY, INOPERABLE, and UNKNOWN. (Definitions of the unit statuses are available under Unit Statuses in the 3ware SAS/SATA RAID Software User Guide, Version 9.5.1.)
 
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 may not be a repeated error, and may be caused by an ECC error, SMART failure, or a device error. Rescanning the controller will clear the drive error status if the condition no longer exists.
Example:
 //localhost> /c2 show unitstatus
 
  Unit  UnitType  Status     %RCmpl  %V/I/M  Stripe  Size(GB)  Cache  AVrfy
  -------------------------------------------------------------------------
  u0    RAID-5    OK           -       -       64K     596.004   ON     OFF
  u1    RAID-0    OK           -       -       64K     298.002   ON     OFF
  u2    SPARE     OK           -       -       -       149.042   -      OFF
  u3    RAID-1    OK           -       -       -       149.001   ON     OFF

Copyright AMCC 2004-2008
To contact Support, log in at https://www.3ware.com

www.3ware.com
1-858-535-6517
1-800-840-6055