This is af SAN Path error : What to do!!!

[Jannik Tonsberg_2]

/opt/resmon/bin/resdata -R 243597572 -r /storage/events/disks/default/1_0_12_0_0.1.22.0.0.15.0 -n 243597828 -a

CURRENT MONITOR DATA:

Event Time..........: Sun May 16 01:15:27 2004
Severity............: SERIOUS
Monitor.............: disk_em
Event #.............: 100876
System..............: tm011.ejb.telia.dk

Summary:
Disk at hardware path 1/0/12/0/0.1.22.0.0.15.0 : Software configuration
error


Description of Error:

The device was unsuccessful in processing the current I/O request because
the request contained a logical unit number, which is not supported for
this device. The request was not processed.

Probable Cause / Recommended Action:

The error most likely indicates that the device is not fully supported by
the current driver. This may or may not cause a problem in the operation
of the device.

Additional Event Data:
System IP Address...: 131.116.105.94
Event Id............: 0x40a6a48f00000002
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/S16K-A
OS Version......................: B.11.11
STM Version.....................: A.30.00
EMS Version.....................: A.04.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100876

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Physical Device Path...: 1/0/12/0/0.1.22.0.0.15.0
Device Class...........: Disk
Inquiry Vendor ID......: HITACHI
Inquiry Product ID.....: DISK-SUBSYSTEM
Firmware Version.......: 2101
Serial Number..........: 63580

Product/Device Identification Information:

Logger ID.........: disc30; sdisk
Product Identifier: Disk
Product Qualifier.: HITACHI DISK-SUBSYSTEM
SCSI Target ID....: 0x0F
SCSI LUN..........: 0x00

SCSI Command Data Block:

Command Data Block Contents:
0x0000: 00 00 00 00 00 00

Command Data Block Fields (6-byte fmt):
Command Operation Code...(0x00)..: TEST UNIT READY
Logical Unit Number..............: 0

Hardware Status: (not present in log record).

SCSI Sense Data:

Undecoded Sense Data:
0x0000: 70 00 05 00 00 00 00 58 00 00 00 00 25 00 00 00
0x0010: 00 00 00 80 D0 50 00 00 00 00 01 01 00 78 00 2F
0x0020: 00 00 00 00 00 00 00 00 00 00 B0 00 00 00 01 24
0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCSI Sense Data Fields:
Error Code : 0x70
Segment Number : 0x00
Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x05
Information Field Valid : FALSE
Information Field : 0x00000000
Additional Sense Length : 88
Command Specific : 0x00000000
Additional Sense Code : 0x25
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00

Sense Key 0x05, ILLEGAL REQUEST, indicates that there was an illegal
parameter in the command data block or in the additional parameters
supplied as data for some commands (FORMAT UNIT, SEARCH DATA, etc.).
This sense key may also indicate that an invalid IDENTIFY message was
received.

The combination of Additional Sense Code and Sense Qualifier (0x2500)
indicates: Logical unit not supported.

[Victor BERRIDGE · Accepted solution]

Hi,
I would check if all HDS recommendations are followed (I/O timeout and queue depth), give them a call and ask them "is it bad news Doctor?"
More seriously as the message says it can or not mean "serious problem" because of not fully supported driver... understand EMS/diagmond does not know much about the driver... So its more up to you to follow and see for yourself...
Ive been living with these messages for almost 6 years now and dont pay any more attention (well some time I do check just to find some recomfort - Nothing has changed...). You may notice when they appear Is it at backup time /export of database? then for me its normal I believe the throughput (bandwidth) is what alarmes the system but it peanuts compared to what HDS can support...
I have these messages on HDS5750/5740 series with SCSI connections and HDS9980 with FC...

My advice is get to learn what you can call acceptable times for such messages (big load) you then have only to check for unexplained situations
Just for informations usually set queue depth at 2 and timeout normally between 60-90 sec. in some cases (config with big filesystems) 180 sec. (with HP aggreeing to support). I woulnd exceed more than 240sec (Its far from HDS standarts)

Good luck

All the best

Victor

[Leon Allen]

I get these messages as well from my san (using seagate cheetah FC disks)

I haven't understood them, but found them to be of little consequence.

would performance be better without them??

[Victor BERRIDGE]

Hi again,
I forgot to mention I noticed a relationship between these alerts and the file cahe buffer size, I had less alerts when the cache was under 500 MB.
I also noticed that after patching the HDS(starting with the patch that removes the 8 LUN limit) some time ago (1-2 years ? cant remember exactly) and I may had also patches for the system to apply for the tachyon HBAs
most (all?) of this type of (unsignificant) alerts stopped (I noticed since on HDS 9980)
On the SAN side we upgraded from a HDS 9960 to HDS 9980. So its difficult for me to remember when or to say what ceased the alert to occur
So I still have these alerts on boxes scsi connected to HDS 57XX and 58XX

If you want I investigate more, I will have a look when I can spare some time

All the best

Victor

[Jannik Tonsberg_2]

My configuration is:
- HDS 9980
- rp8400 x3 (only one have the problem)
- OS HPUX11i
- patch level highst
- Switch 3900 has just been firmeware opgraded by HDS.

It is nice to know that others have the same problem. What I'm thinking is to lock a call at HP. Even if it is not a critical error.
As it is right now the machines are not very loaded. But they will be in the future!

[Victor BERRIDGE]

Hi again,
I was wondering:
Since only one system is affected, its not patch problem on HDS side. Are the 3 boxes identically installed (patches/firmware etc...)?
Were they all 3 on the same brocade switch before its upgrade?
I remembered seeing strange alerts when changing configuration on boxes (migration 9960 to 9980 or changing switches or HBAs) mostly forgotten disks when cleaning up before migrating (they were left when should have been removed (vgexport/vgimport)specially when you have MCSG...

Double check your disk configuration with ioscan then check all the vg: vgdisplay -v ¦grep dsk
and compare with your ioscan -funC disk
output
Is there a mismatch somewhere?

All the best
Victo

[Victor BERRIDGE]

Hi again,
I was wondering:
Since only one system is affected, its not patch problem on HDS side. Are the 3 boxes identically installed (patches/firmware etc...)?
Were they all 3 on the same brocade switch before its upgrade?
I remembered seeing strange alerts when changing configuration on boxes (migration 9960 to 9980 or changing switches or HBAs) mostly forgotten disks when cleaning up before migrating (they were left when should have been removed (vgexport/vgimport)specially when you have MCSG...

Double check your disk configuration with ioscan then check all the vg: vgdisplay -v ¦grep dsk
and compare with your ioscan -funC disk
output
Is there a mismatch somewhere?

All the best
Victo

[Ted Buis]

I don't think you can use EMS with non-HP disk arrays. Stop EMS and disable it.