HP StorageWorks 1510i User Manual

Download

HP StorageWorks 1510i Modular Smart Array Command Line

Interface user guide

active/active ﬁrmware 2.x

Part number: 383074–002

econd edition: May 2008

Legal and notice information

12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java is a US trademark of Sun Microsystems, Inc.

Aboutthisguide .......................... 9

Intendedaudience...................................... 9

Relateddocumentation.................................... 9

Documentconventionsandsymbols ............................. 10

HPtechnicalsupport.................................... 10

HP installation and conﬁgurationassistance ........................... 11

Subscriptionservice ..................................... 11

HPwebsites......................................... 11

Documentationfeedback ................................... 11

1 CLI setup and overview ....................... 13

CLIsetup......................................... 13

AccessingtheCLIthroughaSecureShell(SSH)connection.................. 13

AccessingtheCLIthroughaTelnetconnection ....................... 14

AccessingtheCLIthroughaserialconnection ....................... 15

CLIOverview....................................... 16

CLIcommandsyntax.................................. 16

Examplecommand ................................ 17

CLI commands in redundant conﬁgurations ........................ 17

CLIhelp ....................................... 17

Examplecommand ................................ 17

2Initialconﬁgurationsequence................... 19

Conﬁgurelogicaldrives .................................. 19

ConﬁguringabasiciSCSIsetup(noaccesscontrolsorauthentication)............... 20

ConﬁguringCHAPauthenticationforiSCSIconnections..................... 21

ConﬁguringAccessControlsforLUNaccess.......................... 22

EnablingiSNSdiscoveryoftheiSCSItarget.......................... 22

EnableSLPdiscoveryoftheiSCSItarget............................ 23

Conﬁgurestaticmanagementsettings............................. 23

3 Command reference . ...................... 25

Commandoverview .................................... 25

CanonicaliSCSItarget................................. 25

Alphabeticallistingofcommands .............................. 26

acceptunit ...................................... 27

addacl_entry..................................... 28

addarp ....................................... 29

addinitiator ..................................... 30

addip........................................ 31

addisns_server .................................... 32

addportal ...................................... 33

addportal_group ................................... 34

addroute....................................... 35

addspare ...................................... 36

addtarget ...................................... 37

addunit ....................................... 38

bindportal...................................... 42

bindportal_group................................... 43

1510i Modular Smart Array Command Line Interface user guide

bindunit....................................... 44

clearperf....................................... 45

deleteacl_entry.................................... 46

deletearp ...................................... 47

deleteinitiator..................................... 48

deleteip....................................... 49

deleteisns_server ................................... 50

deleteportal ..................................... 51

deleteportal_group .................................. 52

deleteroute...................................... 53

deletespare ..................................... 54

deletetarget ..................................... 55

deleteunit ...................................... 56

disablethis_controller|other_controller .......................... 58

download ﬁrmware .................................. 59

expandunit...................................... 65

extendunit...................................... 66

help......................................... 67

locate ........................................ 70

migrateunit...................................... 71

refreshisns_entries................................... 73

reset certiﬁcate .................................... 74

resetcontroller .................................... 75

resetmanagement_login ................................ 76

setacl........................................ 77

setauto_path_change ................................. 78

set certiﬁcate ..................................... 79

setdiscovery ..................................... 80

setglobals ...................................... 81

setinitiator...................................... 83

setinitiator_chap ................................... 84

setiscsi_keys ..................................... 85

setisns........................................ 87

setmanagement.................................... 88

setmanagement_login ................................. 90

setport........................................ 91

setpreferred_path................................... 92

setprompt ...................................... 93

setservice ...................................... 94

setsnmp....................................... 95

settarget_chap .................................... 96

setthis_controller|other_controller ............................ 97

setthis_controller_id|other_controller_id ......................... 98

setunit........................................ 99

setunit_id ...................................... 100

showacl_entry .................................... 101

showadu_page.................................... 102

showarp....................................... 103

showauto_path_change ................................ 104

showbox....................................... 105

showcacheinfo .................................... 106

show certiﬁcate .................................... 107

showdiscovery .................................... 108

showdisks ...................................... 109

showdrive_report ................................... 110

showeventlog..................................... 111

showglobals ..................................... 112

showinitiator..................................... 113

showip ....................................... 114

showiscsi_keys .................................... 115

showisns....................................... 116

showisns_server.................................... 117

showmanagement................................... 118

showmib2...................................... 119

showperf ...................................... 120

showport ...................................... 121

showportal...................................... 122

showportal_group................................... 123

show proﬁle ..................................... 124

showpreferred_path.................................. 125

showproxystats.................................... 126

showroute ...................................... 127

showservice ..................................... 128

showsnmp...................................... 129

showtarget...................................... 130

showtaskstats..................................... 131

showtech_support................................... 132

showtgt_stats..................................... 133

showthis_controller|other_controller ........................... 134

showunit....................................... 135

showunit_id ..................................... 137

showversion ..................................... 138

startperf....................................... 139

stopperf....................................... 140

unbindportal..................................... 141

unbindportal_group.................................. 142

unbindunit...................................... 143

A Storage overview . . . ..................... 145

Arraysandlogicaldrives.................................. 145

Fault-tolerancelevels.................................... 146

RAID0—nofaulttolerance ............................... 147

RAID1+0—drivemirroring ............................... 147

RAID5—distributeddataguarding............................ 148

RAID6—advanceddataguarding............................ 149

ComparisonofRAIDMethods................................ 149

ChoosingaRAIDlevel ................................... 150

Index .............................. 151

1510i Modular Smart Array Command Line Interface user guide

Figures

1 2 3 4

Multiplephysicaldrives(D1,D2,andD3)inasystem ................ 145

Multiple physical drives (D1, D2, and D3) conﬁgured into one logical drive (L1) . . . . . 145

Data striping (S1-S4) and data blocks (B1-B12) on multiple physical drives (D1, D2, D3) . . 146 Two arrays (A1, A2) containing ﬁve logical drives (L1 through L5) spread across ﬁve physical

drives (D1 th

RAID1array,withtwophysicalharddrives(D1,D2)................. 147

roughD5) ............................. 146

RAID 1+0 arr

RAID 5 array, with three physical hard drives (D1, D2, D3) showing distributed parity

information(Px,y)................................ 148

RAID 6 array, with four physical hard drives (D1, D2, D3, D4) showing distributed parity

information(Px,y)(Qx,y)............................. 149

ay,witheightphysicalharddrives(D1throughD8) ........... 148

Tables

Documentconventions.............................. 10

CLIspecialkeys ................................ 16

RAID0features ................................ 147

RAID1,RAID1+0features............................ 148

RAID5features ................................ 149

RAID 6 featur

SummaryofRAIDmethods............................ 150

es ................................ 149

Choosing a R

AIDlevel ............................. 150

1510i Modular Smart Array Command Line Interface user guide

About this guide

This document provides information to help you use the HP StorageWorks 1510i Modular Smart Array (MSA1510i) Command Line Interface (CLI).

Intended audi

This guide is intended for users familiar with iSCSI storage networks and, in particular, with RFC3720. If you prefer to use a Graphical User Interface (GUI), consider using the HP Storage Management Utility (SMU), described in the HP Storage Management Utility user gu ide.

ence

Document conventions and symbols

Table 1 Documen

Convention

Blue text: Table 1 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.com

Bold text

Italic text Text emphasis

Monospace text

Monospace, italic text

Monospac

e, bold text

t conventions

Element

Website addresses

• Keys that are pressed

• Text typed into a GUI element, such as a box

• GUI elements that are clicked or selected, such as

menu and list items, buttons, tabs, and check boxes

• File and directory names

• System output

• Code

• Commands, their arguments, and argument values

• Code variables

• Command variables

Emphasized monospace text

WARNING!

Indicates that failure to follow directions could result in bodily harm or death.

CAUTION:

Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT:

Provides clarifying information or speciﬁc instructions.

NOTE:

Provides a

dditional information.

TIP:

Provides helpful hints and shortcuts.

HP technical support

For worldwide technical support information, see the HP support website: http://www.hp.com/support. Before co

• Product model names and numbers

• Technical support registration number (if applicable)

• Product

ntacting HP, collect the following information:

serial numbers

About this guide

• Error messages

• Operating system type and revision level

• Detailed questions

HP installation and conﬁguration assistance

Storage management and networking knowledge is required to successfully install this product. If you are not familiar with installing and conﬁguring storage array systems, HP can install your system for you. For more information, access the HP Services website: h Portfolio banner, select Infrastructure Services > Network Storage Services.

Depending on your needs, different levels of assistance are available, such as:

• Storage depl

• Physical installation

• Logical disk design and conﬁguration

• Service pla

• Service deployment

• Installation Veriﬁcation Testing (IVT)

• Customer o

oyment

nning

rientation

ttp://www.hp.com/go/services. Under the Services

Subscription service

HP recommends that you register your product at the Subscriber’s Choice for Business website:

ttp://www.hp.com/go/e-updates.

After registering, you will receive e-mail notiﬁcation of product enhancements, new driver versions, ﬁrmware updates, and other product resources.

HP websites

For addi

•h

•http://www.hp.com/go/storage

•http:/

•http://www.hp.com/support/manuals

•http://www.hp.com/support/downloads

tional information, see the following HP websites:

ttp://www.hp.com

/www.hp.com/service_locator

Documentation feedback

HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to

storagedocsFeedback@hp.com. All submissions become the property of HP.

1510i Modular Smart Array Command Line Interface user guide

About this guide

1CLIsetupandoverview

The Command Line Interface (CLI) is used to conﬁgure and manage the array controller and its storage. Tasks include conﬁguring logical storage units (LUNs), limiting access to storage, viewing system and component information, conﬁguring iSCSI elements, and setting up the management interface.

The CLI can also be used to display system setup information and status, and, provide information on devices that are attached to the controller.

CLI setup

You can access the CLI in three ways:

• Accessing the CLI through a Secure Shell (SSH) connection

•Accessingt

• Accessing the CLI through a serial connection

NOTE:

For information about planning for and installing the MSA, connecting the hardware, and obtaining the default IP address of the management port, see the

installat

ion and user guide

he CLI through a Telnet connection

HP StorageWorks 1510i Modular Smart Array

Accessing the CLI through a Secure Shell (SSH) connection

SSH provides the most secure way to access the CLI over a network. Data transmitted through SSH is encrypted. Before using SSH, you must download and install an SSH connection utility. HP recommends using a utility called PuTTY. The following procedure describes using PuTTY.

1. If necessary, download and install the PuTTY SSH connection utility. Use an Internet search engine

to locate the latest version of PuTTY.

1510i Modular Smart Array Command Line Interface user guide

2. Launch PuTTY on a PC that is connected to the same LAN as the MSA1510i.

3. Enter the IP address of the MSA1510i management port in the Host Name (or IP address) ﬁeld.

4. Verify that the SSH radio button is selected.

5. Click Open.

The SSH shell opens and you are prompted to log on.

6. Enter your username and password.

NOTE:

When using SSH, Telnet, or the HP Storage Management Utility (SMU) to connect to the MSA1510i management port, you are required to log on. The factory default settings for username and password are both root.Theﬁrst time you log in to the MSA1510i using the default username and password, you are immediately prompted to enter a new username and password. Follow the prompts to set the new username and password. To subsequently changetheusernameandpasswordfromtheCLI,usetheset management_login command.

Accessing the CLI through a Telnet connection

CAUTION:

The Telnet protocol is not a secure method of transmitting data over a network. Because Telnet does not encrypt data, anyone with the proper knowledge and tools can read information being sent over the network. For this reason, HP recommends that you use SSH to connect to the MSA1510i over a network, or use a serial connection to connect to the MSA1510i directly.

NOTE:

Telnet is disabled by default. To enable Telnet, use the SMU. For more information, see the

Management Utility user guide

CLI setup and overview

HP Storage

1. Ensure that the Telnet interface is enabled. To enable Telnet, use the SMU. For more information, see

the HP Storage Management Utility user guide.

2. FromanyPCthatisconnectedtothesameLANastheMSA,clickStartRun to open the Run

dialog box.

3. Enter the following command:

telnet [<ip_address>] where

[<ip_address>] is the IP address of the MSA management port.

The Telnet shell opens and you are prompted to log on.

4. Enter your username and password.

NOTE:

When using SSH, Telnet, or the HP Storage Management Utility (SMU) to connect to the MSA1510i management port, you are required to log on. The factory default settings for

root

usernameandpasswordareboth default username and password, you are immediately prompted to enter a new username and password. Follow the prompts to set the new username and password. To subsequently change the username and password from the CLI, use the set management_login command.

.Theﬁrst time you log in to the MSA1510i using the

Accessing the CLI through a serial connection

Any terminal emulator program may be used to access the CLI, but the following instructions describe using Windows HyperTerminal.

1. From the front of the MSA, connect one end of the custom serial cable (included in the shipping

carton of the MSA) to the serial port of the host computer. Connect the other end to the RJ-45Z adapter on an MSA controller.

NOTE:

In dual-controller conﬁgurations, tasks can be performed through either MSA controller.

NOTE:

An additional or replacement custom serial cable can be ordered using part number 259992-001.

1510i Modular Smart Array Command Line Interface user guide

2. Open your terminal emulation software. The following instructions demonstrate using HyperTerminal:

a. Click StartRun to open the Run dialog box. Type hypertrm.exe, and then click OK.When

accessed for the ﬁrst time, the New Connection dialog box is displayed.

b. In the New Connection dialog box, type a name to associate with the connection between the

controller and the host server, and then click OK. The Connect To dialog box is displayed.

c. In the Connect To dialog box, expand the Connect using drop-down box, select the appropriate

COM port, and then click OK.TheCOMPropertiesdialogboxisdisplayed.

d. In the COM1 Properties dialog box, enter the following settings, and then click OK.

Option Setting

Bits per Second Data bits Parity Stop bits Flow contr

e. On the CLI Session screen, press Enter several times to display the command prompt (CLI>).

CLI Overview

Command strings are entered at the CLI prompt (CLI>). Commands must use a speciﬁc, preset syntax. After a declarative command is entered and executed, the results are displayed at the CLI prompt.

When using the CLI, the following keystrokes have special functions:

Table 2 CLI special keys

Keyboard Keys

Ctrl+B left arrow Moves the cursor back one character Ctrl+F right arrow

Ctrl+P

Ctrl+N down arrow

Arrow Key

up arrow

19200 8 None 1 None

Function

Moves the cursor forward one character Recalls the previous command in the

command buffer Recalls the next command in the command

buffer

CAUTION:

The CLI uses a zero-based numbering system. For example, LUN numbers begin with 0.

CLI command syntax

The following syntax describes the basic command format used for all CLI commands:

verb noun <operand 1> <operand 2> ... <operand n>

The following conventions apply to all CLI commands:

• A basic command includes a word or phrase used to instruct the controller. Commands usually

containaverbwithanoun. EveryCLIcommandmustbeginwithabasiccommand.

• CLI command strings include the basic command plus speciﬁc command parameters. Some

parameters are required; others are optional.

• CLI commands are entered at the CLI prompt.

CLI setup and overview

• Commandsarenotcasesensitiveandmustbetypedinfull.

• The CLI does not support line-continuation characters. If all characters of a command cannot

ﬁt on one line of the CLI, the command wraps to the next line on the screen. The maximum command length is 255 characters.

Example comma

The following

add unit 0 data=”disk101-disk103” raid_level=0

The basic command is add unit. The operands are:

• 0

• data=”disk101-disk103”

• raid_level=0

Some CLI comma string is considered invalid. The syntax of the parameter value is uniquely deﬁned for each CLI command, but must be less than 20 alphanumeric characters.

Some CLI comm operand is av

command has three portions: the basic command and three operands:

nds require an operand. If operands are required but are not entered, the CLI command

ands support operands that modify the command, but are not required. If a modifying

ailable but not used, a default value is used.

CLI commands in redundant conﬁgurations

When a system has two controllers, the same ﬁrmware 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 users who connect the serial port to a serial terminal.

Some CLI commands are entered from one controller's CLI prompt but are for the other controller to execute. Command syntax instructs the controller to accept user input, pass the command to the other controller, and then display the result.

The following keywords are used in the CLI to indicate a speciﬁc controller:

• this_controller—refers to the controller that the CLI is connected to.

• other_controller—refers to the other controller in the MSA.

CLI help

Help commands can be used to display helpful information about CLI commands. Displayed information may include a brief deﬁnition, required command syntax, available operands, the number of characters for a comm

The basic command is help. If a noun or verb is also entered, the display is limited to information about that speciﬁc command. If help is entered without a limiting noun or verb, the displayed lists all possible command v

Example command

To see a list of all possible command verbs and command nouns, enter help without a command verb or noun.

help To see a list of all commands, use the display_all operand:

CLI> help display_all

To see information about a speciﬁc command, enter help followed by the command in question. The following example displays information about the add unit command.

CLI> help add unit

and option value, or a list of allowed/disallowed characters.

erbs and then all possible command nouns.

1510i Modular Smart Array Command Line Interface user guide

CLI setup and overview

2 Initial conﬁguration sequence

TheMSAcanbecompletelyconﬁguredusingtheCLI.IfyouwanttousetheHPStorageManagement Unit (SMU), but the factory default management network settings do not work in your environment, see

Conﬁguring static management settings.

The example commands shown in this chapter are provided as a general reference and may differ from the commands needed for your conﬁguration. The examples show the command that is typed in at the CLI prompt and the system response. For more information on the available options for each command, see Command reference in this guide or the CLI online help.

When conﬁguring the MSA for the ﬁrst time, use the following sequence:

•Conﬁgure logical drives

•Conﬁgure a basic iSCSI setup

•Conﬁgue CHAP authentication for iSCSI connection for iSCSI connections

•Conﬁgure Access Controls for LUN access

• EnableiSNSdiscoveryoftheiSCSItarget

• Enable SLP discovery of the iSCSI target

•Conﬁguring static management settings

Conﬁgure logical drives

Before creating any logical drives, ensure that all disk enclosures are physically connected to the MSA, so that the disks are available for conﬁguration.

1. [Optional] Verify that the disks are detected by the array controller using the show disks command:

CLI> sho

Disk List: (box,bay) (B:T:L) Size Speed Units

Enclosu

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 (

Disk104 (1,04) (0:03:04) 250.0GB 160 MB/s none

Disk105 (1,05) (0:03:05) 250.0GB 160 MB/s none

Enclosur

Disk207 (2,07) (1:08:00) 72.8GB 160 MB/s none

Disk208 (2,08) (1:09:00) 72.8GB 160 MB/s none

Disk209 (

Disk210 (2,10) (1:11:00) 36.4GB 160 MB/s none

w disks

re 1: SATA (0:03:00) PROLIANT 8LCE 1.16

1,03) (0:03:03) 250.0GB 160 MB/s none

e 2: SCSI (1:06:00) PROLIANT 4LEE JB4F

2,09) (1:10:00) 72.8GB 160 MB/s none

1510i Modular Smart Array Command Line Interface user guide

2. Conﬁgure a logical drive on a set of disks using the add unit command:

CLI> add unit 0 raid_level=5 data=disk101-disk105 size=100gb

Logical Unit size = 102398 MB

RAID overhead = 25597 MB

Total space occupied by new unit = 127995 MB

Free space left on this volume: = 1064201 MB

Unit 0 is created successfully.

3. Repeat the add unit command as needed, to conﬁgure the storage in to multiple logical drives.

Conﬁguring a basic iSCSI setup (no access controls or authentication)

The example commands in this section use the simplest syntax and many default parameters. You should provide additional command arguments as required.

1. Create an IP address for iSCSI data trafﬁcusingtheadd ip command:

CLI> add ip SA0

The IP address has been added successfully.

2. Repeat the add ip command as required to conﬁgure addresses on multiple ports. Ports on the

primary controller are named SA0 and SA1. If you have a redundant array controller, the ports are named SB0

3. Use the add portal command to create an iSCSI portal that initiators will use to connect to the system:

CLI> add portal 20.20.20.5

The portal wa

Alias: portal1

4. Make a note of the portal alias, which is used in future commands to refer to the portal.

5. Create a por

CLI> add portal_group

The portal group was added successfully.

tal group using the add portal_group command:

20.20.20.5

and SB1.

s added successfully.

Alias: pg1

Tag: 0

6. Make a note of the portal group alias for use in future commands. Also make a note of the default

tag assigne

7. Create an iSCSI target using the add target command:

CLI> add target

The iSCSI ta

Name: iqn.1986-03.com.hp.storage.msa1510i.sga043600g.target1

Alias: target1

8. Make a note

9. Bind the portal to the portal group using the bind portal command:

CLI> bind portal portal1 pg1

The portal

Initial conﬁguration sequence

d to the portal group.

rget was added successfully.

of the iSCSI target node name and alias for use in future commands.

was bound successfully to the portal group.

10. Use the bind portal_group to bind the portal group to the iSCSI target just created:

CLI> bind portal_group pg1 target1

The portal group was bound successfully to the target.

11 . Bind logical drives to the iSCSI target using the bind unit command:

CLI> bind unit 0 target1 1

On Target target1:

LUN 1 mapped to Unit 0

Alias: lun1t1

12. Repeat the bind unit command as required to bind several logical drives to the target.

13 . Use the add initiator command to create an entry for the iSCSI initiator to enable it to access the

system:

CLI> add initiator iqn.1991-05.com.microsoft:myini.domain.com

The initiator was added successfully.

Name: iqn.1991-05.com.microsoft:myini.domain.com

Alias: initiator1

NOTE:

The iSCSI node name of your initiator can be found under the Initiator Settings tab of the Microsoft iSCSI Initiator control panel window.

Conﬁguration of a basic setup with a single iSCSI target, portal, and initiator is now complete. The initiator has full access to the LUNs on the target and is not required to provide any authentication information to log in.

Conﬁguring CHAP authentication for iSCSI connections

NOTE:

The steps in this section assume that you already have a basic iSCSI setup conﬁgured.

1. Set up a target CHAP secret (password) for one-way authentication using the set target_chap

command:

CLI> set target_chap target1 mychapsecret123

The CHAP settings have been applied.

2. Activate CHAP authentication for the target using the set iscsi_keys command:

CLI> set iscsi_keys target1 authentication=chap

The new values were set successfully.

3. [Optional] Set up an initiator CHAP secret for mutual authentication using the set initiator_chap

command:

CLI> set initiator_chap initiator1 inichapsecret123

The CHAP settings have been applied.

1510i Modular Smart Array Command Line Interface user guide

Conﬁguring Access Controls for LUN access

NOTE:

The steps in this section assume that you already have a basic iSCSI setup conﬁgured.

1. Use the set acl command to enable Access Controls on the target:

CLI> set acl target1 on

Access Controls Enabled

on Target target1

2. Decide whether to grant the initiator access to all LUNs on the target, or to a speciﬁcLUN,and

then do one of the following: To grant the initiator access to all LUNs on the target, use the add acl_entry command:

CLI> add acl_entry initiator1 target=target1

Allowed access to all LUNs

on Target target1

by Initiator initiator1

To grant the initiator access to a speciﬁcLUN,usetheadd acl_entry command:

CLI> add acl_entry initiator1 lun=lun1t1

Allowed Initiator initiator1

access to LUN lun1t1

NOTE:

If more LUNs are added to the target, repeat the add acl_entry command as required to include them.

Enabling iSNS

NOTE:

The steps in this section assume that you already have a basic iSCSI setup conﬁgured.

To set up iSNS, you must ﬁrst choose the method of discovering iSNS servers. Next, you must enable iSNS on the iSCSI target.

• To use DHCP discovery of iSNS servers:

a. Bydefault,theMSA1510iusesDHCPtodiscoveriSNSservers. b. Use the set discovery command to enable iSNS discovery on the iSCSI target.

CLI> set discovery target1 isns=enable iSNS enabled

• To use SLP discovery of iSNS servers:

a. Use the set isns command to change the iSNS server discovery mode:

CLI> set isns server_discovery=slp iSNS parameters set.

b. Use the set discovery command to enable iSNS discovery on the iSCSI target.

CLI> set discovery target1 isns=enable

discovery of the iSCSI target

Initial conﬁguration sequence

iSNS enabled

• To manually add iSNS servers

a. Use the set isns command to change the iSNS server discovery mode:

CLI> set isns server_discovery=manual iSNS parameters set.

b. Use the add isns_server command to add the IP address of the iSNS server:

CLI> add isns_server 20.20.20.26 The iSNS server was added successfully. Alias: isns1

c. Use the set discovery command to enable iSNS discovery on the iSCSI target.

CLI> set discovery target1 isns=enable iSNS enabled

Enable SLP disc

NOTE:

Steps in this section assume that you already have a basic iSCSI setup conﬁgured.

Use the set discovery command to enable SLP discovery on the iSCSI target:

CLI> set discovery target1 slp=enable

SLP enabled

overy of the iSCSI target

Conﬁgure static management settings

To access the MSA1510i management functionality over a network that does not use DHCP, and on which your management host cannot access the default zeroconf* IP address, you must set up a static IP address.

1. Conﬁgure management to use a static IP address using the set management command:

CLI> set management dhcp=disable ip=192.168.1.10/255.255.255.0

gateway=192.168.1.1

2. [Optional] If you have not done so already, conﬁgurealoginandpasswordforaccessing

management functionality using the set management_login command: CLI> set management_login <user_ID><password> where <user_ID>and<password> are your own unique settings.

3. [Optional] Switch management functionality to a different physical port using the set management

command:

CLI> set management port=MA1

1510i Modular Smart Array Command Line Interface user guide

4. [Optional] If required, enable access to the CLI via Telnet (not recommended) using the set service

command:

CLI> set service telnet on

CAUTION:

TheTelnetprotocolisnotasecuremethodoftransmittingdataoveranetwork.Because Telnet does not encrypt data, anyone with the proper knowledge and tools can read information being sent over the network. For this reason, HP recommends that you use SSH to connect to the MSA1510i over a network, or use a serial connection to connect to the MSA1510i directly.

Initial conﬁguration sequence

3 Command reference

Command overview

TheCLIusesthefollowingbasictypesofcommands:

add

bind

delete

help

reset

set

show

NOTE:

For a complet

help display_

NOTE:

Some CLI commands for iSCSI objects refer to an text string that refers to an object. In some cases, when an object is being added, if the alias is not speciﬁed, it is automatically generated by the CLI. In other cases, you must specify the alias.

elistofavailablecommandtypes,usethefollowinghelp command:

all

Creates new conﬁguration elements. Creates assoc Removes conﬁguration elements. Displays all possible commands or a detailed description of a speciﬁed

command. Restores the d Changes the value of conﬁguration elements. Displays detailed information about a conﬁguration element or all conﬁguration

elements in a table

iations between iSCSI elements.

efault values of conﬁguration elements.

alias

.Thealiasisaneasy-to-remember16-character

Canonical iSCSI target

The predeﬁned iSCSI target alias refers to the canonical iSCSI target, which is used during discovery. It can be used to conﬁgure authentication for discovery sessions.

CLI commands that can refer to the canonical iSCSI target are set iscsi_keys, show iscsi_keys,andset

target_chap. Other commands produce an error if the canonical target is speciﬁed. For example,

it is not po

newpage pi

ssible to delete the canonical target.

1510i Modular Smart Array Command Line Interface user guide

Alphabetical l

isting of commands

The following M

accept unit, page 27 add acl_entry, page 28 add arp,page29 add initiator, page 30 add ip, page 31 set target_chap, page 96 add isns_server,page32 set this_controller|other_controller,page97 add portal,page33 set this_controller_id, page 98 add portal_group,page34 add route, page 35 set unit_id, page 100 add spare, page 36 show acl_entry, page 101 add target, page 37 show adu_page, page 102 add unit, page 38 show arp, page 103 bind portal, page 42 show auto_path_change,page104 bind portal_group, page 43 show box,page105 bind unit,p clear perf,page45 show certiﬁcate, page 107 delete acl_entry, page 46 show discovery, page 108 delete arp,page47 show disks, page 109 delete initiator, page 48 show drive_report, page 110 delete ip, page 49 show eventlog, page 111 delete isns_server,page50 show globals, page 112 delete portal,page51 show initiator, page 113 delete por delete route,page53 show iscsi_keys, page 115 delete spare, page 54 show isns, page 116 delete target,page55 show isns_server, page 117 delete unit, page 56 show management, page 118 disable this_controller|other_controller, page 58 show mib2, page 119 download ﬁrmware, page 59 show perf, page 120 expand unit, page 65 show port, page 121 extend unit, page 66 show portal,page122 help, page 67 show portal_group,page123 locate, page 70

migrate unit, page 71 refresh isns_entries, page 73 reset certiﬁcate, page 74 reset controller, page 75 show service, page 128 reset management_login, page 76 show snmp, page 129

set acl, page 77 show target,page130 set auto_path_change, page 78 show taskstats, page 131 set certiﬁcate, page 79 set discovery,page80 show tgt_stats,page133 set globals, page 81 set initiator, page 83 set initiator_chap, page 84 show unit_id, page 137 set iscsi_keys, page 85 show version, page 138 set isns, page 87 set management, page 88 set management_login,page90 unbind portal, page 141 set port, page 91

SA1510i CLI commands are included in this section:

set preferred_path, page 92 set prompt, page 93 set service,page94 set snmp,page95

set unit,page99

age 44

tal_group,page52

show cacheinfo, page 106

show ip,pa

show proﬁle, page 124 show preferred_path,page125 show pro show route, page 127

show tech_support,page132

show this_controller/other_controller, page 134 show unit, page 135

start perf, page 139 stop perf, page 140

ge 114

xystats,page126

newpage pi

Command reference

accept unit

Description Changes the state of the unit back to VOLUME_OK. Use this command to

Syntax accept unit [<unit_number>]

Operands <unit_number>

Example

CLI> accept units NOTE: Accept Unit will cause a temporary LUN path change to this controller. [1970-01-04 15:46:39] SetPreferredPath start... owner=1, change_map=0x0, lun_to_ ctlr_map=0xFFFFFFFF Media exchange completed successfully.

CLI> [1970-01-04 15:46:40] Quiescing host I/O for LUN map 0xFFFFFFFF... Host/pr oxy I/O quiesced. [1970-01-04 15:46:40] Quiescing cache (quick)... Cache quiesced. [1970-01-04 15:46:40] Quiescing background I/O... Background quiesced. [1970-01-04 15:46:40] Flipping ownership(s)... change_map=0x0, lun_to_ctlr_map=0 xFFFFFFFF [1970-01-04 15:46:40] Processing work while quiesced... work processing complete . [1970-01-04 15:46:40] Resuming I/O... I/O Resumed.

accept media exchange on a unit previously marked as failed. The accept unit and accept units commands are identical in functionality.

accept units

[Optional] The number of the unit to be reset. If no value is entered, all units are res

et.

See also • add unit

• bind unit

• delete unit

• show unit

• set unit

• expand uni

• extend unit

• migrate unit

• set unit_

• show unit_id

• unbind unit

newpage pi

1510i Modular Smart Array Command Line Interface user guide

add acl_entry

Description Grants an initiator access to an iSCSI target or speciﬁcLUN.Ifyouspecify

Syntax add acl_entry <initiator> target=<target>

Operands <initiator>

the mapped LUN alias, the initiator is granted access to the speciﬁed mapped LUN. If you specify the target alias, all of the target’s mapped LUNs become accessible to the initiator. If more LUNs are mapped to the target at a la

NOTE:

If Access Con

-oradd acl_entry <initiator> lun=<lun>

The iSCSI alias name of the initiator.

target=<target> The iSCSI alias name of the target.

lun=<lun> The alias name of an existing mapped LUN.

ter time, use the add acl_entry command to include them.

trols are turned off, this command turns them on.

Example

CLI> add acl_entry initiator1 lun=lun1t1

Allowed Initiator initiator1 access to Mapped LUN lun1t1

See also • add unit

• bind unit

• show unit

• set unit

• accept unit

• expand unit

Command reference

newpage pi

• extend unit

• migrate unit

• set unit_id

• show unit_id

• unbind unit

1510i Modular Smart Array Command Line Interface user guide

disable this_controller|other_controller

Description In a dual-controller system, this command disables one of the controllers to

prepare it for removal. When a controller is disabled, all resources being processed by that controller are automatically failed over to the remaining controller. After a controller has been successfully disabled, the LCD panel displays a me

ssage stating that it is safe for that controller to be removed.

Syntax

Operands

Example

CLI> disable other_controller

newpage pi

disable this_controller|other_controller [reboot]

this_controller

Disables the controller through which you are accessing the CLI.

other_cont

other_controller

Disables th

reboot

[Optional] I

roller will disable the other MSA controller.

e other MSA controller.

nstead of disabling the controller, it will be rebooted.

Command reference

download ﬁrmware

Description Updates ﬁrmware on the MSA1510i controller or MSA1510i other

Syntax download firmware <mode>

Operands <mode >,wheremode equals one of the following:

components, or, updates ﬁrmware on the hard drive storage enclosures attached to the rear of the MSA1510i.

IMPORTANT:

Before using this method to update the ﬁrmware,makenoteofthe following:

•ThecustomCL establish the serial connection to the MSA. This command is not available through SSH or Telnet.

• The host com

• Although not used during the update, HP-UX environments must have an MSA ﬁber link to a switch.

• Because this updating method uses a serial connection to the MSA, it is substantially slower than other updating methods. The preferred method of updating MSA1510i ﬁrmware is with the SMU. See the

Storage Management Utility user guide

I cable, shipped with the MSA, must be available to

puter must support the 1k Xmodem (Ymodem) protocol.

for more information.

offline—uploads an MSA ﬁrmware ﬁle, used to update the MSA1510i controller, fan modules, or Environmental Monitoring Unit. Supported for useinsingleanddualcontrollerconﬁgurations, this option requires a manual power-cycle of the MSA upon completion of the update.

online—uploads an MSA1510i controller ﬁrmware ﬁle, to update MSA1510i controller ﬁrmware only. Supported for use in dual-controller conﬁgurations only, this option automatically power-cycles the MSA upon completion of the update.

xml <d|f>—uploads an inventory xml ﬁle,suchaswhenupdating ﬁrmware on SCSI hard drives in attached SCSI storage enclosures.

Supported for use in single and dual controller conﬁgurations, this option requires a manual power-cycle of the MSA upon completion of the update.

d—uses the inventory xml ﬁle to downgrade the component. f—uses the inventory xml ﬁle to update the component, such as when

updating xxx.

sc—uses a smart component to update a system component. Supported for use in single and dual controller conﬁgurations, this option requires a manual power-cycle of the MSA upon completion of the update.

Prerequisites Before updating system ﬁrmware,makenoteofthefollowing:

1510i Modular Smart Array Command Line Interface user guide

• When determining which MSA controller ﬁrmware version to use, review the requirements and

information in the Compatibility Matrix(es), release notes, and other MSA announcements.

• Because ﬁrmware updates require least one restart of the MSA array and its attached storage

enclosures, update system ﬁrmware only during a scheduled maintenance window.

• The following versions of Internet Explorer are supported:

•MSA1510iﬁrmware 1.30 or earlier: IE6.0

•MSA1510iﬁrmware 2.0 or later: IE7.0

• Before updating system ﬁrmware, stop all host trafﬁc to the array controller.

• Before updating system ﬁrmware, make sure that a recent, known good backup of all data on

the MSA array is available.

• Before updating system ﬁrmware,makesurethatacopyoftheconﬁguration, including the iSCSI

IP addressing and portal information, along with the hard drive, LUN, and target information is available.

• If it has been more than six months since you restarted your MSA storage system, HP recommends

that you power-cycle the MSA (power off, and then power on) before updating the ﬁrmware to ensure that you are working with a fresh system.

• For newly installed MSA, do not perform a ﬁrmware update until controller batteries are fully

charged.

• For existing MSA, do not perform a ﬁrmware update until you have conﬁrmed that the “host

mode” or “proﬁle” for each connection is correctly set. The host mode identiﬁes the operating system of each 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 difﬁculties after the update. Depending on your operating system environment or user preference, the host mode is set through the “connection” commands of the CLI or through the “ACL” settings of the SMU. For more information, see the CLI or SMU user documents.

• In dual controller MSA1510i conﬁgurations, you MUST log off all redundant paths to the MSA

array prior to beginning a ﬁrmware update. The update will not succeed if redundant paths are detected by the MPIO/DSM and may require multiple reboots to recover back to the original ﬁrmware version. There could also be potential loss of connection of the Internet Explorer to the management port if there are redundant paths during the ﬂash update cycle.

• In dual controller MSA1510i conﬁgurations, only one of the two MSA controllers is updated

directly. The second MSA controller is updated (cloned) when the MSA is power-cycled near the end of the updating procedure.

• Depending on the storage enclosure model attached to the MSA array (SATA or SCSI), you may

be able to update enclosure ﬁrmware or hard drive ﬁrmware through the MSA utility.

• After the update is complete, be sure to check the status of the MSA for unexpected issues.

After power-cycling the MSA array, verify the status of the connections, deﬁned proﬁle types, redundancy settings, and storage conﬁguration.

•

After the update is complete, power cycle the MSA and all of its attached hard drive storage enclosures to activate the new ﬁrmware.

IMPORTANT:

If you encounter any problems during the ﬁrmware update process, stop and contact HP technical support. See “HP technical support” on page 10 for support contact information.

Example To update MSA controller ﬁrmware or MSA storage enclosure ﬁrmware:

Command reference

1. Determine which version ﬁrmware is currently installed on the MSA by using one of the following

methods:

• With the array controller powered on, press the arrow buttons on the front of the controller until the following message is displayed: 00 Array Controller Firmware ver <version>.

• From the MSA-CLI, enter the show version command. MSA1510i Firmware Revision is included in the displayed system information.

2. Obtain the latest ﬁrmware ﬁles and save to a temporary location on the host:

a. Go to the MSA1510i support page: h

ttp://www.hp.com/support.

b. Select your language and operating system. c. The display is updated to include a list of available downloads for the speciﬁed operating system. d. If you are not yet registered, under the Subscribe to driver and support alerts banner, click Sign

up now to receive e-mail notiﬁcations about MSA ﬁrmware or hardware, driver and support alerts, advisories, and notiﬁcations. This alert notiﬁcation system is a one-way broadcasting method used to distribute important notices about HP devices.

e. Click the title description of the download option to display important information about the

update.

•ClicktheDescription tab for a brief overview about the download.

•ClicktheRelease Notes tab for detailed information about the download, including version information, compatibility information, a summary of changes, important notes, service considerations, and installation precautions.

IMPORTANT:

Besuretoreviewtheonlinereleasenotesandreadmeﬁles for last-minute notiﬁcations about the update.

f. After reviewing the release notes for update, click Download and follow the on-screen instructions

to save the download bundle to a temporary directory on the server.

NOTE:

For downloaded ISO images, create a CD from the downloaded ISO ﬁle using a CD burning tool with the ability to burn a CD from an ISO ﬁle. Do not simply copy the ISO ﬁle to a blank CD.

3. Schedule a maintenance window for the update.

4. Ensure

that there is a valid, recent backup of the system.

5. Stop all host trafﬁctotheMSAarray.

6. If the MSA has not been restarted in the last six months, power cycle the array.

1510i Modular Smart Array Command Line Interface user guide

7. Establish a serial connection to the CLI using an emulator program such as HyperTerminal.

NOTE:

the following example describes the HyperTerminal emulator program.

a. Connect the RJ-45Z end of the custom CLI conﬁguration cable to the port on the front of the

controller. One custom CLI cable is shipped with the MSA.

b. Connect the DB9 end of the CLI cable to the serial port on the host server. c. Set up a terminal emulator from the host computer using the following settings:

Serial port: Bits per second: Data bits: Parity: Stop bits: Flow control:

any open COM port 8 19200

none 1

none

d. After opening the session, press Enter several times to display the CLI command prompt.

8. At the CLI prompt, enter the following command:

CLI> download firmware <offline|online|xml>

where:

Command reference

9. On the menu bar at the top of the emulator window, select Transfer > Send File.

10. In the Send File window:

a. Click Bro

the ﬁrmwa

wse, navigate to the directory in which you placed the ﬁrmware ﬁles, and then select

re ﬁle.

b. Expand the Protocol drop-down box, and then select 1K Xmodem. c. Click Send. A 1K Xmodem status window is displayed.

11 . Wait f

or a completion message to display. ample, the following messages are displayed on the MSA controller LCD panel:

For ex

M S A 1510 i u p d a t e s :

0 updates:

MSA2

307 FIRMWARE FLASH DONE

313 FI

(Each numb

RMWARE FLASH DONE ON BOX <n>

attached storage enclosure is updated one at a time, in sequential box

er order.)

NOTE:

Do not interfere with or cancel the download process. Interrupting the download process might corrupt the ﬁrmware.

1510i Modular Smart Array Command Line Interface user guide

12. Restart the MSA and its attached storage enclosures storage system by doing the following (newly

downloaded ﬁrmware cannot be accessed until the MSA is restarted): a. Press and hold down the MSA Power On/Standby button for approximately ﬁve seconds to

place the MSA in Standby mode.

b. Power off all storage enclosures attached to the MSA. c. Wait approximately two minutes to ensure that the hard disk drives in the enclosures stop

rotating.

d. Restart all storage enclosures attached to the MSA. e. Wait approximately four minutes to allow the enclosures to complete their startup routines. f. Press and release the MSA Power On/Standby button to restart the MSA. g. Wait (up to eight minutes) for the STARTUP COMPLETE message to display on the MSA

controller LCD panel.

13. View the messages displayed on the array controller LCD panel during startup to conﬁrm that the

ﬁrmware was installed successfully and that the array controller restarts successfully.

NOTE:

In dual-controller conﬁgurations, ﬁrmware on the two controllers is compared each time theMSAchassisisrestarted.Iftheversionsaremismatched,thesystempromptstoclone the ﬁrmware on the controller with the latest version over to the controller with the earlier version ﬁrmware. (For the system to operate in a dual-controller mode, ﬁrmware on the controllers must match.)

The following message is displayed on the LCD panel of the controller with the earlier ﬁrmware:

07 CLONE FIRMWARE ? ‘<‘ = NO, ‘>’ = YES

Press the > button on the LCD panel to clone the ﬁrmware.Duringthecloningprocess, informational messages are displayed on the controller LCD panels. When the cloning process is complete, the just-updated controller automatically restarts.

newpage pi

Command reference

expand unit

Description Adds a physical drive or drives to the LUN. This enables the speciﬁed unit

Syntax expand unit <unit><disk range>

Operands <unit>

and all units o

n the same volume to utilize more disks, effectively allowing

them to increase in size.

NOTE:

Because this command affects the entire array, all LUNs made from the array are also affected.

Theunitnumber(0-31)ofanyoneoftheLUNswithinthetargetarray.Any LUN in the array can be entered to identify the array; the space is added to the array and not the LUN.

<diskrange> A range of disks to be included in the LUN. Thisrangemustincludethe pre-expansion disks as well as the additional disks to be added. The range can include a single disk, a series of consecutive disks, or multiple series of single or consecutive disks. Disks are identiﬁed as disk<xyy>, where <x>is the box number (1-3) and <yy> is the bay number (01-14). For example:

disk101

•

disk101-disk105

•

"disk101 disk112-disk202 disk314"

•

Example To expand the array containing unit 4:

CLI> expand unit 4 disk204-disk207 The actual new array capacity will be 3000MB. The array with Unit 4 is being expanded. Use “show unit 4” to monitor progress.

See also • add unit

• bind unit

• delete unit

• show unit

• set unit

• accept unit

• extend unit

• migrate unit

• set unit_id

• show unit_id

• unbind unit

newpage pi

1510i Modular Smart Array Command Line Interface user guide

extend unit

Description Adds unused, available space in an array to the speciﬁed LUN.

Syntax extend unit <u

nit><sizing option>

Operands <unit>

The LUN to whic

hthespacewillbeadded.

<sizing option>, where sizing option equals one of the following:

add_size=<x

xxx>MB|GB—Speciﬁes how much of the available space

in the array to add to the LUN, where <xxxx>representsthesize. You must specify if the size is MB or GB. If no size is speciﬁed, the maximum available sp

ace of the included disks is assigned to the array.

new_size=<xxxx>MB|GB—This option can be used instead of add_size to enter the total new size of the LUN, where <xxxx>representsthesize. YoumustspecifyifthesizeisMBorGB.

Example To extend unit 2 by 1,000 MB:

CLI> extend unit 2 add_size=1000MB The actual new volume size will be 1992MB. Unit 2 is being extended. Use “show unit 2” to monitor progress.

See also • add unit

• bind unit

• delete uni

• show unit

• set unit

• accept un

• expand unit

• migrate unit

• set unit

_id

• show unit_id

• unbind unit

newpage pi

Command reference

help

Description Displays helpful information about CLI commands. Displayed information

may include a b

rief deﬁnition, required command syntax, available operands, the number of characters for a command option value, or a list of allowed/disallowed characters. The basic comm

and is help. If a noun or verb is also entered, the display is limited to information about that speciﬁc command. If help is entered without a limiting noun or verb, the displayed lists all possible command verbs and the

n all possible command nouns.

NOTE:

? may be enter

ed in place of the word help. ? and help are

interchangeable.

Syntax help [noun][verb][display_all]

Operands <noun>

[Optional] Displays a list of all command verbs that may follow that noun.

<verb> [Optional] Displays a list of all command nouns that may follow that verb.

display_all

[Optional] Displays a list of all currently supported CLI commands.

Example help command and response

CLI> help

Possible command verbs: ? help add copy change download delete migrate expand extend accept set locate show disable refresh bind unbind reset start stop clear override

Possible command nouns: unit units profile mode spare firmware unit_id this_controller this_controller_id other_controller other_controller_id globals prompt disk bus box all cancel version disks tech_support standby preferred_path auto_path_change proxystats target_chap initiator_chap discovery isns_server isns isns_entries port ip route arp acl acl_entry initiator target iscsi_keys portal_group portal tgt_stats management service certificate management_login snmp

1510i Modular Smart Array Command Line Interface user guide

controller adu_page mib2 drive_report perf cacheinfo taskstats debug eventlog aculock Specify command word:

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 spare download firmware delete unit delete units delete spare migrate unit expand unit extend unit accept unit accept units set unit_id set this_controller set this_controller_id set other_controller set other_controller_id set globals set prompt set unit locate disk locate unit locate bus locate box locate all locate cancel show unit show units show unit_id show this_controller show other_controller show version show disks show globals show box show profile show tech_support disable other_controller disable this_controller show preferred_path set preferred_path show auto_path_change set auto_path_change show proxystats set target_chap set initiator_chap set discovery show discovery add isns_server delete isns_server show isns_server set isns show isns refresh isns_entries set port show port add ip delete ip show ip add route delete route show route add arp delete arp show arp set acl add acl_entry delete acl_entry show acl_entry bind unit unbind unit add initiator delete initiator show initiator set initiator add target delete target show target set iscsi_keys show iscsi_keys add portal_group delete portal_group bind portal_group unbind portal_group show portal_group add portal delete portal bind portal unbind portal show portal show tgt_stats set management show management set service show service set certificate reset certificate show certificate set management_login reset management_login set snmp show snmp reset controller show adu_page show mib2 show drive_report show tech_support

Command reference

show perf start perf stop perf clear perf show cacheinfo show taskstats set debug show eventlog

Example help add unit command and response

CLI> help add unit

Usage: ’add unit <#> raid_level=R

#={0-31} / R={0,1,5,6(ADG)} / X={positive integer} / S={8,16,32,64,128,256} diskrange examples: DISK101

DISKxyy: x={1,2,3} (box #) / yy={01-14} (bay #)

ex: DISK111 - disk in box 1, bay 11

max_boot is enabled by default. it can be disabled for OS’s that don’t

support the creation of bootdrives > 4GB cache is enabled by default. enables/disables cache for the new unit. add unit creates a new logical unit using the specified settings

data=diskrange

[spare=diskrange] [stripe_size=S] [size=X<GB|MB>] [max_boot=<enable/disable>] [cache=<enable/disable>]

DISK101-DISK105

"DISK101 DISK112-DISK202 DISK314"

newpage pi

1510i Modular Smart Array Command Line Interface user guide

locate

Description Helps you locate speciﬁc hardware by ﬂashing the LEDs of the drives in the

requested hardware. These LEDs are visible from the front of the storage enclosures.

Syntax locate <option> [time=<time>]

Operands <option>, wh

ALL—Flashes the LEDs of all drives connected to the MSA storage sub-system.

BOX <x>—Flashes the LEDs of the drives in the speciﬁed box.

BUS <x>—Fla

where <x> is the bus number.

DISK <x>—Fl number.

UNIT <x>—F <x>istheunitnumber.

CANCEL—Di

time=<time>

] The length of time, in seconds, to ﬂash the LEDs. If no value is

the default value of 30 seconds is used.

Example To ﬂash the

[Optional speciﬁed,

drive LEDs in box 1 for 10 seconds:

ere option equals one of the following:

shes the LEDs of the drives connected to the speciﬁed bus,

ashes the LEDs of the speciﬁed drive, where <x>isthedrive

lashes the LEDs of the drives in the speciﬁed unit, where

scontinues the ﬂashing of the drive LEDs.

CLI> locat

newpage pi

Command reference

e box 1 time=10

migrate unit

Description Migrates an ex

move to an unsu

isting LUN from one RAID level to another. If you attempt to

pported RAID conﬁguration for a LUN, an error message

is displayed.

NOTE:

Before changing the RAID level or stripe size of a LUN, verify there is available, unused space on the array. Migrating from one RAID level to another may require additional space for parity and organizational purposes.

Syntax migrate unit <unit> raid_level=<raid level>

[stripe_size=<size>]

Operands <unit>

The number (0-31) of the LUN to modify.

raid_level=<raid level> The RAID fault-tolerance level to use. RAID levels include:

• 0 = RAID 0 (no fault tolerance)

• 1 = RAID 1 (mirroring)

• 5 = RAID 5 (distributed parity)

• 6 = RAID 6 (Advanced Data Guarding)

NOTE:

If more than one pair of drives are included in a RAID 1 array, the data is striped across the ﬁrsthalfofthedrivesinthearrayandthen each drive is mirrored to a drive in the remaining half of the drives for fault tolerance. This method is referred to as RAID 1+0.

stripe_size=<size> [Optional]Thestripesizetoassign(inKB).Optionsinclude:

• RAID0usesstripesizes8,16,32,64,128,and256(Default:128KB)

• RAID1usesstripesizes8,16,32,64,128,and256(Default:128KB)

• RAID 5 uses stripe sizes 8, 16, 32, and 64 (Default: 16 KB)

• RAIDADGusesstripesizes8,16,32,and64(Default:16KB)

Example Tomigrateunit0toRAID5withastripesizeof32KB:

CLI> migrate unit 0 raid_level=5 stripe_size=32 The RAID level of Unit 0 will now be 5. Unit 0 is being migrated. Use “show unit 0” to monitor progress.

See also • add unit

• bind unit

• delete unit

1510i Modular Smart Array Command Line Interface user guide

newpage pi

• show unit

• set unit

• accept unit

• expand unit

• extend unit

• set unit_id

• show unit_id

• unbind unit

Command reference

refresh isns_entries

Description Re-registers all iSNS-enabled targets with all iSNS servers.

Syntax

Operands None

Example

CLI> refresh isns_entries Refreshed the iSNS entries.

newpage pi

refresh isns_

entries

1510i Modular Smart Array Command Line Interface user guide

reset certiﬁcate

Description Removes the SSL certiﬁcate being used by the management interface and

resets the system to using an internally-generated, self-signed certiﬁcate.

Syntax

reset certifi

cate

Operands None

Example

CLI> reset certificate WARNING: You are about to delete your SSL certificate from the system and reset it to using a default self-signed certificate! Please ensure you have backed up your certificate and private key if you need to use them in the future! Are you sure you want to proceed [Y/n]? Y SSL certificate deleted.