That sounds encouraging, Pete. Can you provide some insight on how to get the patch (I assume that the script below describes how to install it and restart Zenoss)? Also, what happens to an installed patch after you do a Zenoss upgrade? Do you have to determine if the patch is compatible with the new Zenoss rev. and then re-install it if it is?
One more concern of mine that has not yet been addressed: How do I get Zenoss to periodically re-scan address ranges to look for new devices? Zenoss 2.2.3 does not appear to do that even if a subnet's zAutoDiscover property is set to True. What does "zAutoDiscover" really mean? Many thanks, Matt mistich wrote: > zenoss created a patch to do exactly what you want there is a > commandline argument --snmp-strict-discovery which I assume you can put > into the config > > # As root, su to the zenoss user. > # run �zenpatch 10914� > # run �zenmigrate� > # run �zenoss restart� > # > > That should do it. After this, you should have a new zProperty at > Networks on the zProperties tab. The new property is > �zSnmpStrictDiscovery� and can be set to True or False. By default, it > is False. When set to true, discovered ip�s will not create devices > unless snmp info can be retrieved. In conjunction with the > zSnmpCommunities property on Devices, this should filter on community > like 2.1. Please give me a shout if you have any problems or if these > instructions are unclear/inaccurate. > > hope this helps, > Pete > -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=29271#29271 -------------------- m2f --------------------
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
