Incorrect Host aliasing in Federator (4300181)

• Monitored host performance metrics in Child FMS doesn't match with performance metrics in Federator FMS.
• Host object shows multiple aliases in the Federator FMS, but doesn't show any aliases in the Child FMS.
• Host object shows it has collected the systemId in the Federator FMS, but it doesn't show a systemId in the Child FMS.
• Host Object shows multiple rows in the sourceIds property in the Federator FMS.

The Federator FMS is gathering the data from multiple Children FMS. The likely cause is that this Host object has been discovered by more than one Child FMS which can inadvertently be adding the systemId to the monitored Host object and generate Host aliasing in the Federator FMS.

The systemId property, if set, can make unrelated Host objects to be merged as an alias in the Federator FMS even if there aren't any aliases in any of the Children FMS. This often occurs in Linux servers when they're cloned from a Virtual Machine template since they preserve the same System ID.

This may be caused by duplicate agents across different Children FMS as well.

To check if any Host aliasing is occurring in the Federator FMS, use the script in Step 1 of KB 205776. The output might be something like this for example:

Aliases for Host:examplehostname001
examplehostname005
examplehostname003
----

On the Federator FMS, search for this Host object in the Script Console and check the contents of the sourceIds property. See the following example for illustration purposes only:

In the example above the sourceIds are just these two:

0de14755-a4ec-4753-88e8-0d65b65b78bb:1c76a03d-06e7-4f8b-88ca-928b15fd2487:2
dc19e3f0-494a-4d61-a168-5d55befa8b03:49e0b9de-e02a-410c-a3a7-89e7036a6410:50

These strings represent a combination of the Object ID (uniqueId), an Id of the Child FMS and the object version number. When there's an issue with Host aliasing, this property will have 3 or more rows.

In order to fix the problem, follow steps 2 to 4 in KB 205776 for each of the objects in the list above to ensure the systemId is not being collected in any of the associated objects in the Children FMS.

1. To track the issue on each Child FMS, search for the Object ID on the Script Console.
   
2. If it shows that it's collecting the System ID, go through steps 2 to 4 in KB 205776.
3. Delete the Host object using the the Object Cleanup dashboard.
4. Make sure there aren't any duplicate agents monitoring the same Host.
5. Repeat from Step 1 for every row in the sourceIds retrieved at the beginning of the Resolution. If complete, then move on to step 6.
6. After cleaning up any Host objects that have the systemId property set in the Children FMS, the affected Host object in the Federator FMS must be deleted using Object Cleanup dashboard.

The Federator FMS will recreate the Host object next time it resynchronizes with each Child FMS. This can take several hours to complete.