Disk Enclosures
cancel
Showing results for 
Search instead for 
Did you mean: 

CVSDM; DEVICE ADDED Event Code=198

ricardo_24
Occasional Contributor

CVSDM; DEVICE ADDED Event Code=198

Hi,

I have this message in syslog. The complete message is:


"Apr 12 13:39:06 raiarp1 syslog: CVSDM; DEVICE ADDED Event Code=198; Description=
Device Added; Hardware Address=1/0/1/0/0/1/1.6.0;
Apr 12 13:39:13 raiarp1 syslog: CVSDM; DEVICE ADDED Event Code=198; Description=
Device Added; Hardware Address=1/0/0/3/0.6.0;
Apr 12 13:46:09 raiarp1 tftpd[24685]: Timeout (no requests in 10 minutes)
Apr 12 13:55:28 raiarp1 syslog: CVSDM; DEVICE ADDED Event Code=198; Description=
Device Added; Hardware Address=1/0/1/0/0/1/1.6.0;
Apr 12 13:55:35 raiarp1 syslog: CVSDM; DEVICE ADDED Event Code=198; Description=
Device Added; Hardware Address=1/0/0/3/0.6.0;"

The out "ioscan -nf" command dont show this hardware path, see:

ctl 6 0/10/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c8t7d0
ba 7 0/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 1 0/12/0/0 igelan CLAIMED INTERFACE HP A6825-60101 PCI 1000Base-T Adapter
ioa 1 1 sba CLAIMED BUS_NEXUS System Bus Adapter (803)
ba 8 1/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 9 1/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 10 1/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 11 1/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 12 1/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 1 1/10/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter

I was stoped the diagnostics (support tools manager) and this message continuous logged.

My version of stm is: A.38.00

Any idea?
1 REPLY
Andrew Merritt_2
Honored Contributor

Re: CVSDM; DEVICE ADDED Event Code=198

It's actually CommandView SDM (CVSDM) that's generating these messages, though you may also see them being reported by the RemoteMonitor portion of the EMS Hardware Monitors (but all that monitor does is report data from CVSDM).

Which version of CommandView do you have installed? The problem should be fixed with cv 1.06, but has occasionally been seen with that version. Moving the deviceDBFile and recreating it with armdiscover has been seen to fix this in that case.

Andrew