Shazzam Probe not scanning all the IPs in an IP range

Sivaramakrishn3
Tera Expert

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

1 ACCEPTED SOLUTION

Sivaramakrishn3
Tera Expert

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.

View solution in original post

6 REPLIES 6

Maik Skoddow
Tera Patron
Tera Patron

Hi

did you scan syslog and Discovery status entries for any errors?

Kind regards
Maik

Hi Maik,

We did not get any error in the both system Logs and Discovery status entries.

Thanks & Regards,

Siva

Rahul Priyadars
Giga Sage
Giga Sage

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

Sivaramakrishn3
Tera Expert

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.