---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Turn off next-hop route data collection for BGP routers

# Turn off next-hop route data collection for BGP routers {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
You can turn off Next Hop Routing Rule \[dscy_route_next_hop\] table collection for BGP-enabled routers to reduce MID Server memory load during router discovery.

## Before you begin

* Verify that you have at least version 1.35.1 of Discovery and Service Mapping Patterns.
* Navigate to <kbd class="ph userinput">sys_properties.list</kbd> and verify that the glide.discovery.bgp_router_disable property is set to false.
{#turn-off-bgp-next-hop-collection__ul_xfz_2pr_hkc}

Role required: discovery_admin

## About this task

By default, the glide.discovery.bgp_router_disable property is set to true, blocking the entire BGP routing branch including interfaces and neighbors. Setting the property to false enables interface and
neighbor collection but also triggers a full route-table walk. On routers with large route tables, this can cause MID Server memory and performance issues.

The glide.discovery.disable_next_hop_data property controls route-table collection. When this property is set to true, Discovery collects the device, physical interfaces, and neighbors but skips populating the Next Hop Routing Rule \[dscy_route_next_hop\] table. The default value is false.

## Procedure

1. In the navigation filter, enter <kbd class="ph userinput">sys_properties.list</kbd>.
2. In the Name column, search for <kbd class="ph userinput">glide.discovery.disable_next_hop_data</kbd>.
3. Select the glide.discovery.disable_next_hop_data system property.
4. In the Value field, enter <kbd class="ph userinput">true</kbd>.  
   To also collect next-hop route table data, set the value to <kbd class="ph userinput">false</kbd>.
5. Select Update.

## What to do next

Run Discovery again against a BGP-enabled router to apply the changes.
**Related reference**   

* [Network router discovery using patterns](https://www.servicenow.com/docs/AGCTag6vL8z1244SR6jCwA "The Discovery and Service Mapping Patterns application uses the Network Router pattern to find network routers in your environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")

