I suspect we have duplicated ID's for some UNIX computers on our customer. We began suspecting this because we had an UNIX asset that went gone, and logs did not registered any deletion.
I researched a little bit and told our UNIX analyst to follow these steps:
Run the following:
caf stop ccnfcmda -cmd DeleteParameter -ps itrm/rc/host/managed -pn convertedhostuid ccnfcmda -cmd DeleteParameter -ps itrm/cfencrypt -pn LOCALID ccnfcmda -cmd DeleteParamSection -ps itrm/rc/security/providers/common/users
Delete the file "/etc/cadmuuid"
Then run the following:
caf register all
caf start amagent args /RESCAN_INVENTORY /RESCAN_SOFTWARE /RESCAN_HARDWARE /COLLECT
I waited for the collect cycle, however the asset is still not being collected.
Is there any other possible file used for identification?
The file on Unix is the /etc/cadmuuid so if you regenerated this then your issue was not with the hostuuid.
There are quite a few possible reasons for the agent not being collected so it is probably best if you log a support case so we can help you.
You could try this on the Scalability Server :
and execute again the following command on the Unix machine
Do you need anything further on this question?
Do you need any further assistance here?
I actually opened a case for this. It worked for a few hosts I've been looking into, however our customer claims that there's still many hosts that's not registering.
Since I can't actually troubleshoot properly by myself on these UNIX agents, It's preferable to schedule a call between me, CA and our UNIX analyst.
Just as a suggestion.
Not sure if the /RESCAN_HARDWARE parameter actually exists.
Maybe using it may avoid the agent execution.
Can you please try to run the command like this?
caf start amagent args /rescan_inventory /rescan_software /collect
Is the agent collected now?