Help modifying a template

[doogiehausermd]

Hi there, having some issues with the template FortiGate by SNMP as subject says. I posted this to reddit but I thought posting here might be a better idea.

Lots of the values are coming up with no OID found for my access points utilizing this template. For example ,"Preprocessing failed for: .1.3.6.1.4.1.12356.101.14.4.3.1.1.1.16.70.80.52.51 .snip.50.snip.50 = STRING: ... 1. Failed: unable to extract value for given OID: no data was found" for memory capacity for each AP.

I have dug in and see that clicking on the item it says, wc.mem.size[fgWcWtpSessionWtpMemoryCapacity.1.3.6.1.4.1.12356. 101.14.4.3.1.1.1.16.70.80.52.51.snip.50.snip.50]. Now, I know no OID is really that long so my issue is in that item config itself. So I backed up a level via the web UI here to Wireless Discovery, which has the key as wc.mem.size[fgWcWtpSessionWtpMemoryCapacity.{#SNMPINDEX}] and the master item is the "SNMP walk wireless AP" item.

If I manually walk it, I get the proper data, but I have no idea how to translate the serial number in quotes into, well, something manageable in Zabbix so this can work. Obviously {#SNMPINDEX} is my issue. Is there a way I can implement quotation marks on it? I tried wc.mem.size[fgWcWtpSessionWtpMemoryCapacity."{#SNMPINDEX}"] without luck. What is the right way to properly modify the template to capture this data below?

support@zbx-proxy:~$ snmpwalk -v2c -c public -m +FORTINET-FORTIGATE-MIB 10.10.14.1 FORTINET-FORTIGATE-MIB::fgWcWtpSessionWtpMemoryCapacity
FORTINET-FORTIGATE-MIB::fgWcWtpSessionWtpMemoryCapacity.1."FP432FTFXX XXXX1" = Gauge32: 891288
FORTINET-FORTIGATE-MIB::fgWcWtpSessionWtpMemoryCapacity.1."FP432FTFXX XXXX2" = Gauge32: 891288
FORTINET-FORTIGATE-MIB::fgWcWtpSessionWtpMemoryCapacity.1."FP432FTFXX XXXX3" = Gauge32: 891288
FORTINET-FORTIGATE-MIB::fgWcWtpSessionWtpMemoryCapacity.1."FP432FTFXX XXXX9" = Gauge32: 891288

Can someone give me some guidance on where to start trying to fix this?

[troffasky]

Is that space really there in that OID? You can't edit a discovered item, but I suggest that you manually create it, identical to how it is discovered BUT without the space in the OID. Or snmpget that one OID, without the space.
You can also use "snmptranslate -On <some OID>" to get the numeric OID.

[doogiehausermd]

Is that space really there in that OID? You can't edit a discovered item, but I suggest that you manually create it, identical to how it is discovered BUT without the space in the OID. Or snmpget that one OID, without the space.
You can also use "snmptranslate -On <some OID>" to get the numeric OID.

The space is not there, sorry about that. I didn’t even realize it was there when I pasted it

[doogiehausermd]

So Zabbix is converting the serial number to decimal, and I need to get it to stop doing so. Off to the manuals... will update if I find the right answer.

[mrnobody]

Nop, Zabbix is not converting in this case.

LLD (Low Level Discovery) as it name says, is low level, it's more readable for machine than we humans.

In other words, for example; you can walk directly OID for know all interfaces operational status like:

snmpwalk -v2c -c public 10.10.14.1 1.3.6.1.2.1.2.2.1.8

It returns all states of interfaces, and a lot of OID numbers, like machines want! And remember, Zabbix is a software that run on machines, so it likes it too

And you can do the same thing, with translated information:

snmpwalk -v2c -c public 10.10.14.1 IF-MIB::ifOperStatus

It returns same data, but without OID numbers, only with human "more readable" information.

Inside Zabbix you can use both, translated or directly OID.

So, like troffasky said, use snmptraslate.

In my example
Command: snmptranslate -On IF-MIB::ifOperStatus
Returns: .1.3.6.1.2.1.2.2.1.8

In your case, snmptraslate
Command: snmptranslate -On FORTINET-FORTIGATE-MIB::fgWcWtpSessionWtpMemoryCapacity
Returns: OID you are searching for.

If you need to manipulate the OID inside of Zabbix, after getting it without translations, i suggest using preprocessing + JS.

And, if you want to concatenate OID result + {#SNMPINDEX}, don't use ""

[Fossil2876]

Did you ever find the solution to this? I am having a similar issue with the template.

[Fossil2876]

If anyone else has the issue from the WTP SNMP walk value in the default template it seems like the snmp walk in the Master Item needed to be bumped up a bit to allow for all of the information that was discovered to populate.

I change: SNMP walk wireless AP
SNMP OID: from walk[1.3.6.1.4.1.12356.101.14.4.3.1] to walk[1.3.6.1.4.1.12356.101.14.4] and now the data loads for the unsupported items on the APs.