Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Exclude MID server from IP Range? IP ranges vs Discovery Range Set for DMZ

Henrik Jutterst
Kilo Sage

I need to limit Discovery for one MID-server so that it only uses one Discovery Range Set, but I can't seem to figure it out - or if it's possible.

find_real_file.pngFigure 01 - Discovery Range Set, with 139 IP entries


Looking at the MID server I only see the option to add IP ranges, but no option to use the already defined Discovery Range Set with all the IPs involved in the DMZ.

find_real_file.png
Figure 02 - The MID-server with one IP Range

 

So my question is:
Is there a way to limit Discovery for one MID server to only use Discovery Range Set? Or what's the alternatives here?

As I see it, I have no option to add more then one IP range in my definition:

find_real_file.pngFigure 03 - My test IP range.

 

Setting up a Schedule does not help as I see it even though we have the correct Discovery Range Set selected.


find_real_file.png
Figure 04 - Discovery Schedule with selected Discovery Range Set

 

 

What's the best way to move forward so that the MID server only uses DMZ ip range?
The Discovery Range Set is a list of 130+ ranges.

1 ACCEPTED SOLUTION

doug_schulze
ServiceNow Employee
ServiceNow Employee

Applying the specific range set to a schedule that has a single non-clustered midserver should do exactly what you are trying to accomplish. 

View solution in original post

3 REPLIES 3

ersureshbe
Giga Sage
Giga Sage

Hi,

Can you check below article  for your requirement? I hope it will helpful for you.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0748222

We have option include and exclude the discovery. I hope, it will helpful for you.

Please mark as correct answer if it helped.

 

Regards,

Suresh.

Regards,
Suresh.

doug_schulze
ServiceNow Employee
ServiceNow Employee

Applying the specific range set to a schedule that has a single non-clustered midserver should do exactly what you are trying to accomplish. 

Rahul Priyadars
Tera Sage

see if it of any help - https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/product/mid-server/task/t_ConfigureMIDIPRange.html

Regards

RP