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

Any tuturial on configuring SNMPv3 on Cisco Routers for NPM?

I got SNMP on all my servers, but for my network devices I want to configure SNMPv3 for security reasons. I've search the web for a bit and haven't been too successful is there any documentation provided here with the bare bones of configuring SNMPv3 on Cisco Devices?

Find more posts tagged with

Accepted answers

SOcchiogrosso

I used the same configuration on another router and it worked fine, so I am thinking this is an isolated issue with one router.

I'll be looking into this further as time goes on.

All comments

bshopp

Please see my last post here

SOcchiogrosso

Ok, I will read through that.

In the meantime I found this https://www.packetpros.com/ in Miscellanous \ NPM SNMPv3

I submitted the following commands to my router:

snmp-server view ORIONNPM interfaces included

snmp-server group MyGroup v3 auth read ORIONNPM

snmp-server user MyUser MyGroup v3 auth md5 xxxxxxxx priv des56 xxxxxx

However when I add the node to the System Manager and put all the credentials it looks like the NPM accepts the credentials, however the NPM hangs on the popup box where is says it's discovering Interfaces and determining supported MIBs...

Could that be an issue with NPM and not my SNMP configuration?

bshopp

Hard to tell, I am thinking though still SNMP. Another method to check if to get a packet capture with wireshark and see if you see the SNMP response coming back from the device to Orion or not

SOcchiogrosso

I used the same configuration on another router and it worked fine, so I am thinking this is an isolated issue with one router.

I'll be looking into this further as time goes on.