TECHZEN Zenoss User Community ARCHIVE  

Modeler plugin - zenoss.snmp.SnmpV3EngineIdMap

Subject: Modeler plugin - zenoss.snmp.SnmpV3EngineIdMap
Author: Sam Urai
Posted: 2022-01-14 11:48

Hi,

I would like to switch from Snmp v2c to v3 on Zenoss 4.2.5 Core. Does anyone know where to find this plugin - zenoss.snmp.SnmpV3EngineIdMap ? 

Does it help to set an Engine ID automatically?

Thanks


------------------------------
Sam
------------------------------


Subject: RE: Modeler plugin - zenoss.snmp.SnmpV3EngineIdMap
Author: Michael Rogers
Posted: 2022-01-14 15:13

Sam,

The SnmpV3EngineIdMap plugin should be available from the normal modeler plugin selection screen along with the other modeler plugins:


It should poll the SNMP engine ID OID from a device while it models and then set that value as a device-local value on the zSnmpEngineId zProperty.  It's also possible to set the zProp manually, but that's typically not feasible beyond a few devices.

Before switching all of the relevant SNMP zProps for an entire device class, I would recommend starting with a new child class under the current class.  Move a few test devices to the new class and make changes to zProps there.  If configuration issues cause gaps in monitoring, the problem will be constrained to just those test devices.  When the target devices are working as intended, you can move the others to the child class, or alter the original class to match the child.  I would recommend moving devices to the child class to keep them separated by protocol, in case you have devices that can't be switched from SNMP v2c.


------------------------------
Michael J. Rogers
Senior Instructor - Zenoss
Austin TX
------------------------------


Subject: RE: Modeler plugin - zenoss.snmp.SnmpV3EngineIdMap
Author: Sam Urai
Posted: 2022-01-14 16:33

Thanks Michael. That's a good piece of information to consider for switching the devices to snmp v3.  

I don't have the SnmpV3EngineIdMap plugin in the available modeler plugins list. I'm not sure why not and wonder how to get it.

Update: In another 4.2.5 Core instance,  I do see it.  Can it be copied over to this instance?

Thanks


------------------------------
Sam
------------------------------


Subject: RE: Modeler plugin - zenoss.snmp.SnmpV3EngineIdMap
Author: Michael Rogers
Posted: 2022-01-14 16:54

Sam,

Modeler plugins are typically added to the system via product updates (for 4.2.5, that would be an RPS) or via ZenPacks.  I was under the impression that the SnmpV3EngineIdMap plugin was part of the product itself and didn't come from an RPS or a ZenPack.  

It might be possible to simply copy the plugin .py file from one instance to the other, but that just gets the plugin onto the disk.  Without an RPS or ZenPack install, Zenoss doesn't really "know" that the plugin is on disk.

Do you know if these two 4.2.5 installations are on the same RPS version?  Do they have the same list of installed ZenPacks?


------------------------------
Michael J. Rogers
Senior Instructor - Zenoss
Austin TX
------------------------------


Subject: RE: Modeler plugin - zenoss.snmp.SnmpV3EngineIdMap
Author: Sam Urai
Posted: 2022-01-21 12:40

Looks like both instances were installed with 4.2.5 autodeploy script back in 2015 and I don't see zenup installed. Is there a way to find out the current RPS version installed ? 
The installed Zenpacks list is similar between the 2 instances. 

Thanks

------------------------------
Sam
------------------------------


Subject: RE: Modeler plugin - zenoss.snmp.SnmpV3EngineIdMap
Author: Michael Rogers
Posted: 2022-01-24 17:11

Sam,

Prior to the introduction of zenup, patches were managed with the quilt utility.  If either system has an /opt/zenup directory, it's possible that zenup was previously installed but later removed for some reason.  

I did some additional digging and it appears that the plugin in question was introduced in 4.2.4 via RPS SP525, and in 4.2.5 via RPS SP136.

If both of your instances are 4.2.5, but one of them was upgraded from 4.2.4 after SP525 was applied, that might account for the discrepancy.  If you plan to upgrade one or both systems to the latest 4.2.5 RPS (SP743), I would recommend taking a backup first.  (Or, if it's a VM, just clone it and perform the upgrade on the clone and swap it in.)

I hope this helps!

------------------------------
Michael J. Rogers
Senior Instructor - Zenoss
Austin TX
------------------------------


Subject: RE: Modeler plugin - zenoss.snmp.SnmpV3EngineIdMap
Author: Sam Urai
Posted: 2022-01-27 18:56

I had no know idea about "quilt" utility so thank you for sharing that information.   Since I want to know what RPS/SP version currently I've, I came across across "zencheckkrps" script which use it.  But it didn't work for me as zenquilt_update.sh doesn't exist on my Zenoss hosts. I couldn't find it online either.

VM clone strategy to perform the upgrade is I think would be better option for me. 

Thanks

------------------------------
Sam
------------------------------


< Previous
Zenoss 4.2.5 - Not able to set device production state
  Next
Zenoss 4.2.5 - Zeneventserver error - Deadlock detected - General failure indexi ...
>