Re: HBA Errors




you have dead paths, not a dead HBA.
I suggest you look for the cause outside of the host (fabric errors/etc).




-----Original Message-----
From: IBM AIX Discussion List on behalf of Andrew.Townsend@xxxxxxxxx
Sent: Thu 3/23/2006 3:53 PM
To: aix-l@xxxxxxxxxxxxx
Subject: HBA Errors

We received adapter errors in our error report. They are all FSCSI_ERR4
errors. At this time, it appears that the volume group is still OK, but we
are seeing errors in the errorlog.
I've called IBM and they are coming out to replace the adapter.
Here is what I'm am proposing to do:

1) unmount all filesystems relating to the volume group.
2) vary the volume group offline
3) rmdev -Rdl the fscsi1 device
4) have the IBM CE physically replace the card
5) Make the necessary changes on the fabric switch (due to changes in the
WWN on the card)
6) Make necessary changes on the Shark (due to changes in the WWN on the
card)
7) run cfgmgr
8) import the volume group

What am I missing?

Thanks,

Drew

Here is more information:


[root @ uxsybrpt] /mnt/uxsybproa/exports1 >>datapath query adapter

Active Adapters :2

Adpt# Adapter Name State Mode Select Errors Paths
Active
0 fscsi0 NORMAL ACTIVE 2428630040 0 4
4
1 fscsi1 DEGRAD ACTIVE 2424384374 9 4
2
[root @ uxsybrpt] /mnt/uxsybproa/exports1 >>datapath query device

Total Devices : 2


DEV#: 0 DEVICE NAME: vpath0 TYPE: 2105800 POLICY: Optimized
SERIAL: 20124055
==========================================================================
Path# Adapter/Hard Disk State Mode Select Errors
0 fscsi0/hdisk2 OPEN NORMAL 722935964 0
1 fscsi0/hdisk4 OPEN NORMAL 722887613 0
2 fscsi1/hdisk6 DEAD NORMAL 708340421 5
3 fscsi1/hdisk8 OPEN NORMAL 733551035 0

DEV#: 1 DEVICE NAME: vpath1 TYPE: 2105800 POLICY: Optimized
SERIAL: 30124055
==========================================================================
Path# Adapter/Hard Disk State Mode Select Errors
0 fscsi0/hdisk3 OPEN NORMAL 491317251 0
1 fscsi0/hdisk5 OPEN NORMAL 491489212 0
2 fscsi1/hdisk7 DEAD NORMAL 482384514 4
3 fscsi1/hdisk9 OPEN NORMAL 500108404 0
[root @ uxsybrpt] /mnt/uxsybproa/exports1 >>lsvp -a

Hostname VG vpath hdisk Location LUN SN S
Connection Size LSS Vol Rank
-------- -- ----- ----- -------- ------ -
---------- ---- --- --- ----
uxsybrpt sybrptvg vpath0 hdisk2 11-08-01 20124055 Y
R1-B3-H1-ZA 831.8 12 1 1201
uxsybrpt sybrptvg vpath0 hdisk4 11-08-01 20124055 Y
R1-B1-H1-ZA 831.8 12 1 1201
uxsybrpt sybrptvg vpath0 hdisk6 14-08-01 20124055 Y
R1-B4-H1-ZA 831.8 12 1 1201
uxsybrpt sybrptvg vpath0 hdisk8 14-08-01 20124055 Y
R1-B2-H1-ZA 831.8 12 1 1201

uxsybrpt sybrptvg vpath1 hdisk3 11-08-01 30124055 Y
R1-B3-H1-ZA 831.8 13 1 1301
uxsybrpt sybrptvg vpath1 hdisk5 11-08-01 30124055 Y
R1-B1-H1-ZA 831.8 13 1 1301
uxsybrpt sybrptvg vpath1 hdisk7 14-08-01 30124055 Y
R1-B4-H1-ZA 831.8 13 1 1301
uxsybrpt sybrptvg vpath1 hdisk9 14-08-01 30124055 Y
R1-B2-H1-ZA 831.8 13 1 1301

[root @ uxsybrpt] /mnt/uxsybproa/exports1 >>lsvpcfg
vpath0 (Avail pv sybrptvg) 20124055 = hdisk2 (Avail ) hdisk4 (Avail )
hdisk6 (Avail ) hdisk8 (Avail )
vpath1 (Avail pv sybrptvg) 30124055 = hdisk3 (Avail ) hdisk5 (Avail )
hdisk7 (Avail ) hdisk9 (Avail )
[root @ uxsybrpt] /mnt/uxsybproa/exports1 >>errpt | head
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0323153706 T H fscsi1 ADAPTER ERROR
3074FEB7 0323153706 T H fscsi1 ADAPTER ERROR
3074FEB7 0323153406 T H fscsi1 ADAPTER ERROR
3074FEB7 0323153406 T H fscsi1 ADAPTER ERROR
3074FEB7 0323153106 T H fscsi1 ADAPTER ERROR
3074FEB7 0323153106 T H fscsi1 ADAPTER ERROR
3074FEB7 0323152806 T H fscsi1 ADAPTER ERROR
3074FEB7 0323152806 T H fscsi1 ADAPTER ERROR
3074FEB7 0323152506 T H fscsi1 ADAPTER ERROR
[root @ uxsybrpt] /mnt/uxsybproa/exports1 >>errpt -a | more
---------------------------------------------------------------
LABEL: FSCSI_ERR4
IDENTIFIER: 3074FEB7

Date/Time: Thu Mar 23 15:40:04 EST 2006
Sequence Number: 7233
Machine Id: 0055DF8A4C00
Node Id: uxsybrpt
Class: H
Type: TEMP
Resource Name: fscsi1
Resource Class: driver
Resource Type: efscsi
Location: U0.1-P1-I2/Q1

Description
ADAPTER ERROR

Probable Causes
ADAPTER HARDWARE OR CABLE
ADAPTER MICROCODE
FIBRE CHANNEL SWITCH OR FC-AL HUB

Failure Causes
ADAPTER
CABLES AND CONNECTIONS
DEVICE

Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
CHECK CABLES AND THEIR CONNECTIONS
VERIFY DEVICE CONFIGURATION

Detail Data
SENSE DATA
0000 0000 0000 00A1 0000 0013 0200 0000 0000 0000 0000 0000 0000 0000 0000
0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0065 0216 0000
0000
0065 0205 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000
0000 0000 C00F 0000 2512 0002 0000 0000 0000 0000 0001 0000 0000 0000 0000
0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0002 5005
0763
00D0 9B8F 5005 0763 00C0 9B8F 0200 0000 0000 0000 0000 0000 0000 0000 0000
0000
217F 0000



Relevant Pages

  • Re: HBA Errors
    ... then rerun cfgmgr 2x ... the adapter. ... Make the necessary changes on the fabric switch ... CHECK CABLES AND THEIR CONNECTIONS ...
    (AIX-L)
  • Re: HBA Errors
    ... the adapter. ... Make the necessary changes on the fabric switch ... Resource Class: driver ... CHECK CABLES AND THEIR CONNECTIONS ...
    (AIX-L)
  • HBA Errors
    ... I've called IBM and they are coming out to replace the adapter. ... Make the necessary changes on the fabric switch (due to changes in the ... Resource Class: driver ... CHECK CABLES AND THEIR CONNECTIONS ...
    (AIX-L)