Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

msa2012fc - attached to rx3600 running hp-ux 11.23

james gould
Frequent Advisor

msa2012fc - attached to rx3600 running hp-ux 11.23

Have a msa2012fc array. Created a vdisk on the array and when finished got the following error

Event Monitor notification information:
/adapters/events/ql_adapter/0_7_1_0_4_0 is >= 3.

Its current value is CRITICAL(5).

Event data from monitor:

Event Time..........: Thu Jul 29 14:26:59 2010

Severity............: CRITICAL

Monitor.............: dm_ql_adapter

Event #.............: 57
Summary:

Adapter at hardware path 0/7/1/0/4/0 : Private loop device didn't acquire

the hard address.
Description of Error:
lbolt value: 9711773
Private loop device didn't acquire the hard address:

Hard Address is 0x0 but acquired AL_PA is 0xef.



Probable Cause / Recommended Action:



In private loop topology, we require device to set hard address,

and to acquire its Hard address during loop initialization.

Driver has detected that a private loop device didn't acquire

its hard address.
It might be due to multiple devices in the loop with the
same hard address setting. Look for all the devices which has the

reported hard address. Change their hard address settings so that

they have a unique hard address.



NOTE:

1. Please change hard address setting for the newly added

devices, so that old device can keep its hard address.

2. After you change the hard address settings on the devices,
it may be necessary to reset or power-cycle all the devices

which used to have the same hard address setting.

EXAMPLE: You see this diagnostic message and find three

devices with address setting 0x05. You change one device

to address 0x06 and another to 0x07. You now may need to

reset or power-cycle ALL THREE devices.





Additional Event Data:

System IP Address...: 10.9.3.138

Event Id............: 0x4c51c7f300000003

Monitor Version.....: B.02.00

Event Class.........: I/O

Client Configuration File...........:

/var/stm/config/tools/monitor/default_dm_ql_adapter.clcfg

Client Configuration File Version...: A.04.00

Qualification criteria met.

Number of events..: 1

Associated OS error log entry id(s):

0x4c51c7f300000001

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_ql_adapter.htm#57



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/7/1/0/4/0
I/O Log Event Data:

Driver Status Code..................: 0x00000039

Length of Logged Hardware Status....: 0 bytes.

Offset to Logged Manager Information: 0 bytes.

Length of Logged Manager Information: 70 bytes.
Manager-Specific Information:
Raw data from FCMS Adapter driver:

00000001 0094309D 00000002 00000001 00000000 000000EF 2F75782F 636F7265

2F697375 2F464344 2F6B6572 6E2F7372 632F636F 6D6D6F6E 2F777369 6F2F6663

645F646D 2E63