HP-UX Syslog Message

[periyasamy]

Hi

I am workingin HP-UX(11iv2) MC/SG Cluster with EVA 4000 storage.In my hp-ux server from the syslog I am getting the following messages frequently related to the LUNS,Autopath and lvm .So what will be the solution to avoid any inicident due to that message.If anybody aware of the, Pls hel me.


Find the syslog.log file as attachement of this forum.Please view with wordbad.


In /var/adm/syslog/syslog.log
ec 23 01:32:59 ghiaadb1 vmunix:
Dec 23 01:32:59 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 failed! Rerouting to alternate path
Dec 23 01:33:08 ghiaadb1 vmunix: LVM: VG 64 0x020000: PVLink 31 0x140400 Failed! The PV is not accessible.
Dec 23 01:33:08 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 recovered
Dec 23 01:33:08 ghiaadb1 vmunix: LVM: VG 64 0x020000: PVLink 31 0x140400 Recovered.
Dec 23 01:33:09 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 failed! Rerouting to alternate path
Dec 23 01:33:14 ghiaadb1 vmunix: SCSI: Async write error -- dev: b 31 0x140400, errno: 126, resid: 32768,
Dec 23 01:33:14 ghiaadb1 vmunix: blkno: 38501824, sectno: 77003648, offset: 39425867776, bcount: 32768.
Dec 23 01:33:14 ghiaadb1 vmunix: SCSI: Async write error -- dev: b 31 0x140400, errno: 126, resid: 49152,
Dec 23 01:33:14 ghiaadb1 vmunix: blkno: 38502352, sectno: 77004704, offset: 39426408448, bcount: 49152.
Dec 23 01:33:14 ghiaadb1 vmunix: SCSI: Async write error -- dev: b 31 0x140400, errno: 126, resid: 16384,
temp (85%)

Dec 26 21:37:37 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 recovered
Dec 26 21:38:06 ghiaadb1 vmunix:
Dec 26 21:38:06 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 failed! Rerouting to alternate path
Dec 26 21:38:06 ghiaadb1 vmunix: LVM: Failed to automatically resync PV 1f140400 error: 5
Dec 26 21:38:10 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 recovered
Dec 26 21:38:16 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 failed! Rerouting to alternate path
Dec 26 21:38:20 ghiaadb1 vmunix:
Dec 26 21:38:20 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 recovered
Dec 26 21:51:23 ghiaadb1 vmunix: 0/4/1/0/4/0: Device at device id 0x11400 has disappeared from Name Server GPN_FT
Dec 26 21:51:23 ghiaadb1 vmunix: (FCP type) response, or its 'Port World-Wide Name' has changed.
Dec 26 21:51:23 ghiaadb1 vmunix: device id = loop id, for private loop devices
Dec 26 21:51:23 ghiaadb1 vmunix: device id = nport ID, for fabric/public-loop devices
Dec 26 21:51:23 ghiaadb1 vmunix: System won't be able to see LUNs behind this port.
Dec 26 21:51:23 ghiaadb1 vmunix:
Dec 26 21:51:24 ghiaadb1 vmunix: 0/3/1/0/4/0: Device at device id 0x21400 has disappeared from Name Server GPN_FT
Dec 26 21:51:24 ghiaadb1 vmunix: (FCP type) response, or its 'Port World-Wide Name' has changed.
Dec 26 21:51:24 ghiaadb1 vmunix: device id = loop id, for private loop devices
Dec 26 21:51:24 ghiaadb1 vmunix: device id = nport ID, for fabric/public-loop devices
Dec 26 21:51:24 ghiaadb1 vmunix: System won't be able to see LUNs behind this port.
Dec 26 21:51:24 ghiaadb1 vmunix:
Dec 26 21:53:05 ghiaadb1 vmunix: 0/4/1/0/4/0: Device at device id 0x11400 is back in Name Server GPN_FT (FCP type)
Dec 26 21:53:05 ghiaadb1 vmunix: response, and its 'Port World-Wide Name' remains the same as
Dec 26 21:53:05 ghiaadb1 vmunix: original.
Dec 26 21:53:05 ghiaadb1 vmunix: device id = loop id, for private loop devices
Dec 26 21:53:05 ghiaadb1 vmunix: device id = nport ID, for fabric/public-loop devices
Dec 26 21:53:05 ghiaadb1 vmunix: System will be able to see LUNs behind this port
Dec 26 21:53:05 ghiaadb1 vmunix: (might need to run 'ioscan' first).
Dec 26 21:53:05 ghiaadb1 vmunix:
Dec 26 21:53:08 ghiaadb1 vmunix: 0/3/1/0/4/0: Device at device id 0x21400 is back in Name Server GPN_FT (FCP type)
Dec 26 21:53:08 ghiaadb1 vmunix: response, and its 'Port World-Wide Name' remains the same as
Dec 26 21:53:08 ghiaadb1 vmunix: original.
Dec 26 21:53:08 ghiaadb1 vmunix: device id = loop id, for private loop devices
Dec 26 21:53:08 ghiaadb1 vmunix: device id = nport ID, for fabric/public-loop devices
Dec 26 21:53:08 ghiaadb1 vmunix: System will be able to see LUNs behind this port
Dec 26 21:53:08 ghiaadb1 vmunix: (might need to run 'ioscan' first).
Dec 26 21:53:08 ghiaadb1 vmunix:
Dec 26 22:13:04 ghiaadb1 vmunix:
Dec 26 22:13:04 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 failed! Rerouting to alternate path
Dec 26 22:13:13 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 recovered
Dec 26 22:13:13 ghiaadb1 vmunix:
Dec 26 22:17:53 ghiaadb1 vmunix:
Dec 26 22:17:53 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 failed! Rerouting to alternate path
Dec 26 22:17:53 ghiaadb1 vmunix: LVM: VG 64 0x020000: PVLink 31 0x140400 Failed! The PV is not accessible.
Dec 26 22:17:53 ghiaadb1 vmunix: LVM: VG 64 0x020000: PVLink 31 0x140400 Recovered.
Dec 26 22:17:55 ghiaadb1 vmunix: AUTOPATH : Path 0xbc140400 recovered
Dec 26 22:17:55 ghiaadb1 vmunix:
temp (94%)

[Johnson Punniyalingam]

Hi ,

Looking at the post, asume that you failed disk and it has been recovered, this could be some Controller Intermediate Problem,

ioscan -fnC disk --> Can you see all your disk claimed ..?

ioscan -fnH 0/3/1/0 --> does it show's claimed..?

how about EVA 4000 storage Health check..?


Thanks,
Johnson

[F Verschuren]

When you ad a lun to your system your eva server is giving a hickup (we had it also some years a go, ho I remember there is no fix for it, but is can not harm (as long the failed links are recovered whitin a few seconds.

[Avinash20 · Accepted solution]

Please log a call with Solution Center in case you are having support

[sujit kumar singh]

hi


these are the auopath message for the Path 0xbc140400 that is the disk device path for the disk 140400 as minor no.


just can see this from the /dev/dsk/*

#ll /dev/dsk/* | grep 140400

and see which disk ia that .

do a pvdisplay on that to know what VG that belong to :

#pvdislay -v /dev/dsk/cxtydz

knowing the VG name try doing vgdisplay -v to know for the alternate links of that PV

#vgdosplay -v vgXY

this can be a simple path prob that is FC connected in that path prob ..

but these are not that worrisome as a path is recovering also assume that u are using securepath for act/act disk arrays (hope so)

u can howver log a case right...


Regards
Sujit