Item procotols from multiple sources preventing tigger prototype creation

[stevencnz]

Hi there,

I have configured LLD Discovery for BGP neighbors based on their remote IP (using the bgpPeerRemoteAddr OID - 1.3.6.1.2.1.15.3.1.7).

I can create prototype items and the items are discovered ok.

However when I attempt to create a trigger based on those values, it appears that I cannot reference more than one value.

For example, I am trying to configure the following Trigger to react to a BGP neighbor going down, based on a couple of discovered Items:

{Root_Router:bgpPeerOperationalStatus[{#SNMPVALUE}].last(#3)}<>6 and {Root_Router:bgpPeerAdminStatus[{#SNMPVALUE}].last(0)}=2

When I attempt to save the Trigger, I get an error that states:

Trigger prototype <NAME> contain item prototypes from multiple discover rules.

But the problem is they are all from the "BGP Neighbors" Discovery Rule. If remove either of the statements either side of the "and" the trigger saves ok.

The Template that this Discovery Rule is in does inherit from another Template - but nothing from that inherited Template is reference in this Trigger.

Also, I downloaded and imported the template found here: https://share.zabbix.com/network_devices/cisco-bgp4 and it works fine. And it appears to do exactly what I'm trying doing.

I've been trying to figure out why this one works and yet the one that I created (which is virtually a carbon copy) fails - but to no avail. It seems very restrictive to only be able to configure a Trigger based on a single discovery rule.

I have attached a few images showing how my discovery/prototypes are configured.

Any help would be much appreciated.

[batchenr]

Hi there,

I have configured LLD Discovery for BGP neighbors based on their remote IP (using the bgpPeerRemoteAddr OID - 1.3.6.1.2.1.15.3.1.7).

I can create prototype items and the items are discovered ok.

However when I attempt to create a trigger based on those values, it appears that I cannot reference more than one value.

For example I am trying to configure the following to poll for when a BGP neighbor goes down:

{Root_Router:bgpPeerOperationalStatus[{#SNMPVALUE}].last(#3)}<>6 and {Root_Router:bgpPeerAdminStatus[{#SNMPVALUE}].last(0)}=2

When I attempt to save the trigger I get an error that states:

Trigger prototype <NAME> contain item prototypes from multiple discover rules.

But the problem is they are all from the "BGP Neighbors". If remote either of the statements either side of the "and" the trigger saves ok.

The Template this discovery rule is in inherits another from another Template - but nothing from that inherited Template is used in this discovery process.

Also, I downloaded and imported the template found here: https://share.zabbix.com/network_devices/cisco-bgp4 and it works fine. And it appears to do EXACTLY what I'm trying doing.

I've been trying to figure out why this one works and one I created (which is virtually a carbon copy of the downloaded one) fails - but to no avail. It seems very restrictive to only be able to configure a trigger based on a SINGLE discovery rule.

I have attached a few images showing how my discovery/prototypes are configured.

Any help would be much appreciated.

try like this :


({Root_Router:bgpPeerOperationalStatus[{#SNMPVALUE}].last(#3)}<>6) and ({Root_Router:bgpPeerAdminStatus[{#SNMPVALUE}].last(0)}=2)

[stevencnz]

Resolution

Hi batchenr,

Thanks for the help. But we have managed to solve it.

It turns out that the Hosts to which I was trying to apply this Trigger, were also members of the Template that I had downloaded (from https://share.zabbix.com/network_devices/cisco-bgp4).

The discovered items from that template were already in existence for the hosts. This seemed to produce a conflict within Zabbix.

I had deleted the cisco-bgp4 template but only clicked Delete rather than Delete and Clear. As such the hosts held on to their discovered items resulting in the conflict.

To fix it, I re-imported cisco-bgp, re-addded all of the hosts and then deleted the template using the Delete and Clear button.