question Re: Run a Quick Discovery vs Discovery Schedule in ServiceNow AI Platform forum

Run a Quick Discovery vs Discovery Schedule

Sha_pan — Tue, 27 Aug 2019 21:49:25 GMT

I've been using the "Quick Discovery" when testing an IP Address if for example we're having discovery issue on a certain device and we'd like to test discovery on it while applying fixes. But those IP Address I tested were always part of the IP Ranges/Range Sets that we've configured for the discovery schedule.

I'm trying to work on our SOP for extending IP Ranges or amending discovery scope.

I'd like to know if the "Quick Discovery" would still work even though we haven't yet extended the IP Range/Range Set on that specific VLAN on our Discovery Schedule?

The reason I'm asking is if a new VLAN was created, I wonder if we could perhaps run a quick discovery to test one of the IP Address first and see if the MID server can scan it and be able to identify what will be the errors (e.g. firewall blocking, no credential)? We'd like to make sure all are set up before we amend the discovery schedule and include the new VLAN on the Range set.

Thank you,

Sha

Re: Run a Quick Discovery vs Discovery Schedule

Matthew Glenn — Fri, 30 Aug 2019 17:15:23 GMT

You can run a "Quick Discovery" against any IP, regardless of whether or not it's been defined in an IP Range/Range Set.

I just validated this one of my instances.

Re: Run a Quick Discovery vs Discovery Schedule

Ian Mildon — Fri, 30 Aug 2019 17:24:22 GMT

As Matthew mentioned, Quick Discovery is always against a specific IP; and does not need to be part of a Discovery Schedule or defined IP Range. As long as the MID Server can "see" it, it can run a Quick Discovery.