Cassandra Datastax Opscenter 6.0未发送SNMP陷阱

我正在使用datastax opscenter 6.0进行DSE Cassandra监控。已完成发送SNMP陷阱的配置，但陷阱接收器（本例中为HP Openview）未收到此警报。 我在opscenter日志文件中没有看到任何SNMP实时错误。如何追踪准确的错误

这是我的snmp.conf文件：

 [snmp]
 # set to 1 to enable SNMP trap sending
 enabled=1

 # Levels can be a comma-delimited list of any of the following:
 # DEBUG,INFO,WARN,ERROR,CRITICAL,ALERT
 # If the left is empty, OpsCenter will listen for all levels.
 levels=ALERT

 # Comma-delimited list of cluster names for which
 # this alert config will be eligible to run.
 # If left empty, this alert will be called for events on all clusters.
 clusters=

 # SNMP engine ID, specified by rfc3411 and rfc5343.
 # See http://tools.ietf.org/html/rfc3411#section-5
 # SnmpEngineID definition for more information.
 #
 # 32 octet (max length) unique hex engine ID. Must not be all zeroes or all
 # 255's. The first four octets specify the enterprise ID, left filled
 # with zeroes and starting with an 8. The fifth octet specifies a format scheme
 # that specifies the nature of the remaining octets. The remaining octets
 # are given in accordance with the specified format.
 #
 # Format Schemes:
 # 1 -- IPv4 Address scheme
 # 2 -- IPv6 Address scheme
 # 3 -- MAC Address scheme
 # 4 -- Text Address scheme
 # 5 -- Octets scheme
 #
 # Default scheme is octets scheme; if nothing else, you should change
 # 01020304 to a unique octet string.
 #engine_id=80:00:00:00:05:01:02:03:04

 # IPv4 address of the SNMP target.
 target_ip=*.*.*.*         ( commented due to security urpose )

 # Port to direct traps to on the SNMP target.
 target_port=162

 # Set to 1 to use SNMPv3 and the user/privacy key/auth key model. Set to 0 to
 # use SNMPv1/community model.
 use_snmpv3=0

 # SNMPv1/2 community name (for community security model)
 community_name=public

 # SNMPv3 username
 #user=opscusername

 # SNMPv3 authentication protocol
 # Options:
 #   MD5 -- MD5-based authentication protocol
 #   SHA -- SHA-based authentication protocol
 #   NoAuth -- no authentication to use
 #auth_protocol=SHA

 # SNMPv3 authentication key
 #auth_key=authkey1

 # SNMPv3 privacy protocol
 # Options:
 #   DES -- DES-based encryption protocol
 #   AES -- AES128-based encryption protocol (RFC3826)
 #   3DES -- triple DES-based encryption protocol (Extended Security Options)
 #   AES192 -- AES192-based encryption protocol (Extended Security Options)
 #   AES256 -- AES256-based encryption protocol (Extended Security Options)
 #   NoPriv-- no encryption to use
 #privacy_protocol=AES

 # SNMPv3 privacy key
 #privacy_key=privkey1

---

尝试将

levels=ALERT

设置为

levels=

，并确保不仅仅是过滤您首先查找的事件（可以在它正常工作后将其返回，只是更容易查看更多内容）

可以使用wireshark或tcpdump检查陷阱是否通过以下方式发送：

tcpdump -i eth1 -T snmp  "(port 161 or 162)"

---

（注意：eth1可能需要替换为您的接口名称）。SNMP客户端在正确设置方面也可能有一点缺陷，因此很好地检查它们是否正在发送、未处理或未发送。

生成了以下跟踪转储07:57:05.158852 IP ukxxxxx.uk.xxxx-intl.com.58993>snvxxx.uk.xxx-intl.com.snmptrap:V2Trap（433）S:1.1.4.1.0=E:46272.1.0.3 system.sysDescr.0=“系统描述”2.1.1.3=“警告”：46272.1.0.1.1.1.1.1.1.1.3=“警告”：46272.1.0.2.1.1.1.1.1.1.1.1.1.1.1.1.2.1.1.1.1.1.1.2.2.2.1.2.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.4 4=“=“=“节点”节点的“节点正在下降的节点”1.2.2.1.1.1.1.4=“节点的节点：节点：节点正在下降：节点的节点的下行：xx。xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx”xx“E：E：一个“E：46272.xx.xx”xx.xx”xx”1.1.0.2.1.9=“无”E:46272.1.0.2.1.12=“无”E:46272.1.0.2.1.13=“无”从上面的跟踪转储中可以看出snmp陷阱将被发送到HP Openview陷阱接收器，但HP Openivew无法获取它们。已启用增强跟踪，但未从Opscenter服务器接收到陷阱。