Discover two different IPs for same host

[GeorgeHansen]

Hello fellow Zabbix Users,

this is my first post, please have mercy but I could not find anything related to my problem.

Is it possible to discover two different IPs on the same host?
We are using Windows Server machines with Agent2 installed and discovering the agent and SNMP interface works fine.
But we also have to monitor the BMC/mainboard, so CPU temperature, voltage errors, PSU failure etc. This was supposed to happen over SNMP traps, so no authentication, no agent, nothing.
With a discovery for our networks, Zabbix obviously creates two seperate entitites for the same physical host. This could be a work around, but it is rather unpleasant for us.

For a better understanding see attachment.
What may help: The BMC IP adress is always +190 in the last octet, so calculation could help.

Kind regards,
George

[niveastn]

Hi there!

What your discovery rule looks like?

[tim.mooney]

Is it possible to discover two different IPs on the same host?

My answer to the "is it possible" question is generally that almost anything is possible, if it's important enough to you and you are determined enough. Frequently the real question is whether it's important enough to invest the time it will take to accomplish. That almost always goes back to an organization's priorities. I could probably accomplish what you're asking about in a few hours, but if you're new to Zabbix and especially if you were to go the API route (that I mention below), it might take someone in your organization a few weeks before they had the functionality working reliably. The question is, is that worth the time for your organization?

We are using Windows Server machines with Agent2 installed and discovering the agent and SNMP interface works fine.
But we also have to monitor the BMC/mainboard, so CPU temperature, voltage errors, PSU failure etc. This was supposed to happen over SNMP traps, so no authentication, no agent, nothing.
With a discovery for our networks, Zabbix obviously creates two seperate entitites for the same physical host. This could be a work around, but it is rather unpleasant for us.

For a better understanding see attachment.
What may help: The BMC IP adress is always +190 in the last octet, so calculation could help.

Kind regards,
George

As niveastn suggested, this comes down to how much you have customized your discovery rules. The default rules are good defaults, but they're not going to do what you want. I assume you have carefully read the "Interface creation when adding hosts" section of https://www.zabbix.com/documentation...work_discovery , as it's particularly appropriate to your situation. What are you using for "Device uniqueness criteria"?

If you can't get this working solely through network discovery, there is an alternate approach that I know would work, but it requires that someone in your organization write a custom script that uses the Zabbix API to modify existing hosts that have been discovered, to add at least the tertiary interface, and possibly the secondary interface. I can explain more if needed, if the device uniqueness settings for network discovery don't completely solve your problem.