How to restrict networking when Mid server runs on hosts with two networks

[satoshi256]

I currently have a Mid server running on a host with two network interfaces, each network serving a different purpose. One is used for administration and the other for ServiceNow Discovery. I have a few questions related to this setup:

Is there any official documentation or web page regarding the specifications for this type of network restriction?
Should the network restriction be done in the host's server configuration, or is there a way to control it within the ServiceNow configuration?
How does the Mid server behave if no network restrictions are set? In particular, we are interested in knowing how the Mid server reacts to unrelated network traffic.
It would be very helpful if you could share your experience and knowledge on this topic. Also, if you have any information on recommended best practices or configurations, please share them with us. Thank you in advance for your time and assistance.

[Rahul Priyadars]

Have a look at this...

https://docs.servicenow.com/en-US/bundle/vancouver-servicenow-platform/page/product/mid-server/task/...

Is it a case in ur env that all VLAN is accessible from Given Mid Server. From where Other Traffic will come apart from Discovery when u run?

Regards

RP

[satoshi256]

Thanks RP

I don't think what I am asking is on the page I am reading.
If it is on that page, can you give me the keywords or the name of the section?

I have network connectivity.

[Rahul Priyadars · Accepted solution]

Applications, such as Discovery and Orchestration, can specify an IP range or the specific IP address of a target. When the application looks for a MID Server to use during auto-selection, it chooses a MID Server whose IP range includes the application's range or specific IP address. Applications also use other criteria, such as the MID Server's supported application or capability. See MID Server selection for more information.

Procedure

1. Navigate to All > MID Server > IP Ranges.
2. Click New.
3. Complete the form, using the fields in the table.

   IP address ranges

Hope This helps,

Regards

RP

[Hitesh Patel1]

Here is another thing that you can try that worked for me. 

On the mid server, update the config.xml file to add the following parameter and restart the mid server for the changes to reflect.

<property name="mid.probe.local.address" value="<desired nic IP address>" />

Regards,

Hitesh Patel