Receiving "Hardware polling failed: Error 31224" when using SNMPv3 polling in NPM

footerest

A few days ago I noticed that the interface status for all switch interfaces had changed to "unknown" for all switches being monitored via SNMPv3.  For 2 switches using SNMPv2 they are still working fine.

The full message I am receiving is "Hardware polling failed: Error 31224 - Crypto Error - Unable to perform the requested algorithm. If FIPS restrictions are enabled, please select a FIPS compliant algorithm."

   I am assuming that something changed on the Solarwinds server doing the polling.  Any ideas what may have changed?

bluemule

I don't know if this is too little too late, but the same thing happened to me yesterday afternoon.  I resolved the problem earlier this morning.

The first thing I did was log into my SolarWinds Application Server, then I opened up the Orion Services menu (Start/All Programs/SolarWinds Orion/Advanced Features/Orion Service Manager).  I also opened up the standard Windows Server 2008 R2 Services window and took a look around.  While doing this, I discovered the Orion Module Engine service kept shutting itself off and turning back on every five minutes or so.  The SW web interface kept crashing and reporting a port 17777 "no endpoint listening" error.

I then did a search for the Orion Module Engine service issue.  The recommended fix was to repair several of the Orion modules from Windows Start/Control Panel/Programs and Features, beginning with the SolarWinds Job Engine.  Attempts to repair the Job Engine failed.  I received a "fatal error" message.

With that, I decided to re-install SolarWinds Network Performance Monitor (NPM 11.5.2 in my case).  This fixed it.  SNMPv3 began working again, and so did Hardware Health Monitoring.

Root cause of the original issue unknown.

Kind regards!