- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2015 12:53 PM
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
Solved! Go to Solution.
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-12-2015 08:34 AM
Hi Tim,
Over the time I found two work around for this.
1: Discovery of Solaris Zones : So far I did not try this.
2: Solaris Blades : Tried this and it worked fine.
Thanks
Amit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2015 10:03 AM
Amit, you're saying the machine has only one IP on the segment, but the identifier is complaining about multiple IPs?
If you look at the CI, there is only one IP on the segment?
- Tim.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2015 10:44 AM
Hi Tim
Yes, I give you an example. I did a scan on /24 IP range and I got close to 20 IPs saying "Identified, ignored extra IP" for some 10 different IPs already added as CI in CMDB ( i.e. we are talking about 30 IPs, 20 as "Identified, ignored extra IP" and 10 as CIs).
But those 20 IPs were form different servers as I validated it with list of about 50+ IPs given by my AIX / UNIX support team.
Later on I did try to discover few IPs individually and all turned out to be new CI. Whenever i tried to run discovery on 5/ 6 IPs in one go, I used to get message "Identified, ignored extra IP".
Finally I had to discover then one by one and all were created as CI and I came up with this question.
Please advice.
Thanks
Amit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2015 05:18 PM
I have had similar issues when dealing with AIX in our environment. The serial numbers are the exact same from the physical they are hosted on. I've had to mess around with the CI Identifiers to be able to effectively classify all of them. Once created they should be fine and recognize either from Network Adapter or Name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2015 07:28 PM
Hi Andrew
Thanks for this information. Could you please provide more insight on this.
Thanks
Amit