- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2018 08:29 AM
Hi All,
I'm running a quick discovery in an on demand discovery schedule.
I put 10 ips as a quick discovery and only 1 got discovered. I don't see other 9 ips, no error message for them.
where I'm suppose to see those ips if they're not reachable or something?
they're not been excluded.
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2018 06:29 AM
Hi,
Again to comment on this. This IP ports might be closed.
Or you might not be able to enter into them, so we are not able to identify it.
Can you do one thing. Try quick discovery on 2 to 3 IP from Quick ranges and see what you get.
Let me know. I always debug this way because we get limited logs and ecc queues.
Thanks,
Ashutosh Munot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2018 01:11 AM
Hi Ashutosh,
I did quick discovery separately for those ips and now in the discovery logs I see that Shazzam shows No port open error.
same error I was expecting when I hit quick range discovery but there it shows discovery logs only for the ones which are successful discovered.
I'm not able to identify the IPs which have port issues\not reachable through quick range schedule discovery. it's quite a tough to go through Shazzam Input XML and search the messages. rather its pretty easy and clear under the discovery logs if they appear.
though a quick discovery:
through a schedule or quick ranges discovery:
No entry for not reachable, port issue IPs in discovery logs, but entry of only discovered CIs

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2018 03:30 AM
Hi,
Glad it helped.
This happens usually.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2018 05:28 AM
hi sumeet,
there may be 2 reasons for this.
either there is no port open for the devices or there is a timeout issue in making connection.
can you go in probes and increase the value of these 2 parameters for the shazam probe (GenericTCP_waitForConnectMS & HTTP_waitForResponseMS).
and now give it a try.
if still not working then please check the respective port for the devices