I installed the devel package on the second machine and now the second machine
can find pci.h so the two machines have exactly same configuration now.
So I did make uninstall, make clean, make distclean, then re-configure it with
same options, make, then make install. I still didn't get any link
The same configuration options resulted slightly different config on the two
machines:
[machine with link traps working]< checking pci/pci.h usability... yes<
checking pci/pci.h presence... yes< checking for pci/pci.h... yes
[machine with link traps not working]> checking pci/pci.h usability...
Running "net-snmp-config --snmpd-module-list" on the two machines gave the
exactly same list of modules loaded.
ThanksXuan
> Subject: RE: Strange behavior on linkUpDownNotifications
> Date: Thu, 8 Apr 2010 16:26:53 -0700
> From: mike_ay...@tva.tvworks.com
> To: b...@live.com; d.t.shi...@liverpoo
Here is the new update. I manually deleted all the extra MIB files under
/usr/local/share/snmp/mibs directory. Now starting agent with -Dparse-mibs
gave me exactly same MIB modules loaded as the other machine. But that didn't
solve the problem, i.e., I still couldn't receive any link traps. I
After compared the modules loaded on the two machines one module by one module,
I have the following finding:
The machine with link traps working is loaded with less MIB modules.
The machine with link traps not working is loaded with the following additional
MIB
modules:SMUX-MIBAGENTX-MIBSNMP-P
Both machines are loaded with same modules, but in different order.
ThanksXuan
> Date: Wed, 7 Apr 2010 22:10:12 +0100
> Subject: Re: Strange behavior on linkUpDownNotifications
> From: d.t.shi...@liverpool.ac.uk
> To: b...@live.com
> CC: net-snmp-users@lists.sourceforge.net
>
> 2010/4/7 X Z :
I have found the following when using -Dtrap as the option to start snmpd.
The working one (see link up down traps) has the following output:
trap: send_trap -1 -1 NET-SNMP-MIB::netSnmpAgentOIDs.10trap: sending trap
type=167, version=1
The nonworking one has the following output:trap: send_trap -
I tried snmp 5.3.3 on both 64 bits and 32 bits servers, and the link traps only
partially worked for 32 bits server. By "partially", I mean that the agent
didn't take the frequency and -S option, it just simply used the default one
(one minute) and didn't suppress the traps at the agent startup
I just tried snmp 5.3.3 and couldn't get the link traps working. Same behavior
observed. A bunch of link up/down traps when the agent started up or restarted.
After that, even I change the interface to be down by "ifdown eth2", no traps
were sent out.
ThanksXuan
> Date: Tue, 6 Apr 2010 12:19:
Yes. I only got them when agent starts up or restarts, not other times.
ThanksXuan
> Subject: RE: Strange behavior on linkUpDownNotifications
> Date: Mon, 5 Apr 2010 15:30:58 -0700
> From: mike_ay...@tva.tvworks.com
> To: b...@live.com; d.t.shi...@liverpool.ac.uk
> CC: net-snmp-users@lists.sour
> Subject: RE: Strange behavior on linkUpDownNotifications
> Date: Mon, 5 Apr 2010 11:37:04 -0700
> From: mike_ay...@tva.tvworks.com
> To: b...@live.com; d.t.shi...@liverpool.ac.uk
> CC: net-snmp-users@lists.sourceforge.net
>
>
> > From: X Z [mailto:b...@live.com]
> > Sent: Monday, March 29,
11 matches
Mail list logo
