DEVICE ADDED messages in syslog

[Dave Chamberlin]

Hello,
I am noticing that every 20 minutes or so this line is added to the syslog.log file: ...CVSDM; DEVICE ADDED Event Code 198; Description=Device Added; ; Hardware=0/0/0/2/0.6.0.
This would be the address of one of the internal disks. Can someone tell me what these messages are telling me?

[IT_2007]

ESM is monitoring hardware activity. Check ESM monitor log for more details which would be somewhere under /var.

[Steven E. Protter]

Shalom,

Many disk arrays show up as LUN0 on an ioscan, but are not disks, therefore trigger error messages.

This is not anything to worry about, so long as no disk is missing. It is possible for the SAN administrator to change configuration, depending on the array to make this stop.

Another good tactic is to always present one lun to the HP-UX system as LUN0, negating these problems.

SEP

[Prashanth.D.S]

Hi Dave,

Seem to be similar to this issue which i went through recently...

Has the disk at this path been replaced anytime recently ? If so a duplicate entry in the below mentioned file may be causing this issue.

/var/opt/sanmgr/commandview/server/data/DeviceDBFile

If there are any entries found please do the below action..

Remove the bad entry in file
/var/opt/sanmgr/commandview/server/data/DeviceDBFile
Stop and start host agent :
/opt/sanmgr/commandview/client/sbin/HA_Dial_Stop
/opt/sanmgr/commandview/client/sbin/HA_Dial_Start

Best Regards,
Prashanth

Can you check if the below mentioned

[Dave Chamberlin]

Well I looked at the DeviceDBFile and that disk appears 4 times. Once for the original hostname, once for temp hostname change I made and twice with the current hostname, one with full domain and one without. It looks like my va7410 disks are also listed mulitiple times (for different hostnames). As I will be changing the hostname of the box after our Oracle upgrade, I guess I can wait until then to remove the extra entries.

[IT_2007]

If you are certain about duplicate entries for same device then you can remove them online using rmsf command. Make sure that those device addresses are not listed in /etc/lvmtab.

[Steven E. Protter]

Shalom,

This additional information could indicate problems with the configuration of the disk array or SAN network.

Test:
xstm
Try and exercize all disk devices.

this will take time, but some of them will fail instantly. This may lead to my original post being proven or disproven.

Have the SAN admin check the network configuration.

SEP

[Dave Chamberlin]

Hi Steven,

Why would the disk array configuration have anything to do with my internal disks? BTW - my array is a VA7410 and I have two internal disks. The internal disk in question is shown only once using xstm.

[Andrew Merritt_2]

The message is coming from Command View SDM; why it thinks it should monitor your internal disk drive I don't know, unless as suggested the path has been reused.

Prisakanth's suggestion is what I would recommend that you try, since it appears that the DeviceDBFile has got out of sync with reality.

The EMS HW Monitor involvement is limited to the RemoteMonitor process reporting what its been passed by CVSDM.

I don't think running the STM tools is going to tell you anything, either. The EMS HW monitors should know enough to not monitor virtual devices.

Andrew

[Andrew Merritt_2]

Oh, two other things to check:

- Do you have a recent version of CommandView SDM?

- Do you have current OnlineDiags installed?

Andrew