RE: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 (Dave Shield)

2006-07-25 Thread vic
Hi Dave, First of all, thank you so much for such a quick response! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > What do you mean by "initrd level" ? I'm using my own initial ram disk (initrd) image which the bootloader loads, along with the Kernel image. My ma

Re: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 (Dave Shield)

2006-07-25 Thread Dave Shield
On 25/07/06, vic <[EMAIL PROTECTED]> wrote: > I noticed that snmpd > would > not run at all while bootup process is still at the initrd level. What do you mean by "initrd level" ? >But for

RE: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 (Dave Shield)

2006-07-25 Thread vic
al Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield Sent: Thursday, July 20, 2006 9:31 PM To: vic Cc: net-snmp-users@lists.sourceforge.net Subject: Re: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 (Dave Shield) On 20/07/06, vic <[EMAIL PROTECTED]&

Re: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 (Dave Shield)

2006-07-20 Thread Dave Shield
On 20/07/06, vic <[EMAIL PROTECTED]> wrote: > At present, I still do not know where I > went wrong. ... > Any ideas I can start with? Well, there are basically two likely sources for this problem: a) The agent doesn't include support for these two tables b) The agent does, but the snmpd.conf f

RE: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 (Dave Shield)

2006-07-20 Thread vic
Hi Dave, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield Sent: Thursday, July 20, 2006 8:44 PM To: vic Cc: net-snmp-users@lists.sourceforge.net Subject: Re: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 (Dave Shield) > I gues

Re: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 (Dave Shield)

2006-07-20 Thread Dave Shield
On 20/07/06, vic <[EMAIL PROTECTED]> wrote: > I re-read the FAQ. If the following: > > - Why can't I see values in the UCDavis 'extensible' or 'disk' trees? > - Why can't I see values in the UCDavis 'memory' or 'vmstat' tree? > > .are the only entries that are related to my missing "pr" and "ds

Re: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 (Dave Shield)

2006-07-19 Thread vic
Hi Dave, everyone, -Original Message- Message: 2 Date: Thu, 20 Jul 2006 00:22:51 +0100 From: "Dave Shield" <[EMAIL PROTECTED]> Subject: Re: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9 To: vic <[EMAIL PROTECTED]> Cc: net-snmp-users@lists.sour

RE: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9

2006-07-19 Thread vic
RunPath.9682 = STRING: "/bin/spoon" HOST-RESOURCES-MIB::hrSWRunPath.9683 = STRING: "sh" HOST-RESOURCES-MIB::hrSWRunPath.9684 = STRING: "/usr/local/delious-apps/bin/hitouchdaemon" HOST-RESOURCES-MIB::hrSWRunPath.9691 = STRING: "/usr/local/delious-apps/bin/printerdaemon

Re: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9

2006-07-19 Thread Dave Shield
On 19/07/06, vic <[EMAIL PROTECTED]> wrote: > I compiled net-snmp v5.3.1 using default configure. During my tests, I > noticed that prTable and dskTable OIDs (among other UCD-SNMP-MIB modules) > are not getting retrieved by my snmpwalk from another machine. Please see the FAQ entry that refers to

RE: enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9

2006-07-19 Thread Bruce Shaw
>I compiled net-snmp v5.3.1 using default configure. During my tests, >I noticed that prTable and dskTable OIDs (among other UCD-SNMP-MIB modules) >are not getting retrieved by my snmpwalk from another machine. >Some however, gets retrieved properly: What platform and OS? This communication is i

enabling OIDs .1.3.6.1.4.1.2021.2 and .1.3.6.1.4.1.2021.9

2006-07-19 Thread vic
Hi, I compiled net-snmp v5.3.1 using default configure. During my tests, I noticed that prTable and dskTable OIDs (among other UCD-SNMP-MIB modules) are not getting retrieved by my snmpwalk from another machine. Some however, gets retrieved properly: UCD-SNMP-MIB::memIndex.0 = INTEGER: 0 UCD-SNM