Video Screencast Help

need a solution

Created: 01 May 2013 | 4 comments

 

 

we have 2 node cluster and with version 5.1

we experienced outage and  I think it was due to below error messages

can someone shed some light on these messages

 qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop OFFLINE
qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop ONLINE
 fctl: [ID 999315 kern.warning] WARNING: fctl(4): AL_PA=0xe8 doesn't exist in LILP map

 scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875f9d9,0 (ssd3):
    Command failed to complete...Device is gone
 scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875f9d9,0 (ssd3):
    Command failed to complete...Device is gone
 scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875f9d9,0 (ssd3):
    Command failed to complete...Device is gone
 scsi: [ID 243001 kern.info] /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fcp4):
    offlining lun=0 (trace=0), target=e8 (trace=2800004)
 vxdmp: [ID 631182 kern.notice] NOTICE: VxVM vxdmp V-5-0-0 removed disk array 600A0B800075F9D9000000004D2334F5, datype = ST2540-
vxdmp: [ID 443116 kern.notice] NOTICE: VxVM vxdmp V-5-0-0 i/o error occured (errno=0x6) on dmpnode 334/0x2c
 last message repeated 59 times
 vxdmp: [ID 480808 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 118/0x18 belonging to the dmpnode 334/0x28 due to open failure
 vxdmp: [ID 824220 kern.notice] NOTICE: VxVM vxdmp V-5-0-111 disabled dmpnode 334/0x28

 

what is this dmpnode 334/0x28 signify, I forget how to map this to device as i only remember is tht its in hexadecimal.

 

Also, what could be the cause of it ...

 

is it due to HBA as issue starts with the  message like below

 

 qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop OFFLINE
qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop ONLINE
 fctl: [ID 999315 kern.warning] WARNING: fctl(4): AL_PA=0xe8 doesn't exist in LILP map

 

Operating Systems:

Comments 4 CommentsJump to latest comment

rsharma1's picture

Yes, looks like a fault with hba port:

download.oracle.com/docs/cd/E19957-01/816-0252-10/816-0252-10.pdf (diagnosis on pages 67-71 might be relevant to your issue)

stinsong's picture

Hi symsonu,

This problem is caused by HBA fault.

And to match the device number into device file, check the output of ls -l /dev/vx/dmp/*. You will see the major/minor number of each dmp device. The HEX number reported by message is the major/minor number of dmp device. So you can match it into dmp device file. smiley

Gaurav Sangamnerkar's picture

DMP nodes are marked in hexadecimal numbers in the error log .. if you look at /dev/vx/rdmp using ls -l , you can see all major minor numbers .

for your question about conversion of hex code .. use calculator on your laptop ..

for e.g  0x28 in hex converts to 40 (0x will be 0 & 20 converts to 40)  in decimal .. so you can find a device with 334,40 in the list ...

 

G

 

 

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

mikebounds's picture

You can convert from hex to decimal using bash shell too, which is the default shell on most systems these days: 

$ echo $((0x28))
40
Mike

 

 

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below