It does contain the OID in the error and yes it is the same exact one I
have in my perfconf tab.  I did notice that Zen will cut off the leading
period, but I was able to walk the device with and without it just fine.


>From snmpwalk I tried both version 1 and 2c and it walked fine, it is
set to v1 in Zen so I would assume it should work.

I did use the same community to walk the device as I have input into
Zen.  zSnmpCommunity has my community, but it wasn't under
zSnmpCommunities so I added it.  Would that make a difference?

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chet Luther
Sent: Thursday, April 19, 2007 11:35 AM
To: General discussion of using zenoss system
Subject: Re: [zenoss-users] SNMP help

On 4/19/07, Wesley.Sparks <[EMAIL PROTECTED]> wrote:
> Under my Cisco 3005 VPN concentrator, under the perconf tab, I copied
it
> locally and added my datasource and created my graph.  The datasource
I
> created is called alPptpStatsActiveSessions with an OID of
> 1.3.6.1.4.1.3076.2.1.2.3.1.9.  The datapoint is called
> alPptpStatsActiveSessions with the type set to gauge, and all else
> defaults.  I created a graph called Number of PPTP Active Sessions,
with
> a datasource of alPptpStatsActiveSessions_ alPptpStatsActiveSessions,
> and everything else set to defaults.  Using the proper mib file and
the
> above OID from the zen server I can snmpwalk the device and get back
the
> correct values.

Zenoss should contain the bad OID within the error message. Does it
match the one you entered exactly? If so, is Zenoss setup to use the
same SNMP version and community for this device that you're using from
the command line? You can check under its zProperties.

-- 
Chet Luther
[EMAIL PROTECTED]
_______________________________________________
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

Reply via email to