Configuring Arrays on HP Smart Array Controllers Reference Guide

Cnfiguring Arrays n HP Smart Array Cntrllers Reference Guide Abstract This dcument identifies, and prvides instructins fr, the array cnfiguratin tls available fr HP PrLiant cntrller and server prducts. This dcument is fr the persn wh installs, administers, and trubleshts servers and strage systems. HP assumes yu are qualified in the servicing f cmputer equipment and trained in recgnizing hazards in prducts with hazardus energy levels. Part Number: 433572-402 September 2013 Editin: 11

Cpyright 2006, 2013 Hewlett-Packard Develpment Cmpany, L.P. The infrmatin cntained herein is subject t change withut ntice. The nly warranties fr HP prducts and services are set frth in the express warranty statements accmpanying such prducts and services. Nthing herein shuld be cnstrued as cnstituting an additinal warranty. HP shall nt be liable fr technical r editrial errrs r missins cntained herein. Cnfidential cmputer sftware. Valid license frm HP required fr pssessin, use r cpying. Cnsistent with FAR 12.211 and 12.212, Cmmercial Cmputer Sftware, Cmputer Sftware Dcumentatin, and Technical Data fr Cmmercial Items are licensed t the U.S. Gvernment under vendr s standard cmmercial license. Micrsft, Windws, and Windws Server are U.S. registered trademarks f Micrsft Crpratin.

Cntents Overview f array cnfiguratin tls... 5 Utilities available fr cnfiguring an array... 5 Cmparisn f the utilities... 5 Supprt fr standard cnfiguratin tasks... 6 Supprt fr advanced cnfiguratin tasks... 6 HP Smart Array Advanced Pack... 8 Abut SAAP... 8 Required hardware... 8 Optin ROM Cnfiguratin fr Arrays... 9 Abut ORCA... 9 HP Array Cnfiguratin Utility... 10 Abut ACU... 10 Native supprt fr 64-bit and 32-bit perating systems... 10 Accessing ACU in the ffline envirnment... 10 Launching ACU with HP Intelligent Prvisining (Gen8 r later)... 11 Launching ACU during POST (Gen8 r later)... 11 Launching ACU frm the SmartStart CD (G7 r earlier)... 11 Launching ACU frm an ISO image (all generatins)... 11 Accessing ACU in the nline envirnment... 15 Launching ACU n a lcal server... 16 Launching ACU n a lcal server t cnfigure a remte server... 17 Launching ACU n a remte server t cnfigure a lcal server... 18 Using the ACU GUI... 19 Navigating the GUI... 19 Cnfiguratin tasks... 28 Diagnstics tasks... 39 Wizards... 41 Using the ACU CLI... 45 Opening the CLI in Cnsle mde... 46 Opening the CLI in Cmmand mde... 46 CLI syntax... 46 Typical prcedures... 51 Using ACU scripting... 68 Capturing a cnfiguratin... 68 Using an Input script... 68 Creating an ACU script file... 69 Script file ptins... 70 XML supprt... 84 ACU scripting warning messages... 87 ACU scripting errr messages... 87 HP Array Diagnstics and SmartSSD Wear Gauge Utility... 92 Abut the utility... 92 Reprted infrmatin... 92 Installing the utility... 94 Cntents 3

Setting up ADU Remte Service Mde... 95 Launching the utility in CLI mde... 95 Launching the utility in GUI mde... 95 Diagnstic reprt prcedures... 96 Viewing the diagnstic reprt... 96 Generating the diagnstic reprt... 98 Identifying and viewing diagnstic reprt files... 99 SmartSSD Wear Gauge reprt prcedures... 99 Viewing the SmartSSD Wear Gauge reprt... 99 Generating the SmartSSD Wear Gauge reprt... 100 Identifying and viewing SmartSSD Wear Gauge reprt files... 101 Drive arrays and fault-tlerance methds... 102 Drive arrays... 102 Effects f a hard drive failure n lgical drives... 104 Fault-tlerance methds... 105 RAID 0 N fault tlerance... 105 RAID 1 and RAID 1+0 (RAID 10)... 106 RAID 1 (ADM) and RAID 10 (ADM)... 107 RAID 5 distributed data guarding... 109 RAID 6 (ADG) Advanced Data Guarding... 109 RAID 50... 111 RAID 60... 112 Cmparing the hardware-based RAID methds... 112 Selecting a RAID methd... 113 Alternative fault-tlerance methds... 113 Diagnsing array prblems... 115 Diagnstic tls... 115 Trubleshting resurces... 115 Acrnyms and abbreviatins... 117 Dcumentatin feedback... 119 Index... 120 Cntents 4

Overview f array cnfiguratin tls Utilities available fr cnfiguring an array T cnfigure an array n an HP Smart Array cntrller, three utilities are available: HP Array Cnfiguratin Utility (ACU) An advanced utility that enables yu t perfrm many cmplex cnfiguratin tasks Optin ROM Cnfiguratin fr Arrays (ORCA) A simple utility used mainly t cnfigure the first lgical drive in a new server befre the perating system is laded HP Online Array Cnfiguratin Utility fr NetWare (CPQONLIN) A custmized versin f ACU fr nline cnfiguratin f servers that use Nvell NetWare Befre yu use a utility, cnfirm that the utility can supprt the required task. View a cmparisn f the utilities (n page 5). Whichever utility yu use, remember the fllwing factrs when yu build an array: All drives gruped in a lgical drive must be f the same type (fr example, either all SAS r all SATA and either all hard drives r all slid state drives). Fr the mst efficient use f drive space, all drives within an array shuld have apprximately the same capacity. Each cnfiguratin utility treats every physical drive in an array as if it has the same capacity as the smallest drive in the array. Any excess capacity f a particular drive cannt be used in the array and is unavailable fr data strage. The mre physical drives cnfigured in an array, the greater the prbability that the array will experience a drive failure during any given perid. T guard against the data lss that ccurs when a drive fails, cnfigure all lgical drives in an array with a suitable fault-tlerance (RAID) methd. Fr mre infrmatin, see "Drive arrays and fault-tlerance methds (n page 102)." Cmparisn f the utilities Feature ACU CPQONLIN ORCA Interface GUI, CLI, and Scripting Menu-based Menu-based r CLI Languages English, French, German, English English Italian, Japanese, Simplified Chinese, and Spanish Surce f executable file Sftware CD, web, r embedded in the system Sftware CD r web Preinstalled in ROM f HP Smart Array cntrllers When the utility can be used Where the utility can be used All frmats can be run in nline and ffline envirnments. Any machine that uses a supprted brwser Any time the perating system is running Only n the lcal server During POST, befre the perating system is installed Only n the lcal server Overview f array cnfiguratin tls 5

ORCA supprts nly basic cnfiguratin tasks, whereas CPQONLIN and ACU prvide full-range supprt fr standard cnfiguratin tasks (n page 6). ACU als prvides supprt fr advanced cnfiguratin tasks (n page 6). Sme f these advanced tasks are nt available in all ACU interface frmats (GUI, CLI, and Scripting). Supprt fr standard cnfiguratin tasks A "+" indicates the feature r task is supprted. A " " indicates the feature r task is nt supprted. Task ACU CPQONLIN ORCA* Create r delete arrays and lgical drives + + + Assign a RAID level t a lgical drive + + + Identify devices by causing their LEDs t illuminate + + Assign a spare drive t an array + + + Share a spare drive amng several arrays + + Assign multiple spare drives t an array + + Set the spare activatin mde + Specify the size f the lgical drive + + Create multiple lgical drives per array + + Set the stripe size + + Migrate the RAID level r stripe size + + Expand an array + + Set the expand pririty, migrate pririty, and acceleratr rati + + Extend a lgical drive + Set the bt cntrller + + Cnfigure HP SmartCache + *ORCA is nt supprted n the fllwing cntrllers: HP Smart Array P430/2G HP Smart Array P431/2G HP Smart Array P731m/2G Supprt fr advanced cnfiguratin tasks The fllwing table uses these symbls: + The ACU frmat supprts this task. The ACU frmat des nt supprt this task. +/ Supprt fr this task varies by cntrller. T supprt this task, sme cntrllers must have SAAP activated by a registered license key. T identify cntrller-specific feature supprt and SAAP requirements, see the cntrller user guide r the HP website (http://www.hp.cm/prducts/smartarray). Fr mre infrmatin, see "Abut SAAP (n page 8)." Prcedure ACU GUI ACU CLI ACU Scripting Activate r delete license keys + + + Cnfigure multiple systems identically + 1 + 1 + Cnfigure a RAID 6 lgical drive +/ +/ +/ Overview f array cnfiguratin tls 6

Prcedure ACU GUI ACU CLI ACU Scripting Cnfigure a RAID 60 lgical drive +/ +/ +/ Cpy the cnfiguratin f ne system t multiple systems 1 1 + Disable a redundant cntrller + 2 + Enable r disable a physical drive write cache + + + HP Drive Erase (replace the cntent f a physical drive r lgical +/ +/ drive with zers r randm 0 and 1) Identify devices by causing their LEDs t flash + + Mve an array (cpy all array data t a new array and then +/ 2 +/ +/ delete the ld array) Optimize the cntrller perfrmance fr vide +/ 2 +/ +/ Re-enable a failed lgical drive + + Set the surface scan delay + + + Set the preferred cntrller fr a lgical drive (in systems that + 2 + + supprt redundant cntrllers) Shrink an array (restripe the data n an array t ccupy fewer +/ 2 +/ +/ physical drives, then remve the excess drives frm the array) Split a RAID 1 array r recmbine a split array (ffline nly) +/ 1 Scripting is the mst efficient methd fr this task. 2 The task is supprted nly frm the Cnfiguratin screen. Overview f array cnfiguratin tls 7

HP Smart Array Advanced Pack Abut SAAP SAAP is a cllectin f additinal and advanced cntrller features embedded in the firmware f select Smart Array cntrllers. T access SAAP features, activate the sftware with a registered license key. SAAP 1.0 prvides the fllwing features fr HP Smart Array G6 and G7 cntrllers: RAID 6 (ADG) RAID 60 Advanced Capacity Expansin Mirrr splitting and recmbining in ffline mde Physical Drive Erase Perfrmance ptimizatin fr vide n demand Dual dmain T access SAAP features fr HP Smart Array G6 and G7 cntrllers, yu must purchase a license key frm HP. T btain a license key, see the SAAP prduct page n the HP website (http://www.hp.cm/g/saap). T install the license key and activate SAAP, use ne f the fllwing methds: Installing a license key with ACU (n page 33) Installing a license key with ACU CLI ("Entering r deleting a license key" n page 54) Installing a license key with ACU Scripting ("LicenseKey, DeleteLicenseKey" n page 74) Sme SAAP features are required fr advanced cnfiguratin tasks in ACU. Fr a list f these tasks, see "Supprt fr advanced cnfiguratin tasks (n page 6)." Required hardware Fr a list f Smart Array cntrllers that supprt SAAP, see the SAAP prduct page n the HP website (http://www.hp.cm/g/saap). T supprt sme cntrller features, the cntrller may als require a hardware cnfiguratin that includes the fllwing cache (array acceleratr) ptins: A cache mdule that is 256 MiB r larger A cmpatible battery pack r capacitr pack T btain these ptins, cntact an HP authrized reseller r see the HP website (http://www.hp.cm/prducts/smartarray). HP Smart Array Advanced Pack 8

Optin ROM Cnfiguratin fr Arrays Abut ORCA ORCA is a ROM-resident array cnfiguratin utility that executes autmatically during initializatin f an HP Smart Array cntrller. This utility is designed t enable a lgical drive t be cnfigured n a new HP server befre the perating system is installed: If the bt drive has nt been frmatted and the bt cntrller is cnnected t six r fewer physical drives, ORCA runs as part f the aut-cnfiguratin prcess when the new server is first pwered up. During this aut-cnfiguratin prcess, ORCA uses all f the physical drives n the cntrller t set up the first lgical drive. The RAID level used fr the lgical drive depends n the number f physical drives (ne drive = RAID 0; tw drives = RAID 1+0; three t six drives = RAID 5). If the drives have different capacities, ORCA lcates the smallest drive and uses the capacity f that drive t determine hw much space t use n each f the ther drives. If the bt drive has been frmatted r if there are mre than six drives cnnected t the cntrller, yu are prmpted t run ORCA manually. Fr mre infrmatin abut the aut-cnfiguratin prcess, see the HP ROM-Based Setup Utility User Guide n the Dcumentatin CD that is prvided with the server. ORCA is available in tw frmats: Using the ORCA menu-driven interface Using the ORCA CLI HP PrLiant 100 Series servers d nt supprt the CLI frmat. Fr these servers, use the menu-driven interface. Either frmat prvides a quick and easy methd fr basic lgical drive cnfiguratin. Bth frmats have limited supprt fr standard cnfiguratin tasks (n page 6). Hwever, these few tasks are adequate if yur cnfiguratin needs are simple. Fr example, stripe size is predetermined by the RAID level that yu chse, and the size f the lgical drive is determined autmatically by the size f the physical drives that yu select. Optin ROM Cnfiguratin fr Arrays 9

HP Array Cnfiguratin Utility Abut ACU ACU is the main tl fr cnfiguring arrays n HP Smart Array cntrllers. It exists in three interface frmats: the ACU GUI, the ACU CLI, and ACU Scripting. All frmats prvide supprt fr standard cnfiguratin tasks (n page 6). ACU als prvides supprt fr advanced cnfiguratin tasks (n page 6). Sme f the advanced tasks are available in nly ne frmat. The diagnstic features in ACU are als available in the standalne sftware HP Array Diagnstics and SmartSSD Wear Gauge Utility (n page 92). Starting with ACU versin 9.0 and PrLiant Gen8 servers and server blades, ACU is accessible bth ffline and nline: Accessing ACU in the ffline envirnment (n page 10) Using ne f multiple methds, yu can run ACU befre launching the hst perating system. In ffline mde, users can cnfigure r maintain detected and supprted PrLiant devices, such as ptinal Smart Array cntrllers, integrated Smart Array cntrllers, and RAID Array cntrllers. Sme ACU CLI features are nly available in the ffline envirnment, such as setting the bt cntrller and bt vlume. Accessing ACU in the nline envirnment (n page 15) This methd requires an administratr t dwnlad the ACU executables and install them. Yu can run ACU nline after launching the hst perating system. Native supprt fr 64-bit and 32-bit perating systems ACU nw ffers a native 64-bit ACU applicatin fr supprted 64-bit perating systems, eliminating the need fr cmpatibility libraries. A 32-bit ACU applicatin is als available. Users can chse t install the applicatin that matches the OS installed n the server prduct. The 64-bit ACU applicatin is nt a direct upgrade frm 32-bit ACU. On 64-bit systems running 32-bit ACU, yu must uninstall the 32-bit applicatin, and then install the 64-bit applicatin. Future versins f ACU will be available as native 32-bit r native 64-bit applicatins, as lng as 32-bit perating systems are supprted. Accessing ACU in the ffline envirnment T access and launch the ACU GUI in an ffline envirnment, use ne f the fllwing methds: Launching ACU with HP Intelligent Prvisining (Gen8 r later) (n page 11) Launching ACU during POST (Gen8 r later) (n page 11) HP Array Cnfiguratin Utility 10

Launching ACU frm the SmartStart CD (G7 r earlier) (n page 11) Launching ACU frm an ISO image (all generatins) (n page 11) T access the ACU CLI r ACU Scripting in an ffline envirnment, yu must launch ACU frm an ISO image. When ffline ACU launches, an Executin Mde screen des nt appear, because ACU des nt supprt Remte Service Mde in an ffline envirnment. Fr this functinality, use ACU in an nline envirnment ("Accessing ACU in the nline envirnment" n page 15). Launching ACU with HP Intelligent Prvisining (Gen8 r later) 1. Bt the server. 2. Press F10 t launch HP Intelligent Prvisining. 3. At the main screen, select Perfrm Maintenance. 4. At the Maintenance screen, select Array Cnfiguratin Utility (ACU). The system launches the ACU GUI. Launching ACU during POST (Gen8 r later) 1. Bt the server. During POST, the system recgnizes devices. 2. When the system recgnizes a Smart Array cntrller, press F5. The system launches the ACU GUI. Launching ACU frm the SmartStart CD (G7 r earlier) 1. Clse all applicatins. 2. Insert the SmartStart CD int the CD-ROM drive. 3. Restart the server. The server bts frm the CD, and then lads the SmartStart executable and drivers. 4. When prmpted, select the language and agree t the license restrictins. 5. Click Maintain Server. 6. Click Array Cnfiguratin Utility. ACU pens, scans the lcal server, and detects cntrllers. This prcess can last up t 2 minutes. When cntrller detectin is cmplete, the cntrllers are available n the Cntrller/Device menu. Launching ACU frm an ISO image (all generatins) T launch ACU, yu can als bt frm an ISO image. T prepare the image, use ne f the fllwing methds: Munting the image n a lcal drive (n page 12) Munting the image thrugh ilo (n page 12) Burning the image t a CD r DVD (n page 12) Flashing the image t a USB memry key r SD card (n page 12) HP Array Cnfiguratin Utility 11

Installing the image n a PXE server (n page 13) Bting frm the ISO image n a drive, n a key, r thrugh ilo prvides the same GUI interface. The user can select t run Offline ACU GUI, ACU CLI, r ACU Scripting. Munting the image n a lcal drive 1. Dwnlad the HP PrLiant Offline Array Cnfiguratin Utility ISO image frm the HP website (http://h20000.www2.hp.cm/bizsupprt/techsupprt/sftwaredescriptin.jsp?lang=en&cc=us &switem=mtx-aad98a00c0d6469d8abf78e2f3&mde=4&idx=1). 2. Using ISO munting sftware, munt the Offline ACU ISO image t a drive. 3. Set the server t bt the image. 4. Rebt the server. Munting the image thrugh ilo This ilo functinality requires an ilo Advanced license. 1. Dwnlad the HP PrLiant Offline Array Cnfiguratin Utility ISO image frm the HP website (http://h20000.www2.hp.cm/bizsupprt/techsupprt/sftwaredescriptin.jsp?lang=en&cc=us &switem=mtx-aad98a00c0d6469d8abf78e2f3&mde=4&idx=1). 2. Brwse t the server ilo page. 3. Start the remte cnsle fr the server. 4. On the remte cnsle, use the ilo munt feature t brwse t the lcatin f the ISO image. 5. Select the ISO image t be munted. 6. Rebt the server. Burning the image t a CD r DVD 1. Dwnlad the HP PrLiant Offline Array Cnfiguratin Utility ISO image frm the HP website (http://h20000.www2.hp.cm/bizsupprt/techsupprt/sftwaredescriptin.jsp?lang=en&cc=us &switem=mtx-aad98a00c0d6469d8abf78e2f3&mde=4&idx=1). 2. Use a third-party sftware t burn the ISO image t a CD r DVD. 3. Set the server t bt frm the ptical drive. 4. Insert the CD r DVD. 5. Rebt the server. Flashing the image t a USB memry key r SD card 1. Dwnlad the HP PrLiant Offline Array Cnfiguratin Utility ISO image frm the HP website (http://h20000.www2.hp.cm/bizsupprt/techsupprt/sftwaredescriptin.jsp?lang=en&cc=us &switem=mtx-aad98a00c0d6469d8abf78e2f3&mde=4&idx=1). 2. Dwnlad the HP USB Key Utility fr Windws frm the HP website (http://h20000.www2.hp.cm/bizsupprt/techsupprt/sftwaredescriptin.jsp?lang=en&cc=us &switem=mtx-eee9b3632ced47478f9ef85d43&mde=5). CAUTION: Befre creating a btable USB key frm the Offline ACU ISO image, back up any critical data stred n the key t a different lcatin. The utility verwrites all data n the key. HP Array Cnfiguratin Utility 12

3. Using ISO munting sftware, munt the Offline ACU ISO image t a Windws drive. Fr this example, use "E:." 4. Insert a USB key int a USB cnnectr n the Windws system. Fr this example, use "F:." 5. Run the HP USB Key Utility. 6. At the main screen, select Next. 7. If yu agree with the end user license agreement, select the Agree radi buttn, and then click Next. 8. Select Create a btable USB key frm CD/DVD, and then click Next. 9. At the requirements screen, click Next. 10. The Select CD/DVD drive: ptin is selected by default. 11. Frm the pull-dwn menu, select the drive letter fr the lcatin f the munted ISO image (E:). If the lcatin is nt shwn, press Rescan Surce, and then select the lcatin. 12. The USB Key Drive Letter field shws the drive letter fr the USB key (F:). If the drive letter is nt ppulated, select Rescan Target, and then select the drive letter. 13. Click Next. 14. At the fllwing screen, click Next. The USB key is verwritten with the Offline ACU ISO image. 15. Select Finish. Installing the image n a PXE server T install the Offline ACU ISO image n a PXE server and bt frm the image ver a netwrk, use the fllwing prcedures: 1. Review the prerequisites (n page 13). 2. Set up PXELinux (n page 14). 3. Cnfigure PXELinux (n page 14). 4. Specify the ISO image path (n page 14). Depending n the netwrk cnfiguratin, bt times might vary. Prerequisites Befre prceeding with the cnfiguratin, yu must have all the prerequisites: A gd, wrking knwledge f PXE and TFTP A netwrk with a DHCP server n it A TFTP server cnfigured n the same netwrk as the DHCP server A netwrk file server that hsts the ISO images and is accessible by a PXE bted system PXELinux (http://syslinux.zytr.cm/wiki/index.php/pxelinux) These instructins presume that yu are using a Linux TFTP server and the TFTP package (http://www.kernel.rg/pub/sftware/netwrk/tftp). Other TFTP servers shuld wrk similarly. HP Array Cnfiguratin Utility 13

Set up PXELinux Befre prceeding with the cnfiguratin, ensure that yur TFTP server and PXELinux cnfiguratin is set up and cnfigured prperly. T set up PXELinux: 1. Dwnlad the HP PrLiant Offline Array Cnfiguratin Utility ISO image frm the HP website (http://h20000.www2.hp.cm/bizsupprt/techsupprt/sftwaredescriptin.jsp?lang=en&cc=us &switem=mtx-aad98a00c0d6469d8abf78e2f3&mde=4&idx=1). 2. Cpy the ISO image t the netwrk file system, and nte the lcatin. NFS and Windws file shares are supprted. Fr this example, use the fllwing NFS and path t the ISO image: 192.168.0.99:/path/t/acucd/image/hpacuffline-8.75-12.0.is 3. Befre prceeding, test yur netwrk file system t ensure that it is accessible. 4. Access the /system directry f the CD in ne f the fllwing ways: Burn and munt the ISO image. Extract the ISO image using a third-party tl. 5. Cpy all the files frm the /system directry f the CD t yur TFTP server s that it is accessible by the TFTP sftware. Cnfigure PXELinux 1. Using the islinux.cfg file frm the /system/ directry f the CD as a guide, cpy the labeled targets t yur PXELinux cnfiguratin file. Yu d nt need t include the entire file: label ss MENU LABEL HP PrLiant Offline ACU Image kernel hpbt_v.c32 append vmlinuz initrd=initrd.img media=cdrm rw rt=/dev/ram0 ramdisk_size=257144 init=/bin/init lglevel=3 ide=ndma ide=nraid pnpbis=ff vga=791 splash=silent shwpts TYPE=AUTOMATIC label vss MENU LABEL HP PrLiant Offline ACU Image kernel hpbt_v.c32 append vmlinuz initrd=initrd.img media=cdrm rw rt=/dev/ram0 ramdisk_size=257144 init=/bin/init lglevel=3 ide=ndma ide=nraid pnpbis=ff vga=791 splash=silent shwpts TYPE=MANUAL 2. Replace the lines kernel hpbt_v.c32 with kernel vmlinuz. 3. Remve vmlinuz frm the append line. The paths t the files n the TFTP server are vmlinuz and initrd.img. Yu must mdify them t include any directries r naming cnventins yu may have n yur TFTP server. Specify the ISO image path Fr the PXE-bted server t find the ISO image, yu must add the ISO image path t the append line in the PXELinux cnfiguratin file. Add the fllwing arguments: is1=nfs://192.168.0.99/path/t/acucd/image/hpacuffline-8.75-12.0.is is1mnt=/mnt/btdevice HP Array Cnfiguratin Utility 14

The is1 parameter helps the PXE-bted ACU Offline CD lcate the ISO image. The is1mnt parameter tells the PXE-bted ACUCD where the is1 image must be munted. Yur final cnfiguratin must be similar t the fllwing example: label ss MENU LABEL HP PrLiant Offline ACU Image kernel vmlinuz append initrd=initrd.img media=cdrm rw rt=/dev/ram0 ramdisk_size=257144 init=/bin/init lglevel=3 ide=ndma ide=nraid pnpbis=ff vga=791 splash=silent shwpts TYPE=AUTOMATIC is1=nfs://192.168.0.99/path/t/acucd/image/hpacuffline-8.75-12.0.is is1mnt=/mnt/btdevice label vss MENU LABEL HP PrLiant Offline ACU Image kernel vmlinuz append initrd=initrd.img media=cdrm rw rt=/dev/ram0 ramdisk_size=257144 init=/bin/init lglevel=3 ide=ndma ide=nraid pnpbis=ff vga=791 splash=silent shwpts TYPE=MANUAL is1=nfs://192.168.0.99/path/t/acucd/image/hpacuffline-8.75-12.0.is is1mnt=/mnt/btdevice Yu can add additinal ISO images by specifying the additinal is# and is#mnt arguments, fr example, is2=/path/t/is2.is is2mnt=/mnt/is2. Supprted netwrk file systems The fllwing netwrk file systems are supprted fr use with PXE bting: NFS: is1=nfs://192.168.0.99/path/t/acucd/image/hpacuffline-8.75-12.0.is is1mnt=/mnt/btdevice NFS vlumes are munted with the fllwing ptins: - r nlck Windws perating systems: is1=smbfs://192.168.0.99/share/path/t/acucd/image/hpacuffline-8.75-12.0.is is1mnt=/mnt/btdevice Windws perating systems with lgin credentials: is1=smbfs://user:passwrd@192.168.0.99/share/path/t/acucd/image/hpacu ffline-8.75-12.0.is is1mnt=/mnt/btdevice Accessing ACU in the nline envirnment T access, install, and launch ACU in the nline envirnment, yu must dwnlad the ACU executables. All three frmats have separate executables. Starting with versin 8.28.13.0, ACU Scripting is nw a standalne applicatin that is distributed with the ACU CLI applicatin. In ACU versins prir t 8.28.13.0, the scripting executable was prvided with the ACU GUI cmpnent. HP Array Cnfiguratin Utility 15

Users familiar with the previus versins f ACU Scripting must nw install the ACU CLI applicatin t btain the scripting executable. The new ACU scripting executable (hpacuscripting) replaces the frmer executable (cpqacuxe) in all scripts. Fr infrmatin abut the minimum mnitr settings and the versin numbers f supprted perating systems and brwsers, see the README.txt file prvided with the executable. T use ACU in the nline envirnment: 1. Obtain the executable files frm ne f the fllwing lcatins: The HP website (http://www.hp.cm/supprt) When prmpted fr prduct infrmatin, enter the apprpriate server r server blade mdel name. The sftware CD that is prvided with the cntrller 2. Fllw the installatin instructins prvided with the executable. 3. After the executables are installed, launch each executable in the fllwing manner: GUI Click Start, and then select Prgrams>HP System Tls>HP Array Cnfiguratin Utility>Setup HP Array Cnfiguratin Utility. Depending n yur cnfiguratin scenari, chse ne f the fllwing ptins: Launching ACU n a lcal server (n page 16) Launching ACU n a lcal server t cnfigure a remte server (n page 17) Launching ACU n a remte server t cnfigure a lcal server (n page 18) CLI Click Start, and then select Prgrams>HP System Tls>HP Array Cnfiguratin Utility>Setup HP Array Cnfiguratin Utility CLI. Scripting Run hpacuscripting.exe. Launching ACU n a lcal server Micrsft OS 1. Click Start, and then select Prgrams>HP System Tls>HP Array Cnfiguratin Utility>Setup HP Array Cnfiguratin Utility. The Executin Mde screen appears. If Lcal Applicatin Mde is selected, cntinue with step 2. If Remte Service Mde is selected, select Lcal Applicatin Mde, rebt the server, and then cntinue with step 2. 2. Click Start, and then select Prgrams>HP System Tls>HP Array Cnfiguratin Utility. ACU launches in either a brwser (lder versins) r applicatin windw (v8.70 and later) ACU then scans the system and detects cntrllers. This prcess can last up t 2 minutes. When cntrller detectin is cmplete, the cntrllers are available n the Cntrller/Device menu. 3. Cnfigure a cntrller ("Cnfiguring a cntrller" n page 30). When cnfiguratin is cmplete, cntinue with the next step. 4. If yu changed t Lcal Applicatin mde in step 1, and yu are finished cnfiguring arrays n this server, d the fllwing: a. Click Start, and then select Prgrams>HP System Tls>HP Array Cnfiguratin Utility>Setup HP Array Cnfiguratin Utility. b. When the Executin Mde screen appears, select Remte Service Mde. HP Array Cnfiguratin Utility 16

c. Rebt the server. 5. (Optinal) T make newly created lgical drives available fr data strage, use the perating system disk management tls t create partitins and frmat the drives. Linux OS 1. Frm any cmmand prmpt, enter ne f the fllwing: Fr lcal mde, enter: cpqauxe-nsmh Fr remte mde, enter: cpqacuxe-r ACU launches in a brwser (Mzilla Firefx). 2. Fr a list f ptins, enter the fllwing: cpqacuxe-h Launching ACU n a lcal server t cnfigure a remte server 1. On the lcal server (hst), click Start, and then select Prgrams>HP System Tls>HP Array Cnfiguratin Utility>Setup HP Array Cnfiguratin Utility. The Executin Mde screen appears. If Remte Service Mde is selected, cntinue with step 2. If Lcal Applicatin Mde is selected, select Remte Service Mde, rebt the server, and then cntinue with step 2. 2. On the remte server, pen the brwser. 3. Enter the fllwing text int the address field f the remte brwser (where servername is the name r IP address f the hst): http://servername:2301 The lgin screen fr the System Management Hmepage pens. 4. Enter yur lgin credentials: If yu are using versin 2.0.0 r later f the System Management Hmepage, use yur perating system user name and passwrd. If yu are using an earlier versin f the System Management Hmepage, use yur WBEM user name and passwrd. The System Management Hmepage pens. Fr mre infrmatin abut the System Management Hmepage, see the fllwing: The HP System Management Hmepage web page (http://h18013.www1.hp.cm/prducts/servers/management/agents/index.html) The HP System Management Hmepage Installatin Guide n the HP website (http://www.hp.cm) 5. Click Array Cnfiguratin Utility n the left side f the screen. ACU pens, scans the remte server, and detects cntrllers. This prcess can last up t 2 minutes. When cntrller detectin is cmplete, the cntrllers are available n the Cntrller/Device menu. 6. Cnfigure a cntrller ("Cnfiguring a cntrller" n page 30). When cnfiguratin is cmplete, cntinue with the next step. 7. T perate ACU n this server in Lcal Applicatin mde, d the fllwing: HP Array Cnfiguratin Utility 17

a. Click Start, and then select Prgrams>HP System Tls>HP Array Cnfiguratin Utility>Setup HP Array Cnfiguratin Utility. b. When the Executin Mde screen appears, select Lcal Applicatin Mde. c. Rebt the server. 8. (Optinal) T make newly created lgical drives available fr data strage, use the perating system disk management tls t create partitins and frmat the drives. Launching ACU n a remte server t cnfigure a lcal server 1. On the server where ACU is installed, click Start, and then select Prgrams>HP System Tls>HP Array Cnfiguratin Utility>Setup HP Array Cnfiguratin Utility. The Executin Mde screen appears. If Remte Service Mde is selected, cntinue with step 2. If Lcal Applicatin Mde is selected, select Remte Service Mde, rebt the server, and then cntinue with step 2. 2. On the server that yu want t cnfigure, cnnect t the Systems Insight Manager server (prt: 280), and then lg in. 3. Select Device Queries. 4. Under Device by Type, select All Servers. 5. Cnnect t the server that is running ACU. 6. Under Device Links, select System Management Hmepage. The lgin screen fr the System Management Hmepage pens. 7. Lg in using yur credentials: If yu are using versin 2.0.0 r later f the System Management Hmepage, use yur perating system user name and passwrd. If yu are using an earlier versin f the System Management Hmepage, use yur WBEM user name and passwrd. The System Management Hmepage pens. Fr mre infrmatin abut the System Management Hmepage, see the fllwing: The HP System Management Hmepage web page (http://h18013.www1.hp.cm/prducts/servers/management/agents/index.html) The HP System Management Hmepage Installatin Guide n the HP website (http://www.hp.cm) 8. Click Array Cnfiguratin Utility n the left side f the screen. ACU pens, scans the remte server, and detects cntrllers. This prcess can last up t 2 minutes. When cntrller detectin is cmplete, the cntrllers are available n the Cntrller/Device menu. 9. Cnfigure a cntrller ("Cnfiguring a cntrller" n page 30). When cnfiguratin is cmplete, cntinue with the next step. 10. T perate ACU n the remte server in Lcal Applicatin Mde, d the fllwing: a. Click Start, and then select Prgrams>HP System Tls>HP Array Cnfiguratin Utility>Setup HP Array Cnfiguratin Utility. b. When the Executin Mde screen appears, select Lcal Applicatin Mde. HP Array Cnfiguratin Utility 18

c. Rebt the server. 11. (Optinal) T make newly created lgical drives available fr data strage, in a Windws OS, use the perating system disk management tls t create partitins and frmat the drives. Using the ACU GUI Access ACU with ne f the many methds available: Accessing ACU in the ffline envirnment (n page 10) Accessing ACU in the nline envirnment (n page 15) When yu launch the ACU GUI, the applicatin pens and ACU scans the system and detects cntrllers. This prcess can last up t 2 minutes. When cntrller detectin is cmplete, the cntrllers are available n the Cntrller/Device menu. After the GUI is pen, tasks are distributed amng categries. Fr mre infrmatin, see "Navigating the GUI (n page 19)." Navigating the GUI When yu pen ACU, the Welcme screen appears. The fllwing elements are visible: Three tabs appear near the tp left f the screen. The latest versin f the ACU GUI uses tab navigatin. Clicking a tab displays the screen and tasks fr the fllwing categries: Cnfiguratin This screen displays available cntrller and array tasks that the user can select and cmplete manually. HP Array Cnfiguratin Utility 19

In previus versins f ACU, this prcess was called the Standard Cnfiguratin mde. Fr mre infrmatin, see "Cnfiguratin screen (n page 20)." Diagnstics/SmartSSD This screen displays a list f cntrllers and ptins fr generating, viewing, and saving diagnstic reprts fr thse cntrllers. In previus versins, this tab and screen were called Diagnstics. Fr mre infrmatin, see "Diagnstics/SmartSSD screen (n page 22)." Wizards This screen displays available array and cntrller tasks that ACU can cmplete autmatically r with minimal user input, such as express cnfiguratin. In previus versins f ACU, this functinality was called the Cnfiguratin Wizards mde and Express mde. Fr mre infrmatin, see "Wizards screen (n page 25)." The Cntrller/Device menu is belw the tabs. T select a device, click n the menu, and then select a device. Use the scrll bar t view all the devices, as needed. The Rescan System buttn is t the right f the menu. After adding r remving devices, click Rescan System t update the list f available devices. The Help buttn is near the tp right f the screen. T access help tpics, press the H key r click Help. Fr mre infrmatin, see "ACU Help (n page 28)." The Exit ACU buttn is near the bttm left f the screen. Cnfiguratin screen T access this screen, click the Cnfiguratin tab. The Cnfiguratin screen displays the GUI elements frm the Welcme screen and prvides status, mre detailed infrmatin, and available tasks r ptins fr the selected device. HP Array Cnfiguratin Utility 20

When a device is selected, the fllwing elements appear: System Status This panel, at left, prvides the fllwing infrmatin and functinality: Date and time stamps fr the status A Refresh buttn t refresh the status Status icns (critical, warning, and infrmatinal) with the number f individual alerts fr each categry A View Status Alert link that displays device-specific alerts n the right side f the screen Systems And Devices This panel, at left, prvides the fllwing infrmatin and functinality: A tree detailing systems, cntrllers, arrays, physical drives, and lgical drives Expand all and cllapse all buttns A Shw menu that tggles between Lgical View and Physical View Available Tasks This panel, at right, prvides the fllwing infrmatin and functinality: Tasks that are available fr the selected device based n its current status and cnfiguratin HP Array Cnfiguratin Utility 21

Optins and infrmatin pertinent t the task, after a task is selected Fr a list f pssible tasks that are available n the Cnfiguratin screen, see "Cnfiguratin tasks (n page 28)." Diagnstics/SmartSSD screen T access this screen, click the Diagnstics/SmartSSD tab. HP Array Cnfiguratin Utility 22

The Diagnstics/SmartSSD screen prvides a list f cntrllers and ptins related t generating and viewing diagnstic reprts. Tasks are selectable frm this screen. Additinal tasks are available upn clicking Run Array Diagnstics Reprts. On the diagnstic reprt screen, when a device is selected, the fllwing elements appear: Reprt Cntents This panel, at left, prvides the fllwing infrmatin and functinality: A list f all cnnected cntrllers and devices HP Array Cnfiguratin Utility 23

Check bxes fr individual cntrllers r all cntrllers Available Tasks This panel, at right, prvides the fllwing infrmatin and functinality: Tasks that are available fr the selected device based n its current status and cnfiguratin HP Array Cnfiguratin Utility 24

Optins and infrmatin pertinent t the task, after a task is selected Fr a list f pssible tasks that are available n the Diagnstics/SmartSSD screen, see "Diagnstics tasks (n page 39)." Wizards screen T access this screen, click the Wizards tab. HP Array Cnfiguratin Utility 25

The Wizards screen displays the GUI elements frm the Welcme screen and prvides status, mre detailed infrmatin, and available wizards r ptins fr the selected device. When a device is selected, the fllwing elements appear: System Status This panel, at left, prvides the fllwing infrmatin and functinality: Date and time stamps fr the status A Refresh buttn t refresh the status Status icns (critical, warning, and infrmatinal) with the number f individual alerts fr each categry A View Status Alert link that displays device-specific alerts n the right side f the screen Systems And Devices This panel, at left, prvides the fllwing infrmatin and functinality: A tree detailing systems, cntrllers, arrays, physical drives, and lgical drives Expand all and cllapse all buttns HP Array Cnfiguratin Utility 26

A Shw menu that tggles between Lgical View and Physical View In this example, the Systems And Devices infrmatin cntinues past the edge f the panel. T view all f the infrmatin, use the hrizntal scrll bar r use the muse t widen the panel. Available Wizards This panel, at right, prvides the fllwing infrmatin and functinality: Wizards that are available fr the selected device based n its current status and cnfiguratin HP Array Cnfiguratin Utility 27

Optins and infrmatin pertinent t the wizard, after a wizard is selected ACU help Fr a list f pssible wizards that are available n the Wizards screen, see "Wizards (n page 41)." The Help buttn, at upper right, pens the embedded ACU help file. In additin t prviding infrmatin abut the main screens and tabs, Help als prvides several useful tpics fr new users, including the fllwing: Image Legend A visual reference list defining the icns and graphical buttns used in ACU Keybard Cntrls An explanatin and list f keybard functins fr navigating the GUI Keybard Shrtcuts A list f keys and peratins they perfrm within the GUI T view these help tpics and thers, press the H key r click Help. When the Help windw pens, expand the tpic "Getting Started with ACU." The glssary in ACU help defines industry standard and HP terms as they relate t the ACU applicatin. Cnfiguratin tasks Frm the Cnfiguratin screen, yu can perfrm tasks related t cntrllers, arrays, physical drives, and lgical drives. HP Array Cnfiguratin Utility 28

Fr certain tasks, the cntrller must have SAAP activated by a registered license key. Fr mre infrmatin, see "Abut SAAP (n page 8)." When a cntrller r device is selected, the tasks that appear are a subset f the ttal number f pssible tasks fr the selected item. ACU lists r mits tasks based n the cntrller mdel and cnfiguratin. Fr example, if the selected cntrller has n unassigned physical drives, Create Array is nt an available task. The fllwing table lists all the pssible tasks fr every type f item. Item Tasks Cntrller Advanced Cntrller Settings* ** Array Acceleratr Settings Clear Cnfiguratin Cntrller Settings Create Array Disable Standby Cntrller Enable HP SmartCache Manage License Keys* Mre Infrmatin Physical Drive Write Cache Settings Redundancy Settings* View Status Alerts Array Create Array Create Lgical Drive Create Split Mirrr Backup Delete Expand Array Heal Array** Manage Split Mirrr Backup Mre Infrmatin Mve Array** Re-Mirrr Array** Replace Array** Shrink Array** Spare Management Split Mirrred Array** View Status Alerts Lgical drive Create Lgical Drive Delete Erase Drive* ** Extend Lgical Drive Migrate RAID/Stripe Size Mve Lgical Drive* ** Mre Infrmatin Re-enable Failed Lgical Drive View Status Alerts Unused space Create Lgical Drive Mre Infrmatin Physical drive Erase Drive** View Status Alerts Unassigned drives Create Array Mre Infrmatin *This task is nt available n all cntrller mdels. **If perfrmed with an HP Smart Array G6 r G7 cntrller, this task requires a registered SAAP license key r a cntrller where SAAP functinality is standard. See "Abut SAAP (n page 8)." HP Array Cnfiguratin Utility 29

If perfrmed with a Gen8 cntrller, this task requires a registered HP SmartCache license key. Cnfiguring a cntrller 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." 2. Select a cntrller frm the Cntrller/Device menu. The Cnfiguratin screen appears. 3. Cnfigure the cntrller: T cnfigure manually, see "Perfrming a Cnfiguratin task (n page 30)." T cnfigure with a wizard, see "Using Wizards (n page 42)" r "Using Express Cnfiguratin (n page 44)." 4. When prmpted, save the cnfiguratin. 5. D ne f the fllwing: Cnfigure an additinal cntrller. Repeat steps 3 thrugh 5. Click Exit ACU. Perfrming a Cnfiguratin task 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." If ACU is already pen, click the Cnfiguratin tab. 2. Select a device frm the Cntrller/Device menu. HP Array Cnfiguratin Utility 30

The System Status, Systems And Devices, and Available Tasks panels appear. The listed tasks are available fr this device in its current cnfiguratin. Fr mre infrmatin, see "Cnfiguratin tasks (n page 28)." 3. Click a task buttn. HP Array Cnfiguratin Utility 31

A list f all pssible ptins fr that task appears n the right side f the screen, replacing the task list. 4. Select the settings r cnfiguratin ptins fr the device. 5. Use the Next and Back buttns t navigate multiple screens f ptins. 6. Click Save r OK. Rapid Parity Initializatin When yu create a lgical drive, yu must initialize the parity using Rapid Parity Initializatin. RAID levels that use parity (RAID 5, RAID 6 (ADG), RAID 50, and RAID 60) require that the parity blcks be initialized t valid values. Valid parity data is required t enable enhanced data prtectin thrugh backgrund surface scan analysis and higher perfrmance write peratins. Tw initializatin methds are available: Default Initializes parity blcks in the backgrund while the lgical drive is available fr access by the perating system. A lwer RAID level results in faster parity initializatin. Rapid Overwrites bth the data and parity blcks in the fregrund. The lgical drive remains invisible and unavailable t the perating system until the parity initializatin prcess cmpletes. All parity grups are initialized in parallel, but initializatin is faster fr single parity grups (RAID 5 and RAID 6). RAID level des nt affect system perfrmance during rapid initializatin. Rapid Parity Initializatin is available nly fr supprted cntrllers and in arrays cmpsed f supprted physical drives. T select the methd fr parity initializatin: 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." HP Array Cnfiguratin Utility 32

If ACU is already pen, click the Cnfiguratin tab. 2. Select a cntrller frm the Cntrller/Device menu. The System Status, Systems And Devices, and Available Tasks panels appear. 3. Select Create a lgical drive. 4. Make selectins fr Fault Tlerance, Strip Size, Sectrs/Track, Size, and Caching. 5. Under Parity Initializatin Methd, select either Default r Rapid. 6. Click Save. Installing a license key with ACU Yu can use HP SSA t install the license key and activate SAAP and HP SmartCache functinality. Fr mre infrmatin, see "Abut SAAP (n page 8)." T install a license key: 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." If ACU is already pen, click the Cnfiguratin tab. 2. Select a cntrller frm the Cntrller/Device menu. The System Status, Systems And Devices, and Available Tasks panels appear. 3. In the Available Tasks panel, click Manage License Keys. Specific license key tasks appear. A cmplete list f existing license keys als appears. 4. Click Add License Key. 5. Enter the license key number. 6. Click Save. HP Array Cnfiguratin Utility 33

Changing the Spare Activatin Mde The spare activatin mde feature enables the cntrller firmware t activate a spare drive under the fllwing cnditins: When a data drive reprts a predictive failure (SMART) status When a data drive fails; this mde is the default. In nrmal peratins, and fr lder cntrllers, the firmware starts rebuilding a spare drive nly when a data drive fails. With the predictive failure activatin mde, rebuilding can begin befre the drive fails, reducing the likelihd f data lss that culd ccur if an additinal drive fails. T change the Spare Activatin Mde: 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." If ACU is already pen, click the Cnfiguratin tab. 2. Select a cntrller frm the Cntrller/Device menu. The System Status, Systems And Devices, and Available Tasks panels appear. 3. In the Available Tasks panel, click Mdify Spare Activatin Mde. 4. Frm the menu, select ne f the fllwing mdes: 5. Click Save. Failure Spare Activatin Predictive Spare Activatin Changing the Spare Management mde The Spare Management feature prvides multiple methds fr handling spare behavir. Yu can chse frm the fllwing ptins: Dedicated The failed data drive, when replaced, must be rebuilt frm the data n the spare drive. In Dedicated mde, ne spare can be dedicated t multiple arrays. Aut-Replace Drives The spare fr the failed data drive autmatically becmes the replacement data drive. When the spare is replaced, the data drive des nt need t be rebuilt. In Aut-replace mde, spare drives cannt be shared between arrays. If assigning Aut-Replace Drives mde t an array with a RAID 0 drive, Spare Activatin Mde must be set t Predictive Spare Activatin mde. T change the Spare Management mde: 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." If ACU is already pen, click the Cnfiguratin tab. 2. Select a cntrller frm the Cntrller/Device menu. The System Status, Systems And Devices, and Available Tasks panels appear. 3. In the Available Tasks panel, click Spare Management. 4. Frm the menu, select ne f the fllwing mdes: Dedicated Aut-Replace Drives HP Array Cnfiguratin Utility 34

5. Click Save. Abut HP SmartCache HP SmartCache enables slid state drives t be used as caching devices fr hard drive media. Data can be accessed frm the slid state drive instead f hard drives. HP SmartCache prvides the fllwing features: Accelerates applicatin perfrmance Prvides lwer latency fr transactins in applicatins Supprts all perating systems, withut the need fr changes T supprt HP SmartCache, the Smart Array Cntrller firmware must be 3.42 r later. ACU must be versin 9.40.12.0 r later. HP SmartCache requires a Smart Array Advanced Pack license (http://www.hp.cm/g/saap). Enable HP SmartCache Enabling HP SmartCache creates an array t create SmartCaches and assign them t accelerate lgical drives. At least ne lgical drive must be created n the cntrller prir t enabling HP SmartCache. T enable HP SmartCache: 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." 2. Select a cntrller frm the Cntrller/Device menu. The Cnfiguratin screen appears. HP Array Cnfiguratin Utility 35

3. Click Enable HP SmartCache. 4. Select a slid state drive type. 5. Select ne r mre physical drives frm the list f available drives. 6. Click Save. Sme features may nt be available with HP SmartCache enabled. 7. With the SmartCache selected in the left panel, click Create SmartCache fr Lgical Drive. 8. Select the lgical drive t cache. 9. Select the size f the cache. HP recmmends 10% f the drive size, and it must be a minimum f 1 GiB. 10. Click Save. The SmartCache is created fr the Lgical Drive. Wrking with mirrred arrays Amng the advanced tasks pssible with the ACU GUI, yu can split a mirrred array and then recmbine it. This prcess entails breaking a RAID 1 r RAID 1+0 mirrr int tw identical new arrays cnsisting f RAID 0 lgical drives. Supprt fr these prcedures requires the fllwing: The ACU GUI must be run in ffline mde ("Accessing ACU in the ffline envirnment" n page 10). HP Smart Array G6 and G7 cntrller mdels must have a valid SAAP license ("Abut SAAP" n page 8). Mirrred arrays being split can have RAID 1, RAID 1+0, RAID 1 (ADM), r RAID 10 (ADM) cnfiguratins. Arrays with ther RAID cnfiguratins cannt be split. Several reasns exist fr splitting and recmbining a mirrred array. Fr mre infrmatin, see the "RAID 1(+0): breaking mirrrs and rebuilding drives" hw-t white paper n the HP website (http://h20000.www2.hp.cm/bc/dcs/supprt/supprtmanual/c00378986/c00378986.pdf). HP Array Cnfiguratin Utility 36

Splitting a mirrred array 1. Run the ACU GUI in ffline mde. See "Accessing ACU in an ffline envirnment ("Accessing ACU in the ffline envirnment" n page 10)." 2. At the Cnfiguratin screen, select the apprpriate cntrller frm the Cntrller/Device menu. 3. Frm the Systems and Devices tree, select the apprpriate array. 4. In the Available Tasks panel, click Split Mirrred Array. 5. Click OK. 6. When ACU finishes splitting the array, tw lgical drives appear in the Systems and Devices tree: When a RAID 1 r RAID 1+0 array splits, tw RAID 0 lgical drives are created. When an array that cntains a RAID 1 (ADM) lgical drive splits, a RAID 1 lgical drive and a RAID 0 lgical drive are created. When an array that cntains a RAID 10 (ADM) lgical drive splits, a RAID 1+0 lgical drive and a RAID 0 lgical drive are created. 7. Shut dwn the OS. 8. Pwer dwn the server. 9. With pwer ff, remve the physical drives that cnstitute ne f the new arrays. If yu d nt remve the physical drives fr ne f the arrays, the OS will be unable t distinguish between the tw arrays when the server is restarted, because the arrays are identical. 10. Pwer up the server. 11. Restart the OS. Recmbining a split mirrred array 1. Run the ACU GUI in ffline mde. See "Accessing ACU in the ffline envirnment (n page 10)." 2. At the Cnfiguratin screen, select the apprpriate cntrller frm the Cntrller/Device menu. 3. Frm the Systems and Devices tree, select the array t use as the surce array. 4. In the Available Tasks panel, click Re-Mirrr Array. 5. Select the array t be mirrred t the surce array. This array is usually the array that was split frm the riginal mirrred array. Hwever, it can be any ther array f the crrect size. 6. Click OK. 7. When ACU finishes re-mirrring the array, restart the OS. The cntrller uses the rebuild prcess t synchrnize the mirrred drives. The drive nline LED flashes during the rebuild prcess. Depending n the hard drive size and the server lad, this prcess can take up t 2 hurs. Yu can bt the OS during this time, but the lgical drive is nt fault-tlerant until the rebuild is cmplete. Creating a split mirrr backup This task splits an array that cnsists f ne r mre RAID 1, RAID 1+0, RAID 1 (ADM), r RAID 10 (ADM) lgical drives, and then creates tw arrays: a primary array and a backup array. T create a split mirrr backup: 1. Run the ACU GUI in ffline mde. See "Accessing ACU in the ffline envirnment (n page 10)." HP Array Cnfiguratin Utility 37

2. At the Cnfiguratin screen, select the apprpriate cntrller frm the Cntrller/Device menu. 3. Frm the Systems and Devices tree, select the apprpriate array. 4. In the Available Tasks panel, click Create Split Mirrr Backup. A verificatin and message dialg bx appears. 5. Click OK. ACU creates the array accrding t the fllwing rules: If the riginal array cntained RAID 1 r RAID 1+0 drives, then the primary array will cntain RAID 0 drives. If the riginal array cntained RAID 1 (ADM) drives, the primary array will cntain RAID 1 drives. If the riginal array cntained RAID 10 (ADM) drives, the primary array will cntain RAID 1+0 drives. The backup array always cntains RAID 0 lgical drives. The primary array cntinues t be fully accessible t the perating system while the backup array is hidden frm the perating system. 6. When ACU finishes creating the split mirrr backup, the new backup array appears in the Systems and Devices tree: The array includes the designatin "Backup" at the beginning f the array name. Re-mirrring, rlling back, r re-activating a split mirrr backup 1. Run the ACU GUI in ffline mde. See "Accessing ACU in the ffline envirnment (n page 10)." 2. At the Cnfiguratin screen, select the apprpriate cntrller frm the Cntrller/Device menu. 3. Frm the Systems and Devices tree, select the primary array. 4. In the Available Tasks panel, click Manage Split Mirrr Backup. 5. Select ne f the fllwing actins: Re-mirrr the array and preserve the existing data. Discard the backup array. This ptin re-creates the riginal mirrred array with the current cntents f the primary array. Re-mirrr the array and rll back t the cntents f the backup array. Discard existing data. This ptin re-creates the mirrred array but restres its riginal cntents, which are in the backup array. HP recmmends that yu d nt perfrm this ptin under the fllwing circumstances: In an nline envirnment If the lgical drive t be rlled back is munted If the lgical drive t be rlled back is in use by the perating system Activate the backup array. This ptin makes the backup array fully accessible t the perating system. ACU remves the designatin "backup" frm the name f the array. HP Array Cnfiguratin Utility 38

Healing an array The Heal Array peratin enables yu t enter a cmmand t replace failed physical drives in the array with healthy physical drives. After replacement, the riginal array and lgical drive numbering is unaffected. T use Heal Array, yu must meet the fllwing cnditins: The array has at least ne failed drive. The array is nt transfrming (fr example, rebuilding t a spare). The array has a wrking cache, making it capable f transfrmatin. The replacement physical drives and the riginal drives must be f the same interface type, such as SAS, SATA, and s n. A sufficient number f unassigned physical drives f the crrect size are available t replace each failed physical drive in the array. The crrect size is defined as a drive as large as the smallest drive n the array, but n larger than the smallest spare. If using an HP PrLiant Smart Array G6 r G7 cntrller, an SAAP 1.0 license is activated. When yu select Heal Array, and all cnditins are met, ne f the fllwing actins ccurs t the vlume in the array: If a vlume has failed, ACU recreates the vlume. This actin ccurs with a RAID 0 vlume. If a vlume is degraded, ACU rebuilds the vlume. Replacing an array Sme cntrllers may nt supprt this ptin r might require a license key t enable the feature. ACU enables yu t transfer the cntents f an array t an existing empty array r a new array. During this peratin, all lgical drives transfer frm the riginal array t the destinatin array. The riginal array is deleted, and the drives that were being used are freed and listed as unassigned drives. Replacing an array is a time-cnsuming prcess fr tw reasns: all data in each lgical drive is cpied t the destinatin array, and the cntrller perfrms all data transfrmatins while servicing IO requests t ther lgical drives. T perfrm the Replace Array peratin, yu must meet the fllwing cnditins: The destinatin array must have the same number f physical drives as the surce r riginal array. Bth the surce and destinatin arrays must be in OK state. All existing lgical drives in the surce array must be in OK state. The destinatin array must have sufficient capacity t hld all lgical drives present in the surce array. Diagnstics tasks The ACU Diagnstics feature replaced the Array Diagnstic Utility supprted by SmartStart v8.20 and earlier. Beginning with ACU v8.70.9, the diagnstics functinality within ACU has expanded and includes the SmartSSD Wear Gauge. ACU generates the fllwing reprts and lgs: Array diagnstic reprt HP Array Cnfiguratin Utility 39

This reprt cntains infrmatin abut all devices, such as array cntrllers, strage enclsures, drive cages, as well as lgical, physical, and tape drives. Fr supprted slid state drives, this reprt als cntains SmartSSD Wear Gauge infrmatin. SmartSSD Wear Gauge reprt This reprt cntains infrmatin abut the current usage level and remaining expected lifetime f slid state drives attached t the system. Serial utput lgs This lg details the serial utput fr the selected cntrller. Fr each cntrller, r fr all f them, yu can select the fllwing tasks: View Diagnstic Reprt Generate Diagnstic Reprt View Serial Output Lgs View SmartSSD Wear Gauge Reprt Generate SmartSSD Wear Gauge Reprt Fr the view tasks, ACU generates and displays the reprt r lg. Fr the generate tasks, ACU generates a reprt withut the graphical display. Fr either task, yu can save the reprt. In the SmartStart envirnment (G7 r earlier servers), yu can save the reprt t a frmatted diskette r USB device. In nline and ffline envirnments, ACU saves the diagnstic reprt t a cmpressed flder, which cntains an XML reprt, a plain text reprt, and a viewer file s yu can display and navigate the reprt thrugh a web brwser. Each ACU Diagnstics reprt cntains a cnslidated view f any errr r warning cnditins encuntered. It als prvides detailed infrmatin fr every strage device, including the fllwing: Device status Cnfiguratin flags Firmware versin numbers Physical drive errr lgs ACU Diagnstics never cllects infrmatin abut the data cntent f lgical drives. The diagnstic reprt des nt cllect r include the fllwing: File system types, cntents, r status Partitin types, sizes, r layut Sftware RAID infrmatin Operating system device names r munt pints Perfrming a Diagnstics task 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." If ACU is already pen, click the Diagnstics/SmartSSD tab. The Diagnstics/SmartSSD screen appears with the fllwing selectins: View SmartSSD Wear Gauge Reprt HP Array Cnfiguratin Utility 40

Generate SmartSSD Wear Gauge Reprt Run Array Diagnstic Reprts Fr this example, use the diagnstic reprts selectin. 2. Select Run Array Diagnstic Reprts. The array diagnstic reprt screen appears. 3. Select a device r devices frm the Reprt Cntents panel. The Available Tasks panel appears. Fr mre infrmatin, see "Diagnstics tasks (n page 39)." Wizards 4. Click ne f the task buttns: If yu select Generate Diagnstic Reprt, wait fr the reprt t generate, and then click Clse Reprt r Save Reprt. If yu select View Diagnstic Reprt, the reprt appears. When yu are finished viewing the current reprt, click Clse Reprt, Refresh Reprt, r Save Reprt. If yu select View Serial Output Lgs, the lg appears. When yu are finished viewing the lg, click Clse Lgs. Fr mre infrmatin abut reprts and viewing them in a brwser, see the fllwing sectins: "Reprted infrmatin (n page 92)" "Identifying and viewing diagnstic reprt files (n page 99)" "Identifying and viewing SmartSSD Wear Gauge reprt files (n page 101)" Frm the Wizards screen, yu can perfrm tasks related t cntrllers, arrays, physical drives, and lgical drives. HP Array Cnfiguratin Utility 41

Fr certain tasks, the cntrller must have SAAP activated by a registered license key. Fr mre infrmatin, see "Abut SAAP (n page 8)." When a cntrller is selected, the wizards that appear are a subset f the ttal number f wizards that are pssible fr the selected cntrller. ACU lists r mits wizards based n the cntrller mdel and cnfiguratin. Fr example, if the selected cntrller has n unassigned physical drives, Expand Array is nt an available wizard. Wizards are available by selecting the rt cntrller in the Systems and Devices tree. The fllwing list includes all pssible wizards: Add Lgical Drive Cntrller Settings Expand Array Express Cnfiguratin Manage Spare Drive Migrate Lgical Drive Mve Array Remve Lgical Drive Fr mre infrmatin, see "Using Wizards (n page 42)." The Express Cnfiguratin wizard perates differently. See "Using Express Cnfiguratin (n page 44)." Using Wizards 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." If ACU is already pen, click the Wizards tab. 2. Select a cntrller frm the Cntrller/Device menu. HP Array Cnfiguratin Utility 42

The System Status, Systems And Devices, and Available Wizards panels appear. The listed wizards are available fr this device in its current cnfiguratin. Fr mre infrmatin, see "Wizards (n page 41)." 3. Click a wizard buttn. HP Array Cnfiguratin Utility 43

A list f all pssible ptins fr that wizard appears n the right side f the screen, replacing the wizard list. 4. Select the settings r cnfiguratin ptins fr the device. 5. Use the Next and Back buttns t navigate multiple screens f ptins. 6. Click Save r OK. Using Express Cnfiguratin Express Cnfiguratin is a wizard that creates the ptimum number f arrays and lgical drives frm all f the physical drives that are attached t the cntrller. This wizard is available nly under tw cnditins: when an array n the selected cntrller cntains unused drive space, r when physical drives are cnnected t the cntrller, but they are nt assigned t an array. T use Express Cnfiguratin: 1. Open ACU. Fr mre infrmatin, see "Using the ACU GUI (n page 19)." If ACU is already pen, click the Wizards tab. 2. Select a cntrller frm the Cntrller/Device menu. The System Status, Systems And Devices, and Available Wizards panels appear. The listed wizards are available fr this device in its current cnfiguratin. Fr mre infrmatin, see "Wizards (n page 41)." 3. Click Express Cnfiguratin. HP Array Cnfiguratin Utility 44

ACU displays pssible lgical drive cnfiguratins based n grupings f drives with the same capacity. 4. Fr each lgical drive, select a RAID Type. ACU identifies pssible RAID cnfiguratins and lists spare drive capability, the size f the lgical drive, fault tlerance, and write perfrmance. 5. Click Next. The wizard cnfigures the arrays and lgical drives. 6. When the cnfiguratin is cmplete, click Finish. Using the ACU CLI Access ACU with ne f the many methds available: Accessing ACU in the ffline envirnment (n page 10) Accessing ACU in the nline envirnment (n page 15) Sme ACU CLI features are nly available in the ffline envirnment, such as setting the bt cntrller and bt vlume. ACU CLI has tw perating mdes: Cnsle mde ("Opening the CLI in Cnsle mde" n page 46) Yu can adjust several cnfiguratin parameters n several devices withut having t restart ACU each time. Cmmand mde ("Opening the CLI in Cmmand mde" n page 46) HP Array Cnfiguratin Utility 45

Yu can make an islated change f just ne cnfiguratin parameter n ne device. Fr VMware ESXi 5.0, ACU CLI wrks similarly t the Cmmand mde mentined. Hwever, slight differences exist, requiring yu t run ACU CLI thrugh the VMware vsphere esxcli cmmand-line utility. Fr mre infrmatin abut using HP ACU CLI fr ESXi 5.0, see ACU CLI release ntes r the HP website (ftp://ftp.hp.cm/pub/sftlib2/sftware1/pubsw-linux/p414707558/v68034/hpacucli-9.0-24.0.narc h.txt). Opening the CLI in Cnsle mde The syntax f the cmmand required t pen the ACU CLI in Cnsle mde depends n the perating system that yu are using. Fr Micrsft Windws, enter the fllwing text: C:\Prgram Files\Cmpaq\Hpacucli\Bin\hpacucli.exe Alternatively, click Start, and select Prgrams>HP System Tls>HP Array Cnfiguratin Utility CLI>HP Array Cnfiguratin Utility CLI. Fr Linux, enter the fllwing text: [rt@lcalhst rt]# hpacucli After yu have entered Cnsle mde in either perating system, the screen displays the fllwing message and cnsle prmpt: HP Array Cnfiguratin Utility CLI 7.15.17.0 Detecting Cntrllers...Dne. Type "help" fr a list f supprted cmmands. Type "exit" t clse the cnsle. => The remaining examples in the ACU CLI sectin f this guide are described as if entered in Cnsle mde. Opening the CLI in Cmmand mde CLI syntax T use Cmmand mde, identify the apprpriate ACU CLI cmmand ("The <cmmand> variable" n page 47). Then, add the cmmand t the end f the text line that is used fr pening the CLI in Cnsle mde (n page 46). The fllwing examples use help as the cmmand: Using Micrsft Windws : C:\Prgram Files\Cmpaq\Hpacucli\Bin\hpacucli.exe help Using Linux: [rt@lcalhst rt]# hpacucli help The remaining examples in the ACU CLI sectin f this guide are described as if entered in Cnsle mde. Whether entered in Cmmand mde r Cnsle mde, a typical ACU CLI cmmand line cnsists f three parts: a target device, a cmmand, and a parameter with values if necessary. Using angle brackets t dente a required variable and plain brackets t dente an ptinal variable, the structure f a typical ACU CLI cmmand line is as fllws: <target> <cmmand> [parameter=value] HP Array Cnfiguratin Utility 46

The <target> variable This variable prvides the path t the device that yu want t cnfigure. The device can be a cntrller, an array, a lgical drive, r a physical drive. The syntax used is as fllws: cntrller all slt=# wwn=# chassisname="aaa" serialnumber=# chassisserialnumber=# [array=all <id>] [lgicaldrive all #] [physicaldrive all allunassigned [#:]#:#,[#:]#:#... [#:]#:#-[#:]#:#] Fr example: cntrller slt=3 cntrller wwn=500805f3000bac11 cntrller slt=2 array A cntrller chassisname="a" array B lgicaldrive 2 cntrller chassisname="a" physicaldrive 1:0 cntrller all cntrller slt=2 array all cntrller slt=3 physicaldrive 1:2-1:5 The <cmmand> variable The <cmmand> variable can be any f the fllwing wrds r phrases, crrespnding t typical cnfiguratin tasks: add create delete mdify remve set target Nncnfiguratin cmmands are als available: diag ("Generating a diagnstic reprt" n page 53) help ("The help cmmand" n page 51) rescan ("Rescanning the system" n page 54) shrthand ("Keywrd abbreviatins" n page 48) shw ("The shw cmmand" n page 49) versin ("Displaying the current versins f the applicatin layers" n page 51) A cmmand ften requires a parameter, and sme parameters require a value, but the specific parameters and values that are valid fr a given cmmand depend n the target t which yu apply the cmmand. T determine the valid parameters and values fr a particular cmbinatin f target and cmmand variables, yu can query the device ("Querying a device" n page 47). Yu can als inspect the example cmmands in ther sectins f this guide. Querying a device If yu d nt knw what values a parameter can have, yu can smetimes query the device t find ut by entering a? as the value f the parameter. Example cmmand: => ctrl ch="lab4" ld 1 mdify raid=0 ss=? A typical screen respnse in this case culd be: Available ptins are: HP Array Cnfiguratin Utility 47

8 16 (current value) 32 64 128 (default) 256 T determine which parameters can be queried, use the help feature f the CLI ("The help cmmand" n page 51). Hiding warning prmpts When yu enter a cmmand fr an peratin that can ptentially destry user data, the CLI displays a warning and prmpts yu fr input (a y r an n) befre cntinuing the peratin. This situatin is undesirable when running batch file scripts. T prevent warning prmpts frm being displayed, use the term frced as a parameter. Example cmmand: ctrl ch="lab4" ld 1 delete frced Under VMware ESXi 5.0, the frced flag is required fr any cmmand that has the ptin fr a frced flag. If the frced parameter is nt used, the system generates an errr message ntifying the user that the cmmand culd nt be cmpleted withut this flag. Keywrd abbreviatins Several cmmnly used keywrds in the ACU CLI have acceptable abbreviatins, as shwn in the fllwing table. Fr a cmplete list f abbreviatins, enter help shrthand in the ACU CLI. Keywrd Abbreviatin in ACU CLI Keywrd adapterid ai nbatterywritecache nbwc allunassigned all numberparitygrups npg arrayacceleratr aa parallelscsi ps cacherati cr physicaldrive pd chassisname* ch* pstprmpttimeut ppt chassisserialnumber csn preferredpathmde ppm chassisslt chs queuedepth qd cnfiguratinmde cm raid1writebuffering r1wb cnnectinname cn rebuildpririty rp cntrller ctrl redundantcntrller rc ctrlpath cp serialnumber sn degradedperfrmancemde dp spareactivatinmde sam drivetype dt ssdphysicaldrive ssdpd drivewritecache dwc stripesize ss elevatrsrt es surfaceanalysiseventntify saen enclsure enc surfacescandelay ssd exitnerrr ee surfacescanmde ssm expandpririty ep sufacescanpririty sp incnsistencyrepairplicy irp surfacescanschedule sss Abbreviatin in ACU CLI HP Array Cnfiguratin Utility 48

Keywrd Abbreviatin in ACU CLI Keywrd licensekey lk tapedrive td lgicaldrive ld waitfrcacherm wfcr mnpdelay mnpd *The CLI als uses this keywrd and abbreviatin fr the terms bx name and RAID array ID. The shw cmmand The shw cmmand enables yu t btain infrmatin abut a device. Syntax: <target> shw [detail] [status] Abbreviatin in ACU CLI When yu specify a target that cnsists f several devices, the infrmatin in the utput is nrmally less cmprehensive than when yu specify nly ne device as the target. Yu can use the [detail] parameter in this case t retain all the infrmatin usually given fr individual devices. An extra parameter is available fr cntrller targets: cnfig. This parameter is used as fllws: <target cntrller> shw cnfig [detail] If yu use the cnfig parameter, the utput includes infrmatin abut each device cnnected t the cntrller. Example 1 => ctrl slt=9 shw A typical utput wuld be: Smart Array P421 in Slt 9 Bus Interface: PCI Slt: 9 Serial Number: PBKTV0XTAZZ005 RAID 6 (ADG) Status: Enabled Cntrller Status: OK Hardware Revisin: A Firmware Versin: 0.02-106 Rebuild Pririty: Medium Expand Pririty: Medium Surface Scan Delay: 3 secs Surface Scan Mde: Idle Queue Depth: Autmatic Mnitr and Perfrmance Delay: 60 min Elevatr Srt: Enabled Degraded Perfrmance Optimizatin: Disabled Incnsistency Repair Plicy: Disabled Wait fr Cache Rm: Disabled Surface Analysis Incnsistency Ntificatin: Disabled Pst Prmpt Timeut: 15 secs Cache Bard Present: True Cache Status: OK HP Array Cnfiguratin Utility 49

Acceleratr Rati: 10% Read / 90% Write Drive Write Cache: Disabled Ttal Cache Size: 1024 MB Ttal Cache Memry Available: 816 MB N-Battery Write Cache: Disabled Cache Backup Pwer Surce: Capacitrs Battery/Capacitr Cunt: 1 Battery/Capacitr Status: OK SATA NCQ Supprted: True Spare Activatin Mde: Activate n drive failure Cntrller Temperature (C): 40 Cache Mdule Temperature (C): 0 Capacitr Temperature (C): 0 Bt Cntrller: True Primary Bt Vlume: lgicaldrive 1 Secndary Bt Vlume: lgicaldrive 1 Example 2 => ctrl all shw Because this target cnsists f several devices, the utput will be brief. A typical utput wuld be: MSA1000 at dg (sn: P56350D9IP903J, csn: (9J3CJN71XDCH, wwn: 500805F3000BAC11) Smart Array 5312 in Slt 3 (sn: P4AB5X9BFMLNTJ) Smart Array 532 in Slt 2 (sn: P44940LDAORS4F) Example 3 => ctrl ch="lab4" shw cnfig The utput in this case will have detailed infrmatin because the target cnsists f nly ne device. A typical utput wuld be: MSA1000 at dg (sn: P56350D9IP903J, csn: (9J3CJN71XDCH, wwn: 500805F3000BAC11) array A (Parallel SCSI, Unused Space: 20091 MB) lgicaldrive 1 (219 MB, RAID 6(ADG), OK) physicaldrive 1:3 (bx 1:bay 3, Parallel SCSI, 4.3 GB, OK) physicaldrive 1:4 (bx 1:bay 4, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:5 (bx 1:bay 5, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:6 (bx 1:bay 6, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:7 (bx 1:bay 7, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:9 (bx 1:bay 9, Parallel SCSI,??? GB, failed, spare) unassigned drive 1:1 (bx 1:bay 1, Parallel SCSI, 36 GB, OK) physicaldrive 1:2 (bx 1:bay 2, Parallel SCSI, 36 GB, OK) physicaldrive 1:8 (bx 1:bay 8, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:10 (bx 1:bay 10, Parallel SCSI, 9.1 GB, OK) HP Array Cnfiguratin Utility 50

physical physicaldrive 1:11 (bx 1:bay 11, Parallel SCSI, 9.1 GB, OK) Displaying the current versins f the applicatin layers The versin cmmand displays the current versins f the applicatin and ther sftware layers. Syntax: versin Example cmmand: versin A typical utput wuld be: ACU CLI Versin: 9.10.16.0 SulAPI Versin: 6.0.15.0 InfManager Versin: 6.1.14.0 The help cmmand T get help with the CLI, enter help at the CLI prmpt, and then enter ne r mre help items, as fllws: => help <item1> [item2] [item3] A help item can be any f the fllwing: A CLI cmmand ("The <cmmand> variable" n page 47) An ACU CLI keywrd r keywrd abbreviatin ("Keywrd abbreviatins" n page 48) A CLI parameter A term cmmnly used in ACU, such as migrate, extend, r cache The wrd shrthand (gives a list f abbreviatins fr keywrds in the CLI) The help feature f the ACU CLI behaves like a brwser search engine in that each item that yu add t the help input string reduces the amunt f help utput text. Fr example, help cntrller prduces extensive infrmatin, while help cntrller remve restricts the help utput t infrmatin abut hw the remve cmmand applies t cntrllers. Typical prcedures The fllwing sectins describe sme cmmn ACU CLI prcedures. Setting the bt cntrller This prcedure is nly available in the ffline envirnment. The bt cntrller is the first cntrller that the system examines (after pwer up) t find a btable lgical drive r vlume. T wrk prperly, the bt cntrller must have a designated bt vlume. See "Setting the bt vlume (n page 52)." Syntax: <target> mdify [btcntrller=enable disable] where <target> is a cntrller with a vlume that can be set as the bt vlume. Example cmmand: cntrller slt=1 mdify btcntrller=enable HP Array Cnfiguratin Utility 51

Setting the bt vlume This prcedure is nly available in the ffline envirnment. The bt vlume is the vlume that cntains the OS and its supprt files. T wrk prperly, the bt vlume must be accessible by the designated bt cntrller. See "Setting the bt cntrller (n page 51)." Syntax: <target> mdify [btvlume=primary secndary nne] where <target> is a cntrller and a lgical drive. Example cmmands: cntrller slt=1 ld 1 mdify btvlume=primary cntrller slt=1 ld 2 mdify btvlume=secndary cntrller slt=1 ld 1 mdify btvlume=nne Setting the target If yu must perfrm several peratins n a given target device, yu can simplify the required cmmands by setting the device as the default <target> fr the CLI peratins. After yu have set the target, any cmmand that yu enter in the CLI withut a specified <target> is autmatically applied t the set target. If yu must als perfrm peratins n ther devices, yu can still d s at any time by specifying the <target> fr each f thse peratins as usual. Yu can als change the set target r clear it cmpletely. The set target is autmatically cleared when yu clse the CLI. IMPORTANT: Yu cannt use the set target cmmand in batch file scripts. Syntax: set target <target> where <target> is a cntrller, array, r lgical drive. Example cmmands: => set target ctrl slt=3 => clear target Typical scenari First, set a target as fllws: => set target ctrl ch="lab 4" => shw target cntrller chassisname="lab 4" As an example f hw the set target cmmand wrks, check the status f array A n this cntrller: => array A shw MSA1000 at Lab 4 array A Interface Type: Parallel SCSI Unused Space: 7949 MB Status: OK Nte that the cntrller des nt need t be specified because it is currently the set target. Nw clear the target, reset it, and enter a few cmmands fr the new set target: => clear target HP Array Cnfiguratin Utility 52

=> set target ctrl slt=3 => array A add drives=1:7,1:8,1:9 => array B add spares=1:10,1:11 => ctrl slt=4 ld 3 mdify ss=64 => mdify rp=high This sequence includes a cmmand fr a different target (the cntrller in slt 4) as a demnstratin. Nte that the next cmmand in the sequence (the ne fr mdifying the rebuild pririty) applies t the cntrller in slt 3, nt the ne in slt 4. This is because the cmmand des nt specify a <target> fr the rebuild pririty, s the default set target is used instead. Identifying devices Yu can enter a cmmand that causes the LEDs n target devices t flash, enabling yu t identify the devices. After an hur, the LEDs stp flashing. Yu can als stp LED flashing by entering the ff cmmand. Syntax: <target> mdify led=n ff Example cmmands: => ctrl ch="lab 4" mdify led=n => ctrl ch="lab 4" array A mdify led=ff Deleting target devices Syntax: <target> delete [frced] where <target> can be a cntrller, array, r lgical drive. Except in the case f cntrllers, yu can delete several devices simultaneusly if they are f similar type by using the all keywrd. Because deleting a target device can result in data lss, the screen displays a warning prmpt unless yu include the frced parameter. Example cmmands: => ctrl ch="lab 4" delete frced => ctrl slt=3 ld all delete Generating a diagnstic reprt HP prvides several ways fr administratrs t generate diagnstic infrmatin, including all three ACU frmats and the standalne HP Array Diagnstics and SmartSSD Wear Gauge Utility. In ACU CLI, the diag cmmand utputs diagnstic infrmatin abut a specified cntrller r all cntrllers n the system. The ssdrpt ptin generates the SmartSSD Wear Gauge reprt. Syntax: <target> diag <file=filename> [ris=n ff] [ssdrpt=n ff] [xml=n ff] [zip=n ff] where the fllwing is designated: <target> is a cntrller r all cntrllers. <file=filename> designates the target file in which the diagnstic infrmatin is saved. [ris=n ff] determines whether RIS infrmatin is r is nt included. The ff value is prvided fr backward cmpatibility and is ignred. HP Array Cnfiguratin Utility 53

[ssdrpt=n ff] specifies t generate r nt generate the Smart SSD Wear Gauge reprt. The default is ff. [xml=n ff] utputs diagnstic infrmatin in frmatted XML. The ff value is prvided fr backward cmpatibility and is ignred. [zip=n ff] cmpresses the utput t a zipped file. Default behavir is uncmpressed. The ff value is prvided fr backward cmpatibility and is ignred. Example cmmands: ctrl all diag file=c:\allcntrllers.zip ctrl slt=4 diag file=c:\ctrl_slt4.zip ctrl ch="mybx" diag file=mybx.zip ssdrpt=n Erasing a physical r lgical drive Syntax: <target> mdify [erase erasepattern=zer randm_zer randm_randm_zer][deleteaftererase=yes n ] where the target can be any valid physical drive r lgical drive. The ptin t delete the target after erasing it is n lnger supprted. Althugh [deleteaftererase=yes n] can still be entered, it is valid nly if the target is a lgical drive, and the lgical drive will always be erased. T stp an erase prcess at any time, enter the stperase cmmand. Example cmmands: => ctrl slt=3 ld 2 mdify erase erasepattern=zer => ctrl slt=4 ld all mdify erase erasepattern=randm_zer => ctrl slt=3 ld 2 mdify stperase Rescanning the system A rescan detects devices that have been added t the system since the previus rescan r since the ACU CLI was started, whichever is mre recent. Syntax: Use the wrd rescan directly at the ACU CLI prmpt, withut any target device r parameters. Example cmmand: => rescan Entering r deleting a license key Sme advanced cnfiguratin tasks (available nly n certain cntrller mdels) can be perfrmed nly after sftware is installed n the cntrller and a license key is registered t activate the sftware. Syntax: <target> add [lk=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx] where the target is any valid cntrller. The hyphens are ptinal. T delete a license key, use a standard delete cmmand but use the license key (nt the cntrller) as the target: <target> delete Example cmmands: => ctrl slt=5 lk=12345-65432-78787-43434-24680 delete HP Array Cnfiguratin Utility 54

=> ctrl slt=4 add lk=9876543210222224444466666 Optimizing cntrller perfrmance fr vide On sme cntrller mdels, yu can ptimize the cntrller perfrmance fr vide. T use this features n an HP Smart Array G6 r G7 cntrller, a registered SAAP ("Abut SAAP" n page 8) license key is required. Syntax: <target> mdify dp=enable elevatrsrt=disable irp=enable queuedepth=autmatic mnpd=60 where the target is any valid cntrller. The queuedepth parameter can als have a numerical value frm 2 t 32, and the mnpd parameter can have any value frm 0 (disabled) t 60. T disable the vide perfrmance ptimizatin feature, reverse the disable and enable values nted abve, set the queue depth t autmatic, and set mnpd t 0, as in the secnd example cmmand. Example cmmands: => ctrl slt=5 mdify dp=enable elevatrsrt=disable irp=enable queuedepth=16 mnpd=25 => ctrl slt=3 mdify dp=disable elevatrsrt=enable irp=disable queuedepth=autmatic mnpd=0 Creating a lgical drive Syntax: <target> create type=ld [parameter=value] <target> is usually a cntrller, but it can be an array if yu are creating an additinal lgical drive n an existing array. If yu want t create a lgical drive n a grup f physical drives that are nt yet assigned t an array, yu d nt have t build the array first. In the CLI, unlike in the GUI, the array is created autmatically at the same time as the lgical drive. The standard parameters used when creating a lgical drive are described in the fllwing table. If yu d nt specify a particular parameter, the CLI uses the apprpriate default value. Parameter Acceptable values Cmments drives [#:]#:#,[#:]#:#,... [#:]#:# [#:]#:# all allunassigned The default setting is all. raid 0 1 1adm 1+0 1+0adm 5 50 6 60? The default setting is the highest RAID level that the cntrller mdel and number f drives can supprt, except 50 r 60 (which must be specified deliberately). numberparityg rups 2 # The default value is 2. ss 8 16 32 64 128 256 512 1024 default? Units are KB.* The default setting depends n the RAID level. HP Array Cnfiguratin Utility 55

Parameter Acceptable values Cmments size # min max maxmbr? This parameter determines the desired size f the lgical drive. Units are MB.* The default setting is max. sectrs 32 63 default? The default setting depends n the perating system. aa enable disable? The default setting is enable. drivetype sas satalgical sata saslgical par allelscsi ss_sas ss_sata? *Use nly these units. D nt enter any extra text in the cmmand t specify the units. If yu specify an array as the target, yu can mit the drives parameter, because the drives are already implicitly defined by the array ID. This feature is useful if yu are entering the cmmand directly int the CLI cnsle because yu d nt need t remember which drives belng t the array. When yu write a batch file, hwever, it is ften easier t specify every drive in the array than t parse ut the array ID. When yu use the drives parameter yu can list each drive individually, yu can specify a drive range, r yu can specify bth a range and sme individual drives. A drive range can span prts, bxes, and bays. If yu specify individual drives, they d nt have t frm a cntinuus sequence. If yu specify a range, the CLI autmatically excludes frm the target any drive in the range that is unavailable (fr example, a drive is excluded if it already belngs t an array, is a spare, has t small a capacity, r has failed). If yu want t specify an existing array by its drives rather than by array ID, then all f the drives that yu specify must belng t the same array, and nne f the drives in the array can be mitted. Example cmmands: ctrl slt=5 create type=ld drives=1:0,1:1,1:3 raid=adg ctrl slt=5 create type=ld drives=1:1-1:3 raid=adg ctrl slt=5 create type=ld drives=1:7,1:10-2:5,2:8-2:12 raid=adg ctrl slt=5 array A create type=ld size=330 raid=adg The fllwing pair f cmmands demnstrates hw the drives parameter can be used in a batch file t create tw lgical drives n the same array, ne f 330 MB and the ther f 450 MB: ctrl slt=2 create type=ld drives=1:1-1:6 size=330 raid=adg ctrl slt=2 create type=ld drives=1:1-1:6 size=450 raid=5 Sample scenari Cnsider a situatin in which yu want t create tw arrays. One f these arrays needs tw lgical drives, while the ther needs nly ne. First, determine what physical drives are available and what their prperties are: => ctrl ch="lab 4" pd all shw Fr this sample scenari, the screen respnse is: MSA1000 at Lab 4 unassigned physicaldrive 1:12 (bx 1:bay12, Parallel SCSI, 36.4 GB, OK) physicaldrive 1:13 (bx 1:bay13, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:14 (bx 1:bay14, Parallel SCSI, 9.1 GB, OK) Knwing this infrmatin, yu can nw create the first array with ne lgical drive: => ctrl ch="lab 4" create type=ld drives=1:12 Nw, verify that the array has been created: HP Array Cnfiguratin Utility 56

=> ctrl ch="lab 4" pd all shw In this case, the screen respnse is: MSA1000 at Lab 4 array A physicaldrive 1:12 (bx 1:bay12, Parallel SCSI, 36.4 GB, OK) unassigned physicaldrive 1:13 (bx 1:bay13, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:14 (bx 1:bay14, Parallel SCSI, 9.1 GB, OK) The secnd array is t be created n the tw remaining physical drives. Befre creating this array, determine what RAID ptins are available fr these drives: => ctrl ch="lab 4" create type=ld drives=1:13,1:14 size=300 raid=? The respnse in this case is: Available ptins are: 0 1+0 (default value) Nw, create the new array: => ctrl ch="lab 4" create type=ld drives=1:13,1:14 size=300 raid=1+0 It is nt strictly necessary t specify the RAID level in this example because it is the highest pssible level fr this scenari and will be used by default. Hwever, it is included in the cmmand as an example. Nw, verify that the array has been frmed: => ctrl ch="lab 4" pd all shw The screen respnse is: MSA1000 at Lab 4 array A physicaldrive 1:12 (bx 1:bay12, Parallel SCSI, 36.4 GB, OK) array B physicaldrive 1:13 (bx 1:bay13, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:14 (bx 1:bay14, Parallel SCSI, 9.1 GB, OK) T create a secnd lgical drive n array B, yu can specify the array (methd A) r yu can specify every physical drive in the array (methd B). => ctrl ch="lab 4" array B create type=ld size=900 (methd A) => ctrl ch="lab 4" create type=ld drives=1:13,1:14 size=900 (methd B) Finally, verify that the lgical drives have all been created crrectly: => ctrl ch="lab 4" ld all shw MSA1000 at Lab 4 array A lgicaldrive 1 (33.9 GB, RAID 0, OK) array B lgicaldrive 2 (298 MB, RAID 1+0, OK) lgicaldrive 3 (896 MB, RAID 1+0, OK) Mving a lgical drive ACU nw enables yu t mve a single lgical drive frm ne array t anther array. This feature is available n Gen8 Smart Array cntrllers. HP Array Cnfiguratin Utility 57

When mving the lgical drive, yu can chse ne f the fllwing destinatins: An existing array A new array yu create T mve a lgical drive t an existing array, use the fllwing infrmatin. Syntax: <target> mdify [newarray=] Cmmand examples: ctrl slt=1 ld 3 mdify newarray=c ctrl slt=1 ld 3 mdify newarray=? // shws the available arrays T mve a lgical drive and create a new array, use the fllwing infrmatin. Syntax: <target> mdify [drives=[#: ]#:#,[#: ]#:#,[#: ]#:# [#: ]#:#,...] Cmmand examples: ctrl slt=1 ld 3 mdify drives=2e:1:1-2e:1:4 ctrl slt=1 ld 3 mdify drives=? // shws the available drives Yu can use the drivetype parameter t specify the drive interface type. When selecting all physical drives, and multiple drive types exist, yu must specify the drive interface type. Mixed drives are nt allwed n the same array r lgical drives. If all drives n a cntrller are the same type, this parameter is nt needed. Fr drivetype, use ne f the fllwing valid ptins: [drivetype=sas satalgical sata saslgical parallelscsi ss_sas ss_sata?] Cmmand examples: cntrller slt=5 ld 1 mdify drives=? drivetype=sas cntrller slt=5 array A mdify drives=? drivetype=ss_sas Viewing enclsure infrmatin The enclsure keywrd is a valid target fr the shw cmmand, and it utputs the strage enclsure infrmatin. Syntax: enclsure [ all prt:bx serialnumber=xxx ] shw [ detail status ] where the target can be any valid strage cntrller. Example cmmands: cntrller slt=5 enclsure all shw cntrller slt=5 enclsure 4E:1 shw detail cntrller slt=5 enclsure serialnumber=uab123456 shw status Viewing physical drives fr an HBA The nnsa keywrd shws the physical drives behind an HBA r "nn-smart array." Syntax: <target> nnsa shw [ssdinf] Cmmand examples: cntrller nnsa shw cntrller nnsa shw ssdinf HP Array Cnfiguratin Utility 58

Viewing SSD physical drives The ssdphysicaldrive keywrd is a valid target fr the shw cmmand, and it utputs the slid state physical drives n the specified cntrller. Syntax: <target> ssdpd all shw [detail] where the target is any valid cntrller. Example cmmands: cntrller slt=5 ssdpd all shw cntrller slt=5 ssdpd all shw detail Viewing SSD infrmatin The ssdinf keywrd prvides a summary fr slid state drives fr the specified cntrller. Syntax: <target> shw ssdinf [detail summary] Cmmand examples: cntrller slt=1 shw ssdinf cntrller all shw ssdinf cntrller all shw ssdinf detail cntrller all shw ssdinf summary Smart Caching in HPACUCLI HP Smart Caching allws a caching lgical drive t be created n a slid state physical drive, t be assciated with an existing data lgical drive t prvide a perfrmance increase. Cmmand Examples: T create a new Smart Caching array fr existing data lgical drive 1 using the slid state drive 1e:1:10: => ctrl slt=1 create type=ldcache drives=1e:1:10 datald=1 The cmmand abve creates a new Smart Caching array, fr example, "array B." Only ne Smart Caching array may exist n a cntrller. This example creates an additinal caching lgical drive using the existing Smart Caching array fr existing data lgical drive 2: => ctrl slt=1 array B create type=ldcache datald=2 Rapid Parity Initializatin methds RAID levels that use parity (RAID 5, RAID 6 (ADG), RAID 50, and RAID 60) require that the parity blcks be initialized t valid values. Valid parity data is required t enable enhanced data prtectin thrugh backgrund surface scan analysis and higher perfrmance write peratins. Tw initializatin methds are available: Default Initializes parity blcks in the backgrund while the lgical drive is available fr access by the perating system. A lwer RAID level results in faster parity initializatin. Rapid Overwrites bth the data and parity blcks in the fregrund. The lgical drive remains invisible and unavailable t the perating system until the parity initializatin prcess cmpletes. All parity grups are initialized in parallel, but initializatin is faster fr single parity grups (RAID 5 and RAID 6). RAID level des nt affect system perfrmance during rapid initializatin. HP Array Cnfiguratin Utility 59

Rapid Parity Initializatin is available nly fr supprted cntrllers and in arrays cmpsed f supprted physical drives. Example: f creating a lgical drive with Rapid Parity Initializatin: => ctrl slt=3 create type=ld drives=1e:1:1-1e:1:4 parityinitializatinmethd=rapid Assigning a chassis name t the cntrller If a cntrller is cnfigured with at least ne lgical drive, yu can give the cntrller a simplified name (the chassis name) t make it easier t identify and enter the crrect cntrller in a cmmand. Syntax: <target> mdify ch="new chassis name" where <target> is a cntrller. If yu change the chassis name f a cntrller that yu have set as the default target ("Setting the target" n page 52), yu must reset the target. Example cmmands: => ctrl sn=p56350d9ip903j mdify ch="lab 6" => ctrl ch="lab 4" mdify ch="lab 6" Managing spare drives Assigning ne r mre nline spare drives t an array enables yu t pstpne replacement f faulty drives. Hwever, it des nt increase the fault-tlerance level f any lgical drives in the array. Fr example, a lgical drive in a RAID 5 cnfiguratin suffers irretrievable data lss if tw f its physical drives are simultaneusly in a failed state, regardless f the number f spare drives assigned t the array. Any drive that yu want t use as a spare must meet the fllwing criteria: It must be an unassigned drive r a spare fr anther array. It must be f the same type as existing drives in the array (fr example, SATA r SAS). It must have a capacity n less than that f the smallest drive in the array. Syntax: <target> add spares=[#:]#:#,[#:]#:#,[#:]#:# [#:]#:#,... allunassigned [frced] <target> remve spares=[#:]#:#,[#:]#:#,[#:]#:# [#:]#:#,... all where <target> is an array (r lgical drive, if the array cntains nly ne lgical drive). The frced parameter represses any warning message prmpts. If yu specify a drive range, any drives in the range that d nt meet the previus criteria are nt used. Example cmmands: => ctrl slt=3 array B add spares=1:6 => ctrl slt=4 array all add spares=1:5,1:7 => ctrl slt=5 array A add spares=1:1 1:5 => ctrl slt=5 array A remve spares=1:1 1:5 Setting the spare activatin mde The spare activatin mde feature enables the cntrller firmware t activate a spare drive under the fllwing cnditins: When a data drive reprts a predictive failure (SMART) status HP Array Cnfiguratin Utility 60

When a data drive fails; this mde is the default. In nrmal peratins, and fr lder cntrllers, the firmware starts rebuilding a spare drive nly when a data drive fails. With the predictive failure activatin mde, rebuilding can begin befre the drive fails, reducing the likelihd f data lss that culd ccur if an additinal drive fails. Use the spareactivatinmde keywrd t tggle the spare activatin mde fr the cntrller between drive failure and drive predictive failure. Syntax: <target> mdify spareactivatinmde=[ failure predictive ] Example cmmands: cntrller slt=1 mdify spareactivatinmde=predictive cntrller slt=1 mdify spareactivatinmde=failure Spare Management Mde in HPACUCLI The sparetype keywrd allws yu t specify the spare type as "dedicated" (default) r "autreplace." A dedicated spare temprarily takes ver fr a failed drive and can be shared between arrays. An autreplace spare replaces a failed drive and cannt be shared between arrays. Cmmand example: T add a spare with spare type f autreplace: => ctrl slt=1 array A add spares=1e:1:5 sparetype=autreplace Expanding an array Yu can increase the strage space n an array by adding physical drives. Any drive that yu want t add must meet the fllwing criteria: It must be an unassigned drive. It must be f the same type as existing drives in the array (fr example, SATA r SAS). It must have a capacity n less than that f the smallest drive in the array. IMPORTANT: An array expansin, lgical drive extensin, r lgical drive migratin takes abut 15 minutes per gigabyte. While this prcess is ccurring, n ther expansin, extensin, r migratin can ccur simultaneusly n the same cntrller. Cntrllers that d nt supprt a battery-backed write cache d nt supprt this prcess. Syntax: <target> add drives=[#:]#:#,[#:]#:#,[#:]#:# [#:]#:#,... allunassigned [frced] where <target> is an array (r a lgical drive, if the array cntains nly ne lgical drive). The frced parameter represses any warning message prmpts. If yu specify a drive range, any drives in the range that d nt meet the previus criteria are nt used. If yu add an dd number f drives t an array that cntains a RAID 1+0 lgical drive, yu are prmpted t cnvert the RAID 1+0 lgical drive t RAID 5 r RAID 6 (ADG). Adding the frced parameter t the cmmand prevents this prmpt frm appearing. Example cmmands: => ctrl slt=3 array A add drives=1:0,1:1 => ctrl slt=4 ld 1 add drives=allunassigned => ctrl slt=5 array A add drives=1:1 1:5 HP Array Cnfiguratin Utility 61

Shrinking an array Sme cntrllers may nt supprt this ptin r may require a license key t enable this feature. Yu can shrink the size f an array by remving a drive frm an existing array. Observe the fllwing criteria: After the shrink, the array must have sufficient capacity t cntain all f the cnfigured lgical vlumes. Yu may nt remve drives frm the array if the resulting number f drives des nt supprt the fault tlerance (RAID level) f any existing lgical drive. Fr example, if yu have an array with fur physical drives and a RAID 5 lgical drive, yu can remve, at mst, ne drive, because RAID 5 requires at least three physical drives. If the array cntains a RAID 1+0 lgical drive, yu can remve nly an even number f drives. If the array cntains a cmpund RAID (RAID 50 r RAID 60) lgical drive, yu can remve drives nly in multiples f the number f parity grups. Fr example, an array with 10 physical drives and a RAID 50 lgical drive can be shrunk by remving tw r fur drives nly. Syntax: <target> remve drives=[#:]#:#-[#:]#:# where <target> is an array, and the specified physical drives are being remved t shrink the array. Fr example, in an existing array (array a), six drives (1e:1:4-1e:1:9) are in use. With all criteria met, yu can shrink the array t fur drives by remving the last tw drives with the cmmand: <array a> remve drives=1e:1:8-1e:1:9 Example cmmands: => array a remve drives=1e:1:12-1e:1:14 => array b remve drives=1c:1:6-1c:1:7 Mving an array Sme cntrllers may nt supprt this ptin r may require a license key t enable this feature. Yu can mve an array by designating different physical drives fr the array. T mve the array, each f the physical drives where the array will reside must meet the fllwing criteria: It must be an unassigned drive. It must be f the same type as the physical drives currently in the surce array (fr example, SATA r SAS). The destinatin drives must have sufficient capacity t hld all the lgical drives present in the surce array. Like array creatin and expansin, the useable space in all drives is reduced t the size f the smallest physical drive in the destinatin disk set. Mving an array autmatically remves any previusly assigned spare drives. If spares are assigned t the existing array, they must be designated fr the array when it is mved. Syntax: <target> mdify drives=[#:]#:#-[#:]#:# spares=[#:]#:#-[#:]#:# where <target> is an array, and the specified physical drives are the new destinatin fr the array. Fr example, in an existing array, three 72-GB SAS drives (1e:1:4-1e:1:6) are the surce. Anther drive f the same size is the spare (1e:1:9). With all criteria met, yu can mve the array t three different 72-GB SAS HP Array Cnfiguratin Utility 62

drives by specifying the new destinatin drives in the cmmand (1e:1:12-1e:1:14). T maintain the same spare drive, be sure t designate the spare drive fr the mved array. Example cmmands: => array a mdify drives=1e:1:12-1e:1:14 spares=1e:1:9 => array b mdify drives=1c:1:6-1c:1:7 Replacing an array Sme cntrllers may nt supprt this ptin r may require a license key t enable this feature. Yu can replace an array by designating different physical drives fr the array. T replace the array, each f the physical drives where the array will reside must meet the fllwing criteria: The destinatin drives must all be the same type (fr example, SATA r SAS), but d nt have t be same type as the drives in the surce array. A destinatin drive des nt have t be an unassigned drive, but if it is assigned, it must be a drive assigned t the array being replaced. The destinatin drives must have sufficient capacity t hld all the lgical drives present in the surce array. Like array creatin and expansin, the useable space in all drives is reduced t the size f the smallest physical drive in the destinatin disk set. Replacing an array autmatically remves any previusly assigned spare drives. If spares are assigned t the existing array, they must be designated fr the array when it is mved. Syntax: <target> mdify drives=[#:]#:#-[#:]#:# spares=[#:]#:#-[#:]#:# where <target> is an array, and the specified physical drives are the new destinatin fr the array. Fr example, in an existing array, three 72-GB SAS drives (1e:1:4-1e:1:6) are the surce. Anther drive f the same size is the spare (1e:1:9). With all criteria met, yu can mve the array t three different 72-GB SAS r SATA drives by specifying the new destinatin drives in the cmmand (1e:1:12-1e:1:14). T maintain the same spare drive, be sure t designate the spare drive fr the mved array. Example cmmands: => array a mdify drives=1e:1:12-1e:1:14 spares=1e:1:9 => array b mdify drives=1c:1:6-1c:1:7 Extending a lgical drive If the perating system supprts lgical drive extensin, yu can use any unassigned capacity n an array t enlarge ne r mre f the lgical drives n the array. IMPORTANT: An array expansin, lgical drive extensin, r lgical drive migratin takes abut 15 minutes per gigabyte. While this prcess is ccurring, n ther expansin, extensin, r migratin can ccur simultaneusly n the same cntrller. Cntrllers that d nt supprt a battery-backed write cache d nt supprt this prcess. Syntax: <target> mdify size=# max? [frced] where <target> is a lgical drive. HP Array Cnfiguratin Utility 63

If the perating system des nt supprt lgical drive extensin, carrying ut this cmmand makes data n the lgical drive unavailable. Therefre, the CLI displays a warning prmpt as a safeguard in case yu are using such an perating system. T prevent the prmpt frm appearing, use the frced parameter. Example cmmands: => ctrl slt=3 ld 1 mdify size=max => ctrl slt=4 ld 1 mdify size=? => ctrl slt=3 ld 2 mdify size=500 frced Migrating a lgical drive This cmmand enables yu t adjust the stripe size (data blck size) r RAID level f a selected lgical drive. Fr mre infrmatin, see "Selecting a RAID methd (n page 113)." Cnsider the fllwing factrs befre perfrming a migratin: Fr sme RAID-level migratins t be pssible, yu might need t add ne r mre drives t the array. Fr migratin t a larger stripe size t be pssible, the array might need t cntain unused drive space. This extra space is necessary because sme f the larger data stripes in the migrated array are likely t be filled inefficiently. IMPORTANT: An array expansin, lgical drive extensin, r lgical drive migratin takes abut 15 minutes per gigabyte. While this prcess is ccurring, n ther expansin, extensin, r migratin can ccur simultaneusly n the same cntrller. Cntrllers that d nt supprt a battery-backed write cache d nt supprt this prcess. Syntax: <target> mdify [raid=0 1+0 1 5 6 adg?] [ss=8 16 32 64 128 256 default?] where <target> is a lgical drive. The fllwing limitatins apply t this cmmand: Yu cannt simultaneusly query the RAID level and the stripe size f any given lgical drive. If yu d nt specify a RAID level fr a query r migratin, the CLI uses the existing value by default. If yu d nt specify a stripe size, the CLI uses the default stripe size value fr the RAID level that yu specify. Example cmmands: => ctrl slt=3 ld 1 mdify raid=1 => ctrl slt=4 ld 2 mdify ss=16 => ctrl slt=2 ld 3 mdify raid=5 ss=16 Setting the preferred path mde The preferred path mde determines hw I/O traffic t the lgical drives is managed n cntrllers that are in an active/active cnfiguratin. In Autmatic mde, the strage system autmatically selects a suitable path fr I/O traffic t each lgical drive depending n the hst I/O patterns at the time. Because the ptimum path can vary with time, I/O traffic fr any given lgical drive can be directed thrugh either cntrller. In Manual mde, all I/O traffic t a given lgical drive is directed thrugh a designated cntrller. In this case, yu must als specify the preferred cntrller fr each lgical drive ("Assigning a redundant cntrller t a lgical drive" n page 65). Syntax: HP Array Cnfiguratin Utility 64

<target> mdify [preferredpathmde=autmatic manual?] where <target> is a redundant cntrller. Example cmmand: cntrller ch="lab 3" mdify ppm=manual Assigning a redundant cntrller t a lgical drive When yu have set the preferred path mde ("Setting the preferred path mde" n page 64) in a redundant system t Manual, yu must use the chassisslt cmmand t assign each lgical drive in the system t ne f the redundant cntrllers. Syntax: <target> mdify [chassisslt=#?] where <target> is a valid lgical drive n a cntrller that is in an active/active cnfiguratin and # dentes the chassis slt number f the redundant cntrller. (T btain the chassis slt number, use the shw cmmand n the cntrller.) Example cmmand: cntrller ch="lab 3" ld 1 mdify chs=2 Disabling a redundant cntrller This cmmand disables a redundant cntrller that is in an Active-Standby cnfiguratin. IMPORTANT: The redundant cntrller cannt be re-enabled after yu have disabled it. Syntax: <target> mdify redundantcntrller=disable where <target> is a cntrller that has an enabled redundant cntrller. Example cmmand: => ctrl ch="redundant Lab4" mdify rc=disable Changing the Rebuild Pririty setting The Rebuild Pririty setting determines the urgency with which the cntrller treats an internal cmmand t rebuild a failed lgical drive. At the lw setting, nrmal system peratins take pririty ver a rebuild. At the medium setting, rebuilding ccurs fr half f the time, and nrmal system peratins ccur fr the rest f the time. At the high setting, the rebuild takes precedence ver all ther system peratins. If the lgical drive is part f an array that has an nline spare, rebuilding begins autmatically when drive failure ccurs. If the array des nt have an nline spare, rebuilding begins when the failed physical drive is replaced. Syntax: <target> mdify rp=high medium lw? where <target> is a cntrller. Example cmmand: HP Array Cnfiguratin Utility 65

=> ctrl slt=3 mdify rp=high Changing the Expand Pririty setting The Expand Pririty setting determines the urgency with which the cntrller treats an internal cmmand t expand an array. At the lw setting level, nrmal system peratins take pririty ver an array expansin. At the medium setting, expansin ccurs fr half f the time, and nrmal system peratins ccur fr the rest f the time. At the high setting, the expansin takes precedence ver all ther system peratins. Syntax: <target> mdify ep=high medium lw? where <target> is a cntrller. Example cmmand: => ctrl slt=3 mdify ep=high Setting the surface scan mde The surfacescanmde keywrd sets the surface mde fr the cntrller. The available mdes are disable, high, r idle. If yu specify the idle mde, yu must als specify a surface scan delay value. Syntax: <target> mdify [ surfacescanmde=disable idle high? ] Example cmmands: cntrller slt=1 mdify surfacescanmde=high cntrller slt=1 mdify surfacescanmde=disable cntrller slt=1 mdify surfacescanmde=idle surfacescandelay=3 Changing the surface scan delay time The setting fr the surface scan delay determines the time interval fr which a cntrller must be inactive befre a surface scan analysis is started n the physical drives that are cnnected t it. Surface scan analysis is an autmatic backgrund prcess that ensures that yu can recver data if a drive failure ccurs. The scanning prcess checks physical drives in fault-tlerant lgical drives fr bad sectrs, and in RAID 5 r RAID 6 (ADG) cnfiguratins, it als verifies the cnsistency f parity data. Syntax: <target> mdify ssd=# where <target> is a cntrller and # is a number between 1 and 30. This number determines the delay time in secnds, but yu d nt need t include units with the cmmand. Example cmmand: => ctrl sn=p56350d9ip903j mdify ssd=3 Re-enabling a failed lgical drive If a lgical drive has failed and the data n it is invalid r nn-recverable, yu can re-enable the lgical drive s that it can be reused. This prcess preserves the structure f the lgical drive and merely deletes data, whereas a delete cmmand applied t a lgical drive deletes the lgical drive structure as well as the data. HP Array Cnfiguratin Utility 66

Syntax: <target> mdify reenable [frced] Example cmmand: => ctrl slt=3 ld 1 mdify reenable frced Changing the cntrller cache rati The cntrller cache rati setting determines the amunt f memry allcated t read and write peratins. Different types f applicatins have different ptimum settings. Yu can change the rati nly if the cntrller has a battery-backed cache (because nly battery-backed cache can be used fr write cache) and if there are lgical drives cnfigured n the cntrller. Syntax: <target> mdify cr=#/#? where <target> is a cntrller, and #/# is the cache rati in the frmat read percentage/write percentage. Example cmmand: => ctrl slt=3 mdify cr=25/75 Enabling r disabling the drive cache On cntrllers and drives that supprt physical drive write cache, yu can use this cmmand t enable r disable the write cache fr all drives n the cntrller. CAUTION: Because physical drive write cache is nt battery-backed, yu culd lse data if a pwer failure ccurs during a write prcess. T minimize this pssibility, use a backup pwer supply. Syntax: <target> mdify drivewritecache=enable disable? [frced] where <target> is a cntrller that supprts drive write cache. Example cmmand: => ctrl slt=5 mdify dwc=enable Enabling r disabling the array acceleratr If the cntrller has an array acceleratr, yu can disable r enable it fr specified lgical drives. NOTE: Disabling the array acceleratr fr a lgical drive reserves use f the acceleratr cache fr ther lgical drives n the array. This feature is useful if yu want the ther lgical drives t have the maximum pssible perfrmance (fr example, if the lgical drives cntain database infrmatin). Syntax: <target> mdify aa=enable disable? where <target> is a lgical drive. Example cmmand: => ctrl slt=3 ld 1 mdify aa=enable HP Array Cnfiguratin Utility 67

Enabling a script t exit n errr When a script encunters an errr during executin, the exitnerrr keywrd enables the script t decide whether t cntinue r t exit the applicatin and return an exit cde. Syntax: set [exitnerrr=enable disable] Example cmmands: set exitnerrr=enable set ee=disable shw exitnerrr Using ACU scripting Access ACU with ne f the many methds available: Accessing ACU in the ffline envirnment (n page 10) Accessing ACU in the nline envirnment (n page 15) The ACU Scripting applicatin has tw scripting mdes: Capture mde fr capturing a cnfiguratin (n page 68) ACU inspects the cnfiguratin f all internal and external array cntrllers cnnected t the server and then writes a script file describing this cnfiguratin. Input mde fr using an Input script (n page 68) ACU reads the array cnfiguratin described in a specified script file. See "Creating an ACU script file (n page 69)." ACU then applies this cnfiguratin t a target system. Capturing a cnfiguratin T capture the cnfiguratin f a system, enter the fllwing cmmand at the system cmmand line prmpt: hpacuscripting -c [drive:][path]outputfilename.ext [-internal -external] -e [drive:][path]errorfilename.ext OUTPUTFILENAME is the name f the capture file, and ext. is the file extensin. If yu d nt specify a name and lcatin fr this file, ACU uses the default name ACUOUTPUT.ini, and places the file in the ACU wrking directry. The -internal and -external switches limit capture t internal r external cntrllers. The -e switch infrmatin is used nly if ACU must generate an errr file. By default, ACU names the errr file ERROR.ini and places it in the ACU wrking directry. Using an Input script T use an Input script t cnfigure r recnfigure a system, first lcate a suitable ACU script r see "Creating an ACU script file (n page 69)." Then, enter the fllwing cmmand at the system cmmand line prmpt: hpacuscripting -i [drive:][path]filename.ext [-internal -external] [-reset] -e [drive:][path]errorfilename.ext HP Array Cnfiguratin Utility 68

FILENAME is the name f the ACU input file, and ext is the file extensin. If yu d nt specify the name and lcatin f this file, ACU searches fr ACUINPUT.ini in the ACU wrking directry. The -internal and -external switches limit cnfiguratin peratins t internal r external cntrllers. The -reset flag destrys any existing data and verwrites the current cnfiguratin with the cnfiguratin specified in the script. The -e switch infrmatin is used nly if ACU must generate an errr file. By default, ACU names the errr file ERROR.ini and places it in the ACU wrking directry. Creating an ACU script file T create a valid ACU script file, use ne f the fllwing methds: Mdify the sample custm input script (n page 69). Create a Capture file fr capturing a cnfiguratin (n page 68). Yu can create a capture file frm any server that has ACU laded, and then mdify the values f ptins in the file as necessary fr the target system. This methd is useful fr applying a standard cnfiguratin t several servers that have similar strage resurces. Write an riginal script. Each line f text in an ACU script file is in the frmat ptin=value and can be written in uppercase r lwercase letters. Fr infrmatin abut pssible ptin values and the minimum cnfiguratin infrmatin that a valid script must have, see the sample custm input script (n page 69). Yu can add blank lines and cmments t any script t make it easier t read and understand. T create a cmment, enter a semicln, and then enter the cmment text. ACU ignres all text n the same line after a semicln. Sample custm input script The sample script in this sectin gives all pssible values fr each ptin. If an ptin is shwn in bld type, yu must enter a value fr that ptin when writing yur wn script. If a value is shwn in bld type, ACU uses that value as a default setting when creating new lgical drives. Yu can use this script as a template fr yur wn script. Actin = Cnfigure Recnfigure Methd = Custm Aut ; COMMENT: ACU cannt create a RAID 50 r RAID 60 cnfiguratin in Aut mde. Yu must create such cnfiguratins manually using the Custm setting. Cntrller = All First Slt [N][:N] WWN [N] SerialNumber [N] IOCabinet [N],IOBay [N],IOChassis [N],Slt [N],Cabinet [N],Cell [N] ClearCnfiguratinWithDataLss = Yes N ; COMMENT: This ptin is nw deprecated. LicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX DeleteLicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX * ; COMMENT: * is a wild card that enables yu t delete all license keys n the specified cntrller. RAIDArrayID = XXXXXXXXXXXXXXXXXXXX HP Array Cnfiguratin Utility 69

ReadCache = 0 10 20 25 30 40 50 60 70 75 80 90 100 WriteCache = 0 10 20 25 30 40 50 60 70 75 80 90 100 RebuildPririty = Lw Medium High ExpandPririty = Lw Medium High SurfaceScanDelay = N PreferredPathMde = Aut Manual ; COMMENT: the fllwing five entries are used t ptimize the cntrller perfrmance fr vide MNPDelay = 0 1 2... 60 ; units are minutes, zer indicates disabled IRPEnable = Yes N DPOEnable = Yes N ElevatrSrtEnable = Yes N QueueDepth = 2 4 8 16 32 Aut Array = A B C D E F G...Z a b c d e f OnlineSpare = Nne N Prt:ID,Prt:ID... Bx:Bay,Bx:Bay... Prt:Bx:Bay,Prt:Bx:Bay,... ; COMMENT: These values are available nly in Custm methd mde. In Aut methd mde, the chices are Yes N. Drive = * N Prt:ID,Prt:ID... Bx:Bay,Bx:Bay... Prt:Bx:Bay,Prt:Bx:Bay,... DriveType = SCSI SAS SATA LgicalDrive = 1 2 3...32 RAID = 0 1 5 50 6 60 adg aut ; COMMENT: Fr HP Smart Array G6 and G7 cntrllers, RAID 6 and 60 are nly available when SAAP is installed and the license key registered. ParityGrups = 2 N ; COMMENT: Necessary nly fr RAID 50 r 60. N > 2 Size = [N] Max Sectrs = 32 63 StripeSize = 8 16 32 64 128 256 ArrayAcceleratr = Enable Disable PreferredPath = 1 2 HBA_WW_ID = WWN CnnectinName = UserDefinedName HstMde = Default Windws Windws(degrade penvms Tru64 Linux Slaris Netware HP Windws Sp2 ; COMMENT: The Windws(degrade value must be entered as written. Script file ptins Optins in ACU script files are divided int the fllwing categries: HP Array Cnfiguratin Utility 70

Cntrl categry (n page 72) Cntrller categry (n page 72) Array categry (n page 76) Lgical Drive categry (n page 78) HBA categry (n page 83) Each categry has several scripting ptins, but yu d nt always need t assign values t every ptin. ACU can use default values in sme instances, while in ther instances, a listed ptin might nt be relevant fr a particular cnfiguratin r scripting mde. The ptins fr each categry are listed in the fllwing table and described in mre detail in the remainder f this sectin. Categry Optins Descriptin Cntrl Cntrller Array Actin Methd Cntrller CacheState ClearCnfiguratinWithDataLss DeleteLicenseKey DPOEnable DriveWriteCache ElevatrSrtEnable ExpandPririty IRPEnable LicenseKey MNPDelay NBatteryWriteCache PreferredPathMde QueueDepth RaidArrayId ReadCache RebuildPririty SurfaceScanDelay SurfaceScanDelayExtended SurfaceScanMde WriteCache Array Drive DriveType Jin OnlineSpare Split These ptins define the verall behavir f ACU when it prcesses scripts and creates cnfiguratins. Cntrl ptins can ccur nly nce in a script file and must be listed first. Optins in this categry specify the cntrller that is t be cnfigured (r the cntrller that had its cnfiguratin captured). Althugh the Cntrller ptin must begin this sectin f the script, yu can script ther ptins in this categry in any rder. Yu can use ne script file t cnfigure all cntrllers in a system, and yu can cnfigure the cntrllers identically r individually. If yu define each cntrller cnfiguratin individually, enter the ptin values fr ne cntrller and its arrays and lgical drives befre specifying the ptin values fr anther cntrller. These ptins describe an array that is t be cnfigured n the cntrller that was previusly specified in the script. (If n cntrller was previusly specified, ACU stps prcessing the script and creates an errr file.) Althugh the Array ptin must begin this sectin f the script, yu can script the ther ptins in this categry in any rder. HP Array Cnfiguratin Utility 71

Categry Optins Descriptin Lgical Drive ArrayAcceleratr LgicalDrive NumberOfParityGrups PreferredPath RAID Renumber Repeat ResurceVlumeOwner Sectrs ShrinkSize Size SizeBlcks StripSize StripeSize HBA CnnectinName HBA_WW_ID HstMde These ptins describe a lgical drive that is t be cnfigured n an array that was previusly specified in the script. (If n array was previusly specified, ACU stps prcessing the script and creates an errr file.) Althugh the LgicalDrive ptin must begin this sectin f the script, yu can script the ther ptins in this categry in any rder. These ptins specify an HBA that is t be cnfigured. Cntrl categry The Cntrl categry has the fllwing ptins: Actin mde (n page 72) Methd mde (n page 72) Actin mde Yu must specify an Actin mde: In Cnfigure mde, yu can create new arrays, but yu cannt mdify existing arrays. The cntrller must be cnnected t unassigned physical drives fr this mde t be available. In Recnfigure mde, yu can mdify existing arrays. Fr example, yu can set up an array expansin, a lgical drive extensin, r a migratin. These prcedures d nt destry data, unless yu specifically want the data t be deleted. In this mde, ACU des nt change an existing ptin setting unless yu specifically script a different value fr that ptin. If yu use the -reset cmmand line switch, the existing cntrller cnfiguratin is cleared with data lss as the first step in the cnfiguratin prcess. This cmmand line switch is nt cmpatible with Recnfigure mde. Methd mde The default value fr this ptin is Aut. If yu want t use Custm mde, yu must specify it. In Aut mde, ACU can perfrm an expansin, extensin, r migratin withut user interventin if the values that yu set fr ther ptins imply that such an peratin is necessary. Cntrller categry The Cntrller categry has the fllwing ptins: Cntrller (n page 73) CacheState (n page 73) HP Array Cnfiguratin Utility 72

ClearCnfiguratinWithDataLss (n page 74) DeleteLicenseKey ("LicenseKey, DeleteLicenseKey" n page 74) DPOEnable ("Vide perfrmance ptins" n page 75) DriveWriteCache (n page 74) ElevatrSrtEnable ("Vide perfrmance ptins" n page 75) ExpandPririty ("RebuildPririty, ExpandPririty" n page 75) IRPEnable ("Vide perfrmance ptins" n page 75) LicenseKey ("LicenseKey, DeleteLicenseKey" n page 74) MNPDelay ("Vide perfrmance ptins" n page 75) NBatteryWriteCache (n page 74) PreferredPathMde (n page 74) QueueDepth ("Vide perfrmance ptins" n page 75) RaidArrayId (n page 74) ReadCache ("ReadCache, WriteCache" n page 75) RebuildPririty ("RebuildPririty, ExpandPririty" n page 75) SurfaceScanDelay (n page 75) SurfaceScanDelayExtended (n page 75) WriteCache ("ReadCache, WriteCache" n page 75) Cntrller Yu must enter a value fr this ptin because it identifies the cntrller that yu want t cnfigure: All Cnfigure all detected cntrllers in the system. First Cnfigure the first cntrller fund, based n the cntrller with the lwest PCI slt number. Internal cntrllers are used befre external cntrllers. The -internal and -external cmmand line switches influence what ACU regards as the First cntrller. Fr example, if yu use the -external switch, the First cntrller is the first external cntrller discvered, regardless f the number f internal cntrllers in the hst system. Slt [N][:M] Cnfigure the internal cntrller in slt number N, r the external cntrller at prt M in slt N. WWN [N] Cnfigure the external cntrller that has the Wrld Wide Name N. SerialNumber [N] Cnfigure the shared strage cntrller that has serial number N. IOCabinet[N],IOBay[N],IOChassis[N],Slt[N],Cabinet[N],Cell[N] Cnfigure the cntrller in the Integrity server that has the slt path infrmatin defined by this sequence f identifiers. CacheState This ptin enables yu t flush the cache r disable flushing f the cache. Values are FlushEnable and FlushDisable. HP Array Cnfiguratin Utility 73

Yu can use this ptin t prevent stale cache issues. ClearCnfiguratinWithDataLss Clearing the cnfiguratin causes data lss because it deletes all lgical vlumes and arrays n the cntrller. If yu clear a cnfiguratin, yu can write cmmands later in the script file t create a new cnfiguratin frm the liberated drive capacity. The values fr this ptin are Yes r N. The default value is N. DriveWriteCache This ptin cntrls the settings f the write cache fr all cnnected physical disks. Fr this ptin, the setting is Enable r Disable. Nt all physical disks r cntrllers supprt this ptin. LicenseKey, DeleteLicenseKey These ptins enable yu t enter a 25-character license key t activate r uninstall sme cntrller features. Hyphens can be entered, but are nt required. NBatteryWriteCache With this ptin, the cntrller can enable write cache when n battery is present r when the battery fails. Values are Enable r Disable. The default is Disable. Sme cntrllers d nt supprt this ptin. PreferredPathMde The setting that yu select fr this ptin determines hw the preferred I/O path t a particular lgical drive is set fr a redundant array cntrller that is in an active/active cnfiguratin. Nt all cntrllers supprt this feature, and cntrllers in an active/standby cnfiguratin disregard this ptin. Aut is the default setting fr new cnfiguratins. In this case, the strage system autmatically selects the I/O path frm the redundant cntrller t the lgical drive and dynamically lad balances all paths. Manual enables yu t assign the lgical drive t a specific redundant cntrller. If yu select this setting, use the PreferredPath (n page 80) cmmand t specify the path. If yu are recnfiguring a cntrller and d nt specify a setting fr this ptin, the existing setting remains unchanged. RaidArrayId This ptin specifies the RaidArrayId fr cntrllers that supprt this feature, such as fibre and shared strage cntrllers. The RaidArrayId is a user-defined string that identifies cntrllers. "XXXXXXXXXXXXXXXXXXXX" The value can be a string f varying length that cnsists f any f the fllwing characters: a-z A-Z 0-9! @ # * ( ), - _ + :. / [space] This string cannt end in a space character. This string has a maximum length that varies depending n the type f cntrller. Fr RA4x00 cntrllers, the maximum length is 24 characters. Fr ther cntrllers, the maximum length is 20 characters. HP Array Cnfiguratin Utility 74

The qutes enclsing the string are ptinal. The qutes allw yu t use leading space characters in the RaidArrayId. ReadCache, WriteCache Enter a number between 0 and 100 t specify the percentage f cache that is t be allcated t drive reads r writes. The default value fr bth ptins is 50, unless the cntrller firmware supplies a specific default read/write rati. The allwable cache ratis depend n the cntrller mdel and whether it has battery-backed write cache. RebuildPririty, ExpandPririty These ptins establish the pririty fr rebuild and expand functins. Each ptin has three pssible values: Lw, Medium, and High. These ptins are nt required. SurfaceScanDelay Enter a number between 0 and 30 t specify the duratin f the surface scan delay in secnds. This ptin is nt required. If yu d nt specify a value fr this ptin, the delay remains unchanged. A value f 0 disables the scan. SurfaceScanDelayExtended Enter a number between 0 and 300 t specify the duratin f the surface scan delay in tenths f secnds. This ptin is nt required. If yu d nt specify a value fr this ptin, the delay remains unchanged. A value f 0 disables the scan. If this parameter and SurfaceScanDelay are bth in the input file, this parameter takes precedence. SurfaceScanMde This parameter specifies the Surface Scan Mde with the fllwing values: Idle The delay interval is set with the nrmal values frm SurfaceScanDelay r SurfaceScanDelayExtended. High The surface scan enters a mde guaranteed t make prgress despite the level f cntrller I/O. Disabled N mde is selected. Vide perfrmance ptins T use this features n an HP Smart Array G6 r G7 cntrller, a registered SAAP ("Abut SAAP" n page 8) license key is required. T ptimize the cntrller perfrmance fr vide, set values fr the fllwing ptins as indicated: DPOEnable = N ElevatrSrtEnable = Yes IRPEnable = N In additin: Set the MNPDelay t any integer value frm 1 t 60 (units are minutes). If yu want t disable this ptin, set a value f zer instead. HP Array Cnfiguratin Utility 75

Set the QueueDepth t ne f the fllwing values: Array categry 2 4 8 16 32 Autmatic The Array categry has the fllwing ptins: Array (n page 76) CachingArray (n page 76) Drive (n page 76) DriveType (n page 77) Jin (n page 77) OnlineSpareMde (n page 77) OnlineSpare (n page 78) Split (n page 78) Array Enter a letter r pair f letters t identify the array that is t be created r recnfigured, and bserve these additinal limitatins: In Cnfigure mde, ACU creates a new array. The value that yu specify fr the array ptin must be the next available letter r pair f letters in the sequence, accrding t the number f existing arrays n the cntrller. AA fllws Z, and BA fllws AZ. In Recnfigure mde, ACU can either create a new array r recnfigure an existing array. In this case, the value that yu specify can identify an existing array, r it can crrespnd t the next available array letter r pair f letters in the existing cnfiguratin. CachingArray This ptin specifies the Caching Array ID. In Cnfigure mde, ACU creates a new caching array. The value that yu specify fr the array ptin must be the next available array letter in the existing cnfiguratin. AA fllws Z, and BA fllws AZ. In Recnfigure mde, the array letter identifies an existing array, r it can identify the next available array letter in the existing cnfiguratin t create a new array. Drive Yu can use this ptin in the input file t specify new physical drives fr the array. Use this ptin t build a new array r t expand, shrink, r mve an existing array. Observe the fllwing guidelines: If yu are expanding an array, each drive that yu add must have a capacity n less than that f the smallest drive already in the array. The added drives and the existing drives in the array must all be the same type (fr example, SAS r SATA). If yu are mving r shrinking an array, ACU Scripting cmpares the current drives with the requested drives, and then determines whether yu are mving r shrinking. Shrinking r mving an array is supprted nly in Custm methd mde. HP Array Cnfiguratin Utility 76

If the value f the ClearCnfiguratinWithDataLss (n page 74) ptin is Yes, yu can use the Drive ptin t remve drives frm an array. Determine which mde t use: Aut methd mde ACU cnfigures all the available drives n the cntrller int ne array. If the drives are f different capacities, ACU determines the capacity f the smallest drive and uses the same amunt f space n all ther available drives. Custm methd mde T specify the drives t be used in the array (different arrays n the same cntrller can use different methds), chse ne f the fllwing methds: DriveType T specify individual drives, use the applicable cnventin (prt:id, bx:bay, r prt:bx:bay). T specify nly the number f drives t use (nt which specific drive IDs t use), enter that number as the value fr this ptin. Fr example, if yu enter drive=3, ACU uses the first three available drives t build r expand the array that yu define in the remainder f the script. ACU autmatically determines which drives are suitable t use. T use all available drives, enter an asterisk as the value fr this ptin. An array that is cnfigured using this methd cannt have a spare. This ptin specifies the interface type fr drives that ACU must use t build the array. Chse ne f the valid drive types: [SCSI SAS SATA SATASSD SASSSD] The value is ften used with the wildcard (*) r number argument fr Drive. Jin T use the Jin cmmand, bserve the fllwing requirements: The system must be ffline. The -ffline cmmand line flag must be set when yu start ACU Scripting. The cmmand fails if the OS reprts that any f the vlumes invlved in the jin are in use. CAUTION: Executing the Jin cmmand n an nline system can result in kernel panics, blue screens, and/r data lss. The Split cmmand cnverts a RAID 1 r RAID 10 lgical vlume int tw RAID 0 lgical vlumes. The Jin ptin reverses the splitting prcess by recmbining the tw RAID 0 vlumes int a single RAID 1 r RAID 10 vlume, depending n the number f physical disks. Fr this prcess, ID is the ID f the resulting vlume that was jined. All data n the ther vlume is lst. Array = C Jin = A After the cmmand executes, Array C is remved, and its physical drives are nw a mirrr f the drives in Array A. The riginal cntents f Array C are lst. OnlineSpareMde The value fr this ptin specifies the behavir f the spare drives when they are activated. HP Array Cnfiguratin Utility 77

Fr cntrllers that supprt Aut Replace Drive, setting this value t AutReplace enables a rebuilt spare drive t becme a data drive in the array. When the failed data drive is replaced, it assumes the rle f the frmer spare, eliminating the need fr a secnd array rebuild. Behavir Dedicated AutReplace Descriptin Default value fr spares The spare drive becmes a data drive when the rebuild is cmplete. OnlineSpare The value fr this ptin determines whether the array specified previusly in the script will be cnfigured with spare drives. The interface type fr drives and spare drives must match, fr example, all SAS r all SATA. Methd mde Pssible values Default value Custm Aut T specify exactly which drives t use as spares, use the applicable cnventin (prt:id, bx:bay, r prt:bx:bay). T specify nly the number f spares (nt the exact IDs), enter that number as the value fr this ptin. ACU autmatically selects nly thse drives that are suitable fr the array. T specify that the array shuld nt have spares, enter Nne. Yes (indicating ne spare) N In Cnfigure actin mde: Nne In Recnfigure actin mde, ACU ignres any value entered fr this ptin and keeps any spares that are already present in the cnfiguratin. In Cnfigure actin mde: Yes (indicating ne spare) In Recnfigure actin mde, ACU ignres any value entered fr this ptin and keeps any spares that are already present in the cnfiguratin. Split This cmmand splits RAID 1 r RAID 10 vlumes int individual RAID 0 vlumes. Tw values are available: HIDDEN The driver hides the new lgical vlume frm the OS. VISIBLE The new lgical vlume is visible immediately t the OS. Lgical Drive categry The Lgical Drive categry has the fllwing ptins: ArrayAcceleratr (n page 79) LgicalDrive (n page 79) CachingLgicalDrive (n page 79) CachedLgicalDrive (n page 79) NumberOfParityGrups (n page 79) PreferredPath (n page 80) HP Array Cnfiguratin Utility 78

RAID (n page 80) Renumber (n page 80) Repeat (n page 81) ResurceVlumeOwner (n page 81) Sectrs (n page 81) ShrinkSize (n page 81) Size (n page 81) SizeBlcks (n page 82) StripeSize (n page 82) StripSize (n page 82) ArrayAcceleratr This ptin specifies whether the array acceleratr is enabled r disabled fr the specified lgical drive. The default value is Enabled. LgicalDrive The value that yu enter fr this ptin specifies the ID number f the lgical drive that is t be created r mdified. The first lgical drive n an array must have an ID f 1 (nt 0), and lgical drive numbering must be cntiguus. In Cnfigure actin mde, ACU accepts nly the ID number f the next pssible lgical drive. In Recnfigure actin mde, ACU als accepts the ID number f any existing lgical drive. CachingLgicalDrive The value that yu enter fr this ptin specifies the ID number f the caching lgical drive that is t be created r mdified. The first lgical drive n an array must have an ID f 1 (nt 0), and lgical drive numbering must be cntiguus. In Cnfigure mde, ACU accepts nly the ID number f the next pssible lgical drive. In Recnfigure mde, ACU als accepts the ID number f any existing lgical drive. Caching lgical drives and cached data drives must be n the same Array Cntrller. CachedLgicalDrive The value that yu enter fr this ptin specifies the data lgical drive ID number t assciate with the Caching lgical drive. In Cnfigure mde, ACU accepts the ID number f any existing lgical drive. Caching lgical drives and cached data drives must be n the same Array Cntrller. NumberOfParityGrups When yu create a RAID 50 r RAID 60 cnfiguratin, yu must als set the number f parity grups. Yu can use any integer value greater than 1 fr this setting, with the restrictin that the ttal number f physical drives in the array must be exactly divisible by the number f parity grups. HP Array Cnfiguratin Utility 79

The maximum number f parity grups pssible fr a particular number f physical drives is the ttal number f drives divided by the minimum number f drives necessary fr that RAID level (three fr RAID 50, fur fr RAID 60). PreferredPath If yu select the Manual setting fr PreferredPathMde (n page 74), use the PreferredPath cmmand t specify the path fr I/O t the lgical drive n a redundant cntrller in active/active mde. The default setting fr this ptin is 1. With this setting, the cntrller in chassis slt 1 is the preferred cntrller fr I/O t the lgical drive. If yu select 2, the cntrller in chassis slt 2 becmes the preferred cntrller fr the lgical drive. T determine the chassis slt numbers, use the shw cmmand n a cntrller that supprts redundant cntrllers. RAID The value that yu enter fr this ptin specifies the RAID level f the lgical drive. When the Actin mde is Cnfigure and the Methd mde is Aut, ACU autmatically selects the highest RAID level that the cntrller and drive cnfiguratin can supprt except RAID 50 r RAID 60. T specify RAID 50 r 60 fr a cntrller that supprts either f these RAID levels, use the Custm setting. In this case, yu must als specify the number f parity grups ("NumberOfParityGrups" n page 79). When the Actin mde is Recnfigure, the default value is the existing RAID level fr that lgical drive. If yu specify a different RAID setting, then ACU either ignres the new setting (when Methd mde is Aut) r attempts t migrate the lgical drive t the specified RAID level (when Methd mde is Custm). ACU supprts the fllwing values fr RAID levels: 60 RAID 60 50 RAID 50 ADG RAID ADG is the equivalent f RAID 6 6 RAID 6 5 RAID 5 4 RAID 4 10ADM RAID 1 with 3-way mirrring 10 RAID 10 (mirrring with 2 disks) 1ADM RAID 1 with 3-way mirrring 1 RAID 1 (mirrring with 2 disks) 0 RAID 0 When using an HP Smart Array G6 r G7 cntrller, sme RAID levels require SAAP ("Abut SAAP" n page 8). Renumber This ptin renumbers the lgical drive t N. HP Array Cnfiguratin Utility 80

Typically used after a Jin cmmand, this ptin ensures the prper lgical vlume numbering is set, fr example, the bt vlume is ID 1. D nt mix Renumber and Jin peratins in the same script, because ACU Scripting des nt update its internal state after a renumber. If ther cmmands are mixed with Renumber, cmmands targeting specific vlumes might target the incrrect vlume. Repeat The value yu enter fr this ptin specifies the number f times that ACU is t repeat this lgical drive cnfiguratin. Use ne f the fllwing values: N In Cnfigure mde, ACU creates N new lgical drives. MAX ACU creates the maximum number f lgical drives pssible. The number f drives created depends n the number f existing drives and the maximum number f lgical drives supprted by the cntrller. Yu must specify the lgical drive ID as Next. This Size ptin cntrls the size f each lgical drive, r if the size is set t MAX, the size f the vlumes is set t cnsume all available space n the array. ResurceVlumeOwner This ptin specifies that an existing lgical drive (N) shuld be a snapsht resurce vlume. The ptin als specifies the wner lgical drive ID. If yu d nt specify this cmmand n sme lder mdel cntrllers, the lgical drive remains a nrmal data vlume. Sectrs This ptin specifies the number f sectrs that are t cmprise each track. Enter 32 t disable MaxBt r 63 t enable it. Fr new lgical drives, the default setting is 63 if the lgical drive is larger than 502 GB. Otherwise, the default setting is 32. Fr an existing lgical drive, the default setting is the existing setting. Lgical drive perfrmance is likely t decrease with MaxBt enabled. ShrinkSize In Recnfigure mde, this ptin specifies the resulting size f the lgical drive (in MB) t be reduced. ShrinkSize is nt valid in Cnfigure mde. Size This parameter specifies the size f the lgical drive. Use the fllwing values t set the size: N The size in MB MAX Uses all available unused space in the array fr the lgical drive. This value is the default. MAXMBR Creates the largest size f vlume supprtable by a 32-bit MBR (2TiB) HP Array Cnfiguratin Utility 81

In Recnfigure mde, the default setting is the existing size f the lgical drive. If yu enter a larger value, ACU extends the lgical drive t the new size if there is unused drive capacity n the same array, as lng as the perating system supprts lgical drive extensin. Yu cannt reduce the size f the lgical drive. CAUTION: Back up all data befre extending a lgical drive. SizeBlcks This ptin specifies the size f the lgical drive in 512-byte blcks. Use this ptin t set an exact size withut runding. When ACU Scripting captures a cnfiguratin, it reprts vlume sizes runded dwn t the nearest MB. When the capture is played back, the size is reduced t fit within the already runded MB size. This ptin prevents the lss f vlume size ver successive generatins f captures. Hwever, if the size des nt fit the gemetry f the array, caused by different disks r RAID levels, the size will be runded dwn t fit the gemetry. StripeSize Beginning with ACU, ACU CLI, and ACU Scripting v8.55, the term stripe size has been replaced by strip size. This labeling change des nt affect functinality. When distributing data acrss multiple physical drives (striping), the strip size is the amunt f data that is written t each physical drive. The full stripe size refers t the cmbined size f all the strips acrss all physical drives, excluding parity-nly drives. Fr mre infrmatin, see the ptin fr StripSize (n page 82). StripSize Beginning with ACU, ACU CLI, and ACU Scripting v8.55, the StripSize ptin replaces the StripeSize ptin. When distributing data acrss multiple physical drives (striping), the strip size is the amunt f data that is written t each physical drive. The full stripe size refers t the cmbined size f all the strips acrss all physical drives, excluding parity-nly drives. Yu can enter a numerical value fr this ptin t specify the size f the data strips (in kilbytes), r yu can leave this ptin blank and allw ACU t use a default value. Strip sizes available fr a RAID level vary based n the cntrller and the cntrller firmware level. The maximum strip size changes dynamically and is reduced fr arrays with a large number f data drives r with smaller cntrller cache sizes. (The cntrller must be able t read an entire stripe f data at a time int cache memry during transfrmatin. Available memry is the limiting factr. The fllwing strip sizes are available: 8 8 KB 16 16 KB 32 32 KB 64 64 KB 128 128 KB 256 256 KB HP Array Cnfiguratin Utility 82

512 512 KB 1024 1024 KB (supprted starting with Gen8 cntrllers) The default strip size value depends n the actin mde: In Cnfigure actin mde, the default value is determined by the RAID level that yu specified earlier in the script. In Recnfigure actin mde, the default value fr this ptin is the strip size that is already cnfigured fr the lgical drive. If yu enter a value that is different frm the existing strip size, ACU attempts t migrate the lgical drive t the strip size that yu specify. (If yu intend t migrate the lgical drive, back up all data befre starting the migratin prcedure.) HBA categry The HBA categry has the fllwing ptins: CnnectinName (n page 83) HBA_WW_ID (n page 83) HstMde (n page 83) CnnectinName This ptin is a user-defined string used as the cnnectin name fr the specified HBA. The string can cnsist f: A maximum f 16 characters Embedded space characters but cannt end with a space character Any f the fllwing characters: a z, A Z, 0 9,!, @, #, *, (, ), -, _, +, :,., /, and [space] HBA_WW_ID This ptin specifies which HBA, based n its assigned WWN, is mdified by the cnfiguratin changes. HstMde This ptin specifies the HstMde fr a selected HBA. Setting the Hst Mde ptimizes the strage array fr the selected perating system. The available hst mdes fr an HBA are device-specific. Nt all mdes are available n all devices. Nt all HBAs supprt a HstMde. The fllwing perating system ptins might be available: Default Micrsft Windws OpenVMS Tru64 Linux Slaris Netware HP-UX HP Array Cnfiguratin Utility 83

XML supprt XML utput ACU scripting v8.30 and later supprt an XML file frmat fr input and utput. T create an XML utput dcument, use an XML suffix with the utput file name: C:\hpacuscripting -c ut.xml The fllwing text is an example XML utput file. <?xml versin="1.0"?> <Cnfig.dcument> <!-- Date captured: Tue Jun 09 10:03:08 2009 --> <!-- Versin: 8:30:4 --> <Actin>Cnfigure</Actin> <Methd>Custm</Methd> <Cntrller ID="Slt 1"> <!-- Cntrller HP Smart Array P410, Firmware Versin 1.99 --> <ReadCache>25</ReadCache> <WriteCache>75</WriteCache> <RebuildPririty>Medium</RebuildPririty> <ExpandPririty>Medium</ExpandPririty> <SurfaceScanDelay>3</SurfaceScanDelay> <DriveWriteCache>Disabled</DriveWriteCache> <LicenseKey>35DRP-7RH6S-R89GR-4MX6N-8K48X</LicenseKey> <!-- LicenseKeyType "Flex License" --> <MNPDelay>60</MNPDelay> <IRPEnable>Disabled</IRPEnable> <DPOEnable>Disabled</DPOEnable> <ElevatrSrtEnable>Enabled</ElevatrSrtEnable> <QueueDepth>Autmatic</QueueDepth> <!-- Unassigned Drives 1I:4:5 (60.0 GB), 2I:2:1 (72 GB) --> <Array ID="A"> <!-- Array Drive Type is Slid State SATA --> <!-- Free space 0 GBytes --> <!-- 1I:4:8 (120.0 GB),1I:4:7 (120.0 GB) --> <Drive>1I:4:8, 1I:4:7</Drive> <OnlineSpare>N</OnlineSpare> <LgicalDrive ID="1"> <Raid>1</Raid> <Size>114439</Size> <Sectrs>32</Sectrs> <StripeSize>128</StripeSize> <ArrayAcceleratr>Enabled</ArrayAcceleratr> </LgicalDrive> HP Array Cnfiguratin Utility 84

</Array> <Array ID="B"> <!-- Array Drive Type is SAS --> <!-- Free space 0 GBytes --> <!-- 1I:4:6 (72 GB),2I:2:4 (72 GB),2I:2:3 (72 GB),2I:2:2 (72 GB)--> <Drive>1I:4:6, 2I:2:4, 2I:2:3, 2I:2:2</Drive> <OnlineSpare>N</OnlineSpare> <LgicalDrive ID="2"> <Raid>5</Raid> <Size>52478</Size> <Sectrs>32</Sectrs> <StripeSize>64</StripeSize> <ArrayAcceleratr>Enabled</ArrayAcceleratr> </LgicalDrive> <LgicalDrive ID="3"> <Raid>5</Raid> <Size>52478</Size> <Sectrs>32</Sectrs> <StripeSize>64</StripeSize> <ArrayAcceleratr>Enabled</ArrayAcceleratr> </LgicalDrive> <LgicalDrive ID="4"> <Raid>5</Raid> <Size>52478</Size> <Sectrs>32</Sectrs> <StripeSize>64</StripeSize> <ArrayAcceleratr>Enabled</ArrayAcceleratr> </LgicalDrive> <LgicalDrive ID="5"> <Raid>5</Raid> <Size>52478</Size> <Sectrs>32</Sectrs> <StripeSize>64</StripeSize> <ArrayAcceleratr>Enabled</ArrayAcceleratr> </LgicalDrive> </Array> </Cntrller> </Cnfig.dcument> XML input XML input fllws the same frmat as the dcument fr XML utput (n page 84). Use the same parameter rder as the standard input frmat. The fllwing example shws a simple input script in bth standard and XML frmats. HP Array Cnfiguratin Utility 85

Standard frmat Actin= Cnfigure Methd= Custm Cntrller= Slt 1 Array=A Drive= 1I:4:8, 1I:4:7 LgicalDrive= 1 RAID= 0 Size= 100000 XML frmat <?xml versin="1.0"?> <Cnfig.dcument> <Actin>Cnfigure</Actin> <Methd>Custm</Methd> <Cntrller ID="Slt 1"> <Array ID="A"> <Drive>1I:4:8, 1I:4:7</Drive> <LgicalDrive ID="1"> <Raid>0</Raid> <Size>100000</Size> </LgicalDrive> </Array> </Cntrller> </Cnfig.dcument> XML input file DTD The fllwing DTD utlines the parameters fr an ACU scripting XML input file. <!DOCTYPE Cnfig.dcument [ <!ELEMENT Cnfig.dcument ( Actin, Methd, Cntrller+ ) > <!ELEMENT Actin ( Cnfigure Recnfigure ) > <!ELEMENT Methd ( Aut Custm ) > <!ELEMENT Cntrller, Array ) ChassisName? ClearCnfiguratinWithDataLss DPOEnable? DriveWriteCache? ElevatrSrtEnable? ExpandPririty? IRPEnable? Initiatr? LicenseKey? MNPDelay? PreferredPathMde? QueueDepth? ReadCache? RebuildPririty? SurfaceScanDelay? WriteCache? ) > <!ATTLIST Cntrller ID PCDATA #REQUIRED > <!ELEMENT ClearCnfiguratinWithDataLss ( YES NO ) NO > <!ELEMENT DPOEnable ( YES NO ) > <!ELEMENT DriveWriteCache ( ENABLE DISABLE ) > <!ELEMENT ElevatrSrtEnable ( YES NO ) > <!ELEMENT ExpandPririty ( HIGH MEDIUM LOW ) > <!ELEMENT IRPEnable ( YES NO ) > <!ELEMENT LicenseKey ( #PCDATA ) > <!ELEMENT MNPDelay ( #PCDATA ) > <!ELEMENT PreferredPathMde ( AUTO MANUAL ) > <!ELEMENT ReadCache ( 0 10 20 30 40 50 60 70 80 90 100 ) > <!ELEMENT RebuildPririty ( HIGH MEDIUM LOW ) > <!ELEMENT SurfaceScanDelay ( #PCDATA ) > <!ELEMENT QueueDepth ( #PCDATA ) > <!ELEMENT WriteCache ( 0 10 20 30 40 50 60 70 80 90 100 ) > <!ELEMENT Array, LgicalDrive+ ( Drive, OnlineSpare ) > <!ATTLIST Array ID PCDATA #REQUIRED > HP Array Cnfiguratin Utility 86

<!ELEMENT Drive ( ALL #PCDATA ) > <!ELEMENT OnlineSpare ( YES NO #PCDATA ) > <!ELEMENT LgicalDrive ( Raid, Repeat Size, Sectrs, StripeSize, ArrayAcceleratr? ) > <!ATTLIST LgicalDrive ID PCDATA #REQUIRED > <!ELEMENT ArrayAcceleratr ( ENABLE DISABLE ) ENABLE > <!ELEMENT Raid (0 1 1ADM 10 10ADM 4 5 6 ADG 50 60) > <!ELEMENT Repeat ( MAX #PCDATA ) > <!ELEMENT Sectrs ( 32 63 ) > <!ELEMENT Size ( MAX #PCDATA ) MAX > <!ELEMENT StripeSize ( 8 16 32 64 128 256 512 ) > <!ELEMENT Initiatr ( HBA_WW_ID, CnnectinName?, HstMde? ) > <!ELEMENT HBA_WW_ID ( #PCDATA ) > <!ELEMENT CnnectinName ( #PCDATA ) > <!ELEMENT HstMde ( #PCDATA ) > ]> ACU scripting warning messages Warning cde Warning message Cmment r clarificatin 4000 License key is already installed The input file specified a license key. Hwever, a license key is already installed n the cntrller. 4001 Clear cnfiguratin cmmand failed - cnfiguratin is already cleared The -reset ptin was used n a cntrller that des nt have a cnfiguratin. 4002 Chassis name is already set t this value The chassis name is already set t the supplied value. The cmmand is ignred. 4003 One r mre cntrller cmmands were skipped because the cntrller is nt cnfigured Certain cmmands require that the cntrller be cnfigured befre they can be sent t the cntrller. 4004 Using Repeat functin Sme cmmands have been ignred because the Repeat parameter has been specified in the input file. 4005 The system must be rebted fr the firmware flash t cmplete 4006 Unable t set the array acceleratr fr this vlume. The cache bard may be missing r have a bad status, r the cntrller may nt supprt a cache A cntrller has been flashed with new firmware. The new firmware requires a rebt t take effect. The cntrller may nt supprt a cache (fr example, sme Sftware RAID cntrllers) r the cache may be missing r defective. ACU scripting errr messages Errr cde Errr message Cmment r clarificatin 0 N errr exists. The prgram cmpleted HP Array Cnfiguratin Utility 87

Errr cde Errr message 2053 T many cinciding expansin, migratin, r extensin peratins Cmment r clarificatin successfully. The new cnfiguratin requires mre transfrmatins than are pssible at ne time. Fr example, yu cannt expand a lgical vlume and transfrm its RAID level at the same time. 2056 Cntrller des nt supprt license keys The cntrller des nt supprt license key entry r deletin. 2059 Invalid license key The entered license key is nt a valid license key. 2064 Cntrller des nt supprt SSP The cntrller des nt supprt SSP functins. 2817 Invalid Actin The requested actins are invalid, fr example, cmbining -reset with capture mde. 2818 Invalid Methd The methd must be either Custm r Aut. 2819 Invalid Cntrller An invalid cntrller value was specified. 2821 N cntrllers detected N cntrllers were detected. This errr applies t Input mde nly. 2823 Invalid Rebuild Pririty The specified rebuild pririty is nt supprted. 2824 Invalid Expand Pririty The specified expand pririty is nt supprted. This errr als ccurs if the cntrller des nt allw expansin, and therefre des nt supprt expand pririty. 2825 Invalid Array The array ID is invalid. 2826 Array nt specified The Array cmmand is missing frm the script file. Sme cmmands were fund that require an Array t be specified. 2827 New Array ID des nt match the next available Array ID. The array ID in the script file des nt match the array ID f the next available array. Fr example, if the cnfiguratin has an Array A and the input file specifies Array C (withut Array B), then the script generates this errr. 2828 New Array ID already exists The array ID specified in the script file (in Cnfigure mde) already exists in the cnfiguratin. Cnfigure mde can nly create new arrays. 2829 Cannt create Array The cntrller will nt allw a new array t be created, either because the cntrller has n unassigned physical drives attached r because the maximum number f arrays r lgical drives has been reached already. 2830 Cannt expand Array The Array culd nt be expanded, either because the cntrller des nt supprt expansin, r the current cnfiguratin des nt allw expansin t ccur n the array. 2831 Cannt change Array Spare The spare state f the array culd nt be changed. This errr can ccur when yu attempt t add r drp a spare and the current cnfiguratin des nt allw a spare state change fr the array. 2832 Invalid physical drive A specified physical drive is nt a valid physical drive, r it cannt be placed in the array. 2833 Invalid Spare A specified spare is nt a valid spare drive, r it cannt be placed in the array as a spare. 2834 Invalid lgical drive The lgical drive ID is nt valid. HP Array Cnfiguratin Utility 88

Errr cde Errr message 2836 New Lgical Drive ID des nt match the next available lgical drive ID. If yu are attempting t replicate a cnfiguratin that has nn-cnsecutive lgical drive numbers, then yu must change the script file s that the lgical drive numbers are cnsecutive. Cmment r clarificatin The script file specifies a lgical drive ID that is nt the first unused ID in the sequence. Fr example, this message appears if the cntrller has nly Lgical Drive 1 and the script file specifies creatin f Lgical Drive 3 (mitting Lgical Drive 2). A cmmn cause f this errr is that the input file specifies nnsequential lgical drive numbers. In this case, change the lgical drive numbers in the input file s that they are sequential. 2837 New Lgical Drive ID already exists This errr ccurs in Cnfigure mde when the lgical drive ID specified in the script file already exists in the cnfiguratin. In Cnfigure mde, yu can create new lgical drives nly. 2838 Cannt create Lgical Drive The array has n free space, r the maximum number f lgical drives has been reached already. 2839 Cannt migrate Lgical Drive RAID The cntrller des nt supprt RAID migratin, r migratin is nt pssible with the current cntrller cnfiguratin. 2841 Cannt extend Lgical Drive The cntrller des nt supprt extensin, r the current cntrller cnfiguratin cannt be extended. Fr example, extensin is nt pssible if the array has n free space. 2842 Invalid RAID The specified RAID level is invalid r is nt pssible with the current physical disk and array cnfiguratin. 2843 Invalid Size The specified size is invalid r is nt pssible with the current cnfiguratin. 2844 Invalid Stripe Size The specified stripe size is invalid, nt supprted by the current RAID level, r nt pssible with the current cnfiguratin. 2849 Invalid ClearCnfiguratinWithDataLss The valid parameters are Yes and N (default). parameter 2850 Cntrller des nt supprt Chassis Name The cntrller des nt supprt setting a chassis name. 2851 Invalid Chassis Name The entered chassis name is invalid. Use characters frm the set a z, A Z, 0 9,!, @, #, *, (, ),,, -, _, +, :,., /, and [space]. The name cannt end with a space character r exceed the maximum number f characters allwed by the cntrller. 2852 Invalid SSP State The requested SSP state is nt a valid SSP state. 2853 Cannt change SSP settings The SSP settings cannt be changed fr the cntrller r lgical drive. 2854 Invalid SSP Adapter ID The adapter ID is nt a valid adapter ID that was detected by the cntrller. 2857 Invalid Surface Scan Delay 2861 Cntrller des nt supprt redundancy settings The cntrller is nt redundant r des nt supprt redundancy settings. 2864 Invalid Preferred Path Mde The specified value fr the preferred path mde is nt valid, r the cntrller is nt available. 2865 Invalid Preferred Path The specified preferred path is nt a valid chassis HP Array Cnfiguratin Utility 89

Errr cde Errr message Cmment r clarificatin slt fr an available, active cntrller, r the cntrller is nt available. 2866 Failure pening capture file <text> 2867 Failure pening input file <text> 2868 Failure pening errr file <text> 2877 There are n suitable spares available ACU fund n drives that culd be used as spares fr the specified array. 2880 Invalid Physical Disk Type Specified 2882 Invalid MNP delay The specified value fr MNP delay is invalid. 3000 Invalid Optin The value f the ptin supplied t this parameter is invalid. 3002 Cmmand Failed The cntrller returned an errr fr a cmmand. 3003 License Key Delete Failed ACU is unable t delete the license key. 3004 Invalid Sectr Size 3005 Cannt delete Array 3006 Invalid Number f Parity Grups 3007 Chassis name is t lng 3008 Chassis name is already in use Anther cntrller is already using the entered chassis name. 3009 Aut Cnfigure failed The Aut Cnfigure mde was unable t cmplete aut cnfiguratin. 3010 Cannt extend lgical drive, nt enugh free space fr the requested size 3011 Cannt extend lgical drive, requested size is t small 3012 Cannt specify bth SIZE and SHRINKSIZE The input file cannt specify bth a SIZE and SHRINKSIZE parameter. 3013 Cannt shrink Array The array shrink peratin was nt successful. 3014 Cannt mve Array The array mve peratin was nt successful. 3015 Invalid peratin - Advanced Pack supprt required 3016 Spare drives cannt be specified by a cunt in Recnfigure mde 3017 Disk drives cannt be specified by a cunt in Recnfigure mde 3018 Invalid number f physical disks 3019 Cannt create Array - n physical disks specified 3020 SSP must be enabled in rder t perfrm this peratin 3021 Invalid cnnectin name The requested peratin requires a valid license key t be entered. When in Recnfigure mde, the requested spare drives must be specified by their addresses. A simple cunt cannt be used. When in Recnfigure mde, the requested data drives must be specified by their addresses. A simple cunt cannt be used. ACU cannt create an array unless physical disks are specified in the input file DRIVE parameter. Fr the specified peratin, ACU requires SSP t be supprted and enabled. HP Array Cnfiguratin Utility 90

Errr cde Errr message 3022 The cnnectinname cannt be remved when the hstmde has a nn-default value. 3023 Invalid Hst Mde 3024 Invalid Adapter ID 3025 This cntrller des nt have hst mde mdificatin capability Cmment r clarificatin 3026 Yu need t have administratr rights t cntinue. 3027 Anther instance f ACU is already running (pssibly a service). Please terminate the ACU applicatin befre running ACU scripting. 3028 Invalid Drive Cache setting. Valid ptins are ENABLE and DISABLE. 3029 Invalid r ut f rder Cmmand Verify the rdering f the cmmands in the input cnfiguratin file. 3030 Invalid r missing Array fr Recnfigure Expecting a valid array in Recnfigure mde 3031 Invalid r missing Filename fr Firmware Update The firmware filename supplied is nt a valid filename. 3032 Firmware Update Failed The firmware flash peratin n the cntrller failed. 3033 This cntrller has been cnfigured with a Sme changes t SOULAPI are nt mre recent versin f sftware. T prevent backward-cmpatible. This check prevents the use f data lss, cnfiguratin changes t this cntrller are nt allwed. Please upgrade an lder versin f sftware n a cntrller cnfigured with a newer versin, pssibly verriding t the latest versin t be able t cntinue t changes and destrying data. cnfigure this cntrller. 3034 Operatins n this Array are temprarily unavailable while the Array is transfrming. The user requested t many simultaneus changes. Fr example, the user added new disks t an array (expand array) and changed the size r RAID level f lgical vlumes n the array. The slutin is fr the user t wait until the array transfrmatin is cmplete. 3035 Invalid value fr NBatteryWriteCache A prblem exists with the NOBATTERYWRITECACHE cmmand. Check the supplied argument. Nt all cntrllers supprt this peratin. 3036 Cannt delete Lgical Drive A prblem ccurred during the attempt t delete the specified lgical drive. The drive may be in use by the OS, it may nt exist, r it may nt be the last lgical drive n the array. HP Array Cnfiguratin Utility 91

HP Array Diagnstics and SmartSSD Wear Gauge Utility Abut the utility Frmerly knwn as the Array Diagnstics Utility, the HP Array Diagnstics and SmartSSD Wear Gauge Utility cllects all pssible infrmatin abut strage devices in the system, detects all prblems, and prvides a detailed cnfiguratin reprt in.zip frmat. After dwnlading and installing the sftware, yu can run the utility as a GUI r a CLI in an nline envirnment. The functinality in this utility is mirrred in the diagnstics features f the HP Array Cnfiguratin Utility, which can be run in an ffline envirnment. The utility generates tw types f reprts: Array diagnstic reprt This reprt cntains infrmatin abut all devices, such as array cntrllers, strage enclsures, drive cages, as well as lgical, physical, and tape drives. Fr supprted slid state drives, this reprt als cntains SmartSSD Wear Gauge infrmatin. SmartSSD Wear Gauge reprt This reprt cntains infrmatin abut the current usage level and remaining expected lifetime f slid state drives attached t the system. Fr mre infrmatin, see "Reprted infrmatin (n page 92)." Reprted infrmatin The array diagnstic reprt prvides detailed infrmatin abut devices (array cntrllers, strage enclsures, drive cages, physical drives, lgical drives, and tape drives). Fr example, device infrmatin n a typical embedded cntrller might include: Sftware versins Errrs Cntrller infrmatin: Name Attached devices Descriptin PCI bus PCI device PCI functin Drive infrmatin: HP Array Diagnstics and SmartSSD Wear Gauge Utility 92

Interface WWID Drive mdel Serial number Firmware revisin Ttal blcks The SmartSSD Wear Gauge reprt cntains infrmatin n the current usage level f and expected lifetime remaining fr slid state drives attached t the system. Fr discvered SSDs, the reprt summary page prvides the fllwing calculated ttals: Ttal Slid State Drives with Wearut Status Ttal Smart Array Slid State Drives Ttal Nn Smart Array Slid State Drives Ttal Slid State SAS Drives Ttal Slid State SATA Drives Ttal Slid State Drives In additin t these ttals, the summary page als displays the fllwing tables: Slid State Drives with Wearut Status Slid State Drives with Less Than an Estimated 56 Days f Life Remaining Slid State Drives with Less Than 2% Usage Remaining Slid State Drives with Less Than 5% Usage Remaining Smart Array Cntrllers Nn Smart Array Cntrllers When the generated reprt is viewed in a brwser, the reprt page displays the fllwing fields in the SmartSSD Status table. HP Array Diagnstics and SmartSSD Wear Gauge Utility 93

Field SSD Wear Status Pwer Cycles Pwer On Hurs Estimated Life Remaining Based On Wrklad T Date Usage Remaining SSD Utilizatin Descriptin Indicates the SSD's wear status with ne f the fllwing messages: OK Nt Supprted The SmartSSD Wear Gauge lg is full. Wear Gauge parameters are nt available. SSD has less than 5% usage remaining befre wearut. SSD has less than 2% usage remaining befre wearut. SSD has less than an estimated 56 days befre it reaches the maximum usage limit fr writes (wearut) and shuld be replaced as sn as pssible. SSD has less than 5% f usage remaining befre wearut. It has less than an estimated 56 days befre it reaches the maximum usage limit and shuld be replaced as sn as pssible. SSD has less than 2% f usage remaining befre wearut. It has less than an estimated 56 days befre it reaches the maximum usage limit and shuld be replaced as sn as pssible. SSD has reached the maximum rated usage limit fr writes (wearut) and shuld be replaced immediately. Indicates the number f times the SSD has pwered n frm the pwered ff state Indicates the number f hurs the SSD has been pwered n Indicates an estimate f the number f days the SSD has befre SSD Utilizatin reaches 100%. This field is nt displayed when the SSD Utilizatin is still at 0%. Indicates the percentage f the SSD that has nt wrn ut. Usage remaining is equal t the difference f 100 and the SSD Utilizatin percentage. Indicates the percentage f the SSD that has wrn ut Installing the utility 1. Brwse t the HP Array Cnfiguratin Utility website (http://h18004.www1.hp.cm/prducts/servers/prliantstrage/sftware-management/acumatrix /index.html). 2. Click Dwnlad sftware. 3. Select an OS. 4. Identify the preferred sftware and versin, and then click Dwnlad. 5. Save, and then run, the executable file. By default, the sftware installs at C:\Prgram Files\HP System Tls\. HP Array Diagnstics and SmartSSD Wear Gauge Utility 94

Setting up ADU Remte Service Mde Yu can run ADU as a Windws Service, s that it starts autmatically and runs in the backgrund at all times. ACU is accessible remtely frm the System Management Hmepage (https://lcalhst:2381). T set up the service: 1. Click Start>All Prgrams>HP System Tls>HP Array Diagnstics and SmartSSD Wear Gauge Utility>Setup ADU Remte Mde. 2. Select Enable Remte Service Mde. 3. Click OK. Launching the utility in CLI mde 1. Open a cmmand prmpt. 2. Change directry (cd) t the lcatin where hpaducli.exe is installed. This directry is cmmnly C:\Prgram Files\Cmpaq\hpadu\bin. 3. D ne f the fllwing: Generate a diagnstic reprt with the fllwing cmmand: hpaducli -f adu-reprt.zip Generate a SmartSSD Wear Gague reprt with the fllwing cmmand: hpaducli -ssdrpt -f ssd-reprt.zip Fr mre ptins, use the fllwing cmmand: hpaducli -help Launching the utility in GUI mde 1. Click Start>All Prgrams>HP System Tls>HP Array Diagnstics and SmartSSD Wear Gauge Utility>HP Array Diagnstics and SmartSSD Wear Gauge Utility. HP Array Diagnstics and SmartSSD Wear Gauge Utility 95

The splash screen appears. 2. Select ne f the fllwing tasks: Viewing the diagnstic reprt (n page 96) Generating the diagnstic reprt (n page 98) Viewing the SmartSSD Wear Gauge reprt (n page 99) Generating the SmartSSD Wear Gauge reprt (n page 100) Fr mre infrmatin abut the interface, select Help. Diagnstic reprt prcedures Viewing the diagnstic reprt 1. Launch the GUI ("Launching the utility in GUI mde" n page 95). 2. Select View Diagnstic Reprt. HP Array Diagnstics and SmartSSD Wear Gauge Utility 96

The utility generates and displays the reprt. The diagnstic reprt includes an additinal RIS Event Lg tab. Smart Array cntrllers stre cnfiguratin data in the RAID infrmatin sectr f all physical drives. The RIS Event Lg reads the data and displays the decded change lgs. HP Array Diagnstics and SmartSSD Wear Gauge Utility 97

3. Click RIS Event Lg. The lg appears. 4. After reviewing the reprt, d ne f the fllwing: Click Save Reprt, and then save the generated file. Click ADU Hme, and then perfrm additinal tasks. Click Exit ADU. Generating the diagnstic reprt 1. Launch the GUI ("Launching the utility in GUI mde" n page 95). 2. Select Generate Diagnstic Reprt. HP Array Diagnstics and SmartSSD Wear Gauge Utility 98

The utility generates the reprt, and then displays the File Dwnlad dialg bx. 3. Open r save the file. 4. When yu are finished with the file, d ne f the fllwing: Click Save Reprt, and then save the generated file. Click ADU Hme, and then perfrm additinal tasks. Click Exit ADU. Identifying and viewing diagnstic reprt files The diagnstic reprt utput archive cntains the fllwing files: ADUReprt.txt Diagnstic reprt in text frmat ADUReprt.xml Diagnstic reprt in XML frmat ADUReprtViewer.htm HTML viewer fr XML diagnstic reprt SltX.txt (SltX.ld) Cntrller serial utput lg The serial utput lg file(s) are nly available if the HP Smart Array SAS/SATA Event Ntificatin Service is installed and running. T view the diagnstic reprt files in a brwser: 1. Extract ADUReprtViewer.htm t a directry. 2. Open ADUReprtViewer.htm in the brwser. SmartSSD Wear Gauge reprt prcedures Viewing the SmartSSD Wear Gauge reprt 1. Launch the GUI ("Launching the utility in GUI mde" n page 95). 2. Select View SmartSSD Wear Gauge Reprt. HP Array Diagnstics and SmartSSD Wear Gauge Utility 99

The utility generates and displays the reprt. 3. After reviewing the reprt, d ne f the fllwing: Click Save Reprt, and then save the generated file. Click ADU Hme, and then perfrm additinal tasks. Click Exit ADU. Generating the SmartSSD Wear Gauge reprt 1. Launch the GUI ("Launching the utility in GUI mde" n page 95). 2. Select Generate SmartSSD Wear Gauge Reprt. The utility generates the reprt, and then displays the File Dwnlad dialg bx. HP Array Diagnstics and SmartSSD Wear Gauge Utility 100

3. Open r save the file. 4. After reviewing the reprt, d ne f the fllwing: Click Save Reprt, and then save the generated file. Click ADU Hme, and then perfrm additinal tasks. Click Exit ADU. Identifying and viewing SmartSSD Wear Gauge reprt files The SmartSSD Wear Gauge reprt utput archive cntains the fllwing files: SmartSSDWearGaugeReprt.txt SmartSSD wear gauge reprt in text frmat SmartSSDWearGaugeReprt.jsn SmartSSD wear gauge reprt in JSON frmat SmartSSDWearGaugeReprt.htm HTML viewer fr the JSON wear gauge reprt T view the SmartSSD Wear Gauge reprt files in a brwser: 1. Extract the fllwing files t a directry: SmartSSDWearGaugeReprt.jsn SmartSSDWearGaugeReprt.htm All files must reside in the same directry. 2. Open SmartSSDWearGaugeReprt.htm in the brwser. HP Array Diagnstics and SmartSSD Wear Gauge Utility 101

Drive arrays and fault-tlerance methds Drive arrays The capacity and perfrmance f a single physical (hard) drive is adequate fr hme users. Hwever, business users demand higher strage capacities, higher data transfer rates, and greater prtectin against data lss when drives fail. Cnnecting extra physical drives (Pn in the figure) t a system increases the ttal strage capacity but has n effect n the efficiency f read/write (R/W) peratins. Data can still be transferred t nly ne physical drive at a time. Drive arrays and fault-tlerance methds 102

With an array cntrller installed in the system, the capacity f several physical drives can be cmbined int ne r mre virtual units called lgical drives (als called lgical vlumes and dented by Ln in the figures in this sectin). Then, the read/write heads f all the cnstituent physical drives are active simultaneusly, reducing the ttal time required fr data transfer. Because the read/write heads are active simultaneusly, the same amunt f data is written t each drive during any given time interval. Each unit f data is called a blck (dented by Bn in the figure), and adjacent blcks frm a set f data stripes (Sn) acrss all the physical drives that cmprise the lgical drive. Fr data in the lgical drive t be readable, the data blck sequence must be the same in every stripe. This sequencing prcess is perfrmed by the array cntrller, which sends the data blcks t the drive write heads in the crrect rder. A natural cnsequence f the striping prcess is that each physical drive in a given lgical drive will cntain the same amunt f data. If ne physical drive has a larger capacity than ther physical drives in the same lgical drive, the extra capacity is wasted because it cannt be used by the lgical drive. Drive arrays and fault-tlerance methds 103

The grup f physical drives cntaining the lgical drive is called a drive array, r just array (dented by An in the figure). Because all the physical drives in an array are cmmnly cnfigured int just ne lgical drive, the term array is ften used as a synnym fr lgical drive. Hwever, an array can cntain several lgical drives, each f a different size. Each lgical drive in an array is distributed acrss all f the physical drives within the array. A lgical drive can als extend acrss mre than ne prt n the same cntrller, but it cannt extend acrss mre than ne cntrller. Drive failure, althugh rare, is ptentially catastrphic. Fr arrays that are cnfigured as shwn in the previus figure, failure f any physical drive in the array causes every lgical drive in the array t suffer irretrievable data lss. T prtect against data lss due t physical drive failure, lgical drives are cnfigured with fault tlerance ("Fault-tlerance methds" n page 105). Fr any cnfiguratin except RAID 0, further prtectin against data lss can be achieved by assigning a drive as an nline spare (r ht spare). This drive cntains n data and is cnnected t the same cntrller as the array. When any ther physical drive in the array fails, the cntrller autmatically rebuilds infrmatin that was riginally n the failed drive t the nline spare. The system is thus restred t full RAID-level data prtectin, althugh it nw n lnger has an nline spare. (Hwever, in the unlikely event that anther drive in the array fails while data is being rewritten t the spare, the lgical drive will still fail.) When yu cnfigure an nline spare, it is autmatically assigned t all lgical drives in the same array. Additinally, yu d nt need t assign a separate nline spare t each array. Instead, yu can cnfigure ne hard drive t be the nline spare fr several arrays if the arrays are all n the same cntrller. Effects f a hard drive failure n lgical drives When a drive fails, all lgical drives that are in the same array are affected. Each lgical drive in an array might be using a different fault-tlerance methd, s each lgical drive can be affected differently. RAID 0 cnfiguratins d nt tlerate drive failure. If any physical drive in the array fails, all RAID 0 lgical drives in the same array als fail. RAID 10 cnfiguratins tlerate multiple drive failures if n failed drives are mirrred t ne anther. RAID 5 cnfiguratins tlerate ne drive failure. Drive arrays and fault-tlerance methds 104

RAID 50 cnfiguratins tlerate ne failed drive in each parity grup. RAID 6 cnfiguratins tlerate tw failed drives at a given time. RAID 60 cnfiguratins tlerate tw failed drives in each parity grup. RAID 1 (ADM) and RAID 10 (ADM) cnfiguratins tlerate multiple drive failures if n mre than tw drives, mirrred t ne anther, fail. Fault-tlerance methds Several fault-tlerance methds exist. Thse mst ften used with Smart Array cntrllers are hardware-based RAID methds. Tw alternative fault-tlerance methds that are smetimes used are als described ("Alternative fault-tlerance methds" n page 113). Hwever, hardware-based RAID methds prvide a much mre rbust and cntrlled fault-tlerance envirnment, s these alternative methds are seldm used. RAID 0 N fault tlerance A RAID 0 cnfiguratin prvides data striping, but there is n prtectin against data lss when a drive fails. Hwever, it is useful fr rapid strage f large amunts f nncritical data (fr printing r image editing, fr example) r when cst is the mst imprtant cnsideratin. Advantages: Has the highest write perfrmance f all RAID methds. Has the lwest cst per unit f stred data f all RAID methds. All drive capacity is used t stre data (nne is needed fr fault tlerance). Disadvantages: All data n the lgical drive is lst if a physical drive fails. Cannt use an nline spare. Can nly preserve data by backing it up t external drives. Drive arrays and fault-tlerance methds 105

RAID 1 and RAID 1+0 (RAID 10) In RAID 1 and RAID 1+0 (RAID 10) cnfiguratins, data is duplicated t a secnd drive. When the array cntains nly tw physical drives, the fault-tlerance methd is knwn as RAID 1. When the array has mre than tw physical drives, drives are mirrred in pairs, and the fault-tlerance methd is knwn as RAID 1+0 r RAID 10. In each mirrred pair, the physical drive that is nt busy answering ther requests answers any read requests that are sent t the array. This behavir is called lad balancing. If a physical drive fails, the remaining drive in the mirrred pair can still prvide all the necessary data. Several drives in the array can fail withut incurring data lss, as lng as n tw failed drives belng t the same mirrred pair. This fault-tlerance methd is useful when high perfrmance and data prtectin are mre imprtant than the cst f physical drives. Drive arrays and fault-tlerance methds 106

Advantages: This methd has the secnd highest read perfrmance f any fault-tlerant cnfiguratin. N data is lst when a drive fails, as lng as n failed drive is mirrred t anther failed drive. Up t half f the physical drives in the array can fail. Disadvantages: This methd is expensive, because many drives are needed fr fault tlerance. Only half f the ttal drive capacity is usable fr data strage. RAID 1 (ADM) and RAID 10 (ADM) In RAID 1 (ADM) and RAID 10 (ADM) cnfiguratins, data is duplicated t tw additinal drives. When the array cntains nly three physical drives, the fault-tlerance methd is knwn as RAID 1 (ADM). Drive arrays and fault-tlerance methds 107

When the array has mre than three physical drives, drives are mirrred in tris, and the fault-tlerance methd is knwn as RAID 10 (ADM). In each mirrred tri, the physical drives that are nt busy answering ther requests answer any read requests that are sent t the array. This behavir is called lad balancing. If a physical drive fails, the remaining tw drives in the mirrred tri can still prvide all the necessary data. Several drives in the array can fail withut incurring data lss, as lng as n three failed drives belng t the same mirrred tri. This fault-tlerance methd is useful when high perfrmance and data prtectin are mre imprtant than the cst f physical drives. Advantages: This methd has the highest read perfrmance f any fault-tlerant cnfiguratin. N data is lst when tw drives fail, as lng as n tw failed drives are mirrred t anther failed drive. Up t tw-thirds f the physical drives in the array can fail. Disadvantages: This methd is expensive, because many drives are needed fr fault tlerance. Only ne-third f the ttal drive capacity is usable fr data strage. Drive arrays and fault-tlerance methds 108

RAID 5 distributed data guarding In a RAID 5 cnfiguratin, data prtectin is prvided by parity data (dented by Px,y in the figure). This parity data is calculated stripe by stripe frm the user data that is written t all ther blcks within that stripe. The blcks f parity data are distributed evenly ver every physical drive within the lgical drive. When a physical drive fails, data that was n the failed drive can be calculated frm the remaining parity data and user data n the ther drives in the array. This recvered data is usually written t an nline spare in a prcess called a rebuild. This cnfiguratin is useful when cst, perfrmance, and data availability are equally imprtant. Advantages: Has high read perfrmance. Data is nt lst if ne physical drive fails. Mre drive capacity is usable than with RAID 1+0 parity infrmatin requires nly the strage space equivalent t ne physical drive. Disadvantages: Has relatively lw write perfrmance. Data is lst if a secnd drive fails befre data frm the first failed drive is rebuilt. RAID 6 (ADG) Advanced Data Guarding NOTE: Nt all cntrllers supprt RAID 6 (ADG). Drive arrays and fault-tlerance methds 109

RAID 6 (ADG), like RAID 5, generates and stres parity infrmatin t prtect against data lss caused by drive failure. With RAID 6 (ADG), hwever, tw different sets f parity data are used (dented by Px,y and Qx,y in the figure), allwing data t still be preserved if tw drives fail. Each set f parity data uses a capacity equivalent t that f ne f the cnstituent drives. This methd is mst useful when data lss is unacceptable but cst is als an imprtant factr. The prbability that data lss will ccur when an array is cnfigured with RAID 6 (ADG) is less than it wuld be if it was cnfigured with RAID 5. Advantages: This methd has a high read perfrmance. This methd allws high data availability Any tw drives can fail withut lss f critical data. Mre drive capacity is usable than with RAID 1+0 Parity infrmatin requires nly the strage space equivalent t tw physical drives. Disadvantages: The main disadvantage f RAID 6 (ADG) is a relatively lw write perfrmance (lwer than RAID 5) because f the need fr tw sets f parity data. Drive arrays and fault-tlerance methds 110

RAID 50 RAID 50 is a nested RAID methd in which the cnstituent hard drives are rganized int several identical RAID 5 lgical drive sets (parity grups). The smallest pssible RAID 50 cnfiguratin has six drives rganized int tw parity grups f three drives each. Fr any given number f hard drives, data lss is least likely t ccur when the drives are arranged int the cnfiguratin that has the largest pssible number f parity grups. Fr example, fur parity grups f three drives are mre secure than three parity grups f fur drives. Hwever, less data can be stred n the array with the larger number f parity grups. RAID 50 is particularly useful fr large databases, file servers, and applicatin servers. Advantages: Higher perfrmance than fr RAID 5, especially during writes. Better fault tlerance than either RAID 0 r RAID 5. Up t n physical drives can fail (where n is the number f parity grups) withut lss f data, as lng as the failed drives are in different parity grups. Disadvantages: All data is lst if a secnd drive fails in the same parity grup befre data frm the first failed drive has finished rebuilding. A greater percentage f array capacity is used t stre redundant r parity data than with nn-nested RAID methds. Drive arrays and fault-tlerance methds 111

RAID 60 RAID 60 is a nested RAID methd in which the cnstituent hard drives are rganized int several identical RAID 6 lgical drive sets (parity grups). The smallest pssible RAID 60 cnfiguratin has eight drives rganized int tw parity grups f fur drives each. Fr any given number f hard drives, data lss is least likely t ccur when the drives are arranged int the cnfiguratin that has the largest pssible number f parity grups. Fr example, five parity grups f fur drives are mre secure than fur parity grups f five drives. Hwever, less data can be stred n the array with the larger number f parity grups. RAID 60 is particularly useful fr data archives and high-availability slutins. Advantages: Higher perfrmance than fr RAID 6, especially during writes. Better fault tlerance than either RAID 0 r RAID 6. Up t 2n physical drives can fail (where n is the number f parity grups) withut lss f data, as lng as n mre than tw failed drives are in the same parity grup. Disadvantages: All data is lst if a third drive in a parity grup fails befre ne f the ther failed drives in the parity grup has finished rebuilding. A greater percentage f array capacity is used t stre redundant r parity data than with nn-nested RAID methds. Cmparing the hardware-based RAID methds Nt all cntrllers supprt all RAID levels. T supprt sme RAID levels, HP Smart Array G6 and G7 cntrllers require SAAP ("Abut SAAP" n page 8). Drive arrays and fault-tlerance methds 112

Item RAID 0 RAID 1+0 RAID 5 RAID 6 (ADG) Alternative name Striping (n fault tlerance) Mirrring Distributed Data Guarding Advanced Data Guarding RAID 1(0) (ADM) Advanced Data Mirrring Frmula fr number f drives usable n n/2 n-1 n-2 n/3 fr data (n = ttal number f drives in array) Percentage f drive space usable* 100% 50% 67% t 93% 50% t 96% 33% Minimum number f physical drives 1 2 3 4 3 Tlerates failure f ne physical drive N Yes Yes Yes Yes Tlerates simultaneus failure f mre than ne physical drive N Only if n tw failed drives are in the same mirrred N Yes Only if n three drives are in the same mirrr grup pair Read perfrmance High High High High High Write perfrmance High Medium Lw Lw Medium Relative cst Lw High Medium Medium Very high *Values fr the percentage f drive space usable are calculated with these assumptins: (1) all physical drives in the array have the same capacity; (2) nline spares are nt used; (3) n mre than 14 physical drives are used per array fr RAID 5; and (4) n mre than 56 drives are used with RAID 6 (ADG). Selecting a RAID methd Nt all cntrllers supprt all RAID levels. T determine the RAID capabilities f yur cntrller, see the mdel-specific infrmatin fr yur cntrller n the HP website (http://www.hp.cm/prducts/smartarray). Mst imprtant criterin Als imprtant Suggested RAID level Fault tlerance Cst effectiveness I/O perfrmance Cst effectiveness I/O perfrmance Fault tlerance I/O perfrmance Cst effectiveness Fault tlerance RAID 6 RAID 10 (ADM), RAID 1+0, RAID 50, RAID 60 RAID 6 RAID 5 (RAID 0 if fault tlerance is nt required) RAID 5 (RAID 0 if fault tlerance is nt required) RAID 10 (ADM), RAID 1+0, RAID 50, RAID 60 Alternative fault-tlerance methds Yur perating system may als supprt sftware-based RAID r cntrller duplexing. Sftware-based RAID resembles hardware-based RAID, except that the perating system wrks with lgical drives as if they were physical drives. T prtect against data lss caused by physical drive failure, each lgical drive must be in a different array frm the thers. Cntrller duplexing uses tw identical cntrllers with independent, identical sets f drives cntaining identical data. In the unlikely event f a cntrller failure, the remaining cntrller and drives will service all requests. Drive arrays and fault-tlerance methds 113

Neither f these alternative fault-tlerance methds supprts nline spares r autmatic data recvery, nr d they supprt aut-reliability mnitring r interim data recvery. If yu decide t use ne f these alternative methds, cnfigure yur arrays with RAID 0 fr maximum strage capacity and refer t yur perating system dcumentatin fr further implementatin details. Drive arrays and fault-tlerance methds 114

Diagnsing array prblems Diagnstic tls T trublesht array prblems and generate feedback abut arrays, use the fllwing diagnstic tls: ACU Fr mre recent prducts, array diagnstics is available with ACU v8.28.13.0 and later. This utility is available n the SmartStart CD in the cntrller kit and als n the HP website (http://www.hp.cm/supprt). Fr mre infrmatin abut ACU, see "Abut ACU (n page 10)." Fr mre infrmatin abut errr messages, see the HP PrLiant Servers Trubleshting Guide. ADU Fr prducts that supprt SmartStart v8.25 and earlier, this utility is available n the SmartStart CD in the cntrller kit and als n the HP website (http://www.hp.cm/supprt). When prmpted fr prduct infrmatin, enter the server mdel name. Fr mre infrmatin abut the meanings f the varius ADU errr messages, see the HP PrLiant Servers Trubleshting Guide. HP Array Diagnstics and SmartSSD Wear Gauge Utility This standalne diagnstic utility prvides cnfiguratin and errr infrmatin abut array cntrllers, strage enclsures, HBAs, drive cages, lgical drives, physical drives, and tape drives. Fr any supprted SSDs, the utility prvides current usage level and remaining expected lifetime. Fr mre infrmatin, see "HP Array Diagnstics and SmartSSD Wear Gauge Utility (n page 92)." Event Ntificatin Service This utility reprts array events t the Micrsft Windws system event lg and IML. Yu can btain the utility frm the SmartStart CD r the HP website (http://www.hp.cm/supprt). When prmpted fr prduct infrmatin, enter the server mdel name. HP Insight Diagnstics HP Insight Diagnstics is a tl that displays infrmatin abut the system hardware cnfiguratin and perfrms tests n the system and its cmpnents, including drives if they are cnnected t Smart Array cntrllers. This utility is available n the SmartStart CD and als n the HP website (http://www.hp.cm/servers/diags). POST messages Smart Array cntrllers prduce diagnstic errr messages (POST messages) at rebt. Many POST messages suggest crrective actins. Fr mre infrmatin abut POST messages, see the HP PrLiant Servers Trubleshting Guide. Trubleshting resurces HP PrLiant G7 (and earlier) prducts The HP PrLiant Servers Trubleshting Guide prvides prcedures fr reslving cmmn prblems and cmprehensive curses f actin fr fault islatin and identificatin, errr message interpretatin, issue reslutin, and sftware maintenance n PrLiant servers and server blades. This guide includes Diagnsing array prblems 115

prblem-specific flwcharts t help yu navigate cmplex trubleshting prcesses. T view the guide, select a language: English (http://www.hp.cm/supprt/prliant_tsg_en) French (http://www.hp.cm/supprt/prliant_tsg_fr) Italian (http://www.hp.cm/supprt/prliant_tsg_it) Spanish (http://www.hp.cm/supprt/prliant_tsg_sp) German (http://www.hp.cm/supprt/prliant_tsg_gr) Dutch (http://www.hp.cm/supprt/prliant_tsg_nl) Japanese (http://www.hp.cm/supprt/prliant_tsg_jp) HP PrLiant Gen8 prducts The HP PrLiant Gen8 Trubleshting Guide, Vlume I: Trubleshting prvides prcedures fr reslving cmmn prblems and cmprehensive curses f actin fr fault islatin and identificatin, issue reslutin, and sftware maintenance n PrLiant servers and server blades. T view the guide, select a language: English (http://www.hp.cm/supprt/prliant_tsg_v1_en) French (http://www.hp.cm/supprt/prliant_tsg_v1_fr) Spanish (http://www.hp.cm/supprt/prliant_tsg_v1_sp) German (http://www.hp.cm/supprt/prliant_tsg_v1_gr) Japanese (http://www.hp.cm/supprt/prliant_tsg_v1_jp) Simplified Chinese (http://www.hp.cm/supprt/prliant_tsg_v1_sc) The HP PrLiant Gen8 Trubleshting Guide, Vlume II: Errr Messages prvides a list f errr messages and infrmatin t assist with interpreting and reslving errr messages n PrLiant servers and server blades. T view the guide, select a language: English (http://www.hp.cm/supprt/prliant_emg_v1_en) French (http://www.hp.cm/supprt/prliant_emg_v1_fr) Spanish (http://www.hp.cm/supprt/prliant_emg_v1_sp) German (http://www.hp.cm/supprt/prliant_emg_v1_gr) Japanese (http://www.hp.cm/supprt/prliant_emg_v1_jp) Simplified Chinese (http://www.hp.cm/supprt/prliant_emg_v1_sc) Diagnsing array prblems 116

Acrnyms and abbreviatins ACU Array Cnfiguratin Utility ADG Advanced Data Guarding (als knwn as RAID 6) ADM Advanced Data Mirrring ADU Array Diagnstics Utility CPQONLIN NetWare Online Array Cnfiguratin Utility DHCP Dynamic Hst Cnfiguratin Prtcl HBA hst bus adapter ORCA Optin ROM Cnfiguratin fr Arrays POST Pwer-On Self Test RBSU ROM-Based Setup Utility RIS reserve infrmatin sectr SAAP Smart Array Advanced Pack Acrnyms and abbreviatins 117

SAS serial attached SCSI SATA serial ATA SSD slid-state drive SSP Selective Strage Presentatin TFTP Trivial File Transfer Prtcl WBEM Web-Based Enterprise Management WWN Wrld Wide Name Acrnyms and abbreviatins 118

Dcumentatin feedback HP is cmmitted t prviding dcumentatin that meets yur needs. T help us imprve the dcumentatin, send any errrs, suggestins, r cmments t Dcumentatin Feedback (mailt:dcsfeedback@hp.cm). Include the dcument title and part number, versin number, r the URL when submitting yur feedback. Dcumentatin feedback 119

Index A actin mde, ACU scripting 72 ACU (Array Cnfiguratin Utility) 10 ACU GUI, methds fr pening 19 ACU GUI, prcedure verview 30 ACU help 28 ACU scripting 72, 76, 83 additinal infrmatin 114 ADG (advanced data guarding) 109 ADU (Array Diagnstic Utility) 114 ADU Remte Service Mde 95 advanced cnfiguratin tasks, supprt fr 6 advanced data guarding (ADG) 109 array acceleratr, enabling r disabling, ACU CLI 67 array categry ptins, ACU scripting 76 array cncepts 102 array cnfiguratin utilities, features 5 Array Cnfiguratin Utility (ACU) 10 array cnfiguratin, cpying 68, 69 Array Diagnstic Utility (ADU) 114 array, creating, ACU GUI 30, 44 array, creating, ACU scripting 72, 76 array, expanding, ACU CLI 61 array, expanding, ACU GUI 30 array, expanding, ACU scripting 76 array, healing 39 array, mving 62, 76 array, mving, ACU CLI 62 array, mving, ACU GUI 30 array, mving, ACU scripting 76 array, replacing 39, 63 array, shrinking 30, 62, 76 array, shrinking, ACU CLI 62 array, shrinking, ACU GUI 30 array, shrinking, ACU scripting 76 array, specifying, ACU scripting 76 ArrayAcceleratr 79 aut-cnfiguratin prcess 9 B bt cntrller, setting 51 bt vlume, setting 52 C cache rati, ACU CLI 67 cache rati, ACU scripting 75 CacheState 73 capturing cnfiguratins 68 chsing a RAID level 112 ClearCnfiguratinWithDataLss 74 clearing a cnfiguratin 74 CLI (Cmmand Line Interface) 45 CLI abbreviatins 48 CLI syntax 46 CLI, accessing 10, 15, 95 Cmmand Line Interface (CLI) 45 cmmand mde, pening ACU in 46 cmmand variable, ACU CLI 47 cmparisn f RAID features 111 cmparisn f the utilities 5 Cnfiguratin screen 20 Cnfiguratin tasks 28, 30 cnfiguratin tasks, advanced, supprt fr 6 cnfiguratin tasks, perfrming 30, 42, 44, 51, 68 cnfiguratin tasks, standard, supprt fr 6 cnfiguratin utilities, cmparisn f 5 cnfiguratin utilities, descriptin f 5 cnfiguratin utility, chsing 5 cnnectin name 83 cnnectin prfile 83 CnnectinName 83 cnsle mde, pening ACU in 46 cntrl categry, ACU scripting 72 cntrller duplexing 112 cntrller name 60 cntrller ptins, ACU scripting 72 cntrller, specifying, ACU scripting 73 criteria fr selecting a RAID level 112 D data prtectin methds 105, 112 data striping 102, 105 default settings 69 DeleteLicenseKey 74 deleting a device 53 Index 120

device infrmatin, btaining 49 devices, discvering 19 devices, identifying 53 diagnstic reprt 39, 40, 53, 96, 98, 99 diagnstic tls 114 diagnstics 22, 39, 40, 53 Diagnstics screen 22 Diagnstics tasks 39, 40 disabling drive cache 67 disabling the array acceleratr, ACU CLI 67 disabling the array acceleratr, ACU scripting 79 disabling the redundant cntrller 65 distributed data guarding 108 DPOEnable 75 drive array cncepts 102 drive cache, enabling r disabling 67, 74 drive infrmatin 58, 59 drive mirrring 106, 107 drive type, ACU scripting 77 DriveType 77 DriveWriteCache 74 duplexing 112 E ElevatrSrtEnable 75 enabling drive cache 67 enabling the array acceleratr, ACU CLI 67 enabling the array acceleratr, ACU GUI 30, 42 enabling the array acceleratr, ACU scripting 79 enclsure infrmatin 58 erase a drive 54 errr messages 87 example CLI script, creating lgical drive 56 exit n errr 68 exiting the ACU GUI 19 expand pririty, ACU CLI 66 expand pririty, ACU scripting 75 expanding an array, ACU CLI 61 expanding an array, ACU GUI 30, 42 expanding an array, ACU scripting 76 ExpandPririty 75 extending lgical drive capacity 63, 81 F F5 prmpt 11 failed lgical drive, re-enabling 66 fault-tlerance methds 102, 105 features f the utilities 5 frced parameter 48 G GUI, accessing 10, 15, 95 H HBA categry ptins, ACU scripting 83 HBA WWN 83 HBA_WW_ID 83 healing an array 39 help cmmand 51 help resurces 28 hiding warning prmpts, ACU CLI 48 hst mde 83 HstMde 83 HP SmartCaching 34, 35, 59 I I/O path, mdifying 64, 65, 74 identifying devices 53 infrmatin abut devices, btaining 49 Input script, using 68 installing ACU 10 Intelligent Prvisining 11 IRPEnable 75 ISO image 11, 12, 13 ISO image path, specifying 14 J Jin 77 K keywrd abbreviatins 48 L languages 5 LEDs, activating 53 license key 33, 54, 74 LicenseKey 74 lcal applicatin, using ACU as 11, 16 lgical drive capacity extensin 63, 81 lgical drive, caching 79 lgical drive, creating, ACU CLI 55 lgical drive, creating, ACU GUI 30, 42, 44 lgical drive, descriptin f 102 lgical drive, failed, re-enabling 66 lgical drive, migrating, ACU CLI 64 lgical drive, migrating, ACU GUI 30 lgical drive, migrating, ACU scripting 80, 82 Index 121

lgical drive, mving, ACU CLI 57 lgical drive, specifying, ACU scripting 79 LgicalDrive 79 M MaxBt setting 81 menu ptins, ACU GUI 30, 42 methd mde, ACU scripting 72 methds fr pening the ACU GUI 19 migrating stripe size r RAID level, ACU CLI 64 migrating stripe size r RAID level, ACU GUI 30 migrating stripe size r RAID level, ACU scripting 80, 82 mirrred arrays 36 mirrred drives 106, 107 MNPDelay 75 munting virtual media 12, 13 mving an array 62, 76 N navigating the interface 19 nested RAID 110, 111 NBatteryWriteCache 74 Nvell NetWare, cnfiguratin tl fr 5 NumberOfParityGrups 79 O ffline deplyment 10 nline deplyment 15 nline spare, ACU CLI 60 nline spare, ACU GUI 30, 42 nline spare, ACU scripting 78 OnlineSpare 77, 78 pening the ACU GUI 19 perating system supprt 10 Optin ROM Cnfiguratin fr Arrays (ORCA) 9 ptins, scripting, list f 70 ORCA (Optin ROM Cnfiguratin fr Arrays) 9 verview f cnfiguratin utilities 5 P parameters, in CLI, btaining values f 47 parity grups 79, 110, 111 physical drive write cache, enabling r disabling 67 physical drives, adding, ACU CLI 61 physical drives, adding, ACU GUI 30, 42 POST errr messages 114 PreferredPath 80 PreferredPathMde 74 prmpts, hiding, ACU CLI 48 PXE-based deplyment 13 PXELinux setup 13 Q querying a device 47 QueueDepth 75 R RAID 80 RAID level selectin criteria 112 RAID levels 105, 106, 107, 108, 109, 110, 111 RAID levels, cmparisn f features 111 RAID, sftware-based 112 RaidArrayId 74 RAID-level migratin, ACU CLI 64 RAID-level migratin, ACU GUI 30, 42 RAID-level migratin, ACU scripting 80 Rapid Parity Initializatin 32, 59 ReadCache 75 read-write rati, ACU CLI 67 read-write rati, ACU GUI 30 read-write rati, ACU scripting 75, 79 rebuild pririty, ACU CLI 65 rebuild pririty, ACU GUI 30 rebuild pririty, ACU scripting 75 RebuildPririty 75 recmbining a split mirrred array 37 redundant cntrller, disabling 65 redundant cntrller, mdifying I/O path f 64, 65, 74, 80 redundant cntrller, preferred path settings fr 64, 65, 74, 80 re-enabling a failed lgical drive 66 registering a license key 33 re-mirrring a split mirrr backup 38 remte server, cnfiguring 17 remte service, using ACU as 18 renaming a cntrller 60 Renumber 80 Repeat 81 repeat cnfiguratin 81 replacing an array 39, 63 required hardware 8 rescan 19, 54 ResurceVlumeOwner 81 running the ACU GUI 19 Index 122

S sample script 69 screen descriptin 19, 20, 22, 25, 28 script files 69 scripting mdes 68 scripting ptins 70 scripting syntax 69 Sectrs 81 selecting a RAID level 112 shrthand in CLI 48 shw (CLI cmmand) 49 shrinking an array 30, 62, 76 ShrinkSize 81 Size 81 SizeBlcks 82 Smart Array Advanced Pack (SAAP) 8 SmartSSD Wear Gauge reprt 40, 99, 100, 101 SmartStart CD as surce f ACU 11 sftware-based RAID 112 spare activatin mde 60 spare drives, ACU CLI 60 spare drives, ACU GUI 30, 42 spare drives, ACU scripting 78 Split 78 split mirrr backup 37 splitting a mirrred array 37 standard cnfiguratin tasks, supprt fr 6 standby cntrller, disabling 65 stripe size migratin, ACU CLI 64 stripe size migratin, ACU GUI 30, 42 stripe size migratin, ACU scripting 82 stripe size values 82 StripeSize 82 striping data 102, 105 StripSize 82 supprted perating systems 15 supprted tasks 6 surface scan delay 66, 75 surface scan mde 66 SurfaceScanDelay 75 SurfaceScanDelayExtended 75 SurfaceScanMde 75 syntax, CLI 46 trubleshting 114 trubleshting resurces 114 typical prcedures, ACU CLI 51 U utilities, descriptin f 5 V versin cmmand 51 vide perfrmance ptimizatin 55, 75 W warning messages 87 warning prmpts, hiding, ACU CLI 48 wizards mde, ACU GUI 41, 42 Wizards screen 25 write cache, n physical drives, enabling r disabling 67 WriteCache 75 X XML DTD 86 XML input file 85 XML utput file 84 XML supprt 84 T target device, setting 52 target variable, ACU CLI 47 tasks 28, 30, 39, 40 tasks supprted in each utility 6 Index 123