|
|
| Subject: | Warning with message Problem while executing plugin zenoss.snmp.SnmpV3EngineIdMap |
| Author: | [Not Specified] |
| Posted: | 2015-06-11 06:21 |
Hi everyone, I'm new to zenoss here and would appreciate if someone can help me out.
When modelling a Fortigate firewall, I come across this error in SNMPV3EngineIDMap.
The Warning don't seem fatal, as the device is successfully modelled, however, I'm trying to remove the false positive 'warning' if possible. Thank you!
If I use SNMP v1/2 then the modeller can complete without any errors.
Traceback (most recent call last):
File "/opt/zenoss/Products/DataCollector/zenmodeler.py", line 635, in processClient
datamaps = plugin.process(device, results, self.log)
File "/opt/zenoss/Products/DataCollector/plugins/zenoss/snmp/SnmpV3EngineIdMap.py", line 31, in process
om.setSnmpV3EngineId = binascii.hexlify(om.setSnmpV3EngineId)
TypeError: must be string or buffer, not None
| Subject: | Workaround |
| Author: | [Not Specified] |
| Posted: | 2015-06-11 06:40 |
As a temporary workaround, I've removed the SNMPV3EngineIDMap from the model plugins, what effect does it has on the SNMP process, if any Thanks!
| Subject: | Same issue on Ubuntu 16 |
| Author: | [Not Specified] |
| Posted: | 2016-09-26 08:55 |
I had the same issue on an Ubuntu 16.04 virtual host. My resolution was to set the EngineID on the host, becaus net-snmpd didn't set it by default...
wish it helps.
| Subject: | Usually zenoss.snmp |
| Author: | [Not Specified] |
| Posted: | 2016-09-28 14:05 |
Usually zenoss.snmp.SnmpV3EngineIdMap is enabled for efficiency in polling which at the same time has to be changed in the SNMP settings of the firewall as well.
If the modeler is selected in zenoss for the firewall device, and the same setting is not applied on the firewall it is probable to see such alerts.
There is no issue as such whenzenoss.snmp.SnmpV3EngineIdMap is not used, I have been monitoring the firewall without this with no issues.
| < |
Previous zendmd - export list from group, system, etc ... |
Next Moving devices from Zenoss 3.0.2 to Zenoss 4.2.5 |
> |