3ware amcc 9500s-12 manual
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:3ware amcc 9500s-12 manual.pdf
Size: 3743 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 3 May 2019, 17:43 PM
Rating: 4.6/5 from 561 votes.
Status: AVAILABLE
Last checked: 14 Minutes ago!
In order to read or download 3ware amcc 9500s-12 manual ebook, you need to create a FREE account.
eBook includes PDF, ePub and Kindle version
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
3ware amcc 9500s-12 manualWe have 2 3Ware 9500S-12 - Escalade RAID Controller manuals available for free PDF download: User Manual, Installation Manual. Supports the 9000 Series. PN 720-0117-01 March 2005. TrademarksDriver Installation Under Linux.65Appendix C. Warranty, Technical Support, and Service.112. Limited Warranty.Exclusions.State Law Provisions.Obtaining Warranty Protection.AMCC's Technical Support and Services for 3ware RAID Controllers. For more complete information about managing and using arrays connected to the 3ware RAID controller, see 3ware 9000 Series Serial ATA RAID Controller User Guide.Product Features. The 3ware 9000 Series Serial ATA family includes 9500S-4LP, 9500S-8, 9500S-12, 9500S-8MI, and 9500S-12MI. Features of the 3ware 9000 series controllers include. PCI slot that meets the Plug and Play and PC99 specifications. Note: For all 3ware 9000 series models, install the card in a 64-Windows 2000 (Professional, Server, Advanced Server) (SP3 or newer), Windows XP Professional (SP1 or newer), Windows Server 2003 (Standard, Enterprise), Windows XP x64 Edition, Windows Server 2003 x64 Edition.Insert the controller card into the computer. For details see one of the following:Be sure to follow the guidelines presented on attaching the drives to the controller.Excessive force can damage the board or your system. Be sure the board is aligned with its slot on the motherboard before installing. Do not flex the board excessively. Figure 1. 12-Port 3ware 9500S-12 Serial ATA RAID Controller. Figures 2 and 3 show 3ware Serial ATA RAID controllers with 8 ports (there are two versions of the 9500S-8 controller). The last two pins on J7 and J8 are unused. Figure 2. 8-Port 3ware 9500S-8 Serial ATA RAID Controller, Pchip v1.5 (BBU-compatible). Additional Details About the LED Status Connectors. Check with your chassis documentation before connecting. Table 1: LED Indicator Pin Positions.http://konditsioner-odincovo.ru/upload_picture/bosch-integra-ascenta-dishwasher-manual.xml
- Tags:
- 3ware amcc 9500s-12 manual, 3ware amcc 9500s-12 manual download, 3ware amcc 9500s-12 manual pdf, 3ware amcc 9500s-12 manual free, 3ware amcc 9500s-12 manual 2017.
Controller 9500S-4LP LED Header J3 Pin Pair a-anode-plus is on the bottomController 9500S-12 LED Header J7 Pin Pair::::: 0 1 2 3 NU J8::::: 4 5 6 7 NU J9::::: 8 9 10 on J7 and J8 are unused. Figure 3. 8-Port 3ware 9500S-8 Serial ATA RAID Controller, Pchip v1.4 (Non-BBU Compatible)Figure 4. 4-Port 3ware 9500S-4 Serial ATA RAID Controller. Find the PCI slot you want to use for the serial 3ware RAID controller. Figure 5. 12-Port 3ware 9500S-12MI Serial ATA RAID Controller. Models 9500S-12MI and 9500S-8MI, have multi-lane internal connectors, each of which can handle up to four drives. These controllers can be installed in an enclosure with a backplane. If you are using a standard enclosure, connect each of the individual SATA connectors to a drive.Remove the metal filler bracket for the slot. Close the case and reconnect the power cables.Incomplete, degraded, rebuilding, or initializing units cannot be converted. In addition, RAID 0, 10, and 5 units must use a standard 64 KB stripe size. Power down the system, disconnect the drives from the 8000 controller and remove the controller from the system. Install the 9000 controller and attach the drives to the 9000 board, as described earlier in this section.This section includes the following topics. Note: You must attach drives before you can configure RAID arrays. Used with RAID 1, 5, 10 and 50. Hot Swap. The process of exchanging a drive without havingThe following RAID levels and configurations are available for drives attached to a 3ware RAID controller. JBOD. A JBOD is an unconfigured disk attached to your 3ware. RAID controller. JBOD configuration is no longer supported in the 3ware 9000 series. AMCC recommends that you use SingleThe total array capacity is defined as follows. Table 3: Drive Capacity. RAID Level RAID 0 RAID 1 Capacity (number of drives) X (capacity of the smallest drive) capacity of the smallest driveFigure 7. 3ware BIOS ScreenFigure 8.http://sruby.srubystal.pl/user_upload/bosch-instruction-manual-pdf.xml Warning Message When you Start 3BMOtherwise, press any key to continue. Whether you press F8 or Esc to leave 3BM will not have an effect on those changes. For more information, see the 3ware 9000 Series Serial ATA RAID Controller User Guide.For more information, see the discussion of Deleting Units in 3ware 9000 Series Serial ATA RAID Controller User Guide.Figure 10. Asterisks Next to Selected DrivesFigure 11. Create Disk Array Display, RAID 0 Example. Figure 12. Create Disk Array Display, RAID 5 ExampleNote: You can enable or disable the write cache again later without affecting the Size and select the desired stripe size (16KB, 64KB, or 256KB).Figure 14. Stripe Sizes for a RAID 5. To confirm unit configurationThen continue on with the next section. (For details. Type Y to continue, delete any existing data on the drives, and create the unit.Depending on the RAID configuration you are creating, initialization of the unit may begin immediately. Figure 16. Hot Spare IndicatedYou must turn on the 2TB Auto-Carving policy before creating the unit. Units created with this Policy and press Enter.Zeroes are written to all unit members.Initialization of RAID 1, RAID 10, RAID 5 with 3 or 4 disks, RAID 50 with 6, 8, or 9 drives, and RAID 50 with 12 drives configured in 3ware 9000 Series Serial ATA RAID Controller User Guide. After the initial verification, subsequent verifies to a RAID 1 or 10 unit check for data consistency by comparing the data from device precedes the 3ware RAID controller in the boot sequence. Details for both situations are described in the next sections of this guide, under Windows Installation (see page 53), Linux Installation (see page 65), and FreeBSD Installation (see page 87).Windows 2003 64-bit for AMD Opteron is also supported. If you are installing Windows on a new unit or drive managed by the 3ware RAID controller, you must create a 3ware driver diskette. To create a driver disketteInstalling the 3ware Driver and Windows on a New Unit.http://www.drupalitalia.org/node/67926 If you want to install Windows on a new drive configuration managed by the 3ware RAID controller, follow the instructions in this section.When you start Windows after installing a 3ware RAID controller, Windows recognizes it as a Plug and Play device, and brings up the Found New Hardware Wizard. This wizard guides you through installing the 3ware drivers (see Figure 17).Figure 20. Completing Found New Hardware WizardTo install the 3ware driver under Windows XP or 2003Figure 24. Completing Found New Hardware WizardFor more information, see the 3ware 9000 Series Serial ATA RAID Controller User Guide and the 3ware Escalade 9000 Series Serial ATA RAID Controller CLI Guide.A drive or unit managed by the 3ware RAID controller may be configured to be your system's boot device. Obtaining 3ware Linux Drivers. Obtain the 3ware driver for Linux from one of these two sources:Compiled and tested drivers for Red. Hat and SuSE Linux are included on this CD.Warning: Be sure to use the correct driver for your. Materials RequiredRed Hat Linux installation CD-ROM and boot disk. (Not required if Red Hat Linux is already installed on another drive.)A confirmation window opens.You want to update the RAM disk You prefer to load the driver manually or from a script, instead of updating the RAM diskThese conventions are used for variable text for kernel strings and module names in the instructions For example: 2.4.18-14hugmem. Module Naming Conventions. For Redhat workstation on AMD Opteron and Intel EM64T, type. If prompted to overwrite, type y.If prompted to overwrite, type y. Note: Use the appropriate module name and kernel string, asType: modprobe 3w-9xxx. You can also incorporate the insmod command into a startup script.The file created is 3w-9xxx.hug To build Boot module (this is used when creating a driver for the 32-bit driver diskette), type:The file created is 3w-9xxx.botThe file created is 3w-9xxx.i32 6 Copy the module as follows: For 2.4 kernels, copy module to.http://cornerwebstudio.com/images/3ware-9690sa-8i-manual.pdf If Linux is already installed on another device, you may install the 3ware driver from the 3ware software CD-ROM. To create a driver disketteClick OK and continue with installation. Installing the 3ware Driver on a SuSE Linux System that Boots from a Different Device 1 2 Log in as root.FreeBSD 4.10 and later have 9.xxx driver support built in. No driver installation is required. If you are using FreeBSD 4.8 or 4.9, you will need to install the 3ware FreeBSD driver as described below. To install the driver as a moduleIf you do not insert it immediately, the floppy with the 3ware driver, twa.ko, into the floppyUse a screwdriver to remove the black end rail. It aligns and secures the 3ware RAID controller in the computer chassis but is not critical for operation. Important: The battery is a heat-sensitive component. The cooler the battery, the longer the battery lasts. If possible, place the controller with the BBU in a slot with good airflow, away from components that generate the most heat in the system, such as video cards.Figure 1. Points of connection on the BBU (bottom view)Figure 3. Points of connection on the half-height controller (top view). Note: If your 9000 series controller does not have the BBU receptacle, contact technical support for assistance.Full-height board: bracket unscrews from bottom side of board. Figure 4. Removing the screws from the PCI bracketCable management clips. Figure 5. Battery cable inserted through cable management clipsFigure 8. BBU attached to controllerYou can check the status of the battery, and run a battery test to determine if the battery needs to be replaced. For details, see 3ware 9000 Series Serial ATA RAID Controller User Guide.Figure 10. BBU installed on controllersCaution: There is a risk of explosion if the battery isTo obtain a replacement battery, contact AMCC. You can run the battery test from the BBU page of either 3BM or 3DM 2. For detailed instructions, see the 3ware 9000 Series Serial ATA RAID Controller User Guide.Microsoft Windows Hardware Quality Lab (WHQL). AMCC is committed to Microsoft Windows Hardware Quality Labs (WHQL) certification for all its products.Products or parts replaced under this provision shall become the property of AMCC. Software Warranty: AMCC will replace a defective mediaAMCC's Technical Support and Services for 3ware RAID Controllers. For specific answers to questions or to give feedback about the product, visit our Web site at and use our convenient e-mail form. This publication may be co pied or reproduced for reference purposes only. T o do so, simply enter the command and the arguments. RAID 1 is also known as a mirrored array. Mirroring is done on pairs of drives. Enclosure object commands provide information and perform ac tions related to a par ticular en clo s ure. The default is to display the most re cent message first. This command shows the Au to-Rebuild policy. The following table illustrates the supported an d applicable stripes on unit types and controller models. Stripe size units are in K (kiloby tes). For 16 disk s, the disks can be grouped into groups of 4 or 8 drives. Do you want to continue. In this case, the controller will not use the define d schedule timeslots. By default, exportjbod is off. If the JBOD export policy is off, CLI will not be able to create JBODs. One or many attributes can be requested. This command reports the storsave policy on the unit. One or more ports can be specified. For 15 disks, the disks can be grouped into grou ps of 3 or 5 drives. One or many attributes can be sp ecified. The test may take up to 24 hours to complete. The slot name is followed by its status. The fan name is followed by its status. All other purposes require the express written consent of AMCC, 215 Mof fett Park Drive, Sunnyvale, CA 94089. The 3ware logo, 3BM, S torSwitch, and R5 Fusion are all trademarks of AMCC. PowerPC and the PowerPC logo are tradema r ks of Internationa l Business Machines Corporation. All other trademarks herein are property of their respective owners. Disc laimer While every attempt is made to make this document as accurate as possible, AMCC assumes no responsibility for errors or omissions in this document, nor does AMCC make any commitment to update the information contained herein. There are often multiple ways to acc omplish the same configuration and maintenance tasks for your 3ware cont roller. T able 1: Sections in this CL I Guide Chapter Description 1. Introduction to 3 ware Command Line Interface Installation, features, concepts 2. CLI Syntax Reference Describes individual commands using the primary syntax Multiple 3ware RAID controllers can be managed using the CLI via a command line or script. It provides co ntroller, logical unit, drive, enclosure, and BBU (Battery Backup Unit) management. It can be used in both interactive and batch mode, providing higher level AP I (application programming interface) functionalities. Note: Some CLI commands are supported only for particular models of 3ware RAID controllers. Wherever possible, comman ds are labeled to indicate when they are supported for only a subset of cont rollers. Within the 90 00 series, some commands apply to only to models 9550SX, 9590SE, and 9650SE an d not to 9500S, and are so labeled. A few commands apply only to models 950 0S, and are labeled as such. Import ant! For all of the functions of the 3ware CLI to work properly, you must h ave the proper CLI, firmware, and driver versions installed.For a summary of what you can do using the CLI, see “Common T asks Mapped to CLI Commands” on pag e 19. For specific versions of Linux and FreeB SD that are supported for the 3ware CLI, see the Release Notes. T er minolog y This document uses th e following terminology: Logical Unit s. Usually shortened to “units.” These are block devices presented to the operating system. A logical unit can be a one-tier, two-tier, or three-tier arrangement. JBOD, Spare, an d Single logical units are examples of one-tier units. RAID 1 and RAID 5 are examples of two-tier units and as such will have sub-units. RAID 10 and RAID 50 are examples of three-tier units and as such will have sub-sub-units. Port. A controller has one or many ports (typically 4, 8, 12, 16). Each port can be attached to a single disk drive. On a controller such as th e 9590SE-4ME, with a multilane serial port connector, one connector supp orts four ports. For additional information about 3ware controller concepts and terminology, see the user guide that came with you r 3ware RAID controller or the user guide portions of the 3ware HTML Book shelf. Wa r ni n g! If you are using 3DM, as opposed to 3DM2, AMCC does not recommend installing both 3DM and CLI on the same system. Conf licts may occur. For example, if both are inst alled, alarm s will be cap tured only by 3DM. Y ou should u se either CLI or 3DM to manage your 3ware RAID controllers. This is not an issue for 3DM2. Be sure to copy the corre ct version for the version of th e operating system you are using. The CLI prompt is displayed in a DOS console window. Online manual pages are also availabl e in nroff and html formats. Be sure to copy the correct version for the version of th e operating system you are using. T o do so, simply enter the command and the arguments. Single commands can be useful when you want to perform a task such as redirecting the output of the command to a file. It also allows you to use the command line history to eliminate some typing.The file is a text file containing a list of CLI command s which you have entered in advance. Each command must be on a s eparate line. This exampl e sets up a 12-port controller with two units: one with the firs t 2 drives mirrored, and another with the remaining drives in a RAID 5 array. It then prints the configurations for verification.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 working with a 3w are RAID controller, “unit” is the term used to refer to an array of disks that is configured and managed through the 3ware software. If one drive fails, the data is preserved on the paired drive. Mirroring provides data pro tection through redundan cy. Parity works in combination with striping on RAID 5, RAID 6, and RAID 50. Parity informa tion is written to each of the striped drives, in rotation. This is useful when you need to exchange a defective drive in a redundant array. The di sks may be attached to different ports than they were originally attach ed to, without harm to the data. For definitions of other terms used throughout the documentation, see the “Glossary”. A vailable RAID Configur a tions RAID is a method of combining several hard drives into one unit. It of fers fault tolerance and higher throughp ut levels than a single hard drive or group of independent hard dr ives. RAID levels 0, 1, 10 and 5 are the m ost popular. AMCC's 3ware controllers support RAID 0, 1, 5, 6, 10, 50, JBOD and Single Disk. The information below provides a more in-depth ex plan ation of the different RAID levels. For how to configure RAID un its, see “Configuring a New Unit” on page 96. RAID 0 RAID 0 provides improved performance, but no fault t olerance. Since the data is striped across more than one di sk, RAID 0 disk arrays achie ve high transfer rates because they can read an d write data on more tha n one drive simultaneously. The stripe size is conf igurable during un it creation. RAID 0 requires a minimum o f two drives. When drives are configured in a striped disk array (see Figure ?), large files are distributed across the multiple disks using RAID 0 techniques. Striped disk arrays give excepti ona l performance, particularly for data intensive applications such as vide o editing, computer-ai ded design and geographical info rmation systems. RAID 0 arrays are not fault tolerant. The loss of any driv e resu lts in the loss of all the data in that array, and can even cause a system hang, depending on your operating system. RAID 0 arra ys are not recommended for high availability systems unless additional precautions are taken to prevent system hangs and data loss. Figure 1. RAID 0 Configuration Example RAID 1 is also known as a mirrored array. Mirrored disk arrays write the sam e data to two dif ferent drives using RAID 1 algorithms (see Figure ?). This gives your system fault tolerance by preserving the data on one drive if th e other drive fails. W ith T winS tor technology, read performance is twice the speed of a single drive during sequential read operatio n. The adaptive alg orithms in T winStor tech nology boost performance by distinguishing betw een random and sequential read requests. For the sequential requests generated when accessi ng large files, both drives are used, with the heads simultaneous ly reading alternating sec tions of the file. For the smaller random transactions, the data is read from a single optimal drive head. Figure 2. RAID 1 Configuration Example RAID 5 RAID 5 provides performance, fault tole rance, high capacity, and storage efficiency. It requires a minimum of three drives and combines striping data with parity (exclusive OR) to rest ore data in case of a drive failure. Performance and ef ficiency increas e as the number of drives in a unit increases. Parity information is distributed across all of the drives in a unit rather than being concentrated on a single disk (s ee Figure ?). This avoids throughput loss due to contention for the parity drive. RAID 5 is able to tolerate 1 drive failure in the unit. This also means that a RAID 6 unit may be in two dif ferent states at the same time. For example, one sub-unit can be degraded, while another may be rebuilding, or o ne sub-unit may be initializing, while another is verifying. RAID 6 requires a minimum of five drives. Performance and storage efficiency also increase as the number of drives increase. When drives are configured as a striped mirrored array, the disks are configured using both RAID 0 and RAID 1 techni ques, thus the name RAID 10 (see Figure ?). A mi nimum of four drives are required to use this technique. The first two drives are mirro red as a fault tolerant array using RAID 1. The third and fourth drives are mirrored as a second fault tolerant array using RAID 1. The two mirrored arrays are then grouped as a striped RAID 0 array using a two tier structure. Higher data transfer rates are achieved by leveraging T winStor and striping the arrays. In addition, RAID 10 array s offer a higher degree of fault tolerance than RAID 1 and RAID 5, since the array can sustain multiple drive fail ures without data loss. For example, in a twelve-drive RAID 10 array, up to six drives can fail (half of each mirrored pair) and the array will continue to function. Please note that if both halves of a mirrored pair in the RAID 10 array fail, then all of the data will be lost. RAID 50 requires a minimum of six drives. Several combinations are available with RAID 50. For example, on a 12-port controller, you can hav e a grouping of 3, 4, or 6 drives. A grouping of 3 means that the RAID 5 arrays used have 3 disks each; four of these 3-drive RAID 5 arrays are striped together to form th e 12-drive RAID 50 array. On a 16-port controller, you can have a gro uping of 4 or 8 drives. In addition, RAID 50 array s offer a higher degree of fault tolerance than RAID 1 and RAID 5, since the array can sustain multiple drive fail ures without data loss. For example, in a twelve-drive RAID 50 array, up to one drive in each RAID 5 set can fail a nd the array will continue to function. Please note that if two or more drives in a RAID 5 set fail, then all of the data will be lost. Like disks in other RAID configurations, single disk s contain 3ware Disk Control Block (DCB) information a nd are seen by the OS as available units. Single drives are not fault tolerant an d therefore not recommended for high availability systems unless additional precautions are taken to prevent system hangs and data los s. JBOD A JBOD (acronym for “Just a Bunch of Disks”) is an unconfigured disk attached to your 3ware RAID controlle r. JBOD configuration is no longer supported in the 3ware 90 00 series. AMCC recommends that you use Single Disk as a replacement for JBOD, to take advantage of a dvanced features such as caching, OCE, and RLM. JBOD units are not fault tolerant a nd therefore not recommended for high availability systems unless additional precautions are taken to prevent system hangs and data loss. Deter mining W hat RAID Le vel to Use Y our choice of which type of RAID un it (array) to create will depend on your needs. Y ou may wish to maximize speed of access, total amount of storage, or redundant protect ion of data. Each type of RAID unit of fers a different blen d of these characteristics. The following table provides a brief summary of RAID type characteristics. Y ou can create one or more units, depending on the number of drives you have installed. T able 2: RAID Configuration T ypes RAID T ype Description RAID 0 Provides performance, but n o fault tolerance. RAID 1 Provides fault tolera nce and a read speed advantage ov er non- RAID disks. RAID 5 This type of unit provides performance, fault tolerance, an d high storage efficiency. RAID 5 units can tolerate one drive failing before losing da t a. RAID 6 Provides very high fa ult tolerance with the ability to protect against two consecutive drive failures. Performance and efficiency increase with higher numbers of drives. RAID 10 A combination of striped and mirrored units for fault tolerance and high perfo rmance. RAID 50 A combination of RAID 5 and RAID 0. It provides high fa ult tolerance and performance. Single Disk Not a RAID type, bu t supported as a configuration. Provides for maximum disk capacity with no redundancy.This is because th e capacity of each drive is limited to the capacity of the sma llest drive in the unit.The capacity used for each drive is rounded down to the nearest GB for drives under 45 GB (45,000,000,000 byt es), and rounded down to the nearest 5 GB for drives over 45 GB. For example, a 44.3 GB drive will be rounded down to 44 GB, and a 123 GB drive will be rounded down to 120 GB. For more information, see the discussion of drive coercion under “Creating a Ho t Spare” on page 108. Support for Over 2 T erabytes W indows 2000, W indows XP (32-bit), Linux 2.4, and FreeBSD 4.x, do not currently recognize unit capacity in excess of 2 TB. If the combined capacity of the drives to be connected to a unit exceeds 2 T erabytes (TB), you can enable auto-carving wh en you configure your units. Auto-carving divides the available unit capaci ty into multiple chunks of 2 TB or smaller that can be addressed by the operating systems as separate volumes. The carve size is adjustable from 1024 MB to 2048 MB (defaul t) prior to unit creation. If a unit over 2 TB was created prior to enabling the auto-carve option, its capacity visible to the operating syst em will still be 2TB; no additional capacity will be registered. T o change this, the unit has to be recreated. For more information, see “Using Auto-Carving for Multi LUN Support” on page 91. RAID 50 (number of drives - number of groups of drives) X (capacity of the smallest drive) T able 4: Drive Cap acity RAID Level Capacity Throughout this chapter the examples reflect the interactive method of executing 3ware CLI. Common T asks Mapped to CLI Commands The table below lists many of the task s pe ople use to manage their RAID controllers and units, and lists the primary CLI command associated with those tasks.Commands can either select (show, get, present, read) attributes or alter (add, change, set, write) attributes.Information abou t commands is organized by t he object on which the commands act: Shell Object Commands. Shell object commands se t the focus or provide information (such as alarms, d iagnostic s, rebuild schedules, and so forth) about all controllers in the system. For details, see “ Shell Object Commands” on page 23. Controller Object Commands. Controller object commands prov ide information and perform acti ons related to a specific controller. For example, you use controller object co mmands for such tasks as seeing alarms specific to a controller, creating schedules during which b ackground tasks are run, and setting policies for the controller. For details, see “Controller Object Commands” on page 29. Unit Object Commands. Unit object commands pr ovide information and perform actions related to a specific unit on a specific controller. For example, you use unit object commands for such tasks as seeing the rebuild, verify, or initialize status of a unit, starting, stopping, and resuming verifies, starting and stopping rebuilds, and setting policies for the unit. For details, see “Unit Object Commands” on page 59. 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 “P ort Object Comm ands” on page 77. BBU Object Commands. BBU object commands pr ovide information and perform actions related to a Battery Ba ckup Unit on a speci fic controller. For details, see “BBU Object Comma n ds” on page 82. Enclosure object commands provide information and perform ac tions related to a par ticular en closure. For example, you can use enclos ure object c ommands to see information about an enclosure and its elements (slots, fan, and temp erature sensor elements). Help Commands. Help commands allow you to display help information for all commands and attributes. For de tails, see “Help Commands” on page 91. Shell Object Commands Shell object commands are either app licable to all the controllers in the system (such as show, re scan, flush, comm it), or redirect the focused object. The focus command will set the specifie d object in focus and change the prompt to reflect this. This allows you to enter a command that applies to the focus, instead of having to type the entire object name each time. The concept is similar to being in a particular location in a file system and requesting a listing of the current directory.The intention is to provide a global view of th e environment. Not Optimal refers to any state except OK and VERIFYING. Other states include VERIFY -P AUSED, INITIALIZING, INIT - P AUSED, REBUILDING, REBUILD -P AUSED, DEGRADED, MIGRA TING, MIGRA TE-P AUSED, RECOVER Y, INOPERABLE, and UNKNOWN. RRate also applies to initia lizing, migrating, and recovery See the Release Notes for details. The reverse attribute displays the most recent message last.The rebuild rate is also applicable for initializing, migrating, and recovery background tasks.The Port summary section lists all present ports and specifies the port number, disk status, unit affiliation, size (in gigabytes) and blocks (512 bytes), and the serial number assigned by the disk vendor. The BBU summary lists details about the BBU, if one is installed. This feature provides a dia gnostic 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.