Storage System Scripting Utility AA-RU5HC-TE-V31

Reference Guide
hp StorageWorks Storage System Scripting Utility

Enterprise Virtual Array
Product Version: 3.1 Fourth Edition (October 2003) Part Number: AA-RU5HC-TE
This guide describes the commands available in the Storage System Scripting Utility (SSSU) for the Enterprise Virtual Array v3.010. These commands configure and control HSV controllers.
Copyright 20012003 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. This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information contained in this document is subject to change without notice. Compaq Computer Corporation is a wholly-owned subsidiary of Hewlett-Packard Company. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Intel and Celeron are U.S. registered trademarks of Intel Corporation. Intel and Itanium are trademarks or registered trademarks of Intel Corporation in the U.S. and other countries and are used under license. Intel Itanium Processor Family is a trademark in the U.S. and other countries and is used under license. Microsoft, MS-DOS, MS Windows, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered U.S. trademark of Oracle Corporation, Redwood City, California. UNIX is a registered trademark of The Open Group. Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information is provided as is without warranty of any kind and is subject to change without notice. The warranties for Hewlett-Packard Company products are set forth in the express limited warranty statements for such products. Nothing herein should be construed as constituting an additional warranty. Printed in the U.S.A.
Storage System Scripting Utility Enterprise Virtual Array Reference Guide Fourth Edition (October 2003) Part Number: AA-RU5HC-TE
contents
About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Text Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 HP Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 HP Storage Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 HP Authorized Reseller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Formatting and Output of Returned Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Installing the Storage System Scripting Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Installing the HP-UX Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 To Execute SSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Installing the IBM Host Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 LINUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Novell NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 OVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 SUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 TRU64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 To Execute SSSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Starting the Storage System Scripting Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Understanding Paths and Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Contents
Storage System Scripting Utility Enterprise Virtual Array Reference Guide
Contents
SSSU Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Command Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 ADD COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 ADD DR_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 ADD DISK_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 ADD FOLDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 ADD HOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 ADD LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 ADD SNAPSHOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 ADD SYSTEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 ADD VDISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 CAPTURE CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 CAPTURE VALIDATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 DELETE DR_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 DELETE DISK_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 DELETE FOLDER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 DELETE HOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 DELETE LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 DELETE SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 DELETE VDISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 EMVERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 RESTART. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 SELECT MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 SELECT SYSTEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 SET DR_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 SET DISK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 SET DISK_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 SET FOLDER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 SET HOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 SET MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 SET OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Contents
SET SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 SET VDISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 SHOW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 SHOW DR_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 SHOW DISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 SHOW DISK_GROUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 SHOW HOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 SHOW LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 SHOW MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 SHOW MONITOR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 SHOW OPTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 SHOW POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 SHOW SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 SHOW VDISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 SHOW WORLD_WIDE_NAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 A Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Creating a Simple Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Creating the Storage System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Creating and Presenting a Virtual Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Using the SHOW Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 SHOW SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 SHOW VDISK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 SHOW HOST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 SHOW LUN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Tables 1 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Contents
about this guide About this Guide

About this Guide
This reference guide describes the HP StorageWorks Storage System Scripting Utility (SSSU) commands. About this Guide topics include:

Intended Audience, page 8 Related Documentation, page 9 Conventions, page 10 Getting Help, page 12
About this Guide
Intended Audience
This guide is intended for storage administrators who are experienced with the following:

Enterprise Virtual Array v3.0 and v3.010 Configuration of SAN fabrics Windows 2000, Windows NT, Sun Solaris, OpenVMS, Tru64 UNIX, HP-UX, and IBM AIX operating systems
About this Guide
Related Documentation
This section lists documents that provide additional information:
HP SANworks Host Operating System v3.0 Kit for Enterprise Virtual Array Installation and Configuration Guide (available for Sun Solaris, IBM AIX, Windows, Tru64 UNIX, OpenVMS, and HP-UX) HP SANworks Host Operating System v3.0 Kit for Enterprise Virtual Array Release Notes (available for Sun Solaris, IBM AIX, Windows, Tru64 UNIX, OpenVMS, and HP-UX) HP StorageWorks Enterprise Virtual Array Users Guide HP StorageWorks Enterprise Virtual Array - How to Get More Information HP StorageWorks Enterprise Virtual Array Release Notes HP StorageWorks Enterprise Virtual Array Storage System Read Me First HP StorageWorks Enterprise Virtual Array Storage System World Wide Name Label HP StorageWorks Interactive Help for command view eva HP StorageWorks Enterprise Virtual Array Configuration Guide HP StorageWorks Enterprise Virtual Array Upgrade Instructions HP StorageWorks Enterprise Virtual Array License Instructions HP StorageWorks Enterprise Virtual Array Catalog of Associated Documentation HP StorageWorks Enterprise Virtual Array Storage System Installation Instructions HP StorageWorks Heterogeneous Open SAN Design Reference Guide
About this Guide
Conventions
Conventions consist of the following:

Document Conventions Text Symbols
Document Conventions
The document conventions included in Table 1 apply in most cases.
Table 1: Document Conventions Element Cross-reference links Key and field names, menu items, buttons, and dialog box titles File names, application names, and text emphasis User input, command and directory names, and system responses (output and messages) Variables Website addresses Convention Blue text: Figure 1
Bold Italics Monospace font COMMAND NAMES are uppercase monospace font unless they are case sensitive <monospace, italic font> http://www.hp.com
Blue, underlined sans serif font text:
Text Symbols
The following symbols may be found in the text of this guide. They have the following meanings.
WARNING: Text set off in this manner indicates that failure to follow directions in the warning could result in bodily harm or death.
10
About this Guide
Caution: Text set off in this manner indicates that failure to follow directions could result in damage to equipment or data.
Note: Text set off in this manner presents commentary, sidelights, or interesting points of information.
11
About this Guide
Getting Help
If you still have a question after reading this guide, contact an HP-authorized service provider or access our website: http://www.hp.com.
HP Technical Support
Telephone numbers for worldwide technical support are listed on the following HP website: http://www.hp.com/support/. From this website, select the country of origin.
Note: For continuous quality improvement, calls may be recorded or monitored.
Be sure to have the following information available 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
HP Storage Website
The HP website has the latest information on this product as well as the latest drivers. Access storage at: http://www.hp.com/country/us/eng/prodserv/storage.html. From this website, select the appropriate product or solution.
HP Authorized Reseller
For the name of your nearest HP-authorized reseller:

In the United States, call 1-800-345-1518 In Canada, call 1-800-263-5868 Elsewhere, see the HP website for locations and telephone numbers: http://www.hp.com.
12
Introduction
This chapter introduces the HP StorageWorks Enterprise Storage System Scripting Utility (SSSU) v3.1 for the HP StorageWorks Enterprise Virtual Array. The following topics are covered:

Description, page 14 Installing the Storage System Scripting Utility, page 15 Starting the Storage System Scripting Utility, page 21 Understanding Paths and Naming Conventions, page 23
13
Introduction
Description
The Storage System Scripting Utility (SSSU) for Enterprise Virtual Array is a command line application that allows you to configure and control EVA 3000 and 5000 controllers. You can execute configuration requests using Command View EVA or SSSU. Command View EVA is the graphical user interface that allows you to control and monitor a storage system. Use Command View EVA to handle simple or initial configuration tasks easily and expediently. Use SSSU to script and run repetitious and complex configuration tasks.
Formatting and Output of Returned Data

All returned SHOW command data is formatted in the form of:
XMLtag : Data
The XML tag displays before the data, and then the tags data displays.
14
Introduction
Installing the Storage System Scripting Utility

The following procedures assume that you have loaded the Web kit to a CD-ROM. SSSU is installed from your Enterprise Virtual Array host operating system kits. Refer to Chapter 2 in your Enterprise Virtual Array Installation and Configuration Guide for detailed instructions for installing SSSU. Once installed, SSSU can run as a simple executable. For convenience, you can add the directory containing the SSSU executable to your path or copy the executable to a directory already in your path. Ensure that the SSSU executables attributes are set with the correct security and execution flags appropriate for your environment. The executable file is named sssu or SSSU.EXE depending on the operating system environment. Depending on your operating system and workstation, follow one of the procedures below to install SSSU.
Installing the HP-UX Kit

1. If you are re-installing SSSU, remove the older version with the command:
# swremove SSSU
2. Find the CD-ROM device (c3t2d0 in the example shown in step 3) by entering:
# ioscan -fnuCdisk Class I H/W Path DriverS/W State H/W Type Description ========================================================== disk 33 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST32550W /dev/dsk/c0t5d0 /dev/rdsk/c0t5d0 disk 3 8/16/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5401 A /dev/dsk/c3t2d0 /dev/rdsk/c3t2d0 disk 4 8/16/5.4.0 sdisk CLAIMED DEVICE DEC RZ29B (C) D D C /dev/dsk/c3t4d0 /dev/rdsk/c3t4d0 Storage System Scripting Utility Enterprise Virtual Array Reference Guide 15
Introduction
3. Mount the CD-ROM with the command:

# mount /dev/dsk/c3t2d0 /cdrom
4. Copy the depot file from the CD-ROM to a temporary directory on the host system.
# cp /cdrom/sssu_v3_hpux.depot /tmp
5. Enter the following command to run the installation program (swinstall):

# swinstall -s /tmp/sssu_v3_hpux.depot
The SSSU executable is installed in the following directory:

#/sbin
To Execute SSSU
Command line version, type

#sssu
Graphical version, type

#gsssu
Installing the IBM Host Kit

The IBM AIX Kit v3.0B for Enterprise Virtual Array installs the supported FCA driver and the Storage System Scripting Utility (SSSU). The HSV controllers can be configured with SSSU as an alternative to the Command View EVA Element Manager. SSSU allows a command line interface for issuing commands directly to the controller. Complex configuration requests and operations can be handled by either the Command View EVA Element Manager or SSSU. Simple or initial configuration requests can be handled easily and expediently through the element manager, but repetitious and complex configuration steps can be scripted and executed through the command line interface. The CAPTURE CONFIGURATION command is the only way to capture, save, and recreate a storage systems configuration. The following section describes how to install and uninstall the IBM AIX Kit, including the Secure Path driver on the IBM AIX host server. The Secure Path driver is necessary for your IBM AIX server to interact with the Enterprise Virtual Array. 1. Mount the AIX platform kit.
16 Storage System Scripting Utility Enterprise Virtual Array Reference Guide
Introduction
2. Go to the /aix_spec directory. 3. Execute the command

installp -acd sssu-v31.rte all
LINUX
If you have already installed the FCA drivers, you can choose to install just the SSSU. 1. Mount the CD-ROM. 2. Change to the RPMS directory. 3. Enter the following command:
rpm -ivh sssu-<version>.rpm
Novell NetWare
The HSV controllers can be configured with SSSU. SSSU provides a command line interface for issuing commands directly to the controller. Complex configuration requests and operations can be handled by SSSU. Repetitious and complex configuration steps can be scripted and executed through the command line interface.
Note: The CAPTURE CONFIGURATION command is the only way to capture, save, and recreate a storage systems configuration.
Follow this procedure to install the SSSU application.

Note: You must use a Windows NT/2000 client, not a NetWare server, to install the SSSU.
1. Insert the Novell NetWare Kit v3.0B for Enterprise Virtual Array CD-ROM. 2. Copy the SSSU.NLM file to the system directory on the server where you will be running the utility. You can copy the file from a client, or on the server, with the Console One file utitility.
17
Introduction
OVMS
1. Insert the OpenVMS Kit v3.0B for Enterprise Virtual Array CD-ROM. 2. Copy the self-extracting executable file sssu_pcsi_sfx.exe from the CD-ROM to a temporary directory on the host system. 3. Enter the following command to extract the file:
$ run SSSUVxBLDxx
The following file is extracted:

HP-ALPHA-SSSU-V0x00-xx-1.PCSI
Note: The xx designations in the SSSUVxBLDxx command and extracted HP-ALPHA-SSSU-V0x00-xx-1.PCSI file indicate the latest build number.
4. Use the PolyCenter Software Installation program to install SSSU with the command:
$ product install sssu
5. Follow the instructions to complete the installation. The SSSU executable is installed in the following directory by default:
sys$system
SUN
If you have already installed the FCA drivers, you can choose to install just the SSSU. 1. Follow the steps in the normal installation. 2. Choose the manual option. 3. Follow the instructions and select just the CPQhsv package. The SSSU executable is installed in the following directory by default:
/opt/CPQhsv/bin
Note: This is the default installation directory, which the user may alter during the installation process. If you have used a different installation directory, the path would be /<BASE_DIR>/CPQhsv/bin.
18
Introduction
TRU64
1. Insert the Tru64 UNIX Kit v3.0B for Enterprise Virtual Array CD-ROM. 2. Enter the following command to extract the file (for v5.x):
# mount r t cdfs o rrip /dev/disk/cdrom0c /mnt
Note: Substitute your CD-ROM device for cdrom0c, if necessary.
3. Change directories on the CD-ROM by entering:

# cd /mnt
4. Enter the following command to run the installation program:

# setld l
Note: The l is a lowercase L.
The installation asks whether you want to install the listed subsets. 5. Enter the corresponding number of the software and press Return. 6. Select option y and press Return. The SSSU executable is installed in the following directory:
#/usr/opt/ENTP003/sbin
To Execute SSSU
In the command line version, type:
#sssu
WINDOWS
1. Insert the Window NT/2000/Server 2003 Kit v3.0B for Enterprise Virtual Array CD-ROM. If autorun is enabled, the installation program starts automatically. Otherwise, navigate to the root of the CD-ROM and double-click Launch.exe. 2. Click Solution Software V3.0B for Windows NT/2000/Server 2003 on the first screen.
19
Introduction
3. Click Skip Driver Upgrade on the bottom left of the second screen. 4. Click Install SSSU. The installation wizard starts. 5. Follow the instructions to complete the installation. You can run SSSU directly from the CD-ROM. The SSSU executable is located in the SSSU directory on the CD-ROM. Also, you can copy the executable to your server and run it from a directory of your choosing.
20
Introduction
Starting the Storage System Scripting Utility

SSSU starts at a command prompt window, shell, or equivalent.
Note: To run SSSU, you must set up password access to the element manager from the management appliance. You cannot set this password from within SSSU.The SET OPTIONS command on page 82 controls how SSSU behaves. The
options you set with the SET OPTIONS command are in effect for the current session only. Each time you start SSSU, the default options are reinstated.
Note: The CAPTURE CONFIGURATION command on page 50 is the only way to capture, save, and recreate a storage systems configuration. After you have successfully created a storage system, use the CAPTURE CONFIGURATION command to create scripts that you can use to recreate a storage system in the event of failure or to create an exact replica.
Syntax
SSSU <additional arguments>
If SSSU is started without arguments, a generic application <NoSystemSelected> prompt is displayed on the terminal and input can be accepted. If SSSU is started with arguments, those commands are echoed to the input terminal and executed, and then the utility exits.
Note: You must enclose in double quotes any commands or object names that have embedded blanks (spaces).
Examples
SSSU SSSU FILE snapD1.txt SSSU cmd1 cmd2 cmd2
The first example starts SSSU without additional arguments and prompts you for commands.
Storage System Scripting Utility Enterprise Virtual Array Reference Guide 21
Introduction
The second example starts SSSU and then executes the file snapD1.txt from the current directory. The third example starts SSSU and executes multiple commands.
22
Introduction
Understanding Paths and Naming Conventions

This section describes important information about paths and naming conventions in SSSU.
Note: For detailed descriptions of the following commands, refer to Chapter 2.
hi
The following important root folders let you organize your storage system:

\Hosts\ \Virtual Disks\ \Disk Groups\ \Data Replication\ \Hardware\ - This folder exists within SSSU; however, you cannot create any objects within this folder.
You cannot create root-level folders. You can, however, create additional folders within the \Hosts\ and \Virtual Disks\ folders to organize your storage system (see ADD FOLDERon page 36).
Note: SSSU requires that you qualify specified names with full paths. If, however, you are using the default placement when adding Hosts and Virtual Disks, you do not need to include the full path. Hosts Examples
For example, to add a host named engineering to the root Hosts folder:
ADD HOST engineering WORLD_WIDE_NAME=1111-2222-3333-4444
Whenever you refer to this host, you must give the full path. For example, when adding a LUN to this host:
ADD LUN 4 HOST=\Hosts\engineering VDISK="\Virtual Disks\Yekao\ACTIVE"
23
Introduction
If you create a folder structure within the root Hosts, you must include all levels of the folder structure in your commands. Here is an example of how to add the engineering host to the resources folder within the Host root folder:
ADD HOST \Hosts\resources\engineering WORLD=1111-2222-3333-4444
Virtual Disk Example
Because of the space in the root name for the Virtual Disks folder, you must always enclose strings that include the name of this folder within double quotes ().
Note: Remember to include full paths for objects and enclose any paths that contain spaces in double quotes.
For example, to add a virtual disk family new_code to the root folder Virtual Disks:
ADD VDISK \Virtual Disks\new_code SIZE=10
This example creates a 10-GB virtual disk family in the default disk group new_code.
Note: This is a virtual disk family. The actual virtual disk name (the active virtual disk) is \Virtual Disk\new_code\ACTIVE.
If you create a virtual disk (ADD VDISK) within a deeper folder structure, you need to include this full path within double quotes.
ADD VDISK \Virtual Disks\engineering\gene_research SIZE=2
Disk Groups Example
When a path includes the root folder \Disk Groups\, you must enclose the entire path in double quotes:
SHOW DISK_GROUP \Disk Groups\admin ADD VDISK \Virtual Disks\new_code SIZE=10 DISK_GROUP=\Disk Groups\admin
24
Introduction
Note: Although this guide shows commands spanning more than one line, always enter the SSSU command on one line. Note on OS_UNIT_ID and CONSOLE_LUN_ID
This value is used for IBM AIX (set to zero), OpenVMS (required), and Tru64 UNIX (recommended). Other host operating systems ignore the value. See the host operating system installation guides for more information.
Note on Changing Comments on a Disk Enclosure
SSSU does not allow comments to be changed on a disk enclosure. Anyone needing to do this can change them using the CommandView EVA UI.
25
Introduction
26
SSSU Command Reference
This chapter defines all the commands available in SSSU, including:

ADD, page 29 CAPTURE CONFIGURATION, page 50 DELETE, page 54 EMVERSION, page 63 EXIT, page 64 FILE, page 65 HELP, page 66 RESTART, page 67 SELECT, page 68 SET, page 71 SHOW, page 89 SHUTDOWN, page 102
In addition, this chapter includes syntax and examples. The commands are presented in alphabetical order.
27
Command Introduction
Most of the commands have switches that you can also use. These are described under the entry for the command in this chapter. You can display a list of switches for each command directly within the interface by entering a ? after the command or option name. For example, ADD ? displays all of the switches available with the ADD command, and ADD SYSTEM ? displays the switches availalble for the ADD SYSTEM command (see Getting Help on page 12). Remember when you issue commands:

Use the full path to qualify specified names. If a path name contains a space, enclose the entire name in double quotes ().
For a full discussion of these requirements, see Understanding Paths and Naming Conventions on page 23. Appendix A, Configuration Examples, provides a simple configuration example for using these commands to create and present a single LUN to a host. It also includes sample output from SHOW commands.
Note: Commands are not case sensitive, and it is often not necessary to type complete command names. For example, you can type sho for SHOW or shu for SHUTDOWN.
28
ADD
ADD
Use the ADD commands to create new systems, folders, disk_groups, dr_groups, virtual disks, copies, snapshots, as well as to add LUNs and hosts within the Enterprise Virtual Array.
Note: Creating copies, dr_groups, and snapshots of virtual disks is dependent on your licensing level. See the documentation that came with your hardware for more information.
29
ADD COPY
Use the ADD COPY command to create a copy of the specified virtual disk. A copy is a new virtual disk family. The ADD COPY command is equivalent to creating a snapclone within Command View EVA. Syntax
ADD COPY <copy_name> VDISK=<vdisk_family>
Switches The following switches are available with the ADD COPY command. DISK_GROUP= This is the name of the disk group where you want to create the virtual disk copy. The disk group must already exist to use this switch. If not specified, SSSU uses the same group as the source VDISK. OS_UNIT_ID= The ID that is presented to the host operating system. If set to zero, no ID is presented to the host. VDISK= This is the virtual disk name to be copied. WORLD_WIDE_LUN_NAME= Sets the World Wide LUN Name on unpresented storage. WAIT_FOR_COMPLETION Waits until the commands operation completes before displaying the next SSSU prompt (and returning control) or before running another script line. For large (greater than 1 TB) virtual disks, using this option can result in a long period before the prompt displays.
30
ADD COPY
NOWAIT_FOR_COMPLETION Default. Returns control as soon as possible. Some operations are invalid until the initial operation completes in the background. Required Switch The following switch is required with the ADD COPY command: VDISK= Examples
ADD COPY wednesday_nite VDISK=\Virtual Disks\payroll\ACTIVE ADD COPY save_reports VDISK=\Virtual Disks\daily_biz\ACTIVE DISK_GROUP=\Disk Groups\small_disks
The first example copies the virtual disk payroll to a copy wednesday_nite. The second example creates a copy of daily_biz as save_reports within the specified disk group.
Note: When you use the ADD COPY command, you are actually creating a VDISK. If you want to delete the VDISK, you must use the DELETE VDISK command.
31
ADD DR_GROUP
Use the ADD DR_GROUP command to create a data replication group containing the specified source virtual disk. This source VDisk will be replicated on the specified destination system. Syntax
ADD DR_GROUP <dr_group_name> VDISK=<vdisk> DESTINATION SYSTEM=<system>
Switches The following switches are available with the ADD DR_GROUP. ACCESSMODE= The access rights for a connected host. Possible values are readonly and disable. The default is disable, and this is the safest setting.
WARNING: Setting ACCCESSMODE to readonly could seriously impede host OS operation.
COMMENT= Used to attach comments to the DR Group being created. This string must be enclosed in quotes. The maximum number of characters for this optional switch is 64. DESTINATION_SYSTEM= The system on which the destination VDISKS are created on linked systems within this DR Group. DESTINATION_DISK_GROUP= The disk group name in which the VDISK on the destination system is created.
32
ADD DR_GROUP
DESTINATION_VDISK_NAME= The name of the VDISK that is created on the destination system. The default name is the same as that of the source. VDISK= The name of a source system VDISK to be placed within the DR Group. A destination VDISK is automatically created on the destination system. WRITEMODE= Defines the I/O interaction between the destination and source side. Possible values are synchronous and asynchronous. The default is synchronous. Required Switches The following switches are required for the ADD DR_GROUP command.

DESTINATION_SYSTEM = VDISK =
Example
ADD DR_GROUP Transactions DESTINATION_SYSTEM=Makawao VDISK=/Virtual Disks/Hawaii/ACTIVE
This example creates a DR_GROUP named Transactions that contains the source virtual disk \Virtual Disks\Hawaii\ACTIVE. This DR_GROUP will be connected to the destination system Makawao, on which the destination virtual disk \Virtual Disks\Hawaii\ACTIVE (same as the source by default) will be created and added to the destination DR_GROUP.
33
ADD DISK_GROUP
Use the ADD DISK_GROUP command to add a disk group to the system.
Caution: Vraid1 and Vraid5 are virtual disk families that have a SINGLE or DOUBLE group spare policy to ensure that there is adequate space to regenerate data. If you set the spare policy to NONE, the disk group may not have enough available space to regenerate Vraid1 and Vraid5 data.
Syntax
ADD DISK_GROUP <group_name>
Switches The following switches are available with the ADD DISK_GROUP command. COMMENT= This is an optional switch that associates a user-defined comment with the new system. A maximum of 128 characters is allowed, and the string must be enclosed in double quotes. DEVICE_COUNT= The number of physical disks to use for this group. The limit is the number of available disks in the storage system. The default and minimum value is 8. OCCUPANCY_ALARM= The point when a defined percentage of space is used. When this point is reached, an event log is generated and sent to the Management Appliance (optionally the host system) informing the administrator that the group is becoming full. Do not use the percentage sign (%) after the number. The default is 95%. SPARE_POLICY= This parameter determines the amount, if any, of storage space set aside for use in the event that disks fail. The default is single.
34
ADD DISK_GROUP
NONEreserves no space within a disk group to allow for data reconstruction in case of failure of disk drives SINGLEreserves space within a disk group to allow for data reconstruction for failure of a single disk drive DOUBLEreserves space within a disk group to allow for data reconstruction for failure of two disk drives
Note: The space set aside is not in numbers of physical disks. It is the equivalent amount of storage space spread across all disks.
Example
ADD DISK_GROUP \Disk Groups\human_resources DEVICE_COUNT=12 SPARE_POLICY=SINGLE OCCUPANCY_ALARM=75
This example creates a new disk group, human_resources. It has 12 physical disks with the equivalent of one disk set aside as a spare and sends an event log to the Management Appliance when 75% of capacity is reached.
35
ADD FOLDER
Use the ADD FOLDER command to create a new folder within the specified folder to aid in organizing your storage system. You can create folders only under the Virtual Disks and Hosts root folders. You cannot create root folders. For example, if you have a controller that is serving HR and Engineering, you could create four folderstwo to separate the virtual disks and two to separate the hosts:

\Virtual Disks\Engineering and \Virtual Disks\HR \Hosts\Engineering and \Hosts\HR
Creating these folders allows you to put engineering virtual disks and hosts in the Engineering folders and Human Resources storage/hosts in the HR folders. This makes it easier to keep track of the pieces within your storage system. If you want to nest folders inside folders, you must add one folder at a time. Syntax
ADD FOLDER <folder_name>
Switch Only the COMMENT switch is available with the ADD FOLDER command. COMMENT= This is an optional switch that associates a user-defined comment with the new system. A maximum of 128 characters is allowed and the string must be enclosed in double quotes. Examples
ADD FOLDER \Hosts\human_resources ADD FOLDER \Virtual Disks\colorado\colorado springs\engineering
The first example creates a new folder human_resources within the root folder Hosts. The second example creates a folder engineering in the folder colorado springs, which is two levels below the root folder Virtual Disks (\Virtual Disks\colorado\colorado springs).
36
ADD FOLDER
The folder structure in the second example must already have been in place before creating the new folder engineering.
37
ADD HOST
Use the ADD HOST command to add a host and its World Wide Name (WWN) to the list of hosts that can connect to virtual disks within the current system. The ADD HOST command adds the first Fibre Channel Adapter (FCA) only. The SET HOST command (see page 79) adds each subsequent FCA. Syntax
ADD HOST <host_name> WORLD_WIDE_NAME=<world_wide_name>
Switches The following switches are available with the ADD HOST command. IP= This is the network IP address. If the IP address is not specified, the name of the host will be specified as is (DNS). COMMENT= This is an optional switch that associates a user-defined comment with the new system. A maximum of 128 characters is allowed, and the string must be enclosed in double quotes. OPERATING_SYSTEM= The type of operating system for the specified host. Choose one of the following operating systems (they are spelled here as SSSU expects):

CUSTOM HPUX IBMAIX OPEN_VMS SOLARIS TRU64 UNKNOWN WINDOWS

38
ADD HOST
For the default operating system, refer to Agent Options - User Interface Options in the user interface. WORLD_WIDE_NAME= The World Wide Name (WWN) of the fibre channel adapter (FCA). Required Switch The following switch must be set to ensure that Command View EVA recognizes the host added with the ADD HOST command. WORLD_WIDE_NAME Example
ADD HOST \Hosts\development WORLD_WIDE_NAME=5000-1fe1-ff00-0000
This example adds a host development with an adapter at a WWN of 5000-1fe1-ff00-0000.
39
ADD LUN
The ADD LUN command makes previously created VDISKs available to a host. Syntax
ADD LUN <LUN_number> VDISK=<storage_name> HOST=<host_name>
LUN_number is 1 through 255. Switches The following switches are available with the ADD LUN command.
HOST=
The name of the host to which the LUN is presented.

VDISK=
The name of the VDISK that is presented to the host. Required Switches Set the following switches so that Command View EVA recognizes the LUN you add with the ADD LUN command.

HOST VDISK
Examples
ADD LUN 12 VDISK=\Virtual Disks\act\payroll\ACTIVE HOST=\Hosts\sanfran ADD LUN 175 VDISK=\Virtual Disks\user_disk\ACTIVE HOST=\Hosts\corporate
The first example adds LUN 12, which presents the ACTIVE virtual disk for the family payroll to the host called sanfran. The second example adds LUN 175, which presents the ACTIVE virtual disk for the family user_disk to the host called corporate.
40
ADD SNAPSHOT
ADD SNAPSHOT
The ADD SNAPSHOT command creates a picture (not a full copy) of a virtual disk familys active virtual disk.
Note: Creating snapshots of virtual disks depends on your licensing level. Attempting to add a snapshot without the license returns an error message. This message indicates that you need to enter your licensing information in the Command View EVA. You must have a registered license.
Syntax
ADD SNAPSHOT <snapshot_name> VDISK=<vdisk_to_snapshot>
Switches The following switches are available with the ADD SNAPSHOT command.
ALLOCATION_POLICY=
Indicates how the space for the snapshot is allocated.
DEMANDStorage is allocated for the snapshot only when required. As the snapshot and the original storages information diverges, the space allocated for the snapshot increases. FULLYAll storage required to fully contain a snapshot is allocated when the snapshot is created. This is the conservative method to create a snapshot, because adequate space is guaranteed for a full snapshot. This is the default.
OS_UNIT_ID=
The ID that is presented to the host operating system. If set to zero, no ID is presented to the host.
VDISK=
The source virtual disk for this snapshot.

WORLD_WIDE_LUN_NAME=
Sets the World Wide LUN Name.
41
Required Switch The following switch is required with the ADD SNAPSHOT command:
VDISK=
Examples
ADD SNAPSHOT payroll_backup VDISK="\Virtual Disks\payroll\ACTIVE" ALLOCATION_POLICY=DEMAND ADD SNAPSHOT wed_nite_biz VDISK="\Virtual Disks\daily_biz\ACTIVE" ALLOCATION_POLICY=FULLY
The first example creates a snapshot payroll_backup from the ACTIVE partition of Vdisk family payroll that uses capacity only as needed. The second example creates a snapshot wed_night_biz from the ACTIVE partition of the family daily_biz while reserving all capacity necessary to create the snapshot.
Note: To delete snapshots created by ADD SNAPSHOT, use the DELETE VDISK command.
42
ADD SYSTEM
ADD SYSTEM
Use the ADD SYSTEM command to initialize an uninitialized storage system and to create a default disk group. You must select an uninitialized storage system before issuing the ADD SYSTEM command. If the system is already initialized, the command is rejected. Use the SHOW SYSTEM command (see SHOW SYSTEM on page 99) to display the names of the available uninitialized storage systems. The uninitialized storage system display as Uninitialized Storage System#>, in which # represents a number. After initialization is complete, SSSU changes its default prompt back to NoSystemSelected>. Because the systems name changed from the uninitialized string to the name given with the ADD SYSTEM command, you must reselect the system. Issue the SELECT SYSTEM command using the new name of the system.
Note: Appendix A includes a configuration example that explains the sequence of commands you can use to initialize an uninitialized storage system (see Creating a Simple Configuration on page 104).
Syntax
ADD SYSTEM <system_name>
Switches The following switches are available with the ADD SYSTEM command. COMMENT= This is an optional switch that associates a user-defined comment with the new system. A maximum of 128 characters is allowed, and the string must be enclosed in double quotes. CONSOLE_LUN_ID= The LUN used for console communication after system creation. If set to zero, no console LUN is presented to the host.
43
DEVICE_COUNT= The number of physical disks to use for the default disk group of this system. The limit is the number of available disks in the storage system. The default and minimum value is 8. SPARE_POLICY= This parameter determines the amount, if any, of storage space set aside for safety in the event that disks fail. The default SPARE_POLICY is SINGLE.
NONEReserves no space within a disk group to allow for data reconstruction for failure of disk drives. SINGLEReserves space within a disk group to allow for data reconstruction for failure of a single disk drive. This is the default. DOUBLEReserves space within a disk group to allow for data reconstruction for failure of two disk drives.
Example
ADD SYSTEM payroll DEVICE_COUNT=12 SPARE_POLICY=SINGLE
This example creates an initialized system payroll with 12 physical disks and a spare policy of SINGLE.
44
ADD VDISK
ADD VDISK
Use the ADD VDISK command to create a virtual disk with a specified name and parameters.
Note: This command actually creates a virtual disk family and the ACTIVE partition. After you create the family, an initial virtual disk, ACTIVE, is placed as the only virtual disk in the family. This is referred to as the active virtual disk. When you later refer to this virtual disk, specify \ACTIVE after the family name. See the examples that follow the descriptions of the switches.
Syntax
ADD VDISK <storage_name> SIZE=<n>
The n is the virtual disk size in whole GBs. Switches The following switches are available with the ADD VDISK command. COMMENT= This is an optional switch that associates a user-defined comment with the new system. A maximum of 128 characters is allowed and the string must be enclosed in double quotes. DISK_GROUP= The disk group name for where you want to create the virtual disk. The disk group must already exist to use this switch. If not specified, the default disk group is used. MIRRORED_WRITEBACK All writes are stored in mirrored caches. After the data is stored in both caches, the write is complete. If one mirrored cache is unusable, the write is not complete until the data is in both caches.
45
NOMIRRORED_WRITEBACK No writes are stored in mirrored caches. After the data is stored in one cache, the write is complete. The write is complete even if a mirror copy of the cache is not available. OS_UNIT_ID= The ID that is presented to the host operating system. If set to zero, no ID is presented to the host. PREFERRED_PATH= The preferred controller path that is specified to handle all I/O for the virtual disks. If a controller fails, the path always reverts to the working controller.
PATH_A_BOTHController path A fails over to controller B. When controller A restarts, the virtual disks fail back to controller A. This is failover/failback mode. PATH_A_FAILOVERController path A fails over to controller B. When controller A restarts, the virtual disks do not fail back over to controller A. This is failover-only mode. PATH_B_BOTHController path B fails over to controller A. When controller B restarts, the virtual disks fail back to controller B. This is failover/failback mode. PATH_B_FAILOVERController path B fails over to controller A. When controller B restarts, the virtual disks do not fail back over to controller B. This is failover-only mode.
NOPREFERRED_PATH Allows the I/O to be handled by either controller. READ_CACHE Reads are satisfied from the controllers cache. NOREAD_CACHE Reads are always satisfied from the physical disks, not the controllers cache.
46
ADD VDISK
REDUNDANCY= The amount of data protection set when creating the virtual disk. If not specified, the default is Vraid0.
Vraid0Provides no data protection. It distributes data among its member disks into stripes and uses all members to process I/O requests. This method has no overhead associated with duplication of information and provides the highest performance. Vraid1Provides the highest level of data protection but uses the most space. It duplicates data written to one disk onto a backup disk. In a multidisk configuration, Vraid1 mirrors each pair of disks to each other. These disk pairs can then be striped to create a virtual disk. Vraid5Provides a moderate level of data protection. This method distributes the parity information among all disk members. If one drive fails, the failed disk can be recreated after it is replaced.
SIZE= This is a required switch. Size of the storage to be created. You can specify size in whole gigabytes only, and fractions are not allowed (1 GB 2000 GB, limited by the actual amount of space available within the disk group). WORLD_WIDE_LUN_NAME= Sets the World Wide LUN Name.
Note: This switch is commonly used to allow a host to point to a new version of the virtual disk by giving the new virtual disk the same WWN as the old virtual disk.
WRITE_PROTECT Does not allow writing to the virtual disk for all presented LUNs/host. NOWRITE_PROTECT Allows writing to the virtual disk for all presented LUNs/host.
47
WAIT_FOR_COMPLETION Default. Waits until the commands operation completes before displaying the next SSSU prompt (and returning control) or before running another script line. For large (greater than 1 TB) virtual disks, using this option can result in a long period before the prompt displays.
NOWAIT_FOR_COMPLETION
Returns control as soon as possible. Some operations are invalid until the initial operation completes in the background. For example, you cannot present the Vdisk (add a LUN) until the command completes. Required Switch The following switch is required with the ADD VDISK command:
SIZE=
Switch Defaults The following defaults are used for the ADD VDISK command when nothing is specified:

MIRRORED_WRITEBACK NOWRITE_PROTECT OS_UNIT_ID= defaults to zero PREFERRED_PATH= defaults to NOPREFERRED_PATH REDUNDANCY= defaults to Vraid0 DISK_GROUP= /Disk Groups/Default Disk Group
Note: If the Default Disk Group has been renamed, not specifying a disk group will result in error.
READ_CACHE
48
ADD VDISK
Examples
ADD VDISK \Virtual Disk\scratch SIZE=10 REDUNDANCY=VRAID5 READ_CACHE ADD VDISK \Virtual Disks\engineering\gene_research SIZE=2 DISK_GROUP=\Disk Groups\small_disks MIRRORED_WRITEBACK
The first example creates a 10-GB virtual disk scratch within the default disk group using read cache and a Vraid5 redundancy level. The second example creates a 2-GB disk at Vraid0 redundancy level in the small_disks group using mirrored writeback cache.
Note: Remember that this name is the <family_name> and that \Virtual Disks\<family_name>\ACTIVE is the name of the ACTIVE virtual disk. You must use this full path (enclosed in double quotes) when referring to it with any other commands.
49
CAPTURE CONFIGURATION
Syntax
CAPTURE CONFIGURATION <file_name>
CAPTURE CONFIGURATION queries the currently selected system and creates from one to five SSSU scripts. Not all systems require all five scripts. For example, step1A is always generated and may be the only file that is required. You use these scripts to recreate the original configuration and in some cases to assist in the recovery of any site. The scripts output to the console unless you specify a file. The scripts generate five files. Given a file name, _StepXX is appended after the file name and before the extension. XX is the restore step name, which is 1A, 1B, 1C, 2 and 3. For example, specifying CAPTURE CONFIGURATION newyear.txt causes SSSU to create the files newyear_Step1A.txt, newyear_Step1B.txt, newyear_Step1C.txt, newyear_Step2.txt, and newyear_Step3.txt. SSSU checks to see if any files by the names to be generated exist. If so, SSSU prompts you to replace existing files with the new files or abort the command completely. When creating files that contain the scripts, a progress bar displays on the console. This command may take a long time to complete depending on the size of the configuration.
Note: Do not reconfigure the selected system while this command is executing.
Step 1 Scripts The division of step 1 into three smaller steps facilitates data replication (DR) recovery.
Step 1A Script
Creates the storage system, disk groups, hosts, and VDISKs that are not used for data replication, either source or destination, and LUNs for the created disks. Step1A creates a basic system that does not include DR VDISKs or groups. CAPTURE CONFIG always creates this step.
50
CAPTURE CONFIGURATION
Step 1B Script
Creates all source VDISKs used in DR groups on this controller.

Step 1C Script
Presents all source VDISKs (creates LUNS) that are used for DR groups to their hosts. This step exists to assist in recovering from a DR failure in which a source site was lost. LUNs can be presented in their original configuration by running the correct step 1C script. Step 2 Script Recreates all DR-specific configuration information for which this system is the source. This involves the configuration's source DR_GROUPs and their members only. Presentations of remote VDISKs are not restored by this command (see step 3). This step provides flexibility when a site is completely lost. You must run step 1A, step 1B, and step 1C on both source and destination systems before step 2 can be run.
Note: If no destination VDSIK is presented to a host, a blank script will be generated for script 3.
Step 3 Script Presents remote VDISKs (creates LUNS) used for DR groups to their hosts. You must run step 2 on both source and destination systems before step 3 can be run. Restoring Configurations To restore system configuration from captured scripts, you must run the following scripts in the following order on each system that is part of the DR configuration. Before running a captured configuration script, you need to modify an existing script, run an additional script, or enter commands directly at the command line setup, as in steps 1 and 2.
51
Be aware that a specific captured configuration may not be recreated on some systems. For example, if a captured configuration demands 120 disks and the target system contains only 80, the captured configuration will not be successful. 1. Select a manager to specify which management appliance will perform the script commands. 2. Select the system Uninitialized Storage System# to specify the uninitialized storage system on which you want to recreate the captured configuration. 3. Run scripts 1A, 1B, and 1C successfully against ALL systems in the DR configuration. 4. Run the step 2 script successfully against ALL systems in the DR configuration. 5. Run the step 3 script successfully against ALL systems in the DR configuration. Once these scripts have been run against all systems, the DR configuration is restored to its original state. Example
CAPTURE CONFIGURATION c:\sales.txt
This example creates the files sales_Step1A.txt, sales_Step1B.txt, sales_Step1C.txt, sales_Step2.txt, and sales_Step3.txt.
Note: Refer to the FILE command on page 65 for further information about restoring configurations.
52
CAPTURE VALIDATE
CAPTURE VALIDATE
Syntax
CAPTURE VALIDATE <file_name>
CAPTURE VALIDATE checks the specified script file for modification by calculating its checksum and comparing the result against the checksum saved in the file. A script may have been modified (failed the CAPTURE VALIDATE command) but may still work. SSSU runs a script even if its checksum shows file modification. Example
CAPTURE VALIDATE c:\reconfigure_sales_dr_step2.txt
This example determines whether the reconfigure_sales_dr_step2.txt file was modified. Syntax
CAPTURE VALIDATE file_name
User Functionality CAPTURE VALIDATE is a switch that determines if a captured script text file has been edited and modified after it was captured. This allows the user to determine whether the script is a perfect capture of the existing system or if someone has modified it after it was created. Note that the specified script is not executed by this command; the script is checked only to see whether it's original or not. When a script is captured by the CAPTURE commands, a header is written at the front of the text file and a checksum is written at the end. If CAPTURE VALIDATE does not see a correct header, it reports that the script specified is not a CAPTURE-generated script. If the checksum does not match, this command reports that the file has been modified. If and only if a correct header is found and the checksum matches, this command reports that the CAPTURE script specified is unmodified.
53
DELETE
Use the DELETE commands to remove systems, folders, disk groups, DR groups, VDISKs, hosts, and LUNs from the storage system. You can control the behavior of all DELETE commands with the SET OPTIONS command (see SET OPTIONS on page 82 for details on how to use the SAFE_DELETE and NOSAFE_DELETE switches).
Note: All of the DELETE commands require the full path from the root directory to the object you want to delete. Only the DELETE VDISK command has switches available.
54
DELETE DR_GROUP
DELETE DR_GROUP
Deletes the DR Group on the source and destination system. Be sure that VDISKS are unpresented and that the source and destination are not communicating. The SET OPTION NOSAFE_DELETE does not override this requirement. You can delete a DR Group on the source system at any time. Syntax
DELETE DR_GROUP <dr_group_name>
Example
DELETE DR_GROUP \Data Replication\payroll
This example deletes the DR_GROUP payroll.
55
DELETE DISK_GROUP
Use the DELETE DISK_GROUP command to delete a disk group from the configuration. The command is rejected if any virtual disks are present in the disk group. Syntax
DELETE DISK_GROUP <group_name>
Example
DELETE DISK_GROUP \Disk Groups\human_resources
This example deletes a disk group named human_resources.
56
DELETE FOLDER
DELETE FOLDER
Use the DELETE FOLDER command to delete the specified empty folder. You should ensure folders are empty before deleting them because the DELETE FOLDER command will be rejected otherwise. To delete multiple layers of folders, you must do so sequentially.
Note: Ensure folders are empty before deleting them because the DELETE FOLDER command is rejected if the folder has contents.
Syntax
DELETE FOLDER <folder_name>
Examples
DELETE FOLDER \Hosts\human_resources\ DELETE FOLDER \Hosts\colorado\colorado_springs\engineering\
The first example deletes a folder named human_resources within the default Hosts folder. The second example deletes the folder named engineering nested in the path \Hosts\colorado\colorado_springs.
57
DELETE HOST
Syntax
DELETE HOST <host_name>
Example
DELETE HOST \Hosts\development
This example deletes the host development.
58
DELETE LUN
DELETE LUN
Use the DELETE LUN command to remove access to a virtual disk through the LUN from a host. Syntax
DELETE LUN <LUN_name>
Example
DELETE LUN \Hosts\accounting department\12
This example removes access to LUN 12 from the host accounting_department.
59
DELETE SYSTEM
Use the DELETE SYSTEM command to permanently remove the system from an EVA. The system will no longer be accessible, and all data will be lost.
Caution: The DELETE SYSTEM command removes the entire system configuration. All customer data on the entire system is lost when you run this command. In addition, all information about LUNs and hosts on this system is lost.
The DELETE SYSTEM command will be rejected if VDISKs exist. Refer to the SET command for the NOSAFE_DELETE behavior. Syntax
DELETE SYSTEM <system_name>
Example
DELETE SYSTEM payroll
This example deletes the system payroll.
60
DELETE VDISK
DELETE VDISK
Use the DELETE VDISK command to permanently remove the specified virtual disk. The virtual disk is no longer accessible, and all data is lost.
Caution: The DELETE VDISK command removes the entire virtual disk from the storage system. All customer data on the storage specified is destroyed when you run this command. In addition, all information about the LUNs presented from this virtual disk is lost as well.
The DELETE VDISK command will be rejected if presented. See NO_SAFE_DELETE for behavior. Syntax
DELETE VDISK <storage_name>
Switches The following switches are available with the DELETE VDISK command.
WAIT_FOR_COMPLETION
Waits until the commands operation completes before displaying the next SSSU prompt (and returning control) or before running another script line. For large (greater than 1 TB) virtual disks, using this option can result in a long period before the prompt displays.
NOWAIT_FOR_COMPLETION
Default. Returns control as soon as possible. Some operations are invalid until the initial operation completes in the background. Examples
DELETE VDISK \Virtual Disks\d12\ACTIVE WAIT_FOR_COMPLETION DELETE VDISK \Virtual Disks\daily_biz\wed_nite_biz
The first example deletes ACTIVE and the virtual disk family d12. WAIT_FOR_COMPLETION prevents the SSSU prompt from displaying until the virtual disk deletion is completed.
61
The second example deletes the snapshot wed_nite_biz and does not wait for completion.
Note: You cannot delete ACTIVE if a snapshot of the virtual disk exists. You must delete the snapshot and then delete ACTIVE.
62
EMVERSION
EMVERSION
The EMVERISON command is at the root level, as is help. This command provides the user with the element manager version and build number. Syntax
NoSystemSelected: emversion
Switches No additional keywords, parameters, or switches are available with the EMVERSION command. Example
Element manager information Version: 3.10 Build: 14
Note: You will need to select a manager before using the EMVERSION command, but you do not need to select a storage system.
63
EXIT
The EXIT command terminates the SSSU session. If SSSU is accepting input from the terminal or the command line, EXIT causes the program to terminate. If SSSU is processing a script from a file while encountering a FILE command, the behavior of the EXIT command depends on how the FILE command was issued:
If the FILE command was issued from the command line, an EXIT command in the file causes SSSU to terminate. If the FILE command was issued from the terminal, an EXIT command in the file causes SSSU to return to accepting input from the terminal. If a file is currently executing as a result of another FILE command, an EXIT command in that file returns control to the previous file. SSSU does not run any commands in a script beyond the EXIT command. EXIT causes an immediate return to the calling layer.
Syntax
EXIT
Example
EXIT
SSSU terminates.
64
FILE
FILE
The FILE command causes the current mode of input to suspend and redirects the scripting utility to accept input from the specified file. Either the end of the file or an EXIT command in the specified file causes SSSU to again accept input from the previous input source. FILE commands can be nested. Nesting FILE commands means that a file being executed through a FILE command can have FILE commands within its command set. The only limitation on how deep FILE commands may be nested is based on the host systems resources. Syntax
FILE <filename>
An extension is not required by SSSU, although you can choose one appropriate to your environment. Examples
FILE snapd1.txt FILE d:\scripts\snapshots\d27.txt
The first example executes the file snapd1.txt from the current directory. The second example executes a file d27.txt located in the specified directory.
65
HELP
The HELP command displays information about using the SSSU help. To get HELP on specific command syntax, enter a space and a question mark (?) wherever you would normally include a parameter, at any level of a command line. The help system will then list the options available for that parameter. Syntax
HELP
Examples
HELP Command syntax help is available at any point within a command by typing a '?'
The first example accesses HELP.

Add VDISK placeholder REDUNDANCY= ? The system displays: The options are: VRAID0 VRAID1 VRAID5
The second example requests the display of the different valid values for the switch REDUNDANCY.
66
RESTART
RESTART
Use the RESTART command to restart a controller shown by the SHOW POWER command. A power object is a controller. Syntax
RESTART <controller_name>
Switches The following switches are available for the RESTART command:

ALL_PEERS NOALL_PEERS
These switches are described in the following paragraphs.

ALL_PEERS
Restarts all peer controllers (both controllers) on this system.

NOALL_PEERS
Default. Restarts only the specified controller. Examples

RESTART \Hardware\Rack 1\Enclosure 7\Controller B ALL_PEERS RESTART \Hardware\Rack 1\Enclosure 7\Controller A NOALL_PEERS
The first example restarts Controller B, including its peer controller. The second example restarts Controller A, but not its peer controller.
67
SELECT
Use the SELECT command to select a system. After you select a system, the prompt changes to reflect the selected system.
68
SELECT MANAGER
SELECT MANAGER
Use the SELECT MANAGER command to direct the command prompt to a selected Command View EVA or management appliance. All configuration commands run on the selected Command View EVA or management appliance and affect its storage system configuration. The <manager_name> can be a server, appliance name, or an IP address. Unless the SAN administrator has changed the password, the default is password. Syntax
SELECT MANAGER <manager_name> USERNAME=<username> PASSWORD=<password>
Switches The switches available with the SELECT MANAGER command are described in the following paragraphs.
PASSWORD=
Password associated with the username that you use to access the Command View EVA.
USERNAME=
Username that you use to access the Command View EVA. Required Switches The following switches are required with the SELECT MANAGER command:

PASSWORD= USERNAME=
Example
SELECT MANAGER north_campus USERNAME=XXX PASSWORD=XXXX
This example selects the manager north_campus. The username and password for the manager are validated in the background on every command.
69
SELECT SYSTEM
Use the SELECT SYSTEM command to direct the command prompt to the selected system or manager. All configuration commands then affect the selected system. If the system name has spaces in it, the name must be enclosed in double quotes (). Syntax
SELECT SYSTEM <system_name>
Examples
SELECT SYSTEM employees SELECT SYSTEM payroll storage
In the first example, the employees system is selected. The system payroll storage is selected in the second example.
70
SET
SET
Use the SET commands to change the properties of systems, disks, folders, DR groups, disk groups, hosts, and virtual disks. In addition, the SET commands let you reset existing storage settings and application options.
All SET commands require the full path from the root directory to the object you want to rename. You can perform only one property change per SET command.
71
SET DR_GROUP
Use SET DR_GROUP to set the mode of operation of an existing DR Group. Syntax
SET DR_GROUP <dr_group_name>
Switches The switches available with the SET DR_GROUP command are described in the following paragraphs. ACCESSMODE= The access rights for a connected host. Possible values are readonly and disable. ADD_VDISK= Name of a source system VDISK to be added to the DR Group. A destination VDISK is automatically created on the destination system. When adding a VDISK to the DR Group, the following two optional switches may be specified: DESTINATION_DISK_GROUP= The disk group name on the destination system on which the VDISK is created. This switch can be specified only after the ADD_VDISK switch. DESTINATION_VDISK_NAME= The name of the VDISK that is created on the destination system. The default name is the same as that of the source. This optional switch can be specified only after the ADD_VDISK switch. COMMENT= An optional field for attaching comments to the DR Group being created. This string must be enclosed in quotes. The maximum number of characters for this switch is 64.
DELETE_VDISK=
Name of a source system VDISK to be removed from the DR Group. The corresponding destination VDISK on the destination system is removed from the DR Group and deleted from the system.
72
SET DR_GROUP
DETACH_VDISK= Name of a source system VDISK to be removed from the DR Group. The corresponding destination VDISK on the destination system is removed from the DR Group but not deleted. The detached destination VDISK continues to exist as an independent VDISK. FAILOVER Reverses the roles of the DR Groups; the source becomes the destination and the destination becomes the source. This is used to both fail over to the destination site and to fail back when normal operation is to be resumed. FAILSAFE When the connection between the source and the destination system fails, all writes are immediately halted and none is reported as completing until either the connection is restored or NOFAILSAFE is set. NOFAILSAFE This is the default when you first create the DR Group. When the connection between the source and the destination system fails, writes are directed to the log until the connection is restored. At this point, the pending destination writes are pushed across to the destination system. If the log becomes full, the system makes a full copy of the source VDISK to the destination VDISK when the connection is restored. Otherwise, the log resynchs the source and destination VDISKs. NAME= This is the new name for the specified DR_GROUP. SUSPEND Stops replication of data from the source to the destination. This causes the same behavior as if the connection failed. NOSUSPEND Allows replication of data from the source to the destination to resume. This causes the same behavior as if the connection was restored.
73
WRITEMODE= Defines the I/O interaction between the destination and source side. Possible values are synchronous and asynchronous. Example
SET DR_GROUP \Data Replication\Transactions SUSPEND
This example suspends replication for the DR Group Transactions.
74
SET DISK
SET DISK
The SET DISK command changes the properties of a disk. Syntax
SET DISK <name>
Switches The switches available for the SET DISK command are described in the following paragraphs.
COMMENT=
This is an optional switch that associates a user-defined comment with the new system. A maximum of 128 characters is allowed and the string must be enclosed in double quotes.
NAME=
New name to give to the specified disk. Example

SET DISK \Disk Groups\Ungrouped Disks\Disk 005 NAME=5Disk
This example renames the disk Disk 005 to 5Disk.
75
SET DISK_GROUP
The SET DISK_GROUP command changes the specified disk group properties. Syntax
SET DISK_GROUP <name>
Switches The switches available with the SET DISK_GROUP command are described in the following paragraphs.
ADD=
The number of disk drives to add to the specified disk group.

COMMENT=
This is an optional switch that associates a user-defined comment with the disk group. A maximum of 128 characters are allowed and the string must be enclosed in double quotes.
DELETE=
The name of the disk drive to be removed from the disk group. Data is not deleted when the disk is removed from the disk group.
NAME=
New name to give to the specified disk group.

OCCUPANCY_ALARM=
The point when a defined percentage of space is used. When this point is reached, an event log is generated and sent to the Management Appliance (optionally the host system) informing the administrator that the group is becoming full. Do not use the percentage sign (%) after the number.
SPARE_POLICY=
This parameter determines the amount, if any, of storage space set aside for use in the event that disks fail. The default is single.
NONEreserves no space within a disk group to allow for data reconstruction for failure of disk drives
76
SET DISK_GROUP
SINGLEreserves space within a disk group to allow for data reconstruction for failure of a single disk drive DOUBLEreserves space within a disk group to allow for data reconstruction for failure of two disk drives
Example
SET DISK_GROUP \Disk Groups\pool NAME=nuclear secrets
This example renames the disk group pool with the new name nuclear secrets.
77
SET FOLDER
The SET FOLDER command changes the specified folder properties. Syntax
SET FOLDER <name>
Switches The switches available for the SET FOLDER command are described in the following paragraphs.
COMMENT=
This is an optional switch that associates a user-defined comment with the new system. A maximum of 128 characters is allowed, and the string must be enclosed in double quotes.
NAME=
New name to give to the specified folder. Example

SET FOLDER \Virtual Disks\top_secret\ NAME=everyone_knows
This example renames the folder top_secret to everyone_knows.
78
SET HOST
SET HOST
The SET HOST command adds or deletes World Wide Names, sets the operating systems for a host, and adds comments to a specified host.
Note: Use the SET HOST command to add additional FCAs to hosts added to the storage system with the ADD HOST command.
Syntax
SET HOST <name>
Switches The following switches are available with the SET HOST command.
ADD_WORLD_WIDE_NAME=
Adds the World Wide Name of the host port.

DELETE_WORLD_WIDE_NAME=
Deletes the World Wide Name of the host port.

COMMENT=
IP=
This is the network IP address.

NAME=
New name given to the specified host.

OPERATING_SYSTEM=
The type of operating system for the specified host. Choose one of the following operating systems, which are spelled here as SSSU expects:
HPUX
79
IBMAIX OPEN_VMS SOLARIS TRU64 WINDOWS CUSTOM = (You must include the equal sign after CUSTOM, and the value must be 16-digit hexidecimal characters.)
Examples
SET HOST \Hosts\install OPERATING_SYSTEM=OPEN_VMS SET HOST \Hosts\install ADD_WORLD_WIDE_NAME=1000-0000-C922-36CA
The first example assigns OpenVMS as the operating system type for the host install. The second example adds a WWN to the host install.
80
SET MONITOR
SET MONITOR
The SET MONITOR command changes the specified monitor properties. Syntax
SET MONITOR <name>
Switches The following switches are available with the SET MONITOR command:
COMMENT=
This is an optional switch that associates a user-defined comment with the monitor. A maximum of 128 characters (including spaces) is allowed, and the string must be enclosed in double quotes.
NAME=
New name to give to the specified monitor. Example

SET MONITOR \Hardware\Rack 1\Enclosure 7\Controller A COMMENT=cabinet near the door
This example adds the comment cabinet near the door to the monitor Controller A.
Note: Remember to include full paths for objects and enclose any paths that contain spaces in double quotes.
81
SET OPTIONS
The SET OPTIONS command changes the SSSU characteristics.
Note: The options you set with the SET OPTIONS command are in effect for the current session only. Each time you start SSSU, the default options are reinstated.
Syntax
SET OPTIONS
Switches The following switches are available with the SET OPTIONS command.
COMMAND_DELAY=
The number of seconds (0300 seconds) to wait between issuing commands when running a script using the FILE command. The default is 10 seconds. This switch has no effect when you are typing commands.
NOCOMMAND_DELAY
Specifies no wait time between commands issued from within a FILE command.
DISPLAY_WIDTH=
Sets the amount of characters displayed on a line for SHOW commands. The default is 80. If the SSSU output is to be parsed, it is useful to set a high line width. A long line keeps the lines from wrapping, making the output easier to cut, paste, and parse. Line widths from 70 to 500 may be specified.
ON_ERROR=
CONTINUEIn this mode, only the EXIT command causes the scripting utility to halt. This is the default and is recommended when you are manually typing commands. EXIT_ON_ERRORAny error causes the scripting utility to exit with an error code. This mode is useful when requesting the entire script to halt immediately if errors occur while executing a script. This causes the scripting utility to halt on any kind of error: failed command, syntax error, or ambiguous command.
82
SET OPTIONS
HALT_ON_ERRORThis is similar to EXIT_ON_ERROR. Any error causes the scripting utility to halt but not exit until any key is pressed. Then the scripting utility exits with an error code. This allows you to see the error before the window closes on exit.
Note: When manually typing commands, HP does not recommend using the EXIT_ON_ERROR or HALT_ON_ERROR modes. You should avoid these modes because SSSU exits on any kind of error, including a typographical one. RETRIES=
Number of minutes to attempt long period retries, such as when the command view EVA service is busy or restarting. Specify between 110 minutes (inclusive). The default is four minutes.
NORETRIES
Specify that you do not want the scripting utility to retry commands.
SAFE_DELETE
Specify if you want to delete all dependent or related objects before the specified object can be deleted. For example, if you specified a deletion of the VDisk that had LUNs presented, the DELETE VDISK command would be rejected with a message telling you that all the LUNs presented from this storage must be deleted before the storage can be deleted. This is the default. You must always delete related objects if SAFE_DELETE is specified.
NOSAFE_DELETE
Allows the deletion of an object even if related objects are present. The behavior of the NOSAFE_DELETE command depends on the mode of operation (entering commands manually or running commands through a script) in which SSSU is running. If you are entering commands at a terminal, the Are you sure? prompt displays and you must type Yes for the deletion to proceed. Note that you must type a capital Y followed by lowercase es for the deletion to proceed. If the input is from a script (using the FILE command) or from the command line, the deletion proceeds without warning.
83
Caution: Using the NOSAFE_DELETE switch can cause accidental deletion of VDISKs or presentations.
Example
SET OPTION ON_ERROR=HALT_ON_ERROR NORETRIES
The example sets the options for SSSU to stop upon encountering an error and not to retry the commands.
84
SET SYSTEM
SET SYSTEM
Use the SET SYSTEM command to modify system properties. Syntax
SET SYSTEM <name>
Switches The following switches are available for the SET SYSTEM command.
COMMENT=
CONSOLE_LUN_ID=
The LUN used for console communication. If set to zero, a console LUN is not presented to the host.
Note: This value is used for IBM AIX (set to zero), OpenVMS (required), and Tru64 UNIX (recommended). Other host operating systems ignore the value. See the host operating system installation guides for more information. NAME=
New name to give to the specified system. Example

SET SYSTEM engineering NAME=accounting
This example renames the system engineering to accounting.
85
SET VDISK
Syntax
SET VDISK <storage_name>
Switches The following switches are available for the SET VDISK command.
COMMENT=
This is an optional switch that associates a user-defined comment with the new system. A maximum of 128 characters is allowed and the string must be enclosed in double quotes.
MIRRORED_WRITEBACK
All writes are stored in mirrored caches. After the data is stored in both caches, the write is complete. If one mirrored cache is unusable, the write is not complete until the data is in both caches.
NOMIRRORED_WRITEBACK
No writes are stored in mirrored caches. After the data is stored in one cache, the write is complete. The write is complete even if a mirror copy of a cache is not available.
NAME=
New name to give to the specified virtual disk.

OS_UNIT_ID=
The ID that is presented to the host operating system. If set to zero, an ID is not presented to the host.
Note: This is a required field for OpenVMS and is recommended for Tru64 UNIX. It is optional for all other operating systems. PREFERRED_PATH=
The preferred controller path that is specified to handle all I/O for the virtual disks. If a controller fails, the path always reverts to the working controller.
86 Storage System Scripting Utility Enterprise Virtual Array Reference Guide
SET VDISK
PATH_A_BOTHController path A fails over to controller B. When controller A restarts, the virtual disks fail back to controller A. This is failover/failback mode. PATH_A_FAILOVERController path A fails over to controller B. When controller A restarts, the virtual disks do not fail back over to controller A. This is failover-only mode. PATH_B_BOTHController path B fails over to controller A. When controller B restarts, the virtual disks fail back to controller B. This is failover/failback mode. PATH_B_FAILOVERController path B fails over to controller A. When controller B restarts, the virtual disks do not fail back over to controller B. This is failover-only mode.
NOPREFERRED_PATH
Allows the I/O to be handled by any controller.

READ_CACHE
Reads are satisfied from the controllers cache.

NOREAD_CACHE
Reads are always satisfied from media, not the controllers cache.
SIZE=
Indicates the new larger size (you cannot change to a size smaller than the original) of the storage in gigabytes. You can specify size in whole gigabytes only. Fractions are not allowed. The value of SIZE can be 2 GB through 2000 GB depending on the disk groups available space.
WORLD_WIDE_LUN_NAME=
Sets the World Wide LUN Name on unpresented storage (either ACTIVE or snapshot). This switch is rejected when issued against storage that is presented to a host.
Note: This switch is commonly used to allow a host to point to a new version of a snapshot by giving the new snapshot the same WWN as the old snapshot.
87
WRITE_PROTECT
Does not allow writing to the virtual disk for all presented LUNs.
NOWRITE_PROTECT
Allows writing to the virtual disk for all presented LUNs. Example
SET VDISK \Virtual Disks\archive\ACTIVE WORLD_WIDE_NAME_LUN_ NAME=6000-1fe1-ff00-0000
The example assigns the World Wide LUN Name to the ACTIVE virtual disk of the archive family.
88
SHOW
SHOW
Use the SHOW commands to display information about various elements in the currently selected system.
Note: All of the SHOW commands require the full path from the root directory to the object you want to display. Remember to include full paths for objects and enclose any paths that contain spaces in double quotes.
The following switches are available for all SHOW commands.

SHOW <element> FULL SHOW <element> NOFULL (This is the default.)
Example
SHOW VDISK FULL
This example provides all information about all VDISKS. Example

SHOW VDISK NOFULL
This example lists all the VDISKS. Because NOFULL is the default, SHOW VDISK also list all VDISKS. Example
SHOW VDISK <name>
This example displays all the properties of a particular disk.
89
SHOW DR_GROUP
Displays a list of data replication groups for the currently selected system. If you specify the name of the DR Group, it displays detailed information about the specified DR Group. Syntax
SHOW DR_GROUP <dr_group_name>
Example
SHOW DR_GROUP \Data Replication\Transactions
This example shows the DR_Group Transactions.
90
SHOW DISK
SHOW DISK
Use the SHOW DISK command to display disk configuration information for physical disks connected to the currently selected system. Syntax
SHOW DISK <disk_name>
Examples
SHOW DISK SHOW DISK \Disk Groups\Ungrouped Disks\Disk 039"
The first example displays a list of all the physical disks in the currently selected system. The second example displays specific information about the physical Disk 039.
91
SHOW DISK_GROUP
The SHOW DISK_GROUP command displays the disk groups currently configured by this system. If <disk_group_name> is specified, detailed information about the specified disk group is displayed. Syntax
SHOW DISK_GROUP <disk_group_name>
Examples
SHOW DISK_GROUP SHOW DISK_GROUP \Disk Groups\Default Disk Group
The first example displays a list of the available disk groups. The second example displays information about the default disk group.
92
SHOW HOST
SHOW HOST
The SHOW HOST command displays the hosts currently configured on this system. If <host_name> is specified, information about the specified host is displayed. Syntax
SHOW HOST <host_name>
Examples
SHOW HOST SHOW HOST \Hosts\med_lab
The first example displays the list of available hosts on the currently selected system. The second example displays specific information about the host med_lab.
93
SHOW LUN
The SHOW LUN command displays the LUNs currently configured on this system. Syntax
SHOW LUN <LUN_name>
Examples
SHOW LUN SHOW LUN \Hosts\SVT165\13
The first example displays the list of available LUNs on the selected system. The second example displays specific information about the LUN 13 on \Hosts\SVT165.
94
SHOW MANAGER
SHOW MANAGER
The SHOW MANAGER command displays information about the currently selected manager. Syntax
SHOW MANAGER
Switch The switches FULL and NOFULL can be specified but are ignored. Specifying a specific manager name is also ignored. The SHOW MANAGER command always displays the information for the currently selected manager. Example
SHOW MANAGER
The example displays information about the currently selected manager.
95
SHOW MONITOR
The SHOW MONITOR command displays the monitors currently installed on this system. If <monitor_name> is specified, detailed information about that specified monitor is displayed. Syntax
SHOW MONITOR <monitor_name>
Examples
SHOW MONITOR SHOW MONITOR \Hardware\Rack 1\blue_cab
The first example lists monitors available on the currently selected system. The second example displays information about the monitor blue_cab.
96
SHOW OPTIONS
SHOW OPTIONS
The SHOW OPTIONS command displays the current SSSU options. Syntax
SHOW OPTIONS
Example
SHOW OPTIONS
The example shows the following current options set for SSSU:
Options: NOCOMMAND_DELAY DISPLAY_WIDTH = 80 ON_ERROR = CONTINUE RETRIES = 4 (minutes) SAFE_DELETE
97
SHOW POWER
The SHOW POWER command displays the controllers currently configured on this system. If you specify <controller_name>, detailed information about that specific controller is displayed. Controllers are the only power objects. Syntax
SHOW POWER <controller_name>
Examples
SHOW POWER SHOW POWER \Hardware\Rack 1\Enclosure 7\Controller A
The first example displays a list of all power objects within the selected system. The second example displays specific information about Controller A.
98
SHOW SYSTEM
SHOW SYSTEM
Use the SHOW SYSTEM command to display the systems currently managed by command view eva. If <system_name> is specified, detailed information about that specified system is displayed. Syntax
SHOW SYSTEM <system_name>
Examples
SHOW SYSTEM SHOW SYSTEM payroll
The first example displays a list of available systems on this manager. The second example displays specific information about the system payroll.
99
SHOW VDISK
The SHOW VDISK command displays the storage currently configured on this system. If <storage_name> is specified, detailed information about the specified storage is displayed. Syntax
SHOW VDISK <virtualdiskname>
Examples
SHOW VDISK SHOW VDISK \Virtual Disks\scratch_disk\ACTIVE
The first example displays a list of all virtual disks in the currently selected system. The second example displays information about the specific active virtual disk scratch_disk\ACTIVE.
100
SHOW WORLD_WIDE_NAME
The SHOW WORLD_WIDE_NAME command displays the host World Wide Names (WWNs) that are visible to this system and not already assigned to a host. Syntax
Example
This example displays all of the WWNs visible to this system that have not been assigned to a host.
101
SHUTDOWN
Use the SHUTDOWN command to shut down any controller displayed by the SHOW POWER command. Syntax
SHUTDOWN <controller_name>
Switches The following switches are available with the SHUTDOWN command.
ALL_PEERS
Shuts down all peer controllers (both controllers) on this system. This will also power off all drive enclosures.
NOALL_PEERS
Default. Shuts down only the specified controller. Examples

SHUTDOWN \Hardware\Rack 1\Enclosure 7\Controller A NOALL_PEERS SHUTDOWN \Hardware\Rack 1\Enclosure 7\Controller B ALL_PEERS
The first example shuts down only Controller A. The second example shuts down Controller B and the peer.
102
Configuration Examples
This appendix provides examples that describe how to use commands to create a simple configuration and to view specific system information. The following topics are covered:

Creating a Simple Configuration, page 104 Using the SHOW Commands, page 108
103
Creating a Simple Configuration

This section presents a simple configuration example in two ways:

Annotated with steps (page 104 through page 107) Sample output as it displays after executing all of the commands (page 107)
Creating the Storage System

Select the manager with the SELECT MANAGER command. View the systems available on the manager (Uninitialized Storage System1, if this is an uninitialized storage system) with the SHOW SYSTEM command. Select the targeted scell for creation by issuing the command SELECT SYSTEM
Uninitialized Storage System1.
Add (create) the storage system with the ADD SYSTEM command.
1. Start SSSU from anywhere on the same network as your management appliance. The NoSystemSelected> prompt displays. 2. Enter the SELECT MANAGER command with the name of the manager and the logon information (a sample user name, password, and manager are used in the following example).
NoSystemSelected> SELECT MANAGER swma31k008 USERNAME=XXX PASSWORD=XXX NoSystemSelected>
Note: The password is set through the management appliance user interface.
3. At the prompt, enter the SHOW SYSTEM command to display all the available systems on this manager.
NoSystemSelected> SHOW SYSTEM Systems available on this Manager: Uninitialized Storage System1 NoSystemSelected>
The display includes systems that are available on this manager. In the example, the default for an uninitialized storage system is one system named Uninitialized Storage System1.
104
4. Select the Uninitialized Storage System1 system with the SELECT SYSTEM command.
NoSystemSelected> SELECT SYSTEM Uninitialized Storage System1 Uninitialized Storage System1>
The prompt changes to reflect the selected system (Uninitialized Storage System1). 5. Initialize the storage system with the ADD SYSTEM command, providing a name for the system (such as Yekao). This creates one system using 8 disks in the default Disk Group. The default number of disks is 8.
Uninitialized Storage System1> ADD SYSTEM Yekao NoSystemSelected>
Note: The prompt returns to NoSystemSelected> because the systems name has changed. You must reselect the system using the name you just gave it (SELECT SYSTEM Yekao).
105
Creating and Presenting a Virtual Disk

Here are the steps to follow to create a virtual disk and present the system to a host.

Select the newly created system Add a virtual disk (ADD VDISK) to the storage system Add a host to the system (ADD HOST) Add a LUN using a host and a VDISK
NoSystemSelected> SELECT SYSTEM Yekao Yekao>
1. Use the SELECT SYSTEM command to select the system you just created.
The prompt changes to reflect the object selected, in this case the system Yekao. 2. Create a virtual disk using the ADD VDISK command, supplying the virtual disk name and size in whole GBs.
Yekao> ADD VDISK Enicar SIZE=4 Yekao>
This example creates a 4-GB virtual disk named Enicar with a Vraid0 redundancy.
Note: The virtual disk (storage) can be between 2 GB (minimum) and 2000 GBs (maximum). The increments must be in whole GBs.
To present this newly created virtual disk, you need to have at least one host within the storage system. This host must be added to the storage system configuration. You can use the SHOW WORLD_WIDE_NAME command to see the available Fibre Channel Adapter World Wide Names. 3. Use the ADD HOST command to add a host to the storage system, supplying the World Wide Name (WWN) for the host port (FCA). Use caution with WWN assignments as these are not verified against the existing adapter when assigned.
Yekao> ADD HOST \Hosts\SVT165 WORLD_WIDE_NAME=1000-0000-c923-6735 Yekao> SET HOST \Hosts\SVT165 ADD_WORLD_WIDE_NAME=1000-0000-c923-6736 106 Storage System Scripting Utility Enterprise Virtual Array Reference Guide
4. Add the LUN to the host by using the ADD LUN command, supplying the full path to the virtual disk and the host machine.
Yekao> ADD LUN 15 VDISK=\Virtual Disks\Enicar\ACTIVE HOST=\Hosts\SVT165
Remember, for any path or name that contains spaces, you must enclose the entire string in double quotes, as in the example above. Now LUN 15 is presenting the VDISK to the host.
Sample Configuration Command Output
The following example shows the commands that were entered during the previous procedures (page 104 through page 107) without the interruption of the instructions.
NoSystemSelected> SELECT MANAGER swma31k008 USERNAME=XXX PASSWORD=XXX NoSystemSelected> SHOW SYSTEM Systems available on this Manager: Uninitialized Storage System1 NoSystemSelected> SELECT SYSTEM Uninitialized Storage System1 Uninitialized Storage System1> ADD SYSTEM Yekao NoSystemSelected> SELECT SYSTEM Yekao Yekao> ADD VDISK Enicar SIZE=4 Yekao> ADD HOST SVT165 WORLD_WIDE_NAME=1000-0000-c923-6735 Yekao> SET HOST \Hosts\SVT165 ADD_WORLD_WIDE_NAME= 1000-0000-c923-6736 Yekao> ADD LUN 13 VDISK=\Virtual Disks\Enicar\ACTIVE HOST= \Hosts\SVT165
107
Using the SHOW Commands

This section provides examples of using the SHOW command, based on the storage system, host, and virtual disk created in the previous section, Creating a Simple Configuration on page 104. The purpose of this presentation is to provide a sample of SSSU output. To view information about various system attributes, you first select the system and then use the SHOW commands.
SHOW SYSTEM
Use the SHOW SYSTEM command to view information about the selected system. 1. At the NoSystemSelected> prompt, enter SHOW SYSTEM.
NoSystemSelected> SHOW SYSTEM Systems available on this Manager: Yekao Makawao NoSystemSelected>
The available systems on this manager are displayed. 2. Select the system you want with the SELECT command.
NoSystemSelected>SELECT SYSTEM Yekao
3. Use the SHOW SYSTEM command to display information about the system.
Yekao> show system Yekao Yekao information: Initialized Enterprise System Properties: Name : Yekao Licenses : BASIC SNAPSHOT DRM Operational_State : Initialized - Good Total_storage_space : 947.78 GB Storage_space_used : 194.51 GB Available_storage_space : 753.26 GB Device_addition_policy : Manual Console_LUN_ID : 0 Controller_time : 08-Jan-1947 15:01:00 Node_world_wide_name : 5000-1FE1-5000-5C20 Comments : ID : 08000710b4080560bc49010000d0000000000200 ElementRefreshStatus : 0,0,0,0,0,0,0,0,3,0,0,0
108
Yekao>
SHOW VDISK
Use the SHOW VDISK command to display information about the virtual disks (storage) within the selected system. 1. Enter the SHOW VDISK command (with a system selected) to display a list of available storage.
Yekao> show vdisk Vdisks available on this System: \Virtual Disks\maui6228_1\ACTIVE \Virtual Disks\maui_1\ACTIVE \Virtual Disks\lanai_1\ACTIVE Yekao>
Note: Remember that the ADD VDISK command creates a virtual disk family and you must include \ACTIVE when referring to the actual virtual disk.
2. Use the SHOW VDISK command to display information about the virtual disk.
Yekao> show vdisk \Virtual Disks\maui6228_1\ACTIVE \Virtual Disks\maui6228_1\ACTIVE information: Identification: Name : \Virtual Disks\maui6228_1\ACTIVE Family_Name : maui6228_1 Hex_UUID :6005-08b4-0001-49bc-0000-e000-000d-0000 World_Wide_Lun_Name : 6005-08b4-0001-49bc-0000-e000-000d-0000 Attributes: Disk_Type : Original Disk_Group : \Disk Groups\Default Disk Group Capacity_Req : 25 Capacity_Used : 25 Sharing_Relationship : none Redundancy : vRaid5 Write_Cache_Policy : Mirrored write-back
109
Read_Cache_Policy : On Comm_Protocol : Write_Protect : No Enable_Disable : Enable OS_Unit_ID : 0 Preferred_path : No preference Comments : ID : 01200710b4080560bc49010000e0000000000d00 Condition_State: Operational_State : 1 Date Time: Created : 28-Jun-1946 18:28:34 Presentation [0]: StorageClientName : \Hosts\maui_6228 Lun : 1 DR_Attributes: Remote_VDisk: Yekao>
SHOW HOST
Use the SHOW HOST command to display information about the hosts available on the selected storage system. 1. With the system selected, enter SHOW HOST to display the list of available hosts.
Yekao> show host Hosts available on this System: \Hosts\maui \Hosts\maui_6228 \Hosts\lanai Yekao>
2. Use the SHOW HOST command, followed by the specific host name, to display information about the host.
110
Note: Remember that you need to type the full path to the host object and that if there are any spaces within the path or host name, the entire string needs to be enclosed within double quotes.
Yekao> show host \Hosts\maui \Hosts\maui information: Identification: Name : \Hosts\maui IPAddress : Dynamic IP Assignment Status : Initialized - Good Operating_System : IBMAIX Fibre_Channel_adapter_ports: Fibre_Channel_adapter_ports [0]: Port : 5005-02e0-1000-09fe Fibre_Channel_adapter_ports [1]: Port : 5005-02e0-1000-018b Presentation: Presentation [0]: Lun : 1 Virtual_disk : \Virtual Disks\maui_1\ACTIVE Comments : ID : 00800710b4080560bc49010000d0000000001b00 Yekao>
SHOW LUN
Use the SHOW LUN command to display information about specific LUNs. 1. With the system selected, enter the SHOW LUN command to display the list of available LUNs.
Yekao> show lun LUNs available on this Cell: \Hosts\maui_6228\1 \Hosts\maui\1 \Hosts\lanai\1
111
2. Use the SHOW LUN command, with the specific LUN named, to display the specific LUN information.
Yekao> show lun \Hosts\maui\1 \Hosts\maui\1 information: Name : \Hosts\maui\1 StorageName : \Virtual Disks\maui_1\ACTIVE StorageclientName : \Hosts\maui ID : 00880710b4080560bc49010000e0000000000b00 Yekao>
112
glossary
This glossary defines terms used in this guide or related to this product and is not a comprehensive glossary of computer terms. active virtual disk A virtual disk is a simulated disk drive created by the controllers as storage for one or more hosts. An active virtual disk is accessible by one or more hosts for normal storage. An active virtual disk and its snapshot, if one exists, constitute a virtual disk family. An active virtual disk is the only Glossary necessary member of a virtual disk family.
Glossary
See also virtual disk, virtual disk copy, virtual disk family, and snapshot. array All the physical disk drives in a storage system that are known to and under the control of a controller pair. array controller See controller. block Also called a sector. The smallest collection of consecutive bytes addressable on a disk drive. In integrated storage elements, a block contains 512 bytes of data, error codes, flags, and the block address header. cache High-speed memory that sets aside data as an intermediate data buffer between a host and the storage media. The purpose of cache is to improve performance. See also read cache, write cache, and mirrored cache. command view EVA A graphical user interface through which users control and monitor a storage system. The software can be installed on one or more management appliances in a fabric. Each Command View EVA installation is a management agent. communication logical unit number (LUN) See console LUN.
Storage System Scripting Utility Enterprise Virtual Array Reference Guide 113
Glossary
console LUN A SCSI-3 virtual object that makes a controller pair accessible by the host before any virtual disks are created. Also called a communication LUN. console LUN ID The ID that can be assigned when a host operating system requires a unique ID. The console LUN ID is assigned by the user, usually when the storage system is initialized. See also console LUN. controller A hardware/firmware device that manages communications between host systems and other devices. Controllers typically differ by the type of interface to the host and provide functions beyond those the devices support. controller pair Two interconnected controller modules that together control a physical disk array. A controller pair and the disk array together constitute a storage system. default disk group The first disk group created at the time the system is initialized. The default disk group can contain the entire set of physical disks in the array or just a few of the disks. See also disk group. disk A physical storage device (disk drive) connected to the system. disk failure protection A method by which a controller pair reserves drive capacity to take over the functionality of a failed or failing physical disk. DISK_GROUP A collection of disks from which storage is created. DR_GROUP One or more data replication groups that preserve write ordering and share a common log. EMU Environmental Monitoring Unit. An element that monitors the status of an enclosure, including the power, air temperature, and blower status. The EMU detects problems and displays and reports these conditions to a user and the controller. In some cases, the EMU implements corrective action.
114
Glossary
Enterprise Virtual Array The hp name used to describe the storage system that includes controllers, storage devices, enclosures, cables, and power supplies. Also called the Enterprise Storage System. environmental monitoring unit See EMU. event log System information sent to the Management Appliance or host operating system. fabric A Fibre Channel fabric switch or two or more interconnected Fibre Channel switches allowing data transmission. fabric port A port that is capable of supporting an attached arbitrated loop. This port on a loop has the AL_PA hexadecimal address 00 (loop ID 7E), giving the fabric the highest priority access to the loop. A loop port is the gateway to the fabric for the node ports on a loop. failover The process that takes place when one controller assumes the workload of a failed companion controller. Failover continues until the failed controller is operational. FC HBA Fibre Channel Host Bus Adapter. An interchangeable term for Fibre Channel adapter. See also FCA. FCA Fiber Channel Adapter. An adapter used to connect the host server to the fabric. Also called a Host Bus Adapter (HBA) or a Fibre Channel Host Bus Adapter (FC HBA). See also FC HBA fiber The optical media used to implement Fibre Channel. fibre The international spelling that refers to the Fibre Channel standards for optical media. Fibre Channel A data transfer architecture designed for mass storage devices and other peripheral devices that require very high bandwidth. Fibre Channel adapter See FCA.
115
Glossary
GB Gigabyte. A unit of measurement defining either:
A data transfer rate. See also GBps A storage or memory capacity of 1,073,741,824 (230) bytes.
GBps Gigabytes per second. A measurement of the rate at which the transfer of bytes of data occurs. A GBps is a transfer rate of 1,000,000,000 (109) bits per second. See also GB. Giga (G) The notation to represent 109 or 1 billion (1,000,000,000). HBA Host Bus Adapter. See FCA. host A system that has data path access to the virtual disk through a logical unit number (LUN) defined on the system. Host Bus Adapter See FCA. host computer See host. host ports A connection point to one or more hosts through a Fibre Channel fabric. A host is a computer that runs user applications and that uses (or can potentially use) one or more of the virtual disks that are created and presented by the controller pair. host-side ports See host ports. hp StorageWorks The hp trademarked name used to describe the set of rack-mounted enclosures containing controllers, transceivers, I/O modules, EMUs, disk drives, cables, blowers, and power supplies used to design and configure a solution-specific storage system.
116
Glossary
initialization A process that prepares a storage system for use. Specifically, the system binds controllers together as an operational pair and establishes preliminary data structures on the disk array. Initialization also sets up the first disk group, called the default disk group. LUN Logical Unit Number. The host-accessible presentation of a virtual disk on the system. manager The object that controls configuration of the system. The StorageWorks Command View EVA is the manager in the case of the Enterprise Virtual Array. MB Megabtye. A term defining either:
A data transfer rate. See also MBps. A measure of either storage or memory capacity of 1,048,576 (220) bytes.
MBps Megabytes per second. A measure of bandwidth or data transfers occurring at a rate of 1,000,000 (106) bytes per second. Mega A notation denoting a multiplier of 1 million (1,000,000). mirrored caching A process in which half of each controllers write cache mirrors the companion controllers write cache. mirroring The act of creating an exact copy or image of data. monitor An element that monitors the status of an enclosure, including the power, air temperature, and blower status. OSM Open SAN Manager. A centralized, appliance-based monitoring and management interface that supports multiple applications, operating systems, hardware platforms, storage systems, tape libraries, and SAN-related interconnect devices. It is included with and resides on the Management Appliance, a single aggregation point for data management.
117
Glossary
parity A method of checking if binary numbers or characters are correct by counting the ONE bits. In odd parity, the total number of ONE bits must be odd; in even parity, the total number of ONE bits must be even. Parity information can be used to correct corrupted data. parity bit A binary digit added to a group of bits that checks to see if there are errors in the transmission. parity check A method of detecting errors when data is sent over a communications line. With even parity, the number of ONE bits in a set of binary data should be even. With odd parity, the number of ONE bits should be odd. password A security interlock whose purpose is to allow:

A management agent control of only certain storage systems Only certain management agents control of a storage system
physical disk A disk drive mounted in a disk drive enclosure that communicates with a controller pair through the device-side Fibre Channel loops. A physical disk is hardware with embedded software, as opposed to a virtual disk, which is constructed by the controllers. Only the controllers can communicate directly with the physical disks. The physical disks, in aggregate, are called the array and constitute the storage pool from which the controllers create virtual disks. physical disk array See array. port A Fibre Channel connector on a Fibre Channel device. port_name A 64-bit unique identifier assigned to each Fibre Channel port. The port_name is communicated during the login and port discovery processes. preferred path A preference for which controller of the controller pair manages the virtual disk. This preference is set by the user through the Command View EVA when creating the virtual disk. A user can change the preferred path of a virtual disk at any time. The main purpose of selecting a preferred path is load balancing.
118
Glossary
read caching A cache method used to decrease subsystem response times to a read request by allowing the controller to satisfy the request from the cache memory rather than from the disk drives. Reading data from cache memory is faster than reading data from a disk. The read cache is specified as either on or off for each virtual disk. The default state is on. read ahead caching A cache management method used to decrease the subsystem response time to a read request by allowing the controller to satisfy the request from the cache memory rather than from the disk drives. redundancy
Element RedundancyThe degree to which logical or physical elements are protected by having another element that can take over in case of failure. For example, each loop of a device-side loop pair normally works independently but can take over for the other in case of failure. Data RedundancyThe level to which user data is protected. Redundancy is directly proportional to cost in terms of storage usage; the greater the level of data protection, the more storage space is required. An American National Standards Institute (ANSI) interface that defines the physical and electrical parameters of a parallel I/O bus used to connect computers and a maximum of 16 bus elements. The communication protocol used between a controller pair and the hosts. Specifically, the protocol is FC-AL or SCSI on a Fibre Channel. SCSI is the higher command-level protocol and Fibre Channel is the low-level transmission protocol. The controllers have full support for SCSI-2; additionally, they support some elements of SCSI-3.
SCSI (small computer system interface)
SCSI-3 The ANSI standard that defines the operation and function of Fibre Channel systems. snapshot A temporary virtual disk that reflects the contents of another virtual disk at a particular point in time. A snapshot operation is done only on an active virtual disk. The active disk and its snapshot constitute a virtual disk family. See also active virtual disk, virtual disk copy, and virtual disk family.
119
Glossary
spare policy This is the disk failure protection level set for the system and disk groups. See also disk failure protection. SSN Storage System Name. A user-defined, unique 20-character name that identifies a specific storage system. storage pool The aggregated blocks of available storage in the total physical disk array. Storage System Name See SSN. storage system The controllers, storage devices, enclosures, cables, and power supplies and their software. Storage System Scripting Utility (SSSU) A command-line application supplied in the host operating system kits that lets you configure and control HSV controllers. switch An electro-mechanical device that initiates an action or completes a circuit. system A controller or controller pair that is treated conceptually as one controller. In the Command View EVA, the system is the name you give the initialized storage system. TB Terabyte. A term defining either:
A data transfer rate. See also TBps. A measure of either storage or memory capacity of 1,099,5111,627,776 (240) bytes.
TBps Terabytes per second. A data transfer rate of 1,000,000,000,000 (1012) bytes per second. uninitialized storage system A state in which the storage system is not ready for use. See also initialization.
120
Glossary
VDisk (virtual disk) A collection of blocks created on one or more disks that can be used by a host for information storage and retrieval. The host computer sees the virtual disk as real, with the characteristics of an identical physical disk. See also active virtual disk, virtual disk copy, virtual disk family, and virtual disk snapshot. virtual disk copy A clone or exact replica of another virtual disk at a particular point in time. Only an active virtual disk can be copied. A copy immediately becomes the active disk of its own virtual disk family. See also active virtual disk, virtual disk family, and virtual disk snapshot. virtual disk family A virtual disk and its snapshot, if a snapshot exists, constitute a family. The original virtual disk is called the active disk. When you first create a virtual disk family, the only member is the active disk. See also active virtual disk, virtual disk copy, and virtual disk snapshot. virtual disk snapshot See snapshot. Vraid0 A virtualization technique that provides no data protection. Data host is broken down into chunks and distributed on the disks comprising the disk group from which the virtual disk was created. Reading and writing to a Vraid0 virtual disk is very fast and makes the fullest use of the available storage, but there is no data protection (redundancy) unless there is parity. Vraid1 A virtualization technique that provides the highest level of data protection. All data blocks are mirrored or written twice on separate physical disks. For read requests, the block can be read from either disk, which can increase performance. Mirroring takes the most storage space because twice the storage capacity must be allocated for a given amount of data. Vraid5 A virtualization technique that provides moderate data protection using parity striping. Parity is a data protection mechanism for a striped virtual disk. A striped virtual disk is one whose data to and from the host is broken down into chunks and distributed on the physical disks comprising the disk group in which the virtual disk was created. If the striped virtual disk has parity, another chunk (a parity chunk) is calculated from the set of data chunks and written to the physical disks. If one of the data chunks becomes corrupted, the data can be reconstructed from the parity chunk and the remaining data chunks.
121
Glossary
World Wide Name See WWN. write back caching A controller process that notifies the host that the write operation is complete when the data is written to the cache. This occurs before transferring the data to the disk. Write back caching improves response time since the write operation completes as soon as the data reaches the cache. As soon as possible after caching the data, the controller then writes the data to the disk drives. write caching A process when the host sends a write request to the controller and the controller places the data in the controller cache module. As soon as possible, the controller transfers the data to the physical disk drives. WWN World Wide Name. A unique Fibre Channel identifier consisting of a 16-character hexadecimal number. A WWN is required for each Fibre Channel communication port.
122
index
A
ADD COPY examples 31 switches DISK_GROUP= 30 OS_UNIT_ID= 30, 41 VDISK= 30 WORLD_WIDE_LUN_NAME= 30 ADD DISK_GROUP description 34 example 35 switches DEVICE_COUNT= 34 OCCUPANCY_ALARM= 34 SPARE_POLICY= 34 ADD DR_GROUP description 32 example 33 Syntax 32 ADD FOLDER description 36 examples 36 switch, COMMENT= 36 syntax 36 ADD HOST description 38 example 39 switches COMMENT= 38 OPERATING_SYSTEM= 38 WORLD_WIDE_NAME= 39 syntax 38
using 106 ADD LUN description 40 examples 40 switches HOST= 40 VDISK= 40 syntax 40 using 107 ADD SNAPSHOT description 41 examples 42 switches ALLOCATION_POLICY= 41 VDISK= 41 WORLD_WIDE_LUN_NAME= 41 syntax 41 ADD SYSTEM description 43 example 44 switches COMMENT= 34, 36, 38, 43, 45, 85 CONSOLE_LUN_ID= 43 DEVICE_COUNT= 44 SPARE_POLICY= 44 syntax 43 using 105 ADD VDISK description 45 examples 49 switch defaults 48 switches DISK_GROUP= 45
123
Index
Index
Index
MIRRORED_WRITEBACK 45 NOPREFERRED_PATH 46 NOREAD_CACHE 46 NOWRITE_PROTECT 47 OS_UNIT_ID= 46 PREFERRED_PATH= 46, 86 READ_CACHE 46 REDUNDANCY= 47 SIZE= 47 WORLD_WIDE_LUN_NAME= 47 WRITE_PROTECT 47 syntax 45 using 106 audience 14 authorized reseller, HP 12
C
CAPTURE CONFIGURATION description 50 example 52 restoring configurations 51 syntax 50 CAPTURE VALIDATE description 53 example 53 syntax 53 configuration creating 104 importance of capturing 21 CONSOLE_LUN_ID and operating systems 43 conventions document 10 text symbols 10 creating and presenting a virtual disk 106 simple configuration 104 the storage system 104
DELETE DISK_GROUP description 56 example 56 syntax 56 DELETE DR_GROUP example 55 sytax 55 DELETE FOLDER description 57 syntax 57 DELETE HOST syntax 58 DELETE LUN description 59 syntax 59 DELETE SYSTEM description 60 syntax 60 DELETE VDISK description 61 examples 61 syntax 61 DISK SET 75 SHOW 91 DISK_GROUP ADD 34 DELETE 56 SET 76 SHOW 92 document conventions 10
E
Enterprise Virtual Array, and SSSU 14 EXIT description 64 example 64 syntax 64
D
DELETE commands 54
124
Index
F
FILE description 65 examples 65 syntax 65 FOLDER ADD 36 DELETE 57 SET 76 formatting and output of returned data 14
M
MANAGER SHOW 95 MONITOR SET 81 SHOW 96
N
naming disk group example 23 host example 23 paths and 23 virtual disk example 23
G
getting help 12
H
HELP description 66 example 66 syntax 66 help, obtaining 12 HOST ADD 38 SET 79 SHOW 93 HP authorized reseller 12 storage website 12 technical support 12 HP-UX 38, 79 HSV controllers 14
O
OpenVMS 38, 80 and the CONSOLE_LUN_ID 85 operating systems how named in SSSU 38 setting with ADD HOST 79 OPTIONS SET 82 SHOW 97 options, setting for SSSU 82 output of returned data, formatting 14 overview, of SSSU 14
P
paths and naming 23 POWER, SHOW 98 presenting a virtual disk, creating and 106
I
IBM AIX 38, 80 and the CONSOLE_LUN_ID 85 installing SSSU 15
R
RESTART 67 description 67 examples 67 switches ALL_PEERS 67, 102 NOALL_PEERS 67, 102 syntax 67 restoring configurations 51
125
L
LUN ADD 40 DELETE 59 SHOW 94
Index
returned data, formatting and output of 14
S
SELECT 68 SELECT MANAGER examples 69 switches PASSWORD= 69 USER= 69 syntax 69 SELECT SYSTEM examples 70 syntax 70 using 105, 106 SET DISK description 75 example 75 switches COMMENT= 75 NAME= 75 syntax 75 SET DISK_GROUP description 76 example 77 switches ADD= 76 COMMENT= 76 DELETE= 76 NAME= 76 OCCUPANCY_ALARM= 76 syntax 76 SET DR_GROUP description 72 example 74 syntax 72 SET FOLDER description 76 example 78 switches COMMENT= 78 NAME= 78 syntax 78
126
SET HOST description 79 examples 80 switches ADD_WORLD_WIDE_NAME= 79 COMMENT= 79 DELETE_WORLD_WIDE_NAME= 79 OPERATING_SYSTEM= 79 syntax 79 SET MONITOR description 81 example 81 switches COMMENT= 81 NAME= 81 syntax 81 SET OPTIONS description 82 examples 84 switches COMMAND_DELAY= 82 DISPLAY_WIDTH= 82 NOCOMMAND_DELAY 82 NORETRIES= 83 NOSAFE_DELETE 83 ON_ERROR= 82 RETRIES= 83 SAFE_DELETE 83 syntax 82 SET SYSTEM description 85 example 85 switches CONSOLE_LUN_ID= 85 NAME= 85 syntax 85 SET VDISK description 86 examples 88 switches MIRRORED_WRITEBACK 45, 86 NAME= 86
Index
NOMIRRORED_WRITEBACK 46, 86 NOPREFERRED_PATH 87 NOREAD_CACHE 87 NOWRITE_PROTECT 88 OS_UNIT_ID= 86 READ_CACHE 87 SIZE= 87 WORLD_WIDE_LUN_NAME= 30, 87 WRITE_PROTECT 88 syntax 86 SHOW commands 89 output samples 108 SHOW DISK description 91 examples 91 syntax 91 SHOW DISK_GROUP description 92 examples 92 syntax 92 SHOW DR_GROUP description 90 example 90 syntax 90 SHOW HOST description 93 examples 93 output samples 110 syntax 93 SHOW LUN description 94 examples 94 output samples 111 syntax 94 SHOW MANAGER description 95 examples 95 syntax 95 SHOW MONITOR description 96 examples 96
syntax 96 SHOW OPTIONS description 97 example 97 syntax 97 SHOW POWER description 98 examples 98 syntax 98 SHOW SYSTEM description 99 examples 99 output samples 108 syntax 99 using 104 SHOW VDISK description 100 examples 100 output samples 109 syntax 100 SHOW WORLD_WIDE_NAME description 101 example 101 syntax 101 SHUTDOWN description 102 examples 102 syntax 102 simple configuration, creating a 104 SNAPSHOT, ADD 41 SSSU installing 15 naming operating systems 38 overview 14 setting interface options 82 storage system, creating 104 Sun Solaris 38, 80 switch defaults, ADD VDISK 48 symbols in text 10 SYSTEM ADD 43 DELETE 60
127
Index
SET 85 SHOW 99
T
technical support, HP 12 text symbols 10 Tru64 UNIX 38, 80 and the CONSOLE_LUN_ID 85
SHOW 100 virtual disk, creating and presenting a 106 Vraid0 47 Vraid1 34, 47 Vraid5 34, 47
W
websites, HP storage 12 Windows 2000 38, 80 Windows NT 38, 80 WORLD_WIDE_LUN_NAME, use with snapshots 30 WORLD_WIDE_NAME, SHOW 101
V
VDISK ADD 45 DELETE 61 SET 86
128

Storage System Scripting Utility AA-RU5HC-TE-V31

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Storage System Scripting Utility AA-RU5HC-TE-V31

Загружено:

Авторское право:

Доступные форматы

Reference Guide

hp StorageWorks Storage System Scripting Utility

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

about this guide About this Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

About this Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

About this Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

About this Guide

Document Conventions Text Symbols

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

About this Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

About this Guide

Be sure to have the following information available before calling:

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Formatting and Output of Returned Data

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Installing the Storage System Scripting Utility

Installing the HP-UX Kit

3. Mount the CD-ROM with the command:

5. Enter the following command to run the installation program (swinstall):

The SSSU executable is installed in the following directory:

Command line version, type

Graphical version, type

Installing the IBM Host Kit

2. Go to the /aix_spec directory. 3. Execute the command

Follow this procedure to install the SSSU application.

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

The following file is extracted:

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Note: Substitute your CD-ROM device for cdrom0c, if necessary.

3. Change directories on the CD-ROM by entering:

4. Enter the following command to run the installation program:

Note: The l is a lowercase L.

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Starting the Storage System Scripting Utility

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Understanding Paths and Naming Conventions

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Virtual Disk Example

Disk Groups Example

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

SSSU Command Reference

This chapter defines all the commands available in SSSU, including:

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

SSSU Command Reference

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

SSSU Command Reference

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

SSSU Command Reference

Storage System Scripting Utility Enterprise Virtual Array Reference Guide

Storage System Scripting Utility Enterprise Virtual Array Reference Guide