MegaRAID Enterprise 1600 Hardware Guide MAN-471 6/12/01
© Copyright 2001 LSI Logic Corporation All rights reserved. LSI Logic Corporation 6145-D Northbelt Parkway Norcross, GA 30071 This publication contains proprietary information which is protected by copyright. No part of this publication can be reproduced, transcribed, stored in a retrieval system, translated into any language or computer language, or transmitted in any form whatsoever without the prior written consent of the publisher, LSI Logic Corporation.
Table of Contents 1 Overview................................................... 1 Single Ended and Differential SCSI Buses .......................2 Maximum Cable Length for SCSI Standards....................2 Documentation Set............................................................3 2 Introduction to RAID................................ 5 RAID Overview................................................................5 RAID Levels .....................................................................
Table of Contents, Continued 5 Configuring MegaRAID.......................... 33 Configuring SCSI Physical Drives..................................33 Current Configuration.....................................................34 Logical Drive Configuration...........................................36 Physical Device Layout ..................................................37 Configuring Arrays .........................................................39 Configuration Strategies ...............................
Table of Contents, Continued 7 Cluster Installation and Configuration. 75 Software Requirements ...................................................75 Hardware Requirements..................................................76 Installation and Configuration ........................................77 Driver Installation Instructions under Microsoft Windows 2000 Advanced Server....................................78 Network Requirements ...................................................
Preface The MegaRAID Enterprise 1600 64-Bit 160M (Low Voltage Differential SCSI) I2O PCI Disk Array Controller supports four Ultra and Wide SCSI channels with data transfer rates up to 160 MB/s. This manual describes the MegaRAID Enterprise 1600 64-Bit 160M controller.
Preface, Continued Package Contents You should have received: • • • • • • • a MegaRAID Enterprise 1600 64-Bit 160M Controller a CD with drivers, utilities, and documentation a MegaRAID Enterprise 1600 Hardware Guide a MegaRAID Configuration Software Guide a MegaRAID Operating System Drivers Guide software license agreement warranty registration card Technical Support If you need help installing, configuring, or running the MegaRAID Controller, call LSI Logic Technical Support at 678-728-1250.
MegaRAID Problem Report Form Customer Information Name Company Address City/State Country email address Phone Fax Motherboard: Operating System: Op. Sys. Ver.: MegaRAID Driver Ver.
Logical Drive Configuration Logical Drive RAID Level Stripe Size Logical Drive Size Cache Policy Read Policy Write Policy # of Physical Drives LD0 LD1 LD2 LD3 LD4 LD5 LD6 LD7 LD8 LD9 LD10 LD11 LD12 LD13 LD14 LD15 LD16 LD17 LD18 LD19 LD20 LD21 LD22 LD23 LD24 LD25 LD26 LD27 LD28 LD29 LD30 LD31 LD32 LD33 LD34 LD35 LD36 LD37 LD38 LD39 Preface ix
Physical Device Layout Channel A Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number
Channel A Channel B Channel C Channel D Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware l
Disclaimer Disclaimer This manual describes the operation of the LSI Logic MegaRAID Controller.
FCC Regulatory Statement This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. 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.
xiv MegaRAID Enterprise 1600 Hardware Guide
1 Overview The MegaRAID® Enterprise 1600 LVD (Low Voltage Differential SCSI) PCI RAID controller adapter card provides four SCSI channels. Using LVD, you can use cables up to 25 meters long. Throughput on each SCSI channel can be as high as 160 MB/s. MegaRAID supports both a low voltage differential SCSI bus or a single ended SCSI bus. MegaRAID Enterprise 1600 64-Bit LVD is a high performance intelligent PCI-to-SCSI host adapter with RAID control capabilities.
Single Ended and Differential SCSI Buses The SCSI standard defines two electrical buses: • • a single ended bus a differential bus Maximum Cable Length for SCSI Standards Standard Single ended LVD SCSI I Fast SCSI Fast Wide SCSI Ultra SCSI Ultra SCSI Wide Ultra SCSI Wide Ultra SCSI Wide Ultra SCSI Ultra2 SCSI Ultra2 SCSI Wide Ultra2 SCSI Wide Ultra2 SCSI 6m 6m 6m 1.5 m 3m 12 m 12 m 12 m 12 m 12 m 12 m 12 m 12 m 25 m 12 m 25 m 12 m 1.
Documentation Set The MegaRAID Enterprise 1600 64-Bit LVD technical documentation set includes: • • • • the MegaRAID Enterprise 1600 Hardware Guide the MegaRAID Configuration Software Guide the WebBIOS Guide the MegaRAID Operating System Drivers Guide Using MegaRAID Enterprise 1600 Manuals The MegaRAID Enterprise 1600 Hardware Guide includes a RAID overview, RAID planning, and RAID system configuration information. Read it first.
4 MegaRAID Enterprise 1600 Hardware Guide
2 Introduction to RAID RAID (Redundant Array of Independent Disks) is an array of multiple independent hard disk drives that provide high performance and fault tolerance. A RAID disk subsystem improves I/O performance. The RAID array appears to the host computer as a single storage unit or as multiple logical units. I/O is faster because drives can be accessed simultaneously. RAID improves data storage reliability and fault tolerance.
RAID Levels RAID (Redundant Array of Independent Disks) is a collection of specifications that describe a system for ensuring the reliability and stability of data stored on large disk subsystems. A RAID system can be implemented in a number of different versions (or RAID Levels). The standard RAID levels are 0, 1, 3, and 5. MegaRAID supports all standard RAID levels and RAID levels 10, 30, and 50, special RAID versions supported by MegaRAID.
Disk Striping Disk striping writes data across multiple disk drives instead of just one disk drive. Disk striping involves partitioning each drive storage space into stripes that can vary in size from 2 KB to 128 KB. These stripes are interleaved in a repeated sequential manner. The combined storage space is composed of stripes from each drive. MegaRAID supports stripe sizes of 2 KB, 4 KB, 8 KB, 16 KB, 32 KB, 64 KB, or 128 KB.
Disk Mirroring With mirroring (used in RAID 1), data written to one disk drive is simultaneously written to another disk drive. If one disk drive fails, the contents of the other disk drive can be used to run the system and reconstruct the failed drive. The primary advantage of disk mirroring is that it provides 100% data redundancy. Since the contents of the disk drive are completely written to a second drive, it does not matter if one of the drives fails. Both drives contain the same data at all times.
Disk Spanning Disk spanning allows multiple disk drives to function like one big drive. Spanning overcomes lack of disk space and simplifies storage management by combining existing resources or adding relatively inexpensive resources. For example, four 400 MB disk drives can be combined to appear to the operating system as one single 1600 MB drive. Spanning alone does not provide reliability or performance enhancements. Spanned logical drives must have the same stripe size and must be contiguous.
Parity Parity generates a set of redundancy data from two or more parent data sets. The redundancy data can be used to reconstruct one of the parent data sets. Parity data does not fully duplicate the parent data sets. In RAID, this method is applied to entire drives or stripes across all disk drives in an array. A dedicated parity scheme during normal read/write operations is shown below.
Hot Spares A hot spare is an extra, unused disk drive that is part of the disk subsystem. It is usually in standby mode, ready for service if a drive fails. Hot spares permit you to replace failed drives without system shutdown or user intervention. MegaRAID implements automatic and transparent rebuilds using hot spare drives, providing a high degree of fault tolerance and zero downtime. MegaRAID RAID Management software allows you to specify physical drives as hot spares.
Disk Rebuild You rebuild a disk drive by recreating the data that had been stored on the drive before the drive failed. Rebuilding can be done only in arrays with data redundancy such as RAID level 1, 3, 5, 10, 30, and 50. Standby (warm spare) rebuild is employed in a mirrored (RAID 1) system. If a disk drive fails, an identical drive is immediately available. The primary data source disk drive is the original disk drive. A hot spare can be used to rebuild disk drives in RAID 1, 3, 5, 10, 30, or 50 systems.
Logical Drive A logical drive is a partition in a physical array of disks that is made up of contiguous data segments on the physical disks. A logical drive can consist of any of the following: • • • • • an entire physical array more than one entire physical array a part of an array parts of more than one array a combination of any two of the above conditions Hot Swap A hot swap is the manual replacement of a defective physical disk unit while the computer is still running.
Disk Array Types The RAID disk array types are: Type SoftwareBased SCSI to SCSI Bus-Based Description The array is managed by software running in a host computer using the host CPU bandwidth. The disadvantages associated with this method are the load on the host CPU and the need for different software for each operating system. The array controller resides outside of the host computer and communicates with the host through a SCSI adapter in the host. The array management software runs in the controller.
3 RAID Levels There are six official RAID levels (RAID 0 through RAID 5). MegaRAID supports RAID levels 0, 1, 3, and 5. LSI Logic has designed three additional RAID levels (10, 30, and 50) that provide additional benefits.
Selecting a RAID Level The factors you need to consider when selecting a RAID level are listed below. Level Description and Use Pros Cons 0 Data divided in blocks and distributed sequentially (pure striping). Use for non-critical data that requires high performance. Data duplicated on another disk (mirroring). Use for read-intensive fault-tolerant systems Disk striping with a dedicated parity drive. Use for noninteractive apps that process large files sequentially.
RAID 0 RAID 0 provides disk striping across all drives in the RAID subsystem. RAID 0 does not provide any data redundancy, but does offer the best performance of any RAID level. RAID 0 breaks up data into smaller blocks and then writes a block to each drive in the array. The size of each block is determined by the stripe size parameter, set during the creation of the RAID set. RAID 0 offers high bandwidth.
RAID 1 In RAID 1, MegaRAID duplicates all data from one drive to a second drive. RAID 1 provides complete data redundancy, but at the cost of doubling the required data storage capacity. Uses Use RAID 1 for small databases or any other environment that requires fault tolerance but small capacity. Strong Points RAID 1 provides complete data redundancy. RAID 1 is ideal for any application that requires fault tolerance and minimal capacity. Weak Points RAID 1 requires twice as many disk drives.
RAID 3 RAID 3 provides disk striping and complete data redundancy though a dedicated parity drive. The stripe size must be 64 KB if RAID 3 is used. RAID 3 handles data at the block level, not the byte level, so it is ideal for networks that often handle very large files, such as graphic images. RAID 3 breaks up data into smaller blocks, calculates parity by performing an exclusive-or on the blocks, and then writes the blocks to all but one drive in the array.
RAID 3, Continued RAID 5 vs RAID 3 You may find that RAID 5 is preferable to RAID 3 even for applications characterized by sequential reads and writes, because MegaRAID has very robust caching algorithms and hardware based exclusive-or assist. The benefits of RAID 3 disappear if there are many small I/O operations scattered randomly and widely across the disks in the logical drive. The RAID 3 fixed parity disk becomes a bottleneck in such applications.
RAID 5 RAID 5 includes disk striping at the byte level and parity. In RAID 5, the parity information is written to several drives. RAID 5 is best suited for networks that perform a lot of small I/O transactions simultaneously. RAID 5 addresses the bottleneck issue for random I/O operations. Since each drive contains both data and parity numerous writes can take place concurrently.
RAID 10 RAID 10 is a combination of RAID 0 and RAID 1. RAID 10 has mirrored drives. RAID 10 breaks up data into smaller blocks, and then stripes the blocks of data to each RAID 1 raid set. Each RAID 1 raid set then duplicates its data to its other drive. The size of each block is determined by the stripe size parameter, which is set during the creation of the RAID set. RAID 10 can sustain one to four drive failures while maintaining data integrity if each failed disk is in a different RAID 1 array.
RAID 30 RAID 30 is a combination of RAID 0 and RAID 3. RAID 30 provides high data transfer speeds and high data reliability. RAID 30 is best implemented on two RAID 3 disk arrays with data striped across both disk arrays. RAID 30 breaks up data into smaller blocks, and then stripes the blocks of data to each RAID 3 raid set. RAID 3 breaks up data into smaller blocks, calculates parity by performing an exclusive-or on the blocks, and then writes the blocks to all but one drive in the array.
RAID 50 RAID 50 provides the features of both RAID 0 and RAID 5. RAID 50 includes both parity and disk striping across multiple drives. RAID 50 is best implemented on two RAID 5 disk arrays with data striped across both disk arrays. RAID 50 breaks up data into smaller blocks, and then stripes the blocks of data to each RAID 5 raid set.
4 Features MegaRAID Enterprise 1600 64-Bit LVD has four SCSI channels that support 160M and Wide SCSI, with data transfer rates of up to 160 MB/s per SCSI channel. Each SCSI channel supports up to 15 Wide devices and up to seven non-Wide devices.
Configuration on Disk Configuration on Disk (drive roaming) saves configuration information both in NVRAM on MegaRAID and on the disk drives connected to MegaRAID. If MegaRAID is replaced, the new MegaRAID controller can detect the actual RAID configuration, maintaining the integrity of the data on each drive, even if the drives have changed channel and/or target ID. Hardware Requirements MegaRAID can be installed in an IBM AT®-compatible or EISA computer with a motherboard that has PCI expansion slots.
Hardware Architecture Features Specification Processor SCSI Controller memory type Size of Flash ROM Amount of NVRAM Hardware XOR assistance Direct I/O Removable battery-backed cache memory module SCSI bus termination Double-sided DIMMs Direct I/O bandwidth Feature Intel i960RN One Q-Logic 12160 Dual SCSI controllers One 64-bit 168-pin SDRAM DIMM socket provides write-through or write-back caching on a logical drive basis. It also provides adaptive readahead.
RAID Management Features The MegaRAID RAID management features include: Specification Support for SNMP Performance Monitor provided Remote control and monitoring Event broadcast and event alert Hardware connector Drive roaming Support for concurrent multiple stripe sizes Windows NT and NetWare server support via GUI client utility SCO Unix, OS/2, and UnixWare server support via GUI client utility DMI support Management through an industrystandard browser Feature Yes Yes Yes Yes RS232C Yes Yes Yes Yes Yes Y
Operating System Software Drivers Operating System Drivers MegaRAID includes a DOS software configuration utility and drivers for all major operating systems. See the MegaRAID Operating System Drivers Guide for additional information. The DOS drivers for MegaRAID are contained in the firmware on MegaRAID except the DOS ASPI and CD-ROM drivers. Call LSI Logic Technical Support at 678-728-1250 or access the web site at www.lsil.com for information about drivers for other operating systems.
Components The MegaRAID controller uses the 64-bit Intel i960RN Intelligent I/O processor with an embedded 32-bit 80960 Jx RISC processor that runs at 100 MHz. This processor directs all functions of the controller including command processing, PCI and SCSI bus transfers, RAID processing, drive rebuilding, cache management, and error recovery. CPU Cache Memory Cache memory resides in a single 64-bit DIMM socket that requires one X8 or X16 unbuffered 3.3V SDRAM single-sided or double-sided DIMM.
Components, Continued SCSI Termination MegaRAID uses active termination on the SCSI bus conforming to Alternative 2 of the SCSI-2 specifications. Termination enable/disable is automatic through cable detection. SCSI Firmware The firmware handles all RAID and SCSI command processing and also supports: Feature Disconnect/ Reconnect Tagged Command Queuing Scatter/Gather Multi-threading Stripe Size Rebuild Description Optimizes SCSI Bus seek.
Components, Continued Fault-Tolerance The MegaRAID fault-tolerance features are: • • • • • • built-in 9-pin berg connector that provides an RS-232C serial communication interface automatic failed drive detection automatic failed drive rebuild with no user intervention required hot swap manual replacement without bringing the system down SAF-TE compliant enclosure management cache memory Detect Failed Drive The MegaRAID firmware automatically detects and rebuilds failed drives.
5 Configuring MegaRAID Configuring SCSI Physical Drives SCSI Channels Physical SCSI drives must be organized into logical drives. The arrays and logical drives that you construct must be able to support the RAID level that you select. Your MegaRAID adapter has four SCSI channels. Distributing Drives Distribute the disk drives across all channels for optimal performance. It is best to stripe across channels instead of down channels. Performance is most affected for sequential reads and writes.
Current Configuration SCSI ID Device Description SCSI Channel A 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15 SCSI Channel B 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15 SCSI Channel C 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 SCSI Channel D 1 2 34 MegaRAID Enterprise 1600 Hardware Guide Termination?
SCSI ID 3 4 5 6 7 8 9 10 11 12 13 14 15 Device Description Termination? Chapter 5 Configuring MegaRAID 35
Logical Drive Configuration Logical Drive RAID Level Stripe Size Logical Drive Size Cache Policy LD0 LD1 LD2 LD3 LD4 LD5 LD6 LD7 LD8 LD9 LD10 LD11 LD12 LD13 LD14 LD15 LD16 LD17 LD18 LD19 LD20 LD21 LD22 LD23 LD24 LD25 LD26 LD27 LD28 LD29 LD30 LD31 LD32 LD33 LD34 LD35 LD36 LD37 LD38 LD39 36 MegaRAID Enterprise 1600 Hardware Guide Read Policy Write Policy # of Physical Drives
Physical Device Layout Channel A Channel B Channel C Channel D Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive
Channel A Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logical Drive Number/ Drive Number Manufacturer/Model Number Firmware level Target ID Device Type Logic
Configuring Arrays Connect the physical drives to MegaRAID, configure the drives, then initialize them. The number of physical disk drives that an array can support depends on the firmware version. For MegaRAID Enterprise 1600, an array can consist of up to 32 physical disk drives, depending on the RAID level (see page 16 for more information.) Enterprise 1600 supports up to 40 logical drives per controller. The number of drives in an array determines the RAID levels that can be supported.
Configuration Strategies The most important factors in RAID array configuration are: drive capacity, drive availability (fault tolerance), and drive performance. You cannot configure a logical drive that optimizes all three factors, but it is easy to choose a logical drive configuration that maximizes one factor at the expense of the other two factors, although needs are seldom that simple. Maximize Capacity RAID 0 achieves maximum drive capacity, but does not provide data redundancy.
Configuration Strategies, Continued Maximize Drive Availability You can maximize the availability of data on the physical disk drive in the logical array by maximizing the level of fault tolerance. The levels of fault tolerance provided by the RAID levels are: RAID Level 0 1 3 5 10 30 50 Fault Tolerance Protection No fault tolerance. Disk mirroring, which provides 100% data redundancy. 100% protection through a dedicated parity drive. 100% protection through striping and parity.
Assigning RAID Levels Only one RAID level can be assigned to each logical drive.
Optimizing Data Storage Data Access Requirements Each type of data stored in the disk subsystem has a different frequency of read and write activity. If you know the data access requirements, you can more successfully determine a strategy for optimizing the disk subsystem capacity, availability, and performance. Servers that support Video on Demand typically read the data often, but write data infrequently. Both the read and write operations tend to be long.
Planning the Array Configuration Answer the following questions about this array: Question Number of MegaRAID SCSI channels Number of physical disk drives in the array Purpose of this array.
Array Configuration Planner Number of Drives 1 1 2 2 2 3 3 3 3 4 4 4 4 4 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 8 8 8 8 8 8 Possible RAID Levels None RAID 0 None RAID 0 RAID 1 None RAID 0 RAID 3 RAID 5 None RAID 0 RAID 3 RAID 5 RAID 10 None RAID 0 RAID 3 RAID 5 None RAID 0 RAID 3 RAID 5 RAID 10 RAID 30 RAID 50 None RAID 0 RAID 3 RAID 5 RAID 0 RAID 3 RAID 5 RAID 10 RAID 30 RAID 50 Relative Performance Excellent Excellent Excellent Excellent Good Excellent Excellent Good Good Excellent Excellent Good Good Excellent
46 MegaRAID Enterprise 1600 Hardware Guide
6 Hardware Installation Requirements You must have the following items before installing the MegaRAID controller in a server: • • • • • • a MegaRAID Enterprise 1600 64-Bit 160M RAID Controller a host computer with an available PCI expansion slot the MegaRAID Enterprise 1600 Installation CD the necessary SCSI cables and terminators (depends on the number and type of SCSI devices to be attached) an Uninterruptible Power Supply (UPS) for the entire system 160M SCSI hard disk drives and other SCSI devices,
Checklist Perform the steps in the installation checklist: Check Step 1 2 3 4 5 6 7 8 9 10 11 12 48 Action Turn all power off to the server and all hard disk drives, enclosures, and system, components. Prepare the host system. See the host system technical documentation. Determine the SCSI ID and SCSI termination requirements. Make sure the jumper settings on the MegaRAID controller are correct. Install the cache memory.
Installation Steps MegaRAID provides extensive customization options. If you need only basic MegaRAID features and your computer does not use other adapter cards with resource settings that may conflict with MegaRAID settings, even custom installation can be quick and easy. Step Action 1 Unpack the MegaRAID controller and inspect for damage. Make sure all items are in the package. 2 Turn the computer off and remove the cover. 3 Make sure the motherboard jumper settings are correct.
Step 1 Unpack Unpack and install the hardware in a static-free environment. The MegaRAID controller card is packed inside an anti-static bag between two sponge sheets. Remove the controller card and inspect it for damage. If the card appears damaged, or if any of items listed below are missing, contact LSI Logic Technical Support at 678-728-1250.
Step 4 Install Cache Memory Important A minimum of 16 MB of cache memory is required. The cache memory must be installed before MegaRAID is operational. Memory Specifications Insert one in the cache memory socket. DIMM Specifications Install cache memory DIMMs on the MegaRAID controller card in the cache memory socket. Use a 64-bit 3.3V single-sided or double-sided 168-pin unbuffered DIMM. Lay the controller card component-side up on a clean static-free surface.
Step 4 Install Cache Memory, Continued Installing or Changing Memory Important The battery pack harness or cable must be disconnected from J23 on the MegaRAID Enterprise 1600 160M card before you add or remove memory. Step 1 2 3 4 5 6 7 8 9 Action Bring down the operating system properly. Make sure that cache memory has been flushed. You must perform a system reset if operating under DOS. When the computer reboots, the MegaRAID controller will flush cache memory. Turn the computer power off.
Step 5 Set Jumpers Make sure the jumper settings on the MegaRAID card are correct.
Step 5 Set Jumpers, Continued J2, J3, J5, and J7 Termination Enable J2, J3, J5, and J7 are 3-pin bergs that set the SCSI termination for each SCSI channel: Jumper SCSI Channel J2 J3 J5 J7 A B C D SCSI Termination Controlled by Software Short Pins 1-2 Short Pins 1-2 Short Pins 1-2 Short Pins 1-2 SCSI Termination Always Disabled Short Pins 2-3 Short Pins 2-3 Short Pins 2-3 Short Pins 2-3 SCSI Termination Always Enabled OPEN OPEN OPEN OPEN J9, J10, J11, and J12 TERMPWR Enable J9, J10, J11, and J12 are 2
Step 5 Set Jumpers, Continued J14 Serial Port J14 attaches to a serial cable. The pinout is: Pin 1 3 5 7 9 Signal Description Carrier Detect Receive Data Transmit Data Data Terminal Ready Ground Pin 2 4 6 8 10 Signal Description Data Set Ready Request to Send Clear to Send Ring Indicator CUT J19 Onboard BIOS Enable J19 is a 2-pin berg which enables or disables MegaRAID onboard BIOS. The onboard BIOS should be enabled (J19 unjumpered) for normal board position.
Step 6 Set Termination Each MegaRAID SCSI channel can be individually configured for termination enable mode by setting the J2, J3, J5, and J7 jumpers (see the previous page). You must terminate the SCSI bus properly. Set termination at both ends of the SCSI cable. The SCSI bus is an electrical transmission line and must be terminated properly to minimize reflections and losses. Termination should be set at each end of the SCSI cable(s), as shown below.
SCSI Termination The SCSI bus on a SCSI channel is an electrical transmission line. It must be terminated properly to minimize reflections and losses. You complete the SCSI bus by setting termination at both ends. MegaRAID automatically provides SCSI termination at one end of the SCSI bus for each channel.
SCSI Termination, Continued Terminating External Disk Arrays In most array enclosures, the end of the SCSI cable has an independent SCSI terminator module that is not part of a SCSI drive. In this way, SCSI termination is not disturbed when a drive is removed. MegaRAID termination should always be enabled or controlled by software. Make sure J2, J3, J5, and J7 are either always open (termination always enabled), or Pins 1-2 are shorted (termination controlled by software).
SCSI Termination, Continued Terminating Internal and External Disk Arrays You can use both internal and external drives with MegaRAID. You still must make sure that the proper SCSI termination and termination power is preserved. MegaRAID termination should always be disabled or controlled by software. Make sure J2, J3, J5 and J7 have pins 2-3 shorted, or pins 1-2 are shorted (termination controlled by software).
SCSI Termination, Continued Connecting Non-Disk SCSI Devices SCSI Tape drives, scanners, CD-ROM drives, and other non-disk drive devices must each have a unique SCSI ID regardless of the SCSI channel they are attached to. The general rule for Unix systems is: • • • tape drive set to SCSI ID 2 CD-ROM drive set to SCSI ID 5 all non-disk SCSI devices attached to SCSI channel A Make sure that no hard disk drives are attached to the same SCSI channel as the non-disk SCSI devices.
Step 7 Set SCSI Terminator Power J9, J10, J11, J12 These jumpers control TermPWR for the MegaRAID SCSI channels. See the documentation for each SCSI device for information about enabling TermPWR. The factory settings supply TermPWR from the PCI bus. Important The SCSI channels need Termination power to operate. If a channel is not being used and no auxiliary power source is connected, change the jumper setting for that channel to supply TermPWR from the PCI bus.
Step 8 Connect Battery Pack (Optional) There are two ways to install a battery pack onto the Series 471 MegaRAID Enterprise 1600 160M RAID controller. The first way is to use a DIMM with a battery backup attached to it. The battery pack is shown in the bottom view of the DIMM socket below. Pin 1 on the cable from the battery pack is usually denoted by a red wire. The caution information appears on the battery module as shown below.
Step 8 Connect Battery Pack, Continued Board with battery The second way is to install a battery pack on the card itself. You can screw the battery to the board through the backside of the board, using the four holes in the board. Connect the three wires from the battery pack to J23, the external battery connector. A drawing of part of the MegaRAID Enterprise 1600 160M RAID Controller with battery backup is shown below.
Step 8 Connect Battery Pack, Continued Configure Battery Backup After installing the MegaRAID controller and booting, press . Choose the Objects menu. Select Battery Backup. The following menu displays: Menu Item Battery Pack Temperature Voltage Fast Charging No. of Cycles Explanation PRESENT will appear if the battery pack is properly installed; ABSENT if it is not. GOOD appears if the temperature is within the normal range. HIGH appears if the module is too hot.
Step 8 Connect Battery Pack, Continued Changing the Battery Pack The MegaRAID configuration software warns when the battery pack must be replaced. A new battery pack should be installed every 1 to 5 years. Step 1 2 3 4 Action Bring down the operating system properly. Make sure that cache memory has been flushed. You must perform a system reset if operating under DOS. When the computer reboots, the MegaRAID Enterprise 1600 160M controller flushes cache memory. Turn the computer power off.
Step 9 Install MegaRAID Card The MegaRAID card can plug into a 32-bit or 64-bit PCI slot that receives 5 V, and, optionally, 3.3 V through the motherboard. Choose a PCI slot and align the MegaRAID controller card bus connector to the slot. Press down gently but firmly to make sure that the card is properly seated in the slot. The bottom edge of the controller card should be flush with the slot. Insert the MegaRAID card in a PCI slot as shown below: Screw the bracket to the computer frame.
Step 10 Connect SCSI Cables SCSI Connectors Connect the SCSI cables to the SCSI devices. MegaRAID provides two types of SCSI connectors: • • external internal External Connectors J13 provides two ultra high-density external connectors for SCSI channels A and B. J22 provides two ultra high-density connectors for SCSI channels C and D. Internal Connectors Internal connectors are provided for channels A and B only. J4 is the internal connector for channel A. J1 is the internal connector for channel B.
Step 10 Connect SCSI Cables, Continued J13 A and B External Connector J13 is a dual 68-pin ultra-high density external SCSI connectors. It is on the MegaRAID mounting bracket. Connect SCSI Devices When connecting SCSI devices: Action 1 2 3 4 5 6 7 Description Disable termination on any SCSI device that does not sit at the end of the SCSI bus. Configure all SCSI devices to supply TermPWR. Set proper target IDs (TIDs) for all SCSI devices.
Step 11 Set Target IDs Set target identifiers (TIDs) on the SCSI devices. Each device in a specific SCSI channel must have a unique TID in that channel. Non-disk devices (CD-ROM or tapes) should have unique SCSI IDs regardless of the channel where they are connected. See the documentation for each SCSI device to set the TIDs. The MegaRAID controller automatically occupies TID 7 in each SCSI channel. Eight-bit SCSI devices can only use the TIDs from 0 to 6. 16-bit devices can use the TIDs from 0 to 15.
Device Identification on MegaRAID Controllers, Continued Example of MegaRAID ID Mapping ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Channel A A1-1 A2-1 CD A2-5 CD A4-1 Optical Reserved A5-2 A5-6 A6-1 A6-4 A6-7 A7-2 A7-5 A7-8 Channel B A1-2 Scanner A2-3 A2-6 A3-1 Tape A5-1 Reserved A5-3 A5-7 A6-2 A6-5 A6-8 A7-3 A7-6 A8-1 As Presented to the Operating System ID 0 0 0 0 0 0 0 0 70 LUN 0 1 2 3 4 5 6 7 Device Disk (A1-X) Disk (A2-X) Disk (A3-X) Disk (A4-X) Disk (A5-X) Disk (A6-X) Disk (A7-X) Disk (A8-X) Mega
Step 12 Power Up Replace the computer cover and reconnect the AC power cords. Turn power on to the host computer. Set up the power supplies so that the SCSI devices are powered up at the same time as or before the host computer. If the computer is powered up before a SCSI device, the device might not be recognized. During boot, the MegaRAID BIOS message appears: MegaRAID Enterprise 1600 Disk Array Adapter BIOS Version x.xx date Copyright (c) LSI Logic Corporation Firmware Initializing...
Step 14 Install the Operating System Driver Important When booting the system from a drive connected to a MegaRAID controller and using EMM386.EXE, MEGASPI.SYS must be loaded in CONFIG.SYS before EMM386.EXE is loaded. If you do not do this, you cannot access the boot drive after EMM386 is loaded. DOS ASPI Driver The MegaRAID DOS ASPI driver can be used under DOS, Windows 3.x, and Windows 95.
Step 14 Install Operating System Driver, Continued CD-ROM Driver A device driver is provided with MegaRAID for CD-ROM drives operating under DOS, Windows 3.x, and Windows 95. The driver filename is AMICDROM.SYS. The MEGASPI.SYS ASPI manager must be added to the CONFIG.SYS file before you can install the CD-ROM device driver. See the instructions on the previous page for adding the MEGASPI.SYS driver. Copy AMICDROM.SYS to the root directory of the C: drive. Add the following line to CONFIG.
74 MegaRAID Enterprise 1600 Hardware Guide
7 Cluster Installation and Configuration Overview This chapter contains the procedures for installing Cluster Service for servers running the Windows 2000 server operating system. Clusters Physically, a cluster is a grouping of two independent servers that can access the same data storage and provide services to a common set of clients. With current technology, this usually means servers connected to common I/O buses and a common network for client access.
Hardware Requirements The hardware requirements for the Cluster Service node can be found at the following web site: http://www.microsoft.com/windows2000/upgrade/compat/default.asp. • The cluster hardware must be on the Cluster Service Hardware Compatibility List (HCL). To see the latest version of the Cluster Service HCL, go to the following web site: http://www.microsoft.com/hcl/default.asp and search using the word “Cluster.
Installation and Configuration Use the following procedures to install and configure your system as part of a cluster. Step 1 2 3 4 5 6 7 8 9 10 Action Unpack the controller following the instructions on page 50. Set the hardware termination for the controller as “always on”. Refer to the J2, J3, J5 and J7 Termination Enable jumper settings on page 54 for more information. Configure the IDs for the drives in the enclosure. See the enclosure configuration guide for information.
Driver Installation Instructions under Microsoft Windows 2000 Advanced Server After the hardware is set up for the MS cluster configuration, perform the following procedure to configure the driver. Step 1 2 3 4 78 Action When the controller is added to an existing Windows 2000 Advanced Server installation, the operating system detects the controller. Click on Cancel on all detected devices and reboot. After you reboot, install the drivers for the new hardware.
Step 5 Action The following screen displays. Insert the floppy diskette with the appropriate driver disk for Windows 2000. Select Floppy disk drives in the screen below and click on Next. 6 The Wizard detects the device driver on the diskette and the "Completing the upgrade device driver" wizard displays the name of the controller. Click on Finish to complete the installation. Repeat steps 1 – 5 to install the device driver on the second system.
80 Step 9 Action On the screen below, choose to display a list of the known drivers, so that you can choose a specific driver. Click on Next. 10 The following screen displays. Select Other devices from the list of hardware types. Click on Next.
Step 11 12 Action The following screen displays. Select the driver that you want to install for the device. If you have a disk with the driver you want to install, click on Have Disk. The following window displays. Insert the disk containing the driver into the selected drive and click on OK.
Step 13 14 82 Action The following screen displays. Select the processor device and click on Next. On the final screen, click on Finish to complete the installation. Repeat the process on the peer system.
Network Requirements The network requirements for clustering are: • • • • A unique NetBIOS cluster name Five unique, static IP addresses: • two are for the network adapters on the internal network • two are for the network adapters on the external network • one is for the cluster itself A domain user account for Cluster Service (all nodes must be part of the same domain.
Cluster Installation Installation Overview During installation, some nodes are shut down, and other nodes are rebooted. This is necessary to ensure uncorrupted data on disks attached to the shared storage bus. Data corruption can occur when multiple nodes try to write simultaneously to the same disk, if that disk is not yet protected by the cluster software. The table below shows which nodes and storage devices should be powered on during each step.
Installing the Windows 2000 Operating System Install Microsoft Windows 2000 to each node. See your Windows 2000 manual on how to install the Operating System. Log on as administrator before you install the Cluster Services. Setting Up Networks Note: Do not allow both nodes to access the shared storage device before the Cluster Service is installed. In order to prevent this, power down any shared storage devices and then power up nodes one at a time.
Setting Up Networks, Continued Verify that all network connections are correct, with private network adapters connected to other private network adapters only, and public network adapters connected to the public network. View the Network and Dial-up Connections screen to check the connections. Note: Use crossover cables for the network card adapters that access the cluster nodes.
Configuring the Cluster Node Network Adapter Note: Which network adapter is private and which is public depends upon your wiring. For the purposes of this chapter, the first network adapter (Local Area Connection) is connected to the public network, and the second network adapter (Local Area Connection 2) is connected to the private cluster network. This may not be the case in your network.
17 Click OK to return to the previous menu. Perform this step for the private network adapter only. Configuring the Public Network Adapter Note: It is strongly recommended that you use static IP addresses for all network adapters in the cluster. This includes both the network adapter used to access the cluster nodes and the network adapter used to access the LAN (Local Area Network).
and Ping 10.1.1.1 from Node 1. They you would type Ping 192.168.0.172 and 10.1.1.1 from Node 2. To confirm name resolution, ping each node from a client using the node’s machine name instead of its IP number. Verifying Domain Membership All nodes in the cluster have to be members of the same domain and capable of accessing a domain controller and a DNS Server. You can configure them as either member servers or domain controllers.
Setting Up a Cluster User Account The Cluster Service requires a domain user account that the Cluster Service can run under. You must create the user account before installing the Cluster Service. The reason for this is that setup requires a user name and password. This user account should not belong to a user on the domain. Step 1 2 3 4 5 6 7 8 9 10 Description Click on Start. Point to Programs, then point to Administrative Tools. Click on Active Directory Users and Computers.
Setting Up Shared Disks Warning: Make sure that Windows 2000 Advanced Server or Windows 2000 Datacenter Server and the Cluster Service are installed and running on one node before you start an operating system on another node. If the operating system is started on other nodes before you install and configure Cluster Service and run it on at least one node, the cluster disks will have a high chance of becoming corrupted. To continue, power off all nodes. Power up the shared storage devices.
Configuring Shared Disks Perform the following procedure to configure the shared disks. Step 1 2 3 4 Description Right-click on My Computer. Click on Manage, then click on Storage. Double-click on Disk Management. Make sure that all shared disks are formatted as NTFS and are designated as Basic. If you connect a new drive, the Write Signature and Upgrade Disk Wizard starts automatically. If this occurs, click on Next to go through the wizard.
Verifying Disk Access and Functionality Perform the steps below to verify disk access and functionality. Step 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Description Click on Start. Click on Programs. Click on Accessories, then click on Notepad. Type some words into Notepad and use the File/Save As command to save it as a test file called test.txt. Close Notepad. Double-click on the My Documents icon. Right-click on test.txt and click on Copy. Close the window. Double-click on My Computer.
Cluster Service Software Installation Before you begin the Cluster Service Software installation on the first node, make sure that all other nodes are either powered down or stopped and that all shared storage devices are powered on. Cluster Configuration Wizard To create the cluster, you must provide the cluster information. The Cluster Configuration Wizard will allow you to input this information. Step 1 2 3 4 5 6 7 94 Description Click on Start. Click on Settings, then click on Control Panel.
8 9 Click on Next. The Hardware Configuration Certification window appears. Click on I Understand to accept the condition that Cluster Service is supported only on hardware listed on the Hardware Compatibility List. 10 This is the first node in the cluster; therefore, you must create the cluster itself. Select The first node in the cluster, as shown below and then click on Next.
11 12 Enter a name for the cluster (up to 15 characters), and click on Next. (In our example, the cluster is named ClusterOne.) Type the user name of the Cluster Service account that you created during the preinstallation. (In our example, the user name is cluster.) Do not enter a password. Type the domain name, then click on Next. At this point the Cluster Service Configuration Wizard validates the user account and password. 13 Click on Next. The Add or Remove Managed Disks screen displays next.
Configuring Cluster Disks Windows 2000 Managed Disks displays all SCSI disks, as shown on the screen below. It displays SCSI disks that do not reside on the same bus as the system disk. Because of this, a node that has multiple SCSI buses will list SCSI disks that are not to be used as shared storage. You must remove any SCSI disks that are internal to the node and not to be shared storage.
Configuring Cluster Disks, Continued Use the following procedure to configure the clustered disks. 98 Step 1 Description The Add or Remove Managed Disks dialog box specifies disks on the shared SCSI bus that will be used by Cluster Service. Add or remove disks as necessary, then click on Next. 2 The following screen displays. Click on Next in the Configure Cluster Networks dialog box.
4 5 6 public network. Check the box Enable this network for cluster use. Select the option All communications (mixed network), as shown below, and click on Next. The next dialog box configures the private network. Make sure that the network name and IP address correspond to the network interface used for the private network. Check the box Enable this network for cluster use. Select the option Internal cluster communications only, then click on Next.
7 In this example, both networks are configured so that both can be used for internal cluster communication. The next dialog window offers an option to modify the order in which the networks are used. Because Private Cluster Connection represents a direct connection between nodes, it remains at the top of the list. In normal operation, this connection is used for cluster communication.
9 Click Finish to complete the cluster configuration on the first node. The Cluster Service Setup Wizard completes the setup process for the first node by copying the files needed to complete the installation of Cluster Service.
102 10 After the files are copied, the Cluster Service registry entries are created, the log files on the quorum resource are created, and the Cluster Service is started on the first node. A dialog box appears telling you that Cluster Service has started successfully. Click on OK. 11 Close the Add/Remove Programs window.
Validating the Cluster Installation Use the Cluster Administrator snap-in to validate the Cluster Service installation on the first node. Step 1 2 3 4 5 Description Click on Start. Click on Programs. Click on Administrative Tools. Click on Cluster Administrator. The following screen displays. If your snap-in window is similar to that shown above below, your Cluster Service was successfully installed on the first node. You are now ready to install Cluster Service on the second node.
Verify Installation There are several ways to verify that Cluster Service was successfully installed. Here is a simple one: 1. Click Start, click Programs, click Administrative Tools, then click Cluster Administrator. The presence of two nodes (pictured below) shows that a cluster exists and is in operation. 2. Right-click the group Disk Group 1 and select the option Move. This option moves the group and all its resources to another node.
SCSI Drive Installations This information is provided as a generic instruction set for SCSI drive installations. If the SCSI hard disk vendor’s instructions conflict with the instructions in this section, always use the instructions supplied by the vendor. The SCSI bus listed in the hardware requirements must be configured prior to installation of Cluster Services. This includes: • • • Configuring the SCSI devices. Configuring the SCSI controllers and hard disks to work properly on a shared SCSI bus.
106 MegaRAID Enterprise 1600 Hardware Guide
8 Troubleshooting Problem Some operating systems do not load in a computer with a MegaRAID adapter. One of the hard drive in the array fails often Suggested Solution Check the system BIOS configuration for PCI interrupt assignments. Make sure some Interrupts are assigned for PCI. Initialize the logical drive before installing the operating system. Check the drive error counts using Power Console. Format the drive. Rebuild the drive Pressed . Ran Megaconf.
Problem What is the maximum number of MegaRAID adapters per computer? What SCSI IDs can a nonhard disk device have and what is maximum number allowed per adapter? Why does a failed logical array still get a drive assignment? 108 MegaRAID Enterprise 1600 Hardware Guide Suggested Solution Currently, all the utilities and drivers support up to 12 MegaRAID adapters per system. Non-hard disk devices can accommodate only SCSI IDs 1, 2, 3, 4, 5 or 6, regardless of the channel used.
BIOS Boot Error Messages Message Adapter BIOS Disabled. No Logical Drives Handled by BIOS Host Adapter at Baseport xxxx Not Responding Problem The MegaRAID BIOS is disabled. Sometimes the BIOS is disabled to prevent booting from the BIOS. The BIOS cannot communicate with the adapter firmware. Suggested Solution Enable the BIOS via the MegaRAID Configuration Utility utility. Make sure MegaRAID is properly installed. Try moving the MegaRAID card to another PCI slot.
Message Configuration of NVRAM and drives mismatch for Host Adapter. Run View/Add Configuration option of Configuration Utility. Press any key to run the Configuration Utility. Problem The configuration stored in the MegaRAID adapter does not match the configuration stored in the drives. 1 Logical Drive Failed A logical drive failed to sign on. X Logical Drives Degraded 1 Logical Drive Degraded Insufficient memory to run BIOS.
Message The following SCSI IDs are not responding: Channel x:a.b.c Problem The physical drives with SCSI IDs a, b, and c are not responding on SCSI channel x. Suggested Solution Make sure the physical drives are properly connected and are powered on.
DOS ASPI Driver Error Messages Message LSI Logic ASPI Manager has NOT been loaded. Controller setup FAILED error code=[0xab] Corrective Action The ASPI manager is not loaded. One of the failure codes listed below is displayed next. Correct the condition that caused the failure.
Other Potential Problems Topic DOS ASPI CD-ROM drives under DOS Physical Drive Errors Virtual Sizing BSD Unix Multiple LUNs MegaRAID Power Requirements SCSI Bus Requirements Information MEGASPI.SYS, the MegaRAID DOS ASPI manager, uses 6 KB of system memory once it is loaded. At this time, copied CDs are not accessible from DOS even after loading MEGASPI.SYS and AMICDROM.SYS.
Topic Windows NT Installation Information When Windows NT is installed via a bootable CD, the devices on the MegaRAID will not be recognized until after the initial reboot. The Microsoft documented workaround is in SETUP.TXT: SETUP.TXT is on the CD. To install drivers when Setup recognizes one of the supported SCSI host adapters without making the devices attached to it available for use: 1 2 Restart Windows NT Setup.
A SCSI Cables and Connectors SCSI Connectors MegaRAID provides several different types of SCSI connectors for each channel. The connectors are: • • 68-pin high density internal connectors 68-pin ultra high density external connectors 68-Pin High Density SCSI Internal Connectors Each of the SCSI channels on the MegaRAID has a 68-pin high density 0.050 inch pitch unshielded connector. These connectors provide all signals needed to connect MegaRAID to wide SCSI devices.
68-Pin High Density Connectors, Continued Cable Assembly for Internal Wide SCSI Devices The cable assembly for connecting internal wide SCSI devices is shown below: pin 1 pin 1 pin 1 Connectors: 68 position plug (male) AMP - 786090-7 Cable: Flat Ribbon or Twisted-Pair Flat Cable 68 Conductor 0.
68-Pin High Density Connectors, Continued Connecting Internal and External Wide Devices The cable assembly for connecting internal wide and external wide SCSI devices is shown below: A pin 1 pin 1 B pin 1 B Connector A: 68 position panel mount receptacle with 4-40 holes (female) AMP - 786096-7 NOTE: To convert to 2-56 holes, use screwlock kit 749087-1, 749087-2, or 750644-1 from AMP Connector B: 68 position plug (male) AMP - 786090-7 Cable: Flat Ribbon or Twisted-Pair Flat Cable 68 Conductor 0.
68-Pin High Density Connectors, Continued Converting Internal Wide to Internal Non-Wide (Type 2) The cable assembly for converting internal wide SCSI connectors to internal non-wide SCSI connectors is shown below: 68 POSITION CONNECTOR CONTACT NUMBER 50 POSITION CONNECTOR CONTACT NUMBER 6 40 7 41 1 2 3 4 pin 1 * * * 49 16 50 17 51 18 52 19 OPEN OPEN OPEN A 20 21 22 23 24 25 26 27 * * * 29 63 30 64 TABLE 1: 47 48 49 50 pin 1 pin 1 B B Connector A:68 position plug (male) AMP - 749925-5 Connector
68-Pin High Density Connectors, Continued Converting Internal Wide to Internal Non-Wide (Type 30) The cable assembly for connecting internal wide SCSI devices to internal non-wide SCSI devices is shown below: pin 1 A pin 1 B Connector A: 68 position plug (male) AMP - 749925-5 Connector B:50 position plug (male) AMP - 749925-3 Wire: Twisted-Pair Flat Cable or Laminated Discrete Wire Cable 25 pair 0.
68-Pin High Density Connectors, Continued Converting from Internal Wide to Internal Non-Wide (Type 3) The cable assembly for connecting internal wide SCSI devices to internal non-wide (Type 3) SCSI devices is shown below: pin 1 A pin 1 B Connector A: 68 position plug (male) AMP - 786090-7 Connector B:50 position plug (male) AMP - 786090-7 Wire: Flat ribbon or twisted-pair flat cable 50 conductor 0.
68-Pin Connector Pinout for Single-Ended SCSI Signal Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground TERMPWR TERMPWR Reserved Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Ground Connector Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Cable Pin 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 53 55 57 59 61 63 65 67
68-Pin SCSI Connector Pinout, Continued High-Density Connector The following applies to the high-density SCSI connector table on the previous page: • • • • A hyphen before a signal name indicates that signal is active low The connector pin refers to the conductor position when using 0.025 inch centerline flat ribbon cable with a high-density connector (AMPLIMITE.
68-Pin Connector Pinout for Low-Voltage Differential SCSI Signal +DB(12) +DB(13) +DB(14) +DB(15) +DB(P1) +DB(0) +DB(1) +DB(2) +DB(3) +DB(4) +DB(5) +DB(6) +DB(7) +DB(P) Ground DIFFSENS TERMPWR TERMPWR Reserved Ground +ATN Ground +BSY +ACK +RST +MSG +SEL +C/D +REQ +I/O +DB(8) +DB(9) +DB(10) +DB(11) Notes Connector Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Cable Pin 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 53 55 57 59 61
124 MegaRAID Enterprise 1600 Hardware Guide
B Audible Warnings MegaRAID has an onboard tone generator that indicates events and errors. Tone Pattern Three seconds on and one second off One second on and one second off One second on and three seconds off Meaning A logical drive is offline. A logical drive is running in degraded mode. An automatically initiated rebuild has been completed. Examples One or more drives in a RAID 0 configuration failed. Two or more drives in a RAID 1, 3, or 5 configuration failed.
126 MegaRAID Enterprise 1600 Hardware Guide
C Cluster Configuration with a Crossover Cable When you are installing the Cluster Service on the first node in a server cluster, Setup may not detect the network adapter that is connected with a crossover cable. The icon in Network and Dial-up Connections that represents the network adapter connected to the crossover cable is displayed with a red X, and the Network cable unplugged icon in displayed on the taskbar.
Solution Note: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Use Registry Editor at your own risk. You should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD). Disable the Media Sense feature: 1. Start Registry Editor (Regedt32.exe). 2.
Glossary Array A grouping or array of disk drives combines the storage space on the disk drives into a single segment of contiguous storage space. MegaRAID can group disk drives on one or more SCSI channels into an array. A hot spare drive does not participate in an array. Array Management Software Software that provides common control and management for a disk array.
Glossary, Continued Disk Array A collection of disks from one or more disk subsystems combined with array management software. It controls the disks and presents them to the array operating environment as one or more virtual disks. Disk Duplexing A variation on disk mirroring where a second disk adapter or host adapter and redundant disk drives are present. Disk Mirroring Writing duplicate data to more than one (usually two) hard disks to protect against data loss in the event of device failure.
Glossary, Continued Format The process of writing zeros to all data fields in a physical drive (hard drive) to map out unreadable or bad sectors. Because most hard drives are factory formatted, formatting is usually only done if a hard disk generates many media errors. GB Shorthand for 1,000,000,000 (10 to the ninth power) bytes. It is the same as 1,000 MB (megabytes). Host-based Array A disk array with an Array Management Software in its host computer rather than in a disk subsystem.
Glossary, Continued Mapping The conversion between multiple data addressing schemes, especially conversions between member disk block addresses and block addresses of the virtual disks presented to the operating environment by Array Management Software. MB (Megabyte) An abbreviation for 1,000,000 (10 to the sixth power) bytes. It is the same as 1,000 KB (kilobytes). Multi-threaded Having multiple concurrent or pseudo-concurrent execution sequences. Used to describe processes in computer systems.
Glossary, Continued RAID Redundant Array of Independent Disks (originally Redundant Array of Inexpensive Disks) is an array of multiple small, independent hard disk drives that yields performance exceeding that of a Single Large Expensive Disk (SLED). A RAID disk subsystem improves I/O performance on a server using only a single drive. The RAID array appears to the host server as a single storage unit. I/O is expedited because several disks can be accessed simultaneously.
Glossary, Continued SAF-TE SCSI Accessed Fault-Tolerant Enclosure. An industry protocol for managing RAID enclosures and reporting enclosure environmental information. SCSI (Small Computer System Interface) A processor-independent standard for system-level interfacing between a computer and intelligent devices, including hard disks, floppy disks, CD-ROM, printers, scanners, etc. SCSI can connect up to 7 devices to a single adapter (or host adapter) on the computer's bus.
Glossary, Continued Stripe Width The number of disk drives across which the data are striped. Striping Segmentation of logically sequential data, such as a single file, so that segments can be written to multiple physical devices in a round-robin fashion. This technique is useful if the processor can read or write data faster than a single disk can supply or accept it. While data is being transferred from the first disk, the second disk can locate the next segment.
136 MegaRAID Enterprise 1600 Hardware Guide
Index 0 0 DIMM socket, 51 1 160M and WIDE SCSI, 25 6 68-Pin High Density Connectors, 115 A AMICDROM.SYS, 73 AMPLIMITE .
SCSI Channels, 33 Connecting Internal and External Wide Devices, 117 Consistency Check, 6, 129 Converting from Internal Wide to Internal Non-Wide (Type 3), 120 Converting Internal Wide to Internal Non-Wide, 118 Converting Internal Wide to Internal Non-Wide (Type 30), 119 CPU, 30 Crossover Cable, 127 Current Configuration, 34 D Data redundancy Using mirroring, 8 Data Transfer Capacity, 129 Dedicated Parity, 10 Degraded, 129 Devices per SCSI Channel, 29 DIMM socket, 51 DIMMs, 51 Dirty Cache LED Connector, 55
J7 A and B External Connector, 68 J7 Channel D Termination Enable, 53 J9 Channel B TERMPWR Enable, 53 J9, J10, J11, and J12 TermPWR Enable, 54 J9, J10, J11, J12, 61 Jumpers, 53, 54 on motherboard, 50 L Logical Disk, 131 Logical Drive, 13, 131 Logical Drive Configuration, ix, 36 Logical Drive States, 13 Degraded, 13 Failed, 13 Offline, 13 Optimal, 13 M Mapping, 132 Maximum Cable Length, 2 MB, 132 MegaRAID BIOS, 30 MegaRAID BIOS Setup, 31 MegaRAID Card Installing, 66 MegaRAID Enterprise 1600 64-bit 160M Car
Rebuild, 13, 31 Rebuild Rate, 12, 133 Rebuilding a disk, 12 Reconnect, 31 Reconstruct, 133 Reconstruction, 133 RedAlert, 32 Redundancy, 133 Replacement Disk, 133 Replacement Unit, 133 S SAF-TE, 134 Scatter/Gather, 31 SCO Unix, 31 SCSI, 134 SCSI backup and utility software, 32 SCSI Bus, 29, 30 SCSI Bus Widths and Maximum Throughput, 2 SCSI Cable Vendors, 120 SCSI cables, 29 SCSI Cables Attaching, 67 SCSI Channel, 134 SCSI Connectors, 29, 30, 115 SCSI Controller, 29 SCSI Data Transfer Rate, 29 SCSI Device Co
