1. Manuals
  2. Brands
  3. Silicon Graphics Manuals
  4. Disk array system
  5. TP9100
  6. Installation instructions and user manual

Silicon Graphics TP9100 Installation Instructions And User Manual

Hide thumbs Also See for TP9100:
Table of Contents

Advertisement

Quick Links

Download this manual
TPM Installation Instructions and User's Guide
for TP9100
007-4382-002

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the TP9100 and is the answer not in the manual?

Questions and answers

Related Manuals for Silicon Graphics TP9100

Summary of Contents for Silicon Graphics TP9100

  • Page 1 TPM Installation Instructions and User's Guide for TP9100 007-4382-002...
  • Page 2 COPYRIGHT © 2001 Silicon Graphics, Inc. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of Silicon Graphics, Inc.
  • Page 3 Record of Revision Version Description March 2001 Initial Rev October 2001 Functionality updates 007-4382-002...

  • Page 5: Table Of Contents

    Contents List of Figures . . ix List of Tables . . xiii About This Guide. . xv Audience . xv Structure of this Guide . xv Product Support . . xvi Obtaining Publications . xvi Reader Comments . . xvi Introduction Product Overview .
  • Page 6 Invoking TPM . . 16 Setting the Environment Variable for IRIX and Linux: . 16 Starting SGI TP9100 Array Manager for IRIX and Linux . . 16 Starting SGI TP9100 Array Manager for Windows . 17 Setting Up the Browser .
  • Page 7 Contents Reporting Functions . .106 Set Default Screen Refresh Rate . .107 Display (Dual) Controller Status .108 Topology Query . .109 Display Statistical Data by Physical Device .110 Display Statistical Data by Logical (RAID) Disk (6.14 Firmware Only) .110 Display SCSI/Fibre Device Information .111 Display FULL Subsystem Configuration Information .112...

  • Page 9: List Of Figures

    List of Figures TPM InstallShield Wizard . . 10 Figure 2-1 License Agreement Dialog Box . 11 Figure 2-2 Choose Destination Dialog Box . . 12 Figure 2-3 Select Program Folder Dialog Box . 13 Figure 2-4 Installation Complete Dialog Box. .
  • Page 10 List of Figures Warning Screen (6.14, 7.01, and 7.03 Firmware) . . 53 Figure 3-21 Controller Resetting Information Screen . . 53 Figure 3-22 Controller Resetting Status Screen (1 of 2) . 54 Figure 3-23 Controller Resetting Status Screen (2 of 2) .
  • Page 11 List of Figures View/Modify Controller Configuration (partial for 7.01 Firmware) . 89 Figure 3-52 View/Modify Controller Configuration (partial for 7.01 Firmware) . 90 Figure 3-53 View/Modify Controller Configuration (partial for 7.75 Firmware) . 91 Figure 3-54 View/Modify Controller Configuration (partial for 7.75 Firmware) . 92 Figure 3-55 View/Modify Controller Configuration (partial for 7.75 Firmware) .
  • Page 12 List of Figures Logical Subsystem Information (partial for 6.14 Firmware) Figure 3-83 Logical Subsystem Information (partial for 7.01 and Later Figure 3-84 Firmware) Display Environmental Subsystem Information (6.14 Firmware) . Figure 3-85 Display Environmental Subsystem Information (7.01 and Later Figure 3-86 Firmware) Miscellaneous Functions Menu (for 6.14 Firmware) Figure 3-87...
  • Page 13 List of Tables Files in the Distribution (IRIX and Linux) . Table 1-1 Files in the Distribution (Windows) . Table 1-2 Select Physical Device Field Definitions . . 30 Table 3-1 Modify Disk Device Status Field Definitions . 34 Table 3-2 Record Layout .

  • Page 15: About This Guide

    About This Guide This guide provides information on preparing, installing, configuring, and using the Total Performance Manager (TPM) application for the TP9100 external RAID subsystem. Note: At the time of production, an issue with the 7.70 controller firmware resulted in version 7.75 controller firmware code being released.

  • Page 16: Product Support

    About This Guide Product Support SGI provides a comprehensive product support and maintenance program for its products. If you are in North America and would like assistance with your SGI-supported products, contact the Customer Support Center (CSC) at 1-800-800-4SGI (1-800-800-4744) or your authorized service provider. If you are outside North America, contact the SGI subsidiary or authorized distributor in your country.

  • Page 17: Introduction

    Chapter 1 Introduction Product Overview The Total Performance Manager (TPM) application is an HTML-based GUI RAID client-server application manager. It provides a user-friendly graphical user interface (GUI) for configuring and monitoring external RAID disk subsystems that use several families of RAID controller engines. TPM consists of two programs that run natively on an IRIX, Windows, or Linux system that is physically attached to a RAID storage subsystem.

  • Page 18: Features

    1: Introduction Features TPM is designed to support the TP9100 external RAID subsystem. The TPM application provides the following functions: • Configuration: Adds, deletes, and modifies LUNs, topologies, and device status. • Administration: Configures controllers, administers LUNs, and takes controllers online and offline.

  • Page 19: Windows Software Packaging

    Software Packaging Files in the Distribution (IRIX and Linux) Table 1-1 (continued) Files Description Script or executable that discovers SCSI/Fibre Channel damioscan devices and LUNs. Executable file that monitors subystem health. tpmwatch Directory of image files displayed on various Web images/ pages.
  • Page 20 1: Introduction Files in the Distribution (Windows) Table 1-2 (continued) Files Description This executable provides the mailing function and is called dmail.exe from within the tpmwatch executable. The logo that is displayed on the main screen. images\oemlogo.gif The background image displayed on most Web pages. images\wallpaper.gif The username and password file that is validated during passwd.txt...

  • Page 21: Installing, Configuring, And Running Tpm On Irix, Linux, And Windows

    Chapter 2 Installing, Configuring, and Running TPM on IRIX, Linux, and Windows This chapter explains how to install and configure the TPM application on all operating systems. You may install TPM with other active users on the system if you wish. The entire process takes little time and no reboot is required.
  • Page 22 Please note the following information on operating system support: • TP9100 support for Linux has been frozen at Red Hat release 6.2 with Pro Pack 1.3, using TPM 1.0 with controller firmware 6.14, 7.01 and 7.03. Support for the TP9100 on newer releases of Linux will not be developed.

  • Page 23: Installing The Software

    Installing the Software Installing the Software This section describes how to install and uninstall the TPM software on the IRIX, Linux, and Windows platforms. Note: Prior to removing or upgrading the software, Tpm and TPMWatch must first be terminated. Installing TPM on IRIX Platforms Follow this procedure to install TPM on IRIX platforms: Log in as root.

  • Page 24: Uninstalling Tpm On Irix Platforms

    TPM software: rpm -iv /mnt/cdrom/unsupported/linux/rpm/sgi_tpm.rpm At the time of this writing, TP9100 will not operate with SGI ProPack 1.4. SGI ProPack 1.3 works properly with drive firmware 6.14; however, drive downloads to update firmware do not work. 007-4382-002...

  • Page 25: Uninstalling Tpm On Linux (Redhat 6.2 With Sgi Propack 1.3) Platforms

    2. Type the following Red Hat Package Manager (rpm) command to uninstall the TPM software: rpm -ev sgi_tpm At the time of this writing, TP9100 will not operate with SGI ProPack 1.4. SGI ProPack 1.3 works properly with drive firmware 6.14; however, drive downloads to update firmware do not work. 007-4382-002...

  • Page 26: Installing Tpm On Windows Nt 4.0 And Windows 2000 Advance Server Platforms

    2: Installing, Configuring, and Running TPM on IRIX, Linux, and Windows Installing TPM on Windows NT 4.0 and Windows 2000 Advance Server Platforms Log in as administrator. 2. Insert the TPM software CD-ROM into the CD-ROM drive. 3. Select Start –>Run and type the following in the Run dialog box: X:\unsupported\windows\setup.exe where X: corresponds to the drive letter of your CD-ROM drive, OR if you prefer, navigate to the \unsupported\windows folder on the CD-ROM and double click...

  • Page 27: Figure 2-2 License Agreement Dialog Box

    Installing the Software License Agreement Dialog Box Figure 2-2 5. Click Yes. The Choose Destination Location dialog box appears, as shown in Figure 2-3. 007-4382-002...

  • Page 28: Figure 2-3 Choose Destination Dialog Box

    Choose Destination Dialog Box Figure 2-3 6. You can accept the file installation default destination folder (C:\Program Files\SGI\SGI TP9100 Array Manager) or click Browse... to select a file installation different destination folder. 7. When you have selected a destination folder, click Next.

  • Page 29: Figure 2-4 Select Program Folder Dialog Box

    Installing the Software Select Program Folder Dialog Box Figure 2-4 8. Select the program folder for storing program icons and click Next. The Installation Complete dialog box appears, as shown in Figure 2-5. 007-4382-002...

  • Page 30: Figure 2-5 Installation Complete Dialog Box

    2: Installing, Configuring, and Running TPM on IRIX, Linux, and Windows Installation Complete Dialog Box Figure 2-5 9. Click Finish to complete the installation. 007-4382-002...

  • Page 31: Uninstalling Tpm On Windows Nt Or Windows 2000 Advanced Server Platforms

    To perform the uninstall, follow the procedure listed here. Go to Start –> Settings –> Control Panel and double-click Add/Remove Programs. 2. In the list that appears, select the SGI TP9100 Array Manager software entry and click Change/Remove. 3. Click Yes in the Confirm File Deletion dialog box.

  • Page 32: Invoking Tpm

    3. For sh, bash, or ksh SHELL, type: DAM_HOME=/opt/dam export DAM_HOME Starting SGI TP9100 Array Manager for IRIX and Linux Note: Only users with root permissions are allowed to run TPM. To start TPM, enter the following command: /opt/dam/tpm [-D][-W port_number] where port_number is the IP socket/port number required to access the program.

  • Page 33: Starting Sgi Tp9100 Array Manager For Windows

    • Double-click the SGI TP9100 Array Manager icon on the desktop. To turn on debug mode, right-click the SGI TP9100 Array Manager icon on the desktop and click Properties. On the resulting dialog box, add -D to the end of the entry in the Target text box (after the right-hand quote mark).
  • Page 34 2: Installing, Configuring, and Running TPM on IRIX, Linux, and Windows • http://server2.sgi.com:1234, or • http://192.200.200.10:1234 007-4382-002...

  • Page 35: Logon Screen

    Logon Screen Logon Screen After you invoke TPM, the logon screen appears in the browser window, as shown in Figure 2-6. Logon Screen Figure 2-6 Follow these steps to log on: Enter your username. 2. Enter your password. 3. Click Accept. The username and password entered are validated against the file $DAM_HOME/passwd.txt.

  • Page 36: Additional Considerations

    2: Installing, Configuring, and Running TPM on IRIX, Linux, and Windows Additional Considerations Below is a list of additional considerations. • Firewall administrators may block traffic on undefined port numbers such as 2002. Please talk with your security administrator to make sure you agree on what ports are acceptable for running TPM.

  • Page 37: Using Tpm

    Chapter 3 Using TPM This chapter explains how to use TPM to configure and monitor your external RAID disk subsystems. Note: The GUI screens vary according to the firmware (6.14, 7.01, 7.03, or 7.75) installed on the RAID controller. Where the screens are different, both are presented and explained.

  • Page 38: Figure 3-1 Main Menu (Partial Screen)

    3: Using TPM Main Menu (partial screen) Figure 3-1 Figure 3-1 shows a portion of the main menu window that appears once you log on. The main menu windows are different for 6.14, 7.01, 7.03, and 7.75 firmware. The differences will be explained as each menu item is explained in subsequent sections of this chapter.
  • Page 39 Main Menu undesired state. Instead, use the buttons and links that TPM presents at the bottom of each screen. The main menu window has the following principal areas, with the associated explanations on the indicated pages: • “Configuration Functions” on page 26 •...

  • Page 40: New Features

    3: Using TPM New Features This section lists the new firmware and TPM features. New Features for 7.75 Firmware Release on the FFx Controller Reboot On Crash This parameter controls the behavior of the Automatic Restart on Failure feature, and sets the following values: •...

  • Page 41: Specific New Functions For 7.75 Ffx Firmware/Tpm 1.2

    New Features 5. SAN Mapping Enhancement SAN mapping tables store up to 64 host WWNs. With 7.75 firmware, the WWN table was modified to enable the user to remove or delete unused host WWNs. The user can determine which host WWNs are obsolete and need to be removed from the WWN table.

  • Page 42: Configuration Functions

    3: Using TPM Configuration Functions The Configuration Function menu has the following selections, with the associated explanations on the indicated pages: • “Select Physical Device (Configuration Function Menu)” on page 27 • “Modify Disk Device Status (Configuration Function Menu)” on page 30 •...

  • Page 43: Select Physical Device (Configuration Function Menu)

    Configuration Functions Select Physical Device (Configuration Function Menu) To view a table of all devices and RAID subsystems, click the Select physical devices link under Configuration Functions in the main menu. The dialog box shown in Figure 3-2 appears. Figure 3-2 Select Physical Device Dialog Box By activating the desired checkbox under the Select column and clicking the Select button, you can select which RAID subsystem you wish to configure or monitor.
  • Page 44 3: Using TPM Operation It is important for the administrator to know how physical device selection works, because it can serve as a good general debugging tool in the event that your computer does not “see” a specific LUN. The algorithm is the same, regardless of the operating system.
  • Page 45 Qlogic device driver have been terminated first before you remove and reinstall the device driver. Note: Use the qla2100 driver for SGI ProPack1.3. The TP9100 cannot be used with ProPack 1.4. If all of the above remedies fail, a device might be masked because the controller is doing it intentionally.

  • Page 46: Modify Disk Device Status (Configuration Function Menu)

    These are additional fields reported by the OS that help identify the device driver. Channel, ID, LUN Type TPM reports all TP9100 RAID devices. Vendor ID The Vendor ID and Product ID parameters are returned by a standard SCSI Inquiry. You may wish to (SCSI Inquiry), note some interesting information reported by LUNs.

  • Page 47: Figure 3-3 Modify Disk Device Status Dialog Box (For 6.14 Firmware)

    Configuration Functions Modify Disk Device Status Dialog Box (for 6.14 Firmware) Figure 3-3 007-4382-002...

  • Page 48: Figure 3-4 Modify Disk Device Status Dialog Box

    3: Using TPM Figure 3-4 Modify Disk Device Status Dialog Box (for 7.01 and Later Firmware) 007-4382-002...
  • Page 49 Configuration Functions The Status dialog box for controllers with 7.01 and later firmware has the following additional information not displayed for the controllers with 6.14 firmware: • Drive Speed (in RPM) • WWN (worldwide name) The Modify Disk Device Status dialog box allows you not only quickly view status of the drives, but also to define hot spares.

  • Page 50: Table 3-2 Modify Disk Device Status Field Definitions

    3: Using TPM Field Definitions The definition of each field in the Modify Disk Device Status dialog box is given in Table 3-2. Table 3-2 Modify Disk Device Status Field Definitions Field Definition Make/Model/ This field returns the SCSI vendor ID, product ID, and firmware revision for each drive. For proper [Firmware] operation, it is strongly recommended that each drive in a LUN have the same make, model, and firmware release.
  • Page 51 Configuration Functions Finally, TPM does not care to which state you change a drive, so use common sense. If the Modify Disk Device Status screen shows that a drive is used within a LUN, and you change the drive from ON-LINE to some other state, data loss could result. 007-4382-002...

  • Page 52: Create/Destroy/Expand Logical Drives (Configuration Function Menu)

    3: Using TPM Create/Destroy/Expand Logical Drives (Configuration Function Menu) To set up new drive configurations or to add, delete, or expand drives in an existing configuration, select Create/Destroy/Expand Logical Drives under the Configuration Function menu. The dialog box shown in Figure 3-5 appears. Create/Destroy/Expand Logical Drives Dialog Box Figure 3-5 The Create/Destroy/Expand Logical Drives dialog box contains the following buttons:...
  • Page 53 Configuration Functions • Add a LUN: allows you to use free disk space to create one or more additional LUN(s). • Delete Last LUN: allows you to delete the last LUN that was defined. • Expand a LUN: allows you to add capacity to an existing LUN. Note: At the top of the screen is a link marked Click here.

  • Page 54: Figure 3-6 New Configuration Screen

    3: Using TPM New Configuration When you click New Configuration, the screen appears as shown in Figure 3-6. New Configuration Screen Figure 3-6 You may create a new LUN configuration if presently there are no configured LUNs in your array. Drive packs can be spanned, which provides the ability to configure multiple or parts of multiple drive packs as one system drive.
  • Page 55 Configuration Functions • The maximum number of packs that can be combined into a LUN is four for controllers with 6.14 firmware. • The maximum number of packs that can be combined into a LUN is 16 for controllers with 7.01 and later firmware. •...
  • Page 56 LUN, or volume (.999 terabyte (2147483647 blocks [1099511627264 bytes]) required for fx volume header). Because the maximum supported TP9100 LUN capacity size is 2 terabytes, a bug has been submitted requesting that changes be made to Irix infrastructure (for example, fx, prtvtoc, and so on) in order to support a 2 terabyte LUN (1.999 terabytes (4294967295 blocks [2199023255040 bytes]) required for fx volume...

  • Page 57: Figure 3-7 Drives Assigned Into Pack A (6.14 Firmware)

    Configuration Functions Group the First Set of Drives into a Pack To group the first set of drives into a pack, follow these directions: Activate the desired checkboxes in the RAID Subsystems area of the dialog box (see Figure 3-6) and click Select Marked to move drives from the map shown in the RAID Subsystems area of the screen into Pack A.

  • Page 58: Figure 3-8 Drives Assigned Into Pack A (7.01 And Later Firmware)

    3: Using TPM Drives Assigned Into Pack A (7.01 and Later Firmware) Figure 3-8 Figure 3-7 and Figure 3-8 show that four drives have been assigned into drive pack A, which could become a RAID set. Every time a set of drives is assigned, the table cell labeled Next Assign moves to the next row down, where a new drive pack can be created.

  • Page 59: Figure 3-9 All Drive Packs Created (6.14 Firmware)

    Configuration Functions Group the Remaining Drives Into Packs To create remaining drive packs, continue activating drive checkboxes in the RAID Subsystem area of the dialog box and using the Select Next Pack button as necessary until the drives are grouped as desired into separate drive packs. Note: Refer to “New Configuration”...

  • Page 60: Figure 3-10 All Drive Packs Created (7.01 And Later Firmware)

    3: Using TPM Figure 3-10 All Drive Packs Created (7.01 and Later Firmware) 007-4382-002...

  • Page 61: Figure 3-11 Select Drive Packs To Include In Lun

    Configuration Functions Defining a LUN Using the Drive Packs To define a LUN, follow these steps: Click Define LUNs. The screen shown in Figure 3-11 appears. Figure 3-11 Select Drive Packs to Include in LUN 2. Check the boxes at the left (A, B, or C) to select one or more packs to combine into a LUN.

  • Page 62: Figure 3-12 Lun Is Being Defined (6.14 Firmware)

    3: Using TPM Note: For controllers with 6.14 firmware, you must go to the View/Modify RAID Controller Configuration dialog box (see Figure 3-50 on page 87) and select the stripe size before defining the LUN. Figure 3-12 LUN is Being Defined (6.14 Firmware) 007-4382-002...

  • Page 63: Figure 3-13 Lun Is Being Defined (7.01 And Later Firmware)

    Configuration Functions Figure 3-13 LUN is Being Defined (7.01 and Later Firmware) These dialog boxes show that a Logical Drive #0 (LUN 0) is being created that allows you to select the RAID level and usable MB. 4. Select the desired RAID level from the drop-down box shown. 5.

  • Page 64: Figure 3-14 Lun Is Defined

    3: Using TPM Figure 3-14 LUN is Defined The right-hand side of the table shows how the LUN is physically arranged on each disk drive. 6. To continue building LUNs that incorporate drives in other packs, click Select Pack(s) and repeat the process of defining LUNs and their corresponding RAID levels and usable MB.

  • Page 65: Figure 3-15 All Luns Defined (6.14 Firmware)

    Configuration Functions Figure 3-15 All LUNs Defined (6.14 Firmware) 007-4382-002...

  • Page 66: Figure 3-16 All Luns Defined (7.01 And Later Firmware)

    3: Using TPM Figure 3-16 All LUNs Defined (7.01 and later Firmware) At this point, all the LUNs have been defined. Next, the RAID controller must be updated with the new configuration. 007-4382-002...

  • Page 67: Figure 3-17 Updating The Raid Controller Warning Screen

    Configuration Functions Updating the RAID Controller To update the RAID controller with the new LUN configuration, follow these steps: Press the Next Screen button. For 6.14, 7.01, and 7.03 firmware, the warning screen shown Figure 3-17 appears. Figure 3-17 Updating the RAID Controller Warning Screen (6.14, 7.01, and 7.03 Firmware) For 7.75 firmware, the warning screen shown Figure 3-18 appears.

  • Page 68: Figure 3-19 Lun Online Screen (6.14, 7.01, And 7.03 Firmware Only)

    3: Using TPM Figure 3-19 LUN Online Screen (6.14, 7.01, and 7.03 firmware only) Figure 3-20 LUN Online Screen (7.75 firmware only) For 6.14, 7.01, and 7.03 Firmware: 5. Click the Create/Destroy/Expand Logical Drive(s) button if you want to add more LUNs or reconfigure existing LUNs.

  • Page 69: Figure 3-21 Warning Screen (6.14, 7.01, And 7.03 Firmware)

    Configuration Functions The screen shown in Figure 3-21 appears. Figure 3-21 Warning Screen (6.14, 7.01, and 7.03 Firmware) Note: If you are adding a new LUN to an existing configuration, you should unmount any LUNs before resetting. This is especially important if there is a possibility that the host will attempt to issue any I/Os to the LUNs before the controller(s) finish rebooting.

  • Page 70: Figure 3-23 Controller Resetting Status Screen (1 Of 2)

    3: Using TPM A reset is required, and is not optional. The reason that TPM even asks you about initiating a reset is to give you the chance to make sure your host(s) are ready for a reset. For 6.14, 7.01, and 7.03 firmware, the two Reset Status Information windows appear, as shown in Figure 3-23 and Figure 3-24.
  • Page 71 Configuration Functions 8. Click Close This Window on the dialog box shown in Figure 3-24. After the controller(s) are reset (for 6.14, 7.01, and 7.03 firmware only), you must return to the main menu and do the following: Install the device driver for the new LUN (see “Installing Device Drivers for New LUNS (Configuration Function Menu)”...

  • Page 72: Figure 3-25 Create/Destroy/Expand Logical Drives Screen (6.14 Firmware)

    3: Using TPM Add LUN(s) Back at the main menu, click select Create/Destroy/Expand Logical Drives under the Configuration Function menu. The screen shown in Figure 3-25 appears for 6.14, 7.01, and 7.03 firmware. For 7.75 firmware, the screen shown in Figure 3-26 appears. Figure 3-25 Create/Destroy/Expand Logical Drives Screen (6.14 Firmware) 007-4382-002...

  • Page 73: Figure 3-26 Create/Destroy/Expand Logical Drives Screen

    Configuration Functions Figure 3-26 Create/Destroy/Expand Logical Drives Screen (7.01 and Later Firmware) To add one or more LUNs, follow these directions: Click Add LUN(s). A screen similar to the one in Figure 3-27 on page 58 appears. 007-4382-002...

  • Page 74: Figure 3-27 Add Lun(S) Screen

    3: Using TPM Figure 3-27 Add LUN(s) Screen To add a LUN to an existing configuration, at least one LUN must already exist. In addition, unconfigured disks must be available with enough disk space to create an additional LUN. 2. Follow essentially the same procedures as before listed under “New Configuration” on page 38.

  • Page 75: Figure 3-28 Add Lun(S) Warning Screen (6.14, 7.01, And 7.03 Firmware)

    Configuration Functions • Although you can fill out the screens, you must not attempt to save the configuration using the Next Screen button while users are online, because a controller reset is required. 3. When you have finished defining the new LUN, click Next Screen. The warning screen shown in Figure 3-28 appears for 6.14, 7.01, and 7.03 firmware.

  • Page 76: Figure 3-30 Add Lun(S) Confirmation Screen (6.14, 7.01, And 7.03 Firmware) . 60 Figure 3-31 Add Lun(S) Confirmation Screen (7.75 Firmware)

    3: Using TPM Figure 3-30 Add LUN(s) Confirmation Screen (6.14, 7.01, and 7.03 Firmware) 6. Click RESET CONTROLLER if no more LUNs are to be added, or Create/Destroy/Expand Logical Drives if you need to add more LUNs. If you select Create/Destroy/Expand Logical Drives, you are returned to the dialog box of Figure 3-25 on page 56.

  • Page 77: Figure 3-32 Delete Lun Warning Screen

    Configuration Functions Delete LUN Use the Delete LUN button on the Create/Destroy/Expand Logical Drives screen (see Figure 3-25) to delete a LUN. To delete a LUN, follow these directions: Click Delete LUN. The warning screen shown in Figure 3-32 on page 61 is displayed. This screen shows the size and characteristics of the last LUN that was created.
  • Page 78 3: Using TPM Expand LUN RAID expansion allows capacity to be added to an existing RAID set while the controller is online. No resets are required, and I/Os to other LUNs will be serviced (a little slower). The following rules and conditions must be met to expand a LUN: Note: SGI does not support LUN Expansion and MORE operations on the IRIX and Linux operating systems The most important rule is that you must be using a file manager such as Veritas’...
  • Page 79 Configuration Functions 10. In the event of a disk drive failure, the process continues to completion in CRITICAL mode. 11. MORE, Initialize, Rebuild, and Consistency Check are mutually exclusive operations. Only one process may run at a time. 12. No configuration update commands will be accepted during the expansion. 13.

  • Page 80: Figure 3-33 Create/Destroy/Expand Logical Drives Screen (6.14 Firmware)

    3: Using TPM Click Expand LUN in the Create/Destroy/Expand Logical Drives screen (see Figure 3-33 for 6.14 firmware, and Figure 3-34 for 7.01 and later firmware). Figure 3-33 Create/Destroy/Expand Logical Drives Screen (6.14 Firmware) 007-4382-002...

  • Page 81: Figure 3-34 Create/Destroy/Expand Logical Drives Screen

    Configuration Functions Figure 3-34 Create/Destroy/Expand Logical Drives Screen (7.01 and Later Firmware) A screen similar to that shown in Figure 3-35 appears. 007-4382-002...

  • Page 82: Figure 3-35 Expand Lun Screen

    3: Using TPM Figure 3-35 Expand LUN Screen Note: In the screen shown in Figure 3-35, one disk drive has just been added to drive pack A, leaving three unused disk drives that can still be used to expand a LUN. The drives shown in green are in an online state, which means they are configured into LUNs which happen to be online.

  • Page 83: Figure 3-36 Warning Message

    Configuration Functions 3. When you have finished adding drives to a particular pack, use the Select Another Pack button to select and expand another pack, or click EXPAND Selected LUN button to finish the LUN expansion process. If you click EXPAND Selected LUN, the warning message shown in Figure 3-36 appears.

  • Page 84: Initialize Lun(S) (Configuration Function Menu)

    3: Using TPM Initialize LUN(s) (Configuration Function Menu) The LUNs must be initialized before the operating system can use them. The TPM application automatically selects uninitialized LUNs for you and displays their status (INITIALIZED, UNINITIALIZED, or INITIALIZING). To initialize one or more LUNs, follow these steps: Click Initialize LUNs on the main menu.

  • Page 85: Figure 3-38 Initialize Lun (7.75 Firmware)

    Configuration Functions Figure 3-38 Initialize LUN (7.75 Firmware) Note: Do not initialize LUNs in the background from this screen. Instead, Click Initialize LUNs in Background on the main menu (see “Initialize LUNs in Background (Configuration Function Menu)” on page 73). The “Background Init”...

  • Page 86: Figure 3-39 Initialization Confirmation

    3: Using TPM As shown in Figure 3-37, several LUNs are shown as UNINITIALIZED. 2. Type YES in the boxes corresponding to the devices to initialize, and click Initialize at the bottom of the screen. The initialization confirmation screen shown in Figure 3-39 appears. Figure 3-39 Initialization Confirmation 3.

  • Page 87: Figure 3-40 Initialization Progress (6.14 Firmware)

    Configuration Functions Figure 3-40 Initialization Progress (6.14 Firmware) 007-4382-002...

  • Page 88: Figure 3-41 Initialization Progress (7.01 And Later Firmware)

    3: Using TPM Figure 3-41 Initialization Progress (7.01 and Later Firmware) The initialization procedure can be done at any time, and the controller(s) will service I/Os for other LUNs while this is in process. There is also a configurable parameter in the controller configuration that allows you to adjust how much controller CPU time to allow for background operations such as this.

  • Page 89: Initialize Luns In Background (Configuration Function Menu)

    Configuration Functions Initialize LUNs in Background (Configuration Function Menu) Background initialization makes uninitialized system drives consistent by setting the parity while allowing the host to have instantly available read and write access to the system drive. Background initialization is implemented only in version 7.75 and later firmware.

  • Page 90: Figure 3-42 Initialize Luns In Background (7.75 Firmware)

    3: Using TPM Figure 3-42 Initialize LUNs in Background (7.75 Firmware) 2. Click INITIALIZE. The screen shown in appears. Figure 3-43 Initialize LUNs in Background (7.75 Firmware) 3. Click OK. Background initialization now begins and initializes any uninitialized system drives one at a time, and is paused by any of the following operations: 007-4382-002...
  • Page 91 Configuration Functions • Foreground Initialization • Consistency Check and Restore • Rebuild If one of these operations is started while background initialization is executing, background initialization is paused until the interrupting operation is complete. Once paused, background initialization will only continue after a write operation to the LUN. The same is true of a controller reset.

  • Page 92: Configure Host-To-Lun Mapping (Configuration Function Menu)

    Figure 3-44, the SAN Map is the current mapping strategy. Note: SAN MAP is the only mapping strategy supported by the TP9100 RAID system. Click SAN MAP to make any modifications to the mapping strategy. No changes are made until you complete the subsequent dialog boxes.
  • Page 93 Configuration Functions Heed these important warnings: Warning: A reset is required if you change the mapping type (for example, from SAN to Affinity), or the topology type within SAN mapping. You can, however, set things up and postpone the reset until you have some downtime available. Warning: If you make a change to the mapping, be sure to consider how the new mapping might affect device drivers on attached systems.

  • Page 94: Figure 3-45 Storage Area Network

    3: Using TPM SAN Mapping The Storage Area Network (SAN) Mapping feature, also known as Host-to-LUN Mapping feature, restricts host access to logical drives. Each drive is granted only to a single host or group of hosts, providing limited security control of data in an environment where multiple hosts are connected to the controller.
  • Page 95 Configuration Functions If IRIX or Linux computers are involved, then an automatic mount might not occur, but you still have a security risk, and the possibility that a user with root privilege will mount one of these disks, or attempt to create a file system on one of these disks. By utilizing SAN mapping, however, each logical drive can be configured to be visible to a single host computer only.
  • Page 96 3: Using TPM Supported SAN Mapping Topologies The model of controller you use dictates what SAN Mapping topologies are supported. This manual covers all three possibilities (Inactive Port, MultiPort, and Multi-TID). Only one type of SAN topology can be active, and any changes to a topology requires a reboot for it to become effective.

  • Page 97: Figure 3-46 San Mapping

    Configuration Functions Figure 3-46 SAN Mapping Regardless of the topology, the bottom portion of the screen shown in Figure 3-46 will be the same. Administrators must first choose the topology that best matches the SAN environment, then configure the mapping. To change the topology, click the Topology drop down box, then press the Select button.
  • Page 98 3: Using TPM Warning: A reset is required if you change the mapping type (for example, from SAN to Affinity), or the topology type within SAN mapping. You can, however, set things up and postpone the reset until you have some downtime available. Warning: If you make a change to the mapping, be sure to consider how the new mapping might affect device drivers on attached systems.

  • Page 99: Installing Device Drivers For New Luns (Configuration Function Menu)

    Configuration Functions Installing Device Drivers for New LUNS (Configuration Function Menu) Selecting this item on the main menu (see “Main Menu” on page 21) instructs TPM to tell the host computer to scan for new devices and update device drivers. To initiate this process, click Install device drivers for new LUNS on the main menu.

  • Page 100: Send Command To Host (Configuration Function Menu)

    3: Using TPM Send Command to Host (Configuration Function Menu) Use this function to spawn a command line to the IRIX/Linux host that you are communicating with. Note: The Windows OS does not support Send Command to Host. Therefore, it does not appear on the main menu.

  • Page 101: Administrative Functions

    Administrative Functions Administrative Functions The Administrative Functions menu is located on the main screen and is shown in Figure 3-49. Figure 3-49 Administrative Functions Menu This menu has the following selections, with the associated explanations on the indicated pages: • “View/Modify RAID Controller Configuration”...

  • Page 102: View/Modify Raid Controller Configuration

    3: Using TPM View/Modify RAID Controller Configuration This menu selection lets you make changes to your controller. The most important thing to know is that changes labeled On-the-fly are immediate. Those marked Reset require a controller reset to become effective. The two choices labeled New Config can only be made when there are no defined LUNs, as they are data-destructive.

  • Page 103: Figure 3-50 View/Modify Controller Configuration (Partial For 6.14 Firmware)

    Administrative Functions Figure 3-50 View/Modify Controller Configuration (partial for 6.14 Firmware) 007-4382-002...

  • Page 104: Figure 3-51 View/Modify Controller Configuration (Partial For 6.14 Firmware)

    3: Using TPM Figure 3-51 View/Modify Controller Configuration (partial for 6.14 Firmware) 007-4382-002...

  • Page 105: Figure 3-52 View/Modify Controller Configuration (Partial For 7.01 Firmware)

    Administrative Functions Figure 3-52 View/Modify Controller Configuration (partial for 7.01 Firmware) 007-4382-002...

  • Page 106: Figure 3-53 View/Modify Controller Configuration (Partial For 7.01 Firmware)

    3: Using TPM Figure 3-53 View/Modify Controller Configuration (partial for 7.01 Firmware) 007-4382-002...

  • Page 107: Figure 3-54 View/Modify Controller Configuration (Partial For 7.75 Firmware)

    Administrative Functions Figure 3-54 View/Modify Controller Configuration (partial for 7.75 Firmware) 007-4382-002...
  • Page 108 3: Using TPM Figure 3-55 View/Modify Controller Configuration (partial for 7.75 Firmware) 007-4382-002...

  • Page 109: Figure 3-56 View/Modify Controller Configuration (Partial For 7.75 Firmware)

    Administrative Functions Figure 3-56 View/Modify Controller Configuration (partial for 7.75 Firmware) 007-4382-002...
  • Page 110 3: Using TPM The following selections appear on the 6.14 firmware dialog box that do not appear on the 7.01 and later firmware dialog box: • Stripe Size. In controllers with 7.01 and later firmware, the stripe size is selected when the LUN is being defined (see Figure 3-13 on page 47).

  • Page 111: Reset Controller(S)

    Administrative Functions Reset Controller(s) When the Reset Controller(s) menu selection is made, the screen shown in Figure 3-57 appears. Figure 3-57 Reset Controllers Warning Screen Click YES if you wish to reset your controller. If the system is a dual-controller configuration, clicking YES resets both controllers.

  • Page 112: Gracefully Bring A Controller Off Line

    3: Using TPM Figure 3-59 Controller Responding Window As a protective measure, if the controllers are busy servicing I/Os, the Reset command will not be accepted. Gracefully Bring a Controller Off Line When the Gracefully Bring a Controller Off Line menu selection is made, the screen shown in Figure 3-60 appears.

  • Page 113: Gracefully Bring A 2Nd Controller On Line

    Administrative Functions Gracefully Bring a 2nd Controller On Line When the Gracefully Bring a 2nd Controller On Line menu selection is made, the screen shown in Figure 3-61 appears. Figure 3-61 Warning Screen When a failed controller is replaced, the system either automatically detects the replacement (if configured for automatic failback), or is informed of the replacement by issuing this command.

  • Page 114: Perform Data Consistency Operations On A Lun

    3: Using TPM Perform Data Consistency Operations on a LUN When the Perform Data Consistency Check/Restore LUN menu selection is made, the screen shown in Figure 3-62 appears. Figure 3-62 Data Consistency Check/Restore Note: A check consistency will pause any background initialization process. Background initialization will not restart until a write is sent to the LUN against which background initialization was paused.

  • Page 115: Figure 3-63 Operation Started Dialog Box

    Administrative Functions If you click EXECUTE to begin execute any of the check or restore actions, the dialog box of Figure 3-63 appears, indicating that the process has started. Figure 3-63 Operation Started Dialog Box Click OK to proceed. The window shown in Figure 3-64 (for 6.14 firmware), Figure 3-65 (for 7.01 and 7.03 firmware), and Figure 3-66 (for 7.75 firmware) shows the progress a few minutes after initiating a Check and Restore for Logical Drive #0, and 15 minutes after starting a LUN Initialization (format).

  • Page 116: Figure 3-64 Background Initialization Status Screen (6.14 Firmware)

    3: Using TPM Figure 3-64 Background Initialization Status Screen (6.14 Firmware) 007-4382-002...

  • Page 117: Figure 3-65 Background Initialization Status Screen (7.01 And 7.03 Firmware)

    Administrative Functions Figure 3-65 Background Initialization Status Screen (7.01 and 7.03 Firmware) 007-4382-002...

  • Page 118: Figure 3-66 Background Initialization Status Screen (7.75 Firmware)

    3: Using TPM Figure 3-66 Background Initialization Status Screen (7.75 Firmware) 007-4382-002...

  • Page 119: Enable/Disable Write Cache For Lun(S)

    Administrative Functions Enable/Disable Write Cache for LUN(s) When the Enable/Disable Write Cache for LUN(s) menu selection is made, the dialog box shown in Figure 3-67 appears. Figure 3-67 Enable Write Cache For LUN(s) Select the LUNs where you want the cache enabled or disabled and click Apply at the bottom of the screen.

  • Page 120: Modify/Purge Non-Volatile Wwn Tables

    3: Using TPM Modify/Purge Non-Volatile WWN Tables When the Modify/Purge Non-Volatile WWN Tables menu selection is made, the dialog box shown in Figure 3-68 appears. Figure 3-68 World Wide Name Table for RAID Controller The World Wide Name (WWN) table feature has been modified with firmware version 7.75 to include a delete WWN from WWN table option.The number of supported host WWNs is 64.
  • Page 121 Administrative Functions Note: All SAN mapping assignments created using firmware version 7.75 are lost if the firmware is downgraded to previous firmware version. A controller currently maintains a host WWN table until the configuration is cleared. As WWNs are removed and the WWN table updated, any WWNs following those deleted are moved up to fill the vacancies in the WWN table.

  • Page 122: Reporting Functions

    3: Using TPM Reporting Functions The Reporting Functions menu is located on the main screen and is shown in Figure 3-69 for 6.14 controller firmware and in Figure 3-70 for 7.01 and later controller firmware. Figure 3-69 Reporting Functions Menu (for 6.14 Firmware) Figure 3-70 Reporting Functions Menu (for 7.01 and Later Firmware) The Reporting Functions menu has the following selections, with the associated explanations on the indicated pages:...

  • Page 123: Set Default Screen Refresh Rate

    Reporting Functions • “Display Statistical Data by Logical (RAID) Disk (6.14 Firmware Only)” on page 110 • “Display SCSI/Fibre Device Information” on page 111 • “Display FULL Subsystem Configuration Information” on page 112 • “Display Physical Subsystem Information” on page 114 •...

  • Page 124: Display (Dual) Controller Status

    3: Using TPM Display (Dual) Controller Status When the Display (Dual) Controller Status menu selection is made, the screen shown in Figure 3-72 appears. Figure 3-72 Controller Status Information This Screen displays information about the controller(s) and whether or not they are working together.

  • Page 125: Topology Query

    Reporting Functions Topology Query When the Topology Query menu selection is made, the screen shown in Figure 3-73 appears. Figure 3-73 Topology Query This screen displays a list of Fibre Channel host adapters that are (or were) attached to the RAID controller. Use this screen to view limited topology information. Note: This is a read-only display.

  • Page 126: Display Statistical Data By Physical Device

    3: Using TPM Display Statistical Data by Physical Device Note: This function is not supported by the TP9100 RAID system. It is only for JBOD environments. Display Statistical Data by Logical (RAID) Disk (6.14 Firmware Only) When the Display Statistical Data by Logical RAID Disk menu selection is made, the screen shown in Figure 3-74 appears.

  • Page 127: Display Scsi/Fibre Device Information

    Reporting Functions Display SCSI/Fibre Device Information When the Display SCSI/Fibre Device Information menu selection is made, the screen shown in Figure 3-75 appears. Figure 3-75 Display SCSI/Fibre Device Information The screen shows what the standard SCSI inquiry returns for a device or LUN. Use it for diagnostic reasons, or to help analyze any SCSI or Fibre Channel device attached to your computer.

  • Page 128: Display Full Subsystem Configuration Information

    3: Using TPM Display FULL Subsystem Configuration Information When the Display FULL Subsystem Configuration Information menu selection is made, the Controller Information Values (see Figure 3-76), Controller Tunable Parameters (see Figure 3-77), and GroupConfig Structure (see Figure 3-78) screens appear. Figure 3-76 Controller Information Values (partial screen) Figure 3-77 Controller Tunable Parameters 007-4382-002...

  • Page 129: Figure 3-78 Groupconfig Structure

    Reporting Functions Figure 3-78 GroupConfig Structure These screens contain hexadecimal dump information from the controller configuration file. This would be of interest to the technical support group in the event of a problem, or would prove helpful to verify that several subsystem configurations have properly been cloned.

  • Page 130: Display Physical Subsystem Information

    3: Using TPM Display Physical Subsystem Information When the Display Physical Subsystem Information menu selection is made, the screen shown in Figure 3-79 and Figure 3-80 appear (for controllers with 6.14 firmware). Figure 3-81 and Figure 3-82 appear for controllers with 7.01 and later firmware. Figure 3-79 Physical Subsystem Information (partial for 6.14 Firmware) 007-4382-002...

  • Page 131: Figure 3-80 Physical Subsystem Information (Partial For 6.14 Firmware)

    Reporting Functions Figure 3-80 Physical Subsystem Information (partial for 6.14 Firmware) 007-4382-002...

  • Page 132: Figure 3-81 Physical Subsystem Information

    3: Using TPM Figure 3-81 Physical Subsystem Information (partial for 7.01 and later Firmware) 007-4382-002...

  • Page 133: Figure 3-82 Physical Subsystem Information

    Reporting Functions Figure 3-82 Physical Subsystem Information (partial for 7.01 and later Firmware) The 7.01 and later controller firmware returns WWN and Drive Speed information, which are not returned by controllers with 6.14 firmware. These screens shows statistical data, drive status, and errors for all drives in all subsystems.

  • Page 134: Display Logical Subsystem Information

    3: Using TPM Display Logical Subsystem Information When the Display Logical Subsystem Information menu selection is made, the windows shown in Figure 3-83 (for controllers with 6.14 firmware) and Figure 3-84 (for controllers with 7.01 and later firmware) appear. Figure 3-83 Logical Subsystem Information (partial for 6.14 Firmware) 007-4382-002...

  • Page 135: Figure 3-84 Logical Subsystem Information

    Reporting Functions Figure 3-84 Logical Subsystem Information (partial for 7.01 and Later Firmware) The 7.01 and later controller firmware returns a Background Task status line, which is not returned by controllers with 6.14 firmware. The screen shows all configured LUNs, their status, mapping information, and how they are laid out.

  • Page 136: Display Environmental Subsystem Information

    3: Using TPM Display Environmental Subsystem Information When the Display Environmental Subsystem Information menu selection is made, the screen shown in Figure 3-85 (for controllers with 6.14 firmware) and Figure 3-86 (for controllers with 7.01 and later firmware) appears. Figure 3-85 Display Environmental Subsystem Information (6.14 Firmware) 007-4382-002...

  • Page 137: Figure 3-86 Display Environmental Subsystem Information

    Reporting Functions Figure 3-86 Display Environmental Subsystem Information (7.01 and Later Firmware) The two windows for the different controller firmware versions contain the same information, but arranged differently. The windows display status information results of polling the enclosure (and all expansion enclosures) every 10 seconds. Note: If expansion enclosures are attached, all of the same information would be reported for them as well, only with a different Enclosure ID.

  • Page 138: Miscellaneous Functions

    3: Using TPM Miscellaneous Functions The Miscellaneous Functions menu is located on the main screen and is shown in Figure 3-87. Figure 3-87 Miscellaneous Functions Menu (for 6.14 Firmware) Figure 3-88 Miscellaneous Functions Menu (for 7.01 and Later Firmware) The Reporting Functions menu has the following selections, with the associated explanations on the indicated pages: •...

  • Page 139: Figure 3-95 Load Controller Configuration

    Miscellaneous Functions • “Load Controller Configuration” on page 129 • “Flash New Firmware Onto Controller(s)” on page 130 • “Flash New Firmware Onto Supported Disk(s)” on page 131 • “Adjust Battery Settings” on page 134 • “Clear Configuration” on page 136 •...

  • Page 140: Figure 3-89 Display Status Of Background Jobs (6.14 Firmware)

    3: Using TPM Display Status of Background Jobs When the Display Status of Background Jobs menu selection is made, the windows appear as shown in Figure 3-89 (for 6.14 firmware) and Figure 3-89 (for 7.01 and later firmware) appear. Figure 3-89 Display Status of Background Jobs (6.14 Firmware) 007-4382-002...

  • Page 141: Figure 3-90 Display Status Of Background Jobs (7.01 And Later Firmware)

    Miscellaneous Functions Figure 3-90 Display Status of Background Jobs (7.01 and Later Firmware) Note: If a background init is in progress (7.75 firmware), the screen shown in Figure 3-91 appears. 007-4382-002...

  • Page 142: Figure 3-91 Display Status Of Background Jobs-Background Init In Progress (7.75 Firmware)

    3: Using TPM Figure 3-91 Display Status of Background Jobs—Background Init in Progress (7.75 Firmware) These windows show you how initialization, rebuilds, or checks are progressing. The browser title bar (not shown in Figure 3-90) displays the date and time of the last poll. Press the [Return to Main Page] link to exit.

  • Page 143: Flush Controller(S) Write Cache To Disk

    Miscellaneous Functions Flush Controller(s) Write Cache to Disk When the Flush Controller(s) Write Cache to Disk menu selection is made, the screen shown in Figure 3-92 appears. Figure 3-92 Cache Flush Warning Click YES to force a cache flush. You would ordinarily perform this after all LUNs are unmounted, and before a power down.

  • Page 144: Figure 3-94 Save Current Controller Configuration

    3: Using TPM Save Current Controller Configuration When the Save Current Controller Configuration menu selection is made, the screen shown in Figure 3-94 appears. Figure 3-94 Save Current Controller Configuration To save the current controller configuration to a file, type the name of the file in the area provided on the screen and click SAVE Configuration.

  • Page 145: Load Controller Configuration

    Miscellaneous Functions Load Controller Configuration When the Load Controller Configuration menu selection is made, the screen shown in Figure 3-95 appears. Figure 3-95 Load Controller Configuration This screen allows you to load the controller configuration file into another RAID array. You can use this feature to clone a RAID configuration.

  • Page 146: Flash New Firmware Onto Controller(S)

    3: Using TPM Flash New Firmware Onto Controller(s) When the Flash New Firmware Onto Controller(s) menu selection is made, the screen shown in Figure 3-96 appears. Figure 3-96 Flashing New Firmware Warning: If you attempt to flash new firmware to the disk drive or controller while background jobs are running (the drive is transferring data), drive operation could become unpredictable and the drive may even become inoperable.

  • Page 147: Flash New Firmware Onto Supported Disk(S)

    Miscellaneous Functions Flash New Firmware Onto Supported Disk(s) When the menu selection is made, the screen Flash New Firmware Onto Supported Disk(s) shown in Figure 3-97 appears (provided that the Operational Fault Management and Auto Rebuild Management functions on the View/Modify RAID Controller Configuration dialog box are not disabled—see Figure 3-52 on page 89).

  • Page 148: Figure 3-98 Flash New Firmware Dialog Box

    3: Using TPM Go to the Administrative Functions menu and click Reset Controllers (see Figure 3-57 on page 95). After the reset is complete, click the Flash New Firmware Onto Supported Disk(s) menu selection. The dialog box shown in Figure 3-98 appears. Figure 3-98 Flash New Firmware Dialog Box Read all the instructions on the dialog box, select one or more devices to flash, then click FLASH to flash the firmware.

  • Page 149: Figure 3-99 Flash New Firmware Complete Box

    Miscellaneous Functions Figure 3-99 Flash New Firmware Complete Box Wait 120 seconds, as the screen instructs, then cycle the power. After power up and reboot are complete, enable the Operational Fault Management and Auto Rebuild Management functions on the View/Modify RAID Controller Configuration dialog box. 007-4382-002...

  • Page 150: Adjust Battery Settings

    3: Using TPM Adjust Battery Settings When the Adjust Battery Settings menu selection is made, the screen shown in Figure 3-100 appears for 6.14, 7.01, and 7.03 firmware. The screen shown in appears for 7.75 firmware. Figure 3-100 Adjust Battery Settings (6.14, 7.01, and 7.03 Firmware) Figure 3-101 Adjust Battery Settings (7.75 Firmware) 007-4382-002...
  • Page 151 Miscellaneous Functions When the remaining battery power (in minutes) falls below the Battery Threshold (minutes) value entered, a low battery power alarm is triggered and is displayed in the Battery Backup Status portion of the Display Environmental Subsystem Information window (see Figure 3-85 on page 120 and Figure 3-86 on page 121). The buttons at the bottom of the screen operate as follows: •...

  • Page 152: Clear Configuration

    3: Using TPM Clear Configuration When the Clear Configuration menu selection is made, the screen shown in Figure 3-102 appears. Figure 3-102 Clear Configuration Warning: Read the information in the screen before you take any action. To erase the configuration structures, click CLEAR. The confirmation message shown in Figure 3-103 appears.

  • Page 153: Set The Real Time Clock (7.01 And Later Firmware Only)

    Miscellaneous Functions Set The Real Time Clock (7.01 and Later Firmware Only) When the Set Real Time Clock menu selection is made, the dialog box shown in Figure 3-104 appears. Figure 3-104 Set Real Time Clock Click SET CLOCK to synchronize the controller clock with the host computer. The confirmation screen shown in Figure 3-105 appears.

  • Page 154: View The Controller's Internal Event Log (7.01 And Later Firmware Only)

    3: Using TPM View the Controller’s Internal Event Log (7.01 and later Firmware Only) When the View the Controller’s Internal Event Log menu selection is made, the dialog box shown in Figure 3-106 appears. Figure 3-106 View Controller’s Internal Event Log Each time you bring up this dialog box, it displays the events that occurred since the last time the dialog box was brought up.
  • Page 155 Miscellaneous Functions • Append New: appends new events to the raw data text file named eventhistory.log file. • View All Events: displays all events, including old and new events. Note: If you are running gamevent on the system, this button must be used to see all log events, because gamevent is continually emptying the event log.

  • Page 156: Identify A Disk (7.01 And Later Firmware Only)

    3: Using TPM Identify a Disk (7.01 and later Firmware Only) For the Identify a Disk menu selection to work properly, Operational Fault Management (OFM) must be enabled. This is accomplished by enabling the Operational Fault Management function in the View/Modify RAID Controller Configuration dialog box (see Figure 3-52 on page 89).

  • Page 157: Figure 3-108 Ses Drive Locations (Tower Configuration)

    Miscellaneous Functions SES Drives Figure 3-108 SES Drive Locations (Tower Configuration) When the Identify a Disk menu selection is made, the dialog box shown in Figure 3-109 appears. 007-4382-002...

  • Page 158: Figure 3-109 Identify A Disk

    3: Using TPM Figure 3-109 Identify a Disk Click PING to identify a selected drive. 007-4382-002...

  • Page 159: Scan For New Enclosures And Disks

    Miscellaneous Functions Scan for New Enclosures and Disks When the Scan for New Enclosures and Disks menu selection is made (7.75 firmware), the dialog box shown in Figure 3-110 appears. Figure 3-110 View Controller’s Internal Event Log (7.75 Firmware) This feature allows users to add one or more disk enclosures to a configured system while the system continues to operate.
  • Page 160 3: Using TPM 7. After the SES process completes polling the loop, the new enclosures and disk drives are ready for configuration. 8. If the new enclosure(s) are not detected, remove and insert a disk drive from the new enclosure. Removing and inserting a disk drive generates an LIP, and the new disk drives will join the existing fibre loop.

  • Page 161: Save Controller Debug Dump

    Miscellaneous Functions Save Controller Debug Dump When the Save Controller Debug Dump menu selection is made (7.75 firmware), the dialog box shown in Figure 3-110 appears. Figure 3-111 Dump Debug Configuration to Disk (7.75 Firmware) This feature records controller state information when an abort occurs. After the abort has completed, you can click SAVE Debug Dump to retrieve and analyze the abort information to help determine why the abort occurred.

  • Page 162: Stop Configurator Service Routine On Host

    3: Using TPM Stop Configurator Service Routine on Host In TPM 1.0, when the Stop Configurator Service Routine on Host menu selection is made, the screen shown in Figure 3-112 appears. Figure 3-112 TPM 1.0 Stop Service Screen This screen provides an emergency shutdown routine for TPM 1.0. After you click CLEAR, the TPM 1.0 service routine is immediately shut down.

  • Page 163: Automatic Restart (Reboot) On Failure Parameter

    Miscellaneous Functions Automatic Restart (Reboot) on Failure Parameter Controller parameters implemented in firmware version 7.75 and later only control the behavior of the Automatic Restart on Failure (ROF) feature. These parameters are: • ROF Reboot Count: this parameter specifies the maximum number of times a controller attempts automatic restart to recover from firmware detected errors (see the ROF Reboot Count parameter in Figure 3-56 on page 93).

  • Page 165: Tpmwatch Event Monitor And Logger

    Appendix A TPMWatch Event Monitor and Logger TPMWatch is a support program designed to poll RAID subsystems and report their health to an output file. The file can then be used by a user-supplied program or shell script to provide notification in the event a component fails or goes offline. The program works by issuing commands to the controller to report status information for all LUNS, disk drives, and enclosure components (fans, power supplies, batteries, and so on).

  • Page 166: Running The Tpm 1.0 Version Of Tpmwatch From Linux And Irix

    A: TPMWatch Event Monitor and Logger Running the TPM 1.0 Version of TPMWatch From Linux and IRIX To run TPMWatch, make sure the $DAM_HOME environment variable is set, and you invoke the program from root. The syntax is: tpmwatch [-P Freq][-d][-H HistFile][-T LogFile]-S StatusFile -D DeviceFile[-M Addresses][-L] Where: -P Freq: Frequency in seconds between each poll.

  • Page 167: Running The Tpm 1.2 Version Of Tpmwatch From Irix

    Running the TPM 1.2 Version of TPMWatch From IRIX -L: Send events to system log file. An example syntax is: /opt/dam/tpmwatch -D /hw/scsi/sc37d0l0 -P 10 -L & Note: A minimum of two parameters must be specified, one of which must be DeviceFile.
  • Page 168 A: TPMWatch Event Monitor and Logger -T LogFile: Sends error text to user-specified log file -S StatusFile: Status file -D DeviceFile: Device to check (for example, /hw/scsi/sc37d0l0). This is the raw or pass-through driver attached to any LUN on the subsystem. It doesn’t make any difference which LUN you pick.

  • Page 169: Running The Tpm 1.0 Version Of Tpmwatch From Windows

    Running the TPM 1.0 Version of TPMWatch From Windows Running the TPM 1.0 Version of TPMWatch From Windows To run TPMWatch from Windows, you must be at the directory where the executable resides. The syntax is: tpmwatch [-P Freq][-d][-H HistFile][-T LogFile]-S StatusFile -D DeviceFile[-E SMPT -M Addresses][-L] Where: -P Freq: Frequency in seconds between each poll.

  • Page 170: Table A-1 Record Layout

    A: TPMWatch Event Monitor and Logger Note: A minimum of two parameters must be specified, one of which must be DeviceFile. If only the DeviceFile parameter is specified, TPMWATCH will not start, and the syntax usage message will be reported. Table A-1 Record Layout Byte # Size...

  • Page 171: Master/Slave Controller Status Table

    Master/Slave Controller Status Table Record Layout Table A-1 (continued) Byte # Size Description Blank if no none defined 8 X 16 X 1 Status of each Physical Device Disk[Channel][ID] (0:0, 0:1 .. 7:15) + If On-line D if drive is DEAD R if drive is Rebuilding S if drive is in Stand By state ? if drive in unknown state...
  • Page 172 A: TPMWatch Event Monitor and Logger Master/Slave Controller Status Table Table A-2 (continued) Value Meaning Insufficient memory. Waiting for debounce ping. Waiting for replacement notification. Failed Slave States Slave failed. Slave controller is ejected. Slave controller removal is detected. Slave controller is inserted. Command slave controller is inserted.

  • Page 173: Partner Status Table

    Partner Status Table Master/Slave Controller Status Table Table A-2 (continued) Value Meaning States During Redundancy Default slave is slave. Slave entered monitoring mode. Failed Master States Master failed. Master controller is ejected. Master controller removal detected. Master controller is inserted. Command master controller insert.
  • Page 174 A: TPMWatch Event Monitor and Logger Partner Status Table Table A-3 (continued) Value Partner State Notes Failed 0302 Negotiation - SCSI communication failed or wrong cables, or firmware versions/builds are different. Failed Negotiation - host ID mismatch. 0303 Failed Negotiation - SLIP/DIFFL/FBR mismatch. 0304 Failed Negotiation - disk channels available mismatch.
  • Page 175 Partner Status Table Partner Status Table Table A-3 (continued) Value Partner State Notes Failed Hot pull of partner detected while nexus active. 0320 Failed Partner absent at boot. 0321 Failed Power failed before failover finished. 0322 Failed Power failed before relinquish finished. 0323 Failed Controller-controller locking had unrecoverable SCSI...

  • Page 177: Error Codes

    Appendix B Error Codes Table B-1 lists error codes associated with the direct commands (MDACIOCTL). These codes can be reported when using TPM and are provided as reference information. 007-4382-002...

  • Page 178: Table B-1 Error Codes

    B: Error Codes Table B-1 Error Codes Description Illegal field in SCSI CDB. Bounds error. Parity error detected. Internal firmware error. Last check had a good completion. Drive is write-protected. Specified device not present. Invalid enclosure ID specified. Host block count is zero. Unimplemented opcode from host.
  • Page 179 Error Codes Table B-1 (continued) Description Migrate command issued to system drive with more than one span. Disk drive to add is already part of a system drive. Disk drive to add is not in STANDBY (Hot Spare) mode. Multiple system drives defined on PDs to enlarge. Invalid parameter in data list.
  • Page 180 B: Error Codes Error Codes Table B-1 (continued) Description A Config2 parameter can not be changed at this time. Program image failed do to invalid image file. Program image failed do to EEPROM write failure. Program image failed do to EEPROM read/compare failure. Device specified in UDD not previously defined.
  • Page 181 Error Codes Table B-1 (continued) Description Start LBA must be 0. Entire PDD must be used. SDD sent with MORE has bad field(s); illegal state change for logical device. No SES device present (Operational Fault Management MUST be enabled for this command to work). Invalid SAN map.

Table of Contents