SNMP & OID

[Muharrem Salici]

Hi!
This is my first post ever in a forum (:

Zabbix Version: 7.4.5
Debian Version: 12

What am I trying to do? (My goal)

• I want to automatically discover my printers.
• After discovery, I want to sort the printers into groups based on their enterprise ID; for example, 1347 = Kyocera.

The problem / what I configured:

• CLI on the Zabbix Server:
  < snmpwalk -v2c -c [snmp_key] [printer_ip] .1.3.6.1.2.1.1.2.0 >
• Result:
  < SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.1347.41 >
• I created a discovery rule using the SNMP agent check on OID .1.3.6.1.2.1.1.2.0

Now we configured Zabbix to check the network using an SNMP check with that OID (.1.3.6.1.2.1.1.2.0).
We also verified the value of the SNMP OID on the server (SNMPv2-SMI::enterprises.1347.41).
To test what Zabbix receives, I created an item that performs an SNMP check on the OID .1.3.6.1.2.1.1.2.0 — same result (SNMPv2-SMI::enterprises.1347.41).

Next, I created a discovery action with the following condition:

• Condition: "Received value contains SNMPv2-SMI::enterprises.1347"
• Operation: Add to host groups: Access/IT-SUP, Printer/HP

But it doesn’t work.
When I change the condition to:

• "Received value contains .1347"
  It works. However, I don’t want to rely only on the number because, for example, HP’s enterprise number is 11.
  This could be risky since another printer or network device could also have 11 in their ID.
  I want the condition to specifically match "SNMPv2-SMI::enterprises.xx".

What could be the problem?
I suspect that Zabbix discovery rules/actions don’t translate the OID into SNMPv2-SMI::enterprises.1347.41; rather, it may translate it to .1.3.6.1.4.1.1347.41.
This would be confusing since the item itself returns the correct value.

If you need more information, feel free to ask (:
Thank you to everyone looking into this!

[troffasky]

To put it another way, the "Received Value" can only ever be the numeric value. If your actions/triggers/whatever operate on the numeric value rather than the symbolic one, at least you know they won't break if the MIB file gets updated, etc.

[troffasky]

I agree with your suspicion. Is it a problem? .1.3.6.1.4.1.1347.41 is no less unique than SNMPv2-SMI::enterprises.1347.41.

[Muharrem Salici]

Thank you for your reply.
I could let it be on "contains: 1347.".
But i dont get it why the Discovery acts diffrent from the item/cli.

I guess its just a thing where i want to know why it behaves like that and want to have it as " SNMPv2-SMI::enterprises" just because!

[troffasky]

To put it another way, the "Received Value" can only ever be the numeric value. If your actions/triggers/whatever operate on the numeric value rather than the symbolic one, at least you know they won't break if the MIB file gets updated, etc.

[Muharrem Salici]

Well, thank you for the conversation.
I will configure it with the numeric value