MTI9000 DiskArray

http://www-personal.umich.
edu/~rak/9k_manual/
Click on the Topic you would like to see
1. 2. 3. 4. 5. 6. 7. 8. 9. 10.
Introduction Software Installation RPC-Based Utilities Configuring the Array Monitoring Array Events Making Storage Available Replacing Failed Components Error Messages: Desc. and Action Technical Support Numbers Appendix A: HP Patch Installation
MTI Series 9000 Disk Array Subsystem Users Manual Integration with UNIX systems: Sun, HP, IBM, SGI, & DEC
MTI 1111 Pasquinelli Drive Suite 400 Westmont, IL 60559
http://www-personal.umich.edu/~rak/9k_manual/18-Feb-08 11:28:25 AM
http://www-personal.umich.edu/~rak/9k_manual/9kintro_ToC.html
1. Introduction
http://www-personal.umich.edu/~rak/9k_manual/9kintro_ToC.html18-Feb-08 11:28:29 AM
http://www-personal.umich.edu/~rak/9k_manual/9000swinstall_ToC.html
1. Software Installation 1. Option to Retrieve Software from the Internet 2. HP HP-UX for Series 700 1. HP 700 - Software Management Using MTI "INSTALL" 1. HP 700 - Load Software from Local Tape Drive 2. HP 700 - Load Software from Remote Tape Drive 3. HP 700 - Load Software from File Retrieved over the Internet 4. HP 700 - Install Software 5. HP 700 - Check Software 6. HP 700 - Update Software 7. HP 700 - Remove Software 3. HP HP-UX for Series 800 1. HP 800 - Prepare HP-UX for Series 9000 Software 1. HP 800 - HP-UX 9.0.4 - Installing PHKL_5405 & Configuring the spt Device Driver 1. HP/UX 9.0.4 - Obtaining the patch from HP 2. HP/UX 9.0.4 - Hints to Installing PHKL_5405 & Configuring spt 3. HP/UX 9.0.4 - Configuring spt 4. HP/UX 9.0.4 - Recommended Steps After Installing spt 2. HP 800 - HP/UX 10.x - Installing PHKL_5406 & Configuring the spt Device Driver 1. HP/UX 10.x - Obtaining the patch from HP 2. HP/UX 10.x - Hints to Installing PHKL_5406 & Configuring spt 3. HP/UX 10.x - Configuring spt 4. HP/UX 10.x - Example: Configuring spt 2. HP 800 - Software Management Using MTI "INSTALL" 1. HP 800 - Load Software from Local Tape Drive 2. HP 800 - Load Software from Remote Tape Drive 3. HP 800 - Load Software from File Retrieved over the Internet 4. HP 800 - Install Software 5. HP 800 - Check Software 6. HP 800 - Update Software 7. HP 800 - Remove Software 4. Sun Solaris 2.x(SunOS 5.x) 1. Solaris2.x - Software Management Using SVR4 "package" Utilities
http://www-personal.umich.edu/~rak/9k_manual/9000swinstall_ToC.html (1 of 3)18-Feb-08 11:28:36 AM
1. Solaris2.x - Load Software from Local Tape Drive 2. Solaris2.x - Load Software from Remote Tape Drive 3. Solaris2.x - Load Software from File Retrieved over the Internet 4. Solaris2.x - Install Software 5. Solaris2.x - Check Software 6. Solaris2.x - Update Software 7. Solaris2.x - Remove Software 5. Sun Solaris 1.x(SunOS 4.1.x) 1. Solaris1.x - Software Management Using MTI "INSTALL" 1. Solaris1.x - Load Software from Local Tape Drive 2. Solaris1.x - Load Software from Remote Tape Drive 3. Solaris1.x - Load Software from File Retrieved over the Internet 4. Solaris1.x - Install Software 5. Solaris1.x - Check Software 6. Solaris1.x - Update Software 7. Solaris1.x - Remove Software 6. SGI IRIX 1. SGI - Software Management Using SVR4 "package" Utilities 1. SGI - Load Software from Local Tape Drive 2. SGI - Load Software from Remote Tape Drive 3. SGI - Load Software from File Retrieved over the Internet 4. Checking for Existence of SVR4 "package" Utilities 5. SGI - Install Software 6. SGI - Check Software 7. SGI - Update Software 8. SGI - Remove Software 2. SGI - Software Management Using MTI "INSTALL" 1. SGI - Load Software from Local Tape Drive 2. SGI - Load Software from Remote Tape Drive 3. SGI - Load Software from File Retrieved over the Internet 4. SGI - Install Software 5. SGI - Check Software 6. SGI - Update Software 7. SGI - Remove Software 7. IBM AIX 1. IBM - Software Management Using MTI "INSTALL" 1. IBM - Load Software from Local Tape Drive 2. IBM - Load Software from Remote Tape Drive
3. IBM - Load Software from File Retrieved over the Internet 4. IBM - Install Software 5. IBM - Check Software 6. IBM - Update Software 7. IBM - Remove Software 8. DEC Digital UNIX(formerly OSF/1) 1. DEC - Software Management Using MTI "INSTALL" 1. DEC - Load Software from Local Tape Drive 2. DEC - Load Software from Remote Tape Drive 3. DEC - Load Software from File Retrieved over the Internet 4. DEC - Install Software 5. DEC - Check Software 6. DEC - Update Software 7. DEC - Remove Software
http://www-personal.umich.edu/~rak/9k_manual/9000rpc_ToC.html
1. RPC-based Utilities 1. Remote Procedure Call Definition 2. Software Components 1. RPC Server - das_svrd 1. Starting and Stopping das_svrd 2. RPC Client - das_mgr 1. Starting das_mgr 2. Interacting with das_mgr 3. Device Naming Conventions 4. Menu Items 1. Select 2. Current 3. Configure 1. Get 2. Show 3. Detail 4. New 5. Set 6. Clear 7. Save 8. Load 9. Salvage 4. Initialize 5. Check 6. Restore 7. Rebuild 8. Progress 9. Start 10. Stop 11. Hardware 1. BBT 2. Errors 3. Inventory 4. Status 5. Enable 6. Disable 7. Wide
http://www-personal.umich.edu/~rak/9k_manual/9000rpc_ToC.html (1 of 2)18-Feb-08 11:28:38 AM
http://www-personal.umich.edu/~rak/9k_manual/9000rpc_ToC.html
8. Narrow 9. Pause 10. No_Pause 11. LCD_Clear 12. Download 3. RPC Client: das_monitor 1. Starting and Stopping das_monitor 4. RPC Client: das_check 1. What happens if data is found to be inconsistent?
http://www-personal.umich.edu/~rak/9k_manual/9000rpc_ToC.html (2 of 2)18-Feb-08 11:28:38 AM
http://www-personal.umich.edu/~rak/9k_manual/9kconfig_ToC.html
1. Configuring the Array 1. About the Array's Logical Configuration 2. Rules for Setting up a New Configuration 3. New Configuration Options to Consider 1. Hot Spare 1. An Example of When a Hot Spare is Necessary 2. An Example of When a Hot Spare is Not Necessary 2. LUN Sizing 3. Write-Back Caching 4. Striping Optimization 4. Steps for Setting up a New Configuration 1. EXAMPLE CONFIGURATION: LUN 0 = 1MB, LUN 1 = Rest of Capacity 2. EXAMPLE CONFIGURATION: LUN 0 = Total Available Capacity 3. EXAMPLE CONFIGURATION: All LUNs less than 4 GB 5. Initializing LUNs
http://www-personal.umich.edu/~rak/9k_manual/9kconfig_ToC.html18-Feb-08 11:28:41 AM
http://www-personal.umich.edu/~rak/9k_manual/9kmonitr_ToC.html
1. Monitoring Array Events 1. Examining Events
http://www-personal.umich.edu/~rak/9k_manual/9kmonitr_ToC.html18-Feb-08 11:28:44 AM
http://www-personal.umich.edu/~rak/9k_manual/9kavail_ToC.html
1. Making the Storage Available 1. HP HP-UX for Series 700 Machines 1. Configuring HP-UX 9.0.4 for the New Storage 1. Setting Up LUN devices 1. Naming LUNs 2. Creating LUN Device Nodes 2. Building Filesystems on the new LUNs 2. Configuring HP-UX 10.x for the New Storage 2. HP HP-UX for Series 800 Machines 1. Interfacing with the HP-UX Logical Volume Manager 1. Storage Hierarchy 1. Configuration Illustration 2. Physical Volumes 3. Volume Groups 4. Logical Volumes 5. Filesystems 2. Configuring HP-UX 9.0.4 for the New Storage 1. Using Command Line 1. Add the New Physical Volumes 2. Assign the Physical Volume to a Volume Group 1. Using an Existing Volume Group 2. Creating a New Volume Group 3. Create a Logical Volume 4. Create a File System 5. Making the Data Accessible across a Reboot 2. Using sam 3. Configuring HP-UX 10.0 for the New Storage 3. Sun Solaris 1.x(SunOS 4.1.x) 1. Adding Host Support for Alternate LUNs 2. Labeling and Partitioning the LUNs. 3. Building Filesystems on the Partitions 4. Mounting the Filesystems 5. Making the Storage Accessible Across Reboots 4. Sun Solaris 2.x(SunOS 5.x) 1. Labeling and Partitioning the LUN. 2. Building Filesystems on the Partitions 3. Mounting the Filesystems
http://www-personal.umich.edu/~rak/9k_manual/9kavail_ToC.html (1 of 2)18-Feb-08 11:28:47 AM
http://www-personal.umich.edu/~rak/9k_manual/9kavail_ToC.html
4. Making the Storage Accessible Across Reboots 5. SGI IRIX 1. Labeling and Partitioning the LUN. 2. Building Filesystems on the Partitions 3. Mounting the Filesystems 4. Making the Storage Accessible Across Reboots 6. IBM AIX 1. Storage Hierarchy 1. Configuration Illustration 2. Physical Volumes 3. Volume Groups 4. Logical Volumes 5. Filesystems 2. Configuring the New Storage 1. Add the New Physical Volumes 2. Assign the Physical Volume to a Volume Group 3. Create a Logical Volume 4. Create a Journaled File System 7. DEC Digital UNIX(formerly OSF/1) 1. Checking for New Devices Before Booting 2. Accessing, Labeling, and Partitioning the LUN 3. Building Filesystems on the Partitions 4. Mounting the Filesystems 5. Making the Storage Accessible Across Reboots
http://www-personal.umich.edu/~rak/9k_manual/9kavail_ToC.html (2 of 2)18-Feb-08 11:28:47 AM
http://www-personal.umich.edu/~rak/9k_manual/9kreplac_ToC.html
1. Replacing Failed Components 1. Replacing a Failed Disk 2. Replacing a Power Supply 3. Replacing a Fan 4. Replacing a Controller
http://www-personal.umich.edu/~rak/9k_manual/9kreplac_ToC.html18-Feb-08 11:28:50 AM
http://www-personal.umich.edu/~rak/9k_manual/9kerror_ToC.html
1. Error Messages: Descriptions and Action Items
http://www-personal.umich.edu/~rak/9k_manual/9kerror_ToC.html18-Feb-08 11:28:54 AM
http://www-personal.umich.edu/~rak/9k_manual/MTI_tech_sup.html
MTI Technical Support Can be reached at the following toll free number: 1-800-FON-4MTI 1-800-366-4684
http://www-personal.umich.edu/~rak/9k_manual/MTI_tech_sup.html18-Feb-08 11:28:56 AM
http://www-personal.umich.edu/~rak/9k_manual/Appendix_ToC.html
1. APPENDIX A: HP Patch Installation Notes 1. HP-UX 9.0.4 - PHKL_5405 Installation Notes 2. HP-UX 10.0 - Patch PHKL_5406 Installation Notes
http://www-personal.umich.edu/~rak/9k_manual/Appendix_ToC.html18-Feb-08 11:28:59 AM
Introduction
Introduction This document outlines the installation and configuration of the MTI Series 9000 disk array subsystem. The Series 9000 disk array subsystem is a fourth-generation disk array product from MTI that combines the attributes of high-performance, high-availability and easy maintenance in an economical package.
The Series 9000 keeps system administrators notified of changes in the array status via custom developed software. Any disk failures cause an alarm message to be sent to the system console. Network administrators can even configure array messages from several different servers to appear on a central administration machine. This allows for easy integration with existing network monitoring tools. The high-performance of the Series 9000 is due to a number of features: * Fast and Wide SCSI-2 interface * Full support for tagged-command queuing * High-performance write-back cache * Sequential read-ahead capability The installation process breaks down into several major steps as follows: * Installing the array into a rack or into a deskside configuration. See the 9200 Hardware Manual, the 9300 Hardware Manual, or the 9500 Hardware Manual. * Shutting down the system and connecting the array to the proper SCSI bus. See the appropriate host system documentation.
http://www-personal.umich.edu/~rak/9k_manual/9kintro.html (1 of 2)18-Feb-08 11:29:01 AM
Introduction
* Installing the MTI Series 9000 management software. See section 2 - Software Installation. * Configure the array. See section 4 - Configuring the Array. * Integrate new storage into the system. See section 6 - Making the Storage Available. If any problems are encountered, please contact MTI technical support(see section Error! Reference source not found. - Error! Reference source not found.).
http://www-personal.umich.edu/~rak/9k_manual/9kintro.html (2 of 2)18-Feb-08 11:29:01 AM
Installation
Software Installation The Series 9000 array includes software that runs on the host system. This software, while not required for the array to function, allows administrators to manage and monitor the arrays attached to the system. This section describes how to install the software on the host system.
The Series 9000 software is distributed on 4mm and 8mm tape. In addition, the software can be retrieved via anonymous ftp from the Internet. The steps to install the software are summarized as follows: * Load the MTI9000 software package onto the host system. * Make any system preparations that are required . * Install the MTI9000 software package Since each of the following sections are host specific, skip to the relevant section based on your host type.
Option to Retrieve Software from the Internet

In an attempt to make it easy to get software updates and to emphasis our commitment to cross-platform connectivity, MTI has an anonymous ftp at the following address: ftp.npi.com Note, it is only necessary to get the software via the Internet for one of the following reasons: * Update Series 9000 software or firmware * Move a Series 9000 array to a new supported platform * The software was shipped on a media type that is not available on your machine.
http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (1 of 99)18-Feb-08 11:29:39 AM
Installation
After logging on with an `anonymous' id and using your email address for the password, change directories to find the current release of the Series 9000 Software. The following command is an example of what to type at the "ftp>" prompt. When typing the following command, consult Table 2-1 for the proper platform identifier. ftp> cd pub/mti9000/software/<platform identifier> PLATFORM DESCRIPTION FORMAT HP 9000 Series 700, 800 tar HP/UX 9.x , 10. x Silicon Graphics IRIX package IBM RS/6000 AIX 3.2.5, 4.x tar Sun SunOS 4.1.x - Solaris tar 1. x Sun SunOS 5.x - Solaris 2.x package DEC Digital UNIX tar PLATFORM IDENTIFIER hpux FILE
irix aix sunos4.1.x
tar and SVR4
solaris2.x digitalunix
SVR4
Table 2-1 Use the `ls' or `nlist' command of ftp to get a directory listing. There will be a single file in a format that is readable on your machine. Make sure that binary transfer switch is set with the `bin' command. Finally, use the `get' command to transfer the file. When installing the software from a file retrieved over the internet instead of installing from a tape or floppy drive, it is sufficient to replace the retrieved filename for any commands that call for a device name. This is one of the beauties of UNIX.
HP HP-UX for Series 700

This sections describes how to load and install the MTI9000 software package on an HP Series 700 machine.
HP 700 - Software Management Using MTI "INSTALL"

The install is a two step process. Step one is to load the software on the host system from tape or a file retrieved
Installation
over the Internet. Step two is to install the software using the MTI "INSTALL" script. The next several sections describe how to load the software from a variety of places: a local tape drive, a remote tape drive, and from the Internet. Before the software is loaded, make the destination directory with the following command(It is ok to get an error that the directory already exists.): # mkdir -p /usr/local/hpux Now skip to one of the next 3 software load sections that applies to your configuration. HP 700 - Load Software from Local Tape Drive To begin the installation, insert the 4mm or 8mm tape labeled "MTI9000" into the tape drive on the system, become root and type the following commands: # mkdir -p /usr/local # cd /usr/local # tar xf /dev/rmt/<tape device> hpux ...tar output... # cd hpux # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.2.1.4, HP 700 - Install Software. HP 700 - Load Software from Remote Tape Drive If there is no tape drive on the system, insert the tape into the proper tape drive on another system on the network and type the following command on the remote system: # tar xf /dev/rmt/<tape device> hpux - | tar cf /tmp/hpux.tar Now, use the ftp(1C) utility to send the "hpux.tar" file to the "/usr/local" directory of host system that has the array attached. Then, return to host machine and type the following commands: # cd /usr/local # tar xvf hpux.tar
Installation
... .tar output... # cd hpux # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.2.1.4, HP 700 - Install Software. HP 700 - Load Software from File Retrieved over the Internet If the software was downloaded over the Internet as a single file(<filenme>), then copy the file to the "/usr/local/ hpux" directory of the local host where the array is attached. On the host machine and type the following command: # cd /usr/local/hpux # tar xf <filename> ... tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.2.1.4, HP 700 - Install Software. HP 700 - Install Software To integrate the Series 9000 software with the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/hpux/MTI9000 During the install, you will be asked if you want to run the "DAS9000 Consistency Checker regularly". It is strongly recommended to run das_check on a regular basis. If you agree, the installation software will prompt for the following information and the results will be automatically entered in the crontab: * Daily or Weekly * The day for "daily" checks * The hour for check to be started
Installation
Usually, once a week during low usage hours is sufficient, but is can be run daily as in the example below. Note that the array can be online while the check is in progress, but it will be slower than normal, similar to the performance seen while a disk is rebuilding. See das_check(section 3.2.4, RPC Client: das_check) for more details about this process. The example below shows how a typical installation process is started and executed using the "INSTALL" script. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **HP HP-UX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files
Installation
Type 5 to QUIT - quit this utility Enter option?1 Commands in this script need to run with super-user permission in order to INSTALL the MTI 9000 software. Are you sure you want to INSTALL the MTI 9000 software(y/n)? y Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_users...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Creating required symbolic links...done Adding RPC server das_svrd to /etc/inittab...done Adding RPC client das_monitor to /etc/inittab...done Do you want to run the DAS9000 Consistency Checker regularly via a crontab job? yes or no? [yes] : yes
Installation
Run the checker (d)aily or (w)eekly? : d What time should the checker be run? Please enter the hour in 24hour clock format (0-23) : 2 warning: commands will be executed using /bin/sh ***crontab has been updated*** ######################################################### # # # Please reboot your system for changes to take effect. # # # ######################################################### HP 700 - Check Software There are two reasons that a "check" process should be run: * to find out the revision of the currently installed software * to compare the current state of the installed software against the standard installation template Please note that the check should always work immediately after the software is installed. However, if any customization is done, then the check will fail. In any case, the first difference between the standard template and the current state of the installation is displayed if there are any differences. To check the state of the Series 9000 software, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/hpux/MTI9000 Below is an example of what should be displayed during a "check" process: # ./INSTALL ----------------------------------------------------------------------------MTI
Installation
Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **HP HP-UX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?3 The MTI 9000 software is installed correctly. The current revision is: 2.0.beta HP 700 - Update Software If it becomes necessary to update the release of the software without disrupting any configuration files(i.e. scheduled crontab jobs, authorized user lists), then run the "update" process from the INSTALL script. The
Installation
"update" process only replaces binaries and man pages. To update the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/hpux/MTI9000 # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **HP HP-UX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files
Installation
Type 5 to QUIT - quit this utility Enter option?4 Commands in this script need to run with super-user permission in order to UPDATE the MTI 9000 software. Are you sure you want to UPDATE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Starting RPC server das_svrd...done Starting RPC client das_monitor...done HP 700 - Remove Software To remove the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command:
Installation
# cd /usr/local/hpux/MTI9000 Remove the software using option 2 of the INSTALL script. An example is given below. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **HP HP-UX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility
Installation
Enter option?2 Commands in this script need to run with super-user permission in order to REMOVE the MTI 9000 software. Are you sure you want to REMOVE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Removing software......done Removing symbolic links...done Removing RPC server das_svrd from /etc/inittab... done Removing RPC client das_monitor from /etc/inittab...done Removing disktab entry from /etc/disktab...done Removing crontab job for das_check...done
HP HP-UX for Series 800

This sections describes how to load and install the MTI9000 software package on an HP Series 800 machine.
HP 800 - Prepare HP-UX for Series 9000 Software/a>

The software installation process will vary depending the hardware configuration and the operating system revision. For example, all HP 800 class servers running HP/UX 9.0.4 require that an alternate HP device driver, spt, be configured. This is shown graphically in Figure 1. However, servers running 10.x don't need spt if the array is attached to a SCSI host adapter that supports the sdisk device driver. This is shown graphically in Figure 2. In every case, the installation of the MTI suite of management software will follow any system preparation such as installing required patches and configuring spt. To make the proper system preparations, HP/UX 9.0.4 users should proceed directly to section 2.3.1.1, HP 800 HP-UX 9.0.4 - Installing PHKL_5405 & Configuring the spt Device Driver. To make the proper system preparations, HP/UX 10.x users should proceed directly to section 2.3.1.2, HP 800 HP/UX 10.x - Installing PHKL_5406 & Configuring the spt Device Driver.
Installation
HP 800 - HP-UX 9.0.4 - Installing PHKL_5405 & Configuring the spt Device Driver This section describes the system preparation required for machines running HP/UX 9.0.4. The default top level SCSI device driver is called disc3. However, it does not have the capability of handling passthrough type requests used by Series 9000 management software. As a result of this inability, HP has developed a driver known as spt. Patch PHKL_5405 contains spt. This device driver is capable of handling passthrough type requests, but is unfortunately not capable of handling read or write requests. Therefore, the system preparation described in this section is the series of steps taken to configure the spt device driver. After the system preparation is completed as described in this section and the Series 9000 software is installed(see section 2.3.2 - HP 800 - Software Management Using MTI "INSTALL",), the unit will be configured(see section 4 - Configuring the Array)
HP/UX 9.0.4 - Obtaining the patch from HP
The HP patch can be retrieved from a variety of sources. * HP support Line via modem. You will be given a login phone number with your support contract. See your support contract for more details. * HP Support Line is available of the Internet to all customers who meet the NSF Acceptable Use Policy. The HP Support Line machine name is support.mayfield.hp.com, and the IP address is 192.6.148.19. You will need an `ftp handle' to download patches from this machine using ftp. This information can be obtained by calling 1-800-6333600. * The HP Support Line World Wide Web service home page is located at URL(patches can be downloaded without worrying about passwords): http://support.mayfield.hp.com * The Hewlett-Packard World Wide Web home page(Access HP) is located at URL: http://www.hp.com
HP/UX 9.0.4 - Hints to Installing PHKL_5405 & Configuring spt
The HP man page that details how to install the patch and configure the spt device driver is scsi_pt(7). The installation portion of this man page is listed in section 2.3.1.1.1.3, HP/UX 9.0.4 - Configuring spt , for your convenience. This man page should be followed to install the patch and to add the necessary modifications to your kernel. The following hints have been added by the MTI Open Systems Engineering Group to clarify HP's instructions. It is highly recommended that the you read the hint section carefully so that common pitfalls can be avoided. * First, a detailed explanation of the spt mechanism is in order. A SCSI pass-through mechanism is the name for a scheme in which raw SCSI commands can be sent through the device driver to a SCSI device. Normally, a device
Installation
driver responds to read or write requests from a mounted file system. In this case, it is up to the device driver to generate a SCSI read or write command. A SCSI pass-through mechanism works differently. The SCSI command is generated at the application layer and sent through the device driver in a generic wrapper directly to the device. The major thrust behind this technology is to take the intelligence out the kernel(driver) and putting it in the application which is more portable across platforms. * The spt device driver does NOT support read or write requests but it does support the SCSI pass-through mechanism. The disk3 device driver does support read and write requests, but it does NOT support the SCSI passthrough mechanism. * A device can only have a single device driver mapped to it. Therefore, the array will be split up into 2 sections. Each section will be accessed via the same SCSI target address, but each section will have a unique SCSI LUN (logical unit number). The first section will be 1MB in size and will be accessible via SCSI LUN 0. The second section will be the rest of the available space and will be accessible via SCSI LUN 1. * Each SCSI target/LUN combination looks like a separate disk drive to the HP host and will be assigned an HP LU. Don't confuse the HP LU's with the SCSI LUN's. Below in Figure 2-1 is an example of what an "ioscan -f" should look like after the patch has been installed and the system has been configured. Note that LUN's other than 0 will look like standard disk drives to the HP system and will use the default device driver, disc3, to transmit data to and from the array.
Figure 2-1 * During the installation of the spt driver, you will have to edit the "io statement". This is when you have to select which device should attach the spt driver instead of the default disk3 driver. The "io statement" should attach to LUN 0 of the array. After the array is configured in section 3, the disk3 driver will automatically attach to LUN 1 of the array. This is the LUN where all of the data will be stored. * Figure 2-2 below shows an example "io statement" that was created to give the results in the ioscan above:
Installation
Figure 2-2 In the above example, the address of the controller is 52. The SCSI ID of the array is 3. The lu number never changes from 0 unless several arrays are installed on a single machine. If this is the case, the lu will increment for each additional entry in the io statement.
HP/UX 9.0.4 - Configuring spt
While keeping in mind the hints from the MTI Open Systems Engineering Staff of the previous section, follow the below instructions from the HP scsi_pt(7) man page. It is listed below for your convenience. User input is in bold, and additional notes from MTI are in bold italics.. INSTALLATION AND CONFIGURATION The SCSI pass-through file sets are installed on the system via the Update process. After Update completes, the following installation directions need to be completed to successfully use the SCSI passthrough driver. Make a backup copy of the original /etc/master file. $ cp /etc/master /etc/master.9_04 Add the lines from the file /etc/contrib/bin/master.diff to the /etc/master file where the other drivers are defined. NOTE: The insertion point should be immediately before any of the following line: "module scsi3("
Installation
The order is important. For spt to work with lower level device drivers that it has to communicate with, it must be listed before them. Also, add the library "libspt.a" to the loadorder statement in the same file. NOTE: Add libspt.a to the beginning of the loadorder statement. The loadorder statement will look something like this: loadorder libspt.a libnetware.a libuipc.a libnipc.a ... Make a backup copy of the kernel gen file in /etc/conf/gen (typically named /etc/conf/gen/S800 ). $ cp /etc/conf/gen/S800 /etc/conf/gen/S800.nospt Edit the gen file(/etc/conf/gen/S800), adding the include statement for the SCSI passthrough driver (spt). include spt; NOTE: The insertion point should be immediately after all of the other include statements in this file. They are normally at the very beginning of the file. Add an "io statement". The io statement is needed to specify which devices will be used with the SCSI pass-through driver. The io statement is used to override default mappings from drivers to hardware components or to include drivers that do not support autoconfiguration. (Use ioscan(1M) to get hardware path information for hardware connected to your system.)
Installation
For example, to create an "io statement" that maps the spt driver to the devices at hardware paths 56/24.2.0. Modify a typical io statement such as: ... io { } ... To the following for these addresses: ... io { bus_converter address 56 { scsi1 address 24 { target address 2 { spt lu 0 address 0; } } } } ... NOTE: See section 2.3.1.1.1.2, HP/UX 9.0.4 - Hints to Installing PHKL_5405 & Configuring spt, for another example of how to convert a hardware address to an
Installation
io statement structure. Specifically, see Figure 2-2. "bus_converter" is the bus converter at address 56. "scsi1" is the NIO SCSI device driver, 24 is the NIO SCSI card ID. "target address 2" indicates SCSI ID 2. In the line "spt lu 0 address 0", "address 0" indicates SCSI LUN 0. The required LU value for the "spt lu" entry: - is driver dependent - must be unique and in the range of 0 to 0xff inclusive - can be arbitrarily assigned, it does not have to be in sequence - will be overridden by autoconfig and should not be used to create the device special file for this device NOTE: If your system does not have a bus converter, do not use the "bus_converter" statement and associated curly braces. Run uxgen to build the new kernel. $ /etc/uxgen S800 Make a backup copy of the system's current kernel, and move the new kernel into place. $ mv /hp-ux /hp-ux.nospt $ mv ../S800/hp-ux /hp-ux Reboot the system. $ /etc/reboot When the system reboots, run the ioscan command to verify that the system configuration is what you expect, i.e. that the spt driver is tied to the appropriate hardware, and that S/W Status is ok.
Installation
$ ioscan -fk -Cspt Make device special files for the pass-through devices. The character major number is 105, and the minor number format is 0x00LU00, where LU is the Logical Unit assigned to the device obtained from the output of the ioscan command above (see ioscan(1M)). NOTE: Do not use the LU value from the 'io statement' in the gen file as it could have changed during autoconfiguration. This example makes the device special file for the spt mapped device at LU 1. $ mknod /dev/rdrv1 c 105 0x000100 NOTE: It is common to match the suffix of the /dev/rdrv device with the HP LU number. For example, use /dev/rdrv0 for LU 0 and /dev/rdrv1 for LU 1. NOTE: Follow the steps outlined in section 2.3.1.1.1.4, HP/UX 9.0.4 - Recommended Steps After Installing spt.
HP/UX 9.0.4 - Recommended Steps After Installing spt
Even if the Series 9000 software works, standard "ioscan -f" commands will report a "Hardware Mismatch" for the device that has the spt device driver attached. This can be annoying. The rmsf(1m) utility can be used to drop the binding of the disc3 device driver completely from LUN 0. It is used in the following way: rmsf -k -d disc3 -H <hardware address> Subsequent ioscan(1m) commands will reveal the fact that the spt device driver is attached to LUN 0. Using the example from the previous section that had an array connected to hardware address 52.3.0, the following command would be executed: rmsf -k -d disc3 -H 52.3.0
Installation
HP 800 - HP/UX 10.x - Installing PHKL_5406 & Configuring the spt Device Driver The purpose of this section is to determine if it is necessary to configure device drivers and/or install any required patches. First, determine which device driver is attaching to the array by default. If the default device driver that attaches to the array is disc3, then the spt device driver is needed. Furthermore, patch PHKL_5406 is required to fix bugs in the spt device driver. If the sdisk device driver attaches to the array, then proceed directly to section 2.3.2 - HP 800 - Software Management Using MTI "INSTALL". The driver that the array is attached to can be determined by examining the ioscan(1m) output. Here is an example of the ioscan(1m) output when the array is attached to the HSC bus SCSI host adapter, which is used by the sdisk device driver:
Figure 2-3 Here is an example of the ioscan(1m) output when the disc3 device driver is attached to the array via a HP-PB bus SCSI host adapter:
Figure 2-4 Please note that if you are running HP/UX 10.01 or later, the patch for the spt device driver has been incorporated into core OS. If you are unsure what version of the operating system you are running, use the "uname -a" command at your shell prompt.
HP/UX 10.x - Obtaining the patch from HP
If your system is running HP/UX 10.01 or later, then this section can be skipped because the patch has been incorporated into the core OS. If you are unsure what version of the operating system you are running, use the "uname -a" command at your shell prompt. The HP patch can be retrieved from a variety of sources. * HP Support Line via modem. You will be given a login phone number with your support contract. See your support contract for more details.
Installation
* HP Support Line is available of the Internet to all customers who meet the NSF Acceptable Use Policy. The HP Support Line machine name is support.mayfield.hp.com, and the IP address is 192.6.148.19. You will need an `ftp handle' to download patches from this machine using ftp. This information can be obtained by calling 1-800-6333600. * The HP Support Line World Wide Web service home page is located at URL(patches can be downloaded without worrying about passwords): http://support.mayfield.hp.com * The Hewlett-Packard World Wide Web home page(Access HP) is located at URL: http://www.hp.com
HP/UX 10.x - Hints to Installing PHKL_5406 & Configuring spt
The HP man page that details how to install the patch and configure the spt device driver is scsi_pt(7). The installation portion of this man page is listed in section 2.3.1.2.1.3, HP/UX 10.x - Configuring spt, for your convenience. This man page should be followed to install the patch and to add the necessary modifications to your kernel. The following hints have been added by the MTI Open Systems Engineering Group to clarify HP's instructions. It is highly recommended that the you read the hint section carefully so that common pitfalls can be avoided. * First, a detailed explanation of the spt mechanism is in order. A SCSI pass-through mechanism is the name for a scheme in which raw SCSI commands can be sent through the device driver to a SCSI device. Normally, a device driver responds to read or write requests from a mounted file system. In this case, it is up to the device driver to generate a SCSI read or write command. A SCSI pass-through mechanism works differently. The SCSI command is generated at the application layer and sent through the device driver in a generic wrapper and sent directly to the device. The major thrust behind this technology is to take the intelligence out the kernel(driver) and putting it in the application which is more portable across platforms. * The spt device driver does NOT support read or write requests but it does support the SCSI pass-through mechanism. The disk3 device driver does support read and write requests, but it does NOT support the SCSI passthrough mechanism. * A device can only have a single device driver mapped to it. Therefore, the array will be split up into 2 sections. Each section will be accessed via the same SCSI target address, but each section will have a unique SCSI LUN (logical unit number). The first section will be 1MB in size and will be accessible via SCSI LUN 0. The second section will be the rest of the available space and will be accessible via SCSI LUN 1. * Each SCSI target/LUN combination looks like a separate disk drive to the HP host and will be assigned an address. Here is an example of an "ioscan -f" that we are looking for.
Installation
Figure 2-5
HP/UX 10.x - Configuring spt
While keeping in mind the hints from the MTI Open Systems Engineering Staff of the previous section, follow the below instructions from the HP scsi_pt(7) man page. It is listed below for your convenience. User input is in bold format, and addition hints from MTI are in bold italic format. INSTALLATION AND CONFIGURATION The SCSI pass-through file set comes with the core system and will exist after an install or an update. The files in this set (and their proper destinations) are: Filename Protections Full path ======== =========== ========= libspt.a -r--r--r-- /usr/conf/lib/libspt.a scsi_io.c -r--r--r-- /usr/contrib/src/scsi_io.c scsi_pt.7 -r--r--r-- /usr/share/man/man7.Z/scsi_pt.7 spt -r--r--r-- /usr/conf/master.d/spt The following configuration steps need to be completed to successfully use the NIO SCSI pass-through driver. This driver does not autoconfigure. Go to the build area:
Installation
$ cd /stand/build Create a system file from your existing kernel: $ /usr/lbin/sysadm/system_prep -s system Get information about peripherals attached to your system: $ ioscan -f Check if the SCSI pass-through driver is already configured into your current kernel: $ grep spt system If no "spt" line was printed, add a line to the "SCSI drivers" area of the system file: spt A driver statement is needed to override the standard driver which gets autoconfigured for any device. One statement is required for each desired NIO SCSI pass-through device (be it a SCSI target, or a SCSI lun). Append the driver line(s) to the system file: $ cat >> system driver <path> spt ^D # control "D" to exit the cat command <path> = complete hardware path of desired device (from ioscan cmd) Create the conf.c and config.mk files: $ /usr/sbin/config -s system Build a new kernel:
Installation
$ make -f config.mk Verify that the pass-through driver has been built into the new kernel. (A line giving the revision information should be printed): $ what ./vmunix_test | grep scsi_pt Save the old system file: $ mv /stand/system /stand/system.prev Move the new system file to be the current one: $ mv ./system /stand/system Save the old kernel: $ mv /stand/vmunix /stand/vmunix.prev Move the new kernel to be the current one: $ mv ./vmunix_test /stand/vmunix Boot the system from the new kernel: $ exec reboot ONCE THE SYSTEM REBOOTS: Verify the peripheral configuration: $ ioscan -f Determine the major number for the SCSI pass-through driver: $ lsdev -d spt Create the special device file to access the scsi_pt peripheral (refer to the example in the TROUBLESHOOTING section): $ mknod /dev/<devfilename> c <major #> <minor #> <devfilename> = name of the special device file
Installation
NOTE: The typical format for the <devfilename> file, is as follows: /dev/rdrv0 - for the 1st spt device /dev/rdrv1 - for the 2nd spt device /dev/rdrvn - for the n'th spt device <major #> = character major number (from lsdev cmd) <minor #> = minor number in the format 0xIITL00 II = 2 digit card instance number (from ioscan cmd; proper "ext_bus" entry) T = Target ID number (SCSI ID) L = Lun number (SCSI LUN) 00 = Reserved fields, must be zero All ready for use , try the sample program : Compile the sample program: $ cc /usr/contrib/src/scsi_io.c Execute the sample program: $ ./a.out /dev/<devfilename> The sample program should have returned the inquiry data of the target device. If this did not happen, refer to the TROUBLESHOOTING section. TROUBLESHOOTING If the NIO SCSI pass-through driver is not working:
Installation
o Verify the proper configuration of the SCSI pass-through driver into the kernel. o Verify that the hardware is set up properly. + Check that the device is connected, and that its SCSI Bus address is set properly. + Check the reference manual for the device to verify that it is configured properly. + Check that the SCSI Bus is properly terminated. + Verify that the device is operational using some other driver if possible. If a hardware problem is suspected, the SCSI pass-through driver must be unconfigured for that device and the HP specific device driver must be configured before any diagnostic software can be run. o Verify the special device file. + Execute "lsdev -d spt" to find the major number for the SCSI pass-through driver. For example, "lsdev -d spt" might show: Character Block Driver Class 136 -1 spt spt + Run ioscan -kf to find the card instance number, target SCSI ID and SCSI LUN for the desired device. For example "ioscan -kf" might show: Class I H/W Path Driver S/W State H/W Type Description ==============================================================
Installation
bc 0 root CLAIMED BUS_NEXUS ext_bus 2 8 scsi1 CLAIMED INTERFACE HP 28655A - SC target 0 8.3 target CLAIMED DEVICE spt 0 8.3.0 spt CLAIMED DEVICE HP C1718T target 1 8.4 target CLAIMED DEVICE spt 1 8.4.0 spt CLAIMED DEVICE HP C1716T ... In this example there are two desired devices: Device #1 Device #2 ========= ========= card instance number = 2 card instance number = 2 target SCSI ID = 3 target SCSI ID = 4 SCSI LUN = 0 SCSI LUN = 0 + Verify that these are the same values used in the special device files. For example, "ll /dev/c2t*d0" might show: crw-rw-rw- 1 root sys 136 0x023000 Dec 14 15:10 c2t3d0 crw-rw-rw- 1 root sys 136 0x024000 Dec 14 15:10 c2t4d0
HP/UX 10.x - Example: Configuring spt
The following is an example of the steps taken to configure the spt device driver as described by the scsi_pt(7) man page. Use this as a template to be used in conjunction with the installation procedures provided in section 2.3.1.2.1.3, HP/UX 10.x - Configuring spt. ... This is an example session ... # cd /stand/build # /usr/lbin/sysadm/system_prep -s system
Installation
# ioscan -f Class I H/W Path Driver S/W State H/W Type Description =================================================================== bc 0 root CLAIMED BUS_NEXUS ext_bus 0 16 scsi3 CLAIMED INTERFACE HP 28696A - Fast/Wide SCS I Interface target 4 16.4 target CLAIMED DEVICE disk 5 16.4.0 disc3 CLAIMED DEVICE MTI DAS9000 ext_bus 1 52 scsi1 CLAIMED INTERFACE HP 28655A - SCSI Interface target 0 52.1 target CLAIMED DEVICE disk 0 52.1.0 disc3 CLAIMED DEVICE MAXTOR MXT-1240S target 1 52.2 target CLAIMED DEVICE disk 1 52.2.0 disc3 CLAIMED DEVICE TOSHIBA CD-ROM XM-3401TA target 3 52.4 target CLAIMED DEVICE tape 1 52.4.0 tape2 CLAIMED DEVICE EXABYTE EXB-85058SBANXB5 target 2 52.6 target CLAIMED DEVICE disk 2 52.6.0 disc3 CLAIMED DEVICE HP C2247M1 lanmux 0 56 lanmux0 CLAIMED INTERFACE LAN/Console tty 0 56.0 mux4 CLAIMED INTERFACE lan 0 56.1 lan3 CLAIMED INTERFACE lantty 0 56.2 lantty0 CLAIMED INTERFACE processor 0 62 processor CLAIMED PROCESSOR Processor
Installation
memory 0 63 memory CLAIMED MEMORY Memory # grep spt system # cat >> system driver 16.4.0 spt # grep spt system driver 16.4.0 spt # /usr/sbin/config -s system # make -f config.mk Compiling conf.c... Loading the kernel... # what ./vmunix_test | grep scsi_pt scsi_pt.c Revision: 10.00 $Date: 95/03/29 11:38:13 $ # mv /stand/system /stand/system.prev # cp ./system /stand/system # mv /stand/vmunix /stand/vmunix.prev # cp ./vmunix_test /stand/vmunix # exec reboot After the reboot... # ioscan -f Class I H/W Path Driver S/W State H/W Type Description =================================================================== bc 0 root CLAIMED BUS_NEXUS ext_bus 0 16 scsi3 CLAIMED INTERFACE HP 28696A - Fast/Wide SCS
Installation
I Interface target 4 16.4 target CLAIMED DEVICE spt 0 16.4.0 spt CLAIMED DEVICE MTI DAS9000 ext_bus 1 52 scsi1 CLAIMED INTERFACE HP 28655A - SCSI Interfac e target 0 52.1 target CLAIMED DEVICE disk 0 52.1.0 disc3 CLAIMED DEVICE MAXTOR MXT-1240S target 1 52.2 target CLAIMED disk 1 52.2.0 disc3 CLAIMED DEVICE TOSHIBA CD-ROM XM-3401TA target 3 52.4 target CLAIMED DEVICE tape 1 52.4.0 tape2 CLAIMED DEVICE EXABYTE EXB-85058SBANXB5 target 2 52.6 target CLAIMED DEVICE disk 2 52.6.0 disc3 CLAIMED DEVICE HP C2247M1 lanmux 0 56 lanmux0 CLAIMED INTERFACE LAN/Console tty 0 56.0 mux4 CLAIMED INTERFACE lan 0 56.1 lan3 CLAIMED INTERFACE lantty 0 56.2 lantty0 CLAIMED INTERFACE processor 0 62 processor CLAIMED PROCESSOR Processor memory 0 63 memory CLAIMED MEMORY Memory # lsdev -d spt Character Block Driver Class 137 -1 spt spt
Installation
# mknod /dev/rdrv1 c 137 0x004000 # cc /usr/contrib/src/scsi_io.c # ./a.out /dev/rdrv1 The thing claims to be: MTI DAS9000 0141"
HP 800 - Software Management Using MTI "INSTALL"

The install is a two step process. Step one is to load the software on the host system from tape or a file retrieved over the Internet. Step two is to install the software using the MTI "INSTALL" script. The next several sections describe how to load the software from a variety of places: a local tape drive, a remote tape drive, and from the Internet. Before the software is loaded, make the destination directory with the following command(It is ok to get an error that the directory already exists.): # mkdir -p /usr/local/hpux Now skip to one of the next 3 software load sections that applies to your configuration. HP 800 - Load Software from Local Tape Drive To begin the installation, insert the 4mm or 8mm tape labeled "MTI9000" into the tape drive on the system, become root and type the following commands: # mkdir -p /usr/local # cd /usr/local # tar xf /dev/rmt/<tape device> hpux ...tar output... # cd hpux # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.3.2.4 - HP 800 Install Software. HP 800 - Load Software from Remote Tape Drive
Installation
If there is no tape drive on the system, insert the tape into the proper tape drive on another system on the network and type the following command on the remote system: # tar xf /dev/rmt/<tape device> hpux - | tar cf /tmp/hpux.tar Now, use the ftp(1C) utility to send the "hpux.tar" file to the "/usr/local" directory of host system that has the array attached. Then, return to host machine and type the following commands: # cd /usr/local # tar xvf hpux.tar ... .tar output... # cd hpux # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.3.2.4 - HP 800 Install Software. HP 800 - Load Software from File Retrieved over the Internet If the software was downloaded over the Internet as a single file(<filenme>), then copy the file to the "/usr/local/ hpux" directory of the local host where the array is attached. On the host machine and type the following command: # cd /usr/local/hpux # tar xf <filename> ... tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.3.2.4 - HP 800 Install Software. HP 800 - Install Software To integrate the Series 9000 software with the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/hpux/MTI9000
Installation
During the install, you will be asked if you want to run the "DAS9000 Consistency Checker regularly". It is strongly recommended to run das_check on a regular basis. If you agree, the installation software will prompt for the following information and the results will be automatically entered in the crontab: * Daily or Weekly * The day for "daily" checks * The hour for check to be started Usually, once a week during low usage hours is sufficient, but is can be run daily as in the example below. Note that the array can be online while the check is in progress, but it will be slower than normal, similar to the performance seen while a disk is rebuilding. See das_check(section 3.2.4, RPC Client: das_check) for more details about this process. The example below shows how a typical installation process is started and executed using the "INSTALL" script. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta
Installation
**HP HP-UX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?1 Commands in this script need to run with super-user permission in order to INSTALL the MTI 9000 software. Are you sure you want to INSTALL the MTI 9000 software(y/n)? y Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_users...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done
Installation
Creating required symbolic links...done Adding RPC server das_svrd to /etc/inittab...done Adding RPC client das_monitor to /etc/inittab...done Do you want to run the DAS9000 Consistency Checker regularly via a crontab job? yes or no? [yes] : yes Run the checker (d)aily or (w)eekly? : d What time should the checker be run? Please enter the hour in 24hour clock format (0-23) : 2 warning: commands will be executed using /bin/sh ***crontab has been updated*** ######################################################### # # # Please reboot your system for changes to take effect. # # # ######################################################### HP 800 - Check Software There are two reasons that a "check" process should be run: * to find out the revision of the currently installed software * to compare the current state of the installed software against the standard installation template Please note that the check should always work immediately after the software is installed. However, if any customization is done, then the check will fail. In any case, the first difference between the standard template and the current state of the installation is displayed if there are any differences. To check the state of the Series 9000 software, it is necessary to run the "INSTALL" script from within the
Installation
MTI9000 directory. To get into this directory type the following command: # cd /usr/local/hpux/MTI9000 Below is an example of what should be displayed during a "check" process: # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **HP HP-UX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility
Installation
Enter option?3 The MTI 9000 software is installed correctly. The current revision is: 2.0.beta HP 800 - Update Software If it becomes necessary to update the release of the software without disrupting any configuration files(i.e. scheduled crontab jobs, authorized user lists), then run the "update" process from the INSTALL script. The "update" process only replaces binaries and man pages. To update the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/hpux/MTI9000 # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta
Installation
**HP HP-UX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?4 Commands in this script need to run with super-user permission in order to UPDATE the MTI 9000 software. Are you sure you want to UPDATE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done
Installation
Installing das_monitor.l.fmtd...done Starting RPC server das_svrd...done Starting RPC client das_monitor...done HP 800 - Remove Software To remove the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/hpux/MTI9000 Remove the software using option 2 of the INSTALL script. An example is given below. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **HP HP-UX
Installation
Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?2 Commands in this script need to run with super-user permission in order to REMOVE the MTI 9000 software. Are you sure you want to REMOVE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Removing software......done Removing symbolic links...done Removing RPC server das_svrd from /etc/inittab... done Removing RPC client das_monitor from /etc/inittab...done Removing disktab entry from /etc/disktab...done Removing crontab job for das_check...done
Sun Solaris 2.x(SunOS 5.x)

This sections describes how to load and install the MTI9000 software package on an Sun Solaris 2.x machine.
Solaris2.x - Software Management Using SVR4 "package" Utilities

The install is a two step process. Step one is to load the software on the host system from tape or a file retrieved over the Internet. Step two is to install the software using SVR4 "package" utilities. These utilities have the same look and feel across many SVR4-based UNIX operating systems including Sun Solaris 2 and SGI IRIX
Installation
The next several sections describe how to load the software from a variety of places: a local tape drive, a remote tape drive, and from the Internet. Before the software is loaded, make the destination directory with the following command(It is ok to get an error that the directory already exists.): # mkdir -p /usr/local/solaris2.x Now skip to one of the next 3 software load sections that applies to your configuration. Solaris2.x - Load Software from Local Tape Drive To begin the installation, insert the 4mm or 8mm tape labeled "MTI9000" into the tape drive on the system, become root and type the following commands: # cd /usr/local # tar xf /dev/<tape device> solaris2.x ...tar output... # cd solaris2.x Now proceed to section 2.4.1.4 - Solaris2.x - Install Software. Solaris2.x - Load Software from Remote Tape Drive If there is no tape drive on the system, insert the tape into the proper tape drive on another system on the network and type the following command on the remote system(Note: fit the entire command below on a single line): # tar xf /dev/rmt/<tape device> solaris2.x - | tar cf /tmp/solaris2.x.pkg Now, use the ftp(1C) utility to send the "solaris2.x.pkg" file to the "/usr/local/solaris2.x" directory of host system that has the array attached. Now proceed to section 2.4.1.4 - Solaris2.x - Install Software. Solaris2.x - Load Software from File Retrieved over the Internet If the software was downloaded over the Internet as a single file(<filenme>), then copy the file to the "/usr/local/ solaris2.x" directory of the local host where the array is attached. Now proceed to section 2.4.1.4 - Solaris2.x - Install Software. Solaris2.x - Install Software To integrate the Series 9000 software with the operating system, it is necessary to run the pkgadd(1m) utility on
Installation
the MTI9000 package that was just loaded on the system. To get into the proper directory, type the following command: # cd /usr/local/solaris2.x During the install, you will be asked if you want to run the "DAS9000 Consistency Checker regularly". It is strongly recommended to run das_check on a regular basis. If you agree, the installation software will prompt for the following information and the results will be automatically entered in the crontab: * Daily or Weekly * The day for "daily" checks * The hour for check to be started Usually, once a week during low usage hours is sufficient, but is can be run daily as in the example below. Note that the array can be online while the check is in progress, but it will be slower than normal, similar to the performance seen while a disk is rebuilding. See das_check(section 3.2.4, RPC Client: das_check) for more details about this process. The example below shows how a typical installation process is started and executed using pkgadd(1m). Note: The entire pathname must be typed in after the "-d" flag. # pkgadd -d /usr/local/solaris2.x/MTI9000.pkg.<release> The following packages are available: 1 MTI9000 MTI Disk Array Subsystem Series 9000 (sparc) 2.0.beta Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: Processing package instance <MTI9000> from </usr/local/solaris2.x/MTI9000. pkg.2.0.beta> MTI Disk Array Subsystem Series 9000 (sparc) 2.0.beta ----------------------------------------------------------------------------MTI
Installation
Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------Do you want to run the DAS9000 Consistency Checker regularly via a crontab job? yes or no? [yes] : yes Run the checker (d)aily or (w)eekly? : d What time should the checker be run? Please enter the hour in 24hour clock format (0-23) : 2 ## Processing package information. ## Processing system information. 7 package pathnames are already properly installed. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs.
Installation
This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of this package [y,n,?] y Installing MTI Disk Array Subsystem Series 9000 as <MTI9000> ## Installing part 1 of 1. /etc/init.d/das_mon /etc/init.d/das_svr /etc/rc0.d/K76das_mon <symbolic link> /etc/rc0.d/K77das_svr <symbolic link> /etc/rc2.d/S76das_svr <symbolic link> /etc/rc2.d/S77das_mon <symbolic link> /usr/man/catl/das_check.l.fmtd /usr/man/catl/das_mgr.l.fmtd /usr/man/catl/das_monitor.l.fmtd /usr/man/catl/das_svrd.l.fmtd /usr/sbin/das_check /usr/sbin/das_mgr /usr/sbin/das_monitor /usr/sbin/das_svrd /usr/sbin/das_users [ verifying class <none> ] ## Executing postinstall script. Installing cron job for das_check...done
Installation
Installation complete Before starting the RPC server (das_svrd), you should check the list of allowed users in the file /usr/sbin/das_users. The default file grants server access only to root on the local machine. See the das_svrd man page for details of the file's format. To start the server, type "/etc/init.d/das_svr start"; To start the status monitor, type "/etc/init.d/das_mon start". Both programs will be started automatically during future system boots. Installation of <MTI9000> was successful. Solaris2.x - Check Software The pkgchk(1m) command may be used to make sure that all of the files and symbolic links are as stated in the default installation template. Please note that the check should always work immediately after the software is installed. However, if any customization is done, then the check will fail. In any case, the any differences between the standard template and the current state of the installation are displayed if there are any differences. To check the state of the Series 9000 software, follow this example: # /usr/sbin/pkgchk -v MTI9000 /etc /etc/init.d /etc/init.d/das_mon /etc/init.d/das_svr /etc/rc0.d /etc/rc0.d/K76das_mon /etc/rc0.d/K77das_svr /etc/rc2.d
Installation
/etc/rc2.d/S76das_svr /etc/rc2.d/S77das_mon /usr /usr/man /usr/man/catl /usr/man/catl/das_check.l.fmtd /usr/man/catl/das_mgr.l.fmtd /usr/man/catl/das_monitor.l.fmtd /usr/man/catl/das_svrd.l.fmtd /usr/sbin /usr/sbin/das_check /usr/sbin/das_mgr /usr/sbin/das_monitor /usr/sbin/das_svrd /usr/sbin/das_users # To check the revision of the current software or to check on general information about the MTI9000 package, follow the next example: # /usr/sbin/pkginfo -l MTI9000 PKGINST: MTI9000 NAME: MTI Disk Array Subsystem Series 9000 CATEGORY: application ARCH: sparc
Installation
VERSION: 2.0.beta VENDOR: MTI DESC: This package contains a suite of management software for a disk array. PSTAMP: 01/16/96_17:27:29 INSTDATE: Jan 18 1996 04:26 HOTLINE: MTI 1-708-325-4151 STATUS: completely installed FILES: 23 installed pathnames 7 shared pathnames 8 directories 7 executables 630 blocks used (approx) Solaris2.x - Update Software At the present time, the MTI9000 package is tuned to allow for updates. Therefore, if an update is required, use pkgrm(1m) as described in the next section to remove the software and then pkgadd(1m) to add the new release. Note: It is a good idea to save off custom information before removing the package. For instance, the following information should be collected: * /usr/sbin/das_users contains the RPC server authorization list * "crontab -l | grep das_check" will output the current schedule for running das_check Solaris2.x - Remove Software If it becomes necessary to remove the MTI9000 package or to update it, then the pkgrm(1m) utility can be used to remove it. Below is an example of a MTI9000 package removal: # /usr/sbin/pkgrm MTI9000
Installation
The following package is currently installed: MTI9000 MTI Disk Array Subsystem Series 9000 (sparc) 2.0.beta Do you want to remove this package? y ## Removing installed package instance <MTI9000> This package contains scripts which will be executed with super-user permission during the process of removing this package. Do you want to continue with the removal of this package [y,n,?,q] y ## Verifying package dependencies. ## Processing package information. ## Executing preremove script. Stopping the RPC client das_monitor... Stopping the RPC server das_svrd... Removing cron job for das_check... done ## Removing pathnames in class <none> /usr/sbin/das_svrd /usr/sbin/das_monitor /usr/sbin/das_mgr /usr/sbin/das_check /usr/sbin <shared pathname not removed> /usr/man/catl/das_svrd.l.fmtd
Installation
/usr/man/catl/das_monitor.l.fmtd /usr/man/catl/das_mgr.l.fmtd /usr/man/catl/das_check.l.fmtd /usr/man/catl /usr/man <shared pathname not removed> /usr <shared pathname not removed> /etc/rc2.d/S77das_mon /etc/rc2.d/S76das_svr /etc/rc2.d <shared pathname not removed> /etc/rc0.d/K77das_svr /etc/rc0.d/K76das_mon /etc/rc0.d <shared pathname not removed> /etc/init.d/das_svr /etc/init.d/das_mon /etc/init.d <shared pathname not removed> /etc <shared pathname not removed> ## Updating system information. Removal of <MTI9000> was successful
Sun Solaris 1.x(SunOS 4.1.x)

This sections describes how to load and install the MTI9000 software package on an Sun Solaris 1.x machine.
Solaris1.x - Software Management Using MTI "INSTALL"

The install is a two step process. Step one is to load the software on the host system from tape or a file retrieved over the Internet. Step two is to install the software using the MTI "INSTALL" script.
Installation
The next several sections describe how to load the software from a variety of places: a local tape drive, a remote tape drive, and from the Internet. Before the software is loaded, make the destination directory with the following command(It is ok to get an error that the directory already exists.): # mkdir -p /usr/local/sunos4.1.x Now skip to one of the next 3 software load sections that applies to your configuration. Solaris1.x - Load Software from Local Tape Drive To begin the installation, insert the 4mm or 8mm tape labeled "MTI9000" into the tape drive on the system, become root and type the following commands: # mkdir -p /usr/local # cd /usr/local # tar xf /dev/<tape device> sunos4.1.x ...tar output... # cd sunos4.1.x # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.5.1.4 - Solaris1.x Install Software. Solaris1.x - Load Software from Remote Tape Drive If there is no tape drive on the system, insert the tape into the proper tape drive on another system on the network and type the following command on the remote system(Note: fit the entire command below on a single line): # tar xf /dev/rmt/<tape device> sunos4.1.x - | tar cf /tmp/sunos4.1.x.tar Now, use the ftp(1C) utility to send the " sunos4.1.x.tar" file to the "/usr/local" directory of host system that has the array attached. Then, return to host machine and type the following commands: # cd /usr/local # tar xvf sunos4.1.x.tar
Installation
... .tar output... # cd sunos4.1.x # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.5.1.4 - Solaris1.x Install Software. Solaris1.x - Load Software from File Retrieved over the Internet If the software was downloaded over the Internet as a single file(<filenme>), then copy the file to the "/usr/local/ sunos4.1.x" directory of the local host where the array is attached. On the host machine and type the following command: # cd /usr/local/sunos4.1.x # tar xf <filename> ... tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.5.1.4 - Solaris1.x Install Software. Solaris1.x - Install Software To integrate the Series 9000 software with the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/sunos4.1.x/MTI9000 During the install, you will be asked if you want to run the "DAS9000 Consistency Checker regularly". It is strongly recommended to run das_check on a regular basis. If you agree, the installation software will prompt for the following information and the results will be automatically entered in the crontab: * Daily or Weekly * The day for "daily" checks * The hour for check to be started Usually, once a week during low usage hours is sufficient, but is can be run daily as in the example below. Note
Installation
that the array can be online while the check is in progress, but it will be slower than normal, similar to the performance seen while a disk is rebuilding. See das_check(section 3.2.4, RPC Client: das_check) for more details about this process. The example below shows how a typical installation process is started and executed using the "INSTALL" script. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **Sun Solaris 1.x(SunOS 4.1.x) Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility
Installation
Enter option?1 Commands in this script need to run with super-user permission in order to INSTALL the MTI 9000 software. Are you sure you want to INSTALL the MTI 9000 software(y/n)? y Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_users...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Creating required symbolic links...done Adding RPC server das_svrd to /etc/rc.local...done Adding RPC client das_monitor to /etc/rc.local...done Do you want to run the DAS9000 Consistency Checker regularly via a crontab job? yes or no? [yes] : yes
Installation
Run the checker (d)aily or (w)eekly? : d What time should the checker be run? Please enter the hour in 24hour clock format (0-23) : 2 warning: commands will be executed using /bin/sh ***crontab has been updated*** ######################################################### # # # Please reboot your system for changes to take effect. # # # ######################################################### Solaris1.x - Check Software There are two reasons that a "check" process should be run: * to find out the revision of the currently installed software * to compare the current state of the installed software against the standard installation template Please note that the check should always work immediately after the software is installed. However, if any customization is done, then the check will fail. In any case, the first difference between the standard template and the current state of the installation is displayed if there are any differences. To check the state of the Series 9000 software, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/sunos4.1.x/MTI9000 Below is an example of what should be displayed during a "check" process: # ./INSTALL ----------------------------------------------------------------------------MTI
Installation
Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **Sun Solaris 1.x(SunOS 4.1.x) Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?3 The MTI 9000 software is installed correctly. The current revision is: 2.0.beta Solaris1.x - Update Software If it becomes necessary to update the release of the software without disrupting any configuration files(i.e. scheduled crontab jobs, authorized user lists), then run the "update" process from the INSTALL script. The "update" process only replaces binaries and man pages.
Installation
To update the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/sunos4.1.x/MTI9000 # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **Sun Solaris 1.x(SunOS 4.1.x) Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility
Installation
Enter option?4 Commands in this script need to run with super-user permission in order to UPDATE the MTI 9000 software. Are you sure you want to UPDATE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Starting RPC server das_svrd...done Starting RPC client das_monitor...done Solaris1.x - Remove Software To remove the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/sunos4.1.x/MTI9000
Installation
Remove the software using option 2 of the INSTALL script. An example is given below. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **Sun Solaris 1.x(SunOS 4.1.x) Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?2
Installation
Commands in this script need to run with super-user permission in order to REMOVE the MTI 9000 software. Are you sure you want to REMOVE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Removing software......done Removing symbolic links...done Removing RPC server das_svrd from /etc/rc.local... done Removing RPC client das_monitor from /etc/rc.local...done Removing crontab job for das_check...done
SGI IRIX
This sections describes how to load and install the MTI9000 software package on an SGI IRIX machine. The system administrator has two choices when it comes to software management utilities for IRIX: MTI "INSTALL" script, or SVR4 "package"utilities. While it is obvious that for standards sake, SVR4 package compliant utilities would be preferable, there are two reasons why MTI has packaged its software both ways: * The SVR4 package utilities are not installed with SGI pre-loaded operating systems. * The first time an SVR4 package is loaded on a system, it takes about 10-15 minutes to initialize the software package database. Now proceed to one of the next two sections depending on whether it preferred to use the SVR4 "package" utilities or the MTI "INSTALL" script.
SGI - Software Management Using SVR4 "package" Utilities

The install is a two step process. Step one is to load the software on the host system from tape or a file retrieved over the Internet. Step two is to install the software using SVR4 "package" utilities. These utilities have the same look and feel across many SVR4-based UNIX operating systems including Sun Solaris 2 and SGI IRIX The next several sections describe how to load the software from a variety of places: a local tape drive, a remote tape drive, and from the Internet. Before the software is loaded, make the destination directory with the following
Installation
command(It is ok to get an error that the directory already exists.): # mkdir -p /usr/local/irix Now skip to one of the next 3 software load sections that applies to your configuration. SGI - Load Software from Local Tape Drive To begin the installation, insert the 4mm or 8mm tape labeled "MTI9000" into the tape drive on the system, become root and type the following commands: NOTE: Use the "ns" or "no byte swapping" tape device. # cd /usr/local # tar xf /dev/<tape device> solaris2.x ...tar output... # cd solaris2.x Now proceed to section 2.6.1.4 - Checking for Existence of SVR4 "package" Utilities. SGI - Load Software from Remote Tape Drive If there is no tape drive on the system, insert the tape into the proper tape drive on another system on the network and type the following command on the remote system(Note: fit the entire command below on a single line): NOTE: Use the "ns" or "no byte swapping" tape device if the remote tape device is on an SGI machine. # tar xf /dev/rmt/<tape device> solaris2.x - | tar cf /tmp/solaris2.x.pkg Now, use the ftp(1C) utility to send the "solaris2.x.pkg" file to the "/usr/local/solaris2.x" directory of host system that has the array attached. Now proceed to section 2.6.1.4 - Checking for Existence of SVR4 "package" Utilities. SGI - Load Software from File Retrieved over the Internet If the software was downloaded over the Internet as a single file(<filenme>), then copy the file to the "/usr/local/ solaris2.x" directory of the local host where the array is attached. Now proceed to section 2.6.1.4 - Checking for Existence of SVR4 "package" Utilities. Checking for Existence of SVR4 "package" Utilities
Installation
There is a very simple test to see if the proper utilities are loaded. Simply type the following: # ls /usr/sbin/pkgadd /usr/sbin/pkgrm /usr/sbin/pkgadd /usr/sbin/pkgrm If the utilities are not installed, following these instructions to get them loaded. It is assumed that the user is logged in an SGI windowing environment: * Load the IRIX 5.x System CD into the cdrom drive * Goto the "Toolchest" * Goto the "System" folder * Select "System Manager" * In the "Shared Resources" box, double-click the "cdrom" * Single-click the "Customize Installation..." button * Goto the "Selected" menu * Select the "Find..." option * Type "ATT Packaging" in the "Find" box * "2 matches found" should be visible in the "Find" window * Single-click "Close" in the "Find" window * In the "Software Inventory" window, find will have positioned the selected software package on the "ATT Packaging Utility Man Pages" * Scroll up one line to find the "ATT Packaging Utility" * Single-click the "Install" box adjacent to each of these packages * Single-click the "Start" button to begin installation * When the installation is complete, the "Software Manager" will display a successful installation.
Installation
* Goto the "File" menu * Select "Quit" Now proceed to the next section to install the MTI9000 package. SGI - Install Software To integrate the Series 9000 software with the operating system, it is necessary to run the pkgadd(1m) utility on the MTI9000 package that was just loaded on the system. To get into the proper directory, type the following command: # cd /usr/local/irix During the install, you will be asked if you want to run the "DAS9000 Consistency Checker regularly". It is strongly recommended to run das_check on a regular basis. If you agree, the installation software will prompt for the following information and the results will be automatically entered in the crontab: * Daily or Weekly * The day for "daily" checks * The hour for check to be started Usually, once a week during low usage hours is sufficient, but is can be run daily as in the example below. Note that the array can be online while the check is in progress, but it will be slower than normal, similar to the performance seen while a disk is rebuilding. See das_check(section 3.2.4, RPC Client: das_check) for more details about this process. First, make the device special files needed by the MTI9000 software to access the array: % cd /dev % MAKEDEV scsi The example below shows how a typical installation process is started and executed using pkgadd(1m). Note: The entire pathname must be typed in after the "-d" flag. % /usr/sbin/pkgadd -d /usr/local/irix/MTI9000.pkg.2.0.beta The following packages are available: 1 MTI9000 MTI Disk Array Subsystem Series 9000
Installation
(mips) 2.0.beta Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: Processing package instance <MTI9000> from </usr/local/irix/MTI9000.pkg.2.0. beta > MTI Disk Array Subsystem Series 9000 (mips) 2.0.beta MTI Using </opt> as the package base directory. Do you want to run the DAS9000 Consistency Checker regularly via a crontab job? yes or no? [yes] : yes Run the checker (d)aily or (w)eekly? : d What time should the checker be run? Please enter the hour in 24hour clock format (0-23) : 2 ## Processing package information. ## Processing system information. 7 package pathnames are already properly installed. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. The following files are already installed on the system and are being used by another package: /usr/man/catl <attribute change only>
Installation
Do you want to install these conflicting files [y,n,?,q] y ## Checking for setuid/setgid programs. This package contains scripts which may have a security impact and which will be executed during the process of installing this package. Do you want to continue with the installation of this package [y,n,?] y Installing MTI Disk Array Subsystem Series 9000 as <MTI9000> ## Installing part 1 of 1. /etc/init.d/das_mon /etc/init.d/das_svr /etc/rc0.d/K76das_mon <symbolic link> /etc/rc0.d/K77das_svr <symbolic link> /etc/rc2.d/S76das_svr <symbolic link> /etc/rc2.d/S77das_mon <symbolic link> /usr/man/catl/das_check.l.fmtd /usr/man/catl/das_mgr.l.fmtd /usr/man/catl/das_monitor.l.fmtd /usr/man/catl/das_svrd.l.fmtd /usr/sbin/das_check /usr/sbin/das_mgr /usr/sbin/das_monitor /usr/sbin/das_svrd /usr/sbin/das_users [ verifying class <none> ]
Installation
## Executing postinstall script. Installing cron job for das_check...done warning: commands will be executed using /bin/sh Installation complete Before starting the RPC server (das_svrd), you should check the list of allowed users in the file /usr/sbin/das_users. The default file grants server access only to root on the local machine. See the das_svrd man page for details of the file's format. To start the server, type "/etc/init.d/das_svr start"; To start the status monitor, type "/etc/init.d/das_mon start". Both programs will be started automatically during future system boots. Installation of <MTI9000> was successful. SGI - Check Software The pkgchk(1m) command may be used to make sure that all of the files and symbolic links are as stated in the default installation template. Please note that the check should always work immediately after the software is installed. However, if any customization is done, then the check will fail. In any case, the any differences between the standard template and the current state of the installation are displayed if there are any differences. To check the state of the Series 9000 software, follow this example: % /usr/sbin/pkgchk -v MTI9000 /etc /etc/init.d /etc/init.d/das_mon /etc/init.d/das_svr /etc/rc0.d
Installation
/etc/rc0.d/K76das_mon /etc/rc0.d/K77das_svr /etc/rc2.d /etc/rc2.d/S76das_svr /etc/rc2.d/S77das_mon /usr /usr/man /usr/man/catl /usr/man/catl/das_check.l.fmtd /usr/man/catl/das_mgr.l.fmtd /usr/man/catl/das_monitor.l.fmtd /usr/man/catl/das_svrd.l.fmtd /usr/sbin /usr/sbin/das_check /usr/sbin/das_mgr /usr/sbin/das_monitor /usr/sbin/das_svrd /usr/sbin/das_users # To check the revision of the current software or to check on general information about the MTI9000 package, follow the next example: % /usr/sbin/pkginfo -l MTI9000 PKGINST: MTI9000
Installation
NAME: MTI Disk Array Subsystem Series 9000 CATEGORY: application ARCH: mips VERSION: 2.0.beta BASEDIR: /opt VENDOR: MTI DESC: This package contains a suite of management software for a disk arr ay. PSTAMP: 01/15/26_01:37:34 INSTDATE: Jan 18 2026 04:34 HOTLINE: MTI Customer Support 1-708-325-4151 STATUS: completely installed FILES: 23 installed pathnames 6 shared pathnames 8 directories 11 executables 4 setuid/setgid executables 1407 blocks used (approx) SGI - Update Software At the present time, the MTI9000 package is tuned to allow for updates. Therefore, if an update is required, use pkgrm(1m) as described in the next section to remove the software and then pkgadd(1m) to add the new release. Note: It is a good idea to save off custom information before removing the package. For instance, the following information should be collected:
Installation
* /usr/sbin/das_users contains the RPC server authorization list * "crontab -l | grep das_check" will output the current schedule for running das_check SGI - Remove Software If it becomes necessary to remove the MTI9000 package or to update it, then the pkgrm(1m) utility can be used to remove it. Below is an example of a MTI9000 package removal: % /usr/sbin/pkgrm MTI9000 The following package is currently installed: MTI9000 MTI Disk Array Subsystem Series 9000 (mips) 2.0.beta Do you want to remove this package [y,n,?,q] y ## Removing installed package instance <MTI9000> This package contains scripts which may have a security impact and which will be executed during the process of removing this package. Do you want to continue with the removal of this package [y,n,?,q] y ## Verifying package dependencies. ## Processing package information. ## Executing preremove script. Stopping the RPC client das_monitor... Stopping the RPC server das_svrd... Removing cron job for das_check...done ## Removing pathnames in <none> class /usr/sbin/das_users
Installation
/usr/sbin/das_svrd /usr/sbin/das_monitor /usr/sbin/das_mgr /usr/sbin/das_check /usr/sbin <shared pathname not removed> /usr/man/catl/das_svrd.l.fmtd /usr/man/catl/das_monitor.l.fmtd /usr/man/catl/das_mgr.l.fmtd /usr/man/catl/das_check.l.fmtd /usr/man/catl /usr/man /usr <shared pathname not removed> /etc/rc2.d/S77das_mon /etc/rc2.d/S76das_svr /etc/rc2.d <shared pathname not removed> /etc/rc0.d/K77das_svr /etc/rc0.d/K76das_mon /etc/rc0.d <shared pathname not removed> /etc/init.d/das_svr /etc/init.d/das_mon /etc/init.d <shared pathname not removed> /etc <shared pathname not removed>
Installation
## Updating system information. Removal of <MTI9000> was successful.
SGI - Software Management Using MTI "INSTALL"

The install is a two step process. Step one is to load the software on the host system from tape or a file retrieved over the Internet. Step two is to install the software using the MTI "INSTALL" script. First, make the device special files needed by the MTI9000 software to access the array: % cd /dev % MAKEDEV scsi The next several sections describe how to load the software from a variety of places: a local tape drive, a remote tape drive, and from the Internet. Before the software is loaded, make the destination directory with the following command(It is ok to get an error that the directory already exists.): # mkdir -p /usr/local/irix Now skip to one of the next 3 software load sections that applies to your configuration. SGI - Load Software from Local Tape Drive To begin the installation, insert the 4mm or 8mm tape labeled "MTI9000" into the tape drive on the system, become root and type the following commands: NOTE: Use the "ns" or "no byte swapping" tape device. # mkdir -p /usr/local # cd /usr/local # tar xf /dev/rmt/<tape device> irix ...tar output... # cd irix # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.6.2.4 - SGI - Install
Installation
Software. SGI - Load Software from Remote Tape Drive If there is no tape drive on the system, insert the tape into the proper tape drive on another system on the network and type the following command on the remote system: NOTE: Use the "ns" or "no byte swapping" tape device if the remote tape device is on an SGI machine. # tar xf /dev/rmt/<tape device> irix - | tar cf /tmp/irix.tar Now, use the ftp(1C) utility to send the "irix.tar" file to the "/usr/local" directory of host system that has the array attached. Then, return to host machine and type the following commands: # cd /usr/local # tar xvf irix.tar ... .tar output... # cd irix # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.6.2.4 - SGI - Install Software. SGI - Load Software from File Retrieved over the Internet If the software was downloaded over the Internet as a single file(<filenme>), then copy the file to the "/usr/local/ irix" directory of the local host where the array is attached. On the host machine and type the following command: # cd /usr/local/irix # tar xf <filename> ... tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.6.2.4 - SGI - Install Software.
Installation
SGI - Install Software To integrate the Series 9000 software with the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/irix/MTI9000 During the install, you will be asked if you want to run the "DAS9000 Consistency Checker regularly". It is strongly recommended to run das_check on a regular basis. If you agree, the installation software will prompt for the following information and the results will be automatically entered in the crontab: * Daily or Weekly * The day for "daily" checks * The hour for check to be started Usually, once a week during low usage hours is sufficient, but is can be run daily as in the example below. Note that the array can be online while the check is in progress, but it will be slower than normal, similar to the performance seen while a disk is rebuilding. See das_check(section 3.2.4, RPC Client: das_check) for more details about this process. The example below shows how a typical installation process is started and executed using the "INSTALL" script. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559
Installation
1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **SGI IRIX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?1 Commands in this script need to run with super-user permission in order to INSTALL the MTI 9000 software. Are you sure you want to INSTALL the MTI 9000 software(y/n)? y Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_users...done Installing das_print_version...done Installing das_svrd.l.fmtd...done
Installation
Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Creating required symbolic links...done Do you want to run the DAS9000 Consistency Checker regularly via a crontab job? yes or no? [yes] : yes Run the checker (d)aily or (w)eekly? : d What time should the checker be run? Please enter the hour in 24hour clock format (0-23) : 2 warning: commands will be executed using /bin/sh ***crontab has been updated*** ######################################################### # # # Please reboot your system for changes to take effect. # # # ######################################################### SGI - Check Software There are two reasons that a "check" process should be run: * to find out the revision of the currently installed software * to compare the current state of the installed software against the standard installation template Please note that the check should always work immediately after the software is installed. However, if any customization is done, then the check will fail. In any case, the first difference between the standard template and the current state of the installation is displayed if there are any differences.
Installation
To check the state of the Series 9000 software, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/irix/MTI9000 Below is an example of what should be displayed during a "check" process: # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **SGI IRIX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files
Installation
Type 5 to QUIT - quit this utility Enter option?3 The MTI 9000 software is installed correctly. The current revision is: 2.0.beta SGI - Update Software If it becomes necessary to update the release of the software without disrupting any configuration files(i.e. scheduled crontab jobs, authorized user lists), then run the "update" process from the INSTALL script. The "update" process only replaces binaries and man pages. To update the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/irix/MTI9000 # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (76 of 99)18-Feb-08 11:29:39 AM
Installation
**MTI 9000 Software Installation Utility Revision 2.0.beta **SGI IRIX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?4 Commands in this script need to run with super-user permission in order to UPDATE the MTI 9000 software. Are you sure you want to UPDATE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done
Installation
Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Starting RPC server das_svrd...done Starting RPC client das_monitor...done SGI - Remove Software To remove the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/irix/MTI9000 Remove the software using option 2 of the INSTALL script. An example is given below. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta
Installation
**SGI IRIX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?2 Commands in this script need to run with super-user permission in order to REMOVE the MTI 9000 software. Are you sure you want to REMOVE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Removing software......done Removing symbolic links...done Removing crontab job for das_check...done
IBM AIX
This sections describes how to load and install the MTI9000 software package on an IBM AIX machine.
IBM - Software Management Using MTI "INSTALL"

The install is a two step process. Step one is to load the software on the host system from tape or a file retrieved over the Internet. Step two is to install the software using the MTI "INSTALL" script. The next several sections describe how to load the software from a variety of places: a local tape drive, a remote tape drive, and from the Internet. Before the software is loaded, make the destination directory with the following command(It is ok to get an error that the directory already exists.): # mkdir -p /usr/local/aix
Installation
Now skip to one of the next 3 software load sections that applies to your configuration. IBM - Load Software from Local Tape Drive To begin the installation, insert the 4mm or 8mm tape labeled "MTI9000" into the tape drive on the system, become root and type the following commands: # mkdir -p /usr/local # cd /usr/local # tar xf /dev/rmt/<tape device> aix ...tar output... # cd aix # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.7.1.4 - IBM - Install Software. IBM - Load Software from Remote Tape Drive If there is no tape drive on the system, insert the tape into the proper tape drive on another system on the network and type the following command on the remote system: # tar xf /dev/rmt/<tape device> aix - | tar cf /tmp/aix.tar Now, use the ftp(1C) utility to send the "aix.tar" file to the "/usr/local" directory of host system that has the array attached. Then, return to host machine and type the following commands: # cd /usr/local # tar xvf aix.tar ... .tar output... # cd aix # tar xvf MTI9000.tar.<release level>
Installation
... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.7.1.4 - IBM - Install Software. IBM - Load Software from File Retrieved over the Internet If the software was downloaded over the Internet as a single file(<filenme>), then copy the file to the "/usr/local/ aix" directory of the local host where the array is attached. On the host machine and type the following command: # cd /usr/local/aix # tar xf <filename> ... tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.7.1.4 - IBM - Install Software. IBM - Install Software To integrate the Series 9000 software with the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/aix/MTI9000 During the install, you will be asked if you want to run the "DAS9000 Consistency Checker regularly". It is strongly recommended to run das_check on a regular basis. If you agree, the installation software will prompt for the following information and the results will be automatically entered in the crontab: * Daily or Weekly * The day for "daily" checks * The hour for check to be started Usually, once a week during low usage hours is sufficient, but is can be run daily as in the example below. Note that the array can be online while the check is in progress, but it will be slower than normal, similar to the performance seen while a disk is rebuilding. See das_check(section 3.2.4, RPC Client: das_check) for more details about this process. The example below shows how a typical installation process is started and executed using the "INSTALL" script.
Installation
# ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **IBM AIX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?1 Commands in this script need to run with super-user permission in order to INSTALL the MTI 9000 software.
Installation
Are you sure you want to INSTALL the MTI 9000 software(y/n)? y Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_users...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Creating required symbolic links...done Adding RPC server das_svrd to /etc/inittab...done Adding RPC client das_monitor to /etc/inittab...done Do you want to run the DAS9000 Consistency Checker regularly via a crontab job? yes or no? [yes] : yes Run the checker (d)aily or (w)eekly? : d What time should the checker be run? Please enter the hour in 24hour clock format (0-23) : 2
Installation
warning: commands will be executed using /bin/sh ***crontab has been updated*** ######################################################### # # # Please reboot your system for changes to take effect. # # # ######################################################### IBM - Check Software There are two reasons that a "check" process should be run: * to find out the revision of the currently installed software * to compare the current state of the installed software against the standard installation template Please note that the check should always work immediately after the software is installed. However, if any customization is done, then the check will fail. In any case, the first difference between the standard template and the current state of the installation is displayed if there are any differences. To check the state of the Series 9000 software, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/aix/MTI9000 Below is an example of what should be displayed during a "check" process: # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by
Installation
copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **IBM AIX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?3 The MTI 9000 software is installed correctly. The current revision is: 2.0.beta IBM - Update Software If it becomes necessary to update the release of the software without disrupting any configuration files(i.e. scheduled crontab jobs, authorized user lists), then run the "update" process from the INSTALL script. The "update" process only replaces binaries and man pages. To update the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/aix/MTI9000
Installation
# ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **IBM AIX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?4 Commands in this script need to run with super-user permission in order to UPDATE the MTI 9000 software.
Installation
Are you sure you want to UPDATE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Starting RPC server das_svrd...done Starting RPC client das_monitor...done IBM - Remove Software To remove the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/aix/MTI9000 Remove the software using option 2 of the INSTALL script. An example is given below. # ./INSTALL
Installation
----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **IBM AIX Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?2 Commands in this script need to run with super-user permission in order to REMOVE the MTI 9000 software. Are you sure you want to REMOVE the MTI 9000 software(y/n)? y
Installation
Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Removing software......done Removing symbolic links...done Removing RPC server das_svrd from /etc/inittab... done Removing RPC client das_monitor from /etc/inittab...done Removing crontab job for das_check...done
DEC Digital UNIX(formerly OSF/1)

This sections describes how to load and install the MTI9000 software package on an DEC Digital UNIX machine.
DEC - Software Management Using MTI "INSTALL"

The install is a two step process. Step one is to load the software on the host system from tape or a file retrieved over the Internet. Step two is to install the software using the MTI "INSTALL" script. The next several sections describe how to load the software from a variety of places: a local tape drive, a remote tape drive, and from the Internet. Before the software is loaded, make the destination directory with the following command(It is ok to get an error that the directory already exists.): # mkdir -p /usr/local/digitalunix Now skip to one of the next 3 software load sections that applies to your configuration. DEC - Load Software from Local Tape Drive To begin the installation, insert the 4mm or 8mm tape labeled "MTI9000" into the tape drive on the system, become root and type the following commands: # mkdir -p /usr/local # cd /usr/local # tar xf /dev/rmt/<tape device> digitalunix ...tar output...
Installation
# cd digitalunix # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.8.1.4 - DEC - Install Software. DEC - Load Software from Remote Tape Drive If there is no tape drive on the system, insert the tape into the proper tape drive on another system on the network and type the following command on the remote system(Note: the following command must be typed in on a single command line): # tar xf /dev/rmt/<tape device> digitalunix - | tar cf /tmp/digitalunix.tar Now, use the ftp(1C) utility to send the "digitalunix.tar" file to the "/usr/local" directory of host system that has the array attached. Then, return to host machine and type the following commands: # cd /usr/local # tar xvf digitalunix.tar ... .tar output... # cd digitalunix # tar xvf MTI9000.tar.<release level> ... .tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.8.1.4 - DEC - Install Software. DEC - Load Software from File Retrieved over the Internet If the software was downloaded over the Internet as a single file(<filenme>), then copy the file to the "/usr/local/ digitalunix" directory of the local host where the array is attached. On the host machine and type the following command: # cd /usr/local/digitalunix
Installation
# tar xf <filename> ... tar output... The final step should have created a directory named "MTI9000". Now proceed to section 2.8.1.4 - DEC - Install Software. DEC - Install Software To integrate the Series 9000 software with the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/digitalunix/MTI9000 During the install, you will be asked if you want to run the "DAS9000 Consistency Checker regularly". It is strongly recommended to run das_check on a regular basis. If you agree, the installation software will prompt for the following information and the results will be automatically entered in the crontab: * Daily or Weekly * The day for "daily" checks * The hour for check to be started Usually, once a week during low usage hours is sufficient, but is can be run daily as in the example below. Note that the array can be online while the check is in progress, but it will be slower than normal, similar to the performance seen while a disk is rebuilding. See das_check(section 3.2.4, RPC Client: das_check) for more details about this process. The example below shows how a typical installation process is started and executed using the "INSTALL" script. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without
Installation
prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta **DEC Digital UNIX(formerly OSF/1) Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?1 Commands in this script need to run with super-user permission in order to INSTALL the MTI 9000 software. Are you sure you want to INSTALL the MTI 9000 software(y/n)? y Installing das_svrd...done Installing das_mgr...done Installing das_check...done Installing das_monitor...done Installing das_svr...done
Installation
Installing das_mon...done Installing das_users...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Creating required symbolic links...done Adding RPC server das_svrd to /etc/inittab...done Adding RPC client das_monitor to /etc/inittab...done Do you want to run the DAS9000 Consistency Checker regularly via a crontab job? yes or no? [yes] : yes Run the checker (d)aily or (w)eekly? : d What time should the checker be run? Please enter the hour in 24hour clock format (0-23) : 2 warning: commands will be executed using /bin/sh ***crontab has been updated*** ######################################################### # # # Please reboot your system for changes to take effect. # # # #########################################################
Installation
DEC - Check Software There are two reasons that a "check" process should be run: * to find out the revision of the currently installed software * to compare the current state of the installed software against the standard installation template Please note that the check should always work immediately after the software is installed. However, if any customization is done, then the check will fail. In any case, the first difference between the standard template and the current state of the installation is displayed if there are any differences. To check the state of the Series 9000 software, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/digitalunix/MTI9000 Below is an example of what should be displayed during a "check" process: # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (94 of 99)18-Feb-08 11:29:39 AM
Installation
**MTI 9000 Software Installation Utility Revision 2.0.beta ** DEC Digital UNIX(formerly OSF/1) Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?3 The MTI 9000 software is installed correctly. The current revision is: 2.0.beta DEC - Update Software If it becomes necessary to update the release of the software without disrupting any configuration files(i.e. scheduled crontab jobs, authorized user lists), then run the "update" process from the INSTALL script. The "update" process only replaces binaries and man pages. To update the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/digitalunix/MTI9000 # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without
Installation
prior written consent of MTI. MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta ** DEC Digital UNIX(formerly OSF/1) Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?4 Commands in this script need to run with super-user permission in order to UPDATE the MTI 9000 software. Are you sure you want to UPDATE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Installing das_svrd...done Installing das_mgr...done Installing das_check...done
Installation
Installing das_monitor...done Installing das_svr...done Installing das_mon...done Installing das_print_version...done Installing das_svrd.l.fmtd...done Installing das_mgr.l.fmtd...done Installing das_check.l.fmtd...done Installing das_monitor.l.fmtd...done Starting RPC server das_svrd...done Starting RPC client das_monitor...done DEC - Remove Software To remove the Series 9000 software from the operating system, it is necessary to run the "INSTALL" script from within the MTI9000 directory. To get into this directory type the following command: # cd /usr/local/digitalunix/MTI9000 Remove the software using option 2 of the INSTALL script. An example is given below. # ./INSTALL ----------------------------------------------------------------------------MTI Disk Array Subsystem Copyright 1996 All Rights Reserved Worldwide This software contains proprietary information which is protected by copyright. No part of this software may be reproduced without prior written consent of MTI.
Installation
MTI 1111 Pasquinelli Suite 400 Westmont, IL 60559 1-708-325-4151 ----------------------------------------------------------------------------**MTI 9000 Software Installation Utility Revision 2.0.beta ** DEC Digital UNIX(formerly OSF/1) Type 1 to INSTALL - complete install of utilities and configuration files Type 2 to REMOVE - complete removal of utilities and configuration files Type 3 to CHECK - check if software is installed properly Type 4 to UPDATE - update utilities, but do not change config files Type 5 to QUIT - quit this utility Enter option?2 Commands in this script need to run with super-user permission in order to REMOVE the MTI 9000 software. Are you sure you want to REMOVE the MTI 9000 software(y/n)? y Stopping RPC client das_monitor...done Stopping RPC server das_svrd...done Removing software......done Removing symbolic links...done Removing RPC server das_svrd from /etc/inittab... done Removing RPC client das_monitor from /etc/inittab...done
Installation
Removing disktab entry from /etc/disktab...done Removing crontab job for das_check...done
RPC-based Utilities
RPC-based Utilities With the release of revision 2.0 of the suite of management software for Series 9000 arrays, MTI has adopted an RPC(Remote Procedure Call) based software architecture. An RPC based software architecture has resulted in the following enhancements in the current release:
* Utilities can be executed on any supported machine in the network, regardless of where an array is attached. For instance, an array can be attached to a Sun, but the monitor and configuration processes can be executing on an HP. Real benefits can be seen by managing an entire network of servers and arrays from a centralized management station. * When using IBM RS/6000 or SGI machines, it is now possible to run more multiple applications on an array concurrently. Theses machines only allow a single process to use a device for the purposes of sending SCSI passthrough commands. Understandably, it can be annoying to be required to kill monitor processes in order to run a configuration manager. This host bottleneck also hampered development of new software utilities(i.e. das_check). * The Series 9000 software now has intelligence to automatically "find" arrays attached to the system. For instance, when the configuration utility is invoked, no device names are necessary. If there is more than one array attached, the user is prompted with a list of valid Series 9000 array devices. This enhancement would have caused too much overhead to be feasible without an RPC based architecture. * RPC is a standard in the industry across a wide variety of operating systems including most UNIX machines, Novell Netware & Windows NT. This section discusses RPC technology and the use of all RPC-based software modules for the Series 9000 array.
Remote Procedure Call Definition

Remote Procedure Calls (RPC) allows C programs to make procedure calls to other processes. An RPC client process makes procedure calls to an RPC server process. The client and server processes can be running on the same machine or on different machines connected via a network. Furthermore, they can be running on different machine architectures. For example, a client running on a Sun machine can make a procedure call to a Silicon Graphics machine provided that the corresponding server process is running. Figure 3-1 below graphically represents how the RPC architecture has been applied to the suite of management tools for the Series 9000 array.
http://www-personal.umich.edu/~rak/9k_manual/9000rpc.html (1 of 40)18-Feb-08 11:30:02 AM
RPC-based Utilities
Resulting graphical representation of the RPC software architecture applied to the Series 9000 management software. Figure 3-1 The following diagram(Figure 3-2) depicts how an RPC based software architecture can make it easy to manage a network full of Series 9000 arrays running on a variety of different host platforms.
Centralized Management via RPC-based Software Architecture Figure 3-2
Software Components
Release 2.0 of the Series 9000 software contains das_svrd, an RPC server and 3 RPC clients that communicate with
RPC-based Utilities
das_svrd: das_mgr, das_monitor, and das_check. This section describes in detail the use of these utilities. Table 3-1 lists the default path to the Series 9000 software for each of the supported platforms. For the rest of this manual, the symbol <BASEDIR> will be used to designate the default path where the software resides. It is usually a good idea to put <BASEDIR> in your path. CPU Vendor/ <BASEDIR> Sun Solaris etc Sun Solaris sbin SGI IRIX sbin IBM AIX etc HP HP-UX etc DEC Digital etc OS Revision 1.x(SunOS 4.1.3) 2.x(SunOS 5.x) Base Installation Directory /usr/ /usr/ /usr/ /usr/ /usr/ UNIX(OSF) /usr/
Table 3-1
RPC Server - das_svrd

Usage: das_svrd -f [trusted user list] das_svrd is the RPC server daemon which must be running on every host that has a Series 9000 array attached. The server daemon by itself is of no value to a system administrator. However, it is this process that facilitates communication between client processes and Series 9000 arrays. The server daemon will only respond to requests from client daemons with access privileges. The access privileges are setup via an access list kept in a file called das_users. By default, this access list is null. A null access list only allows root on the local machine to use arrays that are attached. If modifications are required, then the das_users file can be edited. This file is located in the base installation directory, <BASEDIR> which is defined in Table 3-1. The access file is a list which contains trusted users, authorization level, and trusted hosts. Each line in the file that does not start with a "#"(comment lines), is an entry. each entry has 3 fields separated by white space(tabs and or spaces). The first field is the user name. The user name can be either the text identifier or the numeric user id(UID). The second field is the authorization level. Valid authorization levels are either "0" or "1". If level "0" is set, than das_svrd will only let non-destructive commands to be sent to the array(i.e. environmental monitoring). If level "1" is set, then das_svrd will perform any screening of commands to the array. A level "1" authorization is only necessary if the user is expected to perform new configurations, download firmware, or other maintenance tasks. The third field is a comma separated list of valid machines that the user can be calling from. The following is an example of a sample access list:
RPC-based Utilities
# MTI # @(#)das_users 1.3 01/17/96 # # # List of authorized users for the DAS9000 RPC clients # The server will allow access only to the users listed here, on the # specified hosts. The format for an entry is split up into 3 fields. # Each field is separated by white space(spaces or tabs). An entry is # ended with a <newline> character. The format of the fields for an entry is # as follows: # # <user> <authorization level> <host>,<host>,... # # # <user> = user name or a numeric user id # <authorization level> = 0 only allows non-destructive commands # i.e. status and performance monitoring # = 1 allows any commands # i.e. new configurations, maintenance # <host>,<host>,... = comma separated list of host where <user> # can be running command from # # NOTE: If this file is empty(except for comments), then only root on the
RPC-based Utilities
# local machine is allowed access to the array. carter 0 sunserver1,sunserver2, hpserver1 admin 1 sunserver1, sunserver2, hpserver1 In the above example, user "carter" can run non-destructive commands only. User "admin" has full access to the arrays that are being managed by the das_svrd using this authorization file. Starting and Stopping das_svrd If the software is installed properly, das_svrd will startup automatically each time the system boots. This is accomplished by invoking a script called das_svr. This invocation is caused by the automatic daemon startup mechanism for your system(see Table 3-2 below). CPU Vendor/ OS Revision Mechanism Sun Solaris 1.x(SunOS 4.1.3) local Sun Solaris 2.x(SunOS 5.x) in e. /etc/rc2.d/S76das_svr > /usr/sbin/ das_svr). SGI IRIX in e. /etc/rc2.d/S76das_svr > /usr/sbin/ das_svr). IBM AIX inittab HP HP-UX inittab DEC Digital UNIX(OSF) inittab An entry is added to the /etc/ file. An entry is added to the /etc/ file. An entry is added to the /etc/ file. A link to the das_svr script is put /etc/rc2.d. (i. Automatic Daemon Startup An entry is added to the /etc/rc. file. A link to the das_svr script is put /etc/rc2.d. (i.
Table 3-2
RPC-based Utilities
das_svr takes a single argument. The value for the argument is either "start" or "stop". To start the RPC server das_svrd, simply execute # <BASEDIR>/das_svr start By default, this script reads the das_users file to determine access privileges. To stop the RPC server: # <BASEDIR>/das_svr stop As das_svrd starts up it scans all available SCSI devices on the system for valid array devices. If a Series 9000 array is found, then a message displaying the device file for each array that is found is sent to syslogd. The syslogd daemon, in turn, routes the message to the standard log file(see Table 5-1 for location of standard log file on your platform) . Below is a an example of the output that would be seen in the standard log file. In this example, an HP9000 Series 700 machine has found and established links with 2 arrays. The device special files for these arrays are /dev/ rdsk/c410d4l0s0 & /dev/rdsk/c410d5l0s0. hp1 /usr/etc/das_svrd[3441]: ** Establishing device links... ** hp1 /usr/etc/das_svrd[3441]: Linking /dev/rdsk/c410d4l0s0 hp1 /usr/etc/das_svrd[3441]: Linking /dev/rdsk/c410d5l0s0 hp1 /usr/etc/das_svrd[3441]: ** Done establishing device links . **
RPC Client - das_mgr

Usage: das_mgr [-h server] -h: the hostname of the machine running the das_svrd RPC server If -h is not specified, the local machine is assumed The first RPC Client to be discussed is the das_mgr utility. This utility is a text-based configuration and maintenance utility. It is used for a variety of purposes ranging from developing new configurations to downloading new firmware to the array controller. Starting das_mgr The first thing to learn about das_mgr is that this utility can manage arrays anywhere on the network. To manage locally attached arrays, invoke the das_mgr utility with no command line arguments. To manage an array attached to another host named <hostname>, invoke the utility with the command line arguments "-h <hostname>".
RPC-based Utilities
When the das_mgr utility is invoked, it queries das_svrd for a list of arrays to manage. If there is only one in the list, then the utility automatically selects it. Otherwise, the list is displayed and you are allowed to select an array from the list. The entries in the list will be in the form of the device special file. Table 3-3 below describes the meaning of the device special files on all supported platforms. Below is an example of how to invoke das_mgr for local array management. # <BASEDIR>/das_mgr Below is an example session to manage a remote array on a host that has 2 arrays attached. In this example, das_mgr is running a Sun and the remote host is intuitively named "remotehost". It happens to be an HP 9000 series 700 running HP-UX 9.0.5. # <BASEDIR>/das_mgr -h remotehost Arrays on host remotehost: 0: /dev/rdsk/c410d4l0s0 1: /dev/rdsk/c300d4l0s0 Enter the array number (0-2) : 0 Main Menu: Select - Select an array/lun Current - Show the current array/lun Configure - Change/Show the configuration Initialize - Initialize the Redundancy Information Check - Check the Redundancy Information Restore - Check and Restore the Redundancy Information Rebuild - Rebuild Data on a Replaced Disk Unit Progress - Report Rebuild Status Start - Start a Replaced Disk Unit as a Spare Stop - Stop a Disk Unit Hardware - Get information on array hardware
RPC-based Utilities
Download - Download Microcode to the Array Controller Help - Display this menu ? - Display this menu Quit - Quit the maintenance Utility Main> current Current Device: remotehost:/dev/rdsk/c410d4l0s0 Main> select Current host/array selection is "remotehost:/dev/rdsk/c410d4l0s0" Enter new host [RETURN to leave host unchanged] :remotehost Arrays on host : 0: /dev/rdsk/c410d4l0s0 1: /dev/rdsk/c300d4l0s0 Enter the array number (0-2) : 1 Main> current Current Device: remotehost:/dev/rdsk/c300d4l0s0 Main> Interacting with das_mgr das_mgr is an interactive menu-driven utility. When selecting a menu option, type in enough characters to make your selection unambiguous. For instance, if the "Current" option in the "Main" menu is required then quickly scan other menu options that start with "c". A quick scan yields that there is another menu selection that starts with "c": "Configure". Therefore, it is necessary to type at least a "cu" to select "Current" and at least a "co" to select "Configure". Of course, it is still valid to type the entire word for the menu selection. On a final note, the menu options are not case sensitive. Device Naming Conventions When it comes to choosing a device name from a list of supported devices, it is helpful to be familiar with the format for a device name. Unfortunately, each platform has its own nomenclature for device names. To make matters worse,
RPC-based Utilities
naming conventions often change with major releases of the operating system. Fortunately, this manual has a summery of the device naming conventions for each of the supported platforms and operating systems in Table 3-3 below. PLATFORM DEVICE SUN Solaris rsd2c 1.x(SunOS) The every device has a unique number. SUN Solaris c1t0d0s0 2.x(Solaris) S= number IBM AIX rhdisk1 that every device has a unique SGI IRIX sc1d0l0 ID HP HP/UX 9.0.5 c410d1s0 for series 700 LUN HP HP/UX 10.x for c1t0d0s0 series 700 S= number HP HP/UX 9.0.4 rdrv1 for series 800 with spt HP HP/UX 10.x for scXdYl0 number. X= Controller number Y= SCSI cXdYlZs0 X= Controller path Y= SCSI ID Z= SCSI cWtXdYsZ W= Controller number X= SCSI ID Y= SCSI LUN Partition rdrvX X= HP assigned LU number /dev/ /dev/rdsk/ /dev/rdsk/ /dev/scsi/ cWtXdYsZ W= Controller number X= SCSI ID Y= SCSI LUN Partition rhdiskX X= an arbitrary number. The only rule is /dev/ /dev/rdsk/ TYPE DESCRIPTION of DEVICE NAME EXAMPLE NAME /dev/
rsdXY
X= an arbitrary number between 0 and 31. only rule is that
rdrvX
X= HP assigned LU number
/dev/
RPC-based Utilities
rdrv1 series 800 with spt HP HP/UX 10.x for c1t0d0s0 series 800 S= without spt number DEC Digital rrz8c UNIX(formerly scsi OSF/1) scsi retrieved
cWtXdYsZ
W= Controller number X= SCSI ID Y= SCSI LUN Partition
/dev/rdsk/
rrzXY
X=((SCSI bus #) * 8) + (SCSI target) The
/dev/
bus number and the target can be by typing "show dev"
at the monitor prompt">>>"(PROM level)
Table 3-3 Menu Items This section takes a methodical approach to describing the function of every menu option that is selectable in das_mgr.
Select
This menu selection allows you to select a different array without leaving the utility. Upon selecting this option, it will be necessary to type the name of the host where the array is attached. If there is more than one array attached, then pick among the available arrays that are listed. Main> select Current host/array selection is "remotehost:/dev/rdsk/c410d4l0s0" Enter new host [RETURN to leave host unchanged] :remotehost Arrays on host :
RPC-based Utilities
0: /dev/rdsk/c410d4l0s0 1: /dev/rdsk/c300d4l0s0 Enter the array number (0-2) : 1 Main>

Current
This menu selection simply displays the current device that is currently connected to the utility. Between the colon's, the name of the host that has the array attached is listed. After the final colon, the full path to the opened device file is displayed. Main> current Current Device: remotehost:/dev/rdsk/c300d4l0s0
Configure
This menu selection will display another menu of choices. These choices allow you to manage the configuration of the array. If data is currently online from the array, then do not select any options other than `get', `show', `detail' or `save'. Main> con Configuration Menu: Get - Get the Current Configuration from the Array Show - Show the Working Configuration Detail - Show Detailed Working Configuration New - Create a New Configuration (Old data will be lost) Set - Set the Array's Config to the Working Config Clear - Clear the Array's Configuration Save - Save the Working Configuration to a File Load - Load the Working Configuration from a File Salvage - Attempt to force a drive to its configured state
RPC-based Utilities
Help - Display this menu ? - Display this menu Quit - Quit the Configuration Menu
Get
This menu selection retrieves the configuration from the NVRAM of the array controller and displays it in a readable format. The "Status" of each LUN will be displayed along with its "Capacity", "RAID" level, and "Cache" algorithm. The "Status" will be either "Online", "Degraded", or "Offline". Obviously, everything is fine if "Online" is reported. "Degraded" means that a single disk has failed. If the failed disk is replaced, then the controller will rebuild to the new disk. When the rebuild is complete, each LUN will change to "Online" status. If "Offline" is reported, then there has been a serious error on the array causing more than 1 disk to fail. This is usually caused by the first disk failure going undetected. An "Offline" status should be reported to the technical support. The "Capacity" of the array is reported in Megabytes. The "RAID" level reported will one of the following: RAID 0 - Hardware striping without any redundancy. This is a very high performing RAID level, but does not protect your data in the event of a disk failure. RAID 1 - Hardware striping across 2 disk drives with full redundancy. This RAID level is also known as mirroring. Mirroring is geared toward very high performance, but is not always attractive due to its 50% capacity overhead. For example, using RAID 1 across two 2GB disk drives only yields 2GB of usable space. RAID 5 - Hardware striping with redundancy. This is a very high performing RAID level used to maximize I/O's per second with many users/processes and a large percentage of reads. This RAID offers very low capacity overhead(as low as 12.5%) and good write performance if the Write-Back cache is enabled. RAID 6 - This is not a recognized RAID level, but stands for a combination of RAID levels. Specifically, it is the combination of RAID 0 and RAID 1. For example, an 8 drive configuration would be configured with two RAID 0 groups each containing 4 disks. The RAID 0 groups would then be mirrored. This is the highest performance RAID combination. The "Write-Back" cache can be Enabled or Disabled. If is enabled, then the controller uses a DRAM write cache to signal an I/O completion to the host before the data actually gets to the underlying disk drives. The data will be synchronized with the underlying disk drives within 3 seconds. This is safe due the fact the cache is battery-backed with trickle charge batteries that can keep data alive for 6 hours with a 16MB cache. In addition, it is recommended that the both of the load sharing power supplies be plugged into a UPS. Each disk within the array has a Channel and Target associated with it. This address is unique for each device. In addition, the disk will have a "Configured State" and a "Current State". An "Online" state is normal. A "Dead" state means that the disk has failed. A "Spare" state indicates that the disk is currently in standby mode. It will be used as the target of a rebuild operation in the event that another disk fails. The number of "Sectors" reported is the number
RPC-based Utilities
of 512 byte blocks available on the disk. For your convenience, the number of Megabytes is reported in the final column. The last entry in this display is a report of the type of stripping that the array is using. The entire array will have a stripe depth that pertains to all LUNs. For your convenience, an 8k stripe depth is interpreted as being optimized for random I/O. Likewise, a 64k stripe depth is interpreted as being optimized for sequential I/O. Below is an example of the type output that can be expected. Configuration> get Reading Configuration from NVRAM... Configuration Read Successful. Displaying Current Working Configuration: LUN 0: Status Online; Capacity 1024 MB; RAID 5; Write-Back Enabled LUN 1: Status Online; Capacity 1024 MB; RAID 5; Write-Back Enabled LUN 2: Status Online; Capacity 1024 MB; RAID 5; Write-Back Enabled LUN 3: Status Online; Capacity 2048 MB; RAID 5; Write-Back Enabled LUN 4: Status Online; Capacity 5120 MB; RAID 5; Write-Back Enabled LUN 5: Status Online; Capacity 14330 MB; RAID 5; Write-Back Enabled Disk Configuration: Configured Current Channel Target State State Sectors MBytes 0 0 Online Online 8386560 4095 0 1 Online Online 8386560 4095 0 2 Online Online 8386560 4095 0 3 Online Online 8386560 4095 1 0 Online Online 8386560 4095 1 1 Online Online 8386560 4095
RPC-based Utilities
1 2 Online Online 8386560 4095 1 3 Spare Spare 8386560 4095 Striping optimized for random I/O
Show
This menu selection displays the working configuration in a readable format. section 3.2.2.4.3.1 - Get, for details on meaning of the various fields. Configuration> show LUN 0: Status Online; Capacity 1024 MB; RAID 5; Write-Back Enabled LUN 1: Status Online; Capacity 1024 MB; RAID 5; Write-Back Enabled LUN 2: Status Online; Capacity 1024 MB; RAID 5; Write-Back Enabled LUN 3: Status Online; Capacity 2048 MB; RAID 5; Write-Back Enabled LUN 4: Status Online; Capacity 5120 MB; RAID 5; Write-Back Enabled LUN 5: Status Online; Capacity 14330 MB; RAID 5; Write-Back Enabled Disk Configuration: Configured Current Channel Target State State Sectors MBytes 0 0 Online Online 8386560 4095 0 1 Online Online 8386560 4095 0 2 Online Online 8386560 4095 0 3 Online Online 8386560 4095 1 0 Online Online 8386560 4095 1 1 Online Online 8386560 4095 1 2 Online Online 8386560 4095
RPC-based Utilities
1 3 Spare Spare 8386560 4095 Striping optimized for random I/O

Detail
This menu selection displays the working configuration in a verbose format. In addition, to fields displayed in section 3.2.2.4.3.1 - Get, the components of each LUN are displayed. A component is known as an "Arm". A number of "Arms" are used together from separate disks to make a logical volume or LUN. Configuration> de LUN 0: Status Online; Capacity 1024 MB; RAID 5; Write-Back Enabled Arm 0: Disk 0: Channel 1 Target 3 Start: 0 Sectors: 349525 Arm 1: Disk 0: Channel 1 Target 0 Start: 0 Sectors: 349525 Arm 2: Disk 0: Channel 0 Target 0 Start: 0 Sectors: 349525 Arm 3: Disk 0: Channel 1 Target 1 Start: 0 Sectors: 349525 Arm 4: Disk 0: Channel 0 Target 2 Start: 0 Sectors: 349525 Arm 5:
RPC-based Utilities
Disk 0: Channel 1 Target 2 Start: 0 Sectors: 349525 Arm 6: Disk 0: Channel 0 Target 3 Start: 0 Sectors: 349525 LUN 1: Status Online; Capacity 1024 MB; RAID 5; Write-Back Enabled Arm 0: Disk 0: Channel 1 Target 3 Start: 349525 Sectors: 349525 Arm 1: Disk 0: Channel 1 Target 0 Start: 349525 Sectors: 349525 Arm 2: Disk 0: Channel 0 Target 0 Start: 349525 Sectors: 349525 Arm 3: Disk 0: Channel 1 Target 1 Start: 349525 Sectors: 349525 Arm 4: Disk 0: Channel 0 Target 2 Start: 349525 Sectors: 349525 Arm 5: Disk 0: Channel 1 Target 2
RPC-based Utilities
Start: 349525 Sectors: 349525 Arm 6: Disk 0: Channel 0 Target 3 Start: 349525 Sectors: 349525 LUN 2: Status Online; Capacity 1024 MB; RAID 5; Write-Back Enabled Arm 0: Disk 0: Channel 1 Target 3 Start: 699050 Sectors: 349525 Arm 1: Disk 0: Channel 1 Target 0 Start: 699050 Sectors: 349525 Arm 2: Disk 0: Channel 0 Target 0 Start: 699050 Sectors: 349525 Arm 3: Disk 0: Channel 1 Target 1 Start: 699050 Sectors: 349525 Arm 4: Disk 0: Channel 0 Target 2 Start: 699050 Sectors: 349525 Arm 5: Disk 0: Channel 1 Target 2 Start: 699050 Sectors: 349525
RPC-based Utilities
Arm 6: Disk 0: Channel 0 Target 3 Start: 699050 Sectors: 349525 LUN 3: Status Online; Capacity 2048 MB; RAID 5; Write-Back Enabled Arm 0: Disk 0: Channel 1 Target 3 Start: 1048575 Sectors: 699050 Arm 1: Disk 0: Channel 1 Target 0 Start: 1048575 Sectors: 699050 Arm 2: Disk 0: Channel 0 Target 0 Start: 1048575 Sectors: 699050 Arm 3: Disk 0: Channel 1 Target 1 Start: 1048575 Sectors: 699050 Arm 4: Disk 0: Channel 0 Target 2 Start: 1048575 Sectors: 699050 Arm 5: Disk 0: Channel 1 Target 2 Start: 1048575 Sectors: 699050 Arm 6:
RPC-based Utilities
Disk 0: Channel 0 Target 3 Start: 1048575 Sectors: 699050 LUN 4: Status Online; Capacity 5120 MB; RAID 5; Write-Back Enabled Arm 0: Disk 0: Channel 1 Target 3 Start: 1747625 Sectors: 1747626 Arm 1: Disk 0: Channel 1 Target 0 Start: 1747625 Sectors: 1747626 Arm 2: Disk 0: Channel 0 Target 0 Start: 1747625 Sectors: 1747626 Arm 3: Disk 0: Channel 1 Target 1 Start: 1747625 Sectors: 1747626 Arm 4: Disk 0: Channel 0 Target 2 Start: 1747625 Sectors: 1747626 Arm 5: Disk 0: Channel 1 Target 2 Start: 1747625 Sectors: 1747626 Arm 6: Disk 0: Channel 0 Target 3
RPC-based Utilities
Start: 1747625 Sectors: 1747626 LUN 5: Status Online; Capacity 14330 MB; RAID 5; Write-Back Enabled Arm 0: Disk 0: Channel 1 Target 3 Start: 3495251 Sectors: 4891306 Arm 1: Disk 0: Channel 1 Target 0 Start: 3495251 Sectors: 4891306 Arm 2: Disk 0: Channel 0 Target 0 Start: 3495251 Sectors: 4891306 Arm 3: Disk 0: Channel 1 Target 1 Start: 3495251 Sectors: 4891306 Arm 4: Disk 0: Channel 0 Target 2 Start: 3495251 Sectors: 4891306 Arm 5: Disk 0: Channel 1 Target 2 Start: 3495251 Sectors: 4891306 Arm 6: Disk 0: Channel 0 Target 3 Start: 3495251 Sectors: 4891306
RPC-based Utilities
Disk Configuration: Configured Current Channel Target State State Sectors MBytes 0 0 Online Online 8386560 4095 0 1 Online Online 8386560 4095 0 2 Online Online 8386560 4095 0 3 Online Online 8386560 4095 1 0 Online Online 8386560 4095 1 1 Online Online 8386560 4095 1 2 Online Online 8386560 4095 1 3 Spare Spare 8386560 4095 Striping optimized for random I/O Stripe Depth = 8k
New
Creating a "New" configuration is described in detail in Chapter 3 - Error! Not a valid bookmark self-reference.. Below is another example of a "New" configuration. Configuration> new Warning: This will create a new configuration. Any data on the array will be lost. Do you wish to continue (y/n)> y Warning: This will immediately make all storage on the array inaccessible. Continuing will take the array offline now. Do you still wish to continue? (y/n)> y
RPC-based Utilities
Searching for Drives... Checking target 0, channel 0... Found a SEAGATE ST15150W Revision 0017 Serial # 00469361 Capacity 8386560 sectors. Checking target 0, channel 1... Found a SEAGATE ST15150W Revision 0017 Serial # 00476434 Capacity 8386560 sectors. Checking target 1, channel 0... Found a SEAGATE ST15150W Revision 0017 Serial # 00459183 Capacity 8386560 sectors. Checking target 1, channel 1... Found a SEAGATE ST15150W Revision 0017 Serial # 00478512 Capacity 8386560 sectors. Checking target 2, channel 0... Found a SEAGATE ST15150W Revision 0017 Serial # 00479524 Capacity 8386560 sectors. Checking target 2, channel 1... Found a SEAGATE ST15150W Revision 0017 Serial # 00452135 Capacity 8386560 sectors. Checking target 3, channel 0... Found a SEAGATE ST15150W Revision 0017 Serial # 00480357 Capacity 8386560 sectors. Checking target 3, channel 1...
RPC-based Utilities
Found a SEAGATE ST15150W Revision 0017 Serial # 00476470 Capacity 8386560 sectors. Checking target 4, channel 0... No device found Checking target 4, channel 1... No device found Checking target 5, channel 0... No device found Checking target 5, channel 1... No device found Checking target 6, channel 0... No device found Checking target 6, channel 1... No device found Found a total of 8 disks. Do you want to configure a spare disk? (y/n)> y Total capacity available is 24570 MB. Configuring LUN 0: Enter Capacity in MB [24570]: 4000 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 1: Enter Capacity in MB [20570]: 4000 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 2: Enter Capacity in MB [16570]: 4000 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 3: Enter Capacity in MB [12570]: 4000 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 4: Enter Capacity in MB [8570]: 4000 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 5: Enter Capacity in MB [4570]: 4000 Use Write-Back Cache for this LUN? (y/n)> y
RPC-based Utilities
Configuring LUN 6: Enter Capacity in MB [570]: Use Write-Back Cache for this LUN? (y/n)> y Optimize for random('r') or sequential('s') I/O?[r] Configuring 7 LUNs, leaving 0 MB free.
Set
This menu option copies the working configuration to the NVRAM and EEPROM of the array. Configuration> set Do you really want to write the working configuration to the array? (Any data on the array will be lost) (y/n)> y Writing Configuration to the array... Set Configuration Successful.
Clear
This menu option clears the configuration on the array. This is the recommended way to prepare an empty standby array. Configuration> clear Do you really want to clear the current configuration of the array? (Any data on the array will be lost) (y/n)> y Clearing Configuration of the array... Clear Configuration Successful. Configuration> get Reading Configuration from NVRAM... Configuration Read Successful. Displaying Current Working Configuration: Disk Configuration:
RPC-based Utilities
Configured Current Channel Target State State Sectors MBytes Striping optimized for random I/O Configuration>
Save
This menu option will save the configuration of the array to a UNIX file. This file should be kept on media that is backed up. It is needed if the disks are moved to a new array or the controller is replaced. This is discussed in section 7.4 - Replacing a Controller. Configuration> save Enter the filename to which you will save the config. > /config.c410d6 Save Configuration Successful.
Load
This is used to recover a configuration of array in the event the array chassis is replaced or the controller is replaced. This is discussed in section 7.4 - Replacing a Controller. After a "Load", the configuration is just in memory. Use "Set" to copy this configuration to NVRAM. Configuration> load Enter the filename containing the new configuration. > /config.c410d6 Configuration Load Successful. Displaying Current Working Configuration: LUN 0: Status Online; Capacity 4000 MB; RAID 5; Write-Back Enabled LUN 1: Status Online; Capacity 4000 MB; RAID 5; Write-Back Enabled LUN 2: Status Online; Capacity 4000 MB; RAID 5; Write-Back Enabled LUN 3: Status Online; Capacity 4000 MB; RAID 5; Write-Back Enabled
RPC-based Utilities
LUN 4: Status Online; Capacity 4000 MB; RAID 5; Write-Back Enabled LUN 5: Status Online; Capacity 4000 MB; RAID 5; Write-Back Enabled LUN 6: Status Online; Capacity 570 MB; RAID 5; Write-Back Enabled Disk Configuration: Configured Current Channel Target State State Sectors MBytes 0 0 Online Online 8386560 4095 0 1 Online Online 8386560 4095 0 2 Online Online 8386560 4095 0 3 Online Online 8386560 4095 1 0 Online Online 8386560 4095 1 1 Online Online 8386560 4095 1 2 Online Online 8386560 4095 1 3 Spare Spare 8386560 4095 Striping optimized for random I/O
Salvage
This menu option is restricted to authorized support personnel only.

Initialize
This menu option initializes a LUN on the array. Each LUN must be initialized separately. ALL LUN's MUST BE INITIALIZED TO ENSURE DATA INTEGRITY. Main> init Enter a LUN (0-7) : 0 Ready to initialize the lun. This will destroy all data on this lun.
RPC-based Utilities
This takes a long time and cannot be interrupted. OK to continue? (y/n)> y Initialization 0% Complete
Check
This menu option will check the data consistency of the array. Each stripe of data including the parity block is read into memory. The parity is calculated and compared to the read parity. If there is an inconsistency, it is reported, but not fixed. This is an excellent way to read all blocks on the array. Running this operation periodically is strongly encouraged to ensure that no bad blocks are found during a critical rebuild operation. A utility called "das_check" has been developed so that these checks can be run automatically in the background during low-usage hours. See section 3.2.4 - RPC Client: das_check. Main> check Enter a LUN (0-7) : 0 Ready to check the consistency of redundancy data. OK to continue? (y/n)> y Consistency Check 0% Complete
Restore
This menu option is identical to the "Check" operation in every way except in the way it handles an inconsistency. An inconsistency is reported AND fixed. Main> re Enter a LUN (0-7) : 0 Ready to check the consistency of redundancy data. OK to continue? (y/n)> y Consistency Check 0% Complete
Rebuild
This menu option allows you to manually rebuild a disk. This is helpful if an automatic rebuild is aborted for any, such as a power down.
RPC-based Utilities
A manual rebuild will also be necessary if an automatic rebuild failed to take the drive out of the rebuilding state due to a bad block that was encountered. Main> rebuild Enter the channel of the drive to be rebuilt: 1 Enter the target id of the drive to be rebuilt: 3 Ready to rebuild data on channel 1 drive 3. OK to continue? (y/n)> y Rebuild LUN 0 0% Complete
Progress
This menu option reports the progress of a rebuild in progress. This is helpful to monitor automatic rebuilds without consulting the LCD panel. Main> pro No Rebuild in progress Main> pro Rebuild LUN 0 1% Complete
Start
This menu option allows you to manually start a disk as a SPARE. This is helpful if an automatic SPARE enable is aborted for any reason, such as a power down. Main> start Enter the channel of the drive to be started as a spare: 1 Enter the target id of the drive to be started as a spare: 3 Ready to start channel 1 drive 3 as a spare. OK to continue? (y/n)> y
Stop
This menu option is for authorized support personnel only.

RPC-based Utilities
Hardware
This menu groups together many commands that are unique to the configuration or the current state of the controller and its environment. Main> h Hardware Menu: BBT - Show Bad Data Block Table Errors - Display Physical Drive Error Table Inventory - Show Information on Disk Drives Status - Show the Current Array Hardware Status Enable - Enable Automatic Fault Management Disable - Disable Automatic Fault Management Wide - Enable Wide SCSI Transfers Narrow - Disable Wide SCSI Transfers Pause - Enable Controller Pause During Boot Sequence No_Pause - Disable Controller Pause During Boot Sequence LCD_Clear - Clear the LCD Help - Display this menu ? - Display this menu Quit - Quit the Configuration Menu
BBT
A series of extremely unusual events can sometimes produce a small amount of unreliable data. In these scenarios, the MTI9000 array keeps track of any unreliable data the write-back bad block table or the bad data block table. These tables provide a LUN number, a logical block address, and a number of blocks that contain unreliable data. With this information, it is possible to determine the file (or files) in a file system that corresponds to the unreliable data. The LUN consistency check and disk drive rebuild process generate bad data block table entries. The write-back bad
RPC-based Utilities
block table keeps track of data in the write-back cache that could not be written to the disk drives. A bad block table read is a destructive read, e.g., a single bad data block table read will clear the information in the table kept by the array. Also, you should not read the bad block table while performing an initialization, consistency check, or rebuild. Hardware> bbt No bad blocks.
Errors
The MTI9000 Array stores error information for each disk drive. The array keeps an ongoing error count each classification for each disk drive and stores all counters in the Error Table. There are 4 classes of errors: parity, hard, soft, and miscellaneous: parity: The parity field counts the number of communication errors that occurred between the MTI9000 array controller and the disk drive. hardware: This field counts the number of hardware related errors experienced by the MTI9000 controller. soft: The soft field keeps a count of the number of recovered (via LUN redundancy) errors due to a bad sector on a disk drive. miscellaneous: The miscellaneous error category increments when a disk drive does not respond in time to a MTI9000 controller command or when an active disk drive is busy when the controller attempts to send it a command. An array power-cycle, reset (e.g., from a SCSI-bus reset), or new configuration procedure clears all the counters in the Error Table. Hardware> err Disk Error Stats: (Chn,Tgt) Soft Hard Parity Misc ( 0, 0) 0 0 0 0 ( 0, 1) 0 0 0 0 ( 0, 2) 0 0 0 0 ( 0, 3) 0 0 0 0 ( 1, 0) 0 0 0 0
RPC-based Utilities
( 1, 1) 0 0 0 0 ( 1, 2) 0 0 0 0 ( 1, 3) 0 0 0 0
Inventory
This menu option reports vital statistics for all disk drives within the array. This information is essential to have on hand when calling in a problem to technical support. It is possible to have drives of various firmware levels as long as the firmware levels are on the qualified list. Hardware> in MTI DAS9000 Revision 0141 Disk Inventory: (Chn,Tgt) Manufacturer Model Number Rev. Serial Number Sectors ( 0, 0) SEAGATE ST15150W 0017 00469361 8388314 ( 0, 1) SEAGATE ST15150W 0017 00459183 8388314 ( 0, 2) SEAGATE ST15150W 0017 00479524 8388314 ( 0, 3) SEAGATE ST15150W 0017 00480357 8388314 ( 1, 0) SEAGATE ST15150W 0017 00476434 8388314 ( 1, 1) SEAGATE ST15150W 0017 00478512 8388314 ( 1, 2) SEAGATE ST15150W 0017 00452135 8388314 ( 1, 3) SEAGATE ST15150W 0017 00476470 8388314
Status
This menu option reports the environmental status of the cabinet as well as host channel configuration parameters. If the Temperature is above 45 degrees Centigrade inside the cabinet, the it is considered Not OK. If a one of the power supplies has failed or a fan has failed then that indicates Not OK status as well. Automatic Fault Management should ALWAYS be enabled for model 9200 and 9500 arrays. Only model 9100 arrays require that this parameter be disabled. SCSI transfer mode should always be Wide except for abnormal or troublesome configurations. This option governs
RPC-based Utilities
what capabilities are reported to the host. The Pause option should be enabled for HP installations. This is only absolutely essential for installations where the root volume is on the array. Hardware> st Cabinet Status: Temperature : OK Power Supply Status : OK Fan Status : OK Auto Fault Mgmt : Enabled (Default) SCSI transfer mode : Wide Pause option : Enabled (Default)
Enable
See section 3.2.2.4.11.4 - Status for details. Hardware> en Hardware> st Cabinet Status: Temperature : OK Power Supply Status : OK Fan Status : OK Auto Fault Mgmt : Enabled (Default) SCSI transfer mode : Wide (Default) Pause option : Enabled (Default)
Disable
See section 3.2.2.4.11.4 - Status for details.
RPC-based Utilities
Hardware> dis Hardware> st Cabinet Status: Temperature : OK Power Supply Status : OK Fan Status : OK Auto Fault Mgmt : Disabled SCSI transfer mode : Wide (Default) Pause option : Enabled (Default)
Wide
See section 3.2.2.4.11.4 - Status for details. Hardware> wi Hardware> st Cabinet Status: Temperature : OK Power Supply Status : OK Fan Status : OK Auto Fault Mgmt : Enabled (Default) SCSI transfer mode : Wide (Default) Pause option : Enabled (Default)
Narrow
See section 3.2.2.4.11.4 - Status for details. Hardware> narr
RPC-based Utilities
Hardware> st Cabinet Status: Temperature : OK Power Supply Status : OK Fan Status : OK Auto Fault Mgmt : Enabled (Default) SCSI transfer mode : Narrow Pause option : Enabled (Default)
Pause
See section 3.2.2.4.11.4 - Status for details. Hardware> pa Hardware> st Cabinet Status: Temperature : OK Power Supply Status : OK Fan Status : OK Auto Fault Mgmt : Enabled (Default) SCSI transfer mode : Wide (Default) Pause option : Enabled (Default)
No_Pause
See section 3.2.2.4.11.4 - Status for details. Hardware> no Hardware> st
RPC-based Utilities
Cabinet Status: Temperature : OK Power Supply Status : OK Fan Status : OK Auto Fault Mgmt : Enabled (Default) SCSI transfer mode : Wide (Default) Pause option : Disabled
LCD_Clear
This menu option will clear the LCD panel. This operation does not effect the performance or configuration of the array, but is useful for clearing up the LCD panel. Hardware> lcd
Download
This menu option is for downloading new firmware to the array controller. Make sure that the array is not in use before selecting this option. This means unmounting any file systems and turning off all daemons. It is a good idea to "save" the configuration of the array before downloading new firmware. The "save" option is under the "configuration" submenu. The controller will accept the new firmware into memory and perform checksum calculations before re-programming itself. This helps ensure that the corrupted firmware will not ruin the controller. It is necessary to reset the SCSI bus(by rebooting) or power-cycle the array before the new firmware takes effect. Main> download Before downloading microcode to the array, be sure that any filesystems on the array have been umounted from the system. Downloading may cause the loss of configuration data. Are you sure that you want to continue? (y/n)> y
RPC-based Utilities
Enter the name of the file containing the firmware to be downloaded to the array controller. > /mtifw.141 About to download /mtifw.141 to the array. Continue? (y/n)> y Download Complete. Reset or power-cycle the array to run the new firmware.
RPC Client: das_monitor

Usage: das_monitor [-h server] -h: the hostname of the machine running the das_svrd RPC server If -h is not specified, the local machine is assumed das_monitor is arguably the most important utility of the suite of management software. This RPC client polls the status of the disk array every 10 seconds. If any state change has been recorded by the disk array, das_monitor records it and sends a message to the syslogd daemon. The syslogd daemon is a standard UNIX mechanism for routing messages to standard log files. das_monitor can be invoked by a privileged user as follows: # <BASEDIR>/das_monitor -h <host where array is attached> The das_monitor process daemonizes itself and runs as a background process which reports errors and changes of state to syslogd. If no arguments are included when das_monitor is invoked, then it will automatically monitor all locally attached Series 9000 Disk Arrays. Refer to section 5 - Monitoring Array Events, for information about what to do when events are logged. Starting and Stopping das_monitor If the software is installed properly, das_monitor will startup automatically each time the system boots. This is accomplished by invoking a script called das_mon. This invocation is caused by the automatic daemon startup mechanism for your system(see Table 3-2 below). CPU Vendor/ OS Revision Mechanism Sun Solaris 1.x(SunOS 4.1.3) local Automatic Daemon Startup An entry is added to the /etc/rc. file.
RPC-based Utilities
Sun Solaris 2.x(SunOS 5.x) in e.
A link to the das_mon script is put /etc/rc2.d. (i.
/etc/rc2.d/S77das_mon > /usr/sbin/ das_mon). SGI IRIX in e. /etc/rc2.d/S77das_mon > /usr/sbin/ das_mon). IBM AIX inittab HP HP-UX inittab DEC Digital UNIX(OSF) inittab An entry is added to the /etc/ file. An entry is added to the /etc/ file. An entry is added to the /etc/ file. A link to the das_mon script is put /etc/rc2.d. (i.
Table 3-4 das_mon takes a single argument. The value for the argument is either "start" or "stop". To start the RPC client das_monitor, simply execute # <BASEDIR>/das_mon start By default, monitoring will begin of all locally attached arrays. If arrays on other machines need to be monitored, simply edit the das_mon script accordingly. To stop all das_monitor processes: # <BASEDIR>/das_mon stop
RPC Client: das_check

Usage: das_check [-a array] [-h host] [-d drive] [-r] [-l logfile] -a: array device to check
RPC-based Utilities
-h: hostname of the machine running the das_svrd RPC server -d: Logical Unit Number (LUN) to check (0 - 7) -r: restore redundancy info -l: log to logfile instead of syslog Before all of the benefits of das_check are discussed, it is important to point out that MTI strongly recommends to run this utility periodically. Host I/O can complete while the das_check is running, but it will be slower than normal. With this in mind, it is good idea to find a time of day at least once a week when host I/O is at a low point. The process usually takes about 1 hour per 30GB of disk space. das_check has been developed as a tool to help surface bad blocks within the array. This utility methodically recalculates the parity block for every stripe of data within the array. For every stripe, the recalculated parity is compared with the stored parity. Errors are reported to the system console and the appropriate logs via syslogd. A more important benefit of das_check is that this process effectively scrubs the array for bad blocks by reading every addressable data block and parity block. If a bad block is encountered, it can be dealt with before the array already has another single-point-of-failure, like a dead disk drive. For example, if a bad block is encountered before a disk drive fails, it can be simply remapped to a good section and the data can be rebuilt using the parity block and the other data blocks in the stripe. Refer to Figure 3-3 and Figure 3-4 for graphical representations of common scenarios that are proactively avoided with das_check.
das_check is an effective pro-active tool to help prevent the above scenario. Figure 3-3
RPC-based Utilities
das_check is an effective pro-active tool to help prevent the above scenario. Figure 3-4 If das_check is started with no arguments, then checks will be started on all arrays that are locally attached. However, this can be overrode with the -a option. When the -a flag is set, then only the array device specified after the flag will be checked. Note: It is not valid to perform a consistency check that already has a single-point-of-failure such as a DEAD DISK The -h flag is the host where the DAS 9000 arrays in question reside. When no remote host is specified, the default is the local system. Remote hosts must be specified by the -h flag. Only one host may be designated by each das_check command. To specify a certain LUN to check, use the -d flag. The default is to check all LUNs. To report status information to a file instead of the syslogd daemon, use the -l flag, followed by the file you wish to output to. To log das_check information to stdout, just type stdout instead of a file name. What happens if data is found to be inconsistent? If das_check sends data inconsistency messages to the system error logs, then the parity can be rebuilt by using the -r option. The default is to not update parity, but rather report when parity does not match data. Example: This is the output when the das_check client discovers incorrect parity information. # <BASEDIR>/das_check -a /dev/rdsk/c410d6s0 -h lumpy -d 2 -r -l stdout Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2 started Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2 0% complete Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2 43% complete
RPC-based Utilities
Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2 86% complete Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2: data inconsistencies found No bad blocks. The DAS 9000 LCD will also show a message: CHK FAILED CODE: #2. The reasons that parity data may be incorrect includes, but is not limited to, improper initialization of the DAS 9000, or unexpected shutdown of the disk array. In any event, incorrect parity data constitutes a point of failure. If this situation continues uncollected, it would result in a loss of any data on the same stripe as the bad parity, if a physical disk drive should fail. Therefore, it is vital that das_check is run regularly, and if data inconsistencies are found, execute das_check with the -r flag. As noted above, the -r flag will recalculate and restore parity if necessary. So the next time we perform the media integrity test, the results should look like this: #/das_check -a /dev/rdsk/c410d6s0 -h lumpy -d 2 -r -l stdout Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2 started Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2 0% complete Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2 43% complete Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2 86% complete Consistency Check on lumpy array /dev/rdsk/c410d6s0, drive 2 completed Notice the data inconsistencies have been eradicated, and, should a physical disk drive fail, data integrity would be maintained. /a>
Configuring the Array
Configuring the Array The Series 9000 disk array ships with a utility program called das_mgr. This program allows the system administrator to configure the storage on individual disk arrays, view the array status and perform other miscellaneous tasks.
To view or change the configuration and status of the array, you should enter the configuration menu. To do this, type "configure" at the prompt (unambiguous abbreviations are acceptable). The example below shows how to use the "get" command from within the configuration menu to see the current configuration and status of the array. # das_mgr Main Menu: Select - Select an array/lun Current - Show the current array/lun Configure - Change/Show the configuration Initialize - Initialize the Redundancy Information Check - Check the Redundancy Information Restore - Check and Restore the Redundancy Information Rebuild - Rebuild Data on a Replaced Disk Unit Progress - Report Rebuild Status Start - Start a Replaced Disk Unit as a Spare Stop - Stop a Disk Unit
http://www-personal.umich.edu/~rak/9k_manual/9kconfig.html (1 of 25)18-Feb-08 11:30:10 AM
Hardware - Get information on array hardware Download - Download Microcode to the Array Controller Help - Display this menu ? - Display this menu Quit - Quit the maintenance Utility Main> con Configuration Menu: Get - Get the Current Configuration from the Array Show - Show the Working Configuration Detail - Show Detailed Working Configuration Edit - Edit the Working Configuration New - Create a New Configuration (Old data will be lost) Set - Set the Array's Config to the Working Config Clear - Clear the Array's Configuration Save - Save the Working Configuration to a File Load - Load the Working Configuration from a File Salvage - Attempt to force a drive to its configured state Help - Display this menu ? - Display this menu Quit - Quit the Configuration Menu Configuration> get
Reading Configuration from NVRAM... Configuration Read Successful. Displaying Current Working Configuration: LUN 0: Status Online; Capacity 12282 MB; RAID 5; Write-Back Enabled Disk Configuration: Configured Current Channel Target State State Sectors MBytes 0 0 Online Online 4192256 2047 0 1 Online Online 4192256 2047 0 2 Online Online 4192256 2047 0 3 Online Online 4192256 2047 1 0 Online Online 4192256 2047 1 1 Online Online 4192256 2047 1 2 Online Online 4192256 2047 Striping optimized for random I/O Configuration> It is also possible to get information about the serial numbers and revisions of the hardware. An example of this is shown below. Main> h Hardware Menu: BBT - Show Bad Data Block Table Errors - Display Physical Drive Error Table
Inventory - Show Information on Disk Drives Spares - Show Sparing Table Status - Show the Current Array Hardware Status Enable - Enable Automatic Fault Management Disable - Disable Automatic Fault Management Wide - Enable Wide SCSI Transfers Narrow - Disable Wide SCSI Transfers Pause - Enable Controller Pause During Boot Sequence No_Pause - Disable Controller Pause During Boot Sequence LCD_Clear - Clear the LCD Help - Display this menu ? - Display this menu Quit - Quit the Configuration Menu Hardware> i MTI DAS9000 Revision 0141 Disk Inventory: (Chn,Tgt) Manufacturer Model Number Rev. Serial Number Sectors ( 0, 0) SEAGATE ST32550N 0014 00086474 4194057 ( 0, 1) SEAGATE ST32550N 0014 00077425 4194057 ( 0, 2) SEAGATE ST32550N 0014 00077560 4194057 ( 0, 3) SEAGATE ST32550W 0007 00027129 4194057
( 1, 0) SEAGATE ST32550N 0014 00040295 4194057 ( 1, 1) SEAGATE ST32550N 0014 00053084 4194057 ( 1, 2) SEAGATE ST32550N 0014 00040058 4194057 Hardware>
About the Array's Logical Configuration

The Series 9000 disk array allows for flexible allocation of storage to SCSI Logical Unit Numbers (LUNs). Each LUN within the array appears to the host to be a separate SCSI disk drive. SCSI specifies a maximum of eight LUNs, numbered 0 through 7, on a SCSI target. Understanding LUN configuration is key to proper installation of the array.
Rules for Setting up a New Configuration

The default recommended configuration varies by the type of host and operating system. In a nutshell, three decisions must be made. First, evaluate whether it is appropriate to have a hot spare configured for your system. Second, the number and size of LUNs must be determined. Third, decide if write-back caching should be enabled. Finally, it must be decided if the array should be optimized for sequential or random operation. PLATFORM RECOMMENDED HP 9000 800 running Sequential HP/UX 9.0.4 (All capacity systems require spt1.) RECOMMENDED CONFIGURATION of LUNs OPTIMIZATION LUN 0 = 1 MB LUN 1 = Rest of available
2.3.1HP 800 - Prepare HP-UX for Series 9000 Software HP 9000 800 running Sequential HP/UX 10.x (spt capacity required1) HP 9000 800 running Sequential LUN 0 = 1 MB LUN 1 = Rest of available
LUN 0 = All available capacity
HP/UX 10.x (spt NOT required1) HP 9000 700 running Random HP/UX 9.0.5 MB MB
LUN 0 = no greater than 4000 MB LUN 1 = no greater than 4000 LUN 2 = no greater than 4000 LUN 3 = no greater than 4000
MB LUN 4 = no greater than 4000 MB LUN 5 = no greater than 4000 MB LUN 6 = no greater than 4000 MB LUN 7 = no greater than 4000 MB IBM RS/6000 running Random AIX 3.2.5 or 4.x MB SGI running IRIX 5.x Sequential or 6. x SUN running Solaris Random 2.x(SunOS 5. x) SUN running SunOS Random 4.1.x Total Total Capacity / 8 LUN 4 = Total Capacity / 8 LUN 5 = Total Capacity / 8 LUN 6 = Total Capacity / 8 LUN 7 = Total
LUN 0 = Rest of available capacity LUN 1 = 1 LUN 0 = Total Capacity
LUN 0 = Total Capacity
LUN 0 = Total Capacity / 8 LUN 1 = Total Capacity / 8 LUN 2 = Capacity / 8 LUN 3 =
Capacity / 8 DEC running Digital Random UNIX LUN 0 = Total Capacity
Table 4-5 As shown in Table 4-5, each system has unique configuration requirements. Below is a brief discussion of these requirements and their implications. HP 9000 800 systems running HP/UX 9.0.4 (All systems require spt1.) use LUN 0 as a communication volume for the Series 9000 management and monitoring software. Therefore, it is preferable to make it as small as possible. It is recommended to just use LUN 1 as the volume to refer to the rest of the available storage. HP's Logical Volume Manager(lvm) is used to break the large LUN into >4 GB sections that can be used for HFS file systems. Note: HP/UX 10.x doesn't support hard partitioning. So if you are not currently using lvm, you now have a reason to learn it. HP 9000 800 systems running HP/UX 10.x (spt required[2] 2.3.1HP 800 - Prepare HP-UX for Series 9000 Software ) use LUN 0 as a communication volume for the Series 9000 management and monitoring software. Therefore, it is preferable to make it as small as possible. It is recommended to just use LUN 1 as the volume to refer to the rest of the available storage. HP's Logical Volume Manager(lvm) is used to break the large LUN into >4 GB sections that can be used for HFS file systems. Note: HP/UX 10.x doesn't support hard partitioning. HP 9000 800 systems running HP/UX 10.x (spt NOT required1) use LUN 0 for everything: data access volume and communication volume for the Series 9000 management and monitoring software. HP's Logical Volume Manager(lvm) is used to break the large LUN into >4 GB sections that can be used for HFS file systems. Note: HP/UX 10.x doesn't support hard partitioning. HP 9000 700 systems running HP/UX 9.0.5 require that a volume be no larger than 4 GB. Therefore, the Series 9000 array has to be setup with many LUNs, each LUN never exceeding 4 GB(about 4000MB). Note: Contrary to what would be a logical deduction, it is not possible to build a filesystem on a volume 4096MB in size. IBM RS/6000 systems running AIX 3.2.5 or 4.x use LUN 1 as a communication volume for the Series 9000 management and monitoring software. Therefore, it is preferable to make it as small as possible. It is recommended to just use LUN 0 as the volume to refer to the rest of the available storage. IBM's Logical Volume Manager is used to break the large LUN into >2 GB sections for AIX 3.2.5 systems or >64 GB sections for AIX 4.x systems. SGI systems running IRIX 5.x or 6.x systems, for the most part, do not support LUNs. Therefore, the entire available capacity is configured for LUN 0.
SUN systems running Solaris 2.x(SunOS 5.x) support LUNs, but the /kernel/drv/sd.conf file needs to be edited. From a performance and management perspective it is better to configure the entire available capacity for LUN 0. SUN systems running SunOS 4.1.x do not support tagged-command queuing. This means that only a single command can be pending on the array at any one time. This is opposed to a Solaris 2.x system which can queue up 64 commands on the array. Since each target/LUN combination is treated as a unique device that can have a single command pending, best performance for random I/O is attained by breaking the array into the maximum number of LUNs according to the SCSI specification: 8. DEC systems running Digital UNIX support LUNs, but they are difficult to configure. If multiple LUNs are desired, then refer to RAID(7) and rz(7). From a performance and management perspective it is better to configure the entire available capacity for LUN 0.
New Configuration Options to Consider

The Series 9000 array does not require much tuning due to its read and write caching algorithms. However, there are some options to consider when setting up a new configuration. These options including the choice between having a hot spare or no hot spare, the size of each LUN, and the type of striping optimization to perform. Below, a brief discussion of each issue should give you some insight to what the optimum options are for your site. If you have any further questions or need additional help, please call technical support.
Hot Spare
A hot spare is a drive that is kept out of the online configuration for emergency purposes. The drive is constantly spinning and is utilized as an immediate replacement for a drive that fails out of the online configuration. When a drive fails, the array is in degraded mode. Since RAID 5 only protects from a single disk failure, a second disk failure before the first disk is rebuilt will result in data loss. If a hot spare is configured, then the time spent in degraded mode when a disk fails is minimized to the time that it takes to rebuild a disk. An Example of When a Hot Spare is Necessary The modularity of the Series 9000 array often results in the array being installed in office environments instead of manned computer rooms. In these office environments, it is common for the array to be unattended for hours or days at a time. The potential of leaving an array in degraded mode for extended periods of time is often enough of a case for justifying a hot spare. An Example of When a Hot Spare is Not Necessary Due to the excellent reporting mechanism employed by the Series 9000 array, it is very possible that an administrator will be notified within minutes of a disk failure. Coupled with a 7x24 manned computer room,
the time it takes between the disk failure and the insertion of the new disk may very short(i.e. within a half hour). In this situation, it is probably better to take advantage of the extra storage and performance of having all of the disks part of the online configuration.
LUN Sizing
Each configured LUN on an array is a slice of storage that will look like a disk drive to the host. While adhering to the rules stated in Table 4-5, it is advisable to configure the least number of LUNs possible. This is simply because it is operationally easier to maintain and balance the load across fewer "disks". For example, it is advised to always configure arrays being attached to Sun Solaris 2.x machines to be a single large LUN. On Solaris 2.x, the single large LUN can be used to accommodate a single large file system that mounts to a single mount point. Conversely, if the same array is split it up into 8 LUNs, then a minimum of 8 filesystems will have to be created. The 8 filesystems will, in turn, have to be mounted to 8 unique mount points. Finally, the administrator will have to balance the capacity/performance load across the 8 distinct volumes.
Write-Back Caching
Write-back caching means that the controller will signal an I/O completion when the data from the host is safe in the controller cache, but before the data is written to the underlying disk drives. This is done solely for performance reasons; leaving the data in the cache allows the controller to perform optimizations over time. Every 3 seconds the controller makes sure that all data in the cache is synchronized with the disk drives. However, the data will continue to live in the cache until its cache line is replaced on an LRU(leastrecently-used) basis. The obvious danger of write-back caching is that a power loss will cause permanent data loss of write data that had not yet been written to disk. Since the host believes that the data has been written, there is no guarantee that the effected files will be detectable with fsck. Protection against the above scenario starts with having a UPS. Preferably, each of the arrays redundant power supplies can take power from a different UPS. Finally, a constantly charged battery that is installed on the controller will send refresh signals to the 16MB DRAM SIMM for 6 hours; if the array is powered off with live data in cache and powered back on within 6 hours, then the live data will be written to disk before any host I/O can complete.
Striping Optimization
While developing a new configuration, it must be decided whether to optimize for sequential or random I/O. If sequential I/O is selected, then a 64k internal stripe depth is selected for the array. Otherwise, an 8k internal stripe depth is selected. The basic goal is to select a stripe depth that is close to, but not less than, the average request size. Refer to Table 4-5 for general recommendations on a per platform basis.
Due to the caching algorithms of the Series 9000 controller, it is usually not necessary to choose a stripe depth other than 8k or 64k. However, if it becomes necessary, use the Series 9000 GUI to develop the configuration. For example, Table 4-5 recommends that a sequential optimization be selected for HP 9000 model 800 systems. However, these systems perform alot of random I/O. The reason behind the recommendation is that the recommended file system block size is 64k, which provides a very balanced random vs. sequential performance profile.
Steps for Setting up a New Configuration

Below are the steps that should be followed for setting up a new configuration on the array: * Make whatever preparations are necessary to erase the array. If the array is new and has never been used, then there are no preparations. However, if there is data on the array, make sure that backups have been made, since the new initialization will erase the current contents of the array. * Invoke the das_mgr utility * Type configure at the "Main>" prompt * Type new at the "Configuration>" prompt to build a new working configuration. * At each "Do you wish to continue (y/n)>" prompt, type yes. * At the "Do you want to configure a spare disk? (y/n)>" prompt, type yes if a hot spare if required for your site. See section 4.3.1 - Hot Spare, for help in deciding whether a hot spare is necessary for your site or not. * At the "Configuring LUN X: Enter Capacity in MB [YY]:" prompt, type in the number of megabytes that the LUN should be. See Table 4-5 for information about the size of each LUN that should be configured for your platform. See section 4.3.2 - LUN Sizing for a further advise. * At the "Use Write-Back Cache for this LUN? (y/n)>", type yes if your system is on a UPS or the controller has a battery backed up cache. See section 4.3.3 - Write-Back Caching for an explanation of this topic. * At the "Optimize for random('r') or sequential('s') I/O?[r]" prompt, type in the appropriate letter for the type of optimization that should be done for this system. See Table 4-5 for a recommended default optimization for your platform. Additionally, see section 4.3.4 - Striping Optimization. * Type set at the "Configuration>" prompt to write the working configuration to the array.
* Type get at the "Configuration>" prompt to read back the configuration from the array. * Compare the retrieved configuration against the desired configuration. If it looks good, goto to the next step. * Type save at the "Configuration>" prompt to save the configuration to a UNIX file. * Save the configuration to a file in a filesystem that is backed up. This file will become necessary if the array controller fails or if the drives are moved to a different chassis. * Type quit at the "Configuration>" prompt to return to the main menu. * Type init at the "Main>" prompt to initialize a LUN. * Methodically select each LUN that was configured in the previous steps. Valid LUNs range from 0 through 7. * When all of the LUNs have been initialized, it is safe to use the array.
EXAMPLE CONFIGURATION: LUN 0 = 1MB, LUN 1 = Rest of Capacity

This section describes the steps to be taken to configure the array for 2 LUNs where LUN 0 is 1 MB and LUN 1 is balance of the available capacity. This a common setup for HP systems running HP/UX 9.0.4 or HP/UX 10.x when spt is Required. This shows an array with six 9 gigabyte drives. A hot spare is required in this example. Additionally, the setup for this platform requires LUN 0 to be 1MB and LUN 1 to be the remainder of the available storage. Configuration> new Warning: This will create a new configuration. Any data on the array will be lost. Do you wish to continue (y/n)> y Warning: This will immediately make all storage on the array inaccessible. Continuing will take the array offline now.
Do you still wish to continue? (y/n)> y Searching for Drives... Checking target 0, channel 0... Found a SEAGATE ST32550N Revision 0014 Serial # 00086474 Capacity 4192256 sectors. Checking target 0, channel 1... Found a SEAGATE ST32550N Revision 0014 Serial # 00040295 Capacity 4192256 sectors. Checking target 1, channel 0... Found a SEAGATE ST32550N Revision 0014 Serial # 00077425 Capacity 4192256 sectors. Checking target 1, channel 1... Found a SEAGATE ST32550N Revision 0014 Serial # 00053084 Capacity 4192256 sectors. Checking target 2, channel 0... Found a SEAGATE ST32550N Revision 0014 Serial # 00077560 Capacity 4192256 sectors. Checking target 2, channel 1... Found a SEAGATE ST32550N Revision 0014 Serial # 00040058 Capacity 4192256 sectors. Checking target 3, channel 0...
Found a SEAGATE ST32550W Revision 0007 Serial # 00027129 Capacity 4192256 sectors. Checking target 3, channel 1... No device found Checking target 4, channel 0... No device found Checking target 4, channel 1... No device found Checking target 5, channel 0... No device found Checking target 5, channel 1... No device found Checking target 6, channel 0... No device found Checking target 6, channel 1... No device found Found a total of 7 disks. Do you want to configure a spare disk? (y/n)> y Total capacity available is 10235 MB. Configuring LUN 0: Enter Capacity in MB [10235]: 1 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 1: Enter Capacity in MB [10234]: Use Write-Back Cache for this LUN? (y/n)> y Optimize for random('r') or sequential('s') I/O?[r] s Configuring 2 LUNs, leaving 0 MB free. Configuration> set Do you really want to write the working configuration to the array? (Any data on the array will be lost) (y/n)> y
Writing Configuration to the array... Set Configuration Successful. Configuration> get Reading Configuration from NVRAM... Configuration Read Successful. Displaying Current Working Configuration: LUN 0: Status Online; Capacity 1 MB; RAID 5; Write-Back Enabled LUN 1: Status Online; Capacity 10234 MB; RAID 5; Write-Back Enabled Disk Configuration: Configured Current Channel Target State State Sectors MBytes 0 0 Online Online 4192256 2047 0 1 Online Online 4192256 2047 0 2 Online Online 4192256 2047 0 3 Spare Spare 4192256 2047 1 0 Online Online 4192256 2047 1 1 Online Online 4192256 2047 1 2 Online Online 4192256 2047 Striping optimized for sequential I/O Configuration> save Enter the filename to which you will save the config.
> /usr/etc/das_config.rdrv3 Save Configuration Successful. Configuration> Goto section 4.5 - Initializing LUNs
EXAMPLE CONFIGURATION: LUN 0 = Total Available Capacity

This section describes the steps to be taken to configure the array for a single LUN 0. This a common setup for HP systems running HP/UX 10.x when spt is not Required, SUN systems running Solaris 2.x, SGI systems running IRIX 5.x or 6.x. Configuration> new Warning: This will create a new configuration. Any data on the array will be lost. Do you wish to continue (y/n)> y Warning: This will immediately make all storage on the array inaccessible. Continuing will take the array offline now. Do you still wish to continue? (y/n)> y Searching for Drives... Checking target 0, channel 0... Found a SEAGATE ST32550N Revision 0014 Serial # 00086474 Capacity 4192256 sectors. Checking target 0, channel 1... Found a SEAGATE ST32550N Revision 0014
Serial # 00040295 Capacity 4192256 sectors. Checking target 1, channel 0... Found a SEAGATE ST32550N Revision 0014 Serial # 00077425 Capacity 4192256 sectors. Checking target 1, channel 1... Found a SEAGATE ST32550N Revision 0014 Serial # 00053084 Capacity 4192256 sectors. Checking target 2, channel 0... Found a SEAGATE ST32550N Revision 0014 Serial # 00077560 Capacity 4192256 sectors. Checking target 2, channel 1... Found a SEAGATE ST32550N Revision 0014 Serial # 00040058 Capacity 4192256 sectors. Checking target 3, channel 0... Found a SEAGATE ST32550W Revision 0007 Serial # 00027129 Capacity 4192256 sectors. Checking target 3, channel 1... No device found Checking target 4, channel 0... No device found Checking target 4, channel 1... No device found Checking target 5, channel 0... No device found Checking target 5, channel 1... No device found
Checking target 6, channel 0... No device found Checking target 6, channel 1... No device found Found a total of 7 disks. Do you want to configure a spare disk? (y/n)> n Total capacity available is 12282 MB. Configuring LUN 0: Enter Capacity in MB [12282]: Use Write-Back Cache for this LUN? (y/n)> y Optimize for random('r') or sequential('s') I/O?[r] s Configuring 1 LUNs, leaving 0 MB free. Configuration> set Do you really want to write the working configuration to the array? (Any data on the array will be lost) (y/n)> y Writing Configuration to the array... Set Configuration Successful. Configuration> get Reading Configuration from NVRAM... Configuration Read Successful. Displaying Current Working Configuration: LUN 0: Status Online; Capacity 12282 MB; RAID 5; Write-Back Enabled Disk Configuration: Configured Current
Channel Target State State Sectors MBytes 0 0 Online Online 4192256 2047 0 1 Online Online 4192256 2047 0 2 Online Online 4192256 2047 0 3 Online Online 4192256 2047 1 0 Online Online 4192256 2047 1 1 Online Online 4192256 2047 1 2 Online Online 4192256 2047 Striping optimized for sequential I/O Configuration> save Enter the filename to which you will save the config. > /usr/etc/das_config.rdrv3 Save Configuration Successful. Configuration> Goto section 4.5 - Initializing LUNs
EXAMPLE CONFIGURATION: All LUNs less than 4 GB

This section describes the steps to be taken to configure the array for multiple LUNs while keeping the size of each LUN less than 4 GB. This is a common setup for HP 9000 Series 700 systems running HP/UX 9.05. # das_mgr Main Menu: Select - Select an array/lun Current - Show the current array/lun
Configure - Change/Show the configuration Initialize - Initialize the Redundancy Information Check - Check the Redundancy Information Restore - Check and Restore the Redundancy Information Rebuild - Rebuild Data on a Replaced Disk Unit Progress - Report Rebuild Status Start - Start a Replaced Disk Unit as a Spare Stop - Stop a Disk Unit Hardware - Get information on array hardware Download - Download Microcode to the Array Controller Help - Display this menu ? - Display this menu Quit - Quit the maintenance Utility Main> con Configuration Menu: Get - Get the Current Configuration from the Array Show - Show the Working Configuration Detail - Show Detailed Working Configuration Edit - Edit the Working Configuration New - Create a New Configuration (Old data will be lost) Set - Set the Array's Config to the Working Config
Clear - Clear the Array's Configuration Save - Save the Working Configuration to a File Load - Load the Working Configuration from a File Salvage - Attempt to force a drive to its configured state Help - Display this menu ? - Display this menu Quit - Quit the Configuration Menu Configuration> new Warning: This will create a new configuration. Any data on the array will be lost. Do you wish to continue (y/n)> y Warning: This will immediately make all storage on the array inaccessible. Continuing will take the array offline now. Do you still wish to continue? (y/n)> y Searching for Drives... Checking target 0, channel 0... Found a SEAGATE ST15150W Revision 0017 Serial # 00469361 Capacity 8386560 sectors. Checking target 0, channel 1... Found a SEAGATE ST15150W Revision 0017
Serial # 00476434 Capacity 8386560 sectors. Checking target 1, channel 0... Found a SEAGATE ST15150W Revision 0017 Serial # 00459183 Capacity 8386560 sectors. Checking target 1, channel 1... Found a SEAGATE ST15150W Revision 0017 Serial # 00478512 Capacity 8386560 sectors. Checking target 2, channel 0... Found a SEAGATE ST15150W Revision 0017 Serial # 00479524 Capacity 8386560 sectors. Checking target 2, channel 1... Found a SEAGATE ST15150W Revision 0017 Serial # 00452135 Capacity 8386560 sectors. Checking target 3, channel 0... Found a SEAGATE ST15150W Revision 0017 Serial # 00480357 Capacity 8386560 sectors. Checking target 3, channel 1... Found a SEAGATE ST15150W Revision 0017 Serial # 00476470 Capacity 8386560 sectors. Checking target 4, channel 0... No device found Checking target 4, channel 1... No device found
Checking target 5, channel 0... No device found Checking target 5, channel 1... No device found Checking target 6, channel 0... No device found Checking target 6, channel 1... No device found Found a total of 8 disks. Do you want to configure a spare disk? (y/n)> y Total capacity available is 24570 MB. Configuring LUN 0: Enter Capacity in MB [24570]: 4096 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 1: Enter Capacity in MB [20474]: 4096 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 2: Enter Capacity in MB [16378]: 4096 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 3: Enter Capacity in MB [12282]: 4096 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 4: Enter Capacity in MB [8186]: 4096 Use Write-Back Cache for this LUN? (y/n)> y Configuring LUN 5: Enter Capacity in MB [4090]: 4096 Maximum capacity is 4090 MB. Enter Capacity in MB [4090]: y Use Write-Back Cache for this LUN? (y/n)> y
Optimize for random('r') or sequential('s') I/O?[r] r Configuring 6 LUNs, leaving 0 MB free. Configuration> set Do you really want to write the working configuration to the array? (Any data on the array will be lost) (y/n)> y Writing Configuration to the array... Set Configuration Successful. Configuration> get Reading Configuration from NVRAM... Configuration Read Successful. Displaying Current Working Configuration: LUN 0: Status Online; Capacity 4096 MB; RAID 5; Write-Back Enabled LUN 1: Status Online; Capacity 4096 MB; RAID 5; Write-Back Enabled LUN 2: Status Online; Capacity 4096 MB; RAID 5; Write-Back Enabled LUN 3: Status Online; Capacity 4096 MB; RAID 5; Write-Back Enabled LUN 4: Status Online; Capacity 4096 MB; RAID 5; Write-Back Enabled LUN 5: Status Online; Capacity 4090 MB; RAID 5; Write-Back Enabled Disk Configuration: Configured Current Channel Target State State Sectors MBytes 0 0 Online Online 8386560 4095
0 1 Online Online 8386560 4095 0 2 Online Online 8386560 4095 0 3 Online Online 8386560 4095 1 0 Online Online 8386560 4095 1 1 Online Online 8386560 4095 1 2 Online Online 8386560 4095 1 3 Spare Spare 8386560 4095 Striping optimized for random I/O Configuration> save Enter the filename to which you will save the config. > /config.c410d6 Save Configuration Successful. Configuration>q
Initializing LUNs/a>
Each LUN within the array must be initialized. This operation is analogous to formatting a disk drive. All data on a LUN is lost when that LUN is initialized. To do this, use the initialize command as shown here. The command will notify you of its progress. The following steps must be taken: * Type init in the main menu. * Type 0 for the LUN to be initialized. * Repeat the above steps for each of the configured LUNs. WARNING: The current version of the utility will let you use LUNs without initializing them. Using the array to store data without initializing new LUNs can cause data corruption after a disk drive failure. Always
initialize new LUNs. MTI can not guarantee proper operation of the array if the LUNs have not been initialized. Here is an initialization example of an array with 2 configured LUNs: 0 & 1. Main> init Enter a system disk/lun (0-7):0 Ready to initialize the lun. This will destroy all data on this lun. This takes a long time and cannot be interrupted. OK to continue? (y/n)> y Initialization 100% Complete Done Main> init Enter a system disk/lun (0-7):1 Ready to initialize the lun. This will destroy all data on this lun. This takes a long time and cannot be interrupted. OK to continue? (y/n)> y Initialization 100% Complete Done Main>/a>
Monitoring Array Events
Monitoring Array Events Array events are reported to the host syslogd (1m) facility via the das_monitor daemon. See section 3.2.3 - RPC Client: das_monitor, for information about starting up the das_monitor process.
The das_monitor process polls each array for every ten seconds for information about the environment of the array. If any of the following scenarios is recognized, an event is logged to the syslogd daemon. * A disk drive changes state(i.e. REBUILDING to ONLINE). * A LUN changes state(i.e. ONLINE to DEGRADED). * The daemon starts and the current state of the array does not match the configured state. * There is change in the status of fans, power supplies or cabinet temperature(i.e. NotOK to OK). * The monitoring daemon is terminated. * A consistency check process is toggled to update status or finds an inconsistency. Once a message is sent to the standard UNIX syslogd daemon, it is up to that process to decide where to log it. This routing of information is governed by the /etc/syslog.conf file, which is read by the syslogd daemon when it is started up. The normal setup for syslogd is to log the error levels that are used by das_monitor in at least 2 locations: the system console and a standard error log file. The standard error log file is different for every host platform. See Table 5-1 for the location of the standard error log file for your system. PLATFORM FILE HP HP/UX 9.0.4 & 10.0 syslog STANDARD ERROR LOG /usr/adm/
http://www-personal.umich.edu/~rak/9k_manual/9kmonitr.html (1 of 3)18-Feb-08 11:30:16 AM
SunOS 4.1.x messages Solaris 2.x messages IBM AIX 3.2.5 & 4.1 errlog SGI IRIX SYSLOG DEC Digital UNIX messages
/var/adm/ /var/adm/ /var/adm/ras/ /usr/adm/ /usr/var/adm/
Table 5-1 See Table 5-2 below for a graphical representation of the event logging mechanism.
das_monitor Reports to the Standard UNIX Reporting Mechanism - syslogd Table 5-2
Examining Events
Every message that ends up being displayed on the system console or is logged in the standard system
log file can be broken up into many important parts. This breakdown is graphically depicted in Table 53 below.
Breakdown of a Standard Error Message Table 5-3 See section 8 - Error Messages: Descriptions and Action Items , or a complete list of possible messages and the corresponding action items.
Making the Storage Available

HP HP-UX for Series 700 Machines
This section provides background and describes the usual steps taken to make new disk storage usable by the HP/UX filesystem. If you already are familiar with how disk storage is managed on HP/UX systems, you can skip this section.
Configuring HP-UX 9.0.4 for the New Storage

Setting Up LUN devices Most SCSI disk drives that are common on HP/UX systems have one SCSI target ID and one SCSI Logical Unit Number. The MTI Series 9000 disk array supports up to eight SCSI Logical Unit Numbers (LUNs) per array, while only using one SCSI target ID. This makes it possible to use up to 32 GB of storage at a single SCSI ID, by dividing the storage into eight SCSI Logical Units with 4 GB of capacity apiece.
Naming LUNs
Most SCSI disks are named cXdYs0, where X represents the controller number and Y represents the SCSI target ID of the disk drive. This notation does not support the concept of logical unit numbers. To use logical unit numbers, HP/ UX names devices in the form cXdYlZs0, where X is the controller number, Y is the SCSI ID and Z is the Logical Unit Number. For example, if we have an array with three 4 GB LUNs at SCSI target 0 on SCSI Controller 0x201, the device names for the LUNs are /dev/[r]dsk/c201d0s0[1], /dev/[r]dsk/c201d0l1s0 and /dev/[r]dsk/ c201d0l2s0. For additional information see the manual page for disks(7).
Creating LUN Device Nodes
To use the LUNs that are configured in the array, you need to create device node entries in the /dev directory for each of the LUNs that are configured. You create these device nodes using the mknod(1m) program. You will need to create both a block and a character (raw) device for each LUN that you configure. # /etc/mknod /dev/dsk/<devname> b <major#> <minor#> and # /etc/mknod /dev/rdsk/<devname> c <major#> <minor#> To determine the major and minor device numbers, look at the numbers already on your system for the disks that are attached. To do this, do an 'ls -l' in each of the /dev/rdsk and /dev/dsk directories. You will get information that looks like the following:
http://www-personal.umich.edu/~rak/9k_manual/9kavail.html (1 of 31)18-Feb-08 11:30:28 AM
crw-r----- 1 root sys 47 0x201600 May 26 14:15 c201d6s0 In this example, 47 is the major number, and 0x201600 is the minor number. The minor number is composed of the controller number (201), the SCSI ID (6), the LUN (0) and the partition (always 0 on 700 Series systems). Looking at the permissions, we see that this is a character (raw) device (the leading 'c'). An example of a matching block device is shown below. Block devices will have a leading 'b'. brw-r----- 1 root sys 7 0x201600 May 26 14:15 c201d6s0 To create device nodes for an array at SCSI ID 2, you could use the following commands: # mknod /dev/rdsk/c201d2s0 c 47 0x201200 # mknod /dev/rdsk/c201d2l1s0 c 47 0x201210 ...and for the block devices... # mknod /dev/dsk/c201d2s0 b 7 0x201200 # mknod /dev/dsk/c201d2l1s0 b 7 0x201210 These commands will create device nodes that look like this: crw-r----- 1 root sys 47 0x201200 Oct 25 21:37 /dev/rdsk/c201d2s0 crw-r----- 1 root sys 47 0x201210 Oct 27 23:58 /dev/rdsk/c201d2l1s0 brw-r----- 1 root sys 7 0x201200 Oct 25 21:37 /dev/dsk/c201d2s0 brw-r----- 1 root sys 7 0x201210 Oct 27 23:58 /dev/dsk/c201d2l1s0 Be sure to check that the permissions on the device are set as in the example above. The default is to leave the devices writable to all users, which leaves a gaping security hole. For more information, see the mknod(1m) manual page. Building Filesystems on the new LUNs If the new LUNs are to be used as standard UNIX filesystems, the final step of the installation is to build new filesystems on the luns that you have created. To do this, you will need to use both the diskinfo(1m) and the mkfs(1m) commands. First get the size of the array in 1K blocks by typing: # diskinfo -b /dev/rdsk/<diskname> This will return a number that you should use in the following command:
# mkfs /dev/rdsk/<diskname> <number-from-above> This will take a few minutes to complete. When the mkfs command is finished, you can mount the storage using the mount(1m) command and begin using the storage. You will need to build filesystems for each of the LUNs that you wish to use.
Configuring HP-UX 10.x for the New Storage

This section has not been completed yet. For general guidlines, see "HP HP-UX for Series 800 Machines: Configuring HP-UX 10.x for the New Storage".
HP HP-UX for Series 800 Machines

This section provides background and describes the usual steps taken to make new disk storage usable by the HP/UX filesystem. If you already are familiar with how disk storage is managed on HP/UX systems, you can skip this section.
Interfacing with the HP-UX Logical Volume Manager

This section provides background for installers who have little experience with the HP/UX Logical Volume Manager. If you already are familiar with how disk storage is managed on HP/UX systems, you can skip this section. Storage Hierarchy The Logical Volume Manager (LVM) controls all of the disk storage on your HP 9000 system. See the HP/UX System Administrator's Guide for details on LVM concepts and management utilities.
Configuration Illustration/a>
Below is an example of an LVM configuration that illustrates the concepts discussed in this section. You should refer to this diagram while you read about the LVM.
This is a graphical representation of an HP/UX storage hierarchy. This example is intended to illustrate several aspects of the rules for LVM configuration. Figure 6-1
Physical Volumes
The disk drives on an HP 9000 are known to HP/UX as physical volumes. Every hard disk on your system is a physical volume. Physical volumes are accessed by the system via device special files. The names of these device special files follow a common format but differ on various platform operating system revisions. Refer to Table 6-1 to find the device nomenclature on your machine. OS REVISION VOLUMES 9.0.x number 10.x Y LUN PATH TO PHYSICAL cXd0s2 cXtYdZ X = HP LU X = controller number Z = SCSI
= SCSI target
Table 6-1 Since the Series 9000 arrays are capable of being divided into a number of SCSI LUNs, each disk array can appear to the system as one or more devices. Each LUN will correspond to one device.
Volume Groups
Physical volumes belong to volume groups. Volume groups are collections of related disks. Every HP 9000 system already has one volume group called vg00. You can either add your new physical volume to vg00 or create a new volume group. Volume groups can be comprised of one or more physical volumes. However, due to the sheer capacity of the Series 9000 arrays, it is usually best to dedicate a volume group to a single array.
Logical Volumes
The next level in the HP/UX storage hierarchy is the logical volume. Logical volumes allow segmentation of the storage allocated in the volume group level. The logical volume must obtain its storage from one and only one volume group. A logical volume spread across multiple volume groups is not permitted. However, multiple logical volumes can be defined on a single volume group. Notice that creating multiple logical volumes on a volume group containing a single physical volume is analogous to partitioning a single disk. If an application accesses a raw device to store its data, it should access at the logical volume level. This is true of a select few databases, but in general accessing the raw device is not practiced.
Filesystems
The files stored on a disk are part of a filesystem. You will need to create a filesystem on each logical volume. There can be exactly one filesystem created on one logical volume. To use an HP/UX filesystem, you must mount it. Mounting a new filesystem puts all of the storage on that filesystem under a directory on the system. This directory is called a mount point. You will need to choose a new mount point for each new filesystem that you create. Before entering sam(1m), choose a mount point for this new filesystem. If you are new to administering UNIX machines, we recommend picking a mount point such as /mnt or / usr1.
Configuring HP-UX 9.0.4 for the New Storage

HP/UX allows many different ways of configuring the storage for your system. New disks can be added to an existing volume group, or assigned to a new volume group that you will create. The number and size of logical volumes in the volume group also varies. The new storage can be integrated into the system via a series of commands typed by the system administrator of via sam(1m). Both methods are documented in the following sections. The following example demonstrates some commands used to install a disk drive on an HP/UX system. In this example, we use commands typed from the Korn Shell. You may also use sam(1m) to perform these functions. Using Command Line This section describes how to integrate the new storage into the system command by command in a standard shell. This method is usually reserved for experienced system administrators, since sam(1m) is easier and more foolproof.
Add the New Physical Volumes
The first task is to find the name of the new disk that has been defined as part of the array. There will be one LU device for each LUN that you have configured (using the das_mgr utility). At the shell prompt, logged in as root, type the following command:
Figure 6-2 This will produce a list of all of the disk drives attached to the system. Locate the disks that are located on the new disk array. You will need to make the disk that has the SCSI target of your array and SCSI LUN 1 into an LVM physical volume[2]. The next step is to make the device on the array into an HP/UX physical volume. The new name for the physical volume will be as follows:
/dev/rdsk/cXd0s2 X = HP/UX LU At the shell prompt, type the following command substituting your device name: /etc/pvcreate -f -t DAS9000 /dev/rdsk/c9d0s2 This command will write the necessary label information to the new drive and add information about the drive to HP/ UX's internal device database.
Assign the Physical Volume to a Volume Group
You can either add the physical volume to an existing volume group, or create a new volume group to contain the physical volume. However, if the new physical volume is larger then other physical volumes in the existing volume group, then you will not be able to realize all of the capacity in the new physical volume.
Using an Existing Volume Group
You can add the new physical volume to an existing volume group by using the extendvg command. For example, if you would like to add the physical volume /dev/dsk/c9d0s2 to the existing volume group vg01, type the following: # vgextend /dev/vg01 /dev/dsk/c9d0s2
Creating a New Volume Group
If do not want to add the new disk to an existing volume group, but prefer to put it in a new volume group, follow these steps: * Make the volume group directory and the volume group device special file * Determine the size of the physical volume * Create the volume group For example, to make a new volume group called 9kvg1 with a single physical volume /dev/dsk/c9d0s2, type the following: First, make the volume group directory and the volume group device special file: # mkdir /dev/9kvg1 # mknod /dev/9kvg1/group c 64 `/usr/etc/MTI9000/find_grp` Next, find the capacity of the physical volume in megabytes by dividing the diskinfo(1m) output by 1024: # expr ` diskinfo -b /dev/rdsk/c9d0s2` / 1024
34674 Finally, create the volume group using the vgcreate(1m) command: NOTE: The number of megabytes derived above is divided by 4 to find out how many 4MB physical extents are necessary per physical volume in this volume group. # /etc/vgcreate -e `expr 34674 / 4` -s 4 /dev/9kvg1 /dev/dsk/c9d0s2 The above command created a volume group called /dev/9kvg1 which has the following characteristics: * The PE size is 4MB. This is a good number for array devices since arrays split up data among the available disks at much smaller sizes(8-64k). * The maximum number of physical extents(PE) that can be allocated out any physical volume within this volume group is 8668(34,674MB). This number is obviously different for every installation. * The name of the volume group is /dev/9kvg1. * The sole physical device is /dev/dsk/c9d0s2. Other devices can be added later.
Create a Logical Volume
We next need to create a logical volume in the volume group. The lvcreate(1m) command creates new logical volumes. For instance: # /etc/lvcreate -l 1000 -n 9klv1 -r n -C y 9kvg1 creates a new logical volume, 1000 physical extents (PE) long, called 9klv1 from the volume group 9kvg1. Use the lvcreate command one or more times to create logical volumes on the new array. Obviously the total number of PEs allocated to logical volumes must be less than or equal to the number of Free PEs available within the volume group. To determine how many PEs are available on a given volume group, type # vgdisplay -v 9kvgl Use the number for "Free PE". The default size of a PE is 4 MB(this is a good number for array devices), so the above command would make a logical volume with a capacity of 4000 MB.
Create a File System
You will now create a new filesystem on each logical volume. The following command creates a new filesystem on logical volume 9klv1. # newfs -f 8192 -b 65536 /dev/9kvg1/r9klv1 DAS9000 After pressing enter, you will have to wait a few minutes for the HP 9000 to make the filesystem on the array. The above step should be repeated for each of the new logical volumes.
Now, create a mount point for the new filesystem. The following example uses 9kfs1 as the directory name, but you can choose whatever name you like: # mkdir /9kfs1 Finally, mount the filesystem using the mount(1m) command. # mount /dev/9kvg1/9klv1 /9kfs1
Making the Data Accessible across a Reboot
In order to have the HP 9000 mount the data automatically after a reboot, an entry has to be made in the /etc/ checklist file. A mount(1m) with the -p option will print all currently mounted filesystems in a format that is suitable for /etc/checklist. Here is an example of how to add the /9kfs1 filesystem: # cp /etc/checklist /etc/checklist.old # mount -p | grep 9kfs1 >> /etc/checklist As a test, unmount the filesystem using the umount(1m) command. Then type "mount -a" to mount every filesystem in the /etc/checklist file. Finally, use the df(1m) command to display characteristics of all mounted filesystems. The new filesystem should be listed under its new logical volume. If it is listed, the storage is ready to be used. Using sam HP/UX allows many different ways of configuring the storage for your system. New disks can be added to an existing volume group, or assigned to a new volume group that you will create. The number and size of logical volumes in the volume group varies. * Invoke the System Administration Manager - sam(1m) # /usr/bin/sam If you are running a text-based version of sam(1m) then icons will be represented as menu options. The arrow keys are used to move between the various items. An item can be selected by pressing the <return> key. To move the cursor between the main window and the menu bar use the <tab> key. * Double-click on the "Disks and File Systems" submenu * Double-click on the "CD-ROM, Floppy, and Hard Disks" * Select the device with the description "MTI DAS9000". It should have "unused" in the "Use" column. * Select "Add a Hard Disk Drive" from the "Actions" menu
* Select "Using the Logical Volume Manager" from the extended menu * Enter a new volume group name in the text window. i.e. 9kvg * Select the "Modify Default Options..." field * Change the parameter labeled "Maximum Physical Extents" * The new value should be 1016 for every 4GB if array space. * Type 20,320 as a default value(this will allow for a 80GB array). * Leave other parameters alone and click on "OK" * Click on "OK" in the "Create a Volume Group" window. * Click on "Yes" in the "Confirmation window * Select "Logical Volumes" from the "List" menu * The following steps should be repeated until the available space is used up. * Select "Create..." from the "Actions" menu * Select "9kvg" from the "Volume Group" scroll box * Enter a new logical volume name in the text window. i.e. lv1 * Choose a logical volume size(less or equal to 4000) in megabytes. * Click on "Modify Logical Volume Options..." * Turn off "Bad Block Relocation" * Turn on "Contiguous Allocation" * Click "OK" in the "Create a Logical Volume" window * Select "Local File Systems" from the "List" menu * The following steps should be repeated until all of the new logical volumes are accounted for. * Select "Add->" from the "Actions" menu * Select "Using the Logical Volume Manager..."
* Choose a logical volume that was just created from the "Unused Logical Volumes" scroll box * Enter a "Mount Directory:" i.e. /usr2 * Click box to "Create New File System" * Make sure that the boxes "Mount Now" and "Mount at Every System Boot" are checked if appropriate. * Click "OK" in the "Add a Local File System" box * Click "OK" to confirm action * Select "Exit" from the "File" menu * Click on "Exit SAM"
Configuring HP-UX 10.0 for the New Storage

HP/UX allows many different ways of configuring the storage for your system. New disks can be added to an existing volume group, or assigned to a new volume group that you will create. The number and size of logical volumes in the volume group varies. * Invoke the System Administration Manager - sam(1m) # /usr/sbin/sam If you are running a text-based version of sam(1m) then icons will be represented as menu options. The arrow keys are used to move between the various items. An item can be selected by pressing the <return> key. To move the cursor between the main window and the menu bar use the <tab> key. * Double-click on the icon "Disks and File Systems" * Double-click on the icon "Volume Groups" * Select "Create or Extend..." from the "Actions" menu * Select the device with the description "MTI DAS9000" * The next window allows several commands to be chained together. First, a volume group needs to be created. Then several logical volumes are to be derived from the volume group. Do not create a logical volume greater than 4092 MB. The reason is that there is a one-to-one mapping between logical volumes and HFS filesystems, and HFS filesystems have a 4GB limitation. * Click "Create or Extend a Volume Group..." * Enter a new volume group name in the text window. i.e. 9kvg
* Click "OK" * Click "Add New Logical Volumes..." * Enter an LV Name. i.e. lv1 * Enter the LV Size(Mbytes). The maximum size is 4092. * Enter the Mount Directory. i.e. /usr2 * Click on "Modify LV Defaults..." * Click on "Use Bad Block Relocation" to turn this feature off. This feature is used for standalone disks that are not protected with RAID redundancy. * Click on "Use Contiguous Allocation" to turn this feature on. * Click on "Modify FS Defaults..." if you would like to override any of the default parameters. The defaults are as follows: the filesystem will be mounted read/write, it will set user ID execution, it will use long file names, sam(1m) will automatically mount the filesystem, and sam(1m) will modify /etc/fstab(4). * Repeat the last few steps until the free space in the volume group is depleted. Then click "OK" in the "Create New Logical Volumes" window. * Click "OK" in the "Add a Disk Using LVM" window. sam(1m) will now execute the chained commands. * Exit sam(1m).
Sun Solaris 1.x(SunOS 4.1.x)

This section provides background and describes the usual steps taken to make new disk storage usable by the SunOS 4.1.x filesystem.
Adding Host Support for Alternate LUNs

This section discusses the modifications that need to be made to the system if you will be dividing the MTI 9000 into multiple logical volumes. This is not a necessary step and can be done at any time. A 2-tier addressing scheme was designed into the original SCSI specification and has been supported ever since. The complete address for a device consists of a target address and a lun address. The target address is easily configurable for a device, usually by changing the position of digital switch on the back of the enclosure. For an 8-bit (narrow) SCSI bus, a valid target address ranges from 0-7, where the host normally uses target address 7. For a 16bit(wide) SCSI bus, a valid target address ranges from 0-15, where the host normally uses target address 7. For embedded controller devices, such as disk and tape devices, the lun address is always zero.
The MTI 9000 RAID controller has a unique target address on the SCSI bus. This is changeable via a digital switch on the back of the enclosure. The host can then select a lun address. There is a one-to-one mapping between logical volumes and lun addresses. Each logical volume that is configured into the array will look like a single disk drive to the host that is addressable on the SCSI bus via its target/lun address. From an operational and load-balancing standpoint, it is usually preferable to minimize the number of logical volumes. However, sometimes unique project requirements or system limitations force us to divide the storage into multiple logical volumes. For example, SunOS 4.1.3 allows for 8 partitions per disk(logical volume). In addition, any partition that will be used for a standard file system(see newfs(1)) has a limitation of 2GB. Therefore, simple arithmetic allows us to realize that any disk(logical volume) larger than 16GB will have wasted space on it. There are 2 ways to get around this limitation: divide the space available on the array into multiple logical volumes smaller than 16GB each or use the unbundled software package, SunSoft's Online: Disksuite(ODS). The latter solution supports a maximum file system size of 1 Terabyte. By default the SunOS kernel only has support for target addresses with a lun address of 0. Therefore, if multiple lun addresses per target address are needed the kernel need to be reconfigured. The steps are as follows: First, become root and change directories to the kernel configuration file directory: # cd /sys/`/bin/arch -k`/conf Find out what configuration file corresponds to the currently running kernel. # /usr/etc/showrev *************** showrev version 1.15 ***************** * Hostname: "ward" * Hostid: "71401975" * Kernel Arch: "sun4m" * Application Arch: "sun4" * Kernel Revision: 4.1.3 (GENERIC) #2: Tue Jul 5 15:56:33 CDT 1994 * Release: 4.1.3 ******************************************************* * The kernel configuration file in the above example is "GENERIC". Copy the kernel configuration file to a different name.
# cp GENERIC GENERIC_ADDLUNS Edit the new kernel configuration file. # vi GENERIC_ADDLUNS Search for the first occurrence of "sd". This will position yourself in the proper section to edit. It will look something like this: # # The following section describes SCSI device unit assignments. # scsibus0 at esp # declare first scsi bus disk sd0 at scsibus0 target 3 lun 0 # first hard SCSI disk disk sd1 at scsibus0 target 1 lun 0 # second hard SCSI disk disk sd2 at scsibus0 target 2 lun 0 # third hard SCSI disk disk sd3 at scsibus0 target 0 lun 0 # fourth hard SCSI disk tape st0 at scsibus0 target 4 lun 0 # first SCSI tape tape st1 at scsibus0 target 5 lun 0 # second SCSI tape disk sr0 at scsibus0 target 6 lun 0 # CD-ROM device scsibus1 at esp # declare second scsi bus disk sd4 at scsibus1 target 3 lun 0 # fifth hard SCSI disk disk sd5 at scsibus1 target 1 lun 0 # sixth hard SCSI disk disk sd6 at scsibus1 target 2 lun 0 # seventh hard SCSI disk disk sd7 at scsibus1 target 0 lun 0 # eighth hard SCSI disk tape st2 at scsibus1 target 4 lun 0 # third SCSI tape tape st3 at scsibus1 target 5 lun 0 # fourth SCSI tape disk sr1 at scsibus1 target 6 lun 0 # 2nd CD-ROM device
scsibus2 at esp # declare third scsi bus disk sd8 at scsibus2 target 3 lun 0 # ninth hard SCSI disk disk sd9 at scsibus2 target 1 lun 0 # tenth hard SCSI disk disk sd10 at scsibus2 target 2 lun 0 # eleventh hard SCSI disk disk sd11 at scsibus2 target 0 lun 0 # twelfth hard SCSI disk scsibus3 at esp # declare fourth scsi bus disk sd12 at scsibus3 target 3 lun 0 # thirteenth hard SCSI disk disk sd13 at scsibus3 target 1 lun 0 # fourteenth hard SCSI disk disk sd14 at scsibus3 target 2 lun 0 # fifteenth hard SCSI disk disk sd15 at scsibus3 target 0 lun 0 # sixteenth hard SCSI disk Now the lun support that is required. For example, we have an MTI 9000 array which resides on the first SCSI bus and has a SCSI target of 1. We want to break it up into 4 logical volumes. This requires 4 "sd" devices which all have a target address of 1 and lun addresses ranging from 0-3. The new "sd" device will have a number associated with it(i.e. sd1). There are only 2 rules for picking a new "sd" number: it must be a positive integer less than 32(0-31) and it must be unique. This is how the section should be modified: # # The following section describes SCSI device unit assignments. # scsibus0 at esp # declare first scsi bus disk sd0 at scsibus0 target 3 lun 0 # first hard SCSI disk disk sd1 at scsibus0 target 1 lun 0 # second hard SCSI disk disk sd16 at scsibus0 target 1 lun 1 # MTI 9000 logical volume disk sd17 at scsibus0 target 1 lun 2 # MTI 9000 logical volume disk sd18 at scsibus0 target 1 lun 3 # MTI 9000 logical volume
disk sd2 at scsibus0 target 2 lun 0 # third hard SCSI disk disk sd3 at scsibus0 target 0 lun 0 # fourth hard SCSI disk tape st0 at scsibus0 target 4 lun 0 # first SCSI tape tape st1 at scsibus0 target 5 lun 0 # second SCSI tape disk sr0 at scsibus0 target 6 lun 0 # CD-ROM device scsibus1 at esp # declare second scsi bus disk sd4 at scsibus1 target 3 lun 0 # fifth hard SCSI disk disk sd5 at scsibus1 target 1 lun 0 # sixth hard SCSI disk disk sd6 at scsibus1 target 2 lun 0 # seventh hard SCSI disk disk sd7 at scsibus1 target 0 lun 0 # eighth hard SCSI disk tape st2 at scsibus1 target 4 lun 0 # third SCSI tape tape st3 at scsibus1 target 5 lun 0 # fourth SCSI tape disk sr1 at scsibus1 target 6 lun 0 # 2nd CD-ROM device scsibus2 at esp # declare third scsi bus disk sd8 at scsibus2 target 3 lun 0 # ninth hard SCSI disk disk sd9 at scsibus2 target 1 lun 0 # tenth hard SCSI disk disk sd10 at scsibus2 target 2 lun 0 # eleventh hard SCSI disk disk sd11 at scsibus2 target 0 lun 0 # twelfth hard SCSI disk scsibus3 at esp # declare fourth scsi bus disk sd12 at scsibus3 target 3 lun 0 # thirteenth hard SCSI disk disk sd13 at scsibus3 target 1 lun 0 # fourteenth hard SCSI disk disk sd14 at scsibus3 target 2 lun 0 # fifteenth hard SCSI disk disk sd15 at scsibus3 target 0 lun 0 # sixteenth hard SCSI disk
As you can see, the only modifications were the addition of 3 lines. Configure the build directory for the new kernel: # config GENERIC_ADDLUNS Move to the build directory and compile the new kernel: # cd ../GENERIC_ADDLUNS # make Make a copy of the old kernel: # cp /vmunix /vmunix.old Copy the new kernel to the root directory so that it will be used at the next reboot. # cp ./vmunix /vmunix Reboot with the new kernel # reboot
Labeling and Partitioning the LUNs.

Before the Sun system can use the storage available on the array, each logical volume must be initialized with a label and then partitioned to your requirements using the Sun format(8S) utility. The utility relies on the fact that an entry has been made in the /etc/format.dat(5) file for the new logical volume. Since the size of logical volumes is site specific, MTI has provided a utility which will automatically create the proper entry. It is called das_labeler. The following steps guide through creating an entry for your logical volume in the format.dat(5) file, and labeling the volume with the format(8S) utility. This process will have to be repeated for every logical volume that has a unique capacity. For example, if all of the logical volumes are configured to have the same capacity, then they can all share the same format.dat(5) entry. First, become root and make a copy of the existing format.dat(5) file. # cp /etc/format.dat /etc/format.dat.orig Next, run the das_labeler utility and redirect the output to append the format.dat(5) file. The -p option informs the utility to use the next argument as the disk type for the new entry. Although the name used for the disk type is arbitrary, it is usually comprised of the product name and the capacity of logical volume. This name will be used later in the format(8S) utility to pick the proper entry.
# /usr/etc/das_labeler -p "MTI 9000 1756MB" sd1 >> /etc/format.dat The new addition the format.dat(5) file will look something like this: # # (c) 1994 National Peripherals, Inc. All rights reserved # MTI DAS9000 256B50141 # last addressable block=524287 # disk_type="MTI 9000 1756MB" \ : ctlr = SCSI : fmt_time = 3 \ : ncyl = 253 : acyl = 2 : pcyl = 256 : nhead = 16 \ : nsect = 128 : rpm = 3600 : bpt = 76800 partition = "MTI 9000 1756MB" \ : disk = "MTI 9000 1756MB" : ctlr = SCSI \ : a = 0, 32768 \ : b = 16, 65536 \ : c = 0, 518144 \ : g = 48, 419840 To complete the labeling, use the Sun format(8S) utility to partition and label all new array devices. An array device is a unique SCSI LUN. Each LUN that has been configured must be put through the following steps independently: * Invoke the format utility using the "format" command * Select an "MTI9000" device from the list of available devices * Select the new format.dat entry from the list of available entries. If the prompt is "format>", then select the "type" option to generate the list. This causes the system to build new geometry and default partition information. * Select the "partition" submenu
* Select the "print" option to print out the default partition table * Remember to make sure that each partition is less than 2GB unless Sun's Online Disk Suite(ODS) is installed. There are 4194304 blocks(512 bytes/block) in 2GB's. * Use the other menu options to customize the partition table * Select the "label" option to write the label to the array * Select the "quit" option to return the root menu * Select the "quit" option to exit the utility
Building Filesystems on the Partitions

This step involves creating a structure on the raw partition space to keep track of the data in a directory format. This meta-data is called the filesystem. One can think of this as a high level format. The newfs(1m) utility is used to place a filesystem structure on each partition. Only a single command line argument is needed: the raw device name. The raw device files are in the "/dev" directory and are always prefixed with an "r". The utility is invoked as in the following example: # newfs /dev/rsd<device number>c /dev/rsdXc: 72224 sectors in 296 cylinders of 4 tracks, 61 sectors 37.0MB in 19 cyl groups (16 c/g, 2.00MB/g, 896 i/g) super-block backups (for fsck -b #) at: 32, 4000, 7968, 11936, 15648, 19616, 23584, 27552, 31264, 35232, 39200, 43168, 46880, 50848, 54816, 58784, 62496, 66464, 70432, # This will take a few minutes and will place a heavy load on the array. Note that since mkfs(1m) operations are 100% small writes, the performance of the array will be at its worst, assuming that it is configured for RAID 5.
Mounting the Filesystems

Once a filesystem has been made, it can be mounted on an empty directory. This directory is known as the mount point for the filesystem. The command to mount the filesystem is intuitively named mount(1m). This command
requires a single command line argument: the block device name. The block device files are in the "/dev" directory. Keeping with the example from the previous section, the filesystem would be mounted with the following command: # mkdir /mnt # mount /dev/sd<device number>c /mnt
Making the Storage Accessible Across Reboots

In order for the system to mount the new storage after each reboot, the new filesystems must have an entry in the fstab (5) file in the /etc directory. This file includes information such as the partition name, the directory mount point, filesystem type(i.e. efs, nfs), and whether to fsck the filesystem or not. Here is an example of an easy way to make the fstab changes: # cp /etc/fstab /etc/fstab.old # mount -p | grep mnt >> /etc/fstab
Sun Solaris 2.x(SunOS 5.x)

This section provides background and describes the usual steps taken to make new disk storage usable by the SunOS 5.x filesystem.
Labeling and Partitioning the LUN.

To complete the installation, use the Sun format(1m) utility to partition and label all new array devices. An array device is a unique SCSI LUN. The recommended default configuration is to setup a single LUN 0. However, any additional LUNs that are configured must be put through the following steps independently: * Invoke the format utility using the "format" command * Select an "MTI9000" device from the list of available devices * Select type "0. Auto configure" from the list of devices. This causes the system to build new geometry and default partition information. * Respond "y" to prompt requesting to write label to array * Select the "partition" submenu * Select the "print" option to print out the default partition table * Usually, the default partitioning is fine since a single large filesystem can be created on partition "2"(the entire array).
* Use the other menu options to customize the partition table * Select the "label" option to write the label to the array * Select the "quit" option to return the root menu * Select the "quit" option to exit the utility

This step involves creating a structure on the raw partition space to keep track of the data in a directory format. This meta-data is called the filesystem. One can think of this as a high level format. The newfs(1m) utility is used to place a filesystem structure on each partition. Only a single command line argument is needed: the raw device name. The raw device files are in the "/dev/rdsk" directory. The utility is invoked as in the following example: # newfs /dev/rdsk/<devicename> newfs: construct a new file system /dev/rdsk/c0t1d0s1: (y/n)? y /dev/rdsk/c0t1d0s1: 410256 sectors in 407 cylinders of 14 tracks, 72 sectors 200.3MB in 26 cyl groups (16 c/g, 7.88MB/g, 3776 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, 16240, 32448, 48656, 64864, 81072, 97280, 113488, 129696, 145904, 162112, 178320, 194528, 210736, 226944, 243152, 258080, 274288, 290496, 306704, 322912, 339120, 355328, 371536, 387744, 403952, # This will take a few minutes and will place a heavy load on the array. Note that since mkfs(1m) operations are 100% small writes, the performance of the array will be at its worst, assuming that it is configured for RAID 5.

Once a filesystem has been made, it can be mounted on an empty directory. This directory is known as the mount point for the filesystem. The command to mount the filesystem is intuitively named mount(1m). This command requires a single command line argument: the block device name. The block device files are in the "/dev/dsk" directory. Keeping with the example from the previous section, the filesystem would be mounted with the following command:
# mkdir /mnt # mount /dev/dsk/<devicename> /mnt

In order for the system to mount the new storage after each reboot, the new filesystems must have an entry in the fstab (4) file in the /etc directory. This file includes information such as the partition name, the directory mount point, filesystem type(i.e. efs, nfs), and whether to fsck the filesystem or not. Here is an example of an easy way to make the fstab changes: # cp /etc/vfstab /etc/vfstab.old # /sbin/mount -p | grep mnt >> /etc/vfstab
SGI IRIX
This section provides background and describes the usual steps taken to make new disk storage usable by the IRIX filesystem. If you already are familiar with how disk storage is managed on IRIX systems, you can skip this section.
Labeling and Partitioning the LUN.

To complete the installation, use the SGI fx(1m) utility to partition and label the new logical volume. The following steps must be performed: * Invoke the fx utility using the "fx -x" command * Respond to prompts with the controller and SCSI ID of the array to be configured. * Select the "label" submenu * Select the "create" submenu * Select the "all" option to create all of the default label information from scratch * Select the ".." choice to backstep one directory * Select the "sync" option to write the label to the array * Select the ".." choice to return to the root menu * Select the "repartition" if it is necessary to change the default partitioning
* Remember, that the efs(4) filesystem has a maximum size of 8GB and that there is a one-to-one mapping between filesystems and partitions. If this is a limitation for your site, see your SGI distributor for information regarding the XFS file system. * Select the "exit" option when finished editing The following example shows how one invokes the utility, creates a label, and synchronizes the new label with the array. # fx -x fx version , Feb 14, 1994 fx: "device-name" = (dksc) fx: ctlr# = (0) <SCSI ctlr number> fx: drive# = (1) <SCSI ID> ...opening dksc(1,1,) ...controller test...OK Scsi drive type == MTI DAS9000 0141 ----- please choose one (? for help, .. to quit this menu)----[exi]t [d]ebug/ [l]abel/ [a]uto [b]adblock/ [exe]rcise/ [r]epartition/ [f]ormat fx> l ----- please choose one (? for help, .. to quit this menu)----[sh]ow/ [sy]nc [se]t/ [c]reate/ fx/label> c ----- please choose one (? for help, .. to quit this menu)----[p]artitions [s]giinfo [b]ootinfo [d]irectory [a]ll fx/label/create> a ...creating default bootinfo
...creating default partitions ...creating default sgiinfo ...creating default volume directory ----- please choose one (? for help, .. to quit this menu)----[p]artitions [s]giinfo [b]ootinfo [d]irectory [a]ll fx/label/create> .. ----- please choose one (? for help, .. to quit this menu)----[sh]ow/ [sy]nc [se]t/ [c]reate/ fx/label> sy writing label info to dksc(1,1,) ----- please choose one (? for help, .. to quit this menu)----[sh]ow/ [sy]nc [se]t/ [c]reate/ fx/label>

This step involves creating a structure on the raw partition space to keep track of the data in a directory format. This meta-data is called the filesystem. One can think of this as a high level format. The mkfs(1m) utility is used to place a filesystem structure on each partition. Only a single command line argument is needed: the raw device name. The raw device files are in the "/dev/rdsk" directory. The utility is invoked as in the following example: # /sbin/mkfs /dev/rdsk/<devicename> /sbin/mkfs: /dev/rdsk/dks1d1s0: blocks=15534080 inodes=1592800 /sbin/mkfs: /dev/rdsk/dks1d1s0: sectors=128 cgfsize=176480 /sbin/mkfs: /dev/rdsk/dks1d1s0: cgalign=1 ialign=1 ncg=88 /sbin/mkfs: /dev/rdsk/dks1d1s0: firstcg=3795 cgisize=4525
/sbin/mkfs: /dev/rdsk/dks1d1s0: bitmap blocks=3793 This will take a few minutes and will place a heavy load on the array. Note that since mkfs(1m) operations are 100% small writes, the performance of the array will be at its worst, assuming that it is configured for RAID 5.

Once a filesystem has been made, it can be mounted on an empty directory. This directory is known as the mount point for the filesystem. The command to mount the filesystem is intuitively named mount(1m). This command requires a single command line argument: the block device name. The block device files are in the "/dev/dsk" directory. Keeping with the example from the previous section, the filesystem would be mounted with the following command: # mkdir /mnt # /sbin/mount /dev/dsk/<devicename> /mnt

In order for the system to mount the new storage after each reboot, the new filesystems must have an entry in the fstab (4) file in the /etc directory. This file includes information such as the partition name, the directory mount point, filesystem type(i.e. efs, nfs), and whether to fsck the filesystem or not. Here is an example of an easy way to make the fstab changes: # cp /etc/fstab /etc/fstab.old # /sbin/mount -p | grep mnt >> /etc/fstab
IBM AIX
This section provides background for installers who have little experience with the IBM Logical Volume Manager. If you already are familiar with how disk storage is managed on AIX systems, you can skip this section.
Storage Hierarchy
AIX 3.0 introduced the Logical Volume Manager(LVM). The LVM controls all of the disk storage on your RS/6000 system. An excellent reference for the LVM is contained in IBM's AIX General Concepts and Procedures manual. Configuration Illustration Below is an example of an LVM configuration that illustrates the concepts discussed in this section. You should refer to this diagram while you read about the LVM.
This is a graphical representation of an AIX storage hierarchy. This example is intended to illustrate several aspects of the rules for LVM configuration. Physical Volumes The disk drives on an RS/6000 are known to AIX as a physical volume. Every hard disk on your system is a physical volume. Physical volumes are typically called hdiskn, where n is an integer assigned by AIX. The system uses this name to access the information on the disk. There is no relationship between SCSI ID and hdiskn assignment. In SMIT, or from the command line, you must add a new physical volume to your system's configuration tables. Since the Series 9000 arrays are capable of being divided into a number of SCSI LUNs, each disk array can appear to the system as one or more hdisk devices. Each LUN will correspond to one hdisk device. Volume Groups Physical volumes belong to volume groups. Volume groups are collections of related disks. Every RS/6000 system already has one volume group called rootvg. You can either add your new physical volume to rootvg or create a new volume group Volume groups can be comprised of one or more physical volumes. Each physical volume must belong to a single volume group. Logical Volumes The next level in the AIX storage hierarchy is the logical volume. Logical volumes allow segmentation of the storage allocated in the volume group level. The logical volume must obtain its storage from one and only one volume group. A logical volume spread across multiple volume groups is not permitted. However, multiple logical volumes can be defined on a single volume group. Notice that creating multiple logical volumes on a volume group containing a single physical volume is analogous to partitioning a single disk. If an application accesses a raw device to store its data, it should access at the logical volume level. This is true of a select few databases, but in general accessing the raw device is not practiced.
Filesystems The files stored on a disk are part of a filesystem. You will need to create a filesystem on each logical volume. There can be exactly one filesystem created on one logical volume. To use an AIX filesystem, you must mount it. Mounting a new filesystem puts all of the storage on that filesystem under a directory on the system. This directory is called a mount point. You will need to choose a new mount point for each new filesystem that you create. Before entering SMIT, choose a mount point for this new filesystem. If you are new to administering UNIX machines, we recommend picking a mount point such as /mnt or /usr1.
Configuring the New Storage

AIX allows many different ways of configuring the storage for your system. New disks can be added to an existing volume group, or assigned to a new volume group that you will create. The number and size of logical volumes in the volume group also varies. The following example demonstrates some commands used to install a disk drive on an AIX system. In this example, we use commands typed from the Korn Shell. You may also use SMIT to perform these functions. Add the New Physical Volumes The first task is to find the name of the new disks that have been defined as part of the array. There will be one "hdisk" device for each LUN that you have configured (using the das_mgr utility). At the shell prompt, logged in as root, type the following command: # lsdev -C -c disk -H This will produce a list of all of the disk drives attached to the system. Locate the hdisks that are located on the new disk array. You will need to make each one of these hdisks a LVM physical volume[3]. The new disks can be identified by their location code. The last two digits of the location code represent the SCSI target ID and LUN respectively. The next step is to make each hdisk device on the array an AIX physical volume. At the shell prompt, type the following command: # chdev -l hdiskn -a pv=yes where hdiskn is the name of the new disk. This command will write the necessary label information to the new drive and add information about the drive to AIX's internal device database, called the object data manager (ODM). Assign the Physical Volume to a Volume Group You can either add the physical volume to an existing volume group, or create a new volume group to contain the physical volume. However, you should not make the hdisk device corresponding to the diagnostic LUN a physical volume. This hdisk is reserved for the use of the das_monitor and das_mgr programs. You can add the new physical volume to an existing volume group by using the extendvg command. For example:
# extendvg -f rootvg hdiskn where hdiskn is the name of the new disk. This example command adds the disk to the root volume group. If do not want to add the new disk to an existing volume group, but prefer to put it in a new volume group, use the mkvg command. For example: # mkvg -f -y mtivg hdiskn where hdiskn is the name of the new disk. This command makes a new volume group called "mtivg" including the physical volume "hdiskn". This command sets up the automatic "vary on" of the new volume group at system restart. NOTE: MTI strongly recommends that all of the LUNs in a single array box be assigned to one volume group. We do not recommend that you make these units part of an existing rootvg. To vary the volume group on now, type: # varyonvg mtivg See the AIX documentation on varyonvg and varyoffvg for details. Create a Logical Volume We next need to create a logical volume in the volume group. The mklv command creates new logical volumes. For instance: # mklv -y samplelv rootvg 100 hdiskn creates a new logical volume, 100 physical partitions (PPs) long, called "samplelv" on the disk "hdiskn" in volume group "rootvg". Use the mklv command one or more times to create logical volumes on the new drive. Obviously the total number of PPs allocated to logical volumes must be less than or equal to the number of PPs available on the new disk. To determine how many PPs are available on a given physical volume, type # lspv hdiskn Use the number for "FREE PPs". The default size of a PP is 4 MB, so the above command would make a logical volume with a capacity of 400 MB. Create a Journaled File System You will now create a new filesystem on the logical volume. The following command creates a new filesystem on "samplelv" which automatically mounts the filesystem on the /mnt directory at system restart. See the manual page on crfs for details. # crfs -v jfs -d samplelv -m /mnt -A yes -p rw
After pressing enter, you will have to wait a few minutes for the RS/6000 to make the filesystem on the disk. You should then mount the new filesystem using the mount command. # mount /mnt As a test, issue a df command. The new filesystem should be listed under its new logical volume. If it is listed, the storage is ready to be used.
DEC Digital UNIX(formerly OSF/1)

This section provides background and describes the usual steps taken to make new disk storage usable by the Digital UNIX filesystem. If you already are familiar with how disk storage is managed on Digital UNIX systems, you can skip this section.
Checking for New Devices Before Booting

Before the system is booted, gather information about the logical location of the new array. The Alpha has the capability of scanning all SCSI busses for targets. The PROM monitor prompt , ">>>", the command to display this listing is "show". Since the array emulates a standard disk drive, it will show up in the listing as a "DK" device. Below is an example of type of output to expect when running the "show" command and how to select the information needed in the next section. >>> show dev DKA200 A/2/0 ------^ This represents the SCSI bus(A). --------^ This represents the SCSI target ID(2). ----------^ This represents the SCSI lun(0). ...Alternatively, you may see this output... >>> show dev dka100.1.0.6.0 DKA100 MTI9000 DAS9000 141 ---------------------^ This represents the SCSI bus(A). ----------------------^ This represents the SCSI target ID(1). ------------------------^ This represents the SCSI lun(0).
Accessing, Labeling, and Partitioning the LUN

The first step to accessing the array is to determine the device name. Using the information from above, the device name is as follows: rzX X= ((SCSI bus #) * 8) + (SCSI target) * The SCSI bus is described by a letter. To convert the letter to a number, use a simple mapping scheme: A=0, B=1, C=2 ... * rz2 = target 2 on SCSI bus "A" * rz10= target 2 on SCSI bus "B" To access the device, its device special files must be created. They are created with the following commands: # cd /dev # MAKEDEV rzX The following steps utilize the disklabel(1m) utility to manage the initialization and administration of the disk. Please note that the disktab(5) entry is no longer necessary. * Use the disklabel(1m) command to write a default label to the disk: # disklabel -r -w /dev/rrzXc sz * Use the disklabel(1m) command to interactively edit the default label: # disklabel -e /dev/rrzXc * This command will bring up your default editor with the current label displayed. * Change the default rpm. The default is 3600. Change it to 7200. * Customize the partition table to your requirements. * Upon quitting your default editor in the normal way, you will be prompted to write the label to the disk. If you are satisfied with the label, then respond with a 'y'.

This step involves creating a structure on the raw partition space to keep track of the data in a directory format. This meta-data is called the filesystem. One can think of this as a high level format.
The newfs(1m) utility is used to place a filesystem structure on each partition. Only a single command line argument is needed: the raw device name. The raw device files are in the "/dev" directory and are prefixed with an "r". The utility is invoked as in the following example: # newfs /dev/rrzXg

Once a filesystem has been made, it can be mounted on an empty directory. This directory is known as the mount point for the filesystem. The command to mount the filesystem is intuitively named mount(1m). This command requires a single command line argument: the block device name. The block device files are in the "/dev" directory. Keeping with the example from the previous section, the filesystem would be mounted with the following command: # mkdir /usr2 # mount /dev/rzXg /usr2

Add any filesystems that should be mounted upon bootup to the fstab(4) file. Each filesystem that is mounted automatically upon bootup has a single line entry in this file. This single line is divided into 5 fields. Each field is separated by white space(spaces or tabs). file_spec mnt_point fs_type mnt_options backup fsck The first field, (file_spec), describes the block special device that is to be mounted. The second field, (mnt_point), specifies either the mount point for the filesystem. The third field, (fs_type), specifies the type of file system. Use "ufs" if newfs(8) was used to created the filesystem. The fourth field, (mnt_options), describes the mount options associated with the file system or partition. It is formatted as a comma separated list of options and contains at least the type of mount (see the fs_type field) plus any additional options appropriate to the file system type or the partition use. You can specify the following mount options. See mount(8) for a complete list and description of the legal mount options for the various file system types. The fifth field, (backup), is used by the dump command to determine which file systems need to be backed up. If the fifth field is not present, a value of zero is returned and dump assumes that the file system does not need to be backed up. The sixth field, (fsck), is used by the fsck command to determine the order in which file system checks are done at reboot time. For the root file system, specify 1 in the fsck field, and for other file systems, specify 2 in the fsck field. File systems that are on the same disk are checked sequentially, but file systems on different disks are checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and the fsck command assumes that the file system does not need to be checked.
An example of an entry for the ongoing example is as follows: /dev/rzXg /usr2 ufs rw 1 2
Replacing Failed Components

Replacing a Failed Disk
The array can be configured with or without hot spare disk drives. A hot spare disk will automatically take the place of a failed disk within the array at the time of the failure. The benefit to hot sparing is that it minimizes the window of vulnerability associated with operating an array in a "degraded" mode.
Without a spare disk, the array will also continue to function in the event of a disk failure. You can replace the failed disk and rebuild the data for that disk without interrupting availability of data to your users. No software intervention is required. The array will sense the insertion of the new disk and will start rebuilding data to it. WARNING: If another disk fails before the rebuild operation completes, all user data on the array will be lost.
Replacing a Power Supply

See the Hardware Manual for your model array. When the power supply is fixed, the monitoring daemon will be notified and an appropriate message will be sent to the syslogd(1m) daemon.
Replacing a Fan
See the Hardware Manual for your model array. When the fan is fixed, the monitoring daemon will be notified and an appropriate message will be sent to the syslogd(1m) daemon.
Replacing a Controller
http://www-personal.umich.edu/~rak/9k_manual/9kreplac.html (1 of 2)18-Feb-08 11:30:31 AM
The following items are criteria for determining that a controller should be replaced: * The subsystem was installed correctly(i.e. this is not a new installation - the subsystem had been working fine) AND * Reads and Writes are now failing to the array AND * The problem cannot be isolated to a subcomponent of the controller by comparing messages in the / usr/adm/syslog with the following table. AND * The problem cannot be isolated to a subcomponent of the controller by using the mti9000 utility. If it becomes necessary to replace the controller board, follow the instructions in the Hardware Manual for your model array. Then perform the following tasks: * Invoke das_mgr utility * Use the load menu option of the configuration submenu to load your saved configuration. * Use the set menu option of the configuration submenu to set the NVRAM of the new controller. * Your data should now be available.
http://www-personal.umich.edu/~rak/9k_manual/9kreplac.html (2 of 2)18-Feb-08 11:30:31 AM
Error Messages: Descriptions and Action Items

Normally, any messages that are generated by the das_monitor daemon will be logged in files that are receiving errors with the LOG_DAEMON facility and the LOG_ERR or LOG_NOTICE or LOG_CRIT levels. In the event that the log file cannot be reached, the messages will be logged to the console only. Table 8-1 contains descriptions and references to corresponding action items for error messages that have been reported by the das_monitor process. Table 8-2 contains a list of common action items that can be performed to handle problems. NOTE: * /dev/rdsk/c201d0s0 is used as the default device for all of the following example error messages. The device on your platform may be of a different format, but is irrelevant for these examples. * Since das_monitor can be monitoring an array on a remote system, the <host> that the message pertains to is listed where appropriate. EXAMPLE ERROR MESSAGES* ACTION
DESCRIPTION
das_monitor: /dev/rdsk/c201d0s0 Temperature on <host> changed from OK to Not overtemperature 6, 2 OK been is at least
An condition has reached. It
45[[ring]]C (113[[ring]]F) . alert only. array will continue to operate. das_monitor: /dev/rdsk/c201d0s0 Temperature on <host> changed from Not OK to has been 1, 2 OK fixed. das_monitor: /dev/rdsk/c201d0s0 Fan on <host> changed from OK to Not OK failed. 4, 2 das_monitor: /dev/rdsk/c201d0s0 Fan on <host> changed from Not OK to OK has been 1, 2 The failure The This is an
A fan has The failure fixed.
das_monitor: /dev/rdsk/c201d0s0 Power Supply on <host> changed from OK to Not supply has 5, 2 OK failed. das_monitor: /dev/rdsk/c201d0s0 Power Supply on <host> changed from Not OK to has been 1, 2 OK
http://www-personal.umich.edu/~rak/9k_manual/9kerror.html (1 of 8)18-Feb-08 11:30:39 AM
A power
The failure
fixed.
das_monitor: Going Down on signal 2 was killed. 15, 2 das_monitor: Going Down on signal 15 was killed. 15, 2 das_monitor: Can't open filename: No Such File or Directory open the file 16,17,18, 2 listed after
The daemon The daemon
Could not for reason colon.
das_monitor: Configuration Read Failed: I/O Error read the 8, 9, 10, 2 from the
Failed to configuration array for
reason listed after colon. das_monitor: /dev/rdsk/c201d0s0 LUN 0 on <host> is degraded failed and 7, 2 LUN to be put in degraded mode. This means that the performance of the array will drop until the failed disk is replaced and the rebuild is complete. Beware that the array can only tolerate 1 disk to be failed at any time without losing data. das_monitor: /dev/rdsk/c201d0s0 LUN 0 on <host> is offline of the 2 comprise this logical volume is not ONLINE. This LUN
A drive has caused this
More than one drives that
cannot be used for data storage or retrieval. das_monitor: /dev/rdsk/c201d0s0 LUN 0 on <host> is online has been 1, 2 The failure fixed. das_monitor: Controller Enquiry Failed for Array /dev/rdsk/c201d0s0 on <host> read enquiry 8, 9, 10, 2 : I/O Error from the reason listed after colon. das_monitor: Read Portword Failed for Array /dev/rdsk/c201d0s2 on <host>: read the 8, 9, 10, 2 :I/O Error the array listed after colon. das_monitor: Array /dev/rdsk/c201d0s0 A 19, 2 currently Online das_monitor: Array /dev/rdsk/c201d0s0 has failed. 3, 2 currently DEAD das_monitor: Array /dev/rdsk/c201d0s0 recovering 20, 2 currently Rebuilding state. das_monitor: Array /dev/rdsk/c201d0s0 previously 21, 2 currently Spare was replaced. now the new Spare device. das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: configured DEAD, was not 21, 2 currently Online be part of volume, but it is present and online. das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: configured DEAD, A 19, 2 currently DEAD
Failed to information array for
Failed to portword from for reason
(0,0) on <host>: configured Online,
N/
This drive
This drive is from a failed
This drive failed and This drive is
This drive configured to any logical
N/
das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: configured DEAD, A 19, 2 currently Rebuilding das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: configured DEAD, was not 21, 2 currently Spare be part of volume, but
N/
This drive configured to any logical was started
as the spare drive after the configuration was das_monitor: Array /dev/rdsk/c201d0s0 A 19, 2 currently Online das_monitor: Array /dev/rdsk/c201d0s0 A 19, 2 currently Online das_monitor: Array /dev/rdsk/c201d0s0 A 19, 2 currently Online das_monitor: Array /dev/rdsk/c201d0s0 A 19, 2 currently Online das_monitor: Array /dev/rdsk/c201d0s0 was 21, 2 currently Online the Spare Another drive failed and this drive was brought up in its das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: configured Spare, drive has 3, 2 currently DEAD failed. das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: configured Spare, has failed 20, 2 currently Rebuilding controller is rebuilding to this drive. das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: configured Spare, A 19
(0,0) on <host>: configured Rebuilding,
initialized. N/
N/
N/
N/
(0,0) on <host>: configured Spare,
This drive configured as device.
place. The Spare
Another drive and the currently
N/
currently Spare
das_monitor: Array /dev/rdsk/c201d0s0 A 19, 2 to Online das_monitor: Array /dev/rdsk/c201d0s0 has failed. 3, 2 to DEAD das_monitor: Array /dev/rdsk/c201d0s0 recovering 20, 2 to Rebuilding state. das_monitor: Array /dev/rdsk/c201d0s0 previously 21, 2 to Spare was replaced. now the
(0,0) on <host>: changed from Online,
N/
This drive
This drive is from a failed
This drive failed and This drive is new Spare
device. das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from DEAD, to was not 21, 2 Online be part of volume, but
This drive configured to any logical it is present
and online. das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from DEAD, to A 19, 2 DEAD das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from DEAD, to A 19, 2 Rebuilding das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from DEAD, to was not 21, 2 Spare be part of volume, but
N/
N/
This drive configured to any logical was started
as the spare drive after the configuration was das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from A 19, 2 Rebuilding, to Online das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from A 19, 2
initialized. N/
N/
Rebuilding, to Online das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from A 19, 2 Rebuilding, to Online das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from A 19, 2 Rebuilding, to Online das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from Spare, to was 21, 2 Online the Spare Another drive
N/
N/
This drive configured as device. failed and
this drive was brought up in its das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from Spare, to drive has 3, 2 DEAD failed. das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from Spare, to has failed 20, 2 Rebuilding controller is rebuilding to this drive. das_monitor: Array /dev/rdsk/c201d0s0 (0,0) on <host>: changed from Spare, to A 19 Spare das_monitor: /dev/tty0p1 Serial Error 0x1, Retry X error - This 22, 23, 24, applicable using the serial interface. das_monitor: /dev/tty0p1 Serial Error 0x2, Retry X timeout error 22, 23, 24, only for systems using the serial das_monitor: /dev/tty0p1 Serial Error 0x3, Retry X error - This 22, 23, 24, applicable 25, 2 for systems
place. The Spare
Another drive and the currently
N/
Send packet error is only
25, 2 for systems
Packet This error is
25, 2 applicable
interface. Get packet error is only
using the serial interface. das_monitor: /dev/tty0p1 Serial Error 0x4, Retry X packet error 22, 23, 24, is only for systems using the serial das_monitor: /dev/tty0p1: Resetting Bus - Current Cmd Resets X, Total Resets Y retry count 22, 23, 24, so the was reset by sending a break to the controller. 25, 2 serial bus interface. The packet was exceeded, 25, 2 applicable Unexpected - This error
Table 8-1 ACTION ITEM DESCRIPTION # 1 * No action - this message means that a failure condition has been corrected. 2 * Call MTI (1-708-3254151) 3 * Replace Drive. Reference the Hardware Manual for your model array. 4 * Replace Fan. Reference the Hardware Manual for your model array. 5 * Replace Power Supply. Reference the Hardware Manual for your model array. 6 * Check Fan, Power Supply, Make sure that the airspace around the array is not constricted(i.e. under a desk and against a wall), Cool room. 7 * This message is informational only. It will be accompanied with another message stating the cause of the failure. 8 * Make sure that external cable connections are tight and secure. 9 * Make sure that there are no bent pins on the male cable connectors or the terminators. 10 * Check to see if other devices on the same bus are working. 11 * Replace controller. Reference the hardware maintenance section for your model array. 12 * Reseat the drive canister in the slot. Simply pull out the drive, and put it back in again. 13 * Check to make sure that power supply is plugged in properly.
14 * Make sure that there are not typos in the /usr/etc/das9kd.conf file. 15 * Kill all daemons, then restart all daemons with dasalert script. 16 * Check for a syntax error in the command line arguments. 17 * Check to make sure that the device special file has been created 18 * Make sure that you are superuser. 19 * This message should never occur. Please save the message and call MTI (1-708325-4151) 20 * A rebuild process is underway. Check later for messages that the rebuild completed. 21 * The state of this drive has changed since the configuration has been written. Treat this message as a benign informational message. 22 * Make sure that no other daemons are using the serial port that is being used to monitor this array(i.e. getty) 23 * Make sure that you are using the correct type of cable(Null-modem for HP, Straight-thru pinout for Sun, SGI, IBM RS/6000). The MTI 9000 is a DCE device. Only Transmit, Receive, and Ground are necessary. 24 * Do not exceed 25' of serial cable. 25 * Try a new serial cable.
Table 8-2
http://www-personal.umich.edu/~rak/9k_manual/Appendix.html
APPENDIX A: HP Patch Installation Notes

HP-UX 9.0.4 - PHKL_5405 Installation Notes
Patch Name: PHKL_5405 Patch Description: s800 9.04 SCSI pass-through driver cumulative patch Creation Date: 95/03/30 Post Date: 95/04/06 Hardware Platforms - OS Releases: s800: 9.04 Products: N/A Filesets: spt-DVR Automatic Reboot?: No Status: General Release Critical: Yes PHKL_5405: HANG PHKL_4956: CORRUPTION Path Name: /hp-ux_patches/s800/9.X/PHKL_5405
http://www-personal.umich.edu/~rak/9k_manual/Appendix.html (1 of 11)18-Feb-08 11:30:43 AM
Symptoms: PHKL_5405: Products using the SCSI Pass-Through driver in a high availability environment will not functions correctly without this patch. Devices may hang. PHKL_4956: Data stored to or retrieved from an archive may be wrong. Defect Description: PHKL_5405: New interface added for products running in a high availability environment. PHKL_4956: A single buffer can be concurrently used for more than one IO. This condition will occur when the system is under heavy memory pressure and the call to physio blocks while trying to get memory and more IOs are sent through the pass through driver. This condition could affect either reads or writes. SR: 4701287649
Patch Files: /etc/conf/lib/libspt.a /etc/contrib/bin/master.diff /etc/contrib/bin/scsi_io.c /usr/man/man7.Z/scsi_pt.7 /usr/include/sys/spt.h what(1) Output: /etc/conf/lib/libspt.a: scsi_pt.c $Revision: 2.1.1.2 $ $Date: 95/03/24 14:50:24 $ PATCH_9.04 (PHKL_5405) /etc/contrib/bin/master.diff: None /etc/contrib/bin/scsi_io.c: None /usr/man/man7.Z/scsi_pt.7: None /usr/include/sys/spt.h: spt.h $Revision: 1.4.1.1 $ $Date: 94/11/18 1 5:27:53 $ */ sum(1) Output:
33701 39 /etc/conf/lib/libspt.a 19447 1 /etc/contrib/bin/master.diff 2930 4 /etc/contrib/bin/scsi_io.c 40054 16 /usr/man/man7.Z/scsi_pt.7 29439 3 /usr/include/sys/spt.h Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHKL_4956 Equivalent Patches: PHKL_5406: s800: 10.00 Patch Package Size: 100 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties,
before installing this patch. -----------------------------------------------------------1. Back up your system before installing a patch. 2. Copy the patch to your /tmp directory and unshar it: cd /tmp cp patch_source/PHKL_5405 . sh PHKL_5405 3. Become root and run update: /etc/update 4. Use the cursor keys to select "Change Source or Destination ->" and press [Return]. 5. Select "From Tape Device to Local System ..." in the Change window and 6. Change "Source: /dev/rmt/0m" to "Source: /tmp/PHKL_5405.updt" 7. Press "Done" (f4). 8. Follow the standard directions for update. Update moves the original software to /system/PHKL_5405/orig. Keep this file to recover from any potential problems. You should move the .text file to
/system/PHKL_5405 for future reference. To put this patch on a magnetic tape and update from the tape drive, use dd: dd if=PHKL_5405.updt of=/dev/rmt/0m bs=2048 Special Installation Instructions: SINGLE_USER: This patch does not cause an auto reboot, however A REGEN AND REBOOT ARE NECESSARY. The system administrator will have to configure the driver and desired devices prior to regenerating the kernel (unless already done) and rebooting. This patch just installs the fileset.
HP-UX 10.0 - Patch PHKL_5406 Installation Notes

Please note that the instructions listed below are only valid for HP/UX 10.0. HP/UX 10.01 includes changes from PHKL_5406 with the core operating system. The following is taken from the PHKL_5406 patch description and installation file: Patch Name: PHKL_5406 Patch Description: s800 10.00 SCSI pass-through driver Creation Date: 95/04/03 Post Date: 95/05/01 Hardware Platforms - OS Releases: s800: 10.00
Products: N/A Filesets: SCSI-Passthru.spt-DVR Automatic Reboot?: No Status: General Release Critical: Yes PHKL_5406: HANG Path Name: /hp-ux_patches/s800/10.X/PHKL_5406 Symptoms: PHKL_5406: Products using the SCSI Pass-Through driver in a high availability environment will not functions correctly without this patch. Devices may hang. Also has fix for problem where data stored to or retrieved from an archive may be wrong. Defect Description: PHKL_5406: New interface added for products running in a high availability environment. It also contains the fix for
the problem where a single buffer can be concurrently used for more than one IO. This condition will occur when the system is under heavy memory pressure and the call to physio blocks while trying to get memory and more IOs are sent through the pass through driver. This condition could affect either reads or writes. SR: 4701287649 Patch Files: /usr/conf/lib/libspt.a /usr/contrib/src/scsi_io.c /usr/share/man/man7.Z/scsi_pt.7 /usr/conf/master.d/spt what(1) Output: /usr/conf/lib/libspt.a: scsi_pt.c Revision: 10.00 $Date: 95/03/29 11:3 8:13 $ /usr/contrib/src/scsi_io.c: None /usr/share/man/man7.Z/scsi_pt.7:
None /usr/conf/master.d/spt: None cksum(1) Output: 1564027304 27768 /usr/conf/lib/libspt.a 2433971724 1919 /usr/contrib/src/scsi_io.c 1523848732 9074 /usr/share/man/man7.Z/scsi_pt.7 1847244798 3989 /usr/conf/master.d/spt Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: PHKL_5405: s800: 9.04 Patch Package Size: 90 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. -----------------------------------------------------------1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHKL_5406 5. Run swinstall to install the patch: swinstall -s /tmp/PHKL_5406.depot PHKL_5406 By default swinstall will archive the original software in /var/adm/sw/patch/PHKL_5406. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHKL_5406.text file to
/var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: swpackage -s /tmp/PHKL_5406.depot -x target_type=tape -d /dev/rmt/0m PHKL_5406 Special Installation Instructions: This product will not have existed on the system prior to this patch so the swinstall option 'MATCH WHAT TARGET HAS' will not work to install this patch. Also, this patch does not cause an auto reboot, however A REGEN AND REBOOT ARE NECESSARY. The system administrator will have to configure the driver and desired devices prior to regenerating the kernel (unless already done) and rebooting. This patch just installs the fileset.
http://www-personal.umich.edu/~rak/9k_manual/9kconfig_fn.html
If you don't know whether you need spt or not, see section - .
[2] If you don't know whether you need spt or not, see section - .
http://www-personal.umich.edu/~rak/9k_manual/9kconfig_fn.html18-Feb-08 11:30:46 AM
http://www-personal.umich.edu/~rak/9k_manual/9kavail_fn.html
[1]By convention, LUN 0 devices have no 'l' in their names.

2
Do not confuse the term "physical volume" with the physical disk drives that are in the disk array. "Physical Volume" is an HP-UX LVM abstraction of a disk drive. They are not physical disk drives.
3
Do not confuse the term "physical volume" with the physical disk drives that are in the disk array. "Physical Volume" is an AIX LVM abstraction of a disk drive. They are not physical disk drives.
http://www-personal.umich.edu/~rak/9k_manual/9kavail_fn.html18-Feb-08 11:30:49 AM

MTI9000 DiskArray

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MTI9000 DiskArray

Hochgeladen von

Copyright:

Verfügbare Formate

http://www-personal.umich.

Click on the Topic you would like to see

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall_ToC.html (1 of 3)18-Feb-08 11:28:36 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall_ToC.html (2 of 3)18-Feb-08 11:28:36 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall_ToC.html (3 of 3)18-Feb-08 11:28:36 AM

http://www-personal.umich.edu/~rak/9k_manual/9000rpc_ToC.html (1 of 2)18-Feb-08 11:28:38 AM

http://www-personal.umich.edu/~rak/9k_manual/9000rpc_ToC.html (2 of 2)18-Feb-08 11:28:38 AM

1. Monitoring Array Events 1. Examining Events

http://www-personal.umich.edu/~rak/9k_manual/9kavail_ToC.html (1 of 2)18-Feb-08 11:28:47 AM

http://www-personal.umich.edu/~rak/9k_manual/9kavail_ToC.html (2 of 2)18-Feb-08 11:28:47 AM

1. Error Messages: Descriptions and Action Items

http://www-personal.umich.edu/~rak/9k_manual/9kintro.html (2 of 2)18-Feb-08 11:29:01 AM

Option to Retrieve Software from the Internet

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (1 of 99)18-Feb-08 11:29:39 AM

irix aix sunos4.1.x

tar and SVR4

HP HP-UX for Series 700

HP 700 - Software Management Using MTI "INSTALL"

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (4 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (5 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (9 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (10 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (11 of 99)18-Feb-08 11:29:39 AM

HP HP-UX for Series 800

HP 800 - Prepare HP-UX for Series 9000 Software/a>

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (12 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (14 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (15 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (16 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (17 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (19 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (21 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (22 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (23 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (25 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (26 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (28 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (30 of 99)18-Feb-08 11:29:39 AM

HP 800 - Software Management Using MTI "INSTALL"

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (31 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (34 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (38 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (39 of 99)18-Feb-08 11:29:39 AM

Sun Solaris 2.x(SunOS 5.x)

Solaris2.x - Software Management Using SVR4 "package" Utilities

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (40 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (43 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (48 of 99)18-Feb-08 11:29:39 AM

Sun Solaris 1.x(SunOS 4.1.x)

Solaris1.x - Software Management Using MTI "INSTALL"

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (50 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (53 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (54 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (58 of 99)18-Feb-08 11:29:39 AM

SGI - Software Management Using SVR4 "package" Utilities

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (59 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (62 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (63 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (67 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (68 of 99)18-Feb-08 11:29:39 AM

http://www-personal.umich.edu/~rak/9k_manual/9000swinstall.html (69 of 99)18-Feb-08 11:29:39 AM

## Updating system information. Removal of <MTI9000> was successful.