For flapping we typically recommend a delay on the Alert Rule, but
this may be a bug related to SNMPv3. If you could open a ticket
capturing the details of the issue we'll get it looked at.
Thanks,
Matt Ray
Zenoss Community Manager
community.zenoss.com
[EMAIL PROTECTED]
On Sep 9, 2008, at 10:31 AM, Anton Menshutin wrote:
I have the similar problem with dlink switches that have identical
engine id. When zenoss queries this devices in a single thread (i.e.
netsnmp library is being initialized only ones) and receives data
with identical snmpv3 engine id it skips second device.
I've managed to debug it by tcpdumping a lot (i saw that device
really answers, but zenoss says it is not) and finally compiling
netsnmp library to dump debugging information.
There were a lot of it :)
I think this is the only way for you to go.
niels2000 wrote:
may wrote:
Check you engineid on each host - it should be unique.
Thank you for the suggestion. As far as I can tell, the engineID is
in fact unique to each host.
[EMAIL PROTECTED] network-scripts]# grep -i engineid /var/net-snmp/
snmpd.conf
oldEngineID 0x80001f888060765b09a94bc04800000000
[EMAIL PROTECTED] log]# grep -i engineid /var/net-snmp/snmpd.conf
oldEngineID 0x80001f8880c084373f6d0bc54800000000
[EMAIL PROTECTED] ~]# grep -i engineid /var/net-snmp/snmpd.conf
oldEngineID 0x80001f88805bdbcc788d3fc64800000000
I am not aware of any other way to extract the engine ID.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=24849#24849
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
