General
cancel
Showing results for 
Search instead for 
Did you mean: 

Recommendations on a EMS dm_sas_adapter event

Doug_3
Frequent Advisor

Recommendations on a EMS dm_sas_adapter event

Hi there,
One time event with no obvious cause. Looking for ideas on other areas to look at. RX3600 with 2 MSA60's in a raid 10 configuration. This has been working quite well for 10 months. Last night EMS broadcast a fault on the SAS adapter on hw path 0.4.1.0 with is the primary path to the array.
xstm and syslog and sasmgr didn't show me anything useful. Ideas or recommendations?
Thanks in advance, Doug

/adapters/events/sas_adapter/0_4_1_0 is >= 3.
Its current value is CRITICAL(5).
Event data from monitor:
Event Time..........: Tue Apr 21 21:41:05 2009
Severity............: CRITICAL
Monitor.............: dm_sas_adapter
Event #.............: 33
System..............:
Summary:
Adapter at hardware path 0/4/1/0 : Task Management function to SAS port
failed.
Description of Error:
lbolt value: 1053534915
TM (0x00000002) to SAS address 0x04e87852c477f76a (dev_t 0x1f040002) failed
with CDB status 0x00000400
Probable Cause / Recommended Action:
Task Management function to SAS port failed.
Please check the following:
1) Verify that the device is powered on and is accepting other commands.
2) If the device is accepting other commands, check device internal logs.
Additional Event Data:
System IP Address...: 10.1.0.16
Event Id............: 0x49ee9fe100000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_sas_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x49ee9fe100000000
Additional System Data:
System Model Number.............: ia64 hp server rx3600
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.60.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_sas_adapter.htm#33
I/O Log Event Data:
Driver Status Code..................: 0x00000021
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 169 bytes.

Manager-Specific Information:

Raw data from SAS MPT SCSI Adapter driver:
01000000 3ECBAAC3 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 544D2028 30783030 30303030 30322920 746F2053 41532061 64647265
73732030 78303465 38373835 32633437 37663736 61202864 65765F74 20307831
66303430 30303229 20666169 6C656420 77697468 20434442 20737461 74757320
30783030 30303034 30
5 REPLIES
Viktor Balogh
Honored Contributor

Re: Recommendations on a EMS dm_sas_adapter event

if you have a contract with HP then I'd suggest you to open a case
****
Unix operates with beer.
Torsten.
Acclaimed Contributor

Re: Recommendations on a EMS dm_sas_adapter event

0/4/1/0 is the path to the internal disks via the built-in sas controller - check them with sasmgr:

# saslist get_info ctrl sasd

# saslist get_info lun sasd

# sasmgr get_info -D /dev/sasd0 -q phy=all

# sasmgr get_info -D /dev/sasd0 -q raid

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor

Re: Recommendations on a EMS dm_sas_adapter event

Event 33

Severity: Major Warning

Description: The device at the specified SAS address is not valid.

Possible Cause: The device at the specified SAS address is not valid.
Recommended Action: If the SAS address is for a valid device, verify all connections to the device. Also verify that the device is operational.



Could be a bad or almost bad disk.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Doug_3
Frequent Advisor

Re: Recommendations on a EMS dm_sas_adapter event

Interesting.
I was on the track of Adapter-controller. It also could be the EMS side. One posting from prior date has a known issue in 2007 for EMS to OS to Hardware. Recommended upgrade of EMS. Our machine is 2009 and versions appear OK. So still guessing.

Since it was a one time event, I am not too worried, esp since it is a raid 10 config on 2 msa60's with 2 paths etc.

Thanks for posting everyone.
Torsten.
Acclaimed Contributor

Re: Recommendations on a EMS dm_sas_adapter event

"I am not too worried, esp since it is a raid 10 config on 2 msa60's with 2 paths etc."

But it points to your internal disks, not to the MSA!

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!