- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2022 02:38 AM
Hi,
I was trying to discover data using Agent Client Collector.
We have an instance with MID Server ip being x. I have installed agent in a server with ip y (Set MID Web server ip as x, port 80 and api key <the auto generated api key> while installation). Post installation the Agent Host is showing as 'y'.
Now following the same steps I have installed another agent in server with ip 'z' (with same MID Web server info). But post installation instead of creating a new CI in cmdb the new agent is updating old agent data (modifying y to z). Also now both agent host is showing as z even though first agent is installed in server y.
I have followed the steps mentioned in ServiceNow Product Documentation.
Please let me know if I am doing something wrong or anything else I need to do other than simple install.
Regards,
Debjit
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2022 05:11 AM
Hi Debjit,
It seems the issue is with identification rule, one of your identification rule is getting matched and has similar values for both the CI. Check and debug the payload which is passed to identifiers.
Currently, You must be seeing multiple relationships to the CI downstream to the agent record.
Regards,
Parag Sanyashiv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2022 05:11 AM
Hi Debjit,
It seems the issue is with identification rule, one of your identification rule is getting matched and has similar values for both the CI. Check and debug the payload which is passed to identifiers.
Currently, You must be seeing multiple relationships to the CI downstream to the agent record.
Regards,
Parag Sanyashiv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-02-2023 06:22 PM
Hi Parag,
Thank you for responding.
Yes, you are right the issue was occurring because both CI was having same serial number which is one of the identification rule. Hence data was getting updated instead of desired new record creation.
Regards,
Debjit