Network Management

List Resources Error in NPM

The following error is displayed when performing List Resources on a node, which has a successful credentials test (SNMP/WMI) and can successfully pull statistics via SNMPWALK or WBEMTest: Node is currently down, unreachable, or provided credentials are not valid.

First published date

10/25/2018 8:35 PM

Last published date

10/5/2021 11:40 AM

Overview

The following error is displayed when performing List Resources on a node:

Node is currently down, unreachable, or provided credentials are not valid


Sometimes it may appear after clicking Force Refresh due to the caching that takes place on the List Resources page. The message may also be visible on the node details page for the node. There are several known common issues for this message.

Product section

Network Performance Monitor

Cause

The true cause may not be addressed by this article because causes can vary so widely. Basically, the issue is that SolarWinds cannot make a connection from the polling engine to the SNMP node in question. This mostly commonly occurs for the following three changes that are regular actions performed against snmp node:
  • List Resources need to be refreshed
  • Credentials/community are no longer valid
  • Node is down
  • SNMP packets are allowed per host

Resolution

First, obtain the current status of the node by clearing the cached List Resources on the page. 
  1. Click List Resources on the node
  2. Click Force Refresh

Sometimes, the error message will be displayed until the cached list resources is refreshed. 

Verify the following:

  • Node is up. Pinging the IP address from the polling engine assigned to the node is a valid test.
  • SNMP tests successfully with SNMPwalk. Run SolarWinds SNMP Walk.
If either test fails above you will want to consult with your Network or firewall team. You will also need to confirm the SNMP settings of the device. It is common that the IP or hostname of your Orion server has changed (due to migration or High Availability failover are the most common reasons) and the SNMP packets are not allowed to be read by the new hostname/IP.

For Windows Devices: You can verify the settings on the Security tab of the SNMP Windows Service Properties window (On snmp device > Start > Run > Services.msc > snmp service > right-click > Properties > security).

(Screenshots property of © 2021 Microsoft)

For non-Windows devices: Contact the vendor for assistance with proper SNMP configuration.