[ZBX-19653] Host prototype / vmware.hv.discovery: Cannot link template(s) invalid token starting with "{#MULTIPATH.COUNT}". Created: 2021 Jul 08  Updated: 2024 Apr 10  Resolved: 2022 Oct 10

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 5.4.2
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Marcel Renner Assignee: Michael Veksler
Resolution: Duplicate Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

SUSE Linux Enterprise Server 15 SP2, PostgreSQL, NGINX, vCenter 6.7.0

Attachments: GIF File Zabbix_2021_07_09_15_02_14_463-invalid-token-multipath.gif     GIF File Zabbix_2021_07_09_15_23_01_251-problem-goes-away-trigger-missing.gif     PNG File image-2021-07-08-11-54-27-429.png     PNG File image-2021-07-08-12-02-47-918.png    
Issue Links:
Duplicate
is duplicated by ZBX-20238 Incorrect LLD rule behaviour in case ... Closed
Team: Team B

 Description   

Steps to reproduce:

  1. Assign VMware template to a vCenter host.
  2. Wait until hypervisor discovery vmware.hv.discovery is finished.
  3. Check info column of hypervisor discovery vmware.hv.discovery.

Result:

Cannot link template(s) invalid token starting with "{#MULTIPATH.COUNT}".

**

The ESX host is not correctly assigned to the template. Some items and triggers are assigned, but as soon as the trigger with *

{#MULTIPATH.COUNT}* has to be assigned, an error occurs and further elements are missing.


Expected:
*{#MULTIPATH.COUNT}

* **is detected as an invalid token. *

{#MULTIPATH.COUNT}* should be a valid token so that the discovery is successful and template is correctly assigned with all item, trigger and graph prototypes.

Workaround:

Exclude trigger prototype with *{#MULTIPATH.COUNT}

* from discovery.

OR

Assign VMware Hypervisor template directly to ESX host.

 Comments   
Comment by Michael Veksler [ 2022 Oct 10 ]

Closing this as a duplicate of ZBX-20238 for now, if you have any more questions, feel free to reopen this ticket!

Generated at Tue Jun 03 17:59:59 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.