topic Re: Syslog with CVSDM message in Disk Enclosures

Syslog with CVSDM message

Peter te Focht — Fri, 27 May 2005 06:46:06 GMT

Once a day, about 12:30, I get a lot of messages in the syslog, they look like this:
CVSDM; CRITICAL Eventcode 199; Description lost connection to host. Unable to communicate to the devicepath; Hardware address=/dev/dsk/c68t2d6; Unknown FRU Location; Unknown Vendor ID; unknown Model ID and so on. However, when I execute an ioscan I don't see any problems. Who can help me, thanks in advance,
Regards, Jan Poortman

Re: Syslog with CVSDM message

Mario_66 — Fri, 27 May 2005 08:39:50 GMT

Hi Jan,

where this device is located: /dev/dsk/c68t2d6? In VA storage? What version of CommandView do you use? Can you describe your system a little bit more?

Regards,
Mario.

Re: Syslog with CVSDM message

Thayanidhi — Sun, 29 May 2005 07:42:15 GMT

Hi,

"ioscan -fnC disk" should show NO_HW for atleast one device. If not then it would be a intermintent problem. So, check syslog.log any other line related to the same device. Id this disk configured any of the exisiting VG? (strings /etc/lvmtab)
You can also EMS alert for this device.
Run cvui (located in /opt/sanmgr/commandview/client/bin)
check the property and status of the array.

Regds
TT

Re: Syslog with CVSDM message

Peter te Focht — Mon, 30 May 2005 03:02:54 GMT

Hello Mario,

We are using the commandview-version 1.08 on hpux11.00. And indeed, the storage is a VA7410.
When running ioscan I have no disks with NO_HW.
Regards, Jan

Re: Syslog with CVSDM message

Peter te Focht — Mon, 30 May 2005 04:01:44 GMT

Hi Thayanidhi,

Thanks for reply, I checked the VA's but they show no errors, even not in the logs.
So I really don't know what is going on.

Re: Syslog with CVSDM message

Mario_66 — Mon, 30 May 2005 10:02:33 GMT

Hi,

do you have any other storage connected to the server with CVSDM installed?

What is output from:

#diskinfo -v /dev/rdsk/c68t2d6

It may be that DB file is corrupted.

Have you tried to restart Host agent? EMS?

Regards,
Mario.

Re: Syslog with CVSDM message

Peter te Focht — Tue, 31 May 2005 07:12:01 GMT

Good Afternoon Mario,

I think you are right, the disks mentioned in the syslog do not exist anymore. So it could be possible that the DB of EMS is corrupt. But how to re-start EMS. I stopped stm and I started it again, is that the right way? In /sbin/init.d it was not possible to stop and start ems.
Regards, Jan

Re: Syslog with CVSDM message

Mario_66 — Tue, 31 May 2005 08:38:11 GMT

Hi,

I am not sure that EMS is causing this problem. It looks more like RemoteMonitoring issue. It tries to reach devices from its DB list and it can not.

Try:

/opt/sanmgr/hostagent/sbin/ha_dial_stop
/opt/sanmgr/hostagent/sbin/ha_dial_start

to restart CV. If it does not help you will have to recreate DB.

BTW, you can restart EMS with command:

/etc/opt/resmon/lbin/monconfig

HTH,
Mario.

Re: Syslog with CVSDM message

Peter te Focht — Tue, 31 May 2005 09:03:23 GMT

Hi Mario,

Stopped and started HA_dial, the result was a lot of error-entries in the syslog.log. Here all these disks were mentioned again.
Can I stop EMS in a high available cluster ???

regards, Jan

Re: Syslog with CVSDM message

Peter te Focht — Wed, 01 Jun 2005 02:11:11 GMT

Hello to all of you.

Since the host, where the problem happens, is a node in a high available cluster, HP advises to run cvsdm only on one node. So I killed the one on this server and we don't see the problem anymore.
I agree, it is not a nice solution.
Thanks for your help.

cheers, Jan

Re: Syslog with CVSDM message

Peter te Focht — Wed, 01 Jun 2005 03:11:23 GMT

Look in the last comment of this thread.

cheers, Jan