asked on

Migration to SNMPv3

I am researching and testing migrating to SNMPv3 from SNMPv2c on Cisco networking equipment. We are a small company (Approx. 30 routers and switches) and we monitor the network using SolarWinds NPM and have had no problems getting event notifications when gear bounces or monitored interfaces bounce. Based on that alone I am thinking that what we have configured generates adequate information/notifications so that all that has to be done to migrate is peel off the SNMPv2c config and add SNMPv3 config.

My question is two fold. Is my train of thought accurate? Secondly, if I specify OID(s) and or specific traps to be generated will the only notifications we receive be the ones specified?

Current SNMPv2c config:
snmp-server community xxxxx RW
snmp-server location yyyyy
snmp-server contact zzzzz@iii.com
snmp-server chassis-id somerouter
snmp-server host x.x.x.x version 2c xxxxx

Proposed Config:
snmp-server group xxx v3 priv
snmp-server user someuser xxx v3 auth sha ooooo priv des ppppp
snmp-server location xyxyxyxyx
snmp-server contact zzzzz@iii.com
snmp-server chassis-id xxxxx
snmp-server host x.x.x.x version 3 priv xtrewq

Steve Jennings

Hello . . . is this still an issue? The question is quite old.

I'd simply configure a single device with SNMPv3 and make sure it's still reachable from Solar Winds . . . configure SNMPv3 on the device and Solar Winds . . . then pull an interface cable or somehow generate a trap to make sure you are receiving traps.

Have fun!
Steve

This question needs an answer!

Become an EE member today

7 DAY FREE TRIAL

Members can start a 7-Day Free trial then enjoy unlimited access to the platform.

View membership options

Learn why we charge membership fees

We get it - no one likes a content blocker. Take one extra minute and find out why we block content.