% Librarian A09-30rWvr{R|5yACCEPT VADDfDELETEEXITBFLASHHELP HPSASLOCATE MSAOverview%$READ&RESET',SCAN+SETISHOW0 SmartArrayrSTARTҋr 1 Overview C MSA_UTIL is an OpenVMS system management tool used for configuring/ and managing the following controllers:I - HP StorageWorks Smart Array Family of Storage Host Bus AdaptersN (53xx series, 64xx series, P400, P700, and P800 with Native Command ! Queuing (NCQ) Firmware) K - HP StorageWorks Modular Smart Array Family of Storage Controllers (MSA1000 and MSA1500)H These controllers  connect to HP StorageWorks Modular Smart ArrayG storage array systems, and to Integrity Server internal SCSI or SAS drives.G Note: To use MSA_UTIL utility, you need to have NETMBX, TMPMBX,D SYSPRV, DIAGNOSE, PHY_IO privileges, AUDIT privileges.wwҋr1 SmartArray 2 Restriction9 - The MSA_UTIL command "SHOW CONNECTIONS" is not E applicable or is not supported on the HP StorageWorks Smart Array Controller. B - Extend, Migrate and Expand commands on Smart Arrays willE fail if the controller cache is bad or the cache battery isE less than 75%. These commands will work on controllers thatG are designed to support volume expansion by using disk drivesF for backing up expand data stripe. This is in the absence of2 battery backed memory on the controller.E - RAID units that have spare disks (RAID 1, RAID 5 and so on)5  cannot be migrated to RAID 0 or JBOD units.G - Multiple capacity disks can be used by specifying the "/SIZE"I qualifier. The maximum value of size specified with the "/SIZE"E qualifier should be the size available on the disk with the lowest capacity. 2 Examples! MSA> SET ADAPTER PKA0:  MSA> SHOW DISKS wwҋr1 MSA2 RestrictionsJ - Extend, Migrate and Expand commands wi ll fail if the controller D cache is bad or the cache battery is less than 75%. These I commands will work on controllers that are designed to support K volume expansion by using disk drives for backing up expand data I stripe. This is in the absence of battery backed memory on the  controller.E - RAID units that have spare disks (RAID 1, RAID 5 and so on)5 cannot be migrated to RAID 0 or JBOD units.G - Multiple cap acity disks can be used by specifying the "/SIZE"I qualifier. The maximum value of size specified with the "/SIZE"E qualifier should be the size available on the disk with the lowest capacity.wwҋr 1 HPSAS= MSA_UTIL has a limited capability for configuring the1 Integrated RAID (IR) functionality on the: HP 8 Internal Port SAS Host Bus Adapter with RAID.; HP recommends using the SAS$UTIL utility instead o fB MSA_UTIL to configure the LSISAS10xx-based SAS controller.wwҋr1 ADD Format:" ADD 2 UNIT  A ADD UNIT is used to create UNITs (logical storage units/ comprising of 1 or more hard drives). Format:2 ADD UNIT / 3 Parameters 6 Unit_n (the unit number can range from 0-31) 3 Qualifiers/ADGJ  Specifies the RAID type for the UNIT as Advanced Data Guard (ADG)./CACHEH Determines whether the controller's cache should be used for theJ UNIT. Caching is ON by default. To disable caching, use a /NOCACHE6 qualifier with SET UNIT or ADD UNIT commands. /DISK H Specifies the disk numbers to be used to form the UNIT. Multiple/ disks must be enclosed in parenthesis.  Format:* /DISK=(disk numbers[,...])F Note: The disk numbers for the existing disks can be obtained + using the SHOW DISKS command. /IDENTIFIER I This is the user-defined identifier for the unit. This identifierJ is used by OpenVMS to name the device. The value of the identifier can be between 1- 9999E Note: Identifier is not required for Smart Array Controllers. Format: /IDENT= n/JBODF Specifies the RAID type to be JBOD. This is also synonymous to RAID 0. /PARTITION G Specifies the partition number to be used for a given UNIT. TheJ first unit that is created on a disk/disk group will automaticallyK be assigned the partition number 0. The units that are subsequentlyN created on this disk/disk group will need to be created with partition& numbers in a sequential order. Format:( /PART=(partition_number) /RAID_LEVEL H  Specifies the RAID type of the UNIT. The support values for this qualifier are 0,1 and 5." - RAID 0 is Data Striping# - RAID 1 is Disk Mirroring6 - RAID 5 is Data Striping with Striped Parity Format:# /RAID=[(0 | 1 | 5)]/SIZEB Specifies the size of the UNIT. When the size qualifier isC not specified, the size defaults to the Maximum capacity of6 the disks depending on the RAID level.    Format:) /SIZE=#(Gb | Mb | Kb | %)/SPARESH Specifies the disk numbers to be used as spare disk(s). MultipleH disks must be enclosed in parenthesis. Assigning a spare disk toF an unit in a drive group will assign the spare disk to all the, configured units in the drive group.F If an unit is created on a disk group to which a spare disk isH assigned, then the spare disk will be configured to the new unitG (if it is not a RAID 0 unit). One spare disk can be assigned to multiple drive groups.G Ensure that the size of the spare disk is at least equal to the7 size of the smallest drive in the drive group.  Format:* /SPARE=(disk_number[,...])F Note: The disk numbers for the existing disks can be obtained + using the SHOW DISKS command. /STRIPE_SIZE G Specifies the stripe size for a given RAID volume. Stripe sizeJ must be one of 8, 16, 32, 64, 128, and 256 values. Raid 5 and ADGL are limited to a maximum 64 KB stripes. RAID 0 and 1 default to 128B KB stripes, and RAID 5 and ADG default to 16 KB stripes. G SAS Smart Array Controllers with Firmware 5.0 onwards support ' 512 KB stripe size with RAID5. Format:& /STRIPE=(stripe_size)/VERBOSE B Provides logging that can be interpreted by engineering. 3 ExamplesA - ADD UNIT 3/ID=1003/DISK=103/JBOD/PARTITION=0/SIZE=8GBB - ADD UNIT 4/ID=1004/DISK=103/JBOD/PARTITION=1/SIZE=10GBA - ADD UNIT 5/ID=1005/DISK=103/JBOD/PARTITION=2/SIZE=8GBL In the above-mentioned examples, 3 units are being created on diskK 103. Notice that the partition numbers are provided in sequential, order on the same disk/disk group.3 Consider the following command sequence: A - ADD UNIT 3/ID=1003/DISK=103/JBOD/PARTITION=0/SIZE=8GBB - ADD UNIT 4/ID=1004/DISK=103/JBOD/PARTITION=2/SIZE=10GBJ Assuming that there is no unit with partition number '1' on thisK disk, the creation of unit 4 will fail since the unit is assignedJ the partition number '2' and the assignment is not in sequential order. 3 RestrictionsH Any two or a combination of all the following qualifiers> cannot be used in conjunction with each other: ( /RAID_LEVEL, /JBOD, /ADGwwxr 1 DELETE Format:' DELETE 2 UNIT F DELETE UNIT is used to delete UNITs. Irrespective of whetherI or not the disk is mounted on OpenVMS, you will be prompted forE confirmation before proceeding to delete the selected UNIT. I Suppose the disk is mounted on OpenVMS node, in addition to theH prompting for confirmation, you will also be informed that the disk is mounted.  Note: H - After a UNIT is deleted, its unit number remains unused7 until manually assigned to a new UNIT.J - Unit numbers are not automatically reassigned when a UNIT is deleted.M - If more than one UNIT has been created on a disk/disk group,; only the last created UNIT can be deleted.M - It is important to maintain a record of the unit numbers andJ the order in which they are created on a disk/disk group. Format:6 DELETE UNIT /  3 Parameters; Unit_n (the unit number can range from 0-31)3 Qualifiers /NOCONFIRM ; Allows the specified unit to be deleted without & prompting for confirmation./VERBOSE C Provides logging that can be interpreted by engineering. 3 Examples MSA> DELETE UNIT 4 Command options G 4 - the unit to be deleted. This is the same number that wasG given to the unit when it was created using the ADD UNIT@ command. In this example, Unit 4 will be deleted.' MSA> DELETE UNIT 4/NOCONFIRM Command options G 4 - the unit to be deleted. This is the same number that wasG given to the unit when it was created using the ADD UNITG command. In this example, Unit 4 will be deleted without+ prompting for confirmation. wwxr1 EXIT # Exits the MSA$UTIL program.  wwxr 1 FLASH Format:& FLASH 2 FIRMWARE E FLASH FIRMWARE is used to update the firmware of a givenB controller. Specify the firmware filename to be used. Format: > FLASH FIRMWARE / 3 Parameters Firmware file name3 Qualifiers/VERBOSEF Provides logging that can be interpreted by engineering.3 RestrictionsL The qualifiers /ONLINE and /TEST cannot be used in conjunction/ with each other at the same time.wwxr1 HELP Format: ! HELP 2 Examples  MSA> HELP J Displaying list of all currently supported MSA_UTIL commands: C ADD UNIT DELETE UNIT FLASH FIRMWARE LOCATE DISKS4 LOCATE UNITS LOCATE BUS LOCATE ALL  MSA> Help ADD ADD  UNIT K ADD UNIT is used to create UNITs (logical storage units9 comprising of 1 or more hard drives). Format:: ADD UNIT  6 Parameters Qualifiers Exampleswwxr 1 LOCATE Format:* LOCATE F When the above-mentioned command is executed, the LEDs ofI the requested drives will blink. These LEDs are visible from: the front of the attached storage enclosures. Note: ; - If time limit is not included with the < LOCATE command, the LEDs will blink for < 30 seconds. In some cases, the LEDs may 6 not blink but will remain steady. < - LOCATE command, does not work from the & STANDBY CONTROLLER2 ALL B LOCATE All causes all the! drives connected to the MSA) storage sub-system to flash.2 BOXC LOCATE BOX causes the disks connected to the specified> box/enclosure number to flash. 2 BUSC LOCATE BUS causes the disks connected to the specified# bus number to flash. 2 CANCEL@ LOCATE CANCEL cancels the current locate operation. 2 DISKS A LOCATE DISKS will make the specified dr "ive to flash.A Disks are identified by their corresponding SCSI busG and SCSI IDs for all the controllers. For SAS controllers,G internally connected disks are numbered based on their bayA numbers and externally connected disks are numbered E based on combination of their box number and bay number 8 as "disk_n = box number *100 + bay number".K Note: The disk numbers for the existing disks can be obtained# 0 using the SHOW DISKS command.2 UNITE LOCATE UNIT causes the disks configured to the specified unit to flash. 2 Qualifiers 3 /Time G Time value contains the time interval for which the disk's LED should flash. Format:E /TIME=xxx-(optional) the length of time to flashK the LEDs, where xxx represents the number of seconds. 3 $/VerboseE Provides logging that can be interpreted by engineering. 2 ExamplesD - Locating all drives attached to the storage enclosure Example command LOCATE ALL4 - Locating all drives in a specific BOX Example command LOCATE BOX 1 Command options:< BOX 1 - the drives in BOX 1 will be flashed.: - Locating all drives for a specifi%c SCSI bus Example command LOCATE BUS 1 Command options:L BUS 1 - all drives connected to bus number 1 will be flashed.5 - Locating all drives in a specific UNIT Example command LOCATE UNIT 1 Command options:= UNIT 1 - the drives in UNIT 1 will be flashed.' - Locating specific drives Example command & LOCATE DISK 102wwxr1 READ Format:' READ 2 FIRMWARE? READ FIRMWARE is used to read the firmware image! on the controller.B Note: Supported only for Smart Array 53xx and Smart3 Array 64xx series controllers. Format:? READ FIRMWARE /  3 Parameters! ' Firmware File Name3 Qualifiers/VerboseG Provides logging that can be interpreted by engineering.wwxr 1 RESET  Format: ( RESET 2 CONTROLLER_TYPEE RESET CONTROLLER_TYPE issues a controller reset to the$ specified controller. A Note: Applicable only for MSA1000/1500 controllers Format:C ( RESET THIS_CONTROLLER OR OTHER_CONTROLLER / #  3 Qualifiers/VERBOSEG Provides logging that can be interpreted by engineering. 3 Examples8 RESET THIS_CONTROLLER OR OTHER_CONTROLLERwwxr1 SCAN Format:( SCAN 2 ALLD Smart Array backplane RAID controllers using parallelB SCSI expect t)o be connected to enclosures that have> individual built in enclosure processors. TheseB processors or Environmental Monitoring Units (EMUs)B monitor fans, control LEDs and so on. The EMUs alsoB provide information about hot-plug events availableC in the enclosure. The Smart Array controller is thusF always aware of the insertion or removal of a SCSI diskH drive when used with such type of enclosu *res, like MSA30.F The 64xx series Smart Array card can also be cabled to C the internal parallel SCSI drives on applicable I64 G platforms. These drives are housed in an enclosure that A is totally passive with respect to hot-plug event F notification. The Smart Array controller cannot detect E that a physical disk has been hot-inserted. If a RAID H physical disk fails and must be replaced, t +he controller H will not start the recovery process on the affected RAID  volumes.G SCAN ALL command sends a SCAN message to the Smart ArrayK controller instructing the controller to scan SCSI buses andL discover new or replaced disk(s). After the SCAN is complete,D the REBUILD operation for the logical volumes will beH initiated for all the UNITs configured in the disk group. D , This command is only applicable for the internal diskG enclosure connected to the Smart Array on I64 platforms.B Note: Refer to START RECOVER command for additionalF information on rebuild of volumes. 3 Parameters None3 Qualifiers None 3 Examples MSA> SCAN ALLwwxr1 SET Format:+ S-ET  2 CONTROLLER  C SET CONTROLLER selects the controller device-name asE the default controller. The device name has the format ddcu, where: ' - dd is the device code.= - c is the controller designation A through Z.7 - u is the unit number (0 through 9999).@ Note: SET CONTROLLER command is synonymous to SET% ADA.PTER command. Format: @ CONTROLLER [DEVICE-NAME:] / 3 Qualifiers/DEFAULT+ Sets the default controller./VERBOSEG Provides logging that can be interpreted by engineering. 3 Examples- MSA> SET CONTROLLER $1$GGA105: 2 GLOBALSB SET GLOBALS is used to set the expand priority, the5 read/write ratio, and the system name. / Format:1 SET GLOBALS / 3 Parameters None3 Qualifiers/EXPAND_PRIORITYE Specifies the expansion priority for the RAID Volumes. Format:= /EXPAND_PRIORITY=(LOW | MEDIUM | HIGH) Description:B EXPAND_PRIORITY=HIGH-the expand priority. Used when> expanding an array to set the priority of arrayA expansion0s in relation to input/output operations.= See below for detailed information about these settings. /READ_CACHEC Specifies the percentage of cache to be used on READ commands. Format:9 /READ_CACHE=(AUTOMATIC | #percent) Description: ? READ_CACHE=50-the read cache. This value must be! between 0 and 100./REBUILD_PRIOR1ITYA Specifies the Rebuild priority of the RAID Volume. Format:7 /REBUILD_P=(LOW | MEDIUM | HIGH) Description:? REBUILD_PRIORITY=HIGH-the rebuild priority. UsedA when rebuilding an array to set the priority of anD array rebuild in relation to input/output operations.A Low-expansion or rebuild takes place only when the? array controller is not b2usy handling normal I/OB requests. This setting has minimal effect on normalB I/O operations. However, there is an increased risk? that data will be lost if another physical drive6 fails while the rebuild is in progress. /WRITE_CACHED Specifies the percentage of cache to be used on WRITE commands. Format:: /WRITE_CACHE=(AUTOMATIC | #percent)  D3escription:A WRITE_CACHE=50-the write cache. This value must be! between 0 and 100. /SYSTEM_NAMED Specifies the name to be assigned for the controller.F Note: This qualifier is not supported for Smart Arrays. Format:* /SYSTEM_NAME=(name) Description: G SYSTEM_NAME="XXX"-the system name, where XXX represents I any user define4d phrase, up to 20 alphanumeric characters./VERBOSEG Provides logging that can be interpreted by engineering. 3 Examples> MSA> SET GLOBALS/EXPAND_PRIORITY=HIGH/REBUILD_C PRIORITY=HIGH/SYSTEM_NAME="XXX"/READ_CACHE=50/# WRITE_CACHE=50F Note: Read_cache plus write_cache must equal 100.@ Example MSA$UTIL response for SHOW GLOBALS: ; 5 Controller: _$1$GGA1002: (DEFAULT)+ Global Parameters:. System Name: ITA8.2-1/ Rebuild Priority: high- Expand Priority: low+ Total Cache: 256MB- 25% Read Cache: 64MB/ 75% Write Cache: 192MB2 UNIT : SET UNIT modifies attributes of existing UNITs. Format:3 6 SET UNIT / 3 Parameters7 Unit_n (the unit number can range from 0-31)3 Qualifiers/ADGG Specifies the RAID type for the existing UNIT to be Advanced@ Data Guard (ADG). This qualifier should be used only C with the /MIGRATE qualifier to migrate from any existing RAID level to ADG. /CACHEK Determines whether the controller's cache should be used for theM UNIT. C7aching is ON by default. To disable caching, use a /NOCACHE9 qualifier with SET UNIT or ADD UNIT commands. /DEL_SPARE H Specifies the spare disks to be removed from use for a unit. ; Multiple disks must be enclosed in parenthesis.  Format:2 /DEL_SPARE=(disk numbers[,...])F Note: If you delete a spare disk (that is, assigned to more I than one LUNs) from one unit, then the disk specified in E 8 the DEL_SPARE qualifier will be deleted from all the & units in a disk group./DISKS; Specifies the disks to be used to form the UNIT.I Multiple disks must be enclosed in parenthesis. This qualifierH should be used only in conjunction with the /EXPAND qualifier9 to expand the disks used by the existing unit. Format:- /DISK=(disk numbers[,...])I Note: The disk numbers for 9the existing disks can be obtained . using the SHOW DISKS command./EXPANDH Allows the specified logical unit and all units in the disk/I disk group to utilize more disks. The EXPAND command does notI increase the size of the logical unit but it merely adds moreA disks, appending extra space on each individual disk.G To increase the size we need to use the "/EXTEND" qualifier% after expanding the un :it.H During expansion of units of a drive group the RAID level ofG certain units might be changed. For example, if an unit of B RAID level 1 with 2 disks is expanded to 3 disks, thenH the RAID level will change to RAID 5 as RAID 1 unit does not) support odd number of disks. J When expanding a unit with other units present on the same set@ of drives, all units will undergo volume expansion.  Format ;:= SET UNIT /EXPAND/DISK=) where Unit_n = (0-31)  Note:L - Diskrange must include both pre-expand disks andL the additional disks. Examples of diskrange are:1 101, (101,112,314,..)B - Only /DISK qualifier should be used inB conjunction with the /EXPAND qua <lifierK - The disk numbers for the existing disks can be B obtained using the SHOW DISKS command./EXTENDA Extends or increases the size of an existing logical D unit. To specify a new size for the unit, use the /SIZE C qualifier. The size specified must be greater than the F current unit size. When extending a unit with other units A present on the same set of drives, some un =its may be C moved (undergo volume expansion) to make space for the % additional size required.= Note that even though the UNIT size increases on A SET UNIT/EXTEND command completing successfully, the B increased size will reflect in OpenVMS only after the B appropriate Dynamic Volume Expansion (DVE) steps such A as SET VOLUME/LIMIT and SET VOLUME/SIZE are executed D successfully at the DCL prompt. >For more details, refer > to Chapter 9 on Dynamic Volume Expansion (DVE) in F "HP OpenVMS System Manager's Volume 1: Essentials manual".I Note: The /SIZE qualifier should be used only in conjunction - with the /EXTEND qualifier.  Format:5 SET UNIT /EXTEND/SIZE=S  K where Unit_n = (0-31) s=size in MB or GB (ex:10MB/20GB) /IDENTIFIERL Speci?fies the unit number to be used by OpenVMS. The value of the1 identifier can be between 1 and 9999. H Note: Identifier is not required for Smart Array controllers. Format: /IDENT= n/JBODI Specifies the RAID type to be JBOD. This is also synonymous to RAID 0./MIGRATEL Migrates the fault tolerance (RAID) level or Stripe size or bothO of an existing logical unit. When migrating a un@it with other unitsL present on the same set of drives, some units may undergo volume expansion. Format: N SET UNIT /MIGRATE [/RAID_LEVEL=R] [/STRIPE_SIZE=S]) where Unit_n = (0-31)# R=(0,1,5)0 S=(8,16,32,64,128,256) Note: I - /ADG or /JBOD can also be used instead of /RAID_LEVELI - Only RAID level and StriApe size can be modified using* the /MIGRATE qualifierL - Cannot migrate any RAID units (RAID 1, RAID 5 and so on)B that have spare disks to RAID 0 or JBOD units. /RAID_LEVELH Specifies the RAID type of the UNIT. The supported values for( this qualifier are 0,1 and 5.$ - RAID 0 is Data Striping% - RAID 1 is Disk Mirroring8 - RAID 5 is Data Striping with Striped Parity? B Note: /RAID_LEVEL should be used only in conjunction- with the /MIGRATE qualifier. Format:' /RAID=[(0 | 1 | 5 )]/SIZE0 Specifies the new size of the UNIT. ; Note: The /SIZE qualifier should be used only in8 conjunction with the /EXTEND qualifier.  Format:, /SIZE=#(Gb | Mb | Kb | %)/SPARESD Specifies the disk to be designated as the Sp Care disk(s).F Multiple disks must be enclosed in parenthesis. Assigning aA spare disk to an unit in a drive group will assign theE spare disk to all the configured units in the drive group.F If an unit is created on a disk group to which a spare diskE is assigned, then the spare disk will be configured to theG new unit (if it is not a RAID 0 unit). One spare disk can be- assigned to multiple drive groups.F D Ensure that the size of the spare disk is at least equal to= the size of the smallest drive in the drive group. Format:- /SPARE=(disk_number[,...])I Note: The disk numbers for the existing disks can be obtained . using the SHOW DISKS command. /STRIPE_SIZEA Specifies the new stripe size for a given RAID volume.A Stripe size must be one of 8, 16, 32, 64, 128, and 256@ values. Raid 5 anEd ADG are limited to a maximum 64 KB? stripes. SAS Smart Array Controllers with Firmware = 5.0 onwards support 512 KB stripe size with RAID5.F Note: The /STRIPE qualifier can only be used in conjunction- with the /MIGRATE qualifier. Format:( /STRIPE=(stripe_size)  /VERBOSED Provides logging that can be interpreted by engineering.3 RestrictionsI - /RAI FD_LEVEL and /STRIPE_SIZE qualifiers can only be used , with the /MIGRATE qualifier.F - The /DISK qualifier can only be used with the /EXPAND  qualifier.F - The /SIZE qualifier can only be used with the /EXTEND  qualifier.E Note: The /EXTEND, /EXPAND and /MIGRATE qualifiers can E only be used with SET UNIT command to change the 4 attributes of an existing unit. G 3 Examples% MSA> SET UNIT 0/CACHE Command optionsG UNIT 0 - the number of the unit to be modified, in this1 example, Unit 0 will be modified. B CACHE/NOCACHE - either enables or disables the useF of the array accelerator cache for the specified UNIT.0 SET UNIT 0/EXPAND/DISK=(0,1,2,3)H This command expands the number of disks used by Unit 0 = H and all the other units on the disk group. * SET UNIT 0/SPARE=(100,101)J This command sets spare to unit 0 and all the other units " on the disk group.8 SET UNIT 0/MIGRATE/RAID=1/STRIPE_SIZE=64G This command migrates the RAID level and Stripe size ofG unit 0. The other units on the disk group might go into' volume expansion state. * SET IUNIT 0/EXTENT/SIZE=6GBJ This command increases the size of Unit 0. The other unitsH on the disk group might go into volume expansion state.  E Note: Size of the UNIT cannot be decreased using the ' SET UNIT command.! SET UNIT 0/ID=100< This command sets the identifier for Unit 0.* SET UNIT 0/DEL_SPARE=(1,2)H If unit 0 has spare disks 1, 2 and 3, Jthen this command D removes the disks 1 and 2 from the spare disk list. C Hence, unit 0 will have only disk 3 as spare disk. , SET UNIT 0/DEL_SPARE=(1,2,3)H If unit 0 has spare disks 1, 2 and 3, then this command D removes all the specified disks 1, 2 and 3 from the 1 spare disk list in a disk group. wwm$r1 SHOW Format:( SHOW 2 CONNECTIONSF SHOW CONNECTIONS displays the World Wide Names of eachE Host Bus Adapter (HBA) attached to the controller. IfH connections between the HBAs and the MSA have been givenC user-defined names, these names are also displayed. Note: J - The SHOW CONNECTIONS command is applicable only for; MSA and not Smart Array controllers.J -L Use the SHOW CONNECTIONS command to verify that allJ connections to the MSA are recognized and defined. N - Use the SHOW CONNECTIONS command to display informationE about each HBA connected to the MSA, including; connection name, WWPN, and profile.  Format:8 SHOW CONNECTIONS / 3 Parameters None3 Qualifiers/VMerboseM Provides logging that can be interpreted by engineering. 3 Examples* MSA> SHOW CONNECTIONS$ Command optionsI CONNECTION NAME-the name of a specific connection to display./ Example MSA$UTIL response:) Connection Name: abc5 Host WWNN = 50060b00-001d25b5 2 Host WWPN = 50060b00-001d25b4+N Profile Name = Default$ Unit Offset = 08 Controller 1 Port 1 Status = Online8 Controller 2 Port 1 Status = Online2 CONTROLLERC SHOW CONTROLLER displays the specified controller'sC information if the controller name is provided. If E the controller name is not provided, then information> of all the connected controllers is displayed.@ O The SHOW CONTROLLER command is synonymous to the% SHOW ADAPTER command.D Note: If the context is set to a specific controllerC and the controller name is not provided, thenE SHOW CONTROLLER displays information pertainingD only to the controller to which the context is set.  Format:I SHOW CONTROLLER (Controller_name:) / <&Pqualifiers>3 Parameters Controller_name:3 Qualifiers/BUS: Displays the Bus number of the controller./BRIEF? Displays limited information of the controller./DEFAULT? Displays information of the default controller. /NODEFAULT< Displays information of all the controllers./FULLA Displays extensive information of the controller. /REVISIONE Q Displays the firmware version of the controller along@ with the default information for the controller. /SUBSYSTEM< Displays the Subsystem ID of the controller./VERBOSEH Provides logging that can be interpreted by engineering. 3 Examples $ MSA> SHOW CONTROLLERJ A default controller is not set. All matching controllers displayed' Controller: _$1$GG RA201:H MSA1000 (c) COMPAQ P56350B9IN2021 Software 4.42) Controller Identifer: 201+ NODE_ID = 500805f3-0001b660% SCSI_VERSION = SCSI-39 Supported Redundancy Mode: Active/Standby7 Current Redundancy mode: Active/Standby% Current Role: Standby* Device Port SCSI address 6 Host Port_1:9 REPORTED PORT_ID = 500805f3-0001b669D S PORT_1_TOPOLOGY = Not available to this program Cache:F 102 megabyte read cache 154 megabyte write cache8 Cache is GOOD, and Cache is enabled./ No unflushed data in cache. Battery:- Battery is fully charged.' Controller: _$1$GGA300:I MSA CONTROLLER (c) HP P56350GX3QN152 Software 6.72* Controller Identifier: T 300+ NODE_ID = 500508b3-00905ed0% SCSI_VERSION = SCSI-3M Supported Redundancy Mode: Asym Active/Active Active/StandbyG Current Redundancy mode: Asymmetrical Active/Active( Current Role: Active. Device Port SCSI address 7 Host Port_1:8 REPORTED PORT_ID = 500508b3-00905ed1C PORT_1_TOPOLOGY = Not available to this program U Cache:F 128 megabyte read cache 128 megabyte write cache8 Cache is GOOD, and Cache is enabled./ No unflushed data in cache. Battery:- Battery is fully charged.' Controller: _$1$GGA301:I MSA CONTROLLER (c) HP P56350GX3QN0FS Software 6.72* Controller Identifier: 301+ NODE_ID = 500508b3-00905ed0% SCSI_VERSION V = SCSI-3M Supported Redundancy Mode: Asym Active/Active Active/StandbyF Current Redundancy mode: Asymmetrical Active/Active' Current Role: Active- Device Port SCSI address 6 Host Port_1:7 REPORTED PORT_ID = 500508b3-00905ed9B PORT_1_TOPOLOGY = Not available to this program Cache:E 128 megabyte read cache 128 megabyte write cache7 W Cache is GOOD, and Cache is enabled.. No unflushed data in cache. Battery:, Battery is fully charged.( Controller: _$1$GGA1002:H MSA1000 (c) COMPAQ P56350A9IMN06M Software 4.42+ Controller Identifier: 1002+ NODE_ID = 500805f3-0001b660% SCSI_VERSION = SCSI-39 Supported Redundancy Mode: Active/Standby: X Current Redundancy mode: Active/Standby' Current Role: Active- Device Port SCSI address 7 Host Port_1:7 REPORTED PORT_ID = 500805f3-0001b661B PORT_1_TOPOLOGY = Not available to this program Cache:E 102 megabyte read cache 154 megabyte write cache7 Cache is GOOD, and Cache is enabled.. No unflushed data in cache. Y Battery:, Battery is fully charged. Adapter: _PKD0:E SA6400 (c) HP P57820FDAPHJE7 Software 1.923 SCSI_VERSION = X3.131:1994 (SCSI-2)' Not currently Redundant$ Current Role: Active3 (No redundant controller installed) Cache:0 128 megabyte read/write cacheB Cache is not configured, and Cache is disabled.. Z No unflushed data in cache. Battery:1 Battery is not fully charged. Adapter: _PKE0:F SA6400 EM (c) HP P577C0EDAPH3JK Software 1.923 SCSI_VERSION = X3.131:1994 (SCSI-2)' Not currently Redundant$ Current Role: Active3 (No redundant controller installed) Cache:1 128 megabyte read/write cacheC [ Cache is not configured, and Cache is disabled./ No unflushed data in cache. Battery:1 Battery is not fully charged. 2 DEVICE 3 NONDISKH SHOW DEVICE NONDISK displays the following information * for all non-disk devices: - WWID - Vendor ID - Product ID ! - Serial number H Not\e: This command is applicable only to P800 and P400 # controllers.  Format: ; SHOW DEVICE NONDISK / 3 Parameters None3 Qualifiers/VERBOSEI Provides logging that can be interpreted by engineering. 2 DISKSE SHOW DISKS displays the following information on2 all available physical disks:" ] - Disk number2 - Enclosure bus number and ID - Disk size/ - UNIT created on the disk/ - Disks assigned as spares Note: B - SHOW DISK can be used to see> information of a particular disk,D where disk_n is the disk number. Disks B are identified by their cor^respondingL SCSI bus and SCSI IDs for all the controllers. G For SAS controllers, internally connected K disks are numbered based on their bay numbers I and externally connected disks are numbered F based on combination of their box number / and bay number as F "disk_n" = box Number *100 + bay numb _er".% Examples@ For SAS controllers, the output of > SHOW DISK command is as follows:  - MSA> SHOW DISK 1? SAS device [Disk]F Disk 1: bus: 1, Target id: 7, Port: 3I, 8 Box/Enclosure: 1, Bay: 1, 1 size 68.37 [73.41]GB@ ` Disk 1, # 0, size 14329984 blocks, 6 (6.83 [7.34] GB), Unit 3.A Disk 1, # 1, size 128979218 blocks, 8 (61.50 [66.04] GB), Unused./ MSA> SHOW DISK 201@ SATA device [Disk]H Disk 201: bus: 1, Target id: 8, Port: 2E, 8 Box/Enclosure: 2, Bay: 1, 3 siz ae 149.05 [160.04]GBC Disk 201, # 0, size 312516272 blocks, : (149.02 [160.01] GB), Unused.& MSA>  F For all other controllers, the output of = SHOW DISK command is as follows: - MSA> SHOW DISK 9 C SAS device [Disk]F Disk 9: bus: 1, Tar bget id: 9, Port: 1E, L Box/Enclosure: 2, Bay: 5, size 68.37 [73.41]GB? Disk 9, # 0, size 2096640 blocks, < (1023.75 [1073.48] MB), Unit 1.? Disk 9, # 1, size 1397664 blocks, : (682.45 [715.60] MB), Unit 2.? Disk 9, # 2, size 1044256 blocks, : (509.89 [534.66] MB), Unit 3.? c Disk 9, # 3, size 1048320 blocks, : (511.88 [536.74] MB), Unit 4.A Disk 9, # 4, size 137722322 blocks, 8 (65.67 [70.51] GB), Unused.# MSA>  G - For Smart Array P400 series of controllers,E the Target id, Connector and BAY are also& displayed.  Format: 6 d SHOW DISKS / 3 Parameters None3 Qualifiers /AVAILABLEB Lists all the disks on which there are no units configured. /ENCLOSURED Displays all the disks connected to a particular  enclosure. < Note: Supported only for SAS controllers. Format:@ SHOW DISKS/ENCeLOSURE =   /FULLG Displays the drive model and the drive serial number7 in addition to the disk information.I Note: For Smart Array P400 series of controllers, the < following information is displayed:- - Connector Location$ - Connector$ - Enclosure - f Bay - WWID+ - Device Type ( - Disk Capacity( - Device Status1 - Device Vendor ID 1 - Device Product ID / - Device Serial Number2 - Device Firmware VersionA - Reserved Area (cfg/status information)4 - Block Size (bytes/sector)+ g - M&P Data Stamped. - Last Failure Reason. - Physical Disk Flags/MEMBER H Displays the disks on which the units are configured./SPARESF Displays the disks that are configured as spare for! logical units./VERBOSEK Provides logging that can be interpreted by engineering. 3 Examples" MSA> SHOW DISKS" h Other Examples: $ - SHOW DISK/SPARE( - SHOW DISK/AVAILABLE( - SHOW DISK/ENCLOSURE 2 GLOBALSH SHOW GLOBALS displays the following global parameters0 for the specified controller: - System name9 - Rebuild and expand priority settings2 - Read and write cache settings Format:6i SHOW GLOBALS / 3 Parameters None3 Qualifiers/BRIEF D Displays the global parameters information of the controller./FULLJ Displays the WWID information in addition to the global< parameters information of the controller./VERBOSEK Provides logging that can be interpreted by engineering. 3 Examplesj SHOW GLOBALS% Global Parameters:% System Name: ABC+ Rebuild Priority: high* Expand Priority: high' Total Cache: 256MB+ 50% Read Cache: 128 MB, 50% Write Cache: 128 MB$ Other Examples:= - SHOW GLOBAL/FULL ( - SHOW GLOBAL/BRIEF 2 PROFILEkA SHOW PROFILE displays all the profile names. Format: I SHOW PROFILE ["Profile_name"] / 3 Parameters! Profile_name3 Qualifiers/VERBOSEM Provides logging that can be interpreted by engineering. 3 Examples' MSA> SHOW PROFILE 2 OTHER_CONTROLLERI SHOW OTHER_CONTROLLER displays informatlion about theG controller that's either STANDBY or ACTIVE to the < controller to which the context is set.; This is not supported for SMART ARRAY.  Format:2 SHOW OTHER_CONTROLLER2 THIS_CONTROLLERD SHOW THIS_CONTROLLER displays information aboutA the controller to which the context is set. A Tmhe state of this controller could be either' ACTIVE or STANDBY.@ This is applicable for both SMART ARRAY and9 MSA1000/MSA1500 type of controllers. Format:1 SHOW THIS_CONTROLLER2 UNITI SHOW UNIT displays the following information for the$ specified UNIT:: - UNIT identifier (user-defined name)" n - UNIT status ) - Percentage rebuild K - List of the disks assigned as data disks to the UNITG - List of the disks assigned as spares to the UNIT! - RAID level - UNIT size Format: > SHOW UNIT / SHOW UNITS:G SHOW UNITS displays information of all othe logicalG volumes configured on the controller. This command8 does not take the parameter unit_n.G Note: From the CLI of MSA1000/MSA1500 controllers,I if ACLs are enabled for the UNITs with respectB to the connections (HBAs to which theseF controllers are connected), then only thoseE corresponding UNITs will be visible to thpe+ respective HBAs.J After the ACLs are enabled, if the user createsJ any UNITs on these controllers (either from CLIK or MSA_UTIL), then the user will have to set theI ACLs explicitly for these UNITs to be visible.3 Parameters Unit_n3 Qualifiers/FULLG Displays the physical configuration inforqmation ofC the UNIT in addition to the UNIT information.  /VERBOSEM Provides logging that can be interpreted by engineering. 3 Examples% SHOW UNIT 0/FULL& SHOW UNIT 1/BRIEF 2 VERSION7 SHOW VERSION displays the MSA$UTIL$ version number. Format:8 SHOW VERSION / 3 r Parameters None3 Qualifiers/FULLH Displays the WWID, firmware version and controller E revision information in addition to the MSA$UTIL version. /VERBOSEM Provides logging that can be interpreted by engineering.2 TECH_SUPPORTB SHOW TECH_SUPPORT executes the following commands in a batch mode:  - SHOWs VERSION! - SHOW CONTROLLER - SHOW GLOBAL - SHOW DISKS - SHOW UNITS" - SHOW CONNECTIONS - SHOW ACLs - SHOW PROFILE  Format:) SHOW TECH_SUPPORT3 Parameters None3 Qualifiers NonewwWvr 1 START Format: . t START 2 RECOVERJ Smart Array backplane RAID controllers using parallelH SCSI expect to be connected to enclosures that haveC individual built in enclosure processors. ThisE processor or Environmental Monitoring Unit (EMU)I monitors fans, controls LEDs and so on. The EMU alsoI provides information about hot-plug events availableI u in the enclosure. The Smart Array controller is thusG always aware of the insertion or removal of a SCSIG disk drive when used with such type of enclosures, like MSA30.I The 64xx series Smart Array card can also be cabled K to the internal parallel SCSI drives on applicable I64G platforms. These drives are housed in an enclosureK t vhat is totally passive with respect to hot-plug eventD notification. The Smart Array controller cannotG detect that a physical disk has been hot-inserted.H If a RAID physical disk fails and must be replaced,G the controller will not start the recovery process2 on the affected RAID volumes. J After replacing the bad disk(s) with the new disk(s),J w if the system is rebooted before issuing the SCAN ALLK command, then all the affected RAID volumes configuredF on these disks will move to the "VOLUME ready forJ recovery operation" state. The REBUILD operation will- not start automatically. J The "START RECOVER" command will initiate the REBUILDB operation for all the UNITs configured in the- x disk group sequentially.L Note that "hiding" the insertion of a new disk from theG controller can result in the REBUILD operation notN starting automatically, even if the controller can detectI hot-plug events, such as when connected to a MSA30. J Removing a disk while the host system is running, andM replacing the disk while the host system is powered off,K y will effectively hide the insertion. The START RECOVERH command will initiate the REBUILD operation in such% scenarios also. H This command is supported on both OpenVMS Alpha and+ OpenVMS I64 platforms.C Note: Refer to SCAN ALL command for additional= information on rebuild of volumes.  Format: * z START RECOVER3 Parameters None3 Qualifiers None 3 Examples) MSA> START RECOVER wwWvr 1 ACCEPT Format:. ACCEPT 2 UNIT> If all drives of a previously failed unit > are in working order, use this command to 9 change the state of the unit bac{k to  VOLUME_OK.> To accept media exchange on a unit marked ; as failed, issue the following command: Format:, ACCEPT UNIT <#>@ where # represents the unit number. 3 Examples' MSA> ACCEPT UNIT 2 2 UNITS= ACCEPT UNITS resets status of all failed ' units to VOLUME_OK.  Format:) ACCEPT UNITSww