Actually, the reason I suggested snmpget is that Zenoss does that rather than an snmpwalk. So if for instance an OID would fail with snmpget, but work with snmpwalk as snmpwalk will walk the OID tree. Not that this sounds like what your problem is.
The other thing is some (many?) of the zenoss packets are custom generated by the twisted python library, so they "look" different than their more standard counterparts. One thing to consider: is there a firewall interspersed between the Zenoss server and the switches that give you the error, but not between the Zenoss server and the ones that work? Another interesting thing to look at is if you're not getting anything in the logs would be to set up Wireshark on the Zenoss server and capture some packets and see if there's a problem generating packets, or more so, what's different between some switches that work and some that don't at the packet level. Also, do both sets of switches support the same SNMP version? Finally, with whatever info you have, come to the 11AM EDT IRC meeting where Zenoss Developers will be answering questions, and see if they can provide more help. -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University genji0714 wrote, On 5/28/2009 8:28 AM: > Hey, > > I am successfully doing an snmpwalk from Zenoss. As for an snmpget I have > only setup a readonly group on my switches. I did check the zsnmpperf logs > with watchdog on and also log severity 10. There was nothing out of the norm. > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=35339#35339 > > -------------------- 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
