nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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
Store

SNMPv3

bleearg13

Does anyone have SNMPv3 running with Cirrus? I'm trying to add my first Cirrus node in that is using v3 and I'm having some trouble. I have the same exact settings in Cirrus as I do in Orion, but for some reason, Cirrus cannot poll the device. In Orion (which is on the same server), I have no context configured, but in Cirrus, it seems that I need a context, or I get an authorization failure when attempting to validate the SNMP credentials. However, with the context in, the SNMP validation passes, but no information is populated, such as the System OID and name. My SNMPv3 view on the router is configured to allow this particular user (the same user that is configured in Orion) to view the entire 1.3 tree. Here's my settings in Cirrus:

SNMP Version: 3
Context: context1
Username: noc
Auth Type: SHA1
Auth Password: <auth_pass>
Encryption Type: AES128
Encryption Password: <encryption_pass>

Is there something I'm missing?

Find more posts tagged with

Accepted answers

chris.lapoint

For folks experiencing this issue, please contact support to get this hotfix.

All comments

ceclark

Looks good to me. The only difference I see from my configs is the encryption type. I'm using DES. What platform is this that it supports AES?

bleearg13

Juniper routers.

ceclark

I wish I had one! I guess I'm not too much help anymore, sorry.

kkunzler

I have Cirrusv5 running SNMPv3 with my Cisco gear. It appears from my testing that SHA-1 is NOT supported by solarwinds, but rather the older (archaic and mostly unused) original SHA algorithm. Of course it could be my Cisco gear is the wrong version, but anyhow they refuse to talk to each other useing SHA. I can get my Cisco gear to to use md5 for auth and aes for encryption, but have never been able to use sha for authentication. Everything else seems correct, here is exactly what I have today:

SNMP Version: 3
Context: <blank>
Username: solarwinds
Auth Type: md5
Auth Password: <auth_pass>
Encryption Type: AES128
Encryption Password: <encryption_pass>

This is a call-out to Solarwinds to support proper SHA-1 for authentication of SNMPv3.

chris.lapoint

For folks experiencing this issue, how long is your password?

bleearg13

The user password or the privacy password? My privacy password is 20 characters long and includes symbols.

kkunzler

I have tested this with 4-5 character all text auth passwords as well as 15 character passwords and am unable to get SHA working against my Cisco gear. I must redact my call-out to Solarwinds as It seems that I placed the blame on them, in reality, I am unsure whether my Cisco gear is SHA or SHA-1. It seems that one or the other is sha and the other sha-1 possibly causing the issue for me, I can't speak for Juniper though. MD5 works well for auth no matter the size of password.

jcooler

Please help!

I am attempting to add a few nodes to NCM using snmp v3 but snmp will not validate.

The nodes work perfect in Orion NPM, using the exact same snmpV3 settings/credentials.

I am using the following:

context [blank]

auth type: MD5

auth pass: [30 chars with several special chars]

encrypt pass: [30 chars with several special chars]

Any ideas on why NCM will not authenticate with snmp v3?

ShamChauthani

What version of NCM are you using?

jcooler

lastest version.

NCM v5.5.1