David Carmean wrote:
If you are using a default Net-SNMP configuration, it will only allow anonymous access to the system variables. If the local hosts shows no Interfaces or Routes in the OS section, this is usually what's going on. The simplest thing to do for Net-SNMP, if your security policies permit, is to create a one-line snmpd.conf file that simply contains one single line with "rocommunity public" (or whatever string you choose).
Indeed this is what was going on. I used to have a single line snmpd.conf when my previous version of zenoss was working but somehow put the default back into place. So that explains why it worked before. You would think the default would be a somewhat working config but apparently not. Now I can get much more data out of the local zenoss system so we're looking good. Now when I go to discover other devices on the network I get errors when pinging:
http://pastebin.ca/672615 Any idea what this traceback means?
Zendisc can't do *anything* without knowing a route out of the local system.
Just out of curiosity, why does it need SNMP to know a route out of the system? Isn't that what the systems routing table is for?
Thanks! _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
