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

SNMP v3 issue in NPM 9.1 SP1

charly_DF

Recently we migrate all our nodes from SNMP v2c to SNMP V3,

but actually, some some times the collection of data stops,

and is required re-ingress the SNMP v3 credentials of the nodes

in status Unknown on Orion!!!!

Help!!!!!!

Find more posts tagged with

Accepted answers

charly_DF

try with SP5, on fixes list it is our bug :-)

All comments

rajivbahl

Even i have this issue due to which i am unable to upgrade to 9.1

All my approx 800 devices are working on SNMPv3 and poller is unable to poll any of them after few cycles of poll. even restarting the NPM service or server itself does not help.

If i downgrade to 9.0 SP2 everything works just fine.

FormerMember

Have you each opened a Support ticket?

rajivbahl

Yes the support ticket is opened

Case #64859 - "Unable to poll CPU utilization after upgrading to NPM 9.1 on SNMPv3"

Opened since : 23/10/2008

Case #63695 - "Unable to poll CPU utilization after upgrading to NPM 9.1"

opened on 16/10/2008

Support team is still working on this and no fixup received till date. I am stuck on NPM9.0 SP2 and cannot upgrade

Case #63695 - "Unable to poll CPU utilization after upgrading to NPM 9.1"

FormerMember

I've checked on your issue, and engineering is investigating it.

I thought it was just me - The nodes are online, they poll fine, but I have to re-add all of the nodes every once in a while whenever I use snmp v3.

This happens whenever the node can't poll for a short while (like an access list, or outage), and it comes up again. I know the interface IDs are the same, but they appear 'blue' on the web interface implying it's unmanagable.

Karlo.Zatylny

Is this just for Cisco devices? Can anyone confirm or deny?

If anyone else is having this issue, please call support and get us diagnostics.

Thanks

I carefully validated my configuration. I was missing a specific SNMP view that was preventing my nodes from being able to poll. This was administrative error on the router and not the fault of solarwinds.

My minumum view for solarwinds is:

snmp-server view monitoring system included
snmp-server view monitoring interfaces included
snmp-server view monitoring ip included
snmp-server view monitoring ciscoMgmt included
snmp-server view monitoring chassis included
snmp-server view monitoring iso included