Disk Enclosures
cancel
Showing results for 
Search instead for 
Did you mean: 

logprn about va7400, and users said the response time was slow.

stephen peng
Valued Contributor

logprn about va7400, and users said the response time was slow.

dear all,
i post my problem in the category of system administrator, but not that many reply to help me to solve the problem yet, it is urgent for me to deal with that problem, so i post here for more helps. thanks all.

stephen peng
Nov 28, 2005 08:31:47 GMT

--------------------------------------------------------------------------------
dear all,
i get following messages for logprn of a va7400, and it repeats every 4 or 5 minutes, and users said that the response time of some regular command, like bdf, was a little bit slow. the fact was that one disk of one enclosure had been failed, was it the main cause of those messages' producing?

Device Unique Name = 50060B0000092645
Device Name = HP StorageWorks Virtual Array 7400
Date = November 28, 2005
Time = 3:01:28 PM GMT+08:00
Controller Time Stamp = 24977853093517
Event Number = 123996
Sequence Number = 6895
Event Type = Controller Event
Event Code = 348
Severity = 1
Event Count = 1
FRU Location = M/C2.H1
FRU Data = enclosureId/slot/component/subcomponent : 0x00/0x01/0x70/0xff
Reporting Controller = M/C2
Event Source Info = serialNum/moduleId/processId : 00PR05B50369/0x47/0xffffffff
Event Description = FRONTEND_FC_ABTS_EVENT_EH This error code indicates that the Host sent a Fibre Channel ABTS (Abort Sequence) BLS frame to the abort an IO. The array will log this event for informational and debug purposes only. It does not necessarily indicate a problem with the array.
Event Unique Info = 0x470097: 0x0004
frontend: osIOCompleted: osIOAbortABTS
NPortID=0x020300,OXID=0x0092,LUN=0x400b
CDB=0x2a080245b80000020000000000000000
et=30.2 qd=4 hwm=56 jl=0x00040000 dl=0x00040000 ro=0x00040000 js=2.

thanks a lot.




Sort Answers By: Date or Points


Luk Vandenbussche Nov 28, 2005 09:29:58 GMT 5 pts

--------------------------------------------------------------------------------
Hi,

Check this threads

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=128865&admit=-682735245+1133170010154+28353475

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=883812&admit=-682735245+1133170151650+28353475

Updating patches en VA firmware is advisable

stephen peng Nov 29, 2005 01:47:44 GMT N/A: Question Author

--------------------------------------------------------------------------------
Luk,
thank you for your reply,i read those threads and i think they met our problem, but i still don't know how to deal with it. do i need to update which patches? do i need to upgrad the firmware to HP14? and how about the "HighPerformance" mode? do i need to configure it? how i can do all these job? could you please offer me some hints or present me some document? thanks a lot.

i read the syslog.log and find some messages like this:
Nov 28 16:29:29 fsjf vmunix: SCSI: Read error -- dev: b 31 0x0a1500, errno: 126, resid: 2048,
Nov 28 16:29:29 fsjf vmunix: blkno: 8, sectno: 16, offset: 8192, bcount: 2048.
Nov 28 16:29:29 fsjf vmunix: LVM: vg[5]: pvnum=0 (dev_t=0x1f0c1500) is POWERFAILED
Nov 28 16:29:42 fsjf vmunix: LVM: Recovered Path (device 0x1f0a1500) to PV 0 in VG 5.
Nov 28 16:29:42 fsjf vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000005e856080), from raw device 0x1f0c1500 (with priority: 1, and current flags: 0xc0) to raw device 0x1f0a1500 (with priority: 0, and current flags: 0x80).
Nov 28 16:29:42 fsjf vmunix: LVM: Recovered Path (device 0x1f0c1500) to PV 0 in VG 5.
Nov 28 16:29:43 fsjf vmunix: LVM: Restored PV 0 to VG 5.
Nov 28 16:29:29 fsjf vmunix: LVM: vg[5]: pvnum=0 (dev_t=0x1f0c1500) is POWERFAILED
Nov 28 16:31:03 fsjf vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000005e856080), from raw device 0x1f0a1500 (with priority: 0, and current flags: 0x40) to raw device 0x1f0c1500 (with priority: 1, and current flags: 0x0).
Nov 28 16:31:03 fsjf vmunix:
Nov 28 16:31:03 fsjf vmunix: SCSI: Read error -- dev: b 31 0x0a1500, errno: 126, resid: 2048,
Nov 28 16:31:03 fsjf vmunix: blkno: 8, sectno: 16, offset: 8192, bcount: 2048.
Nov 28 16:31:03 fsjf vmunix: LVM: vg[5]: pvnum=0 (dev_t=0x1f0c1500) is POWERFAILED
Nov 28 16:31:08 fsjf vmunix: LVM: Recovered Path (device 0x1f0a1500) to PV 0 in VG 5.
Nov 28 16:31:08 fsjf vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000005e856080), from raw device 0x1f0c1500 (with priority: 1, and current flags: 0xc0) to raw device 0x1f0a1500 (with priority: 0, and current flags: 0x80).
Nov 28 16:31:08 fsjf vmunix: LVM: Recovered Path (device 0x1f0c1500) to PV 0 in VG 5.
Nov 28 16:31:03 fsjf vmunix: LVM: vg[5]: pvnum=0 (dev_t=0x1f0c1500) is POWERFAILED
Nov 28 16:31:08 fsjf vmunix: LVM: Restored PV 0 to VG 5.
so i think your thread meet our problem.

stephen peng Nov 29, 2005 02:08:00 GMT N/A: Question Author

--------------------------------------------------------------------------------
beside, from the armdsp -a's output i read some messages:
Array Status:_________________________Warning
Firmware Revision:_______________38370HP20P1007041848
Product Revision:_____________________HP20
Last Event Log Entry for Page 1:______124018

did they say that the firmware version of va7400 is HP20?

thanks a lot.



stephen
3 REPLIES
Luk Vandenbussche
Honored Contributor

Re: logprn about va7400, and users said the response time was slow.

Stephen,

You have scsi errors on your disks.
Are all the leds on the VA7400 are ok.

It seems that you have serious problems.
Is the VA covered by an HP support contract?
stephen peng
Valued Contributor

Re: logprn about va7400, and users said the response time was slow.

Luk,
thank you for your reply.
all the leds of the array are ok, maybe the failed disk led to that problem i though, and io requests on the filesystem which created on the disk group where the failed disk belong to were just serious, and the io average wait number are high.
unfortunately, the array is not covered by HP contract.

stephen
Luk Vandenbussche
Honored Contributor

Re: logprn about va7400, and users said the response time was slow.