Identified, ignored extra IP: False warning in Discovery

[Amit Sharma4]

Hi All

I understand "Identified, ignored extra IP" is a warning in Discovery and supposed to be ignored , generally.

But during my discovery scans I have come across several "Identified, ignored extra IP" warning message which were not correct as in, when I try to discover the IP individually, it creates a new CI with all proper details. On the other hand, if I run discovery on a number of IP address in same segment, I again get the same warning.

Please guide, how to deal with this.

Thanks

Amit

[tim_broberg]

I believe the issue is that it is identifying based on the hardware identifier, which is shared across LPAR's. You can try editing the AIX Serial Number probe to detect LPAR's, and if present read it with uname -L (uname -Ls?), strip away any crud you don't want, and append it to the machine ID. You want multiple LPAR's on the same hardware to get distinct serial numbers like 0694FCG_0, 0694FCG_1, ... where your modifications provide the _0 / _1 bit based on the partition ID and the existing logic provides the 0694FCG.

Discovery team does have plans to address this, and I will nudge them that it is creating customer pain.

Regrettably, my AIX box died of old age, so I'm not in a position to tinker one together for you at this time.

Hopefully pointing out a likely source of the problem will give you some ideas for working through the problem, but it only dashes your hopes, at least it will do so quickly.

We'd love to hear back from you on what results you find,

    - Tim.

[tim_broberg]

I got my hands on an AIX LPAR and tinkered with it a bit.

echo `lsattr -El sys0 -a systemid | cut -f 2 -d\ ` `uname -L` | sed -e 's/ /,/g'

Translated roughly to English: echo the system id, taking the second field, space, LPAR partition ID, replacing spaces with commas.

This works for me on an LPAR, but I have no way to try it on a physical AIX server.

    - Tim.

[Amit Sharma4]

Thanks Tim.

I am checking on this here. As of now the plan for us in not to change any thing OOTB.

I am looking forward for doing some tests. I'll update as soon as I get chance to test it.

Thanks a lot again

[Amit Sharma4]

In addition, it is really a wired issue. I did create CIs manually and after a whole scan on weekend it behaves same way.

Though CIs are there but does not show other details on BSM map.

[Amit Sharma4]

Hi Tim,

I investigated on AIX machines with our support guys and here is what they told me.

They have "N" LPARs sitting on a box (RAC) with same serial number. Each LPR has got a primary IP and Host name. For various other requirements they have creates "M" aliases (different IP and Hostname )for an individual LPR. This kind of LPAR configuration is done for all the LPARs on that box. They are interested to get details of all LPRs in CMDB ( alias can be ignored).    

Discovery is doing its part by dropping the other IPs / aliases once it matches the serial number against those IPs.   So I think first thing I need to do is to exclude the alias IPs on each LPARs from scan and use 1 IP as Primary for scan.   Then I   need to use script to append hostname of LPR in to serial number and use that serial number.

Please advise.

Thanks

Amit