[ZBXNEXT-7069] Add support for vSphere Fault Tolerance (FT) Created: 2021 Nov 22  Updated: 2024 May 13

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: 5.4.7
Fix Version/s: None

Type: New Feature Request Priority: High
Reporter: Marcel Renner Assignee: Michael Veksler
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 5.3.18-59.27-default #1 SMP Tue Oct 5 10:00:40 UTC 2021 (7df2404) x86_64 x86_64 x86_64 GNU/Linux
NAME="SLES"
VERSION="15-SP3"
VERSION_ID="15.3"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP3"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp3"

Attachments: PNG File image-2021-11-22-14-24-26-358.png     PNG File image-2021-11-23-12-05-05-607.png     PNG File image-2021-11-23-12-13-46-496.png    

 Description   

Steps to reproduce:
If you have VMs with vSphere Fault Tolerance (FT), there is a primary and secondary VM which are using the same name in vSphere. But vmware.vm.discovery is not able to take this into account.

Result:
Zabbix tries to create two hosts with the same name, which fails on the second one.

Expected:
There should be a label macro that allow you to detect if it is a virtual machine with FT and if it is a primary or a secondary one. My alternative would be to write the *

{#VM.ID}

* after the affected disovered host at the moment, which does not necessarily make it more readable.

As a small example, vSphere displays the VMs in the overview like this. If Zabbix would do the same for {*}

{#VM.NAME}

{}{*}, it would help a lot.

 Comments   
Comment by Marcel Renner [ 2021 Nov 22 ]

Steps to reproduce:
If you have VMs with vSphere Fault Tolerance (FT), there is a primary and secondary VM which are using the same name in vSphere. But vmware.vm.discovery is not able to take this into account.

Result:
Zabbix tries to create two hosts with the same name, which fails on the second one.

Expected:
There should be a label macro that allow you to detect if it is a virtual machine with FT and if it is a primary or a secondary one. My alternative would be to write the #VM.ID after the affected disovered host at the moment, which does not necessarily make it more readable.

As a small example, vSphere displays the VMs in the overview like this. If Zabbix would do the same for #VM.NAME, it would help a lot.

Generated at Fri Apr 11 23:29:45 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.