How do I prevent Discovery from using SSH for Firewalls?

[Doug5]

I need to prevent Discovery from trying to login to Firewalls using SSH - because it creates annoying errors in the logs on the Firewalls.

I tried using a Behavior in a new Discovery Schedule just for Firewalls - which worked - but then I need to edit all the existing Discovery Schedules (and there are hundreds) to exclude the IP-Addresses of the Firewalls.  I can't use a Global Exclusion because then my new Discovery Schedule does not work.  

Any thoughts?

[dbook]

A global exclusion would be the most sensible way forward as you have hundreds of existing Schedules. 

What is the exact issue with re; 'new Discovery Schedule does not work.  '

All the Global exclusion should be doing is ensuring probes are not sent out to the excluded IPs. 

[Doug5]

This question is a Duplicate of Prevent Discovery from Probing the SSH port on Fir... - ServiceNow Community
Sorr.  I accidentally created it twice.  There used to be a button to display one's Questions, but I can't find it anymore!  Anyway - different problem.  
The new Schedule does not work - because When it runs and attempts to Scan the IPs of the Firewalls, these IPS are in the Global Exclusions so it scans nothing (no IPs).
Last night, I was thinking, I add the Global Exclusion for the firewalls as a Sperate Exclusion with its own sys_id.  I then run the Firewall Discovery using a scheduled Flow.  I would use a Scheduled Flow (rather than a Scheduled Job) because Flow are better at pausing and waiting for things.  The would the temporarily remove the Firewall Exclusion, run the Scheduled Discovery using thee discoveryAPI, wait for the discovery to finish and then put back in the Global Exclusion for the Firewalls.
I wish there was a Comment fields on Scheduled Discoveries - so that Support don't get terribly confused by all this in the future.

[sahithg]

Have tried ip service affinity? that could reduce the hits on target hosts on consecutive discoveries.

[Doug5]

In the End, I created a Scheduled Job that loops the  firewalls in the CMDB and adds (or removes) their IP Address in a new Global Exclusion List just for Firewalls.  Only a203 Firewalls were being discovered using Horizontal Discovery;  Most pf the Firewalls were being imported using an SNMP Get from SolarWinds.