AIX Server discovery issues

[Chintu1]

HI All,

when trying to discover Aix Server it's trying to override the Original Ip of what we had given for quick discovery and updating the other Correct CI. 

And wanted to know why the discovery is conflating the 2 devices.

Let me know if you have any idea on this issue.?

Thanks,

Best regards

CG

[Jordan Hladish1]

Chintu - 

Servers typically have more than one IP address that they respond on. To represent this, CIs have a ip_address field, but things like Servers also have a related list for Network Adapters to show ALL IP addresses related to that device. Any of those IPs could be called "that device's IP address" by definition of how DNS works. This is why filtering devices on IP address can be tricky - what Discovery sets as the 'main' IP address may be different than what you use to Discover the IP.

Additionally, the second IP address is very possibly in your schedule - maybe causing you to Discover the same device twice, and updating the IP address of the device on it's second responding IP in a Schedule.

Jordan

[Ashutosh Munot1]

HI,

If the same device is discovered in same schedule then discovery will mark that IP address in device section as Identified, ignored extra IP.

Now if you want that this should have only one IP address then we have a property called as enforce IP address in discovery properties have a look at that. But then this is system wide property for discovery.

Rest i agree that one server can have many IP address and can flip from one IP to other in different schedules.

Thanks,
Ashutosh

[BRIAN MORAN]

Jordan, late to the party on this one but is there a fix for this AIX issue?.   our issue is not only does it override the IP address but it renames the host also.  We end up with a CI flapping between several names.

We're trying to just discover the IP listed in the FQDNS only and not any of the other IP addresses in the table.  is that a reasonable workaround?

[Jordan Hladish1]

When you're Quick Discovering that device, the Discovery Log should provide some information to you for what the device is "key'ing" on to update an existing item in the CMDB. In your scenario, does the Discovery Logs state that it's matching on serial, IP, etc? This should possibly give you a starting point for how you can customize an Identifier to uniquely grab things, etc.