Discovery Behavior : Does not trigger any other probes except for Shazzam.Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Discovery completes without triggering any probes except for Shazzam probe. Release Any Cause In the discovery IP range if we have an IP network with netmask /32, the discovery fails. Resolution xx.xx.xx.xx/32 netmask is nothing but a single IP. So, instead of using /32 netmask we can use below 2 configurations Create an IP address list and enter the IP that you would like to run discovery on.Create an IP address range and set starting and ending IP as the IP that you would like to discover.