SCSI Reset

[PJSC]

Dear All,
Recently a SCSI resetting always occurs in a ds 2300 disk array at 11:00 everyday.HP has replaced the disk,SCSI cable,SCSI card and BCC.However the issue has been not resolved.Would you please help me to analyse it and how to deal with it? Also I want to know how it will fluence the server and what is the critical level.If can we ignore it?
Thanks in advance.
Below is the detalis.
Notification Time: Mon Dec 11 11:31:06 2006

www sent Event Monitor notification information:

/storage/events/disks/default/0_3_1_0.6.0 is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Mon Dec 11 11:31:06 2006
Severity............: INFORMATION
Monitor.............: disk_em
Event #.............: 100401
System..............: pjscdb2.jil.sc.philips.com

Summary:
Disk at hardware path 0/3/1/0.6.0 : Successful completion of operation


Description of Error:

The device driver has successfully completed an I/O request.

Probable Cause / Recommended Action:

No action is necessary.

Additional Event Data:
System IP Address...: 161.92.151.11
Event Id............: 0x457cd0fa00000004
Monitor Version.....: B.01.01
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):
0x457cd0f90000000a
Additional System Data:
System Model Number.............: 9000/800/rp3440
OS Version......................: B.11.11
STM Version.....................: A.43.00
EMS Version.....................: A.04.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100401

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...: 0/3/1/0.6.0
Device Class...........: Disk
Inquiry Vendor ID......: HP 36.4G
Inquiry Product ID.....: ST336753LC
Firmware Version.......: HPC5
Serial Number..........: 3HX2BF1J00007444847E

Product/Device Identification Information:

Logger ID.........: sdisk
Product Identifier: SCSI Disk
Product Qualifier.: HP36.4GST336753LC
SCSI Target ID....: 0x06
SCSI LUN..........: 0x00

I/O Log Event Data:

Driver Status Code..................: 0x00000000
Length of Logged Hardware Status....: 4 bytes.
Offset to Logged Manager Information: 8 bytes.
Length of Logged Manager Information: 34 bytes.

Hardware Status:

Raw H/W Status:
0x0000: 00 00 00 00

SCSI Status...: GOOD (0x00)
Indicates that the target has successfully completed the command.

SCSI Sense Data: (not present in log record)

SCSI Command Data Block:

Command Data Block Contents:
0x0000: 2A 00 00 05 65 F0 00 00 08 00

Command Data Block Fields (10-byte fmt):
Command Operation Code...(0x2A)..: WRITE
Logical Unit Number..............: 0
DPO Bit..........................: 0
FUA Bit..........................: 0
Relative Address Bit.............: 0
Logical Block Address............: 353776 (0x000565F0)
Transfer Length..................: 8 (0x0008)

Manager-Specific Data Fields:
Request ID.............: 0x0443FB1F
Data Residue...........: 0x00000000
CDB status.............: 0x00000000
Sense Status...........: 0x00000000
Bus ID.................: 0x04
Target ID..............: 0x06
LUN ID.................: 0x00
Sense Data Length......: 0x00
Q Tag..................: 0x7D
Retry Count............: 1

[Sameer_Nirmal]

The Event monitor information you posted is "Informal" and is associated with Event ID "0x457cd0f90000000a". Thus posting the event monitor information of event ID "0x457cd0f90000000a" would be the information to be looked for the cause.

As you said and per the event information, it looks like (assuming the SCSI reset is being reported for the disk only), the SCSI reset is being occured on the bus and then the IO to the disk is reported as completed after an interval.

[Patrick Wallek]

Since the initial SCSI reset, have you reset EMS so all devices are in a normal status?

Try this:

# /etc/opt/resmon/lbin/set_fixed -n \*

This will reset the status of all devices in EMS to good.

Now if you continue to get failures, you should continue to bug HP. That's why you pay support.

[Andrew Merritt_2]

Don't bother with the 'set_fixed', that is not relevant to this and won't do anything useful.

Do you also get a 100091 or other event preceding the 100401?

Do you just get the EMS event, or do you also get something logged in syslog.log? What about in logtool in STM, any SCSI errors there?

The 100401 is just an informational level event, which I think just follows a timeout, saying things are working OK now. On its own, it can be ignored, but it might be suggesting some sort of intermittent problem. The fact that it's the same time every day suggests either that some other application is running every day, or that it's a result of the monitor itself (disk_em) accessing the disk at that time (it checks every 15 minutes, but most events are suppressed for 24 hours once they have happened one time).

I would recommend upgrading to a current version of the OnlineDiags, you have A.43.00, which is 3 years old. The current version is A.53.00. http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE
There are a number of fixes since the A.43.00 version, but I don't recall any specifically for this, since the device in question is a physical disk, I believe. You should also check device drivers are current.

If you're still seeing this after upgrading the OnlineDiags, and drivers if necessary, I agree, keep bugging HP support to get to the bottom of this.

Andrew