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

Silicon Graphics TP9100 Installation Instructions And User Manual

Tpm
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-003

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-003...
  • Page 2 COPYRIGHT © 2002 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 August 2002 Updated to support Release 5.0; TP9100 (1Gb TP9100) and TP9100 (2Gb TP9100) 007-4382-003...

  • Page 5: Table Of Contents

    Installing TPM on IRIX Platforms . Uninstalling TPM on IRIX Platforms . Configuring Usernames and Passwords Invoking TPM . Setting the Environment Variable for IRIX. Starting SGI TP9100 Array Manager for IRIX . Setting Up the Browser . Logon Screen . . 10 Additional Considerations .
  • Page 6 Contents Using TPM . . 13 Main Menu . . 13 Firmware Feature Information . 15 Features for 8.30 Firmware Release . . 15 Features for 7.75 Firmware Release on the FFx Controller . 16 Configuration Functions . . 17 Select Physical Device (Configuration Function Menu) .
  • Page 7 Contents Miscellaneous Functions . . 79 Display Status of Background Jobs . . 80 Flush Controller(s) Write Cache to Disk . 82 Save Current Controller Configuration . 83 Load Controller Configuration . . 83 Flash New Firmware Onto Controller(s) . .

  • Page 9: List Of Figures

    LUN Online Screen. . 35 Figure 3-13 Create/Destroy/Expand Logical Drives Screen . 36 Figure 3-14 Add LUN(s) Screen (12 drive, 1Gb TP9100 RAID Subsystem view) . 37 Figure 3-15 Add LUN(s) Warning Screen . . 38 Figure 3-16 Add LUN(s) Confirmation Screen .
  • Page 10 Initialize LUNs in Background . 48 Figure 3-26 Storage Area Network . . 50 Figure 3-27 SAN Mapping Topology view - 1Gb TP9100 RAID controller . . 53 Figure 3-28 Install New Device Drivers Warning Screen . . 55 Figure 3-29 Administrative Functions Menu .
  • Page 11 List of Figures Display Environmental Subsystem Information . 78 Figure 3-55 Miscellaneous Functions Menu . . 79 Figure 3-56 Display Status of Background Jobs—Background Init in Progress . 81 Figure 3-57 Cache Flush Warning . . 82 Figure 3-58 Cache Flush Successful .

  • Page 13: List Of Tables

    List of Tables Files in the Distribution (IRIX) Table 1-1 Select Physical Device Field Definitions . . 19 Table 3-1 Modify Disk Device Status Field Definitions . 22 Table 3-2 Error-Event Codes . .102 Table B-1 007-4382-003 xiii...

  • Page 15: About This Guide

    This guide provides information on preparing, installing, configuring, and using the Total Performance Manager (TPM) application for the TP9100 1Gb/s FFX RAID controllers with 7.75 firmware and TP9100 2Gb/s FFX -2 RAID controllers with 8.29 and later firmware. Note: For information on TP9100 1Gb/s FFX RAID controllers with firmware levels 6.14, 7.01, and 7.03, see previous versions of this manual.

  • 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 About This Guide • Contact your customer service representative and ask that an incident be filed in the SGI incident tracking system. • Send mail to the following address: Technical Publications 1600 Amphitheatre Pkwy., M/S 535 Mountain View, California 94043-1351 •...

  • Page 19: Introduction

    IRIX system that is physically attached to a RAID storage subsystem. All communication is through the TP9100 Fibre Channel (FC) RAID controller, so that no RS-232 interface is required. The application incorporates an embedded web server to provide the user interface to a user-supplied web browser.

  • Page 20: 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 21 Software Packaging Table 1-1 Files in the Distribution (IRIX) (continued) Files Description Executable file that monitors subystem health. tpmwatch Directory of image files displayed on various webpages. images/ The logo that is displayed on main screen. images/oemlogo.gif The background image displayed on most webpages. images/wallpaper.gif Directory of files that store inquiry, log, and sense codes.

  • Page 23: Installing, Configuring, And Running Tpm On Irix

    Your fibre channel host adapter and drivers must be properly configured. • Operating System. TPM supports the following operating system versions: • IRIX 6.5.8 or later for the 1Gb/s TP9100 (FFX) RAID Controllers • IRIX 6.5.16 or later for the 2Gb/s TP9100 (FFX-2) RAID Controllers 007-4382-003...

  • Page 24: Installing The Software

    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 25: Uninstalling Tpm On Irix Platforms

    Configuring Usernames and Passwords 5. To specify the package, type: list 6. To install the software, type: install 7. At the Install subsystem prompt, type: sgi_tpm 8. To complete the installation, type: 9. Type the following command to exit the install program: quit The exit operation is automatically performed.

  • Page 26: Invoking Tpm

    DAM_HOME /opt/dam 3. For sh, bash, or ksh SHELL, type: DAM_HOME=/opt/dam export DAM_HOME Starting SGI TP9100 Array Manager for IRIX 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 27: Setting Up The Browser

    Invoking TPM By default, TPM interacts with port number 2002. If that port is busy, the program just initializes the service at the next available port number. It is also recommend that you run the service routine in the background to avoid tying up a terminal session. To do this, enter the following command: # /opt/dam/tpm &...

  • Page 28: Logon Screen

    2: Installing, Configuring, and Running TPM on IRIX Logon Screen After you invoke TPM, the logon screen appears in the browser window, as shown in Figure 2-1. Logon Screen Figure 2-1 Follow these steps to log on: Enter your username. 2.

  • Page 29: Additional Considerations

    Additional Considerations 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 31: 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 TP9100 model (1Gb FFX RAID Controller or 2Gb FFX2 RAID Controller) and the firmware level installed on the RAID controller.

  • Page 32: 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 firmware. The differences will be explained as each menu item is explained in subsequent sections of this chapter.

  • Page 33: Firmware Feature Information

    Firmware Feature Information 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 17 •...

  • Page 34: Features For 7.75 Firmware Release On The Ffx Controller

    3: Using TPM 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: • Maximum number of times a controller attempts automatic restart to recover from firmware detected errors •...

  • Page 35: Configuration Functions

    Configuration Functions 6. No Controller Reset Requirement on LUN Addition or Deletion Controller reset is no longer required when deleting or creating new system drives or configurations. 7. No Controller Reset Requirement on Enclosure Addition This feature allows users to add disk enclosures (one or more) to a configured system while the system continues to operate.

  • Page 36: Figure 3-2 Select Physical Device Dialog Box

    3: Using TPM 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. You make your selection by choosing the physical device path associated with any ID/LUN combination displayed.
  • Page 37 Configuration Functions Creates a list of all SCSI and FC device drivers. 2. Issues a standard SCSI inquiry command to report the drive Vendor ID and Product ID fields. If the inquiry fails, TPM assumes the device driver is no good, and skips to the next driver in the list.

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

    RAID type of 7 indicates JBOD. On TP9100 2Gb/sec FC RAID Controllers: The Vendor ID will be SGI and The Product ID field will be TP9100 FFX2. Logical Unit 0 information for RAID type and size of LUN are not provided.

  • Page 39: Figure 3-3 Modify Disk Device Status Dialog Box (Partial View Taken On 1Gb Tp9100 Enclosure)

    Configuration Functions Modify Disk Device Status Dialog Box (partial view taken on 1Gb TP9100 enclosure) Figure 3-3 The Modify Disk Device Status dialog box allows you to not only quickly view status of the drives, but also to define hot spares. Each drive in Figure 3-3 maps to the same physical row and column of the disk drive chassis.
  • Page 40 3: Using TPM Operation Click on a button (or buttons) to change the drive state, then click OK at the bottom of the screen to activate the changes. You would typically use the buttons as follows: • Click ON-LINE to put a drive into the online state. •...

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

    Configuration Functions Table 3-2 Modify Disk Device Status Field Definitions Field Definition Physical The physical number of blocks and MB on the disk. 1 MB = 1024 * 1024 bytes, and one block = 512 bytes. Usable The usable number of blocks and MB on the disk. These numbers are always less than the physical numbers because the RAID controller allocates a portion of disk space for its Configuration On Disk (COD).

  • Page 42: Figure 3-4 Create/Destroy/Expand Logical Drives Dialog Box

    3: Using TPM Figure 3-4 Create/Destroy/Expand Logical Drives Dialog Box The Create/Destroy/Expand Logical Drives dialog box contains the following buttons: • New Configuration: allows you to create a new disk configuration. If LUNs have already been defined, they must be deleted. •...

  • Page 43: Figure 3-5 New Configuration Screen, 1Gb Tp9100 12 Drive Enclosure

    When you click New Configuration, the screen appears as shown in Figure 3-5. Figure 3-5 New Configuration Screen, 1Gb TP9100 12 drive enclosure 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 44 3: Using TPM Note: The initial release of the 2Gb TP9100 (Release 5.0) will only support the following: 16 system drives (LUNs) maximum 32 Disk Drives maximum Creating Drive Packs The primary rules for creating packs are listed below. More details on how to do this are found in subsequent sections of this document.
  • Page 45 Follow this procedure to create and define new LUNs. More details on how to do this are found starting in Figure 3-6 on page 29 of this manual. Note: The RAID Subsystems enclosure view will differ depending on the TP9100 system that TPM is configuring.
  • Page 46 3: Using TPM 4. After you have finished creating the desired drive packs, use the Define LUNs button to create a system disk (LUN). 5. Select the drive pack(s) that you want to define as the new LUN and click Configure New.

  • Page 47: Figure 3-6 Drives Assigned Into Pack A (12 Drive, 1Gb Tp9100 Raid Subsystem View)

    Configuration Functions Drives Assigned Into Pack A (12 drive, 1Gb TP9100 RAID Subsystem view) Figure 3-6 Figure 3-6 shows 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 48: Figure 3-7 All Drive Packs Created (12 Drive, 1Gb Tp9100 Raid Subsystem View)

    When you are finished, the screen looks similar to the one pictured in Figure 3-7. The drives have been grouped into three separate drive packs. Figure 3-7 All Drive Packs Created (12 drive, 1Gb TP9100 RAID Subsystem view) Defining a LUN Using the Drive Packs To define a LUN, follow these steps: Click Define LUNs.

  • Page 49: Figure 3-8 Select Drive Packs To Include In Lun

    Configuration Functions Select Drive Packs to Include in LUN Figure 3-8 2. Check the boxes at the left (A, B, or C) to select one or more packs to combine into a LUN. 3. To create a LUN from drive pack A, for example, activate the A box and click Configure New at the bottom of the screen.

  • Page 50: Figure 3-9 Lun Is Being Defined

    3: Using TPM Figure 3-9 LUN is Being Defined 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 51: Figure 3-10 Lun Is Defined

    Configuration Functions Figure 3-10 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 52: Figure 3-11 All Luns Defined

    3: Using TPM Figure 3-11 All LUNs Defined At this point, all the LUNs have been defined. Next, the RAID controller must be updated with the new configuration. Updating the RAID Controller To update the RAID controller with the new LUN configuration, follow these steps: 007-4382-003...

  • Page 53: Figure 3-12 Updating The Raid Controller Warning Screen

    Configuration Functions Press the Next Screen button. Figure 3-12 Updating the RAID Controller Warning Screen 2. Click YES to save the LUN configuration; otherwise click NO. If all goes well, the screen shown in Figure 3-13 appears indicating that the new LUN(s) are online.

  • Page 54: Figure 3-14 Create/Destroy/Expand Logical Drives Screen

    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-14 appears. Figure 3-14 Create/Destroy/Expand Logical Drives Screen To add one or more LUNs, follow these directions: Click Add LUN(s).

  • Page 55: Figure 3-15 Add Lun(S) Screen (12 Drive, 1Gb Tp9100 Raid Subsystem View)

    Configuration Functions Figure 3-15 Add LUN(s) Screen (12 drive, 1Gb TP9100 RAID Subsystem view) 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.

  • Page 56: Figure 3-16 Add Lun(S) Warning Screen

    3: Using TPM Figure 3-16 Add LUN(s) Warning Screen 4. Click YES to add the LUN, or NO to cancel and go back to the main menu. If you select YES, the confirmation screen in Figure 3-17 appears after a brief waiting period.

  • Page 57: Figure 3-18 Delete Lun Warning Screen

    Configuration Functions Click Delete LUN. The warning screen shown in Figure 3-18 is displayed. This screen shows the size and characteristics of the last LUN that was created. Figure 3-18 Delete LUN Warning Screen 2. Click YES to delete the LUN immediately. 3.
  • Page 58 3: Using TPM Note: SGI does not support LUN Expansion and MORE operations on the IRIX operating system. Note: The initial release of the 2Gb TP9100 (Release 5.0) will only support the following: 16 system drives (LUNs) maximum 32 disk drives maximum If you wish to attempt an online expansion, and your environment is not properly configured, the request will fail, and you will receive an appropriate error message.

  • Page 59: Figure 3-19 Create/Destroy/Expand Logical Drives Screen

    Configuration Functions 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. Write-back cache is disabled during the expansion. 14.

  • Page 60: Figure 3-20 Expand Lun Screen (12 Drive, 1Gb Tp9100 Raid Subsystem View)

    3: Using TPM Figure 3-20 Expand LUN Screen (12 drive, 1Gb TP9100 RAID Subsystem view) Note: In the screen shown in Figure 3-20, 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.

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

    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-21 appears.

  • Page 62: Figure 3-22 Initialize Lun

    3: Using TPM Figure 3-22 Initialize LUN As shown in Figure 3-22, 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-23 appears. 007-4382-003...

  • Page 63: Figure 3-23 Initialization Confirmation

    Configuration Functions Figure 3-23 Initialization Confirmation 3. To continue with the initialization of the LUNs shown on the screen, click OK. A status screen similar to the one shown in Figure 3-24 displays how the procedure is progressing, and updates every 10 seconds. 007-4382-003...

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

    3: Using TPM Figure 3-24 Initialization Progress 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 65: Figure 3-25 Initialize Luns In Background

    Configuration Functions Note: Background initialization can only be performed on valid RAID levels (RAID levels 1, 3, 5 and 0 +1) To initialize LUNs in the background, follow these steps: Click Initialize LUNs in Background on the main menu. The screen shown in Figure 3-25 appears. Figure 3-25 Initialize LUNs in Background 007-4382-003...

  • Page 66: Figure 3-26 Initialize Luns In Background

    3: Using TPM 2. To select an individual Logical Drive to be initialized, select the Initialize radio button next to the desired Logical Drive. To select all Logical Drives created to be initialized, select the Initialize All radio button. 3. Once the Logical Drive or all Logical Drives are selected, click INITIALIZE. The screen shown in Figure 3-26 appears.

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

    Figure 3-28 on page 53, 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 68: Figure 3-27 Storage Area Network

    3: Using TPM Warning: Only the most experienced administrators should make changes in an on-line environment. 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 69 Configuration Functions Without host to LUN mapping, each host computer (1 through 3) has complete access to all four system drives. When a host system boots, IRIX operating systems might not automatically attempt to mount all of these system drives, 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.
  • Page 70 3: Using TPM 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 71: Figure 3-28 San Mapping Topology View - 1Gb Tp9100 Raid Controller

    Configuration Functions Figure 3-28 SAN Mapping Topology view - 1Gb TP9100 RAID controller Regardless of the topology, the bottom portion of the screen shown in Figure 3-28 will be the same. Administrators must first choose the topology that best matches the SAN environment, then configure the mapping.

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

    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 73: Administrative Functions

    Administrative Functions Figure 3-29 Install New Device Drivers Warning Screen If you are running in a live environment with mounted LUNs, you need to be careful about executing this feature. For example, if you changed SAN mapping so logical drive #3 is mapped to LUN 0 instead of LUN 4, then you will make file systems disappear, and confuse your device drivers.

  • Page 74: View/Modify Raid Controller Configuration

    3: Using TPM Figure 3-30 Administrative Functions Menu This menu has the following selections, with the associated explanations on the indicated pages: • “View/Modify RAID Controller Configuration” on page 56 • “Reset Controller(s)” on page 60 • “Gracefully Bring a Controller Off Line” on page 61 •...

  • Page 75: Figure 3-31 View/Modify Controller Configuration, 2Gb Tp9100, 8.40 Firmware (Partial)

    Administrative Functions Figure 3-31 View/Modify Controller Configuration, 2Gb TP9100, 8.40 firmware (partial) 007-4382-003...

  • Page 76: Figure 3-32 View/Modify Controller Configuration, 2Gb Tp9100, 8.40 Firmware (Partial)

    3: Using TPM Figure 3-32 View/Modify Controller Configuration, 2Gb TP9100, 8.40 firmware (partial) 007-4382-003...

  • Page 77: Figure 3-33 View/Modify Controller Configuration, 2Gb Tp9100, 8.40 Firmware (Partial)

    Administrative Functions Figure 3-33 View/Modify Controller Configuration, 2Gb TP9100, 8.40 firmware (partial) Make as many changes as you desire on the screen, then click the Apply button, which saves the new configuration on all controllers, as well as the COD area on your RAID subsystem’s disk drives.

  • Page 78: Figure 3-34 Reset Controllers Warning Screen

    3: Using TPM Reset Controller(s) When the Reset Controller(s) menu selection is made, the screen shown in Figure 3-34 appears. Figure 3-34 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 79: Gracefully Bring A Controller(S) Off Line

    Administrative Functions Figure 3-36 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-37 appears.

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

    3: Using TPM 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-38 appears. Figure 3-38 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 81: Perform Data Consistency Operations On A Lun

    Administrative Functions 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-39 appears. Figure 3-39 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 82: Figure 3-40 Operation Started Dialog Box

    3: Using TPM If you click EXECUTE to begin execute any of the check or restore actions, the dialog box of Figure 3-40 appears, indicating that the process has started. Figure 3-40 Operation Started Dialog Box Click OK to proceed. The window shown in Figure 3-41 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 83: Figure 3-41 Background Initialization Status Screen

    Administrative Functions Figure 3-41 Background Initialization Status Screen 007-4382-003...

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

    3: Using TPM 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-42 appears. Figure 3-42 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 85: Figure 3-43 World Wide Name Table For Raid Controller

    The World Wide Name (WWN) table includes a delete WWN from WWN table and a purge old entries option. • 1Gb TP9100 RAID controllers support a maximum of 64 host WWNs. • 2Gb TP9100 RAID controllers support a maximum of 256 host WWNs.

  • Page 86: Reporting Functions

    3: Using TPM the WWN table entries are deleted, the indices change for any entries following those WWNs that were deleted. Reporting Functions The Reporting Functions menu is located on the main screen and is shown in Figure 3-44. Figure 3-44 Reporting Functions Menu The Reporting Functions menu has the following selections, with the associated explanations on the indicated pages: •...

  • Page 87: Set Default Screen Refresh Rate

    Reporting Functions Set Default Screen Refresh Rate When the Set Default Screen Refresh Rate menu selection is made, the screen shown in Figure 3-45 appears. Figure 3-45 Default Screen Refresh Rate Enter the desired screen refresh rate in seconds and click SAVE. Display (Dual) Controller Status When the Display (Dual) Controller Status menu selection is made, the screen shown in Figure 3-46 appears.

  • Page 88: Topology Query

    3: Using TPM Figure 3-46 Controller Status Information This Screen displays information about the controller(s) and whether or not they are working together. There are nearly 100 different error or warning messages that can be returned, and this could be quite useful in the event you have a controller failure. You should also periodically check this screen during normal operations to make sure that all is well.

  • Page 89: Display Scsi/Fibre Device Information

    Reporting Functions Figure 3-47 Topology Query (16 drive, 2Gb TP9100 RAID Subsystem View) 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.

  • Page 90: Figure 3-48 Display Scsi/Fibre Device Information

    3: Using TPM Figure 3-48 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 91: Display Full Subsystem Configuration Information

    Reporting Functions Display FULL Subsystem Configuration Information When the Display FULL Subsystem Configuration Information menu selection is made, the Controller Information Values (see Figure 3-49), Controller Tunable Parameters (see Figure 3-50), and GroupConfig Structure (see Figure 3-51) screens appear. Figure 3-49 Controller Information Values (partial screen) Figure 3-50 Controller Tunable Parameters 007-4382-003...

  • Page 92: Figure 3-51 Groupconfig Structure

    3: Using TPM Figure 3-51 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 93: Display Physical Subsystem Information

    Reporting Functions Display Physical Subsystem Information When the Display Physical Subsystem Information menu selection is made, the screen shown in Figure 3-52 and Figure 3-53 appear. Figure 3-52 Physical Subsystem Information 007-4382-003...

  • Page 94: Figure 3-53 Physical Subsystem Information

    3: Using TPM Figure 3-53 Physical Subsystem Information These screens show statistical data, drive status, and errors for all drives in all subsystems. It also correctly displays the enclosure number, row, and column of each disk drive. All numbers are cumulative, starting from zero when the subsystem is powered on.

  • Page 95: Display Logical Subsystem Information

    Reporting Functions Display Logical Subsystem Information When the Display Logical Subsystem Information menu selection is made, the windows shown in Figure 3-54 appear. Figure 3-54 Logical Subsystem Information The screen shows all configured LUNs, their status, mapping information, and how they are laid out.

  • Page 96: 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-55 appears. Figure 3-55 Display Environmental Subsystem Information The windows display status information results of polling the enclosure (and all expansion enclosures) every 10 seconds.

  • Page 97: Miscellaneous Functions

    Miscellaneous Functions Miscellaneous Functions The Miscellaneous Functions menu is located on the main screen and is shown in Figure 3-56. Figure 3-56 Miscellaneous Functions Menu The Reporting Functions menu has the following selections, with the associated explanations on the indicated pages: •...

  • Page 98: Display Status Of Background Jobs

    3: Using TPM • “Save Controller Debug Dump” on page 95 • “Stop Configurator Service Routine on Host” on page 96 • “Automatic Restart (Reboot) on Failure Parameter” on page 96 Display Status of Background Jobs When the Display Status of Background Jobs menu selection is made, the windows appear as shown in Figure 3-57.

  • Page 99: Figure 3-57 Display Status Of Background Jobs-Background Init In Progress

    Miscellaneous Functions Figure 3-57 Display Status of Background Jobs—Background Init in Progress These windows show you how initialization, rebuilds, or checks are progressing. The browser title bar (not shown in Figure 3-57 on page 81) displays the date and time of the last poll.

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

    3: Using TPM 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-58 appears. Figure 3-58 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 101: Save Current Controller Configuration

    Miscellaneous Functions Save Current Controller Configuration When the Save Current Controller Configuration menu selection is made, the screen shown in Figure 3-60 appears. Figure 3-60 Save Current Controller Configuration Note: It is highly recommended that users save the configuration after all system drives are created.

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

    3: Using TPM Figure 3-61 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. To clone a configuration this way, the two RAID subsystems must be exactly the same, including the disk drives. The file is or loaded from the sever that launched TPM, not the client machine running the web browser.

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

    Miscellaneous Functions Figure 3-62 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. In this event, drive data recovery may have to be performed by a professional data recovery lab.

  • Page 104: Figure 3-63 Flash New Firmware Onto Supported Disk(S) Dialog Box

    3: Using TPM are already disabled when you click the Flash New Firmware Onto Supported Disk(s) menu selection, the dialog box shown in Figure 3-64 appears. Figure 3-63 Flash New Firmware Onto Supported Disk(s) Dialog Box Warning: The TPMWatch application must be terminated prior to updating disk drive firmware.

  • Page 105: Figure 3-64 Flash New Firmware Dialog Box

    Miscellaneous Functions Figure 3-64 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. When the process is complete, the screen shown in Figure 3-65 appears.

  • Page 106: Adjust Battery Settings

    3: Using TPM Figure 3-65 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. Adjust Battery Settings When the Adjust Battery Settings menu selection is made, the screen shown in Figure 3-66.

  • Page 107: Figure 3-66 Adjust Battery Settings

    Miscellaneous Functions Figure 3-66 Adjust Battery Settings 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-55 on page 78).

  • Page 108: Clear Configuration

    3: Using TPM • Shutdown Battery: this option shuts down charging to the battery. The Battery Backup Unit (BBU) maintains memory content in the presence of AC power failures, AC power glitches, and short power outages. This protection is important when the write-back cache is enabled, and data is waiting to be flushed to the disk drive.

  • Page 109: Set The Real Time Clock

    Miscellaneous Functions Figure 3-68 Clear Configuration Set The Real Time Clock When the Set Real Time Clock menu selection is made, the dialog box shown in Figure 3-69 appears. Figure 3-69 Set Real Time Clock Click SET CLOCK to synchronize the controller clock with the host computer. The confirmation screen shown in Figure 3-70 appears.

  • Page 110: View The Controller's Internal Event Log

    3: Using TPM View the Controller’s Internal Event Log When the View the Controller’s Internal Event Log menu selection is made, the dialog box shown in Figure 3-71 appears. Figure 3-71 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 111: Identify A Disk

    Miscellaneous Functions Identify a Disk For the Identify a Disk menu selection to work properly, Operational Fault Management (OFM) must be enabled. Also, at least one of the SES disk drives must be present and operational. When the Identify a Disk menu selection is made, the dialog box shown in Figure 3-72 appears.

  • Page 112: Scan For New Enclosures And Disks

    3: Using TPM Scan for New Enclosures and Disks When the Scan for New Enclosures and Disks menu selection is made, the dialog box shown in Figure 3-73 appears. Figure 3-73 View Controller’s Internal Event Log This feature allows users to add one or more disk enclosures to a configured system while the system continues to operate.

  • Page 113: Save Controller Debug Dump

    Miscellaneous Functions 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. 9.

  • Page 114: Stop Configurator Service Routine On Host

    3: Using TPM firmware image the abort occurred. The abort code is written to NVRAM when the controller is aborting and generates an event. The abort code takes up two bytes of data. Debug Dump data can be retrieved by going to Miscellaneous Functions and clicking on Save Controller Debug Dump after an abort has completed and the controller is back online.
  • Page 115 Miscellaneous Functions The possible values for the time interval between refreshing the number of restart attempts range from DISABLED to seven days. The values are displayed when you click the ROF Rearm Interval dropdown box. To select a particular value, depress the right mouse button while scrolling to the desired time interval and then release the button to select the value.

  • Page 117: 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 118 A: TPMWatch Event Monitor and Logger -d: Enable debug mode to stderr -e: E-mail error messages (requires -E flag and 7.X FW or above) -i: E-mail informational messages (requires -E flag and 7.X FW or above) -s: E-mail severe messages (requires -E flag and 7.X FW or above) -w: E-mail warning messages (requires -E flag and 7.X FW or above) -H HistFile: Optional event history file.

  • Page 119: Event And Error Codes

    Appendix B Event and Error Codes Event and error codes that are generated by the controller modules are displayed in the controller event log and can be viewed using TPM. Information entries identify an event or error that has occurred. Error codes help to identify the cause of a problem, the failing modules, and the service actions that might be needed to resolve the problem.
  • Page 120 B: Event and Error Codes If this item is an event that is displayed for your information only, no action is required. If this item is an error, this column defines the action you must take to resolve the problem. Table B-1 Error-Event Codes Error-...
  • Page 121 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Rebuild stopped because At least one more physical device failed in It may not be possible to logical drive failed. the array.
  • Page 122 B: Event and Error Codes Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required SCSI command retried on The command may have timed out. Bus None hard disk. reset may have occurred. Device reset may have occurred.
  • Page 123 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Initialization started. Host started the initialization. Wait until the initialization is completed. If the system is shutdown prior to this process being completed, the physical device can be made useful only by reinitializing...
  • Page 124 B: Event and Error Codes Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required A hard disk failed SCSI command timed out on the device. Replace hard disk and because command to the rebuild it. device timed out.
  • Page 125 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required A hard disk failed Bad hard disk. Device write protected. Replace hard disk and because write operation rebuild it. Check the startup of ‘Bad Data Table’...
  • Page 126 B: Event and Error Codes Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required A standby rebuild was A physical device failed and spare was None started. available. Hot spare replaced with a The new hot spare may have a smaller None smaller capacity physical physical capacity than the physical disk it...
  • Page 127 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Online controller Online controller firmware upgrade has None firmware upgrade has completed without error. The partner completed successfully. controller will now be auto flashed. Online controller Online controller firmware upgrade has Use the offline method to...
  • Page 128 B: Event and Error Codes Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Logical drive has been Rebuild completed. User set the physical None placed online. device online. New configuration was added. An automatic rebuild has A physical device failed and a spare None started on logical drive.
  • Page 129 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required A logical drive has been A new configuration has been added. None found. MORE completed. A new controller has been plugged in. Controller has been powered on.
  • Page 130 B: Event and Error Codes Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Data for Disk Block has Data retained in RAID Cache for a Insure that all the Physical been lost due to Logical Write-back Logical Drive cannot be stored Drives related to the Logical Drive problem.
  • Page 131 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Logical drive background Background initialization completed None initialization completed. successfully. Low battery charge level. Controller was powered off for duration Run consistency check to Logical drive may have longer than battery capacity.
  • Page 132 B: Event and Error Codes Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Normal temperature has Faulty fan has been replaced. Room None been restored. temperature was reduced. Over temperature. Room temperature is too high. Bad fan. Turn off the system and allow it to cool down.
  • Page 133 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Fan is not present. Enclosure Management Connection is Follow enclosure broken. Management hardware is bad. management vendor’s Fan is not present. diagnostics and repair procedures.
  • Page 134 B: Event and Error Codes Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Enclosure access is Enclosure managment connection is Follow enclosure offline. broken. Management hardware is bad. management vendor’s diagnostics and repair procedures.
  • Page 135 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Controller is dead. Contact your service System is disconnecting representative. from this controller. Controller has been reset. Controller failed. Controller was removed None from the system.
  • Page 136 B: Event and Error Codes Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required BBU reconditioning is User started a BBU reconditioning. None started. BBU reconditioning is BBU reconditioning completed None finished. successfully. BBU reconditioning is User cancelled the BBU reconditioning.
  • Page 137 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Hard ECC error Faulty memory module. Replace memory module. corrected. BBU recondition needed. None Controller’s partner has None been removed. BBU out of service.
  • Page 138 B: Event and Error Codes Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required Size table full. Too much physical device size Remove unused device information is defined. information for this system. User logged in. An array management utility user logged Not available.
  • Page 139 Event and Error Code Table Table B-1 Error-Event Codes (continued) Error- Event # Type Description Additional Details User Action Required New configuration A new configuration was downloaded to None received. controller. Configuration cleared. Controller was told to clear the None configuration.

Table of Contents