HP D5970A - NetServer - LCII Installation And Configuration Manual

Hp netserver ultra3 scsi hba guide
Hide thumbs Also See for D5970A - NetServer - LCII:
Table of Contents

Advertisement

HP Netserver
Ultra3 SCSI Host Bus Adapter
Installation and Configuration
Guide
HP Part Number 5971-0821
Printed in November 2000

Advertisement

Table of Contents
loading

Summary of Contents for HP D5970A - NetServer - LCII

  • Page 1 HP Netserver Ultra3 SCSI Host Bus Adapter Installation and Configuration Guide HP Part Number 5971-0821 Printed in November 2000...
  • Page 2: Audience Assumptions

    Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
  • Page 3: Table Of Contents

    Contents 1 Installation and Setup ............... 1 Bus Segments on the HP Ultra3 SCSI Host Adapter ........... 2 Installing the HP Ultra3 SCSI Host Bus Adapter ..........3 Setting Up SCSI Devices.................. 5 Choosing SCSI Cables ..................5 Connecting SCSI Devices ................7 HP Ultra3 SCSI Host Adapter Driver Software ...........
  • Page 4 Removing a Host Adapter in Windows NT 4.0 ..........31 Troubleshooting ....................31 Problems and Solutions .................. 31 Error Messages ....................32 adpu160m.sys Error Messages ..............33 4 Microsoft Windows 2000 Installation ........37 Installing the Driver When Installing Windows 2000 ........... 37 Installing the Driver When Windows 2000 is Already Installed ......
  • Page 5 6 SCO OpenServer Installation ..........67 Installing the Driver When Installing SCO OpenServer ........67 Installing SCO OpenServer 5.0.x ..............67 Installing the Driver When SCO OpenServer is Already Installed ...... 68 Using SCO OpenServer and the Host Adapter ..........73 Using Multiple Host Adapters .................
  • Page 6 Notice for Korea .................... 106 Notice for Taiwan ..................107 D Warranty and Support ............109 Hardware Accessories Limited Warranty ............109 Hewlett-Packard Hardware Accessories ............109 Third-Party Hardware Products ..............110 HP Repair and Telephone Support ..............110 U.S. and Canada ..................110 Other Countries ....................
  • Page 7: Installation And Setup

    Installation and Setup The HP Ultra3 Single Channel SCSI Host Bus Adapter enables you to connect up to 15 SCSI devices—such as hard disk drives, scanners, and CD-ROM drives—to HP Netservers with 32-bit or 64-bit PCI expansion slots. You can connect newer Ultra3 and Ultra2 SCSI devices to the two 68-pin Low Voltage Differential/Single-Ended (LVD/SE) connectors.
  • Page 8: Bus Segments On The Hp Ultra3 Scsi Host Adapter

    Bus Segments on the HP Ultra3 SCSI Host Adapter The HP Ultra3 SCSI host bus adapter features technology that ensures you get the best performance from your Ultra3 and Ultra2 SCSI devices by electronically isolating the primary LVD/SE segment from the secondary SE segment on the SCSI bus.
  • Page 9: Installing The Hp Ultra3 Scsi Host Bus Adapter

    Installing the HP Ultra3 SCSI Host Bus Adapter 1. Discharge any static electricity build-up before handling the SCSI host bus adapter by touching a grounded metal object (like the exposed metal parts on the back of your HP Netserver). WARNING Turn OFF power to the HP Netserver and disconnect the power cord.
  • Page 10 Figure 1-4. Host Bus Adapter Installed in 64-bit Slot HP Netservers may have vertical or horizontal expansion slots. Refer to your HP Netserver manual to locate the PCI slots. NOTE Be careful when inserting the HP Ultra3 SCSI host bus adapter in a PCI slot.
  • Page 11: Setting Up Scsi Devices

    Ultra3 twisted pair cable. The HP Ultra3 cable upgrade kit part number is P3469A. These cables can be purchased from an authorized Hewlett-Packard reseller, or on HP Order Assistant (available on the Internet at http://netserver.hp.com/netserver/) See Table 1-1 that follows to determine the correct cable for your HP Netserver...
  • Page 12 Table 1-1. Netserver SCSI Cables HP Netserver SCSI Devices Interface Cable Product Number All Models HP Netserver Rack External D3636C - HDTS68 to Storage/12 (RS/12) HDTS68, 2.5m All Models HP SureStore H/A External D3637C - HDTS68 to TapeArray 5500 VHDC1, 2.5m All Models HP SureStore External...
  • Page 13: Connecting Scsi Devices

    Connecting SCSI Devices You can connect up to 15 SCSI devices to the HP Ultra3 SCSI host bus adapter. Before connecting devices, be sure to review Setting Up SCSI Devices on page 5. Connecting the SCSI Host Adapter to the Common Tray Connect internal Ultra3 and Ultra2 SCSI devices to the internal LVD/SE connector on the HP Ultra3 SCSI host bus adapter.
  • Page 14 3. Plug the internal Ultra2 or Ultra3 SCSI devices to the other cable connectors, starting with the connector at the terminated end of the cable. Terminated LVD SCSI Twisted-Pair Cable Terminator Figure 1-6. Common Tray Cable Connection NOTE Internal Ultra2 and Ultra3 SCSI devices come from the factory with termination disabled and cannot be changed.
  • Page 15 Point-to-Point LVD Twisted-Pair SCSI Cable Figure 1-7. Hot-Plug Cage Cable Connections Connecting Ultra/Fast Wide SCSI Devices Connect internal Ultra/Fast Wide SCSI devices to the 68-pin internal SE Wide SCSI connector. To do this, use a flat 68-pin Wide SCSI cable. Follow these steps to connect the devices: 1.
  • Page 16 68-pin flat SCSI cable Figure 1-8. Connecting Ultra/Fast Wide SCSI Devices 2. Plug the other end of the cable to a terminated Ultra/Fast Wide SCSI device. 3. If you have other Ultra/Fast Wide SCSI devices, attach them to the connectors between the two ends of the cable. Be sure these other devices are unterminated.
  • Page 17 50-pin SE Narrow SCSI cable Figure 1-9. Connecting Ultra/Fast Narrow Devices 2. Plug the other end of the cable to a terminated Ultra/Fast Narrow SCSI device. 3. If you have other Ultra/Fast Narrow SCSI devices, attach them to the connectors between the two ends of the cable. Be sure these other devices are unterminated.
  • Page 18 NOTE We recommend that you connect only Ultra3 and Ultra2 SCSI devices to the external SCSI connector. If you also attach older Ultra SCSI devices, the data transfer speed of the Ultra3 and Ultra2 SCSI devices will drop to the speed of the older devices. (See Bus Segments on the HP Ultra3 SCSI Host Adapter on page 2.) Follow these steps to connect the external devices: 1.
  • Page 19: Hp Ultra3 Scsi Host Adapter Driver Software

    Figure 1-11. Terminating the Last External SCSI Device 4. Terminate only the device at the end of the chain. (Use of an external multi-mode SCSI terminator is required.) 5. Connect power cables to all external devices and to the HP Netserver. HP Ultra3 SCSI Host Adapter Driver Software NOTE To use the HP Ultra3 SCSI host bus adapter, driver software must be...
  • Page 20: Troubleshooting

    Troubleshooting If you have any problems while installing the HP Ultra3 SCSI host bus adapter, check the following items first: • Are all SCSI devices powered on? • Are all SCSI cables and power cables properly connected? • Does each device on the SCSI bus have a unique SCSI ID? •...
  • Page 21: Configuration With Scsiselect

    Configuration with SCSISelect SCSISelect, included with the HP Ultra3 SCSI Host Bus Adapter, enables you to change SCSI settings without opening the computer or handling the host bus adapter. SCSISelect also enables you to low-level format or verify the disk media of your SCSI hard disk drives.
  • Page 22: Starting Scsiselect

    SCSISelect Options Available Default Settings Setting Initiate Wide Negotiation Yes, No Yes (Enabled) Enable Disconnection Yes, No Yes (Enabled) Send Start Unit Command Yes, No Yes (Enabled) N/C (No Change) N/C (No Enable Write Back Cache Yes, No Change) Yes, No No (Disabled) BIOS Multiple LUN Support Yes, No...
  • Page 23: Exiting Scsiselect

    During the startup process, pay careful attention to the messages that appear on your screen. 2. When the following message appears on your screen, press the Ctrl-A keys simultaneously (this message appears for only a few seconds): Press <Ctrl><A> for SCSISelect (TM) Utility! 3.
  • Page 24: Boot Device Options

    gives it the highest priority on the SCSI bus. We recommend that you do not change this setting. • SCSI Parity Checking—(Default: Enabled) When set to Enabled, verifies the accuracy of data transfer on the SCSI bus. Leave this setting enabled unless any SCSI device connected to the Ultra3 SCSI Host Bus Adapter does not support SCSI parity.
  • Page 25: Advanced Configuration Options

    set to No, the SCSI host bus adapter uses 8-bit data transfer unless the SCSI device requests wide negotiation. NOTE Set Initiate Wide Negotiation to No if you are using an 8-bit SCSI device that hangs or exhibits other performance problems with 16-bit data transfer rate enabled.
  • Page 26 • Reset SCSI Bus at IC Initialization—(Default: Enabled) When set to Enabled, the SCSI host bus adapter generates a SCSI bus reset during its power-on initialization and after a hard reset. • Display <Ctrl> <A> Messages during BIOS Initialization—(Default: Enabled) When set to Enabled, the SCSI host bus adapter BIOS displays the Press <Ctrl>...
  • Page 27 The following four options have no effect when the SCSI host bus adapter BIOS is disabled. (The SCSI host bus adapter BIOS is normally enabled by default.) • Domain Validation—(Default: Enabled) Determines the kinds of SCSI devices connected and reduces data transfer speed when legacy SCSI devices are detected.
  • Page 28: Using Scsi Disk Utilities

    Using SCSI Disk Utilities To access the SCSI disk utilities, follow these steps: 1. Select the SCSI Disk Utilities option from the menu that appears after starting SCSISelect. SCSISelect scans the SCSI bus (to determine the devices installed) and displays a list of all SCSI IDs and the devices assigned to each ID.
  • Page 29: Microsoft Windows Nt Installation

    Microsoft Windows NT Installation This chapter explains how to install the HP Ultra3 Family Manager Set driver adpu160m.sys for Windows NT. If you are performing a first time Windows NT installation, see “Installing the Driver When Installing Windows NT” in the next section. If Windows NT is already installed in your system, see “Installing the Driver When Windows NT is Already Installed”...
  • Page 30: Completing A Fresh Windows Nt 4.0 Installation From Cd-Rom

    8. Press Enter to continue with the Windows NT operating system setup. Fol- low the instructions on-screen and in the Windows NT documentation to complete the installation. Completing a Fresh Windows NT 4.0 Installation From CD-ROM 1. Insert the Windows NT 4.0 CD into the CD-ROM drive. 2.
  • Page 31: Updating Windows Nt 4.0

    Updating Windows NT 4.0 1. Start Windows NT. 2. Click the Start button on the Windows NT task bar, and then point to Set- tings. 3. Click the Control Panel. 4. Double-click the SCSI Adapters icon. 5. Click the Drivers tab, and then click the Add button. 6.
  • Page 32: Using Windows Nt Scsi Parameters

    Using Windows NT SCSI Parameters Follow the instructions below to enter the registry values that affect how the Windows NT SCSI manager interprets the generic configuration information of SCSI device drivers. All SCSI host adapters installed in your system are affected by the values you enter here.
  • Page 33: Using Driver-Specific Parameters

    If the Parameters Device keys already exist, skip to Step 8 below to begin entering values. If the keys do not yet exist, you will need to create them by continuing with Step 4. 4. Click on the adpu160m key. 5.
  • Page 34 • /INSTRUMENTATION—enables recording of I/O statistics and errors. If this option is not specified, instrumentation defaults to disabled. The data type for this value is REG_SZ. • /INSTR_ERRLOG_Z=nnn—sets the maximum number of error log entries, if /INSTRUMENTATION is enabled. If a number is not specified, the maximum number or error log entries defaults to 32.
  • Page 35: Hot-Plug Pci Feature

    8. Click on the Device key. 9. Select Add Value from the Edit menu; type Driver Parameters in the Key Name edit box. Enter REG_SZ as the data type and press Enter. 10. A String Editor text box appears. Enter valid parameters in the text box. When entering multiple parameters, each parameter must be separated by a space.
  • Page 36: Using Windows Nt And The Host Adapter

    NOTE The file hotp160m.reg adds Hot-Plug related entries into the NT Registry, including the driver-specific registry value /HOTPLUG. Running hotp160m.reg will overwrite your current driver-specific registry values located at: \HKEY_LOCAL_MACHINE\System\CurrentControlSet\ Services\adpu160m\Parameters\Device\DriverParameters If you have previously added other driver specific registry values, you should note them before running the hotp160m.reg file.
  • Page 37: Removing A Host Adapter In Windows Nt 4.0

    Removing a Host Adapter in Windows NT 4.0 1. From the Control Panel, double-click the SCSI Adapters icon. 2. Click the Drivers tab. 3. Using the arrow keys select the following driver: Adaptec 29160(N), 29160, 39160, AHA-3960D, AIC-7892/7899 Ultra160 PCI SCSI Controller (NT 4.0) 4.
  • Page 38: Error Messages

    Press spacebar NOW to invoke the Last Known Good menu 3. Once your computer is operational again, check all of the hardware and soft- ware configuration changes you want to make. Look specifically for con- flicts with parts of the existing system configuration that are not being changed.
  • Page 39: Adpu160M.sys Error Messages

    adpu160m.sys Error Messages The following error messages are listed sequentially according to the last three digits of the error message. For example, [xxxxx010], [xxxxx011], [xxxxx012], etc. NOTE When reporting problems to HP Customer Support, be sure to include the complete error message in your problem description. [xxxxx004] Command completed with error [xxxxx005] Command completed with error [xxxxx006] Command completed with error...
  • Page 40 it could indicate that the device or system is malfunctioning. Unplug or power down unused devices to see if the problem persists. [xxxxx023] Target device parity error The driver has detected a parity error by the target device. [xxxxx024] Data overrun or underrun The adapter was given more or less data than the expected amount of data.
  • Page 41 [xxxxx096] Adapter hardware initialization failure—possible resource conflict The driver has attempted to initialize the adapter hardware but failed. This might suggest that the adapter resources (e.g., IRQ) conflict with another board installed in your system. [xxxxx097] Unable to allocate memory This indicates that there may be a problem with the amount of memory installed in your system.
  • Page 43: Microsoft Windows 2000 Installation

    Microsoft Windows 2000 Installation This chapter explains how to install the HP Ultra3 Family Manager Set driver for Windows 2000. If you are performing a first-time Windows 2000 installation, see Installing the Driver When Installing Windows 2000. If Windows 2000 is already installed in your system, see To Update the Driver When Windows 2000 is Already Installed on page 37.) Installing the Driver When Installing...
  • Page 44: Upgrading An Existing Windows Nt Version 4 Installation To Windows 2000

    1. Start Windows 2000. 2. Click the Start button on the Windows 2000 task bar, and then point to Settings. 3. Click the Control Panel. 4. Double-click the System icon. 5. Select the Hardware tab and click the Device Manager button. 6.
  • Page 45: Using Advanced Configuration Parameters

    3. Follow the directions from “Installing the Driver When Installing Windows 2000” on page 37. Using Advanced Configuration Parameters Advanced users may use software parameters to alter the configuration of the Windows 2000 device drivers supplied by HP. All Windows 2000 configuration information is stored in a data structure supplied by Windows 2000, called the Registry.
  • Page 46 • DisableMultipleRequests— This limits the number of commands to each logical device to one. The data type for this value is REG_DWORD. • MaximumLogicalUnit — This can limit the scan for connected devices on the SCSI bus. Valid values are 0 to 7. If 1 is specified, the Windows 2000 SCSI manager assumes that no SCSI targets support LUNs other than 0.
  • Page 47: Using Driver-Specific Parameters

    10. Select Add Value from the Edit menu. In the Value Name edit box, enter one of the valid parameter values. Make sure to enter the appropriate data type for the value. To enter additional values, repeat Steps 8 and 9. NOTE Changes made with the Registry Editor do not take effect until you restart your system.
  • Page 48: Troubleshooting

    \HKEY_LOCAL_MACHINE\System\CurrentControlSet\ Services\adpu160m\Parameters\Device If the Parameters\Device keys already exist, skip to Step 10 below to begin entering parameters. If the keys do not yet exist, you will need to create them by continuing with Step 4. 4. Click on the adpu160m key. 5.
  • Page 49: Problems And Solutions

    Problems and Solutions I made changes to the host adapter configuration and Windows 2000 no longer boots! The boot manager for Windows 2000 contains recovery logic to allow you to return to the last known good configuration. If you have changed your host adapter configuration and Windows 2000 no longer boots, follow these steps to recover: 1.
  • Page 50: Driver Error Messages

    3. Click on the Words option. In the Data section of the dialog box, the entry in the second row and second column (to the right of the 0010: entry) lists the error message generated by the driver. The common error messages for the driver are described below. NOTE The entry in the third row of the last column identifies the SCSI ID of the device originating the error.
  • Page 51 [xxxxx012] Error issuing command [xxxxxx99] Error issuing command The driver does not recognize the target device. [xxxxx021] Target device protocol error An unexpected event occurred during data transfer between the adapter and tar- get device. Normally, this indicates a faulty or non-compliant target device. [xxxxx022] Adapter or target device protocol error The adapter or target device has broken the communication protocol.
  • Page 52 [xxxxx081] Adapter initialization failure [xxxxxx8A] Adapter initialization failure [xxxxxx83] Adapter initialization failure An error has occurred while the driver was setting up its internal data structures. Verify that your adapter is supported by this version of the driver. [xxxxx089] Unable to allocate memory This indicates that there may be a problem with the amount of memory installed in your system.
  • Page 53 ponent external to the miniport driver, such as the operating system or an ASPI application. [xxxxxd4] Adapter hardware failure - adapter reset The host adapter hardware failed and the miniport driver has to reset the hard- ware. [xxxxx0d6] Internal driver error An error has occurred while the driver was setting up its internal data structures.
  • Page 55: Novell Netware Installation

    Novell NetWare Installation This chapter explains how to install the HP Ultra3 Family Manager Set driver adpt160m.ham for Novell NetWare— NetWare 3.3, 4.2, and 5.0. If you are performing a first time NetWare installation, see “Installing the Driver When Installing NetWare” in the next section. If NetWare is already installed in your system, see “Installing the Driver When NetWare is Already Installed”...
  • Page 56 4. Reboot your computer after configuring for CD-ROM access. 5. Follow the instructions in your NetWare documentation for installing a new server. 6. After NetWare installs the DOS portion of the software, down and exit to DOS from the server prompt. 7.
  • Page 57: Netware 4.12/4.2

    The slot number can be added to the startup.ncf file, as described in Step 21 below, to automate driver load using the parameter slot=x, where x is the detected slot number (for example, load c:\server.312\adpt160m slot=2). 17. Load Install. Create the NetWare partition, SYS volume, and mount the volume.
  • Page 58: Netware 5.0

    4. Press F3 and enter a:\netware as the path to the adpt160m.ham driver for NetWare. 5. Select adpt160m.ham and press Enter. 6. Select No not to save existing file, Yes to save existing file cdrom.nlm. 7. Select No not to save existing file, Yes to save existing file nbi.nlm. 8.
  • Page 59: Dos Drivers For Cd-Rom Access

    10. To install additional adapters, follow the procedures from Step 4. 11. When complete, select Continue to complete the installation. DOS Drivers for CD-ROM Access The CD-ROM drivers need to be installed only if DOS access to a CD-ROM drive attached to a SCSI host adapter is required. If NetWare is already installed, or if the CD-ROM drive is not connected to a SCSI adapter, these drivers do not need to be copied or installed.
  • Page 60: Installing The Driver When Netware Is Already Installed

    NOTE This will assign the CD-ROM to the next available drive letter, typically D if there is only one DOS drive. If you are using MS-DOS 5.0 and do not already have mscdex.exe, you will need to either upgrade to MS-DOS 6.0 or above, or download mscdex.exe from Microsoft BBS or CompuServe forum.
  • Page 61: Loading The Driver At Server Bootup

    Loading the Driver at Server Bootup To automatically load the adpt160m.ham at server bootup, the startup.ncf file (usually located in your server’s startup directory) must contain a load command line that specifies the location of the driver and any appropriate command line options (see “Using the Load Command Line Options”...
  • Page 62: Adpt160M.ham Command Line Options

    adpt160m.ham Command Line Options Option Values Default Description auto_disable_tagq= on, off Enables/disables auto disable tagged queuing algorithm. dev_enable= 0-FFFF FFFF Allows you to enable the driver's registration of SCSI devices on a per target basis. By default, all targets are scanned. A bit value of 0 causes the target not to register under the operating system.
  • Page 63 Option Values Default Description multlun_targets= 0-FFFF FFFF A bit mask to enable LUNs on selected targets. By default, LUNs on all targets are enabled. This bit mask is entered in hex (see “Bit Mask Options” on page 58). slot= Defines a physical slot number 0-xxxx for the host adapter.
  • Page 64: Bit Mask Options

    Bit Mask Options Use the example below as an aid for calculating Bit Mask option hex values. Each SCSI device is enabled by a 1 in its corresponding bit position. The table that follows the figure, lists the binary-to-hex conversions. Using this example, if you want to enable scanning for LUNs 0, 2, and 6 on all targets, then use the command line option of lun_enable=0045.
  • Page 65: Sample Load Commands

    Sample Load Commands Here is a simple load command with no option switches (if loaded from drive A): load a:\netware\adpt160m.ham If an error message appears when attempting to load the driver, refer to “Troubleshooting” on page 63. Here is an example of the adpt160m.ham driver being loaded with command line options (if loaded from drive A): load a:\netware\adpt160m.ham verbose=y slot=2 Using NetWare and the Host Adapter...
  • Page 66 Menu Choice Default Value 1. Volume Segments On Drive (select for list) 2. Read After Write Verify Hardware Level 3. Drive Light Status Not Supported 4. Driver Operating Status Active 5. Removable Drive Mount Status Mounted 6. Removable Drive Lock Status Not Locked Valid for both removable and non-removable types of SCSI disk drives.
  • Page 67: Using The Netware Tape Backup

    Using the NetWare Tape Backup Included with Novell NetWare is a server-based tape backup utility called sbackup.nlm. This utility allows you to backup server disk drives to a server tape drive. The utility supports HP host adapters. Novell NetWare documentation contains instructions for loading the server backup software.
  • Page 68: Optimizing Performance

    NOTE For multiple LUN CDs, enable multiple LUN scanning with the lun_enable switch (e.g., load adpt160m lun_enable=FF). The lun_enable switch is needed for adpt160m.ham. Enter the following line at the prompt: scan all luns 1. Enter the following line at the prompt and then note the number and name of the CD: :cd device list 2.
  • Page 69: Troubleshooting

    Troubleshooting Error Messages The error messages listed below are the messages associated with the adpt160m.ham driver. Messages are listed sequentially according to the last three digits of the error code. For example, [xxxxx080], [xxxxx081], [xxxxx082], etc. NOTE When reporting problems to HP Customer Support, be sure to include the complete error code in your problem description.
  • Page 70 [xxxxx084] Adapter software initialization failure An error has occurred while the driver was setting up its internal data structures. Try installing the most up-to-date version of the driver available from the HP Web site located at http://netserver.hp.com/netserver/ [xxxxx085] Unable to allocate memory This indicates that there may be a problem with the amount of memory installed in your system.
  • Page 71 [xxxxx099] Adapter software initialization failure [xxxxx09a] Adapter software initialization failure [xxxxx09b] Adapter software initialization failure An error has occurred initializing one of the driver’s internal data structures for a device connected to the adapter. This may result in problems accessing the device.
  • Page 72 [xxxxx0ca] Invalid command line syntax [xxxxx0cb] Invalid command line syntax [xxxxx0cc] Invalid command line syntax The command line syntax for the driver is incorrect. See “Using the Load Command Line Options” on page 55 for entering the correct syntax. [xxxxx07c] Unable to allocate memory [xxxxx07d] Unable to allocate memory [xxxxx07e] Unable to allocate memory [xxxxx07f] Unable to allocate memory...
  • Page 73: Sco Openserver Installation

    SCO OpenServer Installation This chapter explains how to install the HP Ultra3 Family Manager Set driver ad160 for SCO OpenServer 5.0.x. The ad160 driver supports the HP Ultra3 SCSI host bus adapter. If you are performing a first time SCO OpenServer installation, see “Installing the Driver When Installing SCO OpenServer”...
  • Page 74: Installing The Driver When Sco Openserver Is Already Installed

    NOTE Remember that UNIX commands are case sensitive. Enter the commands exactly as shown in the instructions. 1. Insert the SCO OpenServer 5.0.x boot disk into the primary floppy disk drive and turn ON the computer. Alternatively, insert the SCO OpenServer 5.0.x boot CD into the primary CD-ROM drive and turn ON the computer.
  • Page 75 CAUTION Improper or corrupt driver updates might destroy your existing UNIX file system. Back up all important files before proceeding. Installing or updating the driver involves the following tasks, which must be completed in the order presented: • Back up the old UNIX kernel and any other important files. •...
  • Page 76 mount /dev/boot /stand cp /stand/unix /stand/unix.orig NOTE If you ever need to boot up from the pre-update kernel, load the unix.orig backup kernel at the UNIX boot: prompt. To do this, type unix.orig and press Enter. This step is optional. For extra security, you may back up the mdevice file and the sdevice.d directory To perform this backup, type the following and press Enter: copy -rom /etc/conf /etc/conf.bak...
  • Page 77 Please enter the names of the packages you wish to install, or q to quit: At this point, type ad160 and press Enter. The screen then displays this mes- sage and various installation status prompts: Installing adl60 When the driver is loaded, the following message appears, indicating that the adl60 driver has been loaded into the Link Kit for kernel addition: Installed adl60 Modify the mscsi file, if necessary, to change your primary host bus adapter to an...
  • Page 78 Modify the mscsi file according to your hardware setup: • If you are booting from an Ultra3 SCSI host bus adapter, make sure the host adapter prefix for the host adapter number 0 is ad160. • If you are not booting from an Ultra3 SCSI host bus adapter, make sure the host adapter prefix for the host adapter number 0 is the appropriate prefix for each device on your primary HP host adapter.
  • Page 79: Using Sco Openserver And The Host Adapter

    Check the host bus adapter BIOS messages to verify that all your installed SCSI devices are listed. If some or all of your installed SCSI devices do not appear at this time, your SCSI cables may be loose, or the SCSI device setup may not be complete. If so, go back and correct any problem before proceeding.
  • Page 80: Changing The Boot Disk

    Changing the Boot Disk If you are changing the boot device from a non-SCSI hard disk to a SCSI hard disk attached to an HP Ultra3 SCSI host bus adapter, you must reinstall SCO OpenServer. If you are already booting from a SCSI hard disk attached to an HP PCI SCSI host bus adapter, and wish to boot from the same SCSI hard disk attached to an HP Ultra3 host bus adapter, you may elect to either reinstall SCO OpenServer with the new driver, or update SCO OpenServer with the new driver.
  • Page 81: Changing The Maximum Number Of Luns Supported

    char variable = {1,22}; The first number is 1, which overrides the default variable with the value 22. Examples: The following specifies whether the host bus adapter checks parity on incoming SCSI data: ad160_parity[SCSI_NAD160] If the second number is set to 0, parity checking is enabled. If it is set to 1, parity checking is disabled.
  • Page 82: Troubleshooting

    Troubleshooting My computer does not recognize my SCSI devices. At boot time, check to see if the BIOS messages for your primary Ultra3 host bus adapter lists all installed SCSI devices. If some or all devices do not appear, check your host bus adapter User’s Guide for additional troubleshooting information, and check the following: •...
  • Page 83 Look on the first screen of SCSISelect in the upper right hand corner for Bus:Device xx:xxh (shown in hexadecimal). • If the device number is high, power OFF the computer, move the HP Ultra3 SCSI host bus adapter to a PCI slot at the other end of the motherboard, and run SCSISelect again to see if the number is lower.
  • Page 84 adl60 Sdsk 0 0 0 0 NOTE Each field is separated by a tab. Do not use the spacebar to separate fields. The meanings of the fields are as follows: Table 6-1. Host SCSI Host Logical Adapter Device Adapter Unit Target Prefix Type...
  • Page 85 If you are booting from an HP Ultra3 SCSI host bus adapter and are using ISA/ EISA-based host bus adapters as secondary devices, you must disable the BIOS on all ISA/EISA-based host bus adapters. If you are booting from ISA/EISA-based host bus adapters and are using an Ultra3 SCSI host bus adapter as a secondary device, see your ISA/EISA-based host bus adapter documentation to ensure that the host bus adapter is at the lowest BIOS base address.
  • Page 86: Error Messages

    9. Type Y to rebuild the kernel environment. 10. Reboot the system. Error Messages The error messages listed below are the messages associated with the adl60 driver. Messages are listed sequentially according to the last three digits of the error code. For example, [xxxxx010], [xxxxx011], [xxxxx012], etc. NOTE When reporting problems to Customer Support, be sure to include the complete error message in your problem description.
  • Page 87 [xxxxx0a3] Adapter diagnostic failure - possible resource conflict The driver failed the internal software or hardware diagnostic. Refer to your host bus adapter User’s Guide for troubleshooting information. [xxxxx0ca] Cannot initialize device The system, host bus adapter, or target device is busy or is not responding. The target device could not be initialized.
  • Page 89: Sco Unixware Installation

    SCO UnixWare Installation This chapter explains how to install the HP Ultra3 Family Manager Set drivers adst21 and adst70 for UnixWare— UnixWare 2.1x and UnixWare 7.01/7.1. adst21 driver (or package) is used with UnixWare 2.1x. The adst70 driver (or package) is used with UnixWare 7.01/7.1. If you are performing a first time UnixWare installation, see “Installing the Driver When Installing UnixWare”...
  • Page 90: Installing The Driver When Unixware Is Already Installed

    6. If necessary, enter the DCU (Device Configuration Utility) to view/change the UnixWare device driver configuration data. 7. Follow the on-screen instructions to continue with installation. Refer to the UnixWare documentation and on-screen help files for help in selecting options. NOTE If your installation fails, do not attempt to use the update installation pkgadd procedure to fix the installation.
  • Page 91: Back Up The Computer

    was loaded in the previous procedure. Loading the driver causes the driver to become a permanent part of the new boot kernel on rebuild. 4. Rebuild the UnixWare Kernel—Rebuilds the kernel with the new driver. 5. Boot the New Kernel—Reboots the computer with the new kernel. NOTE Remember that UnixWare commands are case sensitive.
  • Page 92: Modify The New System File

    If a mail message informs you that the installation has failed, turn to “Troubleshooting” on page 90. 5. Type pkginfo -l adstxx and press Enter. 6. Verify that the adst21 or adst70 driver is now listed. If the adst21 or adst70 driver does not appear in the pkginfo listing, turn to “Troubleshooting”...
  • Page 93: Boot The New Kernel

    cd /etc/conf/bin ./idbuild -B Status messages appear. 2. When the kernel has been built, type the following and press Enter after each line (0 in -g0 is zero, not the letter O): cd /etc/conf/cf.d cp unix /stand/unix cd / shutdown -g0 3.
  • Page 94: Using Tunable Parameters

    Using Tunable Parameters For UnixWare, some parameters are defined in the following files: /etc/conf/pack.d/adst21/space.c /etc/conf/pack.d/adst70/space.c These parameters can be tuned for either the adst21 driver or the adst70 driver. Please refer to the comments in the appropriate space.c file for a description of these parameters.
  • Page 95 1. Back up all important computer files. 2. At the UnixWare root prompt, type the following: For UnixWare 2.1x: /etc/conf/bin/idinstall -d adst21 The following files will be deleted: /etc/conf/mdevice.d/adst21 /etc/conf/pack.d/adst21/Driver.o /etc/conf/pack.d/adst21/space.c /etc/conf/pack.d/adst21/disk.cfg /etc/conf/sdevice.d/adst21 For UnixWare 7.01/7.1: /etc/conf/bin/idinstall -d adst70 The following files will be deleted: /etc/conf/mdevice.d/adst70 /etc/conf/pack.d/adst70/Driver.o /etc/conf/pack.d/adst70/space.c...
  • Page 96: Troubleshooting

    Troubleshooting Problems and Solutions My computer crashes or displays panic messages during the bootup procedure! You may have to boot from the backup kernel created earlier, and then perform the driver update procedure again. To boot from the old kernel, follow these steps: 1.
  • Page 97 NOTE When reporting problems to Customer Support, be sure to include the complete error code in your problem description. [xxxxx003] Command completed with error [xxxxx004] Command completed with error [xxxxx005] Command completed with error [xxxxx006] Command completed with error [xxxxx007] Command completed with error [xxxxx008] Command completed with error [xxxxx009] Command completed with error A request issued to a target device completed with an indication that there is an...
  • Page 98 [xxxxx020] Adapter or target device not responding or not connected The target device did not respond to the adapter. If the device is present, refer to your host adapter’s user’s guide for troubleshooting information. If the device is no longer connected to the system, ignore this error. [xxxxx021] Target device protocol error An unexpected event occurred during data transfer between the adapter and target device.
  • Page 99 [xxxxx041] Command aborted [xxxxx042] Command aborted [xxxxx043] Command aborted [xxxxx044] Command aborted [xxxxx045] Command aborted An internal condition caused the driver to abort the command. In most cases, the command is retried and is recovered, and normal operation continues. [xxxxx046] Target device did not respond to abort sequence The target device did not abort the command requested by the driver.
  • Page 100 [xxxxx096] Adapter hardware initialization failure - possible resource conflict The driver has attempted to initialize the adapter hardware but failed. This might suggest that the adapter resources (e.g., IRQ) conflict with another board installed in your system. [xxxxx097] Unable to allocate memory This indicates that there may be a problem with the amount of memory installed in your system.
  • Page 101: Linux Support

    Linux Support The HP Ultra3 SCSI host bus adapter supports the following Linux Operating Systems: Linux Operating System World Wide Web URL Caldera Operations eDesktop 2.4 www.caldera.com Debian Linux 2.2 www.debian.com RedHat Linux 6.2 www.redhat.com SuSE Linux 6.4 www.suse.com TurboLinux Workstation 6.0 www.turbolinux.com Installation Guides are available at the web sites listed above.
  • Page 103: A Product Specifications

    Product Specifications These specifications list the operating conditions for the Ultra3 SCSI adapter. Check the User Guide for the server containing the adapter, and ensure that the target operating environment is suitable for both the server and adapter. Electrical Power Requirements 5.0V +/- 5% @ 1.2A maximum Power Consumption 6 W maximum...
  • Page 104 Electrical Device Support Up to 15 LVD or SE SCSI devices Cable Length 25m for a single LVD SCSI device Up to 12m for 15 LVD devices Electrical Termination Automatic active, programmable via SCSISelect Physical Dimensions 6.875 x 3.725 x 0.44 inches 174.63 x 94.62 x 11.18 millimeters Internal One 68-pin LVD SCSI...
  • Page 105 Regulatory Meets USA: CFR 47 part 15, Class B, C63.4 - 1992 electromagnetic Canada: Industry Canada, ICES-003, CISPR 22, compliance Class B requirements of: Europe: EN50081, EN 55022, Class B Japan: VCCI, CISPR 22 Class B ITE South Korea: Min. of Information & Communication, Class B Australia: AS/NZS 3548 - EN 55022 New Zealand: AS/NZS 3548 - EN55022...
  • Page 107: B Troubleshooting

    Troubleshooting Troubleshooting Checklist Most problems that occur with your host adapter result from errors in preparing and connecting devices on the SCSI bus. If you have problems when using your host adapter, check these items first. • Are all SCSI devices powered? •...
  • Page 108 If the message still appears, follow the drive manufacturer's instructions to make sure the drive is set to spin up when the power is switched ON. Start unit request failed The BIOS was unable to send a Start Unit Command to the device. Run the SCSISelect utility and disable Send Start Unit Command for the device.
  • Page 109: C Regulatory Information

    Regulatory Information Regulatory Notices - Electromagnetic Compliance Electromagnetic Compatibility (EMC) requirements have been established in many countries to regulate the radio frequency energy generated by Information Technology Equipment (ITE). This energy is generated during the normal and intended use of this equipment and so it is limited by country regulations to levels intended to minimize potential interference to other electrical equipment, including public safety services.
  • Page 110 HP shielded cables, such as those you receive with your computer. Changes or modifications not expressly approved by Hewlett-Packard could void the user's authority to operate the equipment. Cables used with this device must be properly shielded to comply with the requirements of the FCC.
  • Page 111: Notice For Canada (Industry Canada)

    class A accessory in a system that has been labeled as a class B product, the requirements and notice for class A equipment shall be applied. Notice for Canada (Industry Canada) This digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.
  • Page 112: Notice For Korea

    radio interference may be caused. In this case, you may need to take appropriate corrective actions. Notice for Korea The equipment you have purchased may be in either the class A or class B category. Class A Equipment: Please note that this equipment has been approved for business purposes with regard to electromagnetic interference.
  • Page 113: Notice For Taiwan

    Notice for Taiwan Class A Warning...
  • Page 114 FCC Title 47 CFR, Part 15 Supplementary Information: 1) The product was tested in a typical configuration with Hewlett-Packard servers. 2) The product complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: This device may not cause harmful interference, and This device must accept any interference received, including interference that may cause undesired operation.
  • Page 115: D Warranty And Support

    Hardware Accessories Limited Warranty Hewlett-Packard Hardware Accessories An HP Netserver Hardware Accessory is an internal HP hardware product that is specifically designated for use with HP Netservers; is added on or integrated into an HP Netserver in order to provide higher performance, capacity, or increased capability;...
  • Page 116: Third-Party Hardware Products

    warranty for those products. HP SureStore drives are considered external accessories and carry their own warranty. The customer may be required to run HP-supplied configuration and diagnostic programs before a replacement will be dispatched or an on-site visit is authorized. Third-Party Hardware Products HP does not warrant third-party hardware products.
  • Page 117: Index

    Index aspi8u2.sys 53 Hardware accessories limited warranty 109 aspicd.sys 53 host adapter 101 autoexec.bat 53 Hot-plug PCI 29 Backup 61 Installation – Bit mask options 56 NetWare driver 49 – Booting UnixWare driver 83 – from UnixWare 86 Windows NT driver 23 interference 104 CD-ROM 49 Command line options 54...
  • Page 118 CD-ROM support 61 command line options 54 Tagged commands 56 error messages 63 – Tagged queuing 26 installing the driver 49 Tape backup 61 load command 54 Troubleshooting max_tags 62 – NetWare 63 monitor.nlm 59 – UnixWare 90 optimizing performance 62 –...
  • Page 119 registry editor 25 removing a host adapter 30 removing the driver 30 – troubleshooting 31...

Table of Contents