eHealth Discovery did not Complete. No log Result for DCI Merge

Document ID : KB000029110
Last Modified Date : 07/09/2018
Show Technical Document Details
Introduction:

Description:

If  there are two devices which have exact configuration on the network which are part of primary/secondary - primary/failover devices, after discovering one of the devices and having it saved to the eHealth configuration discovery of the second one results in the elements associated with the first device being updated instead of creating a new set of elements for the second device.

This will parameter on the discovery policy should only be use as need as it ignores the ifIpAddress table and Mac address during the eHealth merging process.


Problem:

When trying to merge the discover data in a dci file to the eHealth database, the merge generates duplicate errors even on a freshly installed eHealth system:

Example:

DccAgent: duplicate Physical Addresses detected - 00:00:00:00:00:00 (Example Address)
DccAgent: duplicate Physical Addresses detected - 00:00:00:00:00:00 (Example Address)

Environment:

eHealth 6.2.x
All supported platforms

Cause: 

It could be that the device is in a cluster running VM with multiple IPs and using the same NIC interface.

Warning: Invalid discover policy name 'Naming'.
Warning: Duplicate devices in configuration:
'{000000.000.053351sdfg.gfgf1f|},
{000d000.0000.0000.0000
{0fdfdfdfexample0000Exampleee'.

eHealth generated a log file (name: '/opt/ehealth/log/discoverInteractive.12.21.2012.114101.log'). Example:

Error: Invocation of command 'nhiDciMerge' failed.

Resolution:

  1. In OneClilck, go to the Policy in use
     
  2. Add the following parameter:

    ignoreAddrClouds
     
  3. Save the changes
     
  4. Rediscover the device system.

For more information:

https://comm.support.ca.com/kb/how-to-discover-a-failoversecondary-device/kb000048235

Instructions:
Please Update This Required Field