Re: [Pysnmp-dev] Pysnmp: Can it receive snmp v3 trap with random engine id
Brought to you by:
elie
From: Ilya E. <il...@gl...> - 2011-06-14 17:58:18
|
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 > ) |