Dave,
I finally got the fix suited for our system.
First, I made sure to make the community name be enclosed inside a single
quote when it is written on the snmpd.conf file.
Then, when the security, group and access info are parsed, I avoided the use
of strtok() but instead made use of the copy_
Hello,
As suggested in the first option
if i make my process p1 as a net snmp subagent using agentx than will the
snmp master agent(SNMPD) will forward all the incoming requests to P1(as
there can be more than one sub-Agent)?
is it possible to filter incoming requests from the snmpd to the p1 ba
> From: Dave Shield [mailto:d.t.shi...@liverpool.ac.uk]
> Sent: Wednesday, January 13, 2010 2:12 PM
> 2010/1/13 Fulko Hew :
> > I'm seeing that by default Net-SNMP is using a domain socket instead
> of TCP
> > port 705.
> >
> > I can force it to use the port by adding the following to the config
>
On Wed, Jan 13, 2010 at 5:18 PM, Dave Shield wrote:
> What version of Net-SNMP is installed on the two systems?
> There has been a significant re-write of the sensors MIB
> recently, which might be one possible explanation of the
> different indexes.
As I mentioned previously, the sensors and UC
2010/1/7 Rick Dicaire :
> Hi folks...I have a dualboot machine, 32 bit hardware, fedora 11 and
> opensuse 11.2. Running net-snmp, with lmsensors support.
> The kernel versions of course differ, as do the sensors3 pkgs, and
> likely the net-snmp pkg versions as well.
What version of Net-SNMP is i
2010/1/13 Fulko Hew :
> I'm seeing that by default Net-SNMP is using a domain socket instead of TCP
> port 705.
>
> I can force it to use the port by adding the following to the config file
>
> agentxsocket tcp:localhost:705
>
> but how can I make that the default at configure/make time?
$ ./conf
Could find that anywhere. Muy bueno Thomas ! Thanks
>> I don't see a tcp option for snmptrap.exe so I assume it isn't there.
>> Does anyone know of a win32 snmptrap sending utility that can send using
>> TCP ?
>Try: snmptrap.exe ... tcp:desthost:162 ...
>
>(with "desthost" being the trap de
Continuing on my quest to get Net-SNMP working well on this old AIX box,
I'm now trying to enable AgentX (master) support...
I'm seeing that by default Net-SNMP is using a domain socket instead of TCP
port 705.
I can force it to use the port by adding the following to the config file
agentxsocke
The only way I can find a subinterface IP address via SNMP is on the
routing or TCP tables if there is a live connection.
Is there a way to tell net-snmp 5.0.9 on RedHat ES 3 to show
subinterface IPs.
It's one thing to not show eth0:1 on the interfaces table but to not
show the IP in the ipAddr
On Wed, Jan 13, 2010 at 11:41 AM, Ron Rader wrote:
>
> If I read your OIDs correctly, .1.3.6.1.4.1.2021.13.16.2.1.3 simply
> identifies lmTempSensorsValue, of which there may be more than one
> Gauge32 instance on any particular host.
>
> Apparently, your two installations simply map CPU tempera
> From: Rick Dicaire [mailto:kri...@gmail.com]
> Under fedora the OID for cpu temp is
>
> .1.3.6.1.4.1.2021.13.16.2.1.3.10
>
> Under opensuse the same resource uses OID
>
> .1.3.6.1.4.1.2021.13.16.2.1.3.1
> Why would the OID be different for the same resource on two different
> linux installat
I sent this out last week, never got a response, maybe it was missed
so I'll ask again...I have a dualboot machine, 32 bit hardware, fedora
11 and
opensuse 11.2. Running net-snmp, with lmsensors support.
Under fedora the OID for cpu temp is
.1.3.6.1.4.1.2021.13.16.2.1.3.10
Under opensuse the same
I think my overriding concern is to minimise merge issues when we
periodically upgrade to subsequent releases of net-snmp. I am more than
happy to feed back any bugs I might find but the grey area is knowing
exactly which part should be fixed.
Personally speaking, the old-school code in
snmpNotifi
2010/1/13 Lewis Adam-VNQM87 :
> Okay, thanks again. I may well speak to the -coders. It seems a shame to
> have gone to the effort of creating scripts that cannot be re-run.
Bear in mind that the MfD code structure is an order of magnitude
more complete (if you ask Robert) / complicated (if you as
Okay, thanks again. I may well speak to the -coders. It seems a shame to
have gone to the effort of creating scripts that cannot be re-run.
Adam.
> -Original Message-
> From: dave.shi...@googlemail.com
> [mailto:dave.shi...@googlemail.com] On Behalf Of Dave Shield
> Sent: Wednesday, Jan
2010/1/13 Lewis Adam-VNQM87 :
> Are the mib2c scripts purely for the benefit of creating
> new user-defined tables?
That's how I view them, yes.
I seem to recall Robert had some method of re-running
mib2c to update the standard structure of MfD-based MIB code.
But I have no involvement with this
Hi Dave,
thanks for the quick response. Yes, I did mean snmp-notification-mib.
I guess I am trying to get the correct "workflow". I understand that the mib2c
will not generate the finished code but now that we have cranked the handle
once with snmpNotifyFilterTable files, do we simply treat the
2010/1/13 Lewis Adam-VNQM87 :
> Looking at the files that combine to provide support for the
> snmpNotifyFilterTable:
>
> agent\mibgroup\notification\snmpNotifyFilterTable.c
> agent\mibgroup\notification\snmpNotifyFilterTable_data_access.c
> agent\mibgroup\notification\snmpNotifyFilterTable_inte
Looking at the files that combine to provide support for the
snmpNotifyFilterTable:
agent\mibgroup\notification\snmpNotifyFilterTable.c
agent\mibgroup\notification\snmpNotifyFilterTable_data_access.c
agent\mibgroup\notification\snmpNotifyFilterTable_interface.c
etc.
I can see that these f
Hi list,
I'm trying to extend the snmpd agent with Perl modules to report status
from several different programs. The modules, when added do snmpd.conf
via "perl do snmpagent.pl" work well, when added as standalone modules.
However I have a problem when I want to register multiple agents via
"
2010/1/13 chris :
> However, I am not interested in statistics on the given interface and
> all its aliases. Is there an option to exclude/disable this interface
> and it aliases from SNMP data?
No - you'd probably need to tweak the code directly.
> If there is no such option, I'd also deactivat
Dear list,
I've got a network configuration where I am forced to create thousands
of network interface aliases. If I create too many of them, snmpd is
consuming most of the system's CPU usage. My guess is that it tries to
iterate over all existing system interfaces (including aliases), which
is an
2010/1/13 Alexander King :
> I used smilint tool in Ubuntu check my mib file,I got so many warings and
> synax errors,but I can use snmptranslate get the structure of the mib very
> well,and I can run compile in MG-soft very well.
I can't comment on the MGSoft tools, but our MIB parser is very
acc
23 matches
Mail list logo
