Datastax Opscenter 6.0不發送SNMP陷阱

Question

我正在使用datastax opscenter 6.0進行DSE Cassandra Monitoring。配置完成以發送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 

Answer 1

嘗試設置levels=ALERT到levels=，並確保它不只是你過濾你想找的第一事件（可以把它找回曾經有工作像你想要更容易看到更多的東西）。

可以使用Wireshark或tcpdump的檢查，如果陷阱正在用類似發：

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

（注：eth1的可能需要您的接口名稱來代替）。 SNMP客戶端在安裝正確的時候可能會有一點點偏差，所以很好檢查它們是否正在發送，未處理與未發送。