Hi, Dave I find the fail reason for the second case is, when send trap and call the function usm_generate_out_msg()->sc_generate_keyed_hash(), it didn't return the correct the value, so the trap fail to send. But I don't know what happened inside this function.
-----邮件原件----- 发件人: Kang Chen [mailto:[email protected]] 发送时间: 2009年4月17日 14:31 收件人: Dave Shield 抄送: [email protected] 主题: 答复: 答复: 答复: 答复: question about SNMPv3 trap In the second case, when I try to send a trap, the snmpd hint 'snmpd: send_trap: USM authentication failure (incorrect password or key)' -----邮件原件----- 发件人: Kang Chen 发送时间: 2009年4月17日 14:28 收件人: 'Dave Shield' 抄送: [email protected] 主题: 答复: 答复: 答复: 答复: question about SNMPv3 trap Hi, Dave First, I configure the snmpd.conf as: createUser leelin MD5 "authpass" DES "privpass" trapsess -v 3 -l authNoPriv -u leelin 172.18.100.148:162 after execute snmpd, the v3 trap can be reveived. The value of three table list as following: 1: snmpTargetAddrTDomain.105.110.116.101.114.110.97.108.48 (TDomain) snmpUDPDomain 2: snmpTargetAddrTAddress.105.110.116.101.114.110.97.108.48 (TAddress) AC.12.64.94.00.A2 (hex) 3: snmpTargetAddrTimeout.105.110.116.101.114.110.97.108.48 (TimeInterval) 1000 4: snmpTargetAddrRetryCount.105.110.116.101.114.110.97.108.48 (Integer32) 5 5: snmpTargetAddrTagList.105.110.116.101.114.110.97.108.48 (SnmpTagList) internal0 [69.6E.74.65.72.6E.61.6C.30 (hex)] 6: snmpTargetAddrParams.105.110.116.101.114.110.97.108.48 (SnmpAdminString) internal0 [69.6E.74.65.72.6E.61.6C.30 (hex)] 7: snmpTargetAddrStorageType.105.110.116.101.114.110.97.108.48 (StorageType) readOnly(5) 8: snmpTargetAddrRowStatus.105.110.116.101.114.110.97.108.48 (RowStatus) active(1) 1: snmpTargetParamsMPModel.105.110.116.101.114.110.97.108.48 (SnmpMessageProcessingModel) 3 2: snmpTargetParamsSecurityModel.105.110.116.101.114.110.97.108.48 (SnmpSecurityModel) 3 3: snmpTargetParamsSecurityName.105.110.116.101.114.110.97.108.48 (SnmpAdminString) leelin [6C.65.65.6C.69.6E (hex)] 4: snmpTargetParamsSecurityLevel.105.110.116.101.114.110.97.108.48 (SnmpSecurityLevel) authNoPriv(2) 5: snmpTargetParamsStorageType.105.110.116.101.114.110.97.108.48 (StorageType) readOnly(5) 6: snmpTargetParamsRowStatus.105.110.116.101.114.110.97.108.48 (RowStatus) active(1) 1: snmpNotifyTag.105.110.116.101.114.110.97.108.48 (SnmpTagValue) internal0 [69.6E.74.65.72.6E.61.6C.30 (hex)] 2: snmpNotifyType.105.110.116.101.114.110.97.108.48 (INTEGER) trap(1) 3: snmpNotifyStorageType.105.110.116.101.114.110.97.108.48 (StorageType) readOnly(5) 4: snmpNotifyRowStatus.105.110.116.101.114.110.97.108.48 (RowStatus) active(1) Second, I remove trapsess -v 3 -l authNoPriv -u leelin 172.18.100.148:162 in snmpd.conf and run snmpd again. Then I configure the three table as following: 1: snmpTargetAddrTDomain.105.110.116.101.114.110.97.108.48 (TDomain) snmpUDPDomain 2: snmpTargetAddrTAddress.105.110.116.101.114.110.97.108.48 (TAddress) AC.12.64.94.00.A2 (hex) 3: snmpTargetAddrTimeout.105.110.116.101.114.110.97.108.48 (TimeInterval) 1000 4: snmpTargetAddrRetryCount.105.110.116.101.114.110.97.108.48 (Integer32) 5 5: snmpTargetAddrTagList.105.110.116.101.114.110.97.108.48 (SnmpTagList) internal0 [69.6E.74.65.72.6E.61.6C.30 (hex)] 6: snmpTargetAddrParams.105.110.116.101.114.110.97.108.48 (SnmpAdminString) internal0 [69.6E.74.65.72.6E.61.6C.30 (hex)] 7: snmpTargetAddrStorageType.105.110.116.101.114.110.97.108.48 (StorageType) nonVolatile(3) 8: snmpTargetAddrRowStatus.105.110.116.101.114.110.97.108.48 (RowStatus) active(1) 1: snmpTargetParamsMPModel.105.110.116.101.114.110.97.108.48 (SnmpMessageProcessingModel) 3 2: snmpTargetParamsSecurityModel.105.110.116.101.114.110.97.108.48 (SnmpSecurityModel) 3 3: snmpTargetParamsSecurityName.105.110.116.101.114.110.97.108.48 (SnmpAdminString) leelin [6C.65.65.6C.69.6E (hex)] 4: snmpTargetParamsSecurityLevel.105.110.116.101.114.110.97.108.48 (SnmpSecurityLevel) authNoPriv(2) 5: snmpTargetParamsStorageType.105.110.116.101.114.110.97.108.48 (StorageType) nonVolatile(3) 6: snmpTargetParamsRowStatus.105.110.116.101.114.110.97.108.48 (RowStatus) active(1) 1: snmpNotifyTag.105.110.116.101.114.110.97.108.48 (SnmpTagValue) internal0 [69.6E.74.65.72.6E.61.6C.30 (hex)] 2: snmpNotifyType.105.110.116.101.114.110.97.108.48 (INTEGER) trap(1) 3: snmpNotifyStorageType.105.110.116.101.114.110.97.108.48 (StorageType) nonVolatile(3) 4: snmpNotifyRowStatus.105.110.116.101.114.110.97.108.48 (RowStatus) active(1) Except the StorageType, all the other variables are the same as the first. But, I still can not receive the V3 trap. -----邮件原件----- 发件人: [email protected] [mailto:[email protected]] 代表 Dave Shield 发送时间: 2009年4月16日 16:29 收件人: Kang Chen 抄送: [email protected] 主题: Re: 答复: 答复: 答复: question about SNMPv3 trap 2009/4/16 Kang Chen <[email protected]>: > In snmpd.conf, I configure the user as following: > createUser leelin MD5 "authpass" DES "privpass" OK > group Groupv3 usm leelin > view if2 included .1.3.6 > access Groupv3 "" usm auth exact if2 if2 if2 These three lines probably aren't relevant (at least not for sending traps). They are concerned with controlling access *to* the agent, not outgoing requests. > if I also configure > trapsess -v 3 -l authNoPriv -u leelin -a MD5 -A authpass -x DES -X privpass > 172.18.100.148:162 > then I can receive the V3 trap in MG-SOFT mibbrowser. > If I don't configure the trapsess command, but configure the three table you > told me before, then I can't receive the v3 trap. Clear the three tables, and re-instate the "trapsess" line as above. Now walk the tables - what do you see? Clear the tables, and remove the "trapsess" line. Now create equivalent entries in the tables. Does it work or not? If not, walk the tables again - what do you see? Dave ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
