LSI KnowledgeBase

Home Search Tags Glossary

Welcome Guest ( Login | Register )

Latest Additions Most Popular

Home » Knowledgebase » LSI Topics » Product » Internal RAID Product » 3ware » SATA/SAS Products » 3DM & CLI » 16389, LSI 3ware CLI commands

16389, LSI 3ware CLI commands

16389, LSI 3ware CLI commands

The CLI commands are documented in the CLI GUIDE

CLI Guide PDF

Additional commands not in the CLI GUIDE (note: not all commands are supported with all 3ware RAID controllers):

Ignore FUA Write Policy

      It displays the controller policy of Ignore FUA writes from host.


            To check the "Ignore FUA Write" policy, use command [tw_cli /cx show ignorefuawrite].
            To set the "Ignore FUA Write" policy, use command [tw_cli /cx set ignorefuawrite=on|off].

Force Drive Cache On Policy

      It displays the controller policy of force drive cache on.

            To check the "Disable Force Drive Cache On" policy, use command [tw_cli /cx show forcedrivecacheon].
            To set the "Disable Force Drive Cache On" policy, use command [tw_cli /cx set forcedrivecacheon=on|off].

Controller Bus Mode

      It displays the RAID controller host bus information.

      To display the "Controller Host Bus Information", use command [tw_cli /cx show ctlbus].

            For example:

//localhost > /c1 show ctlbus
/c1 Controller Bus Type = PCIX
/c1 Controller Bus Width = 64 bits
/c1 Controller Bus Speed = 133 Mhz

LBA Reordering

      Enable or disable LBA Reordering on specified controller.

            To display the LBA Reordering state of the controller, use command [tw_cli /cx show LBAreorder].

            For example:
          //localhost > /c1 show LBAreorder
      //localhost > /c1 LBA Reordering state = off

            To enable LBA Reordering, use command [tw_cli /cx set LBAreorder=on].

            For example:
      //localhost > /c1 set LBAreorder=on
      Setting LBA Reordering on /c1 to [on] ... Done.

        To disable LBA Reordering, use command [tw_cli /cx set LBAreorder=off].

            For example:
      //localhost > /c1 set LBAreorder=off
      Setting LBA Reordering on /c1 to [off] ... Done.

AV Mode

      AV Mode provides faster I/O response time for audio and video applications.

            To display the current state of AV Mode, please use the command [tw_cli /cx show avmode]
            For example:
        //localhost > /c2 show avmode
         /c2 AV Mode Policy = off

            To set the AV Mode to ON, please use the command [tw_cli /cx set avmode=on]
            For example:
        //localhost > /c2 set avmode=on
         Enabling AV Mode Policy on /c2... Done.

            To set the AV Mode to OFF, please use the command [tw_cli /cx set avmode=off]
            For example:
             //localhost > /c2 set avmode=off
         Disabling AV Mode Policy on /c2... Done.

Write DPO

      The use of the write cache may be optimized by having the ability to read it at opportune times during I/O to and from the drives. Working in conjunction with other cache settings the write DPO (Disable Page Out) aids in performance gains related to data caching. The firmware default for writeDPO is "Honor". The user may change the settings with the commands as shown in this section.

      The three settings are ignore, force, and honor host. The following is a brief summary of the settings:

      -- Ignore : disregard the DPO bit in host write commands.
      -- Force : always behave as if DPO bit is set in host write commands.
      -- Honor : honor the write command setting of that of the host.

            To see the write DPO setting of the specified unit, use command [tw_cli /cx/ux show writedpo]
            For example:

         //localhost > /c1/u0 show writedpo
          /c1/u0 Write DPO policy setting = honor

            To configure the write DPO setting of the specified unit, use command [tw_cli /cx/ux set writedpo=ignore|force|honor]
            For example:

         //localhost > /c1/u0 set writedpo=ignore
          Setting Write DPO policy on /c1/u0 to [ignore] ... Done.

Mode Page Control

The Mode Page Control is a new persistent controller parameter that modifies the firmware behavior of host SCSI mode select commands. This parameter and the associated control were added to provide improved boot-time when the OS is installed on a RAID-5 array and the OS would disable the write cache on disk arrays when it updates the Active Directory database at boot time. The Mode page Control setting is used to set the parameter to one of two modes: ignore, or honor. Ignore refers to ignoring the mode select for resetting caching page WCE bit. The complement of this is honor.

To see the Mode Page Control setting of the specified controller, use command [tw_cli /cx show modepgctl].
            For example:

         //localhost > /c1 show modepgctl
          /c1 Mode Page Control setting = ignore

To configure the Mode Page Control setting of the specified controller, use command [tw_cli /cx set modepgctl=ignore|honor].

For example:

          //localhost > /c1 set modepgctl=honor
           Setting Mode Page Control on /c1 to [honor] ... Done.

            The mode page control, not considered as a "controller attribute" since this is a stealth command, would not be listed when the user issues a "/cx show all". In the event that the user wishes to go back to the default setting in case there is an error in the mode page control setting that was chosen, there are three ways that he could see the default:

            1) Do a query ("show") without or prior to setting the mode page control to any value.
            2) See documentation (Undocumented Commands file).
            3) User could input an invalid mode page control and see the output response:
            For example:

        //localhost > /cx set modepgctl=d#ffdc32sanytext
         Error:(CLI:151) Invalid mode page control input [valid: ignore|honor].

Drive Coercion Factor

Each controller has a drive coercion factor that is used during unit creation. The raw capacity of a drive is truncated based on the drive coercion factor. While firmware has been calculating the size of a drive with an implicit drive coercion factor, as drive capacity becomes larger, the equation that is used for truncation is not satisfactory for some customers, who wants to see the drive coercion factor increase for larger drives.

This feature allows the user to specify the drive coercion factor, regardless of the drive size. If no specified drive coercion factor has been made, then the default is used. The default is 1 for disk size of less than 45GB, and 5 for a disk of size greater than or equal to 45GB.

OPERATION

Ignore BBU Not Ready

The Ignore BBU Not Ready control allows an array to keep Write Cache ON and write Journaling enabled regardless of the state of the BBU. This is for applications that require the write cache to always be ON, for example, to prevent loss of video streams coming into the controller, as well as to maintain the data as best as possible in the case of an unclean shutdown. This setting may be used with StorSave being set to Balance or Perform.

To see the Ignore BBU Not Ready setting of the specified unit, use command [tw_cli /cx/ux show ignoreBBUnotready or /cx/ux show ignoreBBU]:

            //localhost > /c1/u0 show ignoreBBUnotready
             /c1/u0 Ignore BBU Not Ready setting = On

To configure the Ignore BBU Not Ready setting of a unit, use command [tw_cli /cx/ux set ignoreBBUnotready=on|off or tw_cli /cx/ux set ignoreBBU=on|off]:

            //localhost > /c1/u0 set ignoreBBU=off
             Setting Ignore BBU Not Ready of /c1/u0 to [off] ... Done.

If you wish to see the default setting, do a query ("show") without or prior to setting the Ignore BBU control to any value. For example:
            //localhost> /c1/u0 show ignoreBBU
         /c1/u0 Ignore BBU Not Ready setting = On

            The Ignore BBU Not Ready, not considered as a "unit attribute" since this is a stealth command, would not be listed when you issue a "/cx/ux show all". Also, as a stealth command, no online help or HTML Help would be available to you. In the event that you wish to know how to use the command correctly, input an invalid Ignore BBU value and see the output response:

            //localhost > /c1/u0 set ignoreBBU= d#f%fdc2anytext
         Error:(CLI:151) Invalid Ignore BBU Not Ready command [valid: on|off].

BBU High Current Test

The BBU High Current Test complements the currently available Capacity Test that may take up to 24 hours to complete and requires the data cache be disabled for the duration of the test. The High Current Test is shorter and takes much less time.

The following table summarizes the set of commands for the High Current Test (and for the Capacity Test) being added per this feature.

Function	Command Syntax
Specify either capacity or high current battery test to run	/cx/bbu start test=capacity\|highcurrent
Specify the capacity test to stop	/cx/bbu stop [test=capacity]
Request to see battery voltage values	/cx/bbu show voltage

Table 2.20.1. Summary of functions and commands.

OPERATION

Drive Power Save

Power Save is a power saving feature that spins down the drives in a unit after a period of inactivity. This timer that would count down before the drives in the unit are spun down is called the Power Save standby timer. After the drives of the unit are spun down, the Power Save status would be “standby”. Unless the drives have spun down, the Power Save status would be “active” (full power).

With the time value set accordingly, during period of inactivity, the timer will count down. If an I/O is received at a drive, the drives of the unit will resume full power until I/O or activity ceases, at which time the countdown would initiate again (see note 3 below).

There are several considerations to note regarding the usage of this feature.

1) This feature is for SATA and SAS drives and for the 9650SE/9690SA/9750 family of controllers only.
2) The drives of a unit that has been inactive with respect to the timer will spin down provided that no background task is running. If a background task (such as Rebuild, Verify, Initialization, and Self-Test) is running for the unit, the drive spin down will be delayed until the background task completes.
3) If any I/O command reaches a drive prior to the timer countdown completes, the I/O is serviced and the timer will reset and start from the beginning again.
4) If the unit in standby mode has a large number of active drives (max is 32), there is potential for the Linux SCSI timeout value to be exceeded during spinup of the drives, depending on the stagger and spinup settings. The user should be aware of this potential and minimize the stagger and spinup values and/or increase the respective operating system timeout as necessary.

Please note that the Power Save status currently has two states: active and standby. When all the drives of the unit have spun down, the Power Save status is Standby. Otherwise, the Power Save status is Active.

Also, the following are defaults for the Power Save function:
Status = Active
Standby timer = 0 minutes

To see the Power Save standby timer value of the specified unit, use command [tw_cli /cx/ux show PowerSaveStandbyTimer or tw_cli /cx/ux show powersavestandbytimer or tw_cli /cx/ux show PSstandbyTimer]:

Keywords:

hidden

Rate this Article:

Add Your Comments

Comment require login or registration.

Details

Last Modified:Wednesday, January 25, 2012
Last Modified By: Administrator
Type: FAQ
Rated 5 stars based on 1 vote
Article has been viewed 2,374 times.
Created:Tuesday, February 22, 2011

Options

Print Article
Bookmark Article

Bookmark Article
Export As PDF

Export As PDF