When there are two devices similarly configured on the network which act as 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 is a common issue/scenario. To allow eHealth to discover both sets of elements without updating one set in a manner to look like the second set, enable the following optional parameter in the Discover Policy used to discover the devices:
Device Matching - Ignore Address Clouds [ignoreAddrClouds]
Where "Device Matching - Ignore Address Clouds" is the name of the parameter and "ignoreAddrClouds" is its symbol. Set the value to 'Yes'