Checkpoint SNMP template giving duplicate generic names for items.

[nebular]

Hello, I'm currently using 6.4.11 on Ubuntu 22.04.4

I added in my Checkpoint firewall, using the Checkpoint SNMP template over snmp3. After much struggling I was finally able to get it to connect and pull data (I needed to install the checkpoint mib file), however the item names that were generated by the discovery rules leave something to be desired. All interfaces and disks are labeled as $1 (which might be because it pulled that data from the linked templates SNMP Interfaces and SNMP Disks). Is there anything I missed with the Checkpoint SNMP template or something I can change that will generate more useful names for items (Which I think it was supposed to do with $1 probably being a variable). Currently I have 11 "Incoming traffic on interface $1" and 11 "Inbound errors on interface $1" items amongst others and I'd rather not have to manually match each item up with each other and rename them.

[Hamardaban]

You are using a template for an old version of zabbix. Previously, it was possible to use positional macros ($X) in the names of items.
This feature has now been removed.
You need to change the prototypes and use LLD macros in them (#abcd)

[cyber]

with v7 this feature should come back...

[Hamardaban]

I read in the Roadmap_7 about the return of using custom macros in names and in prototypes....
And we can only conclude about the return of positional macros by their appearance in the documentation in the list of supported macros..:-)

[nebular]

Well this is mildly frustrating as the template is one I downloaded directly from the integrations section of the website after clicking on the checkpoint logo. One would think that they would either keep the templates advertised on the page up to date with functionality, or remove it as a seemingly officially supported option.

Now I'm wondering if I should take the time to learn how to adapt the template to work as intended with 6.4, or look into reverting to 6.0 (the stated version for the template) as it is still in LTS and then look to upgrade once 7 is released in Q2. Our current installation isn't extensive, so even if I had to recreate it from scratch, it wouldn't be a big deal. I guess it depends if the custom macros will work the same way in 7 as they did in 6. Anyone have any idea if that will be the case?

Edit: I thought 'SNMP Device', 'SNMP Interfaces' and 'SNMP Disks' templates were preinstalled, however they are created when importing the 'Checkpoint SNMP' template. It looks like when they updated Checkpoint SNMP to 6.0 they didn't update the other templates it created. Since all the templates only use $1 it's easy enough to just replace it with [{#SNMPVALUE}] used in the keys.

[Hamardaban]

All the listed options are normal - you can choose.
Of course, the easiest way is to change the $x macro to {#blablabla}

[GRIFFCOMM]

You are using a template for an old version of zabbix. Previously, it was possible to use positional macros ($X) in the names of items.
This feature has now been removed.
You need to change the prototypes and use LLD macros in them (#abcd)

Which version of Zabbix did that change happen? i see this in a template i have, it would be nice to figure out how to fix it.

[Hamardaban]

https://www.zabbix.com/documentation/5.2/en/manual/installation/upgrade_notes_522?hl=Positional%2Cmacros%2Cpositional

[nebular]

Which version of Zabbix did that change happen? i see this in a template i have, it would be nice to figure out how to fix it.

I looked into it, it was depreciated in 4.0 and completely removed in 6.0.

If you look here: https://www.zabbix.com/documentation...rade_notes_400 halfway down under Informational it says that the positional macros have been depreciated and gives a suggested way of adapting item prototypes. The best thing you can do to make adapting the template easier is to figure out what data it was actually pulling based on position. For the Checkpoint one I'm using, it only used $1 which was easy enough to figure out that was coming from the key. You'll probably want to find the documentation for Zabbix 3.4.x to learn exactly how positional macros work.

Edit: found the page in the 3.4 manual that describes how the positional macros work: https://www.zabbix.com/documentation...fig/items/item