LLD discover returns a list of PSUs. in LLD maxros there are:
{#swnum}-contains the number of the switch in the stack.
{#module}-contains the value of module\nomodule. Different types should be taken into account separately
, items are created.
next, I created 18 items that count the number of PSUs (9 variants of values can take swnum and 2 variants of values can take module 9x2=18)
the key of the item that counts the total number, for example, such a psu.count.[module,Sw1] is also correctly counted.
Question: why, if I specify in the trigger prototype
last(/ciscoEnvMonMib PSU_FAN_Temp/psu.count.[{#MODULE},{#SWNUM}])=1
,then zabbix wright:
Incorrect item key "psu.count.[{#MODULE},{#SWNUM}]" provided for trigger expression on "ciscoEnvMonMib PSU_FAN_Temp".
How to avoid it?
{#swnum}-contains the number of the switch in the stack.
{#module}-contains the value of module\nomodule. Different types should be taken into account separately
, items are created.
next, I created 18 items that count the number of PSUs (9 variants of values can take swnum and 2 variants of values can take module 9x2=18)
the key of the item that counts the total number, for example, such a psu.count.[module,Sw1] is also correctly counted.
Question: why, if I specify in the trigger prototype
last(/ciscoEnvMonMib PSU_FAN_Temp/psu.count.[{#MODULE},{#SWNUM}])=1
,then zabbix wright:
Incorrect item key "psu.count.[{#MODULE},{#SWNUM}]" provided for trigger expression on "ciscoEnvMonMib PSU_FAN_Temp".
How to avoid it?