> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:zenoss-users- > [EMAIL PROTECTED] On Behalf Of Kelly F. Hickel > Sent: Thursday, July 03, 2008 8:40 AM > To: General discussion of using zenoss system > Subject: RE: [zenoss-users] how to diagnose "snmp agent down" > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:zenoss-users- > > [EMAIL PROTECTED] On Behalf Of Kelly F. Hickel > > Sent: Thursday, July 03, 2008 6:35 AM > > To: General discussion of using zenoss system > > Subject: [zenoss-users] how to diagnose "snmp agent down" > > > > Hi all, just upgraded to 2.2 community. I was having a problem where > a > > Cisco Pix was always showing as "snmp agent down" and was hoping that > > the upgrade would fix it, but it didn't. > > > > Snmpwalk from the zenoss machine to the pix from the zenoss account > > works fine. > > > > Is there any way to determine how/why zenoss thinks it's failing? > > > > > > I've dug into this a bit and it seems to be the same as this issue from > 2006: > http://community.zenoss.com/forums/viewtopic.php?p=2409&sid=5d086bbb3a6 > 3 > 5304fdce5a6f58b2a2ca > > I've checked zenperfsmnp.py and the MAX_OIDS_PER_REQUEST variable is > still there and defaults to 40, but changing it doesn't seem to help, > even with a setting of 1. Looking through the file, the value doesn't > seem to ever be used. > > So, what's the mechanism to change this now??? > > -Kelly >
OK, so really simple. The setting was moved to the zProperty zMaxOIDPerRequest. So, just make the change on the device property page, and viola! -Kelly _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
