“SNMP polling is failing” Critical node status for Cisco Meraki devices in SolarWinds Platform 2026.1

2/20/2026 3:41 PM

3/30/2026 10:10 PM

After upgrading to SolarWinds Platform 2026.1, node-status behavior was changed that surfaces polling errors and changes the node status to Critical.

Core.Node.Uptime.Snmp.log may contain the following error message:

ERROR DataPreProcessing - Processing result:
PollerResultWrapper: PollerType=N.Uptime.SNMP.Generic,
NetObject=N:1001
ErrorCode=791A,
ErrorMessage=Error 31002 - Invalid OID-1.3.6.1.2.1.1.3.0-ValueType-NoSuchObject

 

• The poller N.Uptime.SNMP.Generic is attempting to read Uptime from OID 1.3.6.1.2.1.1.3.0 (sysUpTime).
• The device returns NoSuchObject for that OID, causing a repeated polling error.

SNMP connectivity is successful, but the repeated failure of sysUpTime will flag the node with “SNMP polling is failing” and mark it Critical.

Symptoms:

The following symptoms may be observed:

• Node status shows Critical with message ‘SNMP polling is failing’.”
• The Test operation for the configured SNMP credentials on the node succeeds.
• Other SNMP-based statistics continue to update.
• Running an SNMP test / SNMP walk to the same Meraki MX from the polling engine succeeds, confirming SNMP is working even though SolarWinds reports ‘SNMP polling is failing’.
• The issue may affect some or all Meraki MX devices; it can appear randomly across Meraki nodes.
• This issue started after upgrading to SolarWinds Platform 2026.1.

This issue is reported with Cisco Meraki devices, but this will apply to any device that does not respond to sysUpTime.

Hybrid Cloud Observability

This issue occurs due to the recent logic change in node-status behavior in SolarWinds Platform 2026.1 where:

 

1. Device capability
• The N.Uptime.SNMP.Generic poller relies on the standard sysUpTime OID:
  1.3.6.1.2.1.1.3.0.
• Certain devices, including some Cisco Meraki MX models, do not expose sysUpTime via SNMP.
• When the OID does not exist, the poller has nothing to query and repeatedly reports an error.
2. Poller assignment behavior
• In current versions, the generic SNMP uptime poller is assigned to SNMP nodes regardless of whether they support sysUpTime.
• On devices that do not publish this OID, the poller will always fail.
3. Enhanced status behavior in 2026.1
   • The SNMP credentials are correct.
   • Other SNMP polling is functioning normally.
• SolarWinds Platform 2026.1 includes an enhancement that tracks persistent poller errors and surfaces them as Polling Issues, affecting node status.
• This enhancement makes the long‑standing assignment behavior more visible as a Critical status with “SNMP polling is failing”, even though:

To resolve this issue, please upgrade to SolarWinds Platform 2026.1.1 and above.  If upgrade is not possible, please use the workaround below.

Workaround – Disable the generic SNMP uptime poller for Meraki devices (advanced / SQL)

These steps will:

• Keep the enhanced Polling Issues behavior for devices that rely on it.
• Avoid false‑positive “SNMP polling is failing” status on devices that do not support sysUpTime, such as certain Cisco Meraki MX/MR models.

This approach disables the N.Uptime.SNMP.Generic poller for specific device types by using a SQL update against the SolarWinds database.

 

1. Connect to the SolarWinds database using SQL Server Management Studio or Database Manager.
2. Run the following query against the SolarWinds database to disable the generic SNMP uptime poller for devices whose machine type matches Cisco Meraki:

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

UPDATE p
SET p.Enabled = 0
FROM Pollers p
INNER JOIN NodesData nd
    ON p.NetObjectType = 'N'
   AND p.NetObjectID  = nd.NodeID
WHERE p.PollerType = 'N.Uptime.SNMP.Generic'
  AND p.Enabled    = 1
  AND (
        nd.MachineType LIKE 'Cisco Meraki MX%'
     OR nd.MachineType LIKE 'Cisco Meraki MR%'
      );

3. After running the script, restart the SolarWinds Collector and Job Engine services.

Once completed, verify the following:

• • Confirm that N.Uptime.SNMP.Generic is no longer enabled for the affected Meraki nodes.
  • Monitor the nodes’ status and Polling Issues panel to ensure “SNMP polling is failing” no longer appears solely due to the missing sysUpTime OID.

To ensure current nodes recalculate their status under the new configuration:

• Temporarily Unmanage and then Remanage the affected nodes (for example, via Settings > Manage Nodes), or
• Allow normal polling cycles to run so status is recalculated.