U SER’S M ANUAL DO-0975-005
SmartRAID V User’s Manual Copyright © 1998, 1999 Distributed Processing Technology Corporation All Rights Reserved – Printed in U.S.A. Storage Manager is a trademark of Distributed Processing Technology Corporation. SmartCache, SmartRAID, RAIDstation and DPT are registered trademarks of Distributed Processing Technology Corporation.
SmartRAID V User’s Manual FCC Statement Warning: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation.
SmartRAID V User’s Manual Distributed Processing Technology Limited Product Warranty PROOF OF PURCHASE MAY BE REQUIRED. YOU MAY REGISTER YOUR PURCHASE BY RETURNING THE ENCLOSED WARRANTY CARD WITHIN 30 DAYS OF PURCHASE.
SmartRAID V User’s Manual Distributed Processing Technology End-User Software License Agreement You may (i) use the software on a single machine; (ii) make only one copy of the software into any machine-readable or printed form for backup purposes; (iii) merge the software into other software for your use on the single machine (provided that any portion of the software merged into other software will continue to be subject to the terms and conditions of this license); (iv) transfer the software and this li
SmartRAID V User’s Manual Release Notes To review release notes and documentation errata associated with the SmartRAID V products, select Help–View README Information in Storage Manager or view the READ.ME file in the DPT install directory for the latest information. Check the DPT web site for availability of an updated version of this manual (SmartRAID V User’s Manual) in Adobe Acrobat PDF format.
SmartRAID V User’s Manual Table of Contents FCC Statement ................................................................................................................. iii VCCI Statement ................................................................................................................ iii Limited Product Warranty ................................................................................................. iv End-User Software License Agreement .........................................
SmartRAID V User’s Manual Configuring Device IDs .............................................................................................. 3-6 SCSI ....................................................................................................................... 3-6 Fibre Channel ......................................................................................................... 3-6 Installation ..................................................................................................
SmartRAID V User’s Manual Saving Controller Firmware to a Disk Image ............................................................... 4-27 Creating a Firmware Disk Image .............................................................................. 4-28 Restoring Firmware from a Disk Image ................................................................... 4-28 Software Installation ............................................................................ 5-1 Windows NT 4.0 ..............................
SmartRAID V User’s Manual Using Storage Manager Remotely ............................................................................. 6-3 Storage Manager on ROM ......................................................................................... 6-4 Physical Configuration View .......................................................................................... 6-4 Logical Configuration View ............................................................................................
SmartRAID V User’s Manual Hot Spares ............................................................................................................... Verify ........................................................................................................................... Background Task Priority ............................................................................................. I/O Statistics ..................................................................................................
SmartRAID V User’s Manual SmartRAID V Architecture ........................................................................................... 7-22 ASPI Protocol ........................................................................................................... 7-22 I2O Messaging Protocol ........................................................................................... 7-22 Command Processing ..........................................................................................
SmartRAID V User’s Manual Specifications ....................................................................................... C-1 DC Power Requirements ............................................................................................... C-2 Environmental Specifications ........................................................................................ C-3 Memory .........................................................................................................................
SmartRAID V User’s Manual xiv
CHAPTER 1: Read This First! Before you begin installing your new DPT controller, please take the time to read this chapter. This chapter is an important guide to the rest of the documentation and provides a summary of the installation process. The term RAID controller used throughout this document applies to all SmartRAID V products. SmartRAID V Documentation A chapter-by-chapter tour of the documentation set.
1-2 Read This First! About the Documentation The complete documentation set for the SmartRAID V product line consists of three parts: • The User’s Manual (this book), which contains information that helps you to configure and install your SmartRAID V product and using the Storage Manager software.
Read This First! 1-3 Chapter 5, Software Installation – This chapter provides instructions for installing DPT drivers and Storage Manager for all supported operating systems. After the hardware is configured and the disk arrays created, you can install the operating system, SmartRAID V drivers and the full, OS-specific version of Storage Manager. Chapter 6, Storage Manager – This chapter provides information about using DPT’s Storage Manager software.
1-4 Read This First! Using RAIDstation? YES NO Configure Cabinet Refer to: Storage Cabinets and Devices manual Fibre Channel? NO Set SCSI ID Configure Termination See Chapter 3, Configuration and Installation YES YES Add-on Modules? NO Plug in RA4050 / SX405x Plug in cache memory Plug in BB4050 See Chapter 3, Configuration and Installation Install the controller Attach cables See Chapter 3, Configuration and Installation Power on system Run SMOR (Storage Manager on ROM) Set termination option Ve
Read This First! 1-5 What’s In the Box? All SmartRAID V controller kits include a controller, utility diskettes (containing drivers and the Storage Manager software for supported operating systems), and documentation. The documentation set consists of this User’s Manual, a Quick Install Guide, and the Storage Manager online help system. NOTE SmartRAID V Ultra2 SCSI controllers include the following additional items: • One internal Ultra/Ultra2 4-device Wide SCSI cable.
1-6 Read This First! Safety Information Throughout this manual are various notices that indicate procedures or practices that can result in loss of data, damage to equipment or personal injury. Be sure to read the following sections for additional information regarding electrical shock hazards and preventing damage from electrostatic discharge. The following symbol will accompany IMPORTANT and CAUTION notices that can result in damage to equipment or loss of data.
Read This First! 1-7 Working with Electricity Any device that uses electricity must be treated with caution. Follow these guidelines to ensure general safety. • Keep the chassis area clear and dust-free during and after installation. • Do not perform any action that creates a potential hazard to people or makes the equipment unsafe. • Before working on the system, unplug the power cord.
1-8 Read This First! Preventing Electrostatic Discharge CAUTION Electrostatic discharge (ESD) can damage electronic components and equipment. ESD occurs when electronic components are improperly handled and can result in complete or intermittent failures. Always follow ESDprevention procedures when removing and replacing components. Use the following guidelines to prevent ESD damage: • Always use an ESD wrist or ankle strap and ensure that it makes skin contact.
CHAPTER 2: About Your New Controller This chapter presents the features of DPT SmartRAID V SCSI and Fibre Channel controllers, along with the Bus Expansion, RAID Accelerator and Battery Backup modules. Feature Overview A look at the features common to SmartRAID V hardware. Millennium Specific features of our high performance RAID controller. Decade and Century What makes our low cost RAID controllers so powerful, and how you can upgrade them to meet your growing needs.
2-2 About Your New SmartRAID V Controller Introduction DPT SmartRAID V products incorporate the latest intelligent controller technology to deliver optimum performance for desktop systems, file servers or multi-user host systems. NOTE ECC-protected cache is available when you use DPT SM4050 or DM4050/DM4060 memory modules. PM3755U2 controllers require DPT DM4050 or DM4060 memory modules. Non-DPT DIMM modules are not supported.
About Your New SmartRAID V Controller 2-3 Product List The following SmartRAID V products and accessories are documented in this manual: Model PM3755F PM3755U2B PM3754U2 Description 64-bit PCI to Fibre Channel RAID Controller 64-bit PCI to Ultra2 Wide SCSI RAID Controller (w/battery backup capability) 32-bit PCI to Ultra2 Wide SCSI RAID Controller PM2654U2-R1 PM2554U2 PM1554U2 32-bit PCI to Ultra2 Wide SCSI RAID Controller 32-bit PCI to Ultra2 Wide SCSI RAID Controller 32-bit PCI to Ultra2 Wide SCSI RA
2-4 About Your New SmartRAID V Controller Product Feature Overview All SmartRAID V controllers include: • Support for I2O OSMs provided by major operating system vendors; DPT provides drivers for some operating systems. See Chapter 5, “Software Installation” for a list of drivers supplied by DPT. • Certifications for major operating systems, including Novell NetWare and Windows NT.
About Your New SmartRAID V Controller 2-5 SmartRAID V Millennium Features SmartRAID V Millennium products are high-performance RAID controllers for host computers with a PCI expansion bus. Key features of the Millennium include: • High-performance RISC processor (80 MIPs) • Hardware RAID 0, 1, and 5 • Support for striping multiple arrays as a single logical drive (RAID 0+1 and RAID 0+5) • Hardware XOR • Up to 256MB of cache per controller • 32-bit PCI and 64-bit PCI bus models Conforms to revision 2.
2-6 About Your New SmartRAID V Controller You can use an SX405x Bus Expansion Module to expand a Millennium controller with one or two additional SCSI channels or with one Fibre Channel Arbitrated Loop (FC-AL) port. Millennium Fibre Channel controllers can be expanded with one additional FC-AL port. By using an SX4055F Bus Expansion Module, Fibre Channel and SCSI buses can coexist on the same SCSI controller (PM375xU2 models only).
About Your New SmartRAID V Controller 2-7 SmartRAID V Decade and Century Features SmartRAID V Decade and Century controllers are designed to provide high performance solutions for workstations and servers in environments where cost is a factor. The following Decade and Century controllers are available: PM1554U2 / PM2554U2 / PM2654U2 Ultra2 Wide Type 32-bit PCI Host Bus Host/Internal Transfer Rate I/O Transfer Rate 1 132 MB/sec 80 MB/sec 1.
2-8 About Your New SmartRAID V Controller The Century controller provides a single Ultra2 SCSI channel and supports up to two additional channels with an SX405x Bus Expansion Module. The SX405x is available in three models, providing either one or two additional SCSI channels or one Fibre Channel Arbitrated Loop (FC-AL) port. By using an SX4055F Bus Expansion Module both Ultra2 SCSI and Fibre Channel can coexist on the same controller.
About Your New SmartRAID V Controller 2-9 SX405x modules attach to the SmartRAID V controller and do not require an additional slot in the host system: • A single channel SX405xU2-1 Ultra2 SCSI Bus Expansion Module adds one SCSI channel and provides one external Very High Density Cable Interconnect (VHDCI) 0.8 mm connection and one internal highdensity 68 pin-connection. • A dual channel SX405xU2-2 Ultra2 SCSI Bus Expansion Module adds two SCSI channels and provides two external VHDCI 0.
2-10 About Your New SmartRAID V Controller BB4050 Battery Module Features The BB4050 Battery Module adds battery backup for the data cache on a SmartRAID V PM3755U2B controller using DPT DM4050 or DM4060 memory modules. The following features of the BB4050 provide additional data security for high-reliability servers: • Nickel Metal Hydride battery pack provides a backup time of 72 hours (using a single 16MB memory module).
About Your New SmartRAID V Controller 2-11 SmartRAID V Controller LEDs SmartRAID V controllers provide nine LEDs that let you visually monitor controller activity. Several different controller states are indicated by the LED as outlined in the following sections. Two additional LEDs indicate the status of the cache memory on the controller. See Appendix A, “Assembly Drawings” for the location of the LEDs on your controller.
2-12 About Your New SmartRAID V Controller LED Display During Controller Active When the power-up sequence is complete, viewing the LEDs can help you determine the operating status of the controller. These LED patterns are also useful for troubleshooting. Refer to Appendix B, “Troubleshooting” for more information on interpreting LED patterns. LED Function 1 Heartbeat. Indicates that controller interrupts are enabled and that the controller is alive.
About Your New SmartRAID V Controller 2-13 BB4050 LED Indicators The BB4050 module has two LED indicators labeled CHARGE and TRICKLE. These LEDs indicate the following conditions: Status TRICKLE LED CHARGE LED Momentary flash On Fast Charge Off On Trickle Charging On Off Charge inhibit Off Off Flashing On On On 1 Initial Powerup Discharge Battery not installed 1. If battery voltage and the ambient temperature are acceptable, the Trickle LED will not remain lit.
2-14 About Your New SmartRAID V Controller
CHAPTER 3: Configuration and Installation Your new DPT SmartRAID V controller is the center of a complete system consisting of the controller, disk drives and other peripherals, and the connecting cables. This chapter discusses configuring these components. Configure Devices This chapter includes information on using SmartRAID V controllers in a Microsoft Cluster Server (MSCS) configuration. Attach Modules Prepare your SCSI peripherals for use by setting their SCSI IDs and termination.
3-2 Adapter Configuration and Installation Installation Overview The process of installing a SmartRAID V controller consists of the following steps: 1. If you are using a RAIDstation storage cabinet, configure it as described in the RAIDstation User’s Manual. 2. Configure device IDs, cables and termination for SCSI devices in the host system. Fibre Channel controllers and devices will automatically configure themselves during boot. 3.
Adapter Configuration and Installation 3-3 Configuration DPT Fibre Channel controllers and attached Fibre Channel devices are plug-and-play and will configure themselves automatically during boot. SCSI devices in the system must be configured prior to use. This configuration includes enabling SCSI termination for the devices and setting the SCSI IDs for each device. Narrow and Wide SCSI The SCSI devices you will be installing can be either Narrow (8-bit) or Wide (16-bit) SCSI devices.
3-4 Adapter Configuration and Installation Configuring SCSI Termination The devices on each physical end of a SCSI cable must be terminated. Depending upon how you configure your system, you will either terminate two SCSI devices, or the SCSI controller and one peripheral SCSI device. NOTE The SCSI cable supplied with your DPT controller has a factory-installed active terminator on the end of the cable. If you are using multiple SCSI busses on a single controller, each separate bus must be terminated.
3-5 Adapter Configuration and Installation The following illustrations show various SCSI cabling examples. Terminate your SCSI devices as shown in the examples, ensuring that only the devices at the ends of the cables are terminated.
3-6 Adapter Configuration and Installation Configuring Device IDs The SCSI specification allows up to 7 SCSI devices (and a controller) to be connected to a single 8-bit SCSI bus. A Wide SCSI bus can support up to 15 devices (and a controller). Up to 126 devices can be attached to a single Fibre Channel loop. SCSI All SCSI devices, including the controller, must be assigned a unique SCSI ID.
Adapter Configuration and Installation 3-7 Installation NOTE SmartRAID V Millennium controllers and Century or Decade controllers with an RA4050 module should have at least 16MB of cache installed. Several optional modules are available to upgrade the performance of your SmartRAID V controller: • RA4050 RAID Accelerator – adds RAID 5, hardware XOR and cache memory capacity to the Decade and Century controllers.
3-8 Adapter Configuration and Installation Installing the RA4050 RAID Accelerator SmartRAID V Century controllers can be upgraded to support RAID 5, 0+5 and data caching by installing the RA4050 RAID Accelerator module. A Decade (PM1554U2) controller has built-in RAID 5 and 0+5 support without an RA4050 module. Adding an RA4050 module to a Decade controller provides up to 64MB of cache and hardware XOR performance for RAID 5 operation.
Adapter Configuration and Installation 3-9 Installing an SX405x Bus Expansion Module SmartRAID V controllers accept the following Bus Expansion Modules: Model Description SX4054U2-1 Single Ultra2 SCSI Bus, 32-bit Expansion Module. Adds one SCSI bus with one internal and one external connector. SX4054U2-2 Dual Ultra2 SCSI Bus, 32-bit Expansion Module. Adds two SCSI buses with two internal and two external connectors. SX4055U2-1 Single Ultra2 SCSI Bus, 64-bit Expansion Module.
3-10 Adapter Configuration and Installation To install an SX4054/SX4055 module: 1. Remove the module mounting bracket from the end of the module. Keep the bracket screws. 2. Attach the module to the controller, connecting P5 on the SX405x to J7 on the controller. Refer to Appendix A, “Assembly Drawings” for connector locations. NOTE SX4055 modules have two connectors (J7 and J8) that must align correctly when installing the expansion module on a Millennium 64-bit controller. 3.
Adapter Configuration and Installation 3-11 Installing SIMMs SmartRAID V PM3754U2 and PM3755F Millennium controllers support up to 256MB of cache using four onboard SIMM sockets. One to four memory modules of the same type and capacity can be installed. SmartRAID V Decade and Century controllers can use up to 64MB of cache provided by the SIMM sockets on an RA4050 module. One to four SIMMs of the same type and capacity can be installed. IMPORTANT All installed SIMMs must be the same type and capacity.
3-12 Adapter Configuration and Installation To install SIMM modules: 1. Install the SIMMs in the sockets as shown starting with socket 1. Refer to Appendix A, “Assembly Drawings” for socket locations. Be sure the SIMM is fully seated and locked in the socket. Although standard 32- or 36-bit 16MB or 64MB low-profile singlesided 60ns EDO SIMMs can be used, DPT recommends that you use DPT SM4050-16 or -64 ECC SIMMs for maximum data integrity. 2.
Adapter Configuration and Installation 3-13 Installing DIMMs IMPORTANT All installed DIMMs must be the same type and capacity. At least one DIMM must be installed. Use only DPT DM4050 or DM4060 DIMMs. Do not use DPT SmartCorrect DM4000 DIMMs. The SmartRAID V Millennium model PM3755U2B has four onboard DIMM sockets for cache memory. The green ECC Enabled LED on the controller is lit when ECC-capable DIMMs are installed. To install DIMM modules: 1.
3-14 Adapter Configuration and Installation Installing the BB4050 Battery Backup Module The BB4050 Battery Backup Module is used only on a PM3755U2B Millennium controller. To install the BB4050 Module: 1. Before installing the BB4050 module, be sure the battery pack electrical connector is plugged in the socket on the BB4050 board. 2. Align the Battery Backup Module and the Millennium controller as shown in the illustration. 3.
Adapter Configuration and Installation 3-15 Installing the Controller 1. Connect the computer’s disk activity LED cable to connector P6 on the controller. See Appendix A, “Assembly Drawings” for the location of this connector. Pins 1 and 3 of P6 are connected to +5V and pins 2 and 4 are connected to GND. Ensure that the positive lead of the LED cable (usually a red wire or marked with a red stripe) is attached to pin 1 or 3 and the negative lead (usually a black wire) is attached to pin 2 or 4. 2.
3-16 Adapter Configuration and Installation Determining the Booting Controller The controller whose BIOS has the lowest address will take control over the boot process and that controller will become the booting controller. Therefore, in a system with multiple controllers, you must ensure that the DPT I2O BIOS occupies the lowest address if you want the DPT controller to be the booting controller.
Adapter Configuration and Installation 3-17 NVRAM Reset SmartRAID V controllers retain their setup parameters even when powered off. These parameters are stored on the controller in an area of nonvolatile memory (NVRAM). There is a possibility that, through improper configuration, the controller can be put into a state where it hangs the system during boot. If this happens, the parameters stored in the NVRAM can be restored to their default settings by the following procedure: 1.
3-18 Adapter Configuration and Installation Using Microsoft Cluster Server The information presented in this section is intended to help you configure SmartRAID V controllers and a storage subsystem for host systems that use Microsoft Cluster Server (MSCS) to provide fault-tolerant network server resources. For specific information about installing and configuring MSCS support on your Windows NT server, refer to the Microsoft Cluster Server Administrator’s Guide.
Adapter Configuration and Installation 3-19 System Requirements DPT SmartRAID V controllers include support for MSCS host configurations. To use Microsoft Cluster Server with a SmartRAID V controller you need to do the following: • Use host systems that conform to the Microsoft Hardware Compatibility List for MSCS. • Install Windows NT Advanced Server Enterprise Edition 4.0 (with Service Pack 5 or later) or Windows 2000 Advanced Server on both server systems. Windows NT Workstation 4.
3-20 Adapter Configuration and Installation How SmartRAID V Works with MSCS When MSCS is operating on a server cluster, the servers continuously send a heartbeat to each other across the private network connection. When a server does not receive this signal for a preset interval, it automatically begins the failover process of providing the resources of the failed server and takes control of the storage subsystem.
CHAPTER 4: Storage Manager on ROM Storage Manager on ROM (SMOR) is a BIOS-based setup utility that lets you configure your DPT SmartRAID V controller without starting an operating system and using Storage Manager. You can also use SMOR to perform basic array configuration. SMOR makes the initial setup of your SmartRAID V controller and RAID storage easier and faster. Run SMOR Run SMOR by pressing Ctrl+D during system boot. Configure your Controller Use SMOR to set the hardware options on your controller.
SMOR 4-2 Overview To configure your hardware and create disk arrays when Storage Manager is not available, run Storage Manager on ROM (SMOR) during the system boot. This is especially useful for a new system where you need to create disk arrays before you install the operating system. After your storage subsystem is configured, install your operating system according to the appropriate procedure in Chapter 5, “Software Installation”.
SMOR Keyboard Reference The navigation keys work in a similar fashion to those of Windows Explorer. Use these keys to move around in SMOR: Menu Control Alt + (Menu Highlight) Select the corresponding menu or menu item. Enter Initiate an action. Up/Down Arrows Move between menu choices. Esc Return to Tree View. Left Pane - Tree View Control Up/Down Arrows Move between elements within the tree. Left/Right Arrows Scroll the tree left and right.
SMOR 4-4 Menu Reference The SMOR Main Menu changes dynamically depending on what is selected in the tree view. The following is a complete list of possible selections: FILE Read System Config Set System Config Exit Rescan the system – unsaved configuration changes are lost. Save and enable configuration changes. Quit SMOR. RAID Create… Delete Rebuild Stop Build Create a new array. Delete the currently selected array. Rebuild a RAID 1, 5, 0+1 or 0+5 array. Stop building or rebuilding an array.
SMOR 4-5 Screen Layout The SMOR interface works like the Windows Explorer tree-structured interface. The screen is divided into three major components: a menu bar across the top of the screen and two display panes below the menu bar. Information & Configuration Tab Pages Menu Bar Tree View The Menu Bar To open a specific menu, press Alt+(highlighted letter of the menu name). After a menu is open, you can select a specific menu item by pressing the key for the letter highlighted on the menu item.
4-6 SMOR The Left Pane – Tree View The Tree View, displayed in the left pane, is the central control for SMOR. This view displays a tree structure that represents the organization of the DPT storage subsystem. This includes DPT controllers, storage devices and arrays detected by SMOR. By moving the highlight with the up and down arrows, you can select items you want to view or configure.
SMOR 4-7 Within the Information View, you select an item to configure by using the Tab or Shift+Tab keys to move the highlight to the item. Items that cannot be selected are shown in black. The way in which you change an item depends on the type of control associated with it. Check-boxes are toggled by using the Spacebar. List-box items (for example, SCSI Transfer Rate) are changed using the up and down arrow keys. List-box items can be recognized by the downward pointing arrow at the right of the item.
SMOR 4-8 Running SMOR Start SMOR by pressing Ctrl+D when the DPT I 2O BIOS message appears on the screen during the boot sequence. The letters that appear during the initial device scan process are: C CD-ROM D Disk drive E Scanner, SAF-TE or intelligent RAID enclosure, or a second controller (MSCS). H Hot spare drives T Tape device 0, 1, 5 Physical arrays identified by the RAID level The position of a letter corresponds to the SCSI ID assigned to that device.
SMOR 4-9 Information/Configuration Windows When you highlight an item within the Tree View, the corresponding Information View is displayed. DPT I2O BIOS Settings The example above is the default Information View when SMOR starts. The settings in this view affect the DPT I2O BIOS and all the DPT controllers in your system. To view or change these settings, highlight DPT Configuration in the tree.
SMOR 4-10 Bootable Devices These settings let you modify the system boot process for host systems with multiple peripheral controllers in cases where the DPT I 2O BIOS does not provide effective or appropriate default operation. The default setting causes the system to follow the order described in the Determining the Booting Controller section of Chapter 3. If you select Disabled, DPT controllers are not used as boot devices.
SMOR 4-11 Controller Information Windows To view or change the configuration of a DPT RAID Controller, highlight the controller in the Tree View. Two tabs are available: Information and Configuration. Controller Information Tab The Information Tab for a Controller displays general information reported by that controller.
SMOR 4-12 Host Bus: Bus Type Always PCI for SmartRAIDV Transfer Host PCI bus transfer rate. 132 MB/sec for 32-bit PCI bus 264 MB/sec for 64-bit PCI bus Attached Modules: Identifies the expansion modules and cache memory modules installed. Attached Modules can be reported as: SX405xU2-1, SX405xU2-2 SX405xF RA4050 BB4050 SCSI Expansion Module* Fibre Expansion Module* RAID Accelerator Battery Backup Module *Bus Expansion Modules are always reported as either SX405xU2 or SX405xF.
SMOR 4-13 HBA Configuration Tab To modify the hardware parameters for the highlighted SmartRAID controller, press Alt+C to display the Configuration tab. Select Default to reset the parameters on this tab to their default values. NOTE Depending on the specific hardware, some items displayed in the Configuration tab may be read-only. The settings are subdivided according to which parameters relate to the individual peripheral bus and which parameters relate to the entire controller.
SMOR 4-14 SCSI ID SmartRAID V controllers are configured by default at SCSI ID 7. This value should not be changed unless required for special configurations. NOTE Fibre Channel IDs can be 0 – 126. However, these IDs are configured dynamically and cannot be changed using SMOR or Storage Manager. TERMPWR By default SmartRAID V controllers supply termination power for other SCSI devices through the TERMPWR line on the SCSI cable.
SMOR 4-15 Device Information Individual devices are listed in the Tree View under the controller to which they are connected. Highlight a device to view its configuration information. The Device Information view displays general device information and hardware configuration. This view is divided into three parts: Identification, Capabilities and Status. Progress shows a numeric percentage of completion for active tasks.
SMOR 4-16 SCSI Capabilities The capabilities section is a list of the capabilities defined in the SCSI specifications. A checkmark indicates that the device supports that SCSI function. Status The following status conditions can be indicated for attached devices: Dead The device failed to respond to controller commands. If the device becomes available it will only change status after the system configuration is read or the host is restarted. Failed A drive failure has occurred.
SMOR 4-17 Array and Array Group Information SmartRAID V controllers implement RAID 0, 1 or 5 disk arrays in hardware. RAID 0 arrays are composed of any combination of individual drives. RAID 1 arrays are always composed of two drives. RAID 5 arrays contain three or more drives. After the arrays have been created, one or more arrays of the same RAID level can be combined into a Parity Group (see the Creating a Parity Group section). Arrays are striped into Parity Groups by the controller firmware.
SMOR 4-18 Identification The identification section displays a general description of the highlighted array: Description The RAID level used for the array. Revision The firmware revision of the controller to which the array is attached. Address The address of the array, in the form HBA n, Channel n, ID n, LUN n. Arrays are always assigned the lowest logical address of any device in the array. This field displays as much information as is necessary to unambiguously define the address of the array.
SMOR Building The array is being built. Created The array or device is defined but not initialized. Dead A write-back cache to the array command failed. This is an unrecoverable failure. Degraded A single drive in the array has failed; array performance is affected. Impacted A verification is being performed on the array; I/O performance is affected. Missing A drive is physically missing or will not respond to commands on the device bus. Optimal The array is fully functional.
SMOR 4-20 Array Operations You can use SMOR to create or manage disk arrays. The following sections describe how to use SMOR to create arrays and parity groups, delete arrays, assign hot spare drives, and rebuild an array. Refer to the Chapter 7, “Theory of Operation” for a complete discussion of RAID levels and disk arrays. Creating an Array To create an array: 1. Select RAID–Create. 2. When the RAID Type dialog appears, select the RAID level you want to use.
SMOR 4-21 b. To remove a previously selected device from the array, highlight the device and press the Spacebar. 4. When you are finished selecting drives for the new array, select Done. 5. If you are creating a RAID 1 array, the RAID-1 Build Option dialog appears. RAID 1 arrays are built by copying the existing data from one device to the other. Select the direction for the copy, then select OK. 6. Select File–Set System Config to start the build process.
SMOR 4-22 Creating a Parity Group Creating a parity group (RAID 0+1 or 0+5) is similar to creating a normal RAID 1 or RAID 5 array group. Do the following to create a RAID 0+1 or RAID 0+5 parity group: 1. Create and build your array groups as described in the preceding section (Creating an Array). Do not initiate the build process on any arrays that you intend to use in a parity group. 2. After your initial array groups are created, select RAID–Create again. 3.
SMOR 4-23 Deleting an Array To delete an array, follow the steps below: 1. In the left pane, highlight the array that you want to remove, then select RAID–Delete. 2. You will be warned that all data will be lost. Choose Yes or No. The array configuration for the devices is not deleted until you select File–Set System Configuration or exit SMOR and choose to save your changes. Hot Spares Any disk drive not assigned to an array or in use by the operating system can be designated as a Hot Spare.
SMOR 4-24 Rebuilding a Failed Array If a drive in a RAID 1 or RAID 5 array fails and the drive is not protected by a Hot Spare, use the following procedure to replace the failed drive. 1. Remove and replace the failed drive according the procedures in your hardware documentation. 2. When the failed drive has been replaced, choose RAID–Rebuild Array to start the rebuild process. The status of the array will change to Rebuilding (view the Information window for that array).
SMOR 4-25 Managing Controller Firmware SMOR includes several features that let you upgrade, save and restore the firmware on your SmartRAID V controller. These options are listed on the Action menu when a controller is selected in the Tree View. The Flash HBA feature lets you install the latest DPT controller firmware, I2O BIOS and SMOR utility software. The Save Firmware feature lets you save the current controller firmware, I2O BIOS and SMOR software along with the NVRAM settings to a floppy disk.
SMOR 4-26 Do the following to upgrade controller NVRAM, firmware, I2O BIOS, or SMOR utility: 1. Place the diskette containing the image files in the diskette drive of the system where the controller is installed. 2. In the Tree View, select the controller that you want to update. 3. Select Action–Flash HBA. The source file browser will appear. 4. Select the diskette drive in the source file browser window and press Enter to expand the drive listing. 5.
SMOR 4-27 Saving Controller Firmware to a Disk Image This feature provides you with a way to save the current ROM software and NVRAM settings for your controller to a bootable diskette. The resulting diskette is a bootable disk and contains a copy of the three controller software components: firmware, I2O BIOS and SMOR. The utility also saves the current and default NVRAM settings. The diskette will contain the following files: SMORbbbb.vvv Where bbbb is the build number and vvv is the version. I2OBIOS.
SMOR 4-28 Creating a Firmware Disk Image To create the firmware backup diskette: 1. Press Ctrl+D when the DPT I2O BIOS banner appears during system startup to start SMOR. 2. Move the highlight to the controller that you want to backup. 3. Insert a blank, formatted diskette into the host diskette drive. NOTE This operation overwrites the entire diskette. Any existing data is erased. 4. Press Alt+A to select the Action drop-down menu. 5. Select Save Firmware.
CHAPTER 5: Software Installation Your new SmartRAID V controller uses I 2O drivers that may be supplied by DPT or your operating system vendor. This chapter discusses driver and operating system installation when using SmartRAID V controllers. After you install the operating system, you can install Storage Manager. Storage Manager is available for: Windows NT 4.0 A DPT I2O driver is supplied with your controller. Windows 95/98 A DPT I2O driver is supplied with your controller. SCO UNIX 3.2V4.2, ODT 3.
Software Installation 5-2 Windows NT 4.0 The DPT SmartRAID V driver for Windows NT 4.0 provides support for both disk drives and other SCSI devices, such as CD-ROMs and scanners. NOTES • Windows NT must be updated with Service Pack 4 or later. • If you choose the Microsoft I2O OSM in place of the DPT class or miniport driver, you will not be able to use Storage Manager. • The Windows NT 4.0 OSM is not compatible with Windows 2000.
Software Installation 5-3 There are three driver installation scenarios for Windows NT 4.0: • Installing the SmartRAID V controller into a new system, then installing Windows NT 4.0 • Upgrading an existing Windows NT 4.0 system • Adding a SmartRAID V controller into an existing Windows NT 4.0 system, to be used in addition to a currently installed SmartRAID IV or SmartCache IV controller Each of these cases requires a slightly different procedure.
Software Installation 5-4 NOTE If a SmartRAID IV or SmartCache IV controller is installed, Windows NT mass storage detection routines will load an older DPT driver for that device from the Windows NT diskette or CD-ROM. After Windows NT installation completes, update the driver using the version contained on the DPT diskette that was supplied with your SmartRAID IV or SmartCache IV controller.
Software Installation 5-5 Upgrading an Existing System NOTE If you have already installed a SmartRAID V controller into your system and want to change drivers, refer to the Adding to an Existing System section instead of this procedure. To upgrade an existing Windows NT 4.0 system to a SmartRAID V controller, follow the steps below: 1. From the Control Panel, select the SCSI Adapters icon. Then select the Drivers tab and click Add. 2. Insert the DPT Windows NT diskette, then click Have Disk. 3.
Software Installation 5-6 Adding to an Existing System (Microsoft OSM) NOTE If you use the Microsoft I 2O OSM in place of the DPT miniport driver, you will not be able to run Storage Manager. To add a DPT SmartRAID V controller to an existing Windows NT 4.0 system using the Microsoft Windows NT OSM, do the following: 1. Obtain a copy of the self-extracting file for the Microsoft I 2O drivers and extract the drivers to a directory or diskette. 2. From Control Panel, select the SCSI Adapters icon.
Software Installation 5-7 Windows 95/98 The DPT SmartRAID V driver for Windows 95/98 provides support for both disk drives and other devices, such as CD-ROMs and scanners.
Software Installation 5-8 8. Remove the boot diskette from the floppy disk drive and reboot the system from the C: drive. 9. Insert the Windows 98 Full Installation CD in the CD-ROM drive. 10. Enter the drive letter assigned to the CD-ROM and run SETUP (for example, D:\SETUP). 11. Follow the Windows 98 installation prompts. 12. During one of the device detection boot processes, Windows 98 will identify PCI Card and/or Memory Controller devices.
Software Installation 5-9 Installing Windows 95 (OEM SR2 – Version 950b) This section describes the steps to install Windows 95 (OEM SR2 Version) on one disk drive or array group using a SmartRAID V controller. Ensure that your disk drives, arrays, CD-ROM drive, and any other SCSI devices attached to the controller are recognized by SMOR before proceeding. Do the following to install Windows 95 (OEM SR2 Version) with a SmartRAID V controller: 1. Boot DOS from a bootable DOS diskette. 2.
5-10 Software Installation Contact your motherboard vendor and apply the patch. After the patch is installed and the system is restarted, Windows 95 will repeat the device discovery process. If you are installing the operating system, go back to step 12 and continue the procedure. If you are adding a SmartRAID V to an existing configuration, go to step 3 on page 5-12 and continue the procedure. 14. Insert the DPT Disk 1 diskette into the floppy drive and let Windows search for the drivers. 15.
Software Installation 5-11 Installing Windows 95 (Retail Upgrade – Version 950a) SmartRAID V controllers are not supported by Windows 3.1, therefore an upgrade process from Windows 3.1 to Windows 95 does not apply. However, the Retail Upgrade Version (950a) can be installed like a new operating system if you have your original Windows 3.1 diskettes. Follow the installation instructions in the Installing Windows 95 (OEM SR2 950b) section of this chapter.
Software Installation 5-12 Contact your motherboard vendor and apply the patch. After the patch is installed and the system is restarted, Windows 95 will repeat the device discovery process. If you are installing the operating system, go to step 12 on page 9 and continue the procedure. If you are adding a SmartRAID V to an existing configuration, go to step 3 and continue the procedure. 3. Select PCI Card and choose Update Driver from the Driver tab.
Software Installation 5-13 Installing Storage Manager for Windows When the SmartRAID V controllers are properly recognized by Windows, run SETUP.EXE from the DPT Windows 95/98 diskette and follow the on-screen prompts to install the Storage Manager software. The installation program detects which version of Windows you are using and installs the appropriate Storage Manager files for your operating system. If you will use remote communication, be sure to select the Communication Server install option.
Software Installation 5-14 SCO UNIX A diskette for SCO UNIX 3.2V4.2 and SCO UNIX OpenServer 5 (3.2V5.x) is included with your SmartRAID V controller. The DPT diskette for SCO contains the drivers for both versions of SCO. A second diskette contains a Motif version of DPT Storage Manager for each version of SCO UNIX. NOTE When assigning numbers to controllers, SCO starts with zero. Storage Manager numbers controllers starting with one. Installing SCO UNIX 3.2V4.
Software Installation 5. NOTE 5-15 Continue the installation according to the SCO documentation. If you are installing from tape or CD-ROM, SCO UNIX 3.2V4.2 expects to find the tape at Controller 0, SCSI ID 2, LUN 0 and the CD-ROM at Controller 0, SCSI ID 5, LUN 0. SCO OpenServer 5 will locate the tape or CD-ROM at any valid SCSI address. Adding to an Existing SCO UNIX 3.2V4.2 or OpenServer 5 System When adding a DPT controller to an existing SCO UNIX configuration, perform the following steps. 1.
Software Installation 5-16 NOTE When you reboot several WARNING messages may appear and scroll off the screen quickly. These will not occur after “diskadd” is run and can be ignored. 6. Use the diskadd utility to add drives or arrays that are attached to a SmartRAID V controller. Run the sdiconfig –l utility in a terminal window or non-GUI screen. This will list all controllers recognized by the operating system and any attached devices.
Software Installation 5-17 Novell NetWare You must follow the procedures in the following sections to installing a SmartRAID VI controller for Novell NetWare, especially as a booting controller. There are specific steps that must be completed to ensure that NetWare will recognize the DPT controller and any attached devices. The DPT diskette for NetWare contains the device drivers you need to install a DPT controller for NetWare 4.2 and 5.0.
Software Installation 5-18 NetWare 4.11 – Boot Controller This section describes how to install a SmartRAID VI controller as a boot device for NetWare 4.11 servers. NOTE Part of this procedure requires that you have enough free space on your C: drive to hold the contents of the NetWare CD-ROM. 1. Download the NW411.ZIP file from the DPT Technical Support web site. Extract the files to a floppy disk. 2. Install the DPT controller as the primary controller and attach the disk drives.
Software Installation 5-19 NetWare 4.11 – Secondary Controller This section describes how to integrate a DPT SmartRAID VI controller into a new or existing Novell NetWare 4.11 system as a secondary controller. Ensure that your NetWare version is at the minimum patch level specified by Novell. NOTE The server must have patch kit IWSP4 or later installed to use the drivers supplied by DPT. NetWare 4 Support Pack 8 contains the latest Novell I2O drivers.
Software Installation 5-20 NetWare 4.2 – Boot Controller This procedure is for installing a SmartRAID VI controller as the boot device in a NetWare 4.2 server. 1. Install the SmartRAID VI controller as the primary controller and attach the disk drives or storage subsystem. Ensure that you are using a CD-ROM that is not attached to the DPT controller. 2. Create a directory on the C: drive named NWUPDATE. 3. Insert the DPT NetWare diskette into the floppy disk drive. 4. Copy A:\NW42 to C:\NWUPDATE.
Software Installation 5-21 NetWare 4.2 – Secondary Controller This section describes how to integrate a DPT SmartRAID VI controller into a new or existing Novell NetWare 4.2 system as a secondary controller. Ensure that your NetWare version is at the minimum patch level specified by Novell. NOTE NetWare 4 Support Pack 8 contains the latest Novell I2O drivers. These drivers are newer than the ones from DPT but have not been tested for compatiblity with DPT controllers.
Software Installation 5-22 NetWare 5.0 – Boot Controller Use the following procedure to install support for a SmartRAID VI controller during installation of NetWare 5. The controller should be installed at the beginning of the procedure so that it can be detected by the install routine. 1. Install the DPT controller as the primary controller and attach the disk drives. You can use SMOR to create disk arrays or Hot Spare drives when you boot the system. 2.
Software Installation 5-23 NetWare 5.0 – Secondary Controller This section describes how to integrate a DPT SmartRAID VI controller into a new or existing Novell NetWare 5.0 system as a secondary controller. Ensure that your NetWare version is at the minimum patch level specified by Novell. NOTE NetWare 5 Support Pack 4 contains the latest Novell I2O drivers. These drivers are newer than the ones from DPT but have not been tested for compatiblity with DPT controllers.
Software Installation 5-24 Installing Remote Communication Support 1. Insert the DPT NetWare diskette in the server’s floppy disk drive. 2. Enter the following command at the prompt: LOAD A:\DPTINST.NLM 3. You will be prompted to choose whether to load the remote communication support immediately or delay loading until the server is restarted.
Software Installation 5-25 Red Hat Linux 5.2 and 6.0 These instructions are for installation of the DPT device driver for Linux on a system using Red Hat Linux 5.2 or 6.0. 1. Install and configure your DPT controller according to the instructions in Chapter 3, “Configuration and Installation”. 2. If you want to install Linux on a disk array, use SMOR to configure any disk arrays before beginning the operating system installation.
Software Installation 5-26 5. When prompted, insert the DPT driver diskette and press OK. 6. You will be prompted for the language and keyboard type. 7. You will be asked to specify the location of the media packages to be installed. If you are installing from CD-ROM, select Local CD-ROM. If you selected CD-ROM, you will be asked what type of CD-ROM you have. 8. The system will ask you to specify a driver. Scroll down and select the DPT I2O driver. 9.
Software Installation 4. 5-27 When the download is complete, run the following command from the prompt: tar -xvf linsm218.tar 5. After the file extraction is finished, run the following command from the prompt: ./install You will be asked if you want the DPT Communication Server to load on boot. The default is No. If you will access this host from a remote Storage Manager client, enable the DPT Communication Server. 6. Reboot the system, when the installation is complete. 7.
5-28 Software Installation
CHAPTER 6: Storage Manager DPT’s Storage Manager gives you complete control over your storage subsystem. You can manage your storage locally, remotely across a network or by using a modem. Physical View Storage Manager brings out the best in your DPT hardware, from checking your equipment configuration – to managing your disk arrays – to providing online event logging and performance statistics.
Storage Manager 6-2 Introduction DPT Storage Manager is included with your SmartRAID V controller. This utility performs several functions: • Checks hardware configuration. • Allows you to create, expand or delete disk arrays. • Provides online functions for the DPT storage subsystem such as event logging and notification, array status and I/O statistics. • Provides remote access to DPT hardware and attached storage devices across a TCP/IP network.
Storage Manager 6-3 Running Storage Manager You can run Storage Manager: • On the same computer that contains the DPT hardware and peripheral devices (local operation). • Remotely, across a TCP/IP network. This lets you view and configure servers from remote locations. • In demo mode, where Storage Manager simulates a storage subsystem that contains various types of DPT controllers and peripheral devices. This lets you experiment with various storage configurations.
6-4 Storage Manager Storage Manager on ROM Storage Manager on ROM (SMOR) is a ROM-based version of Storage Manager which is provided on your SmartRAID V controller. If you are installing a new system, use SMOR to configure your RAID subsystem prior to installing your operating system. You can access SMOR during the system boot by pressing Ctrl+D after the DPT I2OBIOS is loaded. Refer to “Chapter 4, Storage Manager on ROM” for more information.
Storage Manager 6-5 The Switch View button toggles between the Physical Configuration View and the Logical Configuration View window. Create Array Group starts the process of creating a RAID logical disk. Print will print a text report of the subsystem configuration.
6-6 Storage Manager Logical Configuration View On the right side of the Logical Configuration View window are all physical devices that are attached to DPT controllers. On the left side of the window are the associated logical devices as seen by the host computer. Non-disk devices use the same icon for both logical and physical views. Disks drives can be seen either as individual drives or as members of arrays.
Storage Manager 6-7 Logical Device Address Every device and array is assigned a logical device address by Storage Manager. This is the address used by the host operating system to access the device or array. Logical device addresses appear in parentheses under the logical device and LSU icons on the Logical Configuration View window.
Storage Manager 6-8 Device The unique ID for that device. For an array, this is the lowest ID among the drives that make up the array. LUN Logical Unit Number for that device (normally 0). NOTE Array groups are automatically assigned an address that corresponds to the lowest logical device address used by a device in that array group. For example, if the lowest member device address for an array is HBA:0 Bus:1 ID:12 LUN:0, the LSU address will be HBA:0 Bus:1 ID:12 LUN:0.
Storage Manager Building Status flag: blue - This flag appears on an array icon when an array that was created is being built. Status flag: white - This flag appears on the drive icon that data will be copied to in a RAID 1 array build. Failed Status flag: red - This flag appears on a drive icon when the drive has failed. On an array icon, this flag indicates that one drive has failed in a RAID 0 array or two or more drives have failed in a redundant array.
6-10 Storage Manager Information Windows Double click on a controller or device icon to display an Information window for that controller or device. Host Bus Adapter Information Window The Host Bus Adapter Info window displays configuration information reported by that controller. The Controller section displays the Model, Serial #, Firmware revision and amount of installed Cache. ECC is checked only if DPT ECC SIMMs or DIMMs are installed.
Storage Manager 6-11 Battery Backup Configuration NOTE During the initial calibration cycle for a BB4050 module, the controller disables automatic, low-battery write-through mode. After the calibration, use the Battery Backup Configuration dialog to set a threshold for entering write-through mode when the battery charge drops below a predetermined level.
Storage Manager 6-12 Click the Defaults button to set the Battery Capacity Warnings to their default values. Actual default values are calculated by the controller based on the size of the cache memory. BB4050 Battery Status Messages Battery Module status is reported as one of the following: Full The battery is fully charged. Charging The battery is charging after being partially or fully discharged.
Storage Manager 6-13 Battery Maintenance (BB4050) IMPORTANT The BB4050 module will not be able to provide backup capability during this operation. The Maintenance operation can be used to ensure the battery remains capable of accepting a full charge. The Maintenance cycle completely discharges and then recharges the battery pack. This helps to eliminate any voltage-depression effects resulting from the battery pack being partially discharged and then recharged repeatedly during normal operation.
Storage Manager 6-14 SCSI ID DPT controllers are set at ID 7 by default. The ID for a SmartRAID V Fibre Channel controller can change dynamically as the Fibre Channel loop self-configures. Refer to Chapter 3, Configuration and Installation for information about selecting an alternate SCSI ID. SCSI TERMPWR By default SmartRAID V controllers supply termination power through the TERMPWR line on the SCSI cable.
Storage Manager 6-15 Buttons available are: Test Alarm – lets you test the audible alarm on the controller. Flash – displays the Flash Configuration dialog to update the controller firmware and BIOS. Caching – allows you to select the controller cache parameters. Defaults – resets the controller configuration to factory default settings. Cancel – cancels any changes you have made and returns to the Host Bus Adapter Info window.
Storage Manager 6-16 The current controller Model, Firmware Version and Type are displayed. To specify an image file for the flash operation, you can type a path and filename in the Filename field or click on Browse to use the standard file selection dialog. Firmware images are contained in a xxxxxxxx.FWI file, where the 8-character file name consists of the 4-digit controller model and a 4-digit release number. A DPT I2O BIOS image is contained in a file named I2OBIOS.
Storage Manager 6-17 Device Information Window This window displays the following information: Description The manufacturer and model. Revision The drive firmware version. Address The logical address of the device. Capacity Storage capacity of the device in megabytes. For removable media disk devices, Capacity is reported for the currently inserted media. Disk devices also display the number of Sectors on the media along with the Physical and Logical sector size.
6-18 Storage Manager Various buttons are available depending upon the type of device. Disk drive devices will have an Event Log and I/O Stats button. Disk drives that are not members of arrays have Make HotSpare, Configure and Format buttons. Print is always available. Disk drives that are members of arrays display a Fail Drive button. If the drive is a Hot Spare, the Remove Hotspare button replaces the Make Hotspare button.
Storage Manager 6-19 Predictive caching is a feature of SmartRAID V controllers that attempts to reduce average disk access time by determining when the host is requesting data that it read previously and reading in additional sequential data before it is actually requested. This feature can provide enhanced performance when you have a host with 20 or more users who are frequently accessing large, individual sequential files.
6-20 Storage Manager From the Logical Configuration View, you can double-click on an Array Group icon to display the Array Group Information window. Information windows for arrays that are part of a Parity Group can be viewed by clicking on the icons for those arrays.
Storage Manager 6-21 The Array Group Information window displays the following information: NOTE Name The descriptive name assigned to the array. An icon in the upper right corner of the window indicates the RAID level. Address This is the logical device address used by the host operating system to access the logical drive. The address is the same one as the lowest device address disk drive in the array. Capacity The total usable storage capacity of the array in megabytes (MB).
Storage Manager 6-22 Creating an Array Group To create an Array Group, do the following: 1. Click the Create Array Group button. 2. The Select Array Type dialog appears. Specify whether or not you want Drive fault tolerance (RAID 1 or 5) or No fault tolerance (RAID 0) Select whether the array is to be Optimized for Capacity (RAID 5) or Optimized for Performance (RAID 1).
Storage Manager 6-23 During the drive selection process some drives might be displayed in a blue color. This indicates that these drives cannot be included in the array unless you change the configuration. You must either select more drives for the array or remove one or more drives from the array. See the introduction to the Array Groups section for rules regarding the number of drives that can be included in arrays. 4.
Storage Manager 6-24 If you want to monitor the progress of the build operation, display the Array Group Information window for the new array group. The build progress is displayed as a percentage of completion in the Status field. You can also view the Information window for an array that is a member of a Parity Group to monitor the progress for that component of the Parity Group.
Storage Manager NOTE 6-25 There is a significant impact on system performance during array expansion. The relative priorities given to system performance and the array expansion process can be adjusted by use of the Background Task Priority setting in Storage Manager. Dynamic Array Expansion maintains the performance gains of RAID 0 and RAID 5, spreading accesses randomly across the drives in the array. The DPT controller presents the same number of LSUs to the operating system after the expansion.
Storage Manager 6-26 NOTE If a drive fails during expansion, the expansion will complete successfully. However, the new, larger array will be in a degraded state until the problem is fixed. If there is a Hot Spare associated with the array, the degraded array is rebuilt using the Hot Spare. If there is no Hot Spare, replace the defective drive, and start a rebuild of the array. • Each new drive added to an array must be at least equal to the capacity of the smallest capacity drive already in the array.
Storage Manager 6-27 7. When you are finished choosing drives, click Done. The icon for the Array Group appears with a black flag until the expansion process is started. 8. Select File–Set System Configuration to start the array expansion. The status flag on the Array Group turns blue and the flags on the components turn white during the expansion process. You can perform other activity on the system while the expansion continues, because the array is fully functional during the expansion process.
Storage Manager 6-28 Deleting an Array Group To delete an Array Group, do the following: 1. From the Logical Configuration View window, select the LSU or Array Group icon of the array you want to delete. Then click Delete Array Group. 2. Click OK when the confirmation message appears to complete the delete operation. Click Cancel to exit without deleting the Array Group.
Storage Manager 6-29 Events Events are generated for detected fault conditions as well as subsystem status changes. The events are grouped into four categories as follows: 1 – Soft Error An operation on a disk drive that caused an error but was successful after a retry. 2 – Recoverable Hard Error An error on a disk drive, controller or peripheral bus, where the data was recovered using ECC or from redundant array information.
Storage Manager 6-30 Event Logging When events occur, they are automatically logged in the cache on the SmartRAID V controller where they occurred. In addition, you can specify that Storage Manager maintain an event log on disk (see Event Notification). The contents of the event log can be displayed by clicking Event Log in any controller, drive or array information window. Only the events pertaining to that controller, drive or array are displayed.
Storage Manager 6-31 Event Notification If your operating system supports a Broadcaster, Storage Manager lets you specify that event messages be sent to users, groups, devices, through e-mail, to the system error log and the DPT Log File. Select Options– Event Broadcast Control to display the Event Broadcasting dialog. The options in the Event Broadcasting dialog may vary depending upon your operating system.
6-32 Storage Manager You can select or modify the following parameters: Time Interval Specified time interval at which point the Broadcaster will read the event logs of all DPT controllers with cache. Any new event messages are broadcast to each specified destination (based on the Display Threshold setting). Broadcast to Computer(s) Enable this option to send event messages to each system in the Computer Names list.
Storage Manager 6-33 Pager Event Messaging DPT Storage Manager for Windows NT can also send event messages to alphanumeric paging devices. The messages are sent as e-mail to pagers that support e-mail text message delivery. NOTE: This feature should work with any alphanumeric paging system that supports message delivery via e-mail. Contact your service provider for specific information.
Storage Manager 6-34 Broadcasters Broadcasters are provided on the DPT diskettes for Windows NT, SCO UNIX and SCO UnixWare. The Broadcaster collects events logged by DPT controllers in the host computer on which that broadcaster is running. The Broadcaster records these events to disk files for each controller for use by Storage Manager.
Storage Manager 6-35 Broadcaster for SCO UNIX Systems DPT provides a Broadcaster for SCO UNIX 3.2V4.2, SCO OpenServer 5 and SCO UnixWare 7. The Broadcaster collects events from DPT controllers and saves them to files in the /usr/dpt directory for use by Storage Manager. Events can also be sent to an ASCII file, specified devices, the User/Group list or e-mailed to users as specified in the Event Broadcasting dialog. Installing the Broadcaster The DPT diskette for SCO contains the Broadcaster for SCO.
Storage Manager 6-36 Broadcaster for Windows NT The Windows NT Broadcaster collects events from DPT controllers and records them to files in the \DPTMGR directory for use by Storage Manager. Additionally, events are sent to the Windows NT Event Viewer. Installing the Broadcaster When the DPT installation program runs, the Broadcaster is copied to the C:\DPTMGR subdirectory by default. The Broadcaster is installed as a Windows NT service and runs automatically whenever the system is started.
Storage Manager 6-37 This window displays a list of the events submitted to the Application Log by the DPT Broadcaster, as well as other applications. Events are singleline entries that contain the following information: Icon An icon that indicates the Windows NT severity level for the event. DPT events can be assigned severity levels of Error, Warning, Information, Operation, or Unknown. Date The date the event was logged by the controller. Time The time the event was logged by the controller.
Storage Manager 6-38 Formatting Drives SmartRAID V controllers can perform a low-level format on attached fixed disk drives. This function is available from the SCSI Device Information window in Storage Manager. SmartRAID V controllers format drives in standard 512-byte format. A low-level format is not normally required before using a disk drive.
Storage Manager 6-39 Drive Failures Drive failures are indicated by flags on the icons associated with the Array Group, array and individual drives. Failure conditions are indicated as follows: A drive belonging to an Array Group fails The drive icon displays a red flag in both the Physical and Logical Configuration Views. The failed drive belongs to a RAID 0 Array Group The icon for the failed drive displays black flag.
Storage Manager 6-40 Rebuilding a Degraded Array NOTE You can select Rebuild even if the failed drive has not been replaced and try using the drive again. If the rebuild attempt is not successful, replace the drive before starting another rebuild. When a drive in a RAID 1 or RAID 5 array fails, and that drive is not protected by a Hot Spare, do the following to restore the array to Optimal status: 1. Replace the failed drive according to the procedure in your hardware documentation. 2.
Storage Manager 6-41 Hot Spares To assign a drive as a Hot Spare, click Make Hotspare in the drive’s SCSI Device Information window. Click Remove Hotspare to reassign an existing Hot Spare drive as a normal drive. Any drive that is not assigned to an array can be assigned as a Hot Spare. Hot Spares are reserved to automatically replace failed drives in RAID 1 or 0+1 and RAID 5 or 0+5 arrays and cannot be accessed by the operating system for data storage.
Storage Manager 6-42 Verify NOTE Data inconsistencies should not occur under normal conditions. However, a power failure that interrupts an array write operation can cause inconsistencies. Using the Verify function to make the data consistent does not ensure that the new consistent data is the correct data. Running a Verify operation for RAID 1 and RAID 5 arrays ensures that the redundant information contained in the array is consistent.
Storage Manager 6-43 Background Task Priority You can run rebuild and verification operations without taking an array offline. These functions are performed as background tasks on the SmartRAID V controller and are transparent to the host operating system. However, the controller interleaves I/O from the operating system with I/O from the background task and this can affect system performance.
Storage Manager 6-44 I/O Statistics SmartRAID V controllers keep a cumulative record of I/O operations in cache RAM for use in analyzing the efficiency of the storage subsystem. You can view this data by selecting I/O Stats in the Information window for any, controller, drive or array. By analyzing these statistics, the array configuration, cache and stripe size can be optimized for your particular system configuration.
Storage Manager 6-45 Command Statistics Total Comm ands The total number of commands received from the host computer. This includes read and write commands and other commands that may not involve device I/O. M isaligned Transfer The number of commands that required data to be transferred starting at a RAM address location that was not an even byte value. SCSI Bus Resets The total number of SCSI bus resets that have been issued by the controller.
Storage Manager 6-46 I/O Commands The number of read and write commands issued by the computer to the controller. If you use RAID and caching, the number of commands issued to the drives can differ significantly from this value. Total Sectors The total number of sectors read and written from the host computer. The total number of sectors (read or written from the host computer) that were found in the controller cache and did not require a disk access.
Storage Manager 6-47 If cache hits are low, adding more cache RAM can also increase the hit count. Systems with a large number of disk writes also derive significant performance benefits from the controller cache. For RAID 0 and RAID 5 arrays, the default stripe size is set for optimal performance in most environments. However, some specific environments can benefit from smaller or larger stripes.
6-48 Storage Manager Remote Communication The Storage Manager Remote Communication feature lets you use Storage Manager running on your local workstation to manage remote server systems that contain DPT controllers. The Available Connections window shows the types of connections you can use and any predefined connections you have created.
6-49 Storage Manager Communicating Across a Network Storage Manager can run as a client/server application across a network using a TCP/IP connection. The Storage Manager client runs on a supported workstation operating system and connects to one of the supported networked servers running the DPT communication engine. The following illustration shows the supported workstation and server connections for a TCP/IP network.
Storage Manager 6-50 You must configure Remote Communication before it can be used. For both workstations and servers, this is done by editing the DPT configuration file (DPTMGR.INI). There may be additional server configuration steps, depending on your operating system. You must have physical connections between the servers and client workstations. NOTE Under Windows 95/98, the server must be started manually by selecting the DPT Communication Server icon.
Storage Manager 6-51 Setting up the Server If you are using an operating system that supports the DPT communication server and selected the Communication Server option during Storage Manager setup, the server was automatically installed at that time. Additional steps may be required to complete the installation, depending on your operating system. Some operating systems (such as Windows NT) require setting up a user name and/or password before the server can be accessed. The default password is password.
Storage Manager 6-52 SCO UNIX Under SCO UNIX, a communication server entry is placed into the rc.d files, which causes it to be started when the system is booted into multiuser mode. During installation, the file dptcom.chk is created in the directory into which Storage Manager is installed. The ownership of this file is set to root/dtadmain, and permissions are -rw-rw---(6608). Access to SCO servers requires both a user name and password.
Storage Manager 6-53 Connecting to Remote Systems Select Communication–Make Connection to use Storage Manager to manage DPT hardware in a remote server system using the remote communication feature. This menu item displays the Available Connections window. NOTE: You can also use the IP=address command line parameter when you start Storage Manager. This parameter causes Storage Manager to connect to the remote system at the specified IP address instead of the default Local connection.
6-54 Storage Manager Making a Manual Connection Under the Manual Connections section of the Available Connections window, there is an icon the TCP/IP protocol that you configured in the DPTMGR.INI file, and an icon for the system you are using (Local). To make a connection to a remote system, click the icon that represents the protocol for that system. (To select the system from which you are running Storage Manager, select the Local icon).
Storage Manager 6-55 Using the Phonebook You can save the server name, address, user name and protocol of systems you frequently access in the Phonebook. After you have entered data for a system, you can place an icon under Custom Connections to make future connections to that system without having to reenter the connection information each time. To make an entry in the Phonebook, fill in the appropriate fields.
Storage Manager 6-56 Using a Custom Connection Under the Custom Connections section of the Available Connections window, there is one icon for each system that you marked for display in the Phonebook. To make a connection to a remote system, double-click the icon. The Connection Information dialog appears. Enter the password of the server selected. Refer to Connecting Servers and Workstations for details. When you click OK, Storage Manager will attempt to connect to the remote system.
CHAPTER 7: Theory of Operation This chapter provides background and reference information about: Chapter Topics: • Intelligent RAID Controllers • Operation of SmartRAID V controllers • Pipelined Parallel Processing • Disk array configuration • Caching Algorithms • SCSI device interfaces and cabling • RAID Levels • Controller Architecture • I2O Messaging • PCI Data Transfer • On-board Microprocessor • SCSI Interface • Cabling and Termination • Fibre Channel Arbitrated Loop • I2O BIOS 7-1
7-2 Theory of Operation Intelligent RAID Controllers File servers achieve maximum throughput when the performance of their component subsystems is optimized for the CPU bandwidth. If any component is not capable of supplying data at an optimum rate, that component will restrict the data path performance and slow down the entire system. Conversely, a component with significantly greater performance than the rest of the system can have much of its performance potential unused.
Theory of Operation 7-3 Intelligent I/O To maximize the performance of a busy server requires a data storage subsystem that incorporates intelligent I/O. Such a subsystem would have a microprocessor embedded in the I/O and storage subsystem that is dedicated to handling interrupt requests and I/O processing functions in place of the host CPU. Intelligent I/O frees the CPU to process user application software and requests, which significantly increases data throughput and overall system response.
Theory of Operation 7-4 I2O and Intelligent RAID Controllers Several information technology industry leaders have formed a Special Interest Group (SIG) to promote intelligent I/O standards for the entire industry. These standards, referred to as the Intelligent I/O (I2O) specification, address the performance issues caused by I/O interrupts sent to the host CPU and the need for unique drivers for every combination of I/O device and operating system.
7-5 Theory of Operation Pipelined Parallel Processing (P3) Traditional RAID controller designs execute host commands sequentially. Each command initiates a sequence of hardware activities that are processed one after the other until the command is complete. If any of these activities are delayed, hardware components must wait. These delays compromise performance.
Theory of Operation 7-6 • Hardware RAID Processor – DPT’s P 3 architecture is based on a new DPT-exclusive ASIC. This specially designed integrated circuit provides memory-to-memory and disk-to-memory data transfers that are fully concurrent with controller CPU execution. Depending on whether the PCI bus is 32-bit or 64-bit, data transfers occur at 132 or 264 MB/sec data rates, respectively.
7-7 Theory of Operation Software and Hardware Caching The SmartRAID V cache is designed to enhance performance in environments that are already software cached, such as UNIX, Novell and Windows NT. Although software caches are beneficial, hardware caching offers a significant advantage in larger, heavily loaded systems when combined with the software cache for the operating system. The purpose of the operating system cache is to minimize disk reads.
Theory of Operation 7-8 HEAVILY LOADED SYSTEM HEAVILY LOADED SYSTEM With Hardware Cache Without Hardware Cache Application programs write to OS cache: Bus activity: Idle time Idle time Application programs write to OS cache System Bus activity Idle time Idle time OS cache flushes to SmartRAID (1ms per write) SmartRAID Bus OS cache flushes to disk (~11ms per write) SmartRAID elevator-sorted writes to disk (1-5ms per write) As an example, consider an operating system with 4MB of dirty data in it
7-9 Theory of Operation DISK WRITES DISK WRITES Without Elevator Sorting: 11ms average disk write With Elevator Sorting: 1-5ms average disk write 4 65 4 65 93 11 93 17 31 11 17 31 27 27 Caching SmartRAID V controllers can operate in write-back or write-through mode and also use a predictive caching algorithm to optimize disk I/O for the host system. This section describes the methods and rules used by SmartRAID V controllers to cache data for host I/O operations.
Theory of Operation 7-10 Flush Strategy DPT SmartRAID V controllers continually flush all dirty cache pages to disk, with bursts occurring every second and increasing to 4 times per second as the number of dirty pages increases. The data is written to disk in elevator sorted order. The cache flushing routine establishes a flush rate that writes all the dirty pages to disk within three minutes. If there is no host activity, the cache flush will occur in less than three minutes.
7-11 Theory of Operation Pre-Fetch The SmartRAID V pre-fetch algorithm analyses disk access patterns to detect whether the host is reading data that it previously read. By using records stored in virtual cache, the caching algorithm determines the boundaries of the contiguous block of previously read data surrounding the current host read request, then reads that data block into cache.
Theory of Operation 7-12 Caching Host Reads Because there is no advantage in using controller cache to duplicate the operating system cache, SmartRAID V controllers with cache only cache predictive and dirty data. Read cache misses are transferred directly from disk to host, bypassing the controller cache. Optimizing Operating System Cache Size When configuring a server, you should always consider the effect of the operating system cache on the disk subsystem.
Theory of Operation 7-13 RAID The basic idea of RAID (Redundant Array of Independent Disks) is to combine multiple inexpensive disk drives into an array of disk drives to obtain performance, capacity and reliability that exceeds that of a single large drive. The array of drives appears to the host computer as a single logical drive. The Mean Time Between Failure (MTBF) of the array is equal to the MTBF of an individual drive, divided by the number of drives in the array.
Theory of Operation 7-14 STRIPING DISK DRIVES Disk 1 1 5 9 13 Disk 2 2 6 10 14 Disk 3 3 7 11 15 Disk 4 4 8 12 16 Data stripes from each drive are interleaved to create one logical drive. By striping the drives in the array with stripes large enough so that each record falls entirely within one stripe, most records can be evenly distributed across all drives. This keeps all drives in the array busy during heavy load situations.
7-15 Theory of Operation RAID 1, also known as disk mirroring, is simply a pair of disk drives that store duplicate data but appear to the computer as a single drive. Although striping is not used within a single mirrored drive pair, multiple RAID 1 arrays can be striped together to create a single large array consisting of pairs of mirrored drives. All writes must go to both drives of a mirrored pair so that the information on the drives is kept identical.
7-16 Theory of Operation RAID 3, as with RAID 2, sector-stripes data across groups of drives, but one drive in the group is dedicated to storing parity information. RAID 3 relies on the embedded ECC in each sector for error detection. In the case of drive failure, data recovery is accomplished by calculating the exclusive OR (XOR) of the information recorded on the remaining drives. Records typically span all drives, which optimizes the disk transfer rate.
7-17 Theory of Operation RAID 5, sometimes called a Rotating Parity Array, avoids the write bottleneck caused by the single dedicated parity drive of RAID 4. Under RAID 5 parity information is distributed across all the drives. Since there is no dedicated parity drive, all drives contain data and read operations can be overlapped on every drive in the array. Write operations will typically access one data drive and one parity drive.
Theory of Operation 7-18 In summary: • RAID 0 is the fastest and most efficient array type but offers no faulttolerance. RAID 0 requires a minimum of two drives. • RAID 1 is the best choice for performance-critical, fault-tolerant environments. RAID 1 is the only choice for fault-tolerance if no more than two drives are used. • RAID 2 is seldom used today since ECC is embedded in all hard drives. RAID 2 is not supported by SmartRAID V.
Theory of Operation 7-19 Creating Data Redundancy RAID 5 offers improved storage efficiency over RAID 1 because only the parity information is stored, rather than a complete redundant copy of all data. The result is that three or more drives can be combined into a RAID 5 array, with the storage capacity of only one drive dedicated to store the parity information. Therefore, RAID 5 arrays provide greater storage efficiency than RAID 1 arrays.
Theory of Operation 7-20 RAID 5 Updating Parity During Writes XOR WRITE READ DATA XOR READ WRITE PARITY The cost of storing parity, rather than redundant data as in RAID 1, is the extra time required for the write operations to regenerate the parity information. This additional time results in slower write performance for RAID 5 arrays over RAID 1.
Theory of Operation 7-21 Degraded Mode When a drive fails in a RAID 0 array, the entire array fails. In a RAID 1 array, a failed drive reduces read performance by 50%, as data can only be read from the remaining drive. Write performance is increased slightly because only one drive is accessed. A RAID array operating with a failed drive is said to be in degraded mode. RAID 5 arrays synthesize the requested data by reading and XORing the corresponding data stripes from the remaining drives in the array.
Theory of Operation 7-22 SmartRAID V Architecture SmartRAID V controllers can process commands from the operating system using two different protocols: • ASPI (Advanced SCSI Programming Interface), which is compatible with tape and CD-ROM application software. • I2O Messaging, which uses the full performance capability and function of the PCI bus. ASPI Protocol SmartRAID V controllers can communicate with any ASPI protocol device under Windows NT and Windows 95/98.
Theory of Operation 7-23 Command Processing The I 2O messaging protocol is based on the existence of a messaging FIFO (first-in, first-out) queue and a reply FIFO queue. Each queue consists of a list of message frames. The messaging queue contains requests for I/O processing that are read by the HDM. The reply queue is where completion statuses are posted by the controller and read by the OSM. DPT SmartRAID V controllers use I2O messaging to process a command from the host computer as follows: 1.
Theory of Operation 7-24 Command Queuing I2O messaging allows the controller to queue multiple commands from the host and execute them out of order for greater efficiency. When a command is complete, the controller transfers status information to host memory. This status message contains information indicating which command was just completed and enables commands to be executed in a different order than they were issued by the host.
Theory of Operation 7-25 PCI Data Transfer and Bus Mastering The Peripheral Component Interconnect (PCI) bus provides a means to interconnect peripheral chips and expansion cards to the computer backplane. PCI is optimized for peripheral device controllers that transfer data in blocks. PCI allows for data transfer rates of 132MB/sec (32-bit PCI) and 264MB/sec (64-bit PCI). If a Plug-and-Play BIOS is available, automatic expansion card configuration is also available.
Theory of Operation 7-26 On-Board Microprocessor SmartRAID V controllers use embedded processors to maximize their performance when installed in fully loaded servers. The onboard microprocessor performs high-level processing of commands from the host and controls the sequencing of command execution on the controller. A fast microprocessor enables the controller to process more I/O commands per second which is especially important when caching and RAID are used.
Theory of Operation 7-27 Logical Unit Numbers (LUN) A SCSI device may contain up to eight sub-devices or Logical Units, assigned Logical Unit Numbers (LUN) 0 – 7. SmartRAID V controllers support multiple LUNs. However, most devices other than bridge controllers consist of only one LUN and are accessed as LUN 0 by SmartRAID V controllers. Bridge Controllers Bridge controllers are single devices that can, in turn, control multiple peripheral devices.
Theory of Operation 7-28 Transfer Padding and Residue Reporting In unusual cases, a SCSI peripheral device might read or write more data than was requested by the host. If this occurs during a write operation, SmartRAID V controllers automatically transfer pad data by adding additional bytes to the end of the data. If this occurs during a read operation, the controller automatically strips off additional bytes of data read from the device. This prevents the data from overwriting valid data in host memory.
Theory of Operation 7-29 Multi-Mode SCSI To ensure backward compatibility with existing SCSI devices, all SmartRAID V Ultra2 controllers support both LVD and single-ended devices. This is referred to as multimode SCSI. Both types of devices can be attached to the same SCSI bus with the following restrictions: • If all devices on the bus are Ultra2, the bus operates in LVD mode and runs at the maximum Ultra2 speed (40 MHz).
Theory of Operation 7-30 The original SCSI specification synchronous transfer rates of up to 5MHz. The SCSI-2 specification increased the maximum synchronous rate to 10MHz. Devices that support the faster 10MHz rate are called Fast SCSI devices. The SCSI-3 specification defines transfer rates up to 20MHz (Fast20/Ultra SCSI). The SCSI-3 SPI-2 specification defines synchronous data transmission speeds of up to 40MHz.
Theory of Operation 7-31 Beware of capacitance changes. As devices are added to a SCSI bus, capacitance is introduced to each signal from the connectors, receivers, and circuit board traces. The SCSI-3 working specification limits this capacitance to 25pF because added capacitance lowers the impedance of the cable near the device and adds delay. Look for input filters that may be attached to the SCSI front-end of the device’s printed circuit board. These filters add capacitance.
7-32 Theory of Operation Cabling Ultra2 (LVD) SCSI When the total length of a SCSI cable must exceed the maximum length for single-ended buses, DPT recommends the use of an Ultra2 Low Voltage Differential SCSI interface. The following guidelines will help ensure reliability when configuring Ultra2 SCSI systems: • Use twisted-pair cable.
Theory of Operation 7-33 SCSI Termination SCSI termination for SmartRAID V controllers is controlled through Storage Manager or SMOR. Refer to Chapter 3, “Configuration and Installation” for information about setting SCSI termination for SmartRAID V controllers. SmartRAID V controllers contain onboard active SCSI terminators for maximum reliability with Fast and Ultra SCSI devices.
Theory of Operation 7-34 TERMPWR SCSI terminators need power to operate. SmartRAID V controllers always supply power for their own onboard SCSI terminators and, by default, supply termination power for other devices using the TERMPWR line on the SCSI cable. Most SCSI devices allow the way in which TERMPWR is supplied to their onboard SCSI terminators to be selected using jumpers on the device. Devices that supply SCSI bus termination should be configured to supply their own isolated TERMPWR.
Theory of Operation 7-35 Fibre Channel Arbitrated Loop (FC-AL) Fibre Channel is an industry standard set of protocols for information transfer using a serial bus. Fibre Channel provides for reliable high-speed transfer of large amounts of information over long cable lengths. SmartRAID V Fibre Channel controllers support transfer rates of 1GHz among up to 126 devices over a maximum of 30 meters (98 feet) of copper or 10 km (6.2 miles) of optical cable.
Theory of Operation 7-36 DPT I2O BIOS SmartRAID V controllers are shipped with the DPT I 2O BIOS loaded on an EEPROM. This BIOS intercepts and processes Int13 requests with an embedded DOS driver. The host system Plug-and-Play BIOS can automatically disable or change the address of the I 2O BIOS ROM. In systems with multiple DPT controllers, the first DPT I2O controller found during boot loads its BIOS and installs all of the DPT I2O hardware on the system.
APPENDIX A: Assembly Drawings This chapter contains outline drawings of DPT’s SmartRAID V products with jumpers and connectors labeled for easy reference. Millennium Controllers PM3755F PM3755U2B PM3754U2 See the SmartRAID V Controller LEDs section in Chapter 2 for specific information about the LED indicators on your controller or module.
A-2 Assembly Drawings PM3755F ECC EN pin-1 P9 P6 P4 ECC ERR pin-1 87654321 IRQ Audible Alarm J9 SIMM 1 SIMM 2 SIMM 3 J8 J7 SIMM 4 P4 Pins 1-2 NVRAM Clear Pins 3-4 Misc (Reserved, do not use) P6 Disk Activity LED Connector P9 Pins 1-2 Load Pins 3-4 Run J7 32-bit Bus Expansion Module Connector J8 64-bit Bus Expansion Module Connector J9 External Fibre Channel HSSDC Connector (Bus 0) 1…8, IRQ Adapter Activity LEDs ECC EN ECC Enabled LED (Green) ECC ERR ECC Error LED (Red)
Assembly Drawings A-3 PM3755U2B J10 pin-1 ECC EN 87654321 P6 IRQ ECC ERR pin-1 P4 DIMM 3 & 4 J12 pin-1 J7 J11 J8 P9 pin-1 Audible Alarm RUN LOAD P4 Pins 1-2 NVRAM Clear Pins 3-4 Misc (Reserved, do not use) P6 Disk Activity LED Connector P9 Pins 1-2 Load Pins 3-4 Run J7 32-bit Bus Expansion Module Connector J8 64-bit Bus Expansion Module Connector J10 Internal Wide Ultra2 SCSI Connector (Bus 0) J11 External Wide Ultra2 SCSI Connector (Bus 0) 1…8, IRQ Adapter Activity LEDs E
A-4 Assembly Drawings PM3754U2 P4 J10 pin-1 ECC EN P6 87654321 IRQ ECC ERR pin-1 Audible Alarm pin-1 J11 pin-1 SIMM 1 P9 J4 SIMM 2 SIMM 3 SIMM 4 P4 Pins 1-2 NVRAM Clear Pins 3-4 Misc (Reserved, do not use) P6 Disk Activity LED Connector P9 Pins 1-2 Load Pins 3-4 Run J4 Bus Expansion Module Connector J10 Internal Wide Ultra2 SCSI Connector (Bus 0) J11 External Wide Ultra2 SCSI Connector (Bus 0) 1…8+IRQ Adapter Activity LEDs ECC EN ECC Enabled LED (Green) ECC ERR ECC Error LED
Assembly Drawings A-5 PM1554U2, PM2554U2 and PM2654U2 pin-1 87654321 IRQ P6 P9 pin-1 pin-1 J11 J7 P4 Pins 1-2 NVRAM Clear Pins 3-4 Misc (Reserved, do not use) P6 Disk Activity LED Connector P9 Pins 1-2 Retry (Reserved, do not use) Pins 3-4 Reset (Reserved, do not use) J7 Bus Expansion Module Connector J10 Internal Ultra2 Wide SCSI Connector (Bus 0) J11 External Ultra2 Wide SCSI Connector (Bus 0) 1…8, IRQ Adapter Activity LEDs P4 RA4050 Module Connector J10
A-6 Assembly Drawings SX4054U2-1 Bus Expansion Module pin-1 J2 pin-1 J3 P5 J2 Internal Ultra2 Wide SCSI Connector (Bus 1) J3 External Ultra2 Wide SCSI Connector (Bus 1) P5 Mating Connector for SmartRAID V Controller
Assembly Drawings A-7 SX4054U2-2 Bus Expansion Module pin-1 J4 pin-1 J2 pin-1 J3 P5 pin-1 J1 J1 External Ultra2 Wide SCSI Connector (Bus 2) J2 Internal Ultra2 Wide SCSI Connector (Bus 1) J3 External Ultra2 Wide SCSI Connector (Bus 1) J4 Internal Ultra2 Wide SCSI Connector (Bus 2) P5 Mating Connector for SmartRAID V Controller
A-8 Assembly Drawings SX4055U2-1 Bus Expansion Module pin-1 J2 pin-1 J3 P5 P3 J2 Internal Wide Ultra2 SCSI Connector (Bus 1) J3 External Wide Ultra2 SCSI Connector (Bus 1) P3 64-bit SmartRAID V Adapter Connector P5 Mating Connector for SmartRAID V Controller
Assembly Drawings A-9 SX4055U2-2 Bus Expansion Module pin-1 J4 pin-1 J2 pin-1 J3 P5 P3 pin-1 J1 J1 External Wide Ultra2 SCSI Connector (Bus 2) J2 Internal Wide Ultra2 SCSI Connector (Bus 1) J3 External Wide Ultra2 SCSI Connector (Bus 1) J4 Internal Wide Ultra2 SCSI Connector (Bus 2) P3 64-bit SmartRAID V Adapter Connector P5 Mating Connector for SmartRAID V Controller
A-10 Assembly Drawings SX4055F FC-AL Bus Expansion Module P5 P3 P2 P2 Fibre Channel (FC-AL) Connector (Bus 1) P3 64-bit SmartRAID V Adapter Connector P5 Mating Connector for SmartRAID V Controller
Assembly Drawings A-11 ECC ERR ECC EN RA4050 RAID Accelerator Docking Guide J1 SIMM 1 Docking Connector SIMM 2 SIMM 3 SIMM 4 Docking Guide J1 Docking Connector ECC EN ECC Enabled LED (Green) ECC ERR ECC Error LED (Red) Audible Alarm
A-12 Assembly Drawings BB4050 Battery Module TRICKLE Stability Bracket mounting location J1 CHARGE Mounting Hole P12 Mounting Holes Board shown without Stability Bracket J1 Battery Cable Connector P12 Connector for SmartRAID V PM3755U2B TRICKLE LED indicator for trickle charge activity CHARGE LED indicator for charging/recharging cycle ! CAUTION ! Danger of explosion if battery is incorrectly replaced. Replace only with the same or equivalent type recommended by the manufacturer.
APPENDIX B: Troubleshooting This chapter provides answers to many commonly asked questions. If a situation occurs that is not covered in this chapter, or if the recommendations here do not correct the problem, contact DPT Technical Support. We are always ready to assist you. DPT Technical Support Phone: 407-830-5522 (Press 6 and follow the prompts.) Fax: 407-830-4793 Internet: http://www.dpt.
B-2 Troubleshooting Problem: When the DPT I2O BIOS displays the peripheral devices at system boot, a device does not appear. Solution: The following conditions can cause this to occur: The device ID might be set to the same ID as the DPT controller (ID 7). Ensure that all devices have a unique ID. Fibre Channel devices automatically configure a unique ID for each device on the bus. The device might not be powered on. The device is not connected to the SCSI cable or the connection is loose.
Troubleshooting Problem: B-3 The controller does not respond and one of the following LED patterns occurs at power-up: LEDs 6 and 7 alternating with LEDs 5 and 8 LEDs 5 and 6 alternating with LEDs 7 and 8 LEDs 5 and 7 alternating with LEDs 6 and 8 Solution: These patterns indicate that the DPT controller is not being configured by the motherboard BIOS. SmartRAID V Century controllers require a motherboard BIOS that supports multifunction devices, where one of the devices is a PCI-PCI bridge.
Troubleshooting B-4 Problem: The controller does not respond and various LEDs in the 1–4 range flash once per second. Solution: This pattern indicates an internal microprocessor trap occurred in the controller. Remove all attached devices, cables and option modules and retry. If the trap error disappears, reconnect the cables and devices, one device at a time, until the faulty device, cable or module is isolated. If the error persists, contact DPT Technical Support.
Troubleshooting B-5 Problem: The SmartRAID V controller I2O BIOS reports the drive as a disk instead of a drive. Solution: This typically happens when a drive that is attached to a SmartRAID V controller has been formatted with a sector size other than 512 bytes . Use Storage Manager or SMOR to reformat the drive with 512 byte sectors. This can also occur if the drive is the 9th or higher logical drive attached to the controller.
Troubleshooting B-6 Problem: After updating the SmartRAID V controller firmware or BIOS and rebooting, LEDs 1 and 5 or 2 and 5 flash once per second. Solution: These patterns indicate that the adapter startup code detected a firmware checksum error or a flash error. Attempt the firmware update procedure again by using the procedure in the following Problem description to recover from this condition. Problem: A flash ROM upgrade is unsuccessful, causing the controller to hang.
Troubleshooting B-7 Problem: After a flash ROM upgrade of the I 2O BIOS only, pressing Ctrl+D at the system prompt displays the message Card not configurable. Solution: Perform a flash ROM upgrade for SMOR to correct this condition. Problem: The floppy disk drive cannot be accessed after installing a DPT controller. Solution: Use SMOR to enable the EBDA Relocation option. Problem: The controller’s audible alarm is sounding during normal operation. Solution: This indicates a drive has failed.
B-8 Troubleshooting
APPENDIX C: Specifications This chapter lists the electrical and environmental specifications for the SmartRAID V product line.
C-2 Specifications DC Power Requirements Voltage: 5 V ± 5% Ripple and Noise: 50mv peak-to-peak max Component Current (typical) PM3754U2B 1.82A PM3755U2B 1.90A PM3755F 1.82A PM2654U2 1.63A (with SX4054U2) 1.60A (with SX4055F) 1.35A (with RA4050; no cache) PM2554U2 1.15A PM1554U2 1.15A RA4050 0.20A SX4054U2 0.48A SX4055U2 0.98A SX4055F 0.45A BB4050 0.27A (not charging) 1.16A (charging) SM4050-16 0.16A SM4050-64 0.16A Voltage: 3.
C-3 Specifications Environmental Specifications Ambient Temp (operating): 10° C to 50° C 10° C to 40° C (PM3755U2B with BB4050) Relative Humidity (operating): 10% to 90% non-condensing Altitude (operating): 3,000 meters (10,000 feet) NOTE Maximum ambient temperature is 40°C when using a BB4050 module. Memory SmartRAID V controllers accept up to four memory modules. The total memory installed must not exceed the maximum cache capacity of the controller.
C-4 Specifications DIMMs DIMMs to be installed in SmartRAID V controllers must be DPT DM4050 or DM4060 memory modules only. Use of non-DPT DIMMs can result in data corruption. Battery The following applies to the BB4050 module only: Type: Capacity: Backup time: Charge time: Operating Temp: Nickel Metal Hydride 3800mAH (minimum) 72 hours (with one 16MB memory module installed) 3 hours 10° C to 40° C Exceeding the temperature limits can shorten the battery life and reduce the battery capacity.
APPENDIX D: SNMP Simple Network Management Protocol (SNMP) is an industry-wide standard protocol designed to allow you to remotely manage your computer network. By using the DPT SNMP subagent and an SNMP-based management console, you can get the DPT hardware configuration and information for your servers from a remote workstation.
D-2 Simple Network Management Protocol Introduction Simple Network Management Protocol (SNMP) lets you obtain basic DPT hardware configuration and status information from an SNMP-based management console. You can also receive SNMP Traps, which are messages about changes in the hardware status. These messages alert you to important events that affect the DPT hardware and attached devices.
Simple Network Management Protocol D-3 Every system resource to be managed is represented as an object and the MIB is a collection of these objects. In a network environment each system (workstation or server) maintains a copy of the MIB containing the current status of the objects which it defines. The MIB information is kept up-to-date by a software agent. At the operating system level, there is a Master Agent that controls the system MIB.
D-4 Simple Network Management Protocol Refer to the MIB itself for the exact contents of each of these groups. The following lists are the groups’ contents: DPT SCSI System Modules group identifies the versions, creation date and various capabilities of the software modules. The following specific modules are included: DPT SNMP Subagent DPT SNMP Engine DPT SCSI Driver DPT SCSI Logger MIB revision information DPT SCSI Controller group is a list of all DPT controllers in the system.
Simple Network Management Protocol D-5 DPT SCSI Device group is a list of SCSI Devices managed by the DPT SCSI subsystem and represents the physical configuration. For each device in the system there is: Device SCSI Address information: Controller Bus ID LUN Device SCSI Inquiry data Device Capacity and Block Size Device RAID level and status (Optimal, Failed, etc.) DPT SCSI Array group contains all the RAID-specific information within the DPT SCSI subsystem.
D-6 Simple Network Management Protocol What’s Included The DPT SNMP software components are included on the diskettes in the DPT controller package. Specific components vary by operating system. The Windows 95/98 and Windows NT components are on the DPT Windows diskette.
Simple Network Management Protocol D-7 Operating System Support The following table lists the environments in which DPT hardware is manageable from an SNMP management console: Operating System Comments Novell NetWare Versions 4.11, 4.2 and 5.0 Windows 95/98 Windows NT 4.0 Workstation and Server versions Installation of DPT SNMP Software The following topics describe how to install DPT SNMP subagent software components and how to install SNMP support for Microsoft Windows 95/98 and Windows NT 4.0.
Simple Network Management Protocol D-8 Installing SNMP for Microsoft Windows 95 If your operating system is Windows 95, the SNMP Service must be installed by following these steps: 1. Insert the Windows 95 Installation CD-ROM into your CD-ROM drive. If the Autostart window appears, close the window. 2. Launch the Network icon in Control Panel. Click Add and select Service as the type of network component to install. 3. Click Add, then click the Have Disk button.
Simple Network Management Protocol D-9 Operation Before you can view information about your DPT hardware, you must install the DPT Management Information Base (MIB) into the Management Console database. During the installation of the SNMP feature, the DPT MIB is installed by default as DPTMGR\DPTSCSI.MIB. Refer to your SNMP Management Console documentation for more information about adding this MIB to your existing database. The DPT SNMP sub-agent can be accessed from any SNMP Management Console.
D-10 Simple Network Management Protocol TC P/IP SNM P M anagem ent Console SNM P M aster Agent DPT SCS I Sub-Agent SN MP Trap Broadcast M odule DPT Engine DPT Event Logger DPT Driver D P T C ontroller DPT SNMP Sub-Agent The DPT SNMP sub-agent attaches to the operating systemspecific Master Agent to handle SNMP requests for objects defined in the DPT MIB. It also broadcasts the DPT-specific Traps to the designated management consoles.
Simple Network Management Protocol D-11 DPT SNMP Trap Broadcaster Module The SNMP Trap implementation uses the Broadcaster feature of the DPT Event Logger. The Event Logger has individual broadcast modules that have complete control over how events are received from the Event Logger. The modules define what events are to be sent and how they want to receive the event information. Each broadcast module has control over which events are to be broadcast, how they are broadcast and where they are sent.
D-12 Simple Network Management Protocol
Glossary This glossary provides brief definitions of selected terms and acronyms used throughout this manual.
G-2 Glossary Adapter SCSI Host Bus Adapter or HBA ANSI American National Standards Institute. Arbitrated Loop See FC-AL. Bridge Controller A device which appears as a single device on the bus, but which bridges to multiple devices. Bridge controllers are typically used to overcome limitations on the number of devices that can be on a single bus or to control remote subsystems. Array Group A group of disk drives that appear to the computer as a single logical drive.
Glossary Controller A device that controls the transfer of data between a computer and a peripheral device. For example, disk drives, video displays, keyboards, and printers all require controllers. The DPT SmartRAID V is a controller for disk drives and disk arrays. See also, HBA. DAE Dynamic Array Expansion. A feature that enables you to increase your storage capacity under Windows NT by adding one or more drives to your RAID 0 and RAID 5 arrays while your system remains online.
G-4 Glossary EDO DRAM Extended Data Output DRAM. A type of RAM that improves memory read performance on systems that are designed to use EDO memory. Flash ROM A nonvolatile memory device on the controller that can be reprogrammed using special software without removing it from the board. Elevator Sorting A method of sorting records or cache pages by physical location on disk so that the information can be written to disk with less seek and rotational latency.
Glossary HSSDC High Speed Serial Data Connector. The industry standard modular connector used on Fibre Channel controllers. I 2O Intelligent I/O Architecture. A proprietary specification that provides a standardized software interface between peripheral devices with built-in intelligence and a host operating system. ID A numeric value used by SCSI devices to address one another. (IDs can be from 0 to 7 or 0 to 15 for Wide SCSI.) Fibre Channel devices can have ID numbers from 0 to 126.
G-6 Glossary MTBF Mean Time Between Failure. The average time between expected failures of a device in a large sample group of devices. Multilevel RAID A method of combining multiple RAID 1 or RAID 5 arrays into a single array, providing increased storage and performance in multiuser environments. Non-Redundant Array An Array Group with no fault tolerance (RAID 0). If only one drive in a non-redundant array fails, the entire array will fail. NVRAM Nonvolatile Random Access Memory.
Glossary SAF-TE SCSI Accessed Fault-Tolerant Enclosure. A specification (co-developed by nStor Corporation, Inc. and Intel Corp.) which provides a standardized method for monitoring and reporting on the condition of disk drives, power supplies and cooling systems used in high availability LAN servers and storage subsystems.
G-8 Glossary Termination A method of matching the transmission impedance of an electrical bus so that signal reflections are minimized or eliminated. TERMPWR A signal line on the SCSI bus that supplies electric power for SCSI bus terminators. Throughput A term used to describe the amount of data that can be processed or transmitted by a system in a given amount of time. Tree View The view in SMOR that provides a graphic display of all controllers and devices on the system in a hierarchical format.
Index Index address controller 3-16, 4-13 I2O BIOS 7-36 logical device 6-7 alarm audible 2-13, 6-39 disable 2-13, 6-39 testing 6-15 architecture, SmartRAID V 7-22 array group building with SMOR 4-21 building with Storage Manager 6-23 caching configuration 6-18 copying data 6-23 creating 4-20, 6-22 deleting 4-23, 6-28 expanding 6-26 hot spare rebuild 6-41 information (SMOR) 4-17 modifying 6-24 naming 6-24 number of drives 6-19 rebuilding 6-21, 6-40 starting a build 6-28 task priority 6-43 ASPI protocol 7-22
I-2 cache caching host reads 7-12 configuring 6-18, 7-6 DIMM, installing 3-13 DOS/Windows 3.1 setting 4-10 flushing 7-7, 7-10 operating system 7-7 operating system, size of 7-12 optimizing size 7-12 predictive 2-4, 6-19, 7-10 requirements 3-11, 3-13 SIMM, installing 3-11 virtual 7-6, 7-10 write-back vs.
Index event notification broadcasters 6-34 configuring 6-31 NetWare 6-34 pager messages 6-33 SCO Unix 6-35 SCO UnixWare 6-35 SNMP D-11 Windows NT 6-36 expanding arrays 6-26 extended BIOS data area definition of G-3 relocation, enabling 4-10 SMOR parameter 4-10 troubleshooting B-2, B-7 extended Int 13 4-10 F Fibre Channel cable 3-3 configuration 3-3, 3-6 connector 3-3, 7-35 controller 2-5, A-2 description of 7-35 device ID 3-6 expansion module 2-6, 2-8 firmware file name 4-27 restoring from disk 4-28 saving
I-4 Int 13, extended 4-10 IRQ 3-16 K keys, SMOR navigation 4-3 L LED battery module 2-13, A-12 cache status 2-12 Century/Decade, location of A-5 controller active 2-12 controller idle 2-11 disk activity 3-15 ECC enabled 3-11, 3-13 PM375x, location of A-3 power up sequence 2-11 RA4050, location of A-11 Linux driver installation 5-25 Storage Manager 5-26 locality of reference 7-10 logical block addressing 4-10 logical device address 6-7 logical storage unit (LSU) 6-19 logical unit number (LUN) 7-27 LVD SCSI
Index Windows 95/98 5-7 Windows NT 5-2 operating system services module (OSM) description of 7-22 dynamic array expansion 6-25 Microsoft Windows 5-2, 5-6 P pager event notification 6-33 parity group 7-18 partial stripe write 7-19 password, remote communication changing 6-51 default 6-51 SCO servers 6-52 Windows 95/98 6-51 Windows NT 6-51 PCI bus 2-5, 7-25 performance caching 7-6 intelligent I/O 7-3 pipelined parallel processing 7-5 physical configuration view 6-4 pipelined parallel processing 7-5 powerup b
I-6 devices, number of 3-6 differential 7-28 LUNs 7-27 LVD 7-28 LVD cabling 7-32 mixing LVD and non-LVD devices 7-29 multi-mode 7-29 residue reporting 7-28 single-ended cabling 7-30 singled-ended 7-28 synchronous 7-29 termination 3-4, 7-33 TERMPWR 4-13, 4-14, 7-34 transfer padding 7-28 transfer rate 7-30 Ultra2 cabling 7-32 wide 3-3, 3-6, 7-29 SES (SCSI Enclosure Services) G-7 SIMM installing 3-11 restrictions 3-11 single-ended SCSI 7-28 SM4050, installing 3-11 SmartRAID V architecture 7-22 configuration 6-
Index event notification 6-31, 6-34 NetWare 6-34 SCO Unix 6-35 SCO UnixWare 6-35 Windows NT 6-36 I/O statistics 6-44 Linux installation 5-26 modem operation 6-48 network operation 6-3, 6-48 overview 6-2 physical configuration view 6-4 platforms supported 5-1 remote operation 6-3, 6-48 running 6-3 SCO UNIX installation 5-14 system requirements 6-2 Windows installation 5-13 striping 7-13 sub-agent, SNMP D-10 SX405x connectors 2-9 features 2-8 installation 3-9 types 2-8 synchronous SCSI 7-29 system requirement
