MarkWalther asked a question.
ILMT Connector duplicating Server entries in Inventory.
Has anyone seen their IBM BixFix ILMT connector duplicating device entries? It seems to happen when the Server with the Integration Manager installed on it gets rebooted.
Wondering if it is something simple before I log a support ticket.
Thank you
Mark Walther
Another thing I notice is that when the Server is rebooted with SIM installed the aggregations run even if they are not scheduled (excluded from the Global schedule). Is this a normal thing? Can it be overridden?
we have the same problem where we are getting duplicates when using ILMT via SIM on servers that also have an agent installed. We have tried changing the time for ILMT data collection to occur before the agent scan, but that hasn't changed things. Will try the other way now of having ILMT after the agent scan.
Hi, have you looked at Hostname-Only mode and Hostname Normalisation. Given the manner in which external connectors can feed information to Snow Invenory vs what the Snow agent presents, its possible that Snow thinks a server is not the same one from each source and the matching routine creates a duplicate. By implementing the above options its possible to change what used to match a machine so that duplication is prevented. The example given on the Hostname Normalisation docs even give ILMT as a worked example....
thanks Colin, I was wondering if it may be related to these hostname settings, it is a windows server though and does not come in with FQDN from either source. I have enabled for this site, so we'll see over the next few days if there is any change :)
We had implemented Hostname Normalization already. I just verified it was still in the config file. I'll need to look at the Hostname-Only one.
Thank you
Yes, looks like both are in the config.
</Master>
<AgentIdentity>
<HostnameNormalization>
<SiteConfiguration expression="{A} AND {B}">
<SiteNames name="A">
<SiteName>snow*</SiteName>
</SiteNames>
<ConfigNames name="B">
<ConfigName>XYLEM_Win-20240514</ConfigName>
</ConfigNames>
</SiteConfiguration>
</HostnameNormalization>
<HostNameOnly>
<SiteConfiguration expression="{A} AND {B}">
<OperatingSystems name="A">
<OperatingSystem>AIX</OperatingSystem>
</OperatingSystems>
<SiteNames name="B">
<SiteName>XYLEM</SiteName>
</SiteNames>
</SiteConfiguration>
</HostNameOnly>
</AgentIdentity>
</Configuration>
Hey Mark, I was responding specifically to SeanMag's post, apologies for the confusion. Looking at the behaviour you are seeing, have you seen this KB? It could be that the server reboot is then causing the SIM connector to trigger its aggregation in quick succession with the agent sending data?
Yes, I had narrowed it down to when the SIM servers are rebooted. It appears even non-scheduled connectors run the aggregation when the service starts post reboot. I had ILMT in 2 SIM servers, one for testing (non-scheduled) and another for the scheduled. I removed the test one to see if that fixes it on the next patching reboot schedule.