Network Management

Topology Polling job in the SolarWinds Platform fails because of time out

This article explains how to resolve high memory usage issues with the Topology Job Engine worker and address timeouts in the Topology Polling job caused by excessive data from the device.

First published date

4/15/2025 3:31 PM

Last published date

4/15/2025 3:31 PM

Overview

If the timeout for the Topology SNMP polling job is too long, it may lead to high memory usage.


(Example of a Topology Job Engine worker in Task Manager)

Affected Pollers include:

  • N.Topology_STP.SNMP.Dot1dStp
  • N.Topology_Layer2.SNMP.Dot1dTpFdb
  • N.Topology_Layer2.SNMP.Dot1dTpFdbNoVLANs
  • N.Topology_Layer2.SNMP.Dot1qTpFdb
  • N.Topology_Layer2.SNMP.Dot1qTpFdbNoVLANs
  • N.Topology_Layer3_IpRouting.SNMP.inetCidrRouter
  • N.Topology_Layer3_IpRouting.SNMP.ipCidrRouter
  • N.Topology_Layer3_IpRouting.SNMP.ipForwardRouter
  • N.Topology_Layer3_IpRouting.SNMP.rolesRouter
  • N.Topology_Layer3_IpRouting.SNMP.ipv6Router

In case of timeouts, the SolarWinds.Topology.log file at C:\ProgramData\SolarWinds\Logs\Orion contains the following exception:
ERROR DataPreProcessing - Skipping result processing because the job failed, PollingPlanID=SolarWinds.Topology, DescriptionID=node.topology.layer:XX, JobKey=Topology, Entities=[N:XX], State=Canceled

Product section

Orion Platform

Cause

The Topology Poller may not retrieve all data from the device within the allotted time. The default timeout for the Topology SNMP polling job is 30 minutes, as set by the “SnmpTopologyTimeout” centralized setting.

Resolution

  1. Navigate to the Advanced Configuration Page at https://{OrionServer}/Orion/Admin/advancedconfiguration/global.aspx.
  2. Change the “MaximumNumberOfRowsPolledByTopologyPollers” option to a value greater than zero.
    1. Start with 10,000 and decrease the value if timeouts persist.

Data polled by the listed Topology Pollers can be found in the following database tables: PortItems, NodeL2Connections, NodeL3RoutingData.