3ware 9500s user manual
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:3ware 9500s user manual.pdf
Size: 3924 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 28 May 2019, 22:16 PM
Rating: 4.6/5 from 819 votes.
Status: AVAILABLE
Last checked: 2 Minutes ago!
In order to read or download 3ware 9500s user 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 9500s user manualAll rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form by any means, electronic, mechanical, photocopying, recording or otherwise, without the proper written consent of 3ware, Inc., 455 West Maude Ave., Sunnyvale, CA 94085. When it is running, you can use your browser to view status and perform administrative tasks locally or remotely. You can also download the current version from the website at 3DM must be installed on the system in which the controller is installed. 3DM does not have to be installed on remote systems in order to remotely manage a 3ware controller. You may enter multiple e-mail addresses, separating each entry with a comma (,). 3ware 9000 Series Serial ATA RAID Controller User Guide. To do so, click View Certificate and then click Install Certificate. Figure 12. Security Alert dialog box When the first 3DM screen appears in your browser, log in as Administrator and use the default password, 3ware www.3ware.com. To start the installation Insert the 3ware software installation CD-ROM for Linux into the CD- ROM drive.It is a good idea to leave 3DM running on the system that contains your 3ware RAID controller. That way email alerts can be sent by 3DM, and administrators can manage the controller remotely, if remote administration is enabled. You do not need to install the 3DM software on the remote computer. As you work in 3DM, the Messages area just below the menu bar displays information about the results of commands you have selected. Help lets you access information about using 3DM, and provides access to an electronic copy of this User Guide. 3ware 9000 Series Serial ATA RAID Controller User Guide. Table 5: List of 3DM Pages 3DM Page Description Controller Summary Provides basic information about each 3ware RAID Page controller in your system. To see this page, click Summary in the menu bar. Controller Details. These passwords work independently of each other.http://www.stumet.eu/pliki/bosch-induction-cooktop-pie645q14e-manual.xml
- Tags:
- 3ware 9500s user manual.
The default password for both the User and Administrator is “3ware”. Passwords are case sensitive. You can only change passwords if you are logged in as Administrator. If you change the Administrator password, you will be automatically logged out, and must log back in with the new password. That way you can be assured that the information you see in 3DM is current. If two different versions of 3DM are both running, they have Note: to be listening on different ports. In addition, alarms cannot be captured by both versions. 3ware 9000 Series Serial ATA RAID Controller User Guide. Controller Summary Page The software version shown in the screenshots in this Note: manual are preliminary examples only. For the current released and tested version number, refer to the 9000 release notes. www.3ware.com. The Summary page provides basic information about each 3ware RAID controller in your system. To see details about the units in a controller, click the link in the ID column. Provides access to the firmware’s error log. When you click this Error Log.For details about each of the RAID levels, see “Understanding RAID Concepts and Levels” on page 8. The logical capacity (size) of the unit. Capacity. 3ware 9000 Series Serial ATA RAID Controller User Guide. For multiple drive units, the port numbers are shown in the subunits section. The port number is a link to the Drive Information page. 3ware 9000 Series Serial ATA RAID Controller User Guide. Consult your disk drive manufacturer for information on how to interpret the SMART data. The SMART data meaning varies by disk drive manufacturer and model. 3ware 9000 Series Serial ATA RAID Controller User Guide. You can see if this setting is enabled in the Other Controller Settings field at the bottom of this Controller Settings page. Indicates whether write cache will Disable Write Cache on Unit Degrade.After the unit is rebuilt, the write cache will be re-enabled automatically. www.3ware.com.http://www.odocamilloturrini.it/UserFilesFCK/bosch-induction-cooktop-user-manual.xml The Scheduling page is not available for 7000- and 8000- series controllers. If you want to schedule tasks for one of those controllers, use 3DM Version 1.x. 3ware 9000 Series Serial ATA RAID Controller User Guide. If none of the tasks are checked, self-tests will never run, even if you have scheduled time slots set. www.3ware.com. Moreover, if anything unusual is found during any self-test, it will be logged as an Alarm. 3ware 9000 Series Serial ATA RAID Controller User Guide. Always use the Remove link to remove a drive before unplugging it. www.3ware.com. If those drives were previously part of a 3ware RAID configuration and they still have valid DCB (Disk Configuration Block) information on them, the controller tries to piece them back together into a working unit. If a working unit can be formed, it will appear in the Unit Maintenance list when the scan is complete, and the operating system will be notified of the unit. Removes a selected unit and allows you to unplug the drives Remove Unit.The drives appear in the list of Available Drives. www.3ware.com. A window like the one in Figure 24 shows the drives you selected, and lets you specify configuration settings. 3ware 9000 Series Serial ATA RAID Controller User Guide. The default stripe size of 64KB will give the best performance with applications that have many sequential reads and writes. A larger stripe size will give better performance with applications that have a lot of random reads www.3ware.com. Alarms Page Figure 26. Alarms Page The Alarms page appears when you click Alarms on the menu bar. 3ware 9000 Series Serial ATA RAID Controller User Guide. The time shown for alarms generated by 9000-series controllers is the time received by the driver from firmware. The specific text relating to the alarm condition. Message. www.3ware.com. This field determines whether e-mail notification is Enabled or Send E-mail. Disabled. 3ware 9000 Series Serial ATA RAID Controller User Guide.http://www.drupalitalia.org/node/67887 When 3DM is first installed, the default password for both is 3ware Select the access level for which you are setting the Change Password For. Failure to do so will cause 3DM to stop responding and you will have to restart it by hand. Saves a new port number. Change Port button. 3ware 9000 Series Serial ATA RAID Controller User Guide. This publication may be co pied or reproduced for reference purposes only. 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.http://dkc1burgas.com/images/3ware-9500-manual.pdf 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. Mirroring is done on pairs of drives. 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. Rescanning th e controller will clear the drive error status if the condition no longer exists. Additional attributes about controllers, units, ports and disks can be obtained by querying for them explicitly. For de tails, see the other show subcommands. One or many attr ibutes can be specified. Specifying an invalid attribute will terminat e the loop.On 9500S and earlier controllers, ph ysically-removed disk(s) will still be counted.This command reports the controller ho st bus type, bus speed, and bus width. This command reports the current JBOD Export Policy: on, off, or Not Supported.This command reports the time delay between each group of spinups at the power on. 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. This command reports the Auto-C arve policy. If the policy is on, all newly created or migrated units larger than the carvesize will be automatically carved into multiples of carvesize volu mes plus one remainder volume. Each volume can be treated as an individual drive with its own file system. The default carvesize is 2TB.If you use a 32-bit operating system, it is recommended that you keep the policy on unless you know that your operatin g system supports disks that are larger than 2 TB. When the au tocar ve policy is off, all newly created units will consist of one single volume. This command shows the maxi mum size of the volumes that will be created if the autocarve policy is set to on. The carvesize can be s et between 1024 G B and 2048 GB. Default carvesize is 2048 GB (2 TB). The other 16 MB is reserved fo r use by the controller. If the policy is enabled, the firmware will select drives to use for rebuilding a degraded unit using the following priority order. If the policy is disabled, only spare drives will be used for an automatic rebuild operation. Rescanning th e controller will clear the drive error status if the condition no longer exists. Possible unit types include raid0, raid1, raid5, raid 6 (9650SE on ly), raid10, raid50, single, spare, and JBOD. In addition, users can assign the unit a name. The following table shows supported types and controller models. One or more ports can be speci fied. Multiple ports can be specified using a colon (:) or a da sh (-) as port index separators. A dash indicates a range and can be mixed with colo ns. Note: The unit’s serial number cannot be changed.Stripe size units are in K (kiloby tes). If no stripe size is specified, 64K is used by default, if applicable. If you need to change the stripe size after the unit is created, yo u can do so my migrating the unit. At the bottom-mo st layer, N number of disks per group are used to form the RAID 5 layer. Th ese RAID 5 arra ys are then integrated into a RAID 0. This attribute allows y ou to specify the number of disks in the RAID 5 level. V alid values are 3, 4, 5, 6, 7, and 8. Note that a sufficient number of disks are required for a given pattern or disk group. For example, given 6 disks, specifying 3 will create two RAID 5 arrays. W ith 12 disks, specifying 3 will create four RAID 5 arrays under the RAID 0 level. With only 6 disks a grouping of 6 is not allowed, as you wo uld basically be creating a RAID 5. The default RAID 50 g rouping varies, based on number o f disks. For 6 and 9 disks, default grouping is 3. For 8 disks, the default grouping i s 4. For 10 disks, the default grouping is 5, and fo r 12 disks, the disks can be grouped into groups of 3, 4, or 6 dri ves (the group of 4 drives is set by default as it pr ovides the best of net capacity and performan ce).For 16 disk s, the disks can be grouped into groups of 4 or 8 drives.By default CLI will inform the operating system.Enabling write cache increases write performance at the cost of potential data loss in case of sudden power loss (unless a BBU or UPS is installed). By default the cache is enable d. T o avoid the possibility of data loss in the event of a sudden power loss, it is recommended not to set nocac he unless there is a BBU (battery backup unit) or UPS (uninterru ptible power supply) installed.On model 900 0, the JBOD autoverify attribute is not pe rsistent (does not survive reboots).The default is for th e qpolicy to be on (in other words, noqpolicy is not specified). For a spar e unit, specifying noqpolicy has n o effect and the default remains. If the spare unit becomes a true unit, it would adopt the qpolicy of the “new” unit. For JBOD, the qpolicy cannot be set during unit creation, and specify ing noqpolicy returns an error. The follo wing table illustrates the supported Model-Unit T ypes. This table only ap plies to setting this feature at unit creation time. IgnoreECC only applies to redundant units.This feature is only for 9550SX, 9590SE, an d 9650SE controllers. The controller will update its list of ports (attached disks), and attempts to read every DCB (Disk Configuratio n Block) in order to re-assemble its view and awareness of logical units. A ny newly found unit(s) or drive(s) will be listed.The default is to inform the operating system.This command allows the downloading of the specified firmware image to the corresponding controller.