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

Error in SNMPV3

rafaelPISE4

Good afternoon everyone, how are you?

I'm having a strange problem setting up a server using the SNMPv3 protocol.

Testing on the node results in an error.

I've already checked the port, firewall blocking, and I can't find the problem.

Since I'm starting with Self Hosted, where can I find the logs to see what the problem might be?

Find more posts tagged with

sam

npm

Comments

Lofstrand

SNMP is hard to troubleshoot in that way that it doesn't say much where the issue is. I usually use some third-party snmp testing tool, there are several out there, install it on the polling engine and run if from there. Can be easier and faster to test different settings.

One tool ca be the in solarwinds built in SNMPWalk tool.

With SNMPv3, check if you have the correct encryption ciphers chosen in both ends.

vinay.by

SNMPv3 prerequisites and checks

SNMP credentials for the SolarWinds Platform

How to configure SNMPv3 - THWACK

bourlis

Hi rafaelPISE4,

Can you supply any details, like the type of server, is the SNMP v3 settings in an application or in the OS itself, what's the error message, edited example of your SNMP settings?

When I first implemented SNMPv3, whenever I ran into a wall I always rolled back to the simplest version of SNMPv3 and worked up from there. For example,

Get a baseline with SNMPv3 user only.
1. NoAuthNoPriv: No authentication or privacy (least secure).
  1. If that work move to step 2
Introduce Authentication protocols with known working SNMPv3 user.
1. AuthNoPriv: Authentication but no encryption
  1. First introduce MD5 auth (less secure).
    1. If that works, try a more secure version.
  2. Next introduce SHA auth (more secure).
    1. If that works, move to step 3.
Introduce Privacy protocols, with known working SNMPv3 user and Auth protocol.
1. AuthPriv: both auth and privacy.
  1. First introduce DES (less secure).
    1. If that works, move to the next step.
  2. Next introduce AES (more secure)

It's worth nothing that some systems lesser Auth/Priv version, but most systems default to SHA-256 & AES-128 but I've seen some lesser versions. I would start with those and then play around from there.

Also make good notes as you test!!!

Also do more product specific searches, I've seen applications that require OID information in the SNMPv3 settings or a hex mask setting.

rafaelPISE4

Good afternoon, how are you @bourlis?

The user uses authentication without encryption.

Using MIB Walker, with the same credentials and specific OID, it retrieves the information I need, but using the credentials in Orion, the test fails.

It's a cloud server, an Ubuntu server, and we are using SNMPv3 there.

rafaelPISE4

In your case, scenario two, MD5 along with the password and without encryption.

Using it this way in MIB WALK, it worked.

Lofstrand

It's not that you can't PING the device from the SolarWinds server? When you add a node in SolarWinds it tries to ping the node first, if that fails the error might look the same as when SNMP fails.

Try to ping the node from the server to see if that works. If not, there is your issue.

rafaelPISE4

Good morning friend... yes, it pings normally and even the TNC tests via PowerShell work perfectly, that's what I find strange.

TerryHarding

Check that the following OIDs are correctly reported:

1.3.6.1.2.1.1.1.0 sysdescr
1.3.6.1.2.1.1.2.0 sysobjectid
1.3.6.1.2.1.1.3.0 sysuptime

cnorborg

One of my first steps is to always try it using SNMP v2c with a simple community. If that doesn't work, SNMPv3 won't work either. If that works, then try it using a >very< simple auth/priv passwords, just characters and not too long. If that works, you have a problem with your password of some sort…