TECHZEN Zenoss User Community ARCHIVE  

Switching between SNMP v2c and v3

Subject: Switching between SNMP v2c and v3
Author: Shea Johnson
Posted: 2018-07-27 12:13

I am running Zenoss Core 4.2 and had been running SNMP v2c to monitor Red Hat workstations. I have since switched over to SNMP v3, but now have alarms coming in saying that "SNMP agent down", "unable to read processes on device" and "does not publish "HOST-RESOURCE-MIB". I can SNMP v3 walk the host and I can model the host as well. When I look at the performance data, all the stats show "-nan" so I'm not getting those data points.

When I added SNMP v3 I ran the following:
service snmpd stop
net-snmp-create-v3-user -ro -A snmpv3authPass -a SHA -X snmpv3encPass -x AES snmpv3user
service snmpd start
The output then showed:
adding the following line to /var/lib/net-snmp/snmpd.conf:
createUser snmpv3user SHA "snmpv3authPass" AES snmpv3encPass
adding the following line to /etc/snmp/snmpd.conf:
rouser snmpv3user

I also updated the following fields in Zenoss:

Do I need to additional updates or configuration changes? Did I miss something? Thanks for your help in advance!

-Shea


Subject: RE: Switching between SNMP v2c and v3
Author: Chris De Coster
Posted: 2019-05-07 15:08

Hi, maybe a little late...
Zenoss takes the "snmpv3 engine ID" into account.
This has to be unique per server you monitor. 

Zenoss has a plugin that you can use to set the engineID in the configuration.

------------------------------
Chris De Coster
------------------------------


Subject: RE: Switching between SNMP v2c and v3
Author: Jay Stanley
Posted: 2019-05-09 07:59

Yeah, make sure you add the modeler 'zenoss.snmp.SnmpV3EngineIdMap' as the first modeler in the list on the device class or device and Zenoss will set the engine ID zProp during modeling

------------------------------
jstanley
------------------------------


< Previous
Service is not getting started
  Next
Zenoss 6 Core missing ZenJMX Container
>