Host interface missing in Item-Template

[babelr]

Hi!

My Setup
Zabbix Server Version: 3.4.2
Zabbix Proxy Version: 3.4.2
Server / Proxy running on Oracle Linux Server 7.4
Installed using zabbix yum repositories

What I'm trying to do
I'm monitoring a bunch of HP ProLiant Servers using the zabbix agent for linux and IPMI via HP's Integrated Lighs Out (iLO) Management interface.

What I'd like to do is, create a "Simple check" Item along with a trigger, which pings the iLO IP Address and make other triggers depend on the first one. So in other words, if iLO goes down or gets disconnected all alerts would be suppressed and mail flooding would be avoided.

What I have so far

• Host with 2 IP Addresses (Agent interface and IPMI interface)
• A few items and triggers using Zabbix Agent
• A few items and triggers using the IPMI interface
• One item using simple check with "icmpping[,3]" as key and the IPMI IP address as host interface

This works (confirmed that the icmp ping goes to the IPMI address with tcpdump)

That's where I'm stuck
When I tried to move that simple check item into a template, I noticed that there is no "Host interface" field. So how can I specify that the IPMI Address has to be used?
I thought about using the <target> parameter of icmpping with a {HOST.CONN} macro, but it doesn't seem to provide the IPMI Address, only the Zabbix Agent Address
Is there a Macro for the IPMI Connection? I've been through the Supported Macros by Location list and can't seem to find any

Any help appreciated
Cheers
Rene

[kaspars.mednis]

Hello,

documentation says

https://www.zabbix.com/documentation/3.4/manual/appendix/macros/supported_by_location#footnotes

2 The {HOST.*} macros supported in item key parameters will resolve to the interface that is selected for the item. When used in items without interfaces they will resolve to either the Zabbix agent, SNMP, JMX or IPMI interface of the host in this order of priority.

SNMP items work for me this way, i think IPMI must work too.
just define IPMI item in template, add IPMI interface to the host and try

Regards,
Kaspars

[babelr]

Hey Kaspars

Thanks for your reply!
I may not have expressed myself very well. I either need a macro, that returns the IPMI address specifically or some way to define the interface in the template when using a "simple check" item.
In my case, using {HOST.*} will always return the address of the Zabbix agent interface, because the host it's going to be applied to, has the Zabbix agent interface and the IPMI interface configured.

I managed to find a solution (or workaround) in the meantime.

• I created the simplecheck item in the template with "icmpping[,3]" as key.
• I applied that template to a host, configured with a Zabbix agent interface and an IPMI interface
• I edited the item on that host (not the template) and set the Host interface to the IPMI connection

By doing so I lose the benefits of using a template, because I have to edit every single item after applying it to multiple hosts.
I wonder why the item's "Host interface" selection is not usable in the template but only on the host.

Regards
Rene

[kaspars.mednis]

Ok, the use user macro {$IPMI_IP} on template, use it in items keys and edit it on each host.
still manual editing on each host, but at least not on each item...

If i will find some better ideas, i will write here

Regards,
Kaspars

[Flocky]

If i will find some better ideas, i will write here

Hello, I have the same problem and no idea how to solve it. Can you help me ?

[jnovacek]

Sorry for adding to many years old topic, but I need the same thing. There is still no better way how to define interface (SNMP, or IMPI) for Item in Template ?
I have couple hundreds servers with both Agent and SNMP interfaces defined, with different IPs (Agent=OS; SNMP=ILO) and I would like to ping ILO interface as part of "HP ILO SNMP" template and ping Agent interface IP as part of "ICMP ping" template.
It is very much different situation whether ILO or main server OS is not responding to ICMP checks, and I don't like the idea of having two separate hosts per server (one for ILO and one for OS).