- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2022 07:24 PM
Shazzam probe input payload doesn't have the result for all the IPs in the provided IP range. Because of this, certain devices are not discovered. When we individually scan the missing IPs, we are able to discover the devices. Your help is much appreciated. Thank you in advance!
Sample IP range used: 172.29.196.0/24
Missing IPs: 172.29.196.15, 172.29.196.34, 172.29.196.45
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2022 09:43 PM
The issue is resolved after setting the mid server property "mid.shazzam.threads" to 0. Looks like SanDiego has some issue in using multiple threads. This is the workaround.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2022 08:01 PM
Hi
did you scan syslog and Discovery status entries for any errors?
Kind regards
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2022 09:36 PM
Hi Maik,
We did not get any error in the both system Logs and Discovery status entries.
Thanks & Regards,
Siva

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2022 09:01 PM
Discovery in Shazzam probe i.e. first phase will scan all IPs in that range unless they are not in exclude IP list.
During Schedule run assuming devices and IP are active?
Best place is to check the logs as stated already.
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2022 09:43 PM
The issue is resolved after setting the mid server property "mid.shazzam.threads" to 0. Looks like SanDiego has some issue in using multiple threads. This is the workaround.