[ZBXNEXT-6121] Support for LLD macro in SNMPv3 contextname is not working Created: 2016 Mar 25  Updated: 2023 Sep 11

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

Type: New Feature Request Priority: Critical
Reporter: Jean-Eudes Onfray Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 23
Labels: lld, snmp, snmpv3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File lld_macro_in_snmpv3_contextname.diff    
Issue Links:
Duplicate

 Description   

I'd like to add support for LLD macro in SNMPv3 contextname item field.

I want to monitor BGP peers in several Avaya Ethernet Routing Switches.

Some of the BGP peers are inside VRF and can only be accessed with the use of specific SNMPv3 contextname. I've created a discovery rule that list all VRF and then all BGP peers inside these. For example:

{
	"data":[
		{
			"{#SNMPVALUE}":"BGP to xx.xx.xx.xx",
			"{#SNMPINDEX}":"1.4.dd.dd.dd.dd.1.4.xx.xx.xx.xx",
			"{#SNMPCONTEXT}":""
		},
		{
			"{#SNMPVALUE}":"In vrf1 BGP to yy.yy.yy.yy",
			"{#SNMPINDEX}":"1.4.dd.dd.dd.dd.1.4.yy.yy.yy.yy",
			"{#SNMPCONTEXT}":"vrf1"
		}
	]
}

Here's a patch against current trunk that should do the job!

Can this feature be included in some next release?

Thanks

 Comments   
Comment by 11Thirty8 [ 2018 Feb 06 ]

I have this need too.

Specifically trying to monitor Checkpoint VS (Virtual Systems) with SNMP LLD via a template.
The list of VS context names (vsid1, vsid2, etc..) is available via SNMPv2, and the discovery rule looks like this:

Name: VS Stats
Type: SNMPv2 agent
Key: vacmContextName
SNMP OID: .1.3.6.1.6.3.16.1.1.1.1.5
SNMP community: {$SNMP_COMMUNITY}

An item prototype then looks like this:

Name: {#SNMPVALUE} - Connections: Current
Type: SNMPv3 agent
Key: fwNumConn.[{#SNMPVALUE}]
SNMP OID: .1.3.6.1.4.1.2620.1.1.25.3.0
Context name: ctxname_{#SNMPVALUE}
Security name: *********
Security level: authNoPriv
Authentication passphrase: ********

This gives nice LLD items on the templated host like this:

Name: VS Stats: vsid1 - Connections: Current
Key: fwNumConn.[vsid1]

Name: VS Stats: vsid2 - Connections: Current
Key: fwNumConn.[vsid2]
etc..

Item status is "Enabled" and shows up in latest data, but no values ever get collected, since the

{#SNMPVALUE} part in "Context name" never gets resolved, and "ctxname_{#SNMPVALUE}

" is instead send to the Checkpoint firewall, which it of course cannot translate to an existing VS context.

I've verified that using a user definable macro indeed does work in the "Context name" field, which does produce valid item data via SNMPv3.

Having the

{#SNMPVALUE}

, and maybe also

{#SNMPINDEX}

, macro resolve properly in the "Context name" field would be very useful.

I hope this usage description might help push the development of this forward.
Thanks in advance.

Comment by Alexander Vladishev [ 2020 Aug 07 ]

I cannot treat this issue as a bug report. Currently Zabbix does not officially support lld macros in the SNMP context field. Moving back to ZBXNEXT project.

Comment by Alexander Vladishev [ 2020 Aug 07 ]

Probably this will be implemented in ZBXNEXT-2072.

Comment by Dimitri Bellini [ 2020 Sep 04 ]

Hi Alexander,

I would encourage the implementation of this feature because is very import for a good "discovery" on most of Network/SAN devices.

Thanks so much

Generated at Fri Apr 19 04:15:55 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.