SNMPv3 test credential failed to authenticate

brichardi
Kilo Contributor

Hello,

I have created snmpv3 and test it against a printer and keep getting "Authenticate failure".   I have tested this snmpv3 account using Solarwinds, and download Paessler snmp tester tool and they both successful.   I have used all of the encryption combination that I can think of and its still not working.

Your help is appreciated.

Thanks

6 REPLIES 6

Johan van den H
Kilo Sage

Hi Brichardi,

Has this issue been solved yet?
We are facing the same problem.

Kind regards,
Johan van den Hoven

Shekhar Deshing
Mega Expert

I guess You can check the PowerShell Version it should be above V2.0 on windows.

Because last time it was giving an error for me as 'Authentication Failure' on local system so I upgraded PowerShell version and restarted MID server.

Thanks 

 

Shekhar Deshing
Mega Expert

I am not sure what environment you are using however You can check the Logs for where you installed MID server :

C:\<mid server locatio>\agent\logs\agent0.log (file) you can verify if you are getting an error there related to your authentication.

 

 

Johan van den H
Kilo Sage

We are running PowerShell 5.1

 

Error message from agent0.log:

03/26/19 13:35:08 (124) Worker-Interactive:CommandPipeline-b9e70327db5c7780e953b29f2996192e Worker starting: CommandPipeline source: 10.90.128.3
03/26/19 13:35:12 (639) Worker-Interactive:CommandPipeline-b9e70327db5c7780e953b29f2996192e Enqueuing: C:\install\Servicenow\MIDserver-extract\agent\work\monitors\ECCSender\output_0\ecc_queue.b9e70327db5c7780e953b29f2996192e.xml
03/26/19 13:35:12 (639) Worker-Interactive:CommandPipeline-b9e70327db5c7780e953b29f2996192e Worker completed: CommandPipeline source: 10.90.128.3 time: 0:00:04.515
03/26/19 13:35:13 (077) ECCSender.1 Sending ecc_queue.b9e70327db5c7780e953b29f2996192e.xml
03/26/19 13:35:39 (487) LogStatusMonitor.60 stats threads: 84, memory max: 910.0mb, allocated: 792.0mb, used: 139.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes