msgAuthoritativeEngineID (also known as snmpEngineID or ”Engine ID”) is never shared by two devices. According to RFC 2571 (section 3.1.1.1) it must be unique for each device. Configuring SNMP monitoring To start monitoring Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1, 192.168.1.0/24, 192.168.3.1-255, 192.168.1-10.1-255, ::1,2001:db8::/32 There are some restrictions on display names in Zabbix emails in comparison to what is allowed by RFC 5322, as illustrated by examples: Valid examples: zabbix@company.com (only email address, no need

time.Now().Format(time.RFC3339) } A plugin must register itself during initialization. func init() { plugin.RegisterMetric(&impl, "Time", "system.time", "Returns time string in RFC 3999 format.") } where msgAuthoritativeEngineID (also known as snmpEngineID or ”Engine ID”) is never shared by two devices. According to RFC 2571 (section 3.1.1.1) it must be unique for each device. Configuring SNMP monitoring To start monitoring Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1, 192.168.1.0/24, 192.168.3.1-255, 192.168.1-10.1-255, ::1,2001:db8::/32

msgAuthoritativeEngineID (also known as snmpEngineID or ”Engine ID”) is never shared by two devices. According to RFC 2571 (section 3.1.1.1) it must be unique for each device. Configuring SNMP monitoring To start monitoring Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1, 192.168.1.0/24, 192.168.3.1-255, 192.168.1-10.1-255, ::1,2001:db8::/32 Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1, 192.168.1.0/24, 192.168.3.1-255, 192.168.1-10.1-255, ::1,2001:db8::/32

or ”Engine ID”) is never shared by two devices. According to RFC 2571 (section 3.1.1.1) it must be unique for each device. Warning: RFC3414 requires the SNMPv3 devices to persist their engineBoots. Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1, 192.168.1.0/24, 192.168.3.1-255, 192.168.1-10.1-255, ::1,2001:db8::/32 Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1, 192.168.1.0/24, 192.168.3.1-255, 192.168.1-10.1-255, ::1,2001:db8::/32

msgAuthoritativeEngineID (also known as snmpEngineID or ”Engine ID”) is never shared by two devices. According to RFC 2571 (section 3.1.1.1) it must be unique for each device. Configuring SNMP monitoring To start monitoring There are some restrictions on display names in Zabbix emails in comparison to what is allowed by RFC 5322, as illustrated by examples: Valid examples: zabbix@company.com (only email address, no need brackets around email address) ”Zabbix\@\” (although valid by RFC 5322, quoted pairs and comments are not supported in Zabbix emails) Connection security Select the

msgAuthoritativeEngineID (also known as snmpEngineID or ”Engine ID”) is never shared by two devices. According to RFC 2571 (section 3.1.1.1) it must be unique for each device. Configuring SNMP monitoring To start monitoring There are some restrictions on display names in Zabbix emails in comparison to what is allowed by RFC 5322, as illustrated by examples: Valid examples: zabbix@company.com (only email address, no need brackets around email address) ”Zabbix\@\” (although valid by RFC 5322, quoted pairs and comments are not supported in Zabbix emails) Connection security Select the

compatible IPv6 ad- dresses” (0000::/96 pre- fix) are sup- ported but dep- re- cated by RFC4291. Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain Spaces are al- Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain Spaces are allowed 连接，并期望一个登录提示 (’:’ 在最后)。如果未指定，则使用缺省端口 23。 Item net.udp.service parameters ntp 在 UDP 上发送一个 SNTP 包，并根据 RFC 4330, section 5需要验证响应。如果未指定，则使用默认端口 123。 10 Implementation details of net.tcp.service and net.udp

compatible IPv6 ad- dresses” (0000::/96 pre- fix) are sup- ported but dep- re- cated by RFC4291. Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain Spaces are al- Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain Spaces are allowed 连接，并期望一个登录提示 (’:’ 在最后)。如果未指定，则使用缺省端口 23。 Item net.udp.service parameters ntp 在 UDP 上发送一个 SNTP 包，并根据 RFC 4330, section 5需要验证响应。如果未指定，则使用默认端口 123。 10 Implementation details of net.tcp.service and net.udp

地 址。 ’0.0.0.0/0’ 用 来 允 许 任 何 IPv4 地 址。 注 意， “IPv4 兼 容 IPv6 地 址” (0000::/96 开 始) 允 许 使 用， 但 被 RFC4291遗 弃。 例 子: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain Zabbix 2.2 以 后 支 持 是一样的，’::/0’ 允许所有 IPv4 或 IPv6 地址。 ’0.0.0.0/0’ 用来允许任何 IPv4 地址。 注意，”IPv4 兼容 IPv6 地址” (0000::/96 开始) 允许使用，但 被 RFC4291遗弃. 例子: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain Zabbix 2.2 以后支持空格。 ServerActive 连接，并期望一个登录提示 (’:’ 在最后)。如果未指定，则使用缺省端口 23。 Item net.udp.service parameters ntp 在 UDP 上发送一个 SNTP 包，并根据 RFC 4330, section 5需要验证响应。如果未指定，则使用默认端口 123。 5 触发器 118 1 支持的触发器函数 trigger expressions 可用的函数列出如下。 函数

compatible IPv6 ad- dresses” (0000::/96 pre- fix) are sup- ported but dep- re- cated by RFC4291. Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain Spaces are al- Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain Spaces are allowed Note, that ”IPv4-compatible IPv6 addresses” (0000::/96 prefix) are supported but deprecated by RFC4291. Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain Spaces are allowed