答复: 答复: question about SNMPv3 trap

2009-04-15 Thread Kang Chen
Hi, Dave After I configure the SNMP-TARGET-MIB::snmpTargetAddrTable SNMP-TARGET-MIB::snmpTargetParamsTable SNMP-NOTIFICATION-MIB::snmpNotifyTable I can receive the v1 or v2c trap, But I still can not receive the v3 trap. I'm copying the configuration as following: 1: snmpTargetAddrTDomain.105.11

[RFC PATCH] DISMAN EVENT MIB - Disable triggers and clean up callbacks on SIGHUP

2009-04-15 Thread Tushar Gohad
On a SIGHUP, clear_mteTTable() clears trigger_table_data but the mteTrigger entries remain registered in the POST_READ_CONFIG callbacks table. This causes multiple trap notifications for the same event when a SIGHUP is issued to snmpd. The patch below makes sure that the callbacks for the mteT

Re: Performance and correctness problems in Python bindings

2009-04-15 Thread Bill Fenner
We did some further analysis of the regexp. We found: 1. Replacing \w+(?:\-*\w+)+ with \w[-\w]+ turns 5 hours into a few ms. It still varies based on the length of the string, but it maxed out at 100ms for hrSWInstalledLastUpdateTime. 2. This regexp is different from the one in the perl module

Re: linker errors on libnetsnmptrapd.so

2009-04-15 Thread Geoffrey Bays
Wes: I took a look at snmptrapd_handlers.c dropauth and SyslogTrap are extern ints in snmptrapd_handlers.c.But they are not initialized there. So they should be initialized in some other module. The event_input function is referenced in snmptrapd_handlers.c, but defined in snmptrapd.c, and snmptra

Re: Performance and correctness problems in Python bindings

2009-04-15 Thread Wes Hardaker
> On Tue, 14 Apr 2009 08:00:05 -0700, Bill Fenner said: BF> Recently, we tracked down some pretty bad performance in our test BF> infrastructure to the same regexp. I find it odd that any regexp could possibly take that long trying to measure such a short string. I'd also file a bug in the

Re: question about the engineid

2009-04-15 Thread Wes Hardaker
> On Wed, 15 Apr 2009 13:32:37 +0800, Kang Chen > said: KC> When I want to receive a v3 trap using snmptrapd, I must assign the same KC> engineid both in snmpd.conf and snmptrapd.conf. KC> But, if I use MG-SOFT mibbrowser to receive the v3 trap, I need not to KC> assign the engineid in

Re: NETSNMP crashing

2009-04-15 Thread Wes Hardaker
> On Wed, 15 Apr 2009 16:05:51 +0530, > said: ao> When I try to run snmp -v 5.3.0.1 in MontaVista Can you try with a more recent branch of the 5.3 line? ao> It is dumping core files. Here is the gdb backtrace: It's also possible you have multiple versions of the libraries installed an

Re: Adding an ADSL MIB to the agent

2009-04-15 Thread Dave Shield
2009/4/15 Andy Burns : > how would I pick an OID, just start with a 1.3.6.1.3.random experimental one? Assuming this isn't going to be distributed outside your own private use, then use NET-SNMP-MIB::netSnmpPlaypen If it's likely to be used more widely, then you should apply for your own enterpri

Re: Adding an ADSL MIB to the agent

2009-04-15 Thread Andy Burns
> My immediate reaction would be to use the "extend" directive > to invoke the westell command directly.   That would provide the > basic information very simply. > > The main problem is that the output of this directive is string-based, > rather than numeric values (even if those strings actually

Re: Adding an ADSL MIB to the agent

2009-04-15 Thread Dave Shield
2009/4/15 Andy Burns : > I'd like to be able to collect and graph my ADSL stats into cacti, I'm > aware of various ADSL MIBs, RFC2662 seems to cover all the stats I > have available > > e.g. the westell utility currently outputs the following to stdout [snip] > I don't know whether the snmpd a

Adding an ADSL MIB to the agent

2009-04-15 Thread Andy Burns
Hi, I'm running snmpd on my openwrt firewall (WRT54GS hardware which has 1 WiFi interface and 1 NIC wired to an internal VLAN switch connecting to 5 external Ethernet ports usually configured as 1 WAN and 4 LAN) my ADSL connection is a separate router (Westell 7400) which doesn't support SNMP or an

NETSNMP crashing

2009-04-15 Thread anoopchandran.othayoth
Hi All When I try to run snmp -v 5.3.0.1 in MontaVista 3.4.3-25.0.100.0600729, I get following error in the console: r...@test:# ./snmpd -c ${CUR_DIR}/../temp/snmpd.conf -DTest,Test1,instanceID,Bootstrap -M ${CUR_DIR}/../mibs No log handling enabled - turning on stderr logging re