Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

SNMP and WMI Failing after upgrade

We migrated our Solarwinds instance from Server 2012 to Server 2019 and upgraded all modules to version 2019.4 on Monday, but now, for some reason, all nodes are showing that SNMP polling has failed and nodes that can be successfully pinged from the Orion server show to be down. Any thoughts or tips? I can't seem to figure it out.

SNMPissues_LI.jpg

Find more posts tagged with

snmp polling failure

Accepted answers

klevans8907

So it turns out that all ping was failing. A systems engineer from my company was able to identify that Windows Firewall (even though it was disabled) was not allowing the Orion Trap Service to communicate out. Once that change was made on the local firewall and the Orion server was rebooted, everything seems to be polling as it should.

All comments

wilder

Check community string or credentials maybe? What happens when you do the SNMP test on the Edit Node Properties page?

Did the server name or IP of the poller change? Maybe devices need to have the new names/ip added in its SNMP service of allowed servers?

adam.beedell

If the last database sync is out of date reset the Collector service

If some nodes on a polling engine have their NextPollUTC date in the past reset the JobEngine service

If neither of those seem appropriate let us know

klevans8907