Network Management

Interfaces discovery via SNMPv2 or SNMPv3 are not showing any interface on list resources after upgrading to SolarWinds Platform 2024.4, 2025.1 and 2025.2

This article explains where interfaces are discovered; however, network interfaces do not appear in the list of resources after upgrading to SolarWinds Platform 2024.4, 2025.1 and 2025.2. The network interfaces appear correctly if an SNMPwalk is performed separately outside the SolarWinds Platform.

First published date

1/27/2025 11:24 AM

Last published date

12/8/2025 4:53 AM

Overview

After upgrading to SolarWinds Platform 2024.4, 2025.1 and 2025.2, interfaces does not appear when running List Resources or discovery, although data such as CPU or Memory comes, network interfaces are not listed or do not appear properly.

 

Symptoms: 

  • Interface discovery occurs, but no interfaces appear under List Resources
  • Interface discovery no longer works for some devices after upgrading to SolarWind Platform 2024.4, 2025.1 or 2025.2
  • Utilizing SNMPWalk, SNMP is properly returning interface data with:
    • error-status: noError (0)
    • error-index is a non-zero

Product section

Orion Platform

Cause

This error message occurs due to a change for Asset Inventory SNMP polling in SolarWinds Platform 2024.4 where SNMP response has a error-index populated with a non-zero.  This issues will impact the following versions:

 

  • SolarWinds Platform 2024.4
  • SolarWinds Platform 2024.4.1
  • SolarWinds Platform 2025.1
  • SolarWinds Platform 2025.1.1
  • SolarWinds Platform 2025.2

Resolution

To resolve this problem, please upgrade to SolarWinds Platform 2025.2.1 and above.  To immediately fix this problem, perform following one of the following workarounds:

Workaround 1

  • When performing List Resources or Discover Interfaces, change the node to SNMPv1, then run discovery again.  Once network interfaces are found, then change back to SNMPv2 or v3 for polling.

Workaround 2:

  • Utilizing the PowerShell script (below) to invoke SWIS verbs Orion.NPM.Interfaces DiscoverInterfacesOnNode and Orion.NPM.Interfaces AddInterfacesOnNode.
# This sample script demonstrates the use of two verbs provided for adding
# NPM interfaces:
# o  Orion.NPM.Intefaces.DiscoverInterfacesOnNode
# o  Orion.NPM.Interfaces.AddInterfacesOnNode
#
# Note: These verbs are provided by SWISv3 only.
#
# The script lists all interfaces on a specified node and adds only
# selected interfaces to monitor.
#
# Please update the hostname and credential setup below to match your
# configuration, as well as the nodeId variable to refer the existing node to use.

Install-Module SwisPowerShell
Import-Module SwisPowerShell

# Connect to SWIS
$hostname = "localhost"
$username = "admin"

$password = convertto-securestring -String "<Password>" -AsPlainText -Force

$SWIS_Credentials = new-object -typename System.Management.Automation.PSCredential -argumentlist $username, $password
$swis = Connect-Swis -Credential $SWIS_Credentials

# The node ID to discovery interfaces on
$nodeId = <NodeID>

# Discover interfaces on the node
$discovered = Invoke-SwisVerb $swis Orion.NPM.Interfaces DiscoverInterfacesOnNode $nodeId

if ($discovered.Result -ne "Succeed") {
    Write-Host "Interface discovery failed."
}
else {
    # Uncomment one of the following to limit the interfaces that get added:

    # No. 1: Remove interfaces that are NOT ifType 6 (FastEthernet)
    # $discovered.DiscoveredInterfaces.DiscoveredLiteInterface | ?{ $_.ifType -ne 6 } | %{ $discovered.DiscoveredInterfaces.RemoveChild($_) | Out-Null }

    # No. 2: Remove interfaces that have a caption of 'lo' (Loopback)
    #$discovered.DiscoveredInterfaces.DiscoveredLiteInterface | ?{ $_.Caption.InnerText -eq 'lo' } | %{ $discovered.DiscoveredInterfaces.RemoveChild($_) | Out-Null }

    # Add the remaining interfaces
    Invoke-SwisVerb $swis Orion.NPM.Interfaces AddInterfacesOnNode @($nodeId, $discovered.DiscoveredInterfaces, "AddDefaultPollers") | Out-Null
}