San errors

balaji_vvv — Tue, 01 Dec 2009 15:18:01 GMT

I have seen this errors on syslog after rebooting the machine today.
Everything looks fine (Green and all available disk. The server is connected to virtual array via fiber channel switch (2 path). Can anyone help me is somethig to worry about?

Dec 1 09:00:00 xxx syslog: CVSDM; INFORMATION Event Code=400; Description=542:BACKEND_LINK_DOWN_EH A disk interface has been down for longer than the time allowed for normal recovery. Array function will continue without use of this channel. This can be caused by a bad connection to disks (internal orexternal), or by a failind disk or controller.; Ckpt 0x16016d: 0x00000002 ctlr 0 loop 1; backend: Link Inactive, abort init; enclosureId/slot/component/subcomponent : 0x00/0x00/0x81/0xff; controller tick : 37146783778843; serialNum/moduleId/processId : 00PR02C51244/0x16/0xffffffff; ; Hardware Address=0/5/2/0.1.7.43.0.0.0; FRU Location=M/C1.J2; Vendor ID=HP; Model ID=A6218A; Product S/N=00USE00003P7; Latest information on this event at http://docs.hp.com/hpux/content/hardware/ems/RemoteMonitor.htm#400
Dec 1 09:00:01 xxx syslog: CVSDM; INFORMATION Event Code=400; Description=542:BACKEND_LINK_DOWN_EH A disk interface has been down for longer than the time allowed for normal recovery. Array function will continue without use of this channel. This can be caused by a bad connection to disks (internal orexternal), or by a failind disk or controller.; Ckpt 0x16016d: 0x00000002 ctlr 1 loop 1; backend: Link Inactive, abort init; enclosureId/slot/component/subcomponent : 0x00/0x01/0x81/0xff; controller tick : 37146784600947; serialNum/moduleId/processId : 00PR02C51246/0x16/0xffffffff; ; Hardware Address=0/5/2/0.1.7.43.0.0.0; FRU Location=M/C2.J2; Vendor ID=HP; Model ID=A6218A; Product S/N=00USE00003P7; Latest information on this event at http://docs.hp.com/hpux/content/hardware/ems/RemoteMonitor.htm#400

Re: San errors

Rita C Workman — Tue, 01 Dec 2009 15:33:13 GMT

I don't know your environment, but for me:

The error seems to be saying...you have a link down. Your up because you have two paths and one is still fine.

It tells you backend_link_down.

Check your physical HBA's and confirm that everything is connected and live.

I'm no virtual array person, but if your physical fiber is solid, then check your virtual setup.

[Something to worry about?] Something that needs addressed, and if the other path goes down...then you will surely be worrying.

Regards,
Rita

Re: San errors

balaji_vvv — Tue, 01 Dec 2009 16:23:40 GMT

Thanks. I didnt see any link down or any kind of alert when i see at the back of server or array or switch. I will open a case with hp.

Re: San errors

Torsten. — Tue, 01 Dec 2009 21:26:01 GMT

Must be a VA74xx.

M/C2.J2

This is the connection to the disk enclosures.

Send a

# armdsp -a

topic Re: San errors in Operating System - HP-UX

San errors

Re: San errors

Re: San errors

Re: San errors