Enable Error Message "x.x.x.x is not a reachable host (no response to target ports scanned by MID)" For A Scheduled Discovery?

Tom Rausch · ‎06-15-2020

Overview

Can I enable the error message "x.x.x.x is not a reachable host (no response to target ports scanned by MID)" when I run a Scheduled Discovery? I receive that error message when I run a Quick Discovery, but I do not receive that error message when I run a Scheduled Discovery. I want this error message so I receive a log entry for every IP address that is not Discoverable; I currently receive no such error message

Example

When I run a Quick Discovery of a single IP address, 10.254.8.241, the IP is not reachable, and I receive this error message in the Discovery Log.

"10.254.8.241 is not a reachable host (no response to target ports scanned by MID)."

The benefit is that I receive a message in the Discovery Log that identifies an IP address that is NOT Discoverable.

When I run a Scheduled Discovery of the subnet 10.254.8.240/28, which includes the IP address 10.254.8.241, the Discovery finds eight devices; the IP address 10.254.8.241 has no device and so there is no associated device on this list.

10.254.8.245 dccan100tol02 Windows Server
10.254.8.246 cacol2app21 Windows Server
10.254.8.247 cacol2app20 Windows Server
10.254.8.248 dccan100sql17 Windows Server
10.254.8.250 (empty) Active, couldn't classify: No WMI connec
10.254.8.251 dccan100tola3 Windows Server
10.254.8.252 dccan100exc13 Windows Server
10.254.8.253 (empty) Active, couldn't classify: No WMI connec

These IPs in the Discovery Range have no devices. There is no mention of these IP addresses in the Discovery Log.

10.254.8.241
10.254.8.242
10.254.8.243
10.254.8.244
10.254.8.249
10.254.8.254

I would like to see these messages in the Discovery Log

10.254.8.241 is not a reachable host (no response to target ports scanned by MID).
10.254.8.242 is not a reachable host (no response to target ports scanned by MID).
10.254.8.243 is not a reachable host (no response to target ports scanned by MID).
10.254.8.244 is not a reachable host (no response to target ports scanned by MID).
10.254.8.249 is not a reachable host (no response to target ports scanned by MID).
10.254.8.254 is not a reachable host (no response to target ports scanned by MID).

Tom Rausch · ‎04-08-2021

Hello, @Peter Wood and @Marskh11 ,

I have not found a workaround and I'm not sure that I ever will. One possible complication is that the number of IPs that are designated "not a reachable host" can be massive for subnets with small CIDR host identifier bits. For example, if one scans the subnet "10.0.0.0/8", Discovery would have to report on 16,777,216 IP addresses, most of which are like designated "not a reachable host." This alone is one reason not to report on IP addresses that are designated "not a reachable host".

This is also discussed in this linked post.

Discovery Report Shazzam IPs Neither "Active" Nor "Alive"?

View solution in original post

valarmathi_kann · ‎06-15-2020

Hi TOM,

I see from the code that the message "x.x.x.x is not a reachable host (no response to target ports scanned by MID)" is shown in the discovery log only during quick disocvery and in the discovery_schedule where single IPs are specified in the IP ranges.

Unfortunately, for the network ranges provided in the disocvery ip range doesn't throw this message. We have to update the code to show this message.

To track the steps performed on each device in the subnet, you could see the discovery_log based on the device field [ip_address].

Tom Rausch · ‎06-16-2020

Hello, Valarmathi,

Thank you for your reply.

You state, "We have to update the code to show this message." Can you suggest which code needs to be modified and in which way to show this message? I can then proceed with my own modifications.

Regards,

Tom Rausch

Omkar Mone · ‎06-15-2020

Hello,

Please check if the MID is up and running, also try to ping the host machine once, if that is successful please check if the ports are allowed by Firewall.

Regards

Omkar Mone

Ashutosh Munot1 · ‎06-16-2020

HI,

This message is specific to quick discovery for single IP and not for whole schedule.

Thanks,
Ashutosh