---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Omit network adapter secondary IP addresses

# Omit network adapter secondary IP addresses in Linux discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Limit Linux discovery to specific network adapters and their primary IP addresses to improve performance by ignoring secondary IP addresses.

## About this task

Configuring the network_adapter_exclusion_list system property ensures that only specified network adapters and their primary IP addresses are used during Linux discovery. Secondary IP addresses that are not named are automatically omitted.

## Before you begin

Role required: admin

## Procedure

1. In the navigation filter, enter <kbd class="ph userinput">sys_properties.list</kbd>.
2. In the Name field, search for <kbd class="ph userinput">network_adapter_exclusion_list</kbd>.
3. Select the network_adapter_exclusion_list property.
4. In the Value field, enter the network adapter associated with the NIC IP address to exclude it from deletion.  
   The network adapter must be entered in one of the formats listed in the following table.{#omit-adapter-secondary-ip-linux__table_d2c_mxg_xdc__entry__2}

   | Format | Description |
   |-|-|
   | Single name | Single adapter name. For example: <kbd class="ph userinput">bond0</kbd>. |
   | Regular expression matching multiple adapter names | Regular expression that matches multiple adapter names ending with one or more digits. For example: <kbd class="ph userinput">bond\d+</kbd>. |
   | Multiple adapter names | Multiple adapter names, separated by commas, including regular expression. For example: <kbd class="ph userinput">nic1,bond\d+</kbd>. |
   [ ]

   {#omit-adapter-secondary-ip-linux__table_d2c_mxg_xdc}
5. Select Update.
{#omit-adapter-secondary-ip-linux__steps_y1f_lwg_xdc}

## Result

When the predefined schedule triggers the Linux server discovery or a scheduled horizontal discovery runs, only the specific network adapters and their primary IP addresses are included in the discovery process.

For more information, see [Schedule a horizontal discovery](https://servicenow-prod.fluidtopics.net/CIQEq9XeYjrEAd3sKWHEVg "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.").
**Related reference**   

* [Linux discovery](https://servicenow-prod.fluidtopics.net/tbWHQ8W2tJRHRooeehDOHA "Discovery and Service Mapping applications use probes and patterns to discover and map information about Linux computers and servers. The information is populated in the CMDB. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")