What is the setting in the CI so Discovery doesn't scan it? I've added a screen shot of the field that has to have an opt

JA12
Tera Contributor

There are like 15 options in the Discovery Source box. What option should be selected if I do not want Discovery to scan an asset?

 

thanks

 

find_real_file.png

6 REPLIES 6

DaveHertel
Kilo Sage
Kilo Sage

Hi -- the Discovery Source field is not what you are looking for.  This field only shows WHERE the CI came from, but does not control if the CI is scanned via disco or not.

To stop a CI from being scanned by Discovery, the disco job/ecosystem must be informed not to scan the CI, which can be done via a few ways:

  • Dont' include the IP of the CI in the discovery scope/range for schedules
  • Blacklist the IP from an existing range/set.  This is effectively the same as the prior point, just a different approach
  • don't include the credential for the CI in Discovery's scope.  Or if there is a enterprise cred that is used for all machines remove that cred from this CI.   the point being to block disco from having required access

Bottom line:  If a device's IP is in scope for a discovery schedule and valid credentials exist to scan it, and the disco MID servers can reach the device, it'll generally get discovered. 

Hope this helps?

 

+1 twice over to what Dave says but you might also look at the IRE to set data precedence rules on devices in the CMDB that should or should not be updated by a particular discovery source

JA12
Tera Contributor

First - I'm not an Admin. But do have access to the CIs.

So an admin has to do the steps mentioned above because I'm not an admin and was hoping I can make those changes on the CI.

Can I set the fill box in the Discovery Source to "Manual entry or None?'"

find_real_file.png

No, that will be worthless and it'll likely just get overwritten next time Discovery runs.

Same answer as before - if you want to stop the CI from being discovered, the setup of Disco (IP, schedule, credential, etc.) needs to change

The Discovery source field has NOTHING to do with controlling IF a CI get discovered or not.  that field just reports where the data came from.