Start a Conversation

Unsolved

A

1 Rookie

 • 

19 Posts

2192

December 11th, 2018 09:00

Discovery failing

Hello,

Appreciate if anyone has an idea to why this is not working. I have create a discovery job to scan a complete subnet x.x.x.0 which always fails with 

Running
Unable to connect to the device.
Task Failed. Completed With Errors.
 
If I discover an IP within that range it gets discovered just fine. Somehow all discovery jobs for complete subnets (mostly /24) are failing with that above error.

1 Rookie

 • 

19 Posts

December 11th, 2018 09:00

Already think that I found the issue being that I am not specifying the subnet mask.

1 Message

February 25th, 2019 01:00

i am the same error, pls share for it.

13 Posts

February 25th, 2019 07:00

Since you weren't putting the subnet it was just scanning that 1 ip address.  Here are some examples for discovery ranges

Sample Valid IP Range Format:
10.35.0.0 (single IP address)
10.36.0.0-10.36.0.255 (range of IP's)
10.37.0.0/24 (entire subnet of IP's)

No Events found!

Top