Re: [Pysnmp-dev] Pysnmp: Can it receive snmp v3 trap with random engine id
Brought to you by:
elie
From: chengkeke <che...@16...> - 2011-06-15 02:31:03
|
Hi Ilya & all, Now, I can get snmp v3 trap base on examples of v3 in pysnmp web site. I used the version pysnmp-4.1.10a. Here are my new questions. 1. There two network card in my computer. If set host as 127.0.0.1, local IP is 192.168.0.100, can't get trap information. After I change host to 192.168.0.100, it works well.So we can't set host as 127.0.0.1(want to receive all traps sent to local computer), is it correct? 2. In the sample, we only get name, val in varBinds. Can we get other information, for example, sec-name, auth protocol, auth key, privacy protocol, privacy key and agent ip address? [We can get details information in v1.] In pysnmp\proto\api, we only have v1 and v2c. Thanks all. Cherry At 2011-06-15 01:58:08,"Ilya Etingof" <il...@gl...> wrote: > >There's no need for Notification Receiver to configure Originator's >EngineID (as Notification Originator is an authoritative entity in SNMPv3 >terms). > >Therefore I'd advise to fire up your Notification Receiver (without >having ContextEngineID configured to it) and see if it receives traps >from your Originator. > >Please let me know in case of any issues. > >-ilya > >> I have seen the examples in the web site, we need to add v3 user and >> when we receive a trap. >> >> >> One of our device using random engine ID, when sending the v3 trap.Is it possible to receive this kind of trap with pysnmp? If yes, could anyone give me a sample because the example in http://pysnmp.sourceforge.net/examples/4.x/v3arch/manager/ntfrcv.html is to receive notification. >> >> >> config.addV3User( >> snmpEngine, 'test-user', >> config.usmHMACMD5AuthProtocol, 'authkey1', >> config.usmDESPrivProtocol, 'privkey1' >> # '\x80\x00\x4f\xb8\x1c\x3d\xaf\xe6' # ContextEngineID of >> # Notification Originator >> ) |