Report to list nodes with polling issues in SolarWinds Platform 2026.1

2/12/2026 10:47 PM

2/12/2026 10:47 PM

In SolarWinds Platform 2026.1, node status can change to Critical or Misconfigured when core SNMP, WMI, or WinRM polling fails repeatedly, even though the device still responds to ICMP (ping).

Examples:

• Node status is Critical, SNMP polling is failing: 'Request timed out - possible causes include network issues, incorrect community string or SNMPv3 credentials, or device not responding.'
• Node status is Misconfigured, Wmi polling is failing: 'The user name or password is incorrect.'

Internally, these nodes are also flagged with a property that indicates a polling error. Instead of clicking each node individually, you can create a report that lists all such nodes in one place, with the most important fields on a single screen.

This KB shows how to build that report using the web‑based report wizard and a custom table based on Nodes.

Hybrid Cloud Observability

This article describes a recommended configuration, not a defect.

Without a central report:

• Nodes with polling issues may only be visible through alerts or by opening individual Node Details pages.
• After upgrading to 2026.1, customers may suddenly see many nodes in Critical/Misconfigured states with “polling is failing” messages and have no simple way to see all affected nodes.

A dedicated report makes it easier to:

• Triage after upgrades
• Prioritize remediation by criticality, site, or environment
• Distinguish polling issues from true node down conditions

Follow the steps below to create a Custom Table report that lists nodes with polling issues.

1. Decide which columns you want in the report

Suggested columns:

• Node:
• Node Name / Caption
• IP Address
• Status information:
• Status (for example, Up, Critical, Misconfigured)
• Status Description (for example, “SNMP polling is failing: …”)
• Polling context:
• Polling Engine (Engine Name or Engine ID)
• Polling Method (for example, SNMP, WMI/WinRM, Agent) – if available in your version
• Environment context (optional):
• Custom property for Environment (for example, Production/Test)
• Custom property for Site / Location
• Any other custom properties your organization uses (Owner, Region, Business Unit, etc.)

These fields give you a clear view of “who is affected,” “how badly,” and “where.”

 

2. Create a new Custom Table report

1. In the SolarWinds web console, go to Reports > All Reports (or Reports > Manage Reports depending on your version).
2. Click Create New Report.
3. Choose Custom Table as the report type and click Next.

 

3. Configure the data source (Nodes)

1. When prompted for what the report should show, choose Nodes as the data source.
2. In the Custom Table wizard:
• Set the Object Type to Node (Orion.Nodes).
• Confirm that the data is coming from the Nodes entity, not from interfaces or other objects.

 

4. Filter the table to only show nodes with polling issues

Still in the Custom Table wizard, configure the Filters:

1. Add a filter row for “Is Polling Error”:
• Is Polling Error is equal to True
• 

 

5. Select and arrange the columns

In the Columns step of the Custom Table:

1. Add the following columns (names may differ slightly by version):
   • Environment
   • Site / Location
   • Region
   • Owner / Business Unit
• Caption (or Node Name)
• IP Address
• Status
• Status Description
• EngineID
• Any custom properties you use for grouping or ownership, such as:
2. Arrange the columns in an order that makes sense for your operations team, for example:
1. Caption
2. IP Address
3. Status
4. Status Description
5. EngineID
6. Environment
7. Site

 

6. Sorting and grouping (optional but recommended)

On the Layout or Sort / Group step:

• Sort by:
• Status descending (so Critical shows before Misconfigured)
• Then Node Name / Caption ascending
• Optionally group by:
• Environment (custom property)
• Site / Location

This helps you see, for example, “all Production nodes with polling issues” or “all nodes at a given site.”

 

7. Name, save, and schedule the report

1. Give the report a clear name, for example:
• “Nodes with polling issues (Critical/Misconfigured)”
2. (Optional) Add a short description:
• “Shows nodes that are Critical or Misconfigured because SNMP/WMI/WinRM polling is failing while ICMP is still working.”
3. Choose a report **category** such as:
• Node & Group Reports
• Troubleshooting / Health
4. Save the report.
5. (Optional) Configure a schedule to email this report to operations or NOC teams regularly, especially after upgrades, or add it to a shared dashboard as a resource.