我已经通过docker images部署了OpenNM,并且SNMPV3轮询工作起作用,但无法获得SNMPV3陷阱或信息。
trapd-configuration.xml:
<?xml version="1.0"?>
<trapd-configuration snmp-trap-port="162" new-suspect-on-trap="true">
<snmpv3-user
security-name="trapuser"
security-level="3"
auth-passphrase="authsecret"
auth-protocol="SHA"
privacy-passphrase="privsecret"
privacy-protocol="AES"/>
</trapd-configuration>
如果我从另一个主机运行以下内容,该主机通过snmpv3进行了opennms的轮询:
snmptrap -Dusm -v 3 -l authPriv -u trapuser -a SHA -A authsecret -x AES -X privsecret <opennms-host-ip> 42 coldStart.0
OpenNM不会生成任何事件。在trapd.log中,我可以看到以下警告:
2018-04-26 09:26:33,364 WARN [DefaultUDPTransportMapping_0.0.0.0/162] o.s.MessageDispatcherImpl: statusInfo=1.3.6.1.6.3.15.1.1.3.0 = 0, status=1404
我能告诉的是与未知用户名有关的。
同样,告知我也无法正常工作,我在trapd.log文件中得到相同的警告,在发件人侧也有类似的警告。如果我运行tcpdump,我可以看到它可以从OpenNM中检索远程引擎。
snmpinform -Dusm -v 3 -l authPriv -u trapuser -a SHA -A authsecret -x AES -X privsecret <opennms-host-ip> 42 coldStart.0
registered debug token usm, 1
usm: potentially bootstrapping the USM table from session data
usm: getting user
usm: USM processing has begun (offset 39)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
usm: USM processing begun...
usm: USM processing completed.
usm: potentially bootstrapping the USM table from session data
usm: no flag defined... continuing
usm: user exists? x=(nil)
usm: Building user trapuser...
usm: USM processing has begun (offset 80)
usm: getting user trapuser
usm: match on user trapuser
usm: Encryption successful.
usm: USM processing completed.
usm: USM processing begun...
usm: match on user trapuser
usm: USM processing completed.
snmpinform: Unknown user name
关于我做错了什么的想法?
您可以尝试以下操作:
打开$OPENNMS_HOME/etc/service-configuration.xml
并在AsteriskGatway
服务后启动陷阱守护程序。要执行此操作,请找到以下XML块:
<service enabled="true">
<name>OpenNMS:Name=Trapd</name>
<class-name>org.opennms.netmgt.trapd.jmx.Trapd</class-name>
<invoke method="init" pass="0" at="start"/>
<invoke method="start" pass="1" at="start"/>
<invoke method="status" pass="0" at="status"/>
<invoke method="stop" pass="0" at="stop"/>
</service>
默认情况下,陷阱是在Correlator
之后启动的。削减&amp;在AsteriskGateway
服务之后粘贴整个服务定义块:
<service enabled="false">
<name>OpenNMS:Name=AsteriskGateway</name>
<class-name>org.opennms.netmgt.asterisk.agi.jmx.AsteriskGateway</class-name>
<invoke method="init" pass="0" at="start"/>
<invoke method="start" pass="1" at="start"/>
<invoke method="status" pass="0" at="status"/>
<invoke method="stop" pass="0" at="stop"/>
</service>
您现在可以尝试处理SNMPV3陷阱吗?