The Troubleshooting Tools

You can use these tools to troubleshoot the HP RAID 4Si product:

The HP RAID 4Si irdiag command; see the description below.
The HP RAID 4Si irdisplay command; see “The irdisplay Command”.
The HP RAID 4Si i2outil command; see “The i2outil Command”.
The HP-UX ioscan command; see the ioscan(1M) man page.
IRM.




	NOTE: Because the HP RAID 4Si product contains its own monitoring daemon (`irmd`), the Event Monitoring System (EMS) is not supported for RAID 4Si logical drives.

The irdiag Command

The HP RAID 4Si irdiag command displays status and diagnostic information about all of the HP RAID 4Si controllers installed in the HP-UX system.

If you include /sbin in your PATH statement, you can run the command as it is shown below. Otherwise, you must include /sbin as part of the command name (that is, /sbin/irdiag).

You must be logged in as root to run this command.

The syntax is as follows:

irdiag {i|v} [device_file]

where

i queries the controller specified by device_file. If you do not specify device_file, all installed controllers are queried. If a controller is operational, the corresponding information for it is displayed. If a controller is not responding, errors are displayed. You must specify i or v (see the next bullet).
v queries the controller specified by device_file. If you do not specify device_file, all installed controllers are queried. If a controller is operational, the corresponding information for it is displayed. If a controller is not responding, errors are displayed. Note that the information this option reports is more detailed—it reports on each controller, SCSI channel, logical drive, and physical drive. You must specify v or i (see the previous bullet).
device_file specifies the HP RAID 4Si controller you want information for.

Examples of irdiag

Some examples of using irdiag are shown below.

Example 1

Issuing the command

irdiag -i

generates output that could look like this:

Adapter Hardware Path:  0/7/0/1
 
     Device File: /dev/iop0
     Product ID: 467
     Firmware Version: U.01.06
     Number of Logical Drives Configured: 3
     Maximum Concurrent Commands Supported: 254
     Maximum Targets Supported per Channel: 16
     Number of Channels: 4
     Flush Interval: 4
     Rebuild Rate: 30
     Dram Size (Mb): 128
     Battery Pack: Present
     Battery Status: Charging Completed
     Battery Temperature: Good
     Battery Voltage: Good

Example 2

Issuing the command

irdiag -v

generates output that could look like this:

******************** Internal RAID Adapter 0/7/0/1 ********************
 
PowerFail Safeguard    = ENABLED
Disk Spin Up           = AUTOMATIC
Rebuild Rate           = 30%
Firmware Version       = U.01.06
DRAM Size              = 128 MB
Device File            = /dev/iop1
Hardware Path          = 0/7/0/1
Adapter Type           = 467
Speaker                = DISABLED
Battery Pack           = CONNECTED
Battery Status         = CHARGING COMPLETED
Battery Temperature    = GOOD
Battery Voltage        = GOOD
Battery Charge Counter = 1
Configuration Saves    = 6
Firmware Downloads     = 2
Initiator ID           = 7
 
----------Channel 0----------
 
State                  = ACTIVE
Termination            = WIDE
SCSI Transfer Rate     = ULTRA-2
SCSI Devices Attached:
 
Ch   ID   Type           Capacity  Vendor/Product/Revision       Status
 
0    0    DISK           8681 MB   IBM DMVS09D HP07              HOTSPARE
0    1    DISK           8681 MB   IBM DMVS09D HP07              ONLINE
0    2    DISK           8681 MB   IBM DMVS09D HP07              ONLINE
0    3    DISK           8681 MB   IBM DMVS09D HP07              ONLINE
0    8    DISK           8681 MB   IBM DMVS09D HP07              ONLINE
0    9    DISK           8681 MB   IBM DMVS09D HP07              ONLINE
0    10   DISK           8681 MB   IBM DMVS09D HP07              ONLINE
0    11   DISK           8681 MB   IBM DMVS09D HP07              READY
0    12   DISK           8681 MB   IBM DMVS09D HP07              READY
0    13   DISK           8681 MB   IBM DMVS09D HP07              READY
0    14   SES            N/A       HP A5272A HP04
 
----------Channel 1----------
 
State                  = ACTIVE
Termination            = WIDE
SCSI Transfer Rate     = ULTRA-2
SCSI Devices Attached:
 
None Detected
 
----------Channel 2----------
 
State                  = ACTIVE
Termination            = WIDE
SCSI Transfer Rate     = ULTRA-2
SCSI Devices Attached:
 
None Detected
 
----------Channel 3----------
 
State                  = ACTIVE
Termination            = WIDE
SCSI Transfer Rate     = ULTRA-2
SCSI Devices Attached:
 
None Detected
 
----------------------LOGICAL DRIVES SUMMARY--------------------
LD      RAID    Size                    #Stripes        StrpSz  Drive-State
 
0       1       8682MB(8.5GB)           2               64KB    OPTIMAL
1       1       8682MB(8.5GB)           2               64KB    OPTIMAL
2       1       8682MB(8.5GB)           2               64KB    OPTIMAL
 
 
--------------------------Logical Drive 0-------------------------
 
RAID LEVEL   = 1
Size         = 8682MB (8.5GB)
StripeSize   = 64KB
Write Policy = WRTHRU
Read Policy  = ADAPTIVE
Cache Policy = Cached IO
#Stripes     = 2
State        = OPTIMAL
Spanned      = NO
#Spans       = 1
Disks in Span 0 :
Ch   ID   Type      Capacity  Vendor/Product/Revision       Status
 
0    1    DISK      8681 MB   IBM DMVS09D HP07              ONLINE
0    2    DISK      8681 MB   IBM DMVS09D HP07              ONLINE
 
--------------------------Logical Drive 1-------------------------
 
RAID LEVEL   = 1
Size         = 8682MB (8.5GB)
StripeSize   = 64KB
Write Policy = WRTHRU
Read Policy  = ADAPTIVE
Cache Policy = Cached IO
#Stripes     = 2
State        = OPTIMAL
Spanned      = NO
#Spans       = 1
Disks in Span 0 :
Ch   ID   Type      Capacity  Vendor/Product/Revision       Statu
 
0    3    DISK      8681 MB   IBM DMVS09D HP07              ONLINE
0    8    DISK      8681 MB   IBM DMVS09D HP07              ONLINE
 
--------------------------Logical Drive 2-------------------------
RAID LEVEL   = 1
Size         = 8682MB (8.5GB)
StripeSize   = 64KB
Write Policy = WRTHRU
Read Policy  = ADAPTIVE
Cache Policy = Cached IO
#Stripes     = 2
State        = OPTIMAL
Spanned      = NO
#Spans       = 1
Disks in Span 0 :
Ch   ID   Type      Capacity  Vendor/Product/Revision       Status
 
0    9    DISK      8681 MB   IBM DMVS09D HP07              ONLINE
0    10   DISK      8681 MB   IBM DMVS09D HP07              ONLINE
 
-----------------SCSI Device 0:0----------------
 
Channel         = 0
Target          = 0
Block Size      = 512 Bytes
Device Type     = DISK
Capacity        = 8681 MB
Vendor ID       = IBM
Product ID      = DMVS09D
Revision        = HP07
SCSI Standard   = SCSI-3
Media Errors    = 0
Other Errors    = 0
State           = HOTSPARE
Tag Depth       = 0
SyncNegotiation = 0
 
-----------------SCSI Device 0:1----------------
 
Channel         = 0
Target          = 1
Block Size      = 512 Bytes
Device Type     = DISK
Capacity        = 8681 MB
Vendor ID       = IBM
Product ID      = DMVS09D
Revision        = HP07
SCSI Standard   = SCSI-3
Media Errors    = 0
Other Errors    = 0
State           = ONLINE
Tag Depth       = 0
SyncNegotiation = 0
Part of Logical Drive 0
 
-----------------SCSI Device 0:2----------------
 
Channel         = 0
Target          = 2
Block Size      = 512 Bytes
Device Type     = DISK
Capacity        = 8681 MB
Vendor ID       = IBM
Product ID      = DMVS09D
Revision        = HP07
SCSI Standard   = SCSI-3
Media Errors    = 0
Other Errors    = 0
State           = ONLINE
Tag Depth       = 0
SyncNegotiation = 0
Part of Logical Drive 0
         .
         . 
         .
-----------------SCSI Device 0:14----------------
 
Channel         = 0
Target          = 14
Device Type     = SES
Vendor ID       = HP
Product ID      = A5272A
Revision        = HP04
SCSI Standard   = SCSI-2
Tag Depth       = 0
SyncNegotiation = 0
 
-----------Enclosure at Channel 0:Target 14-------------
 
Enclosure is in SES mode
 
ENCLOSURE CONFIGURATION
 
Enclosure Vendor ID                   = HP
Product ID                            = A5272A
Product Revision Level                = HP04
Vendor Specific Enclosure Information = Ultra2 SCSI High Availability Storage
System 1010D
 
Monitored elements:        Up to 10 Disk Device
        Up to 2 Power Supply
        Up to 2 Fan
        Up to 4 Temperature
        Up to 1 Audible Alarm
        Up to 2 Enclosure Services Controller
        Up to 2 Port Transceiver
        Up to 6 Voltage Sensor
 
ENCLOSURE STATUS
 
Critical condition detected (see below)
 
Device 0 Okay
        SCSI TID:  0
Device 1 Okay
        SCSI TID:  8
Device 2 Okay
        SCSI TID:  1
Device 3 Ok
        SCSI TID:  9
Device 4 Okay
        SCSI TID:  2
Device 5 Ok
        SCSI TID:  10
Device 6 Okay
        SCSI TID:  3
Device 7 Okay 4
        SCSI TID:  11
Device 8 Okay 2
        SCSI TID:  13
Device 9 Okay 6
        SCSI TID:  12
Power supply 0 Critical
        Failed LED on
Power supply 1 Okay
Cooling element 0 Okay
        Fan speed:  intermediate
Cooling element 1 Okay
        Fan speed:  intermediate
Temperature sensor 0 Okay
        Temperature = 25 Celsius
Temperature sensor 1 Okay
        Temperature = 26 Celsius
Temperature sensor 2 Not installed
Temperature sensor 3 Not installed
Unspecified 0 Okay
Enclosure controller 0 Okay
        Active controller
Enclosure controller 1 Not installed
SCSI port/transceiver 0 Okay
SCSI port/transceiver 1 Not installed
Voltage sensor 0 Okay
        Voltage = 338 millivolts
Voltage sensor 1 Okay
        Voltage = 516 millivolts
Voltage sensor 2 Okay
        Voltage = 1224 millivolts
Voltage sensor 3 Not installed
Voltage sensor 4 Not installed
Voltage sensor 5 Not installed
         .
         .
         .
        Ch0     Ch1     Ch2     Ch3
ID
0       HSP     -       -       -
1       ONL     -       -       -
2       ONL     -       -       -
3       ONL     -       -       -
4       -       -       -       -
5       -       -       -       -
6       -       -       -       -
7       -       -       -       -
8       ONL     -       -       -
9       ONL     -       -       -
10      ONL     -       -       -
11      RDY     -       -       -
12      RDY     -       -       -
13      RDY     -       -       -
14      -       -       -       -
15      -       -       -       -
 
where RDY  = READY
      ONL  = ONLINE
      HSP  = HOTSPARE
      FAIL = FAILED
      RBLD = REBUILD
      UNKN = UNKNOWN

You can also see the irdiag(1M) man page for information.

The irdisplay Command

The HP RAID 4Si irdisplay command displays the following information:

For each controller it finds—combined output of the irdiag -i and ioscan commands.
For each logical drive it finds—combined output of the ioscan and diskinfo commands.

If you include /sbin in your PATH statement, you can run the command as it is shown below. Otherwise, you must include /sbin as part of the command name (that is, /sbin/irdisplay).

You must be logged in as root to run this command.

The syntax is as follows:

irdisplay [-f]

where

-f forces ioscan to rescan all of the hardware installed in the system. Always specify this option after you have changed the HP RAID 4Si configuration.

Example of irdisplay

As an example of using irdisplay, issuing the command

irdisplay

generates output that could look like this:

********************************************************************
                 Internal RAID Adapter 0/7/0/1
 
                          Device File: /dev/iop1
                           Product ID: 467
                     Firmware Version: U.01.06
  Number of Logical Drives Configured: 3
Maximum Concurrent Commands Supported: 254
Maximum Targets Supported per Channel: 16
                   Number of Channels: 4
                       Flush Interval: 4
                         Rebuild Rate: 30
                       Dram Size (Mb): 128
                         Battery Pack: Connected
                       Battery Status: Charging Completed
                  Battery Temperature: Good
                      Battery Voltage: Good
      PCI to PCI Bridge Hardware Path: 0/7/0/0
             PCI to PCI Bridge Driver: PCItoPCI (Class ba Instance 8)
                Adapter Hardware Path: 0/7/0/1
                       Adapter Driver: iop_drv (Class i2o Instance 1)

You can also see the irdisplay(1M) man page for information.

The i2outil Command

You can use the HP RAID 4Si i2outil command to do the following:

Display the Logical Configuration Table (LCT), Status Buffer, and the Group1 parameter values of the Executive Parameter Group.
Get or clear the IOP driver statistics.
Download the HP RAID 4Si controller firmware.

If you include /usr/sbin in your PATH statement, you can run the command as it is shown below. Otherwise, you must include /usr/sbin as part of the command name (that is, /usr/sbin/i2outil).

You must be logged in as root to run this command.

The syntax is as follows:

i2outil device_file get_lct
        device_file get_status_buf
        device_file get_group1_parms
        device_file get_stats
        device_file clear_stats
        device_file download {DDM|IRTOS|PRIV} file_name

Note that some of the lines in the above syntax are indented for readability purposes only. When you actually type the command, you do not have to indent anything.

The command parameters are as follows:

device_file specifies the HP RAID 4Si controller you want to get information about or download firmware to.
get_lct displays important field values of the Logical Configuration Table (LCT) entries.
get_status_buf displays important field values of the Status Buffer.
get_group1_parms displays important field values in the Executive Parameter Group1.
get_stats displays the statistics maintained by the IOP driver.
clear_stats clears the statistics maintained by the IOP driver.
download downloads an image of type DDM, IRTOS, or PRIV (specify only one) that is in the file file_name to the controller. Note that if you want to download firmware to the controller, the image type is PRIV and file_name specifies the file that contains the firmware image.

Examples of io2util

Some examples of using io2util are shown below.

Example 1

Issuing the command

i2outil /dev/iop1 get_lct

generates output that could look like this:

**********************   LCT   *********************
Number of Entries = 5
Entry   Class   SubClass   LocalTID   ParentTID   UserTID   DeviceFlags
0)      0x000   0x00000001  0x000      0x000       0x000     0x00000002
1)      0x001   0x00000020  0x008      0x000       0x000     0x00000002
2)      0x010   0x00000000  0x010      0x008       0xfff     0x00000002
3)      0x010   0x00000000  0x011      0x008       0xfff     0x00000002
4)      0x010   0x00000000  0x012      0x008       0xfff     0x00000002

Example 2

Issuing the command

i2outil /dev/iop1 get_status_buf

generates output that could look like this:

 ............ Printing STATUS BUF .................
Organization ID = 0x0067
HostUnitID = 0x0000
IOP_ID = 000
MessengerType = 0
IopState = 8
I2oVersion = 1
SegmentNumber = 0xfff
InboundMFrameSize = 128 bytes
InitCode = 0x80
MaxInboundMFrames = 256
CurrentInboundMFrames = 128
MaxOutboundMFrames = 256
ExpectedLCTSize = 768
IopCapabilities = 0x00000004
DesiredPrivateMemSize = 0
CurrentPrivateMemSize = 0
CurrentPrivateMemBase = 0x00000000
DesiredPrivateIOSize = 0
CurrentPrivateIOSize = 0
CurrentPrivateIOBase = 0x00000000
SyncByte = 255

Example 3

Issuing the command

i2outil /dev/iop1 get_group1_parms

generates output that could look like this:

Inbound Frame Size = 128
Inbound Size Target = 128
Inbound Frames Max = 256
Inbound Frames Target = 256
Number of Inbound Frames = 128
Frames in Inbound Free List = 0
Frames in Inbound Post List = 0
Static Frame Count = 0
Static Instance Count = 0
Max Static Frames = 0
Static Instance Limit = 0
Outbound Frame Size = 128
Max Outbound Frames = 256
Target Max Outbound Frames = 256
Frames in Outbound Free List = 0
Frames in Outbound Post List = 0
Init Code = 0x80

Example 4

Issuing the command

i2outil /dev/iop1 get_stats

generates output that could look like this:

****************** IOP STATISTICS ********************
------------------------------------------------------
                STATE INFO
                ==========
IOP Driver State = READY
------------------------------------------------------
                MESSAGE SIZE
                ============
IOP Request Message Size = 128
IOP Reply Message Size = 128
------------------------------------------------------
            MESSAGES SENT AND RECEIVED
            ==========================
Pull Messages Sent = 0, Push Messages Sent = 110608
Total Messages Sent = 110608
Total messages received = 110602
------------------------------------------------------
                MISCELLANEOUS INFORMATION
                =========================
Number of Spurious Interrupts = 23
Outbound FIFO empty count = 0

Example 5
Issuing the command
i2outil /dev/iop1 clear_stats
generates output that looks like this:
The statistics was cleared successfully

The Troubleshooting Tools

Technical documentation

» Table of Contents

» Glossary

» Index

The irdiag Command

Examples of irdiag

The irdisplay Command

Example of irdisplay

The i2outil Command

Examples of io2util