HP StorageWorks 1000/1500 Modular Smart Array Command Line Interface user guide This guide details the Command Line Interface (CLI), which is used to configure and manage the following products: — HP StorageWorks 1000 Modular Smart Array (MSA1000) — HP StorageWorks 1500 Modular Smart Array (MSA1500) Part number: 347282–004 Fourth edition: June 2007
Legal and notice information © Copyright 2002-2007 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . . . . . . . . . . . . HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-authorized reseller. . . . . . . . . . . . . . . . . . . . . . . . .
Basic command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example command and response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example command and response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1 2 3 4 5 6 7 8 Tables 1 2 3 4 5 6 7 8 6 Multiple physical drives (D1, D2, and D3) in a system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Multiple physical drives (D1, D2, and D3) configured into one logical drive (L1) . . . . . . . . . . . . . . . . . 45 Data striping (S1-S4) and data blocks (B1-B12) on multiple physical drives (D1, D2, and D3). . . . . . . .
About this guide This user guide provides information to help you use the MSA Command Line Interface (CLI). Intended audience This book is intended for use by administrators with a moderate amount of SAN-management experience.
Indicates that failure to follow directions could result in bodily harm or death. WARNING! CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: NOTE: TIP: 8 Provides clarifying information or specific instructions. Provides additional information. Provides helpful hints and shortcuts.
HP technical support Telephone numbers for worldwide technical support are listed on the HP support website: http://www.hp.com/support/. Collect the following information before calling: • Technical support registration number (if applicable) • Product serial numbers • Product model names and numbers • Applicable error messages • Operating system type and revision level • Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored.
1 Overview and setup The Command Line Interface (CLI) is used to configure and manage the MSA array controller and its storage. Some configuration and management tasks include configuring storage units (LUNs), limiting access to the storage, and viewing information on MSA components (controller, unit, and cache). In addition, the CLI can be used to display system setup information and status. It may also provide information on devices that are attached to the controller.
CLI commands in redundant configurations When an MSA has two controllers, the same firmware image is run on both controllers. The two controllers communicate with each other through a PCI bus called the inter-controller link (ICL). Each controller has a serial port and has a CLI available to the users who connect the serial port to a serial terminal. Some CLI commands are entered from one controller’s CLI prompt but are executed from the other controller.
Overview of CLI storage configuration procedures When using the CLI to initially configure the MSA controller and its storage, use the following sequence: 1. Create the LUNs. See ”LUN-related commands” on page 25 for command descriptions. NOTE: OpenVMS environments must assign a unique ID number to each LUN. See ”Assigning a name or ID to a LUN” on page 28 for instructions. 2. Enter array controller settings, including global parameters. See ”Global commands” on page 35 for command descriptions.
Accessing the CLI The CLI is accessed through a host computer connected to the serial port of an MSA controller. Use the following steps to establish a serial connection to the controller: 1. Make sure there is an MSA controller installed in Slot 1 of the unit (Slot 1 is located on the front right of the unit). In multipathing configurations, two MSA controllers must be installed. 2. Connect the MSA controller to a host using the custom serial cable included in the shipping carton of the MSA.
The COM Properties dialog box is displayed. d. Enter the following settings, and then click OK. Bits per Second: 19200 Data bits: 8 Parity: None Stop bits: 1 Flow control: None The CLI input screen is displayed. e. Press Enter several times to display the command prompt (CLI>). Commands can now be entered at this CLI prompt.
Overview and setup
2 Using the CLI Managing and configuring the MSA and its storage includes configuring LUNs, entering connection information, limiting access to the storage, and viewing information about the configuration. This chapter is organized in the order in which the commands are used when configuring a new MSA installation.
Example help display_all command and response CLI> help display_all Displaying list of all currently supported CLI commands: ? help add unit add units add connection add acl add profile copy profile change mode add spare download firmware delete unit delete units delete connection delete acl delete profile delete spare migrate unit expand unit extend unit accept unit accept units rename connection set unit_id set this_controller set this_controller_id set other_controller set othe
Show commands The show command is used to view MSA configuration and status information. A few samples are provided in the following paragraphs.
Example show disks command and response for an MSA1500 CLI> show disks Disk List: (box,bay) (B:T:L:) Enclosure 1: SATA Size Speed SATA PROLIANT 8LCE Units Disk101 (1,01) (0:03:01) 250.0GB 160 MB/s none Disk102 (1,02) (0:03:02) 250.0GB 160 MB/s none Disk103 (1,03) (0:03:03) 250.0GB 160 MB/s none Disk104 (1,04) (0:03:04) 250.0GB 160 MB/s none Disk105 (1,05) (0:03:05) 250.0GB 160 MB/s none Disk106 (1,06) (0:03:06) 250.
Example show globals command and response CLI> show globals Global Parameters: System Name: MSA-1 Rebuild Priority: medium Expand Priority: medium Surface Delay: 3.0 seconds Total Cache: 256MB 50% Read Cache: 128 MB 50% Write Cache: 128 MB Temperature: EMU: 30 Celsius, 86 Fahrenheit PS1: 40 Celsius, 104 Fahrenheit PS2: 40 Celsius, 104 Fahrenheit Example show version command and response CLI> show version MSA 1500 Firmware Revision: 6.
Example show version -all command and response CLI> show version -all MSA 1500 Firmware Revision: 5.10b414 (SGA0434084) MSA 1500 Firmware Revision: 7 [AutoRev: 0x010000] Fibre Module AutoRev: 0x020000 SCSI I/O Module Bus 0 Revision: 2.02 SCSI I/O Module Bus 1 Revision: 2.02 SCSI I/O Module Bus 2 Revision: 2.02 SCSI I/O Module Bus 3 Revision: 2.02 Fan Control Module A Revision: 2.38 Fan Control Module B Revision: 2.
Example show this_controller command and response CLI> show this_controller Controller 1 (right controller): MSA1500 c Hewlett-Packard xxx Version 6.86 Build 122 Hardware 7 Component Enclosure. Controller Identifier: NODE_ID=yyyyyyyy-yyyyyyyy SCSI_VERSION=SCSI-3 Supported Redundancy Mode: Active/Standby Asm-Active/Active Current Redundancy Mode: Asym-Active/Active Device Port SCSI address 6 Terminal speed for the CLI is set to 19200.
Example show connections command and response NOTE: Use the show connections command to verify that all connections to the MSA are recognized and defined, including the profile type.
LUN-related commands The following commands are used to physically locate specific hard drives in a LUN as well as create, delete, and modify storage LUNs.
Creating LUNs A LUN is a logical storage unit comprised of one or more hard drives. When a LUN is initially created, the LUN Unit ID is automatically set to the same number assigned to the LUN. If desired, this LUN ID name can be changed. See ”Assigning a name or ID to a LUN” on page 28 for procedural information. The basic command is add unit. A variety of options are available to modify the command.
IMPORTANT: Maintain a record of the units as they are created. These unit numbers are used in other CLI commands. In addition to recording the unit number, the drives included, RAID type and size, record the order in which they are created. Example command and response to create a single LUN from a group of drives CLI> add unit 0 data=”disk101-disk107 disk110” raid_level=6 stripe_size=64 First volume to be configured on these drives.
Example command and response to create a LUN with an assigned spare CLI> add unit 4 data=”disk211-disk212” raid_level=1 spare=”disk213” First volume to be configured on these drives. Logical Unit size = 69460 MB RAID overhead = 69460 MB Total space occupied by new unit = 138920 MB Free space left on this volume = 0 MB Unit 4 is created successfully. Assigning a name or ID to a LUN If desired (or required by your operating system), each LUN can be assigned a unique name or ID, in addition to its number.
Adding a spare to an existing LUN Basic command add spare unit=<#> Command options #—the unit to assign the spare to. This is the same number that was given to the unit when it was created with the add unit command. diskrange—indicates the drives to assign as the spare to the LUN. Disks are identified by box number and bay number.
Deleting spares Basic command delete spare unit <#> Command options unit #—the unit that will no longer have access to the spare. This is the same number that was given to the unit when it was created with the add unit command. diskrange—the spare drive or range of spares to remove from use. Disks are identified by box number and bay number.
Extending a LUN CAUTION: In an HP-UX environment, extending a LUN as described in this section is not supported. See the HP-UX documentation for instructions on extending LUNs on an HP-UX system. To incorporate unused, available space in an array to a specific LUN: Basic command extend unit <#> [new_size=syy|add_size=syy] Command options #—the LUN to which the space will be added.
The RAID level of Unit 0 will now be 5. Unit 0 is being migrated. Use “show unit 0” to monitor progress. Changing the cache setting for a LUN To enable or disable the array accelerator cache for a specific LUN: Basic command set unit <#> Command options #—the number of the LUN to modify. In this example, LUN 0 will be modified. cache=enable|disable—either enables or disables the use of the array accelerator cache for the specified LUN.
Example command and response CLI> set preferred_path this_controller 0-9 SetPreferredPath start... change_map=0x2FF, lun_to_ctlr_map=0x3FF POST_Do_Msg: 67 CACHE HARDWARE TEMPORARILY DISABLED Quiescing host I/O for LUN map 0xFFEFF... Host/proxy I/O quiesced... Quiescing host I/O for LUN map 0xFFF00100... Host/proxy I/O quiesced... Quiescing cache flush task... Quiescing background I/O... Background quiesced... Flipping ownership(s)...
Enabling/disabling automatic path switching NOTE: This command is available only with active/active firmware (v6.x or later). If implicit path changes are enabled, controller firmware will automatically determine and, as needed, switch controller paths for units based on host request load, according to the specified preferences. Basic command set auto_path_change [prp=#] [mnr=#] [twp=#] [twl=#] Command options enable|disable—enables or disables implicit path switching.
Global commands The CLI provides the ability to configure the MSA controller, enter global settings, and perform system-wide commands, including: • Setting global variables • Setting the controller ID • Setting hard addressing • Changing the CLI prompt • Updating MSA firmware • Disabling a controller for removal • Overriding the ACU lock • Enabling or disabling debug console logging Setting global variables A single command with a variety of parameters is used to set the expand priority, the read/write rat
Example command and response CLI> set globals expand_priority=medium rebuild_priority=medium system_name=”MSA-1” read_cache=50 write_cache=50 Global Parameters: System Name: MSA-1 Rebuild Priority: medium Expand Priority: medium Total Cache: 256MB 50% Read Cache: 256MB 50% Write Cache: 256MB Setting the controller ID This command can be used to assign a unique name to each controller installed in the MSA. NOTE: In OpenVMS environments, a unique identifier must be assigned to each MSA controller.
Changing the CLI prompt To temporarily change the CLI prompt from the default of “CLI>”: Basic command set prompt Command options new_prompt—the user-defined name for the prompt (up to 24 alphanumeric characters). Example command and response CLI> set prompt MSA-1 MSA-1> Updating MSA firmware Periodically, HP releases updated versions of MSA controller firmware. Updates may include: additional features and functions, performance enhancements, and fixes to known issues.
• For newly installed MSA, do not perform a firmware update until the controller batteries are fully charged. • For existing MSA, do not perform a firmware update until you have confirmed that the “host mode” or “profile” for each connection is correctly set. The host mode identifies the operating system of each HBA connection to the storage. Do not use the “default” setting. If the host mode is not properly set, hosts may lose access to the storage or experience other difficulties after the update.
NOTE: In dual-controller configurations, firmware on the two controllers is compared each time the MSA chassis is restarted. If the versions are mismatched, the system prompts to clone the firmware on the controller with the latest version over to the controller with the earlier version firmware. The following message is displayed on the LCD panel of the controller with the earlier firmware: 07 CLONE FIRMWARE ? ‘<‘ = NO, ‘>’ = YES Press the > button on the LCD panel to clone the firmware.
Host connection commands Each time the MSA is powered on, all active HBA connections to the MSA are automatically detected and identified by their WWPN. Before a host accesses the storage of the MSA, you must identify the operating system (host mode) of each connection. HP also recommends assigning a user-defined name to each connection, to make the identification and setup of each connection easier. After connections are established, be sure to restrict access to the LUNs to specific hosts.
Changing the profile of a connection To change the operating-system profile associated with an existing connection (or to change the HBA of a connection): NOTE: The connection profile is sometimes referred to as the Host Mode. Basic command set connection [wwpn=xxxxxxxx-xxxxxxxx] [profile=profile_name] [offset=offset_value] Command options ConnectionName—the name of the connection to modify. wwpn=xxxxxxxx-xxxxxxxx—the WWPN of the connection to modify, using the WWPN of the HBA.
Deleting the user-defined name of a connection To remove the user-defined name associated with a connection to a host: Basic command delete connection Command options connection_name—the nickname that was assigned to the HBA within the host. Example command and response CLI> delete connection MSA-1 Connection(s) has been deleted successfully. Creating a new profile This command creates a new host profile.
Changing the profile mode This command changes a host profile mode based on the number of the mode that is displayed in the show profile command. CAUTION: Use only under the advise of an authorized customer support technician. Basic command change mode Command options profileName—the name of an existing profile. hostModeNumber—the number that is displayed next to the mode in the show profile command.
Adding to the ACL Two methods of entering LUN assignments are available: • Adding to the ACL using the connection name • Adding to the ACL using the WWPN Basic command add acl -oradd acl Command options connection=name—the name of the connection to grant access. connection=wwpn=xxxxxxxx-xxxxxxxx—the wwpn of the connection to grant access. unit=#—the LUN or range of LUNs to assign to the indicated host.
A Storage overview Arrays and logical drives The capacity and performance of a single physical (hard) drive is adequate for home users. However, business users demand higher storage capacities, higher data transfer rates, and greater protection against data loss when drives fail. Connecting extra physical drives (Figure 1) to a system increases the total storage capacity but has no effect on the efficiency of read/write (R/W) operations. Data can still be transferred to only one physical drive at a time.
For data in the logical drive to be readable, the data block sequence must be the same in every stripe. This sequencing process is performed by the array controller, which sends the data blocks to the drive write heads in the correct order. A natural consequence of the striping process is that each physical drive in a given logical drive will contain the same amount of data.
RAID 0—No fault tolerance A RAID 0 configuration (Figure 3) provides no protection against data loss when a drive fails. However, it is useful for rapid storage of large amounts of non-critical data (for printing or image editing, for example), or when cost is the most important consideration. Table 3 RAID 0 features Advantages Disadvantages Highest write performance of all RAID methods. All data on the logical drive is lost if a physical drive fails.
In each mirrored pair, the physical drive that is not busy answering other requests answers any read requests that are sent to the array. (This behavior is called load balancing.) If a physical drive fails, the remaining drive in the mirrored pair can still provide all the necessary data. Several drives in the array can fail without incurring data loss, as long as no two failed drives belong to the same mirrored pair.
B1 B2 P1,2 Q1,2 B3 P3,4 Q3,4 B4 P5,6 Q5,6 B5 B6 Q7,8 B7 B8 P7,8 D1 D2 D3 D4 15317 Figure 8 RAID 6 array, with four physical hard drives (D1, D2, D3, and D4) showing distributed parity information (Px,y)(Qx,y) This method is most useful when data loss is unacceptable, but cost is also an important factor. The probability that data loss will occur when arrays are configured with RAID 6 is less than when they are configured with RAID 5.
Comparison of RAID methods Table 7 summarizes important features of the different RAID levels.
Index A Access Control Lists See ACL ACL adding to with the CLI 44 commands 43 deleting from, with the CLI 44 viewing, with the CLI 43 ADD ACL command 44 ADD CONNECTION command 40 ADD PROFILE command 42 ADD UNIT command 26 array controller configuration, with the CLI 35 arrays and logical drives 45 audience 7 authorized reseller, HP 9 C cache, enabling/disabling per LUN with the CLI 32 CHANGE MODE command 43 CLI ACL commands 43 ACL, adding to 44 ACL, deleting from 44 ACL, viewing 43 ACU, overriding lockout
EXTEND UNIT command 31 symbols in text 8 F T fault tolerance methods 46 flashing LEDs, with the CLI 25 technical support, HP 9 text symbols 8 G W global controller settings, changing with the CLI 35 websites HP documentation 7 HP storage 9 HP Subscriber’s choice 9 H hard addressing, setting 36 hard drives, locating with the CLI 25 help, obtaining 9 HP authorized reseller 9 storage website 9 Subscriber’s choice website 9 technical support 9 Hyper Terminal, setting up 14 I inter-controller link, de
