high-availability setup. However, for this functionality to work it is required to update the time format in any bash, perl and SNMPTT scripts to ”%Y-%m- %dT%H:%M:%S%z” (i.e. 2024-01-10T11:56:14+0300). API changes passing the traps to Zabbix - either a Bash or Perl script or SNMPTT. Note: The simplest way to set up trap monitoring after configuring Zabbix is to use the Bash script solution, because Perl and SNMPTT receiving a trap: 1. snmptrapd receives a trap 2. snmptrapd passes the trap to the receiver script (Bash, Perl) or SNMPTT 3. The receiver parses, formats and writes the trap to a file 4. Zabbix SNMP trapper

passing the traps to Zabbix - either a Bash or Perl script or SNMPTT. Note: The simplest way to set up trap monitoring after configuring Zabbix is to use the Bash script solution, because Perl and SNMPTT receiving a trap: 1. snmptrapd receives a trap 2. snmptrapd passes the trap to the receiver script (Bash, Perl) or SNMPTT 3. The receiver parses, formats and writes the trap to a file 4. Zabbix SNMP trapper to start the SNMP trapper process and point to the trap file that is being written by SNMPTT or a Bash/Perl trap receiver. To do that, edit the configuration file (zabbix_server.conf or zabbix_proxy.conf):

passing the traps to Zabbix - either a Bash or Perl script or SNMPTT. 267 Note: The simplest way to set up trap monitoring after configuring Zabbix is to use the Bash script solution, because Perl and receiving a trap: 1. snmptrapd receives a trap 2. snmptrapd passes the trap to the receiver script (Bash, Perl) or SNMPTT 3. The receiver parses, formats and writes the trap to a file 4. Zabbix SNMP trapper to start the SNMP trapper process and point to the trap file that is being written by SNMPTT or a Bash/Perl trap receiver. To do that, edit the configuration file (zabbix_server.conf or zabbix_proxy.conf):

passing the traps to Zabbix - either a Bash or Perl script or SNMPTT. Note: The simplest way to set up trap monitoring after configuring Zabbix is to use the Bash script solution, because Perl and SNMPTT receiving a trap: 1. snmptrapd receives a trap 2. snmptrapd passes the trap to the receiver script (Bash, Perl) or SNMPTT 3. The receiver parses, formats and writes the trap to a file 4. Zabbix SNMP trapper to start the SNMP trapper process and point to the trap file that is being written by SNMPTT or a Bash/Perl trap receiver. To do that, edit the configuration file (zabbix_server.conf or zabbix_proxy.conf):

在 Zabbix 中接收 SNMP 陷阱要与 snmptrapd 一起使用，以及将 snmp 陷阱传递给 Zabbix 的机制之一，Bash 或 Perl 脚本或 SNMPTT 。 Note: 配置 Zabbix 后设置 trap 监控最简单的方法是使用 Bash 脚本方案，因为 Perl 和 SNMPTT 在现代发行版中经常缺失，需要更复杂 的配置。但是，该方案使用配置为 traphandle Perl 解决方案（带 有 “do perl” 选项的脚本或 SNMPTT）。 接收陷阱的工作流程： 1. snmptrapd 收到陷阱 2. snmptrapd 将陷阱传递给接收器脚本（Bash、Perl）或 SNMPTT 3. 接收方解析、格式化并将 trap 写入文件 4. Zabbix SNMP trapper 读取并解析 trap 文件 5. 对于每个陷阱，Zabbix 会 SNMPTrapperFile=[TRAP FILE] Warning: 如果使用 systemd 参数 PrivateTmp，则该文件不太可能在/tmp 下工作。 配置 Bash 陷阱接收器 要求：只有 snmptrapd。 Bash 陷阱接收器 脚本 可用于将陷阱直接从 snmptrapd 传递给 Zabbix 服务器。要配置它，请将 traphandle 选项添加到 snmptrapd 配 置文件

Zabbix 高可用性中使用 SNMP traps 现在，Zabbix 在高可用性设置中切换活动节点时可以从正确位置读取 SNMP trap 文件。 120 但是，为了使此功能正常工作，需要将所有 bash、perl 和 SNMPTT 脚本中的时间格式更新为”%Y-%m-%dT%H:%M:%S%z”（例如 2024-01-10T11:56:14+0300）。 12 升级说明 7.0.1 Breaking 在 Zabbix 中接收 SNMP 陷阱要与 snmptrapd 一起使用，以及将 snmp 陷阱传递给 Zabbix 的机制之一，Bash 或 Perl 脚本或 SNMPTT 。 Note: 配置 Zabbix 后设置陷阱监控的最简单方法是使用 Bash 脚本解决方案，因为现代发行版中经常缺少 Perl 和 SNMPTT，并且需要 更复杂的配置。但是，此解决方案使用配置为 traphandle 入式 Perl 解 决方案（带有 do perl 选项的脚本或 SNMPTT）。 接收陷阱的工作流程： 1. snmptrapd 收到陷阱 2. snmptrapd 将陷阱传递给接收器脚本（Bash、Perl）或 SNMPTT 261 3. 接收方解析、格式化并将 trap 写入文件 4. Zabbix SNMP trapper 读取并解析 trap 文件 5. 对于每个陷阱，Zabbix

restart Zabbix daemons. To do so, run: rczabbix-server restart rczabbix-agentd restart 7.1 Bash completion Bash completion for Zabbix daemons and utilities has been included since the appliance version version 2.4.6, but was not included with the previous versions. To install it, run: zypper in zabbix24-bash-completion Confirm the installation and close your login session, then log in again. 8 Naming, init recipient (”To”) is specified in user media properties. Here is an example alert script: #####!/bin/bash to=$1 subject=$2 body=$3 cat <

0 码力 | 910 页 | 10.81 MB | 1 年前

3

configuration script mysql.size parameter. It con- tained a complex bash expression and was failing if the default shell was not bash (CVE-2016-4338). 1 Manual structure Structure The content of this recipient (”To”) is specified in user media properties. Here is an example alert script: #####!/bin/bash to=$1 subject=$2 body=$3 cat <

0 码力 | 791 页 | 9.66 MB | 1 年前

3

configuration script mysql.size parameter. It con- tained a complex bash expression and was failing if the default shell was not bash (CVE-2016-4338). 19 What’s new in Zabbix 2.2.15 19.1 Daemon improvements recipient (”To”) is specified in user media properties. Here is an example alert script: #####!/bin/bash to=$1 subject=$2 body=$3 cat <

0 码力 | 918 页 | 11.28 MB | 1 年前

3

configuration script mysql.size parameter. It contained a complex bash expression and was failing if the default shell was not bash (CVE-2016-4338). 9 What’s new in Zabbix 3.0.4 1 Frontend improvements server configuration file AlertScriptsPath variable. Here is an example alert script: #####!/bin/bash to=$1 subject=$2 body=$3 cat <

0 码力 | 1074 页 | 12.04 MB | 1 年前

3