Changed SNMP version, now can't collect statistics

My environment recently changed our SNMP version from SNMP2c to SNMPv3. I can go through and change the credentials for the devices in bulk, but it seems to not take, and the interfaces show an 'unknown' status. Now all we have is ping, so we are missing T1 bandwidth utilization for 700 remote sites.

Is there any EASY way to get them all working again? I hate to remove and re-add all of the routers since most of them have VoIP and discovery takes a long time.

HELP!

Find more posts tagged with

snmpv2

snmpv3

Accepted answers

jlintner

My original problem was not if SNMPv3 would work, but rather this:

I had over 700 devices/sites polling using SNMPv2c, collecting stats on mainly the serial interfaces on our routers along with CPU and memory utilization. We had a mandate to stop using SNMPv2c and use only SNMPv3. No problem, right? Configure the router with the V3 details (user, group, view, etc) and they would poll. But, try changing the SNMPv2c polled device properties to use SNMPv3 credentials - can't retain any of the historical data - it wouldn't automatically re-discover the device and interfaces again - it would only say 'unknown status'. The only answer was to remove all interfaces then rediscover/re-add the device using the V3 credentials - 700+ times! It took three of us working in our spare time to get it completed in a couple of weeks.

SNMPv3 polling was never an issue; it was changing devices from SNMPv2c to use SNMPv3 credentials in Orion NPM!

Now, if Solarwinds can solve the SNMPv3 trap issue we'd be good!

All comments

neilmborilla

Roll it back to SNMP2c

bshopp

What version are you currently on?

jlintner

Sorry - I'm running NPM 9.1, SP5.

bshopp

I would recommend upgrading to 9.5 and seeing if the issue goes away as we fixed some issues around SNMPv3.

afarmer

I usually click poll and rediscovery when I upgrade mine from SNMPv2c to SNMPv3 or wait until the next rediscovery interval. Is rediscovery what you are referring to as taking a long time? I haven't had any problems with mine. This was in 9.1 and now I have 9.5 but it was the same in both.

wsl

I am using 9.5 SP3 and setting up SNMPv3 polling to Cisco IOS 12.2 ..I am able to validate snmp credentials but machine type is " unknown"...if I do a list resources, there are no interfaces that show up but I am able to see interfaces if i click the node...seems like SNMPv3 is partially working. I have added these parameters on the device

snmp-server view Orion_view internet included

snmp-server view Orion_view system included

snmp-server view Orion_view interfaces included

snmp-server view Orion_view chassis included

Node Status		Node status is Up.
	IP Address		10.64.0.1
	Dynamic IP		No
	Machine Type		Unknown
	DNS
	System Name
	Description
	Location
	Contact
	Last Boot		Thursday, April 23, 2009 4:13 AM
	Operating System
	IOS Image		Unknown
	Hardware		Physical
	Telnet		telnet://10.64.0.1
	Web Browse		http://10.64.0.1

jlintner

My original problem was not if SNMPv3 would work, but rather this:

SNMPv3 polling was never an issue; it was changing devices from SNMPv2c to use SNMPv3 credentials in Orion NPM!

Now, if Solarwinds can solve the SNMPv3 trap issue we'd be good!

Sol

We have the exact same problem: Cisco 3750 running snmp v2c, changed to SNMP v3, and suddenly we have no SNMP data, only PING data. This problem was reported over a year ago, what is the fix? Blowing away the device and historical data is not a viable solution!

bshopp

We have a bug in 10.1 where if you want to pick up the change you need to restart the netperfmon service. This is fixed in NPM 10.1.2 which is currently in RC and available in your portal now

supahabs

anyone know if changing from SNMPv2 to SNMPv3 with version NPM 10.4.2, will wipe out the historical data?

shuth

Changing to SNMPv3 in NPM 10.4.2 should NOT wipe out your historical data. I have changed from SNMP v2 to v3 in NPM 10.2.2, 10.3.x and 10.4.x with no issues.

I just double checked for you in a lab running 10.4.2 and the node has continued polling (see screencap). The double data point at around 18:55 is a forced poll after SNMPv3 was configured.