Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP 9000 and HP Integrity Systems: AB290A PCI-X 2-Port U320 SCSI and 2-Port Gigabit Ethernet Combination Card Installation Guide > Chapter 1 Hardware and Software Installation Procedure

Step 9: Verify the SCSI installation

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

After installing the scsiU320-00 software bundle containing the mpt driver, installing the AB290A adapter, and attaching the peripheral devices, verify that all of the components are working by following these steps:

  • To verify that the mpt driver appears for each installed card, enter:

    ioscan -fnkd mpt

    The ioscan output will be similar to the following example:

    # ioscan -fnkd mpt
    Class I H/W Path Driver S/W State H/W Type Description

    ================================================
    ext_bus 6 1/0/2/0/0 mpt CLAIMED INTERFACE HP AB290A PCI-X 2port U320 SCSI/2port 1000Base-T Adapter
                            /dev/mpt6
    ext_bus 7 1/0/2/0/1 mpt CLAIMED INTERFACE HP AB290A PCI-X 2port U320 SCSI/2port 1000Base-T Adapter
                            /dev/mpt7
    ext_bus 8 1/0/4/0/0 mpt CLAIMED INTERFACE HP AB290A PCI-X 2port U320 SCSI/2port 1000Base-T Adapter
                            /dev/mpt8
    ext_bus 9 1/0/4/0/1 mpt CLAIMED INTERFACE HP AB290A PCI-X 2port U320 SCSI/2port 1000Base-T Adapter
                            /dev/mpt9

    In this example, two AB290A adapters are installed on the system. The fourth and fifth columns in the ioscan output indicate that the adapters have been claimed by the mpt driver. The third column shows the hardware path of the slot in which the card is installed. This path will be different for each installed card. The AB290A adapter supports two PCI devices or functions (one per channel). Two lines are listed for each AB290A adapter, —one for channel A (denoted by a 0 as the last digit in the hardware path), and one for channel B (denoted by a 1 as the last digit in the hardware path). The device file for each channel of each installed adapter is in the second line of the ioscan output, for example: /dev/mpt6 or /dev/mpt7.

    • For more detailed information on installed AB290A adapter(s), including the SCSI parameter settings as well as verification of devices that have been connected to the AB290A adapter(s), issue the mptconfig <dev file> command for each channel of each AB290A adapter. Use the device files displayed in the ioscan -fnkd mpt output.

      For example:

      # mptconfig /dev/mpt8
       Scan For Devices ...
      ---- ADAPTER INFORMATION -----------------------------------------------------
       Device File                   : /dev/mpt8
       Hardware Path                 : 1/0/4/0/0
      ---- BUS PARAMETERS ----------------------------------------------------------
       Initiator SCSI ID : 5
       SCSI Bus Rate : Ultra320
       SCSI Bus Width : Wide
      ---- CHANNEL CAPABILITIES ----------------------------------------------------
       Req/Ack Offset : 127
       Bus Mode : LVD
       Quick Arbitration Selection : Enabled
       DT Clocking : Enabled
       Packetized : Enabled
      ---- TARGET PARAMETERS -------------------------------------------------------
       Target Description       Firmware In Use In Use
       Id                       Version Rate Width
      ------------------------------------------------------------------------------
       0 ST318453LC HPC3 Ultra320 Wide
       2 ST373453LC HPC3 Ultra320 Wide
       4 ST373453LC HPC4 Ultra320 Wide
      ------------------------------------------------------------------------------
      #
      NOTE: When the system boots after installation, the insf command creates the proper device files for the “ctl” interfaces (which would include the AB290A adapter) as well as the SCSI devices attached to the AB290A adapter. Sometimes, however, the insf command does not create all of the device files that are needed. For example, this happens when you attach SCSI disks to the adapter after the system boots, but the adapter is already installed in the system.

      If you see a SCSI device listed in the ioscan output, but there is no device file in the second line of the ioscan output for that device, the device file is missing. To solve this problem, issue the insf -e command, which will create all of the device files.

      For more information about the ioscan command, see the ioscan(1M) man page.

      For more information about the insf command, see the insf (1M) man page.

      Refer to your system documentation for information about verifying system operation.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2005 Hewlett-Packard Development Company, L.P.