StorageWorks_HSZ40_Array_Controller_Utility_for_____ SystemlManager's Guide for HSZterm Order Number: AA-QC39B-TE This guide explains how to use Version 1.1A of the StorageWorks HSZ40 Array Controller Utility for Digital UNIX. Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ March, 1996 Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from Digital, an authorized sublicensor, or the identified licensor. While Digital believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Digital Equipment Corporation makes no representations that the interconnection of its products in the manner described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1996. All rights reserved. Printed in the U.S.A. Alpha, Bookreader, DEC, DEC 3000, HSZ, StorageWorks, TK50, ULTRIX, and the DIGITAL logo are trademarks of Digital Equipment Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company LTD. NFS is a registered trademark of Sun Microsystems, Inc. OSF/1 is a registered trademark of the Open Software Foundation, Inc. PostScript is a registered trademark of Adobe. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... v 1 Product Overview 1.1 General Implementation Considerations............ 1-1 1.2 Digital UNIX for Alpha Implementations........... 1-1 2 Preparing for Installation 2.1 Using RIS for Client Installations............... 2-1 2.2 Installing the StorageWorks HSZ40 Array Controller Utility in a RIS Server Area.......... 2-2 2.3 Installation Procedure Requirements.............. 2-2 2.3.1 Time Required for Installation ................ 2-2 2.3.2 Login Privileges .............................. 2-2 2.3.3 Hardware Requirements ......................... 2-3 2.3.4 Software Requirements ......................... 2-3 2.3.5 Disk Space Requirements ....................... 2-4 2.3.6 Determining Available Disk Space .............. 2-4 2.4 Backing Up Your System Disk...................... 2-6 2.5 Error Recovery................................... 2-6 3 Installation Procedures 3.1 Installing the StorageWorks HSZ40 Array Controller Utility Locally....................... 3-1 3.1.1 Starting the Installation Procedure ........... 3-2 3.1.1.1 Using CD-ROM Distribution Media............. 3-2 3.1.1.2 Installing the StorageWorks HSZ40 Array Controller Utility from a RIS Server........ 3-2 iii 3.1.2 Responding to Installation Procedure Prompts .. 3-4 3.1.2.1 Selecting Subsets........................... 3-4 3.1.2.2 Monitoring Displays During the Subset Loading Process............................. 3-5 3.2 Installing the StorageWorks HSZ40 Array Controller Utility into a Server Environment..... 3-5 4 Postinstallation Procedures 4.1 Running the Installation Verification Procedure.. 4-1 4.2 After Installing the Software.................... 4-1 4.3 Reporting Product Problems....................... 4-2 5 Using the HSZterm Utility 5.1 Login Privileges................................. 5-1 5.2 Finding the Bus Number........................... 5-2 5.2.1 Starting HSZterm in a Single Controller Configuration.................................. 5-6 5.2.2 Starting HSZterm in a Dual Controller Configuration.................................. 5-7 5.3 Starting the HSZterm Utility..................... 5-9 5.4 Obtaining More Information with the -q Option.... 5-14 6 HSZterm Command Line Description 6.1 Command Line Syntax.............................. 6-1 6.1.1 Command Line Options .......................... 6-1 6.1.2 Detailed Option Descriptions .................. 6-2 6.1.2.1 Options -b [bus-number], -t [target-number], and -l [LUN-number]......................... 6-2 6.1.2.2 Option -f special........................... 6-2 6.1.2.3 Option -v................................... 6-3 6.1.2.4 Option -o logfile........................... 6-5 6.1.2.5 Option -h................................... 6-6 6.1.2.6 Option -q................................... 6-7 6.2 HSZ CLI Commands................................. 6-8 6.2.1 Using the RUN Command from HSZterm ............ 6-8 6.3 Error Messages................................... 6-8 iv 7 HSZterm Protocols A Files Installed on Your System B Sample Installation C Sample Installation Verification Procedure Examples 5-1 Finding the Bus Number ........................ 5-3 5-2 Example of Bus Number ......................... 5-6 5-3 How to Start the HSZterm Utility Using the Bus, Target, and LUN Parameters..................... 5-11 5-4 How to Start the HSZterm Utility Using the -f Option......................................... 5-11 5-5 How to Start the HSZterm Utility with -f and Additional Arguments........................... 5-12 5-6 How to Use the -q Option for More Controller Information.................................... 5-14 B-1 Installation of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System............................... B-1 C-1 IVP of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System......................................... C-1 Tables 2-1 Subset Size (Kilobytes Required) on Digital UNIX Systems .................................. 2-4 6-1 HSZterm Command Line Options .................. 6-1 A-1 Installed StorageWorks HSZ40 Array Controller Utility Files.................................. A-1 v _________________________________________________________________ Preface This guide describes the use and administration of the StorageWorks[TM] HSZ40 Array Controller Utility Digital UNIX[R] software. Intended Audience This guide is intended for the following personnel: o A system manager who manages a node-specific system o A Remote Installation Services (RIS) manager who manages a RIS server area o A system manager who expects to install the StorageWorks HSZ40 Array Controller Utility from the RIS server area of a remote system Structure of This Manual This manual is organized as follows: Chapter 1 Presents an overview of the StorageWorks HSZ40 Array Controller Utility. Chapter 2 Describes the prerequisites necessary for installing the StorageWorks HSZ40 Array Controller Utility. Chapter 3 Describes installation procedures for installing the StorageWorks HSZ40 Array Controller Utility. Chapter 4 Describes procedures that you must do after installing the StorageWorks HSZ40 Array Controller Utility. v Chapter 5 Describes how to use the HSZterm utility. Chapter 6 Describes the HSZterm command line syntax and options. Chapter 7 Describes the protocol rules for the HSZterm utility. Appendix A Presents a list of the files on your system after installation. Appendix B Presents a sample installation of the StorageWorks HSZ40 Array Controller HSZterm Utility on a Digital UNIX system. Appendix C Presents a sample of the Installation Verification Procedure (IVP) software on a Digital UNIX system. vi Related Documentation The following documentation is related to the StorageWorks HSZ40 Array Controller Utility. ___________________________________________________________ Document_Title____________________________Order_Number_____ DEC OSF/1 Installation Guide AA-PS2DE-TE DEC OSF/1 Sharing Software on a Local AA-PS3LC-TE Area Network DEC OSF/1 System Administration AA-PS2RC-TE StorageWorks Array Controllers HS Family EK-HSFAM-UG of Array Controllers User's Guide StorageWorks Array Controllers HS Family EK-HSFAM-SV of_Array_Controllers_Service_Manual________________________ Documentation Conventions The following conventions are used in this manual: [parameter] In command formats, brackets indicate the optional parameters. When you enter the optional parameter, do not enter the brackets. UPPERCASE The Digital UNIX operating system and differentiates between uppercase and lowercase lowercase letters. Literal strings that appear in text, examples, syntax descriptions and function descriptions must be entered exactly as shown. user input This bold typeface is used in interactive examples to indicate user input. system This typeface is used in interactive and code output examples to indicate system output. In text, this typeface is used to indicate the exact name of a command, option, partition, pathname, directory, or file. % The default user prompt is your system name followed by a right angle bracket (>). In this manual, a percent sign (%) is used to represent this prompt. # A number sign is the default superuser prompt. vii In procedures, a sequence such as indicates that you must hold down the key labeled Ctrl while you press another key on the keyboard or a pointing device button. In procedures, a key name is shown enclosed to indicate that you press that key on the keyboard. setld(8) This convention means that the setld command is found in section 8 of the Digital UNIX Reference Manual. viii 1 _________________________________________________________________ Product Overview This chapter describes the HSZterm Utility. HSZterm provides a host-resident virtual maintenance terminal facility for communicating with an HSZ-series controller over its host Small Computer System Interface (SCSI) bus interface. The virtual maintenance terminal communication protocol was developed explicitly for the HSZ-series controllers. 1.1 General Implementation Considerations The terminal interface uses portable C I/O functions and does not support asynchronous terminal I/O. This is not a restriction of the virtual maintenance terminal protocol. The HSZterm utility uses the following SCSI commands when communicating with the HSZ-series controllers: TEST UNIT READY INQUIRY SEND DIAGNOSTIC RECEIVE DIAGNOSTIC REQUEST_SENSE 1.2 Digital UNIX for Alpha Implementations The HSZterm utility issues SCSI commands through the Common Access Method (CAM) interface. The superuser (root) privilege is required to run the HSZterm utility on Digital UNIX Alpha [TM] implementations. Product Overview 1-1 2 _________________________________________________________________ Preparing for Installation Before starting the installation procedures in Chapter 3, complete the preparation requirements outlined in this chapter. This chapter provides the necessary information to make your installation run smoothly. You need to be aware of your installation options. This chapter helps you determine the following: o How do you install the StorageWorks HSZ40 Array Controller Utility from distribution media? o How do you use the Digital UNIX Remote Installation Service (RIS)? o Does the system on which you install the StorageWorks HSZ40 Array Controller Utility meet the hardware, software, and disk space requirements? o How much disk space do you need? 2.1 Using RIS for Client Installations If you expect to install the StorageWorks HSZ40 Array Controller Utility subsets from a RIS server area of a remote system for installation on your local system, first check with your site system administrator to make sure of the following: o A StorageWorks HSZ40 Array Controller Utility for Digital UNIX for HSZterm kit must be installed in the RIS server area and be available for use. o Your system is registered as a RIS client. o If the StorageWorks HSZ40 Array Controller Utility subsets are available to you on a RIS server system, you need the name of that system to start the installation procedure described in this guide. Preparing for Installation 2-1 2.2 Installing the StorageWorks HSZ40 Array Controller Utility in a RIS Server Area If you manage a Remote Installation Services (RIS) server area and intend to install the StorageWorks HSZ40 Array Controller Utility in your server area, see the following sections of this guide: o Appendix A for information about contents of the media kit o Section 2.3 for hardware and software requirements, for the names and numbers of software subsets, and for disk space requirements o Section 3.1.2.2 for information about the displays and prompts that relate to the StorageWorks HSZ40 Array Controller Utility installations To start the installation procedure, do not use the setld(8) command. Use the ris utility. For more information on the ris utility, see Section 3.2. 2.3 Installation Procedure Requirements The following sections discuss the requirements for installing the StorageWorks HSZ40 Array Controller Utility. 2.3.1 Time Required for Installation A local or RIS server installation takes from 5 minutes to 10 minutes depending on the type of media and your system configuration. A RIS client installation can take longer because it is dependent on network activity at the time you do the installation. If the network is not active, you should expect an installation time roughly equal to a local installation with the Installation Verification Procedure (IVP). 2.3.2 Login Privileges You must be able to log in as the superuser on the system where you are installing the StorageWorks HSZ40 Array Controller Utility to have sufficient privileges to install this software. 2-2 Preparing for Installation 2.3.3 Hardware Requirements You need the following hardware to perform the installation: o An HSZ40 array controller with HSOF V2.0 or higher o Software distribution device If you are installing from media, you need a CD-ROM, such as an RRD42. You must know how to load the media supplied with the software distribution kit on the appropriate drive. The documentation for the CD-ROM that you are using explains how to load media. o Terminal You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure for the StorageWorks HSZ40 Array Controller Utility. 2.3.4 Software Requirements The StorageWorks HSZ40 Array Controller Utility for Digital UNIX for HSZterm Version V1.1A requires that Version 2.0 or higher of DEC OSF/1 be installed. In addition, the StorageWorks HSZ40 Array Controller Utility requires the following Digital UNIX software subsets to be loaded on the system where you install the StorageWorks HSZ40 Array Controller Utility software: OSFBASE200 or higher, named "DEC OSF/1 V2.0 Alpha AXP Operating System ( Rev 240 )" The StorageWorks HSZ40 Array Controller Utility files are loaded into /usr/opt/SWA11A. A symbolic link is created in /usr/bin that points to the utility executable. A symbolic link for the manual page is created in /usr/share/man/man8. Symbolic links for the documentation files are created in /usr/share/doclib/StorageWorks. To load the reference pages, you must be able to write to these directories. If your /usr/share/man/man8 directories are NFS[R] mounted or are nonexistent, the subset for the reference pages cannot be made available. Preparing for Installation 2-3 2.3.5 Disk Space Requirements The disk space requirements discussed in this section apply to the file systems on which you load the StorageWorks HSZ40 Array Controller Utility subsets. Table 2-1 lists the disk space requirements for loading the StorageWorks HSZ40 Array Controller Utility software subsets on Digital UNIX for Alpha systems. This table specifies disk space requirements by file system for the convenience of those doing installations on systems where these file systems are mount points for different disk partitions. ________________________ Note ________________________ Table 2-1 lists the disk space occupied by files after installation. If you are extracting files from media using the ris utility only, the StorageWorks HSZ40 Array Controller Utility files require 650 blocks of space to be available in the RIS server area. ______________________________________________________ Table 2-1 Subset Size (Kilobytes Required) on Digital UNIX __________Systems__________________________________________ Subset /usr size in Title_______SubsetName______________________blocks_________ SWACLI11A HSZ40 Array Controller CLI 240 Utility (Digital UNIX) SWAMAN11A HSZ40 Array Controller 28 Utility Manual Pages SWADOC11A HSZ40 Array Controller 966 ____________Utility_Documentation__________________________ 2.3.6 Determining Available Disk Space To determine if you have enough disk space to load the StorageWorks HSZ40 Array Controller Utility for Digital UNIX for HSZterm, follow these steps: 1. Using Table 2-1, total the values for the subsets that you plan to load in each file system. 2-4 Preparing for Installation 2. To determine the current amount of free space for a directory path, log in to the system where you plan to install the StorageWorks HSZ40 Array Controller Utility. You can check which file systems are mounted and where they are by displaying the file /etc/fstab or by executing the /etc/mount command without any arguments. For example, to display /etc/fstab, enter the following command: # more /etc/fstab The system displays the following: /dev/rz2a / ufs rw 1 1 /dev/rz2h /usr ufs rw 1 2 /dev/rz2b swap1 ufs sw 0 2 /dev/rz2g /var ufs rw 1 2 /usr/users@server /usr/users nfs rw,bg 0 0 This display indicates that /usr is mounted on /dev/rz2h. The /usr directory is the only mount point that affects where the StorageWorks HSZ40 Array Controller Utility files are to reside; the system has only one local disk drive and the /usr/opt directory resides on the h partition of that drive. Enter the df(1) command to determine the total space and free space for the file systems where the StorageWorks HSZ40 Array Controller Utility files are to reside. Based on the previous display of the /etc/fstab file, which shows that only /usr is a mount point, you would need to inspect free space only in the /usr file system. Enter the following command to inspect the free space: # df /usr The system displays the following: Filesystem 512-blks used avail capacity Mounted on /dev/rz2h 810952 656540 73316 90% /usr This display indicates that there are 73,316 data blocks free. This free space must accommodate the subset requirements listed in Table 2-1 for both the root directory and /usr file systems. Preparing for Installation 2-5 3. Compare the space required for subsets with the free space currently on the file systems where the StorageWorks HSZ40 Array Controller Utility files are to reside. 2.4 Backing Up Your System Disk Digital recommends that you back up your system disk before installing any software. Use the backup procedures established at your site. For details on performing a system disk backup, see your Digital UNIX documentation. 2.5 Error Recovery If errors occur during the installation, the system displays failure messages. If the installation fails due to insufficient disk space, the installation procedure displays the following message: There is not enough file system space for subset SWACLI11A Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o The prerequisite software version is incorrect. If the system notifies you that any of these conditions exist, take the appropriate action described in the message. 2-6 Preparing for Installation 3 _________________________________________________________________ Installation Procedures This chapter describes the installation procedures for the StorageWorks HSZ40 Array Controller Utility for Digital UNIX for HSZterm software. Before you begin, you must be familiar with the general options and requirements discussed in Chapter 2 that apply to installing the StorageWorks HSZ40 Array Controller Utility. The StorageWorks HSZ40 Array Controller Utility can be installed either locally or remotely, as follows: o Locally from the CD-ROM or the RIS media (for RIS clients). Section 3.1 explains how to perform a local installation. o Remotely to a RIS server area for future client use. The installation procedures assume that you have already created your server environment and are ready to add the StorageWorks HSZ40 Array Controller Utility. Section 3.2 explains how to perform a RIS server installation. 3.1 Installing the StorageWorks HSZ40 Array Controller Utility Locally The StorageWorks HSZ40 Array Controller Utility installation procedure loads the StorageWorks HSZ40 Array Controller Utility files onto a disk that belongs to the system where you perform the installation. When the StorageWorks HSZ40 Array Controller Utility is run, its executable image is mapped into the memory on this system. The following sections explain how to start a local installation procedure and how to respond to installation procedure prompts. Installation Procedures 3-1 3.1.1 Starting the Installation Procedure If you are installing the StorageWorks HSZ40 Array Controller Utility from CD-ROM media, start with Section 3.1.1.1. If you are installing the StorageWorks HSZ40 Array Controller Utility on a client system using a RIS kit, start with Section 3.1.1.2. 3.1.1.1 Using CD-ROM Distribution Media If you are installing the StorageWorks HSZ40 Array Controller Utility from CD-ROM media, start the installation procedure as follows: 1. Log in as the superuser (login name root) to the system where you are installing the StorageWorks HSZ40 Array Controller Utility. 2. Mount the media on the appropriate CD-ROM drive. # mount -r /dev/rz4c /mnt 3. Make sure that you are at the root (/) directory by entering the following command: # cd / 4. Enter a setld(8) command that specifies the -l (load) function and the directory on the CD-ROM where the kit is located. setld -l /mnt/swa11A/kit See Section 3.1.2 to continue the installation. 3.1.1.2 Installing the StorageWorks HSZ40 Array Controller Utility from a RIS Server To install the StorageWorks HSZ40 Array Controller Utility from a RIS server to a RIS client, you must first install the StorageWorks HSZ40 Array Controller Utility in your RIS server environment. See your RIS manager if the StorageWorks HSZ40 Array Controller Utility is not already installed in the RIS server. 3-2 Installation Procedures To install the StorageWorks HSZ40 Array Controller Utility subsets that reside in an /var/adm/ris distribution area on a remote system, start the installation procedure as follows: 1. Log in as the superuser (login name root) to the system where you are installing the StorageWorks HSZ40 Array Controller Utility. 2. Make sure that you are at the root (/) directory by entering the following command: # cd / 3. Enter a setld(8) command that requests the load function and identifies the system where the StorageWorks HSZ40 Array Controller Utility subsets are located. For example, if you are loading the StorageWorks HSZ40 Array Controller Utility subsets from a RIS distribution area on node englishorn, enter the following command: # setld -l englishorn: If an error is displayed by the system, verify that you correctly followed the preparation steps in Section 2.1. See Section 3.1.2 to continue the installation. Installation Procedures 3-3 3.1.2 Responding to Installation Procedure Prompts This section explains the installation procedure prompts and displays. 3.1.2.1 Selecting Subsets After you enter the setld(8) command for local (node- specific) installations, or after you start the ris utility for server installations, the installation procedure displays the names of the StorageWorks HSZ40 subsets and prompts you to specify the subsets that you want to load: host # setld -l /mnt/swa11A/kit The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) HSZ40 Array Controller Utility Documentation 2) HSZ40 Array Controller Utility Manual Pages 3) HSZ40 Array Controller Utility (Alpha) Or you may choose one of the following options: 4) ALL of the above 5) CANCEL selections and redisplay menus 6) EXIT without installing any subsets Press RETURN to display the next screen: Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 4 You are installing the following optional subsets: HSZ40 Array Controller Utility Documentation HSZ40 Array Controller Utility Manual Pages HSZ40 Array Controller Utility (Alpha) Is this correct? (y/n): y When installing this software from a RIS server, note that the subset numbers can vary depending on what products are available in the RIS area. 3-4 Installation Procedures 3.1.2.2 Monitoring Displays During the Subset Loading Process During the installation, the procedure will display a copyright notice and some status messages. Example B-1 provides a sample installation procedure. When the installation procedure completes, a # prompt appears. The installation procedure is invoked by entering the setld -l command. Chapter 4 discusses the postinstallation requirements specified in final informational messages from the procedure. If, during the course of the installation, you encounter errors from the setld(8) utility, see the Diagnostics section of the setld(8) reference page for an explanation of the error and the appropriate action to take. If the verification process fails, you can look in the file /var/adm/fverifylog for information that can help you diagnose the problem. 3.2 Installing the StorageWorks HSZ40 Array Controller Utility into a Server Environment This section explains how to start the installation procedure and load software subsets when you are installing the StorageWorks HSZ40 Array Controller Utility into an environment controlled by RIS. For a CD-ROM media kit, mount the media on the appropriate device of the server node. You will be prompted later to enter the name of the special file for that device. The Guide to Sharing Software on a Local Area Network explains how to install the StorageWorks HSZ40 Array Controller Utility into a RIS server environment. RIS Server Installations The following sample session describes how to add the StorageWorks HSZ40 Array Controller Utility product to the ris area: 1. Log in and become the superuser. 2. Mount the media on the appropriate CD-ROM drive # mount -r /dev/rz4c /mnt Installation Procedures 3-5 3. Invoke the ris utility by entering the following command: # /usr/sbin/ris 4. Select the Install Software option from the main menu by entering "i;" *** RIS Utility Main Menu *** a) ADD a client d) DELETE software products i) INSTALL software products l) LIST registered clients m) MODIFY a client r) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: i 5. Choose option 2 from the RIS Software Installation Menu: RIS Software Installation Menu: 1) Install software into a new area 2) Add software into an existing area 3) Return to previous menu Enter your choice: 2 6. A list of available environments appears from which you might select ris: You have chosen to add a product to an existing environment. Select the remote installation environment: 1) /var/adm/ris/ris0.alpha 'DEC OSF/1 Operating System V3.2 ( Rev 214 )' 2) /var/adm/ris/ris1.alpha 'DEC OSF/1 V3.0 Alpha AXP Operating System ( Rev 347 )' Enter your choice or press RETURN to quit: 1 7. You are prompted next for an input device name: Enter the device special file name or the path of the directory where the software is located. For example; /dev/rmt0h): /mnt/swa11A/kit 3-6 Installation Procedures 8. Choose one of the following options: 1) Extract software from /mnt/swa11A/kit 2) Create symbolic link to /mnt/swa11A/kit Enter your choice: 1 9. The next message lists the software subsets you select for automatic installation. The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) HSZ40 Array Controller Utility Documentation 2) HSZ40 Array Controller Utility Manual Pages 3) HSZ40 Array Controller Utility (Alpha) Or you may choose one of the following options: 4) ALL of the above 5) CANCEL selections and redisplay menus 6) EXIT without installing any subsets Press RETURN to display the next screen: Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 4 You are installing the following optional subsets: HSZ40 Array Controller Utility Documentation HSZ40 Array Controller Utility Manual Pages HSZ40 Array Controller Utility (Alpha) Is this correct? (y/n): y If the displayed subsets are not the ones you intended to choose, enter "N." In this case, the subset selection menu is displayed again, and you can correct your choice of optional subsets. If the displayed subsets are the ones you want to load, enter "Y." Refer to Section 3.1.2.2 for information on monitoring the displays during the subset load process and on completing the installation procedure. Installation Procedures 3-7 10.After the subsets are installed, the following message is displayed: Media extraction complete. 11.The ris main menu then appears for your next selection. 12.After completing the installation, dismount the media from the appropriate device of the server node. 3-8 Installation Procedures 4 _________________________________________________________________ Postinstallation Procedures This chapter explains what you need to do following the installation to make the StorageWorks HSZ40 Array Controller Utility software ready for use. 4.1 Running the Installation Verification Procedure Run the Installation Verification Procedure (IVP) to be sure that the StorageWorks HSZ40 Array Controller Utility is correctly installed. You might also want to run the IVP after a system failure to be sure that users can access the StorageWorks HSZ40 Array Controller Utility. The IVP will verify that the checksums of the installed files match the expected checksums. To run the IVP after an installation, enter the following command: # setld -v SWACLI11A You need an HSZ40 array controller and some target IDs to run the IVP. For detailed examples of the StorageWorks HSZ40 Array Controller Utility IVP, see Appendix C. 4.2 After Installing the Software After installing and verifying the StorageWorks HSZ40 Array Controller Utility software, see Chapter 5 for information on what you must do to set up a system to use the StorageWorks HSZ40 Array Controller Utility software. Postinstallation Procedures 4-1 4.3 Reporting Product Problems No support is provided for the StorageWorks HSZ40 Array Controller Utility. However, if a problem occurs which may be the result of the HSZ40 Array Controller environment, and if you have a Digital service agreement for the HSZ40 Array Controller subsystem, or it is is under warranty, call Digital Multivendor Customer Services. 4-2 Postinstallation Procedures 5 _________________________________________________________________ Using the HSZterm Utility This chapter describes how to configure your system to use the HSZterm utility and provides information on how to start and use the HSZterm utility. The HSZterm utility provides a virtual terminal facility and a command passing capability for communicating with an HSZ40 array controller over the SCSI bus. This virtual terminal protocol was developed explicitly for the HSZ40 program. For more information on the HSZterm protocol, see Chapter 7. 5.1 Login Privileges You must be able to log in as the superuser on the system where you are installing the StorageWorks HSZ40 Array Controller Utility for Digital UNIX for HSZterm to have sufficient privileges to use this software. _______________________ Caution _______________________ Do not run more than one virtual terminal session with the HSZ40 at one time. The HSZterm Utility interfaces directly with the HSZ40 Command Line Interpreter (CLI); there is no mechanism for coordinating disparate commands to the CLI from distinct sessions. If multiple sessions are active at the same time, the results of any operation in either session are unpredictable. ______________________________________________________ Using the HSZterm Utility 5-1 5.2 Finding the Bus Number The HSZterm utility is installed in the /usr/bin directory by setld. The superuser (root) privilege is required to run the HSZterm utility. You must know the bus to which the HSZ40 array is attached before you can use HSZterm. If you do not know the HSZ40 array's bus number, use the uerf command to display the boot record and examine the SCSI mnemonics. On DEC OSF/1 V2.0 and earlier each type of SCSI adapter had a specific mnemonic; the PMAZC was called "asc" and a port on the KZMSA was called "skz". On DEC OSF/1 V3.0 and V3.2 all SCSI buses have the mnemonic "scsi". If the HSZ40 was found when the system last booted, you can get the bus number from the configuration line for the HSZ40. In Example 5-1 these are disks rz33, rz34, rz35, and rz36, which are on "scsi4 bus 4". Therefore, the HSZ40 is on bus 4. If the HSZ40 wasn't found at boot, you may be able to identify which bus it is on by looking at the controller mnemonics. 5-2 Using the HSZterm Utility Example 5-1 Finding the Bus Number # uerf -R -r 300 | page uerf version 4.2-011 (122) ********************************* ENTRY 1. ********************************* ----- EVENT INFORMATION ----- EVENT CLASS OPERATIONAL EVENT OS EVENT TYPE 300. SYSTEM STARTUP SEQUENCE NUMBER 0. OPERATING SYSTEM DEC OSF/1 OCCURRED/LOGGED ON Mon Mar 6 15:00:49 1995 OCCURRED ON SYSTEM robinton SYSTEM ID x00020004 CPU TYPE: DEC 3000 SYSTYPE x00000000 MESSAGE LK401 keyboard, language English _(American) Alpha boot: available memory from _0x7d8000 to 0x4000000 DEC OSF/1 V3.2 (Rev. 214); Mon Mar 6 _14:58:42 MST 1995 physical memory = 64.00 megabytes. available memory = 53.64 megabytes. using 238 buffers containing 1.85 _megabytes of memory tc0 at nexus scc0 at tc0 slot 7 tcds0 at tc0 slot 6 scsi0 at tcds0 slot 0 rz1 at scsi0 bus 0 target 1 lun 0 (DEC _ RZ26 (C) DEC T392) rz2 at scsi0 bus 0 target 2 lun 0 (DEC _ RZ26 (C) DEC 392A) rz3 at scsi0 bus 0 target 3 lun 0 (DEC _ RZ26 (C) DEC T392) tz4 at scsi0 bus 0 target 4 lun 0 (DEC _ TZK10 02B5) scsi1 at tcds0 slot 1 tz8 at scsi1 bus 1 target 0 lun 0 (DEC (continued on next page) Using the HSZterm Utility 5-3 Example 5-1 (Cont.) Finding the Bus Number _ TZ875 (C) DEC 9514) fb0 at tc0 slot 8 1280X1024 bba0 at tc0 slot 7 ln0: DEC LANCE Module Name: PMAD-BA ln0 at tc0 slot 7 ln0: DEC LANCE Ethernet Interface, _hardware address: 08-00-2B-2A-1E-DA tcds1 at tc0 slot 2 scsi2 at tcds1 slot 0 scsi3 at tcds1 slot 1 fta0: DEC DEFTA FDDI Module Name: _PMAF-FA fta0 at tc0 slot 3 fta0: DMA Available. fta0: DEC DEFTA (PDQ) FDDI Interface, _Hardware address: 08-00-2B-A2-84-A7 fta0: Firmware rev: 1.0 nvtc0 at tc0 slot 4 system id of = 2b2a1eda. presto: NVRAM tested read/write ok presto: using 1047040 bytes of NVRAM _at 0x8caf2000 presto: primary battery ok tza0 at tc0 slot 5 scsi4 at tza0 rz33 at scsi4 bus 4 target 1 lun 0 _(DEC HSZ40 (C) DEC V25Z) rz34 at scsi4 bus 4 target 2 lun 0 _(DEC HSZ40 (C) DEC V25Z) rz35 at scsi4 bus 4 target 3 lun 0 _(DEC HSZ40 (C) DEC V25Z) rz36 at scsi4 bus 4 target 4 lun 0 _(DEC HSZ40 (C) DEC V25Z) DEC3000 - M500 system Firmware revision: 2.4 PALcode: OSF version 1.28 dli: configured SuperLAT. Copyright 1993 Meridian _Technology Corp. All rights (continued on next page) 5-4 Using the HSZterm Utility Example 5-1 (Cont.) Finding the Bus Number _reserved. To confirm which bus the HSZ40 is on, use the scu utility. o First, make sure the HSZ40 is powered up and attached to the SCSI bus. o If the HSZ40 hasn't been configured and you have a dual controller subsystem, remove the program card from one of the controllers. o Run the scu scan commands; scu scan and scu show on the bus to which you think the HSZ40 is attached. If it is the right bus, you will see a target number (target 2 is the factory-set default) with Logical Unit Number (LUNs) 0 through 7 with Device Type (not present). Example 5-2 shows an HSZ40 at Bus 4, targets 1 through 4, with LUNs 0 through 7. Where LUNs are defined, the device type is "Direct Access"; otherwise it is "not present". If no targets are listed for a bus on which you know a HSZ40 resides, you must hook up a terminal or set up a tip connection to the HSZ40 serial port and issue the SET THIS ID = (x,x) command. To use tip, add the following line anywhere in the /etc /remote file and then run tip using the same name you added in the /etc/remote file: hsz40:dv=/dev/tty01:br#19200:pa=none: Then, enter the following command: hosts # tip hsz40 HSZ> Using the HSZterm Utility 5-5 Example 5-2 Example of Bus Number # scu scan edt bus 4 Scanning bus 4, please be patient... # scu show edt bus 4 CAM Equipment Device Table (EDT) Information: Bus: 4, Target: 1, Lun: 0, Device Type: Direct Access Bus: 4, Target: 1, Lun: 1, Device Type: Direct Access Bus: 4, Target: 1, Lun: 2, Device Type: Direct Access Bus: 4, Target: 1, Lun: 3, Device Type: Direct Access Bus: 4, Target: 1, Lun: 4, Device Type: Direct Access Bus: 4, Target: 1, Lun: 5, Device Type: (not present) Bus: 4, Target: 1, Lun: 6, Device Type: (not present) Bus: 4, Target: 1, Lun: 7, Device Type: (not present) Bus: 4, Target: 2, Lun: 0, Device Type: Direct Access Bus: 4, Target: 2, Lun: 1, Device Type: (not present) Bus: 4, Target: 2, Lun: 2, Device Type: (not present) Bus: 4, Target: 2, Lun: 3, Device Type: (not present) Bus: 4, Target: 2, Lun: 4, Device Type: (not present) Bus: 4, Target: 2, Lun: 5, Device Type: (not present) Bus: 4, Target: 2, Lun: 6, Device Type: (not present) Bus: 4, Target: 2, Lun: 7, Device Type: (not present) Bus: 4, Target: 3, Lun: 0, Device Type: Direct Access Bus: 4, Target: 3, Lun: 1, Device Type: (not present) Bus: 4, Target: 3, Lun: 2, Device Type: (not present) Bus: 4, Target: 3, Lun: 3, Device Type: (not present) Bus: 4, Target: 3, Lun: 4, Device Type: (not present) Bus: 4, Target: 3, Lun: 5, Device Type: (not present) Bus: 4, Target: 3, Lun: 6, Device Type: (not present) Bus: 4, Target: 3, Lun: 7, Device Type: (not present) Bus: 4, Target: 4, Lun: 0, Device Type: Direct Access Bus: 4, Target: 4, Lun: 1, Device Type: (not present) Bus: 4, Target: 4, Lun: 2, Device Type: (not present) Bus: 4, Target: 4, Lun: 3, Device Type: (not present) Bus: 4, Target: 4, Lun: 4, Device Type: (not present) Bus: 4, Target: 4, Lun: 5, Device Type: (not present) Bus: 4, Target: 4, Lun: 6, Device Type: (not present) Bus: 4, Target: 4, Lun: 7, Device Type: (not present) 5.2.1 Starting HSZterm in a Single Controller Configuration If you have a single controller and have identified the bus and target, you can start HSZterm and start configuring your HSZ40. The example below shows the command to use 5-6 Using the HSZterm Utility to start HSZterm for the HSZ40 identified in the previous example. This HSZ40 is at bus 4 and target 2. This example uses LUN 7, but on a new system you can use any LUN. host # hszterm -b4 -t2 -l7 ________________________ Note ________________________ Once your system is configured, we recommend using an unconfigured LUN. ______________________________________________________ 5.2.2 Starting HSZterm in a Dual Controller Configuration If the HSZ40s are not factory-configured in dual-redundancy mode, the HSZ40 subsystems will fail to communicate with the host. To configure the HSZ40s into dual-redundancy mode, perform the following steps. o Remove the program card from one controller. (For this example, call this controller B.) o Start the other controller. (For this example, call this controller A.) o Use HSZterm to issue the "show this" command on controller A. HSZ-A> Controller: HSZ40 (C) DEC CX01105912 Firmware V25Z-0, Hardware 0000 Configured for dual-redundancy with ZG42800024 In dual-redundant configuration SCSI address 6 Time: 07-MAR-1995 11:22:03 Host port: SCSI target(s) (1, 2, 3, 4), Preferred target(s) (1, 3) Cache: 32 megabyte write cache, version 2 Cache is GOOD Battery is GOOD No unflushed data in cache CACHE_FLUSH_TIMER = DEFAULT (10 seconds) CACHE_POLICY = A HSZ-A> o If the controller A is already set for dual-redundancy, Using the HSZterm Utility 5-7 repeat the above steps for controller B. If both HSZ40s are configured for dual-redundancy, no other actions need be taken. Proceed to Section 5.3. o Set the prompt on controller A to distinguish it from controller B using the "set this prompt" command. o Set the id to a unique number using the "set this id" command. (The default factory setting is 2, so at least one of the HSZ40s will require a new ID.) o Exit HSZterm and stop the controller by using the "shutdown this" command. o Start controller B by pushing in the program card and hitting the reset button. o Change the prompt on controller B with the "set this prompt" command. o Start controller A by replacing the program card and hitting the reset button. (Ignore any "Controller misconfigured" error messages.) o Configure the HSZ40s for failover using the "set failover copy = this" and wait for the HSZ40s to restart. o Set new IDs for both controllers using the "set this id=(#,#) preferred=(#,#)" command, where # is any unique id number on the bus. SCSI error messages, such as in the example below, can be displayed if failover occurs or the HSZ40 is restarted while the HSZterm Utility is running. These are event notification messages and do not indicate serious system problems. %HSZterm HSZterm: SEND DIAGNOSTIC ioctl failed: %s. CAM status = 0x44 (SIM Queue frozen-CCB request completed with an err) HSZterm: CHECKSENSE status returned from SCSI command. HSZterm: Device not ready. HSZterm: ASC = 4, ASQ = 0. HSZterm: Unit Attention. HSZterm: ASC = a0, ASQ = 5. 5-8 Using the HSZterm Utility 5.3 Starting the HSZterm Utility To start the HSZterm utility, enter hszterm and identify the HSZ40 array controller with which you wish to communicate. You identify the HSZ40 array controller through the path to the device using the -f option or specify the bus, target, and logical unit numbers using -b, -t, and -l options. You can obtain the bus and target using the file command. The LUN is the last digit in the unit number. The program is invoked by entering one of the following commands: # hszterm -f # hszterm -b -t -l where: is the path for the device (that is, /dev/rrz9a). is the number of the SCSI bus. is the target ID of the HSZ40 array controller. is the logical unit number of one of the devices connected to the HSZ40 array controller. If you are running HSZterm on an HSZ40 array controller with no units or LUNs set up on it, use the target ID and LUN 0. ________________________ Note ________________________ Digital recommends that you use the (-b -t -l) method to reach an undefined LUN. ______________________________________________________ The hszterm command either starts a virtual terminal session with the HSZ40 array controller over the SCSI bus, or sends commands to the HSZ40 array controller with the output of those commands going to stdout. The HSZterm utility determines the mode in which to run in by checking for additional arguments on the command line. The HSZterm utility then establishes a communications link with the HSZ40 array controller. From this point on, it appears as if the terminal is directly attached to the HSZ40 array controller. Using the HSZterm Utility 5-9 The following three examples show different ways to start the HSZterm utility. Example 5-3 uses the bus, target, and LUN parameters to start the HSZterm Utility. This is the preferred start-up method. 5-10 Using the HSZterm Utility Example 5-3 How to Start the HSZterm Utility Using the Bus, Target, and LUN Parameters # hszterm -b4 -t1 -l7 Starting HSZterm Version V1.1A Copyright Digital Equipment Corporation 1996. All rights reserved Copyright Digital Equipment Corporation 1993, 1995. All rights reserved. HSZ40 Firmware version V25Z-0, Hardware version 0000 Last fail code: 20080000 Press " ?" at any time for help. HSZ> Example 5-4 starts the HSZterm utility by means of the -f option and a special file. Example 5-4 How to Start the HSZterm Utility Using the -f Option # hszterm -f /dev/rrz33c Starting HSZterm Version V1.1A Copyright Digital Equipment Corporation 1996. All rights reserved Copyright Digital Equipment Corporation 1993, 1995. All rights reserved. HSZ40 Firmware version V25Z-0, Hardware version 0000 Last fail code: 20080000 Press " ?" at any time for help. HSZ> Example 5-5 shows how to start the HSZterm utility in command mode with additional arguments. When the HSZterm utility is started with additional arguments, it immediately establishes a connection with the HSZ40 array controller and passes arguments as commands to the HSZ40 array controller. The results are output to stdout. Using the HSZterm Utility 5-11 Example 5-5 How to Start the HSZterm Utility with -f and Additional Arguments # hszterm -f /dev/rrz33c "show this" help Copyright Digital Equipment Corporation 1993, 1995. All rights reserved. HSZ40 Firmware version V25Z-0, Hardware version 0000 Last fail code: 20080000 Press " ?" at any time for help. HSZ> Controller: HSZ40 (C) DEC CX01105912 Firmware V25Z-0, Hardware 0000 Configured for dual-redundancy with ZG42800024 In dual-redundant configuration SCSI address 6 Time: 07-MAR-1995 11:27:38 Host port: SCSI target(s) (1, 2, 3, 4), Preferred target(s) (1, 3) Cache: 32 megabyte write cache, version 2 Cache is GOOD Battery is GOOD No unflushed data in cache CACHE_FLUSH_TIMER = DEFAULT (10 seconds) CACHE_POLICY = A HSZ> Help may be requested by typing a question mark (?) at the CLI prompt. This will print a list of all available commands For further information the user may enter a partial command and type a space followed by a "?" to print a list of all available options at that point in the command. For example: SET THIS_CONTROLLER ? Prints a list of all legal SET THIS_CONTROLLER commands HSZ> When the last argument is processed, the HSZterm utility exits automatically. 5-12 Using the HSZterm Utility The HSZterm utility uses standard input (stdin) and standard output (stdout), allowing the file containing HSZ40 commands to be passed directly to the HSZ40 array controller and allowing the output to be saved to a file. Input and output also can be redirected and piped. Using the HSZterm Utility 5-13 5.4 Obtaining More Information with the -q Option To obtain more information on the HSZ40 array controller, you can use the -q option, which causes the HSZterm utility to issue a SCSI inquiry command at startup. Example 5-6 is an example of the -q option: Example 5-6 How to Use the -q Option for More Controller Information # hszterm -q -f /dev/rrz33c Starting HSZterm Version V1.1A Copyright Digital Equipment Corporation 1996. All rights reserved Periph Device Type = 0x0 (Direct-access Device) Periph Qualifier = 0x0 (Device supported, is (may be) connected) Device Type Modifier = 0x0 RMB = 0x0 (Medium is not removable) ANSI Version = 0x2 ECMA Version = 0x0 ISO Version = 0x0 AENC = 0x0 TrmIOP = 0x0 Response Data Format = 0x2 Additional Length = 0x51 Soft Reset = 0x0 Command Queue = 0x1 Linked = 0x0 Synchronous = 0x1 16 bit bus = 0x1 32 bit bus = 0x0 Relative Addressing = 0x0 Vendor Identification = DEC Product Identification = HSZ40 (C) DEC Product Revision Level = V25Z Copyright Digital Equipment Corporation 1993, 1995. All rights reserved. HSZ40 Firmware version V25Z-0, Hardware version 0000 Last fail code: 20080000 Press " ?" at any time for help. HSZ> ^D 5-14 Using the HSZterm Utility 6 _________________________________________________________________ HSZterm Command Line Description This chapter describes the HSZterm Command Line Interface (CLI) beginning with the syntax. The options and commands are described in the following sections. 6.1 Command Line Syntax The syntax for the HSZterm command line is as follows: hszterm options [commands] 6.1.1 Command Line Options Table 6-1 describes the HSZterm options. Table_6-1_HSZterm_Command_Line_Options_____________________ Option_Variable__Function__________________________________ -b bus-number Specifies the bus number. -t target- Specifies the target number. number -l LUN-number Specifies the LUN number. -f special Specifies the path to the device. -v Sets the level of verbosity. The HSZterm utility can be made to perform its actions with a great deal of diagnostic output. This option allows setting the level of this extra output. -o logfile Specifies the log file in which to save the output. (continued on next page) HSZterm Command Line Description 6-1 Table_6-1_(Cont.)_HSZterm_Command_Line_Options_____________ Option_Variable__Function__________________________________ -h Causes the command to display a brief help message. -q Causes the HSZterm utility to perform a _________________SCSI_inquiry_command_at_startup.__________ 6.1.2 Detailed Option Descriptions The following sections describe the HSZterm command line options. 6.1.2.1 Options -b [bus-number], -t [target-number], and -l [LUN-number] The -b, -t, and -l options must be used together to identify which HSZ40 controller to communicate with. These options specify the bus number, target number, and LUN number. host # hszterm -b15 -t3 -l7 Starting HSZterm Version V1.1A Copyright Digital Equipment Corporation 1996. All rights reserved Copyright Digital Equipment Corporation 1993, 1995. All rights reserved. HSZ40 Firmware version V25Z-0, Hardware version 0000 Last fail code: 20080000 Press " ?" at any time for help. HSZ40 B> 6.1.2.2 Option -f special The -f option identifies the HSZ40 controller with which to communicate when you have a device file that points to a device associated with the HSZ40 controller. You can use any partition on the device. ________________________ Note ________________________ Digital recommends that you use the (-b -t -l) method to reach an undefined LUN. ______________________________________________________ 6-2 HSZterm Command Line Description # hszterm -f /dev/rrz33c Starting HSZterm Version V1.1A Copyright Digital Equipment Corporation 1996. All rights reserved Copyright Digital Equipment Corporation 1993, 1995. All rights reserved. HSZ40 Firmware version V25Z-0, Hardware version 0000 Last fail code: 018800A0 Press " ?" at any time for help. HSZ> 6.1.2.3 Option -v The -v option traces the HSZterm utility's actions. host # hszterm -b15 -t3 -l7 -v Starting HSZterm Version V1.1A Copyright Digital Equipment Corporation 1996. All rights reserved A device has been selected. %HSZterm - SCSI_Inq() called... Do Connect. %HSZterm - SCSI_TUR() called... %HSZterm - SIM_Release() called... %HSZterm HSZterm: TEST UNIT READY ioctl failed: %s. CAM status = 0x44 (SIM Queue frozen-CCB request completed with an err) HSZterm: CHECKSENSE status returned from SCSI command. %HSZterm - SCSI_RequestSense() called... HSZterm: Device not ready. HSZterm: ASC = 4, ASQ = 0. %HSZterm - Validate_DiagPages() called... %HSZterm - SCSI_SendDiag() called... %HSZterm - SCSI_RecvDiag() called... %HSZterm - VT_Send() called... %HSZterm - SCSI_SendDiag() called... %HSZterm - VT_Read() called... HSZterm Command Line Description 6-3 %HSZterm - SCSI_SendDiag() called... %HSZterm - SCSI_RecvDiag() called... Copyright ) Digital Equipment Corporation 1993, 1995. All rights reserved. HSZ40 Firmware version V25Z-0, Hardware version 0000 Last fail code: 20080000 Press " ?" at any time for help. %HSZterm - VT_Read() called... %HSZterm - SCSI_SendDiag() called... %HSZterm - SCSI_RecvDiag() called... HSZ40 B> 6-4 HSZterm Command Line Description 6.1.2.4 Option -o logfile The -o option specifies the log file in which to save the output of the session. This is easier to use than trying to redirect stdout during an interactive session. The following example shows a session and the log file generated by that session. host # hszterm -b15 -t1 -l7 -o test1.log Starting HSZterm Version V1.1A Copyright Digital Equipment Corporation 1996. All rights reserved Copyright ) Digital Equipment Corporation 1994 HSZ40 Firmware version V20Z-0, Hardware version 0000 Last fail code: 08080000 Press " ?" at any time for help. HSZ40 A> show unit full LUN Uses -------------------------------------------------------------- D100 DISK120 Switches: RUN NOWRITE_PROTECT READ_CACHE WRITEBACK_CACHE MAXIMUM_CACHED_TRANSFER_SIZE = 1024 State: ONLINE to this controller Not reserved Write cache good PREFERRED_PATH = THIS_CONTROLLER D300 DISK130 Switches: RUN NOWRITE_PROTECT READ_CACHE WRITEBACK_CACHE MAXIMUM_CACHED_TRANSFER_SIZE = 1024 State: ONLINE to the other controller Write cache good PREFERRED_PATH = OTHER_CONTROLLER HSZ40 A> ^D host # cat test1.log HSZterm Command Line Description 6-5 Copyright ) Digital Equipment Corporation 1994 HSZ40 Firmware version V20Z-0, Hardware version 0000 Last fail code: 08080000 Press " ?" at any time for help. HSZ40 A> show unit full LUN Uses -------------------------------------------------------------- D100 DISK120 Switches: RUN NOWRITE_PROTECT READ_CACHE WRITEBACK_CACHE MAXIMUM_CACHED_TRANSFER_SIZE = 1024 State: ONLINE to this controller Not reserved Write cache good PREFERRED_PATH = THIS_CONTROLLER D300 DISK130 Switches: RUN NOWRITE_PROTECT READ_CACHE WRITEBACK_CACHE MAXIMUM_CACHED_TRANSFER_SIZE = 1024 State: ONLINE to the other controller Write cache good PREFERRED_PATH = OTHER_CONTROLLER HSZ40 A> host # host # 6.1.2.5 Option -h The -h option generates a short help file message describing the options for HSZterm, as follows: host # hszterm -h usage: hszterm [ options ] Options: 6-6 HSZterm Command Line Description -b - Specify bus. -t - Specify target. -l - Specify LUN. -f - Path to device. -o - Log file. -q - Display Inquiry data at startup. -v - Set level of verbosity. -h - Simple help message. host # 6.1.2.6 Option -q The -q option causes the HSZterm utility to issue a SCSI inquiry command at startup and write the results of the inquiry to stdout. host # hszterm -b15 -t1 -l7 -q Starting HSZterm Version V1.1A Copyright Digital Equipment Corporation 1996. All rights reserved Periph Device Type = 0x1F (Unknown Device) Periph Qualifier = 0x1 (Device supported, is not connected) Device Type Modifier = 0x0 RMB = 0x0 (Medium is not removable) ANSI Version = 0x2 ECMA Version = 0x0 ISO Version = 0x0 AENC = 0x0 TrmIOP = 0x0 Response Data Format = 0x2 Additional Length = 0x51 Soft Reset = 0x0 Command Queue = 0x1 Linked = 0x0 Synchronous = 0x1 16 bit bus = 0x1 32 bit bus = 0x0 Relative Addressing = 0x0 Vendor Identification = DEC Product Identification = HSZ40 (C) DEC Product Revision Level = V25Z-0 Copyright Digital Equipment Corporation 1993, 1995. All rights reserved. HSZ40 Firmware version V25Z-0, Hardware version 0000 Last fail code: 08080000 Press " ?" at any time for help. HSZ40 A> HSZterm Command Line Description 6-7 6.2 HSZ CLI Commands The HSZterm utility supports a subset of the HSZ CLI commands found in the StorageWorks HS Family of Array Controllers User's Guide. Refer to this User's Guide for the command lists. 6.2.1 Using the RUN Command from HSZterm The hszterm command restricts access to the HSZ40 programs that can be used with the RUN command. The set of allowed commands can be set using the environment variable HSZTERM_ RUN. This is a comma separated list of the utilities the user would like to be able to run. If no list is specified the default list will consist of CONFIG, FLS, FMU, CLCP and CLONE. It will never allow running the utilities CFMENU, VTDPY, DILX or TILX, even when they are included in the list specified by HSZTERM_RUN. This example limits the run list to CONFIG, CLONE and FLS. # setenv HSZTERM_RUN CONFIG,CLONE,FLS 6.3 Error Messages The HSZterm utility supports some of the HSZ40 CLI error messages described in the HS Family of Array Controllers User's Guide. See that manual to interpret CLI error messages. 6-8 HSZterm Command Line Description 7 _________________________________________________________________ HSZterm Protocols The HSZterm utility uses vendor-specific diagnostic pages for communicating with the HSZ40 array controller. These pages provide two-way communication with the Command Line Interpreter (CLI) on the HSZ40 array controller. The virtual terminal protocol was developed explicitly for the HSZ40 program. The SCSI commands used by the HSZterm utility are as follows: TEST UNIT READY INQUIRY SEND DIAGNOSTIC RECEIVE DIAGNOSTIC The virtual terminal protocol allows asynchronous delivery of control characters using the HSZ40 CLI Send Diagnostic Page with the CLI Cmd Code field set to ANSWER and the control character placed in the first byte of the ASCII text buffer. Any other characters in the ASCII text buffer are ignored. There is no connection made between the host process and the HSZ40 array controller. Therefore, it is possible to implement a host interface that would allow you to exit the host program while a program is running within the HSZ40 array controller and resume the terminal session at a later time. This also implies that if multiple users attempt to have simultaneous virtual terminal sessions, the resulting messages would be unpredictable. HSZterm Protocols 7-1 A _________________________________________________________________ Files Installed on Your System This appendix lists the files on your system after you install StorageWorks HSZ40 Array Controller Utility for Digital UNIX for HSZterm. Table A-1 describes the contents of the StorageWorks HSZ40 Array Controller Utility directories. Table A-1 Installed StorageWorks HSZ40 Array Controller Utility __________Files__________________________________________________ Directory________File__________________Description_______________ /usr/bin hszterm HSZterm executable file /usr/share/man hszterm.8 Reference page file /man8 /usr/share cover_letter.ps Customer letter, /doclib cover_letter.txt PostScript /StorageWorks hszterm_smg.ps Customer letter, text hszterm_smg.txt V1.1A System Manager's hszterm_smg.decw_ Guide, PostScript[R] book V1.1A System Manager's hszterm_smg.decw_ Guide, text bookshelf V1.1A System Manager's _______________________________________Guide,_Bookreader_________ Files Installed on Your System A-1 B _________________________________________________________________ Sample Installation Example B-1 is a sample installation procedure of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System. Example B-1 Installation of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System # setld -l /mnt/swa11A/kit The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) HSZ40 Array Controller Utility (Alpha) 2) HSZ40 Array Controller Utility Documentation 3) HSZ40 Array Controller Utility Manual Pages Or you may choose one of the following options: 4) ALL of the above 5) CANCEL selections and redisplay menus 6) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 4 You are installing the following optional subsets: HSZ40 Array Controller Utility (Alpha) HSZ40 Array Controller Utility Documentation HSZ40 Array Controller Utility Manual Pages (continued on next page) Sample Installation B-1 Example B-1 (Cont.) Installation of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. ***** ***** Subset: SWACLI11A ***** Phase: PRE_L ***** Action: ***** StorageWorks HSZ40 Array Controller Utility V1.1A for Digital UNIX Installation Procedure *********************************************************************** * * * Copyright Digital Equipment Corporation 1994, 1995. * * All rights reserved. * * * * Restricted Rights: Use, duplication, or disclosure by the U.S. * * Government is subject to restrictions as set forth in subparagraph * * (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in * * FAR 52.227-14 Alt. III, as applicable. * * * * This software is proprietary to and embodies the confidential * * technology of Digital Equipment Corporation. Possession, use, * * or copying of this software and media is authorized only pursuant * * to a valid license from Digital or an authorized sublicensor. * * * *********************************************************************** ***** ***** SWACLI11A: PRE_L phase complete. ***** HSZ40 Array Controller Utility (Alpha) Copying from /mnt/swa11A/kit (disk) Verifying (continued on next page) B-2 Sample Installation Example B-1 (Cont.) Installation of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System ***** ***** Subset: SWAMAN11A ***** Phase: PRE_L ***** Action: ***** StorageWorks HSZ40 Array Controller Utility V1.1A for Digital UNIX Installation Procedure *********************************************************************** * * * Copyright Digital Equipment Corporation 1994, 1995. * * All rights reserved. * * * * Restricted Rights: Use, duplication, or disclosure by the U.S. * * Government is subject to restrictions as set forth in subparagraph * * (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in * * FAR 52.227-14 Alt. III, as applicable. * * * * This software is proprietary to and embodies the confidential * * technology of Digital Equipment Corporation. Possession, use, * * or copying of this software and media is authorized only pursuant * * to a valid license from Digital or an authorized sublicensor. * * * *********************************************************************** ***** ***** SWAMAN11A: PRE_L phase complete. ***** HSZ40 Array Controller Utility Manual Pages Copying from /mnt/swa11A/kit (disk) Verifying (continued on next page) Sample Installation B-3 Example B-1 (Cont.) Installation of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System ***** ***** Subset: SWADOC11A ***** Phase: PRE_L ***** Action: ***** StorageWorks HSZ40 Array Controller Utility V1.1A for Digital UNIX Installation Procedure *********************************************************************** * * * Copyright Digital Equipment Corporation 1994, 1995. * * All rights reserved. * * * * Restricted Rights: Use, duplication, or disclosure by the U.S. * * Government is subject to restrictions as set forth in subparagraph * * (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in * * FAR 52.227-14 Alt. III, as applicable. * * * * This software is proprietary to and embodies the confidential * * technology of Digital Equipment Corporation. Possession, use, * * or copying of this software and media is authorized only pursuant * * to a valid license from Digital or an authorized sublicensor. * * * *********************************************************************** ***** ***** SWADOC11A: PRE_L phase complete. ***** HSZ40 Array Controller Utility Documentation Copying from /mnt/swa11A/kit (disk) Verifying (continued on next page) B-4 Sample Installation Example B-1 (Cont.) Installation of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System ***** ***** Subset: SWACLI11A ***** Phase: POST_L ***** Action: ***** Creating symbolic link... ***** ***** SWACLI11A: POST_L phase complete. ***** Configuring "HSZ40 Array Controller Utility (Alpha)" (SWACLI11A) ***** ***** Subset: SWAMAN11A ***** Phase: POST_L ***** Action: ***** Creating symbolic links... ***** ***** SWAMAN11A: POST_L phase complete. ***** Configuring "HSZ40 Array Controller Utility Manual Pages" (SWAMAN11A) ***** ***** Subset: SWADOC11A ***** Phase: POST_L ***** Action: ***** Creating symbolic links... ***** ***** SWADOC11A: POST_L phase complete. ***** Configuring "HSZ40 Array Controller Utility Documentation" (SWADOC11A) (continued on next page) Sample Installation B-5 Example B-1 (Cont.) Installation of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System B-6 Sample Installation C _________________________________________________________________ Sample Installation Verification Procedure Example C-1 is a sample installation verification procedure the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System. Example C-1 IVP of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System # setld -v SWACLI11A HSZ40 Array Controller Utility (Alpha) (SWACLI11A) ***** ***** Subset: SWACLI11A ***** Phase: V ***** Action: ***** Beginning of the Installation Verification Procedure. (continued on next page) Sample Installation Verification Procedure C-1 Example C-1 (Cont.) IVP of the StorageWorks HSZ40 Array Controller Utility Program on the Digital UNIX Operating System *********************************************************************** * * * Copyright Digital Equipment Corporation 1994, 1995. * * All rights reserved. * * * * Restricted Rights: Use, duplication, or disclosure by the U.S. * * Government is subject to restrictions as set forth in subparagraph * * (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in * * FAR 52.227-14 Alt. III, as applicable. * * * * This software is proprietary to and embodies the confidential * * technology of Digital Equipment Corporation. Possession, use, * * or copying of this software and media is authorized only pursuant * * to a valid license from Digital or an authorized sublicensor. * * * *********************************************************************** Looking for an HSZ40. IVP - StorageWorks HSZ40 Array Controller Utility was succesfully installed End of the Installation Verification Procedure. ***** ***** SWACLI11A: V phase complete. ***** C-2 Sample Installation Verification Procedure