Discovery CI

mike2agk
Tera Contributor

Team,

when i run quick discovery against an IP e.g [1.1.1.1.1] it discovers a CI and updates the CI in the CI table. However, the IP that gets updated in the CI table[1.1.1.2.2] is not same as the IP[1.1.1.1.1] i ran a quick discovery with.

Appreciate any input

Thanks

Mike

1 ACCEPTED SOLUTION

glide.discovery.enforce_ip_syncEnforce syncing of IP addresses Sets the first IP address. Each time a computer with multiple NICs is discovered, one of the IP addresses associated with the NICs is chosen as the IP Address field of the CI. A value of false collects all NIC IP addresses.
  • Type : true | false
  • Default value: true

There is actually a property that does this. As you can see it basically randomly changes one. I think if you set this to false it would set that attribute with a list of all the ips but I can't guarantee this behaviour as I haven't changed it before. You could try searching all script include scripts for that property and see if you can find the code that sets it.

View solution in original post

11 REPLIES 11

You are going to have to dive into the probe/sensors and see what's setting it. It could be set at identification time too so you will have to dig into the code. I haven't looked for it before but if it's not specifically in the identify probe/sensor then it's probably in one of the script includes that get called.

,

thanks for the feedback. But what am i looking for in the probe/sensors and what do i change or update it to. Also to mention that its only some not all of the IP's that have this issue when i run a quick discovery

 

Thanks

Mike

glide.discovery.enforce_ip_syncEnforce syncing of IP addresses Sets the first IP address. Each time a computer with multiple NICs is discovered, one of the IP addresses associated with the NICs is chosen as the IP Address field of the CI. A value of false collects all NIC IP addresses.
  • Type : true | false
  • Default value: true

There is actually a property that does this. As you can see it basically randomly changes one. I think if you set this to false it would set that attribute with a list of all the ips but I can't guarantee this behaviour as I haven't changed it before. You could try searching all script include scripts for that property and see if you can find the code that sets it.

I'll do you one better look at the script include IPAddressFixup. It must be getting called from somewhere else. Either way to get it to set to just the ip that it is being discovered by you will have to do some customization using a business rule or something. Hope this helps.

I updated the property to true[ it wasn't checked], i also deleted the previously discovered CI and ran discovery again against the IP and it worked