Ad Widget

**kloczek** · 25-05-2018, 19:03

If OID does not exist on SNMP agent side it is not zabbix issue .. really.

**Theolude** · 28-05-2018, 10:16

Originally posted by kloczek

If OID does not exist on SNMP agent side it is not zabbix issue .. really.

Hi Kloczek,

It's not exactly that ... the OID exist as a leaf of the master OID.
I know the master OID, but the leaf is unknown until an error occur. I can get it with a snmpwalk from the server, but sure a snmpget from the master OID return nothing.

I would like to know if Zabbix can manage this situation. It means, getting a tree of a snmpwalk from a know OID roots (it's possible to get more than one leaf in case of multiple errors).

Thanks, Théo

**aigars.kadikis** · 28-05-2018, 14:20

Originally posted by Theolude

Hi Kloczek,

It's not exactly that ... the OID exist as a leaf of the master OID.
I know the master OID, but the leaf is unknown until an error occur. I can get it with a snmpwalk from the server, but sure a snmpget from the master OID return nothing.

I would like to know if Zabbix can manage this situation. It means, getting a tree of a snmpwalk from a know OID roots (it's possible to get more than one leaf in case of multiple errors).

Thanks, Théo

Maybe MIB translations fails. Is this command working without errors?:

Code:

snmpwalk -v2c -cpublic 192.168.88.1 -On .1.3.6.1.2.1.43.18.1.1.8  | cut -d ' ' -f 1 | xargs snmpget -v2c -cpublic 192.168.88.1 -On

Does all leafs under .1.3.6.1.2.1.43.18.1.1.8 happens to be encoded in Hex-STRING?

**Theolude** · 28-05-2018, 14:46

Originally posted by aigars.kadikis

Maybe MIB translations fails. Is this command working without errors?:

Code:

snmpwalk -v2c -cpublic 192.168.88.1 -On .1.3.6.1.2.1.43.18.1.1.8 | cut -d ' ' -f 1 | xargs snmpget -v2c -cpublic 192.168.88.1 -On

Does all leafs under .1.3.6.1.2.1.43.18.1.1.8 happens to be encoded in Hex-STRING?

No, this is the Xerox support which explain me that.
I try your code, if i've ANY error on printer 192.168.10.22, i got it :

Code:

.1.3.6.1.2.1.43.18.1.1.8 = No Such Instance currently exists at this OID

If i've an error, i got it (with your little code):

Code:

6D: Unknown Object Identifier (Sub-id not found: (top) -> 6D)
6C: Unknown Object Identifier (Sub-id not found: (top) -> 6C)
6E: Unknown Object Identifier (Sub-id not found: (top) -> 6E)
6C: Unknown Object Identifier (Sub-id not found: (top) -> 6C)

If i do a snmpwalk only, i've :

Code:

.1.3.6.1.2.1.43.18.1.1.8.1.549 = Hex-STRING: 30 30 35 2D 31 32 31 20 49 6E 63 69 64 65 6E 74
20 70 61 70 69 65 72 20 64 61 6E 73 20 6C 65 20
63 68 61 72 67 65 75 72 20 64 65 20 64 6F 63 75
6D 65 6E 74 73 2E 20 44 C3 A9 67 61 67 65 72 20
6C 65 20 63 69 72 63 75 69 74 20 70 61 70 69 65
72 2E 20 4C 61 20 6E 75 6D C3 A9 72 69 73 61 74
69 6F 6E 20 65 73 74 20 64 C3 A9 73 61 63 74 69
76 C3 A9 65 C2 A0 3B 20 74 6F 75 74 65 73 20 6C
65 73 20 61 70 70 6C 69 63 61 74 69 6F 6E 73 20
6E 27 75 74 69 6C 69 73 61 6E 74 20 70 61 73 20
6C 65 20 73 63 61 6E 6E 65 72 20 73 6F 6E 74 20
64 69 73 70 6F 6E 69 62 6C 65 73 2E

WHich is the correct error code in Hex (and what i want), translation in ASCII is :
CT005-121 Incident papier dans le chargeur de documents. Dégager le circuit papier. La numérisation est désactivée ; toutes les applications n'utilisant pas le scanner sont disponibles.

**aigars.kadikis** · 28-05-2018, 15:09

What snmpget version you are using:

Code:

snmpget -V

What distribution lies under the hood?

It seems like the problem may be related to multiline Hex-STRING. Does your device has any single line Hex-STRING OID? Can it be queried by snmpget?

**Theolude** · 28-05-2018, 15:17

Code:

snmpget -V

NET-SNMP version: 5.7.3

What distribution lies under the Hood?

Debian GNU/Linux 9.4 (stretch)

It seems like the problem may be related to multiline Hex-STRING. Does your device has any single line Hex-STRING OID? Can it be queried by snmpget?

In fact it's a multiline value Hex string.

Yes the Xerox printer can be queried by SNMPGET (read my comments in my last post).

The problem is NOT to get the value (it's a next problem), for moment my question is :
How to manage an unknown OID, which appears ONLY when an error occurs on the Xerox device, and we know only the ROOD OID.
This ROOT OID has any LEAF, NEVER, EXCEPT in case of problem on the device. But we don't know the OID of this leaf before the problem occurs.

How to manage that ?

**aigars.kadikis** · 28-05-2018, 16:38

You need to discover the indexes. Let me design one example. For example, if my snmpwalk output is

Code:

# snmpwalk -v2c -cpublic 192.168.88.1 -On 1.3.6.1.2.1.17.4.3.1.1
.1.3.6.1.2.1.17.4.3.1.1.112.90.182.181.190.45 = STRING: 70:5a:b6:b5:be:2d
.1.3.6.1.2.1.17.4.3.1.1.184.39.235.203.74.178 = STRING: b8:27:eb:cb:4a:b2
.1.3.6.1.2.1.17.4.3.1.1.228.141.140.131.49.147 = STRING: e4:8d:8c:83:31:93

The base is .1.3.6.1.2.1.17.4.3.1.1
and leaf indexes are
112.90.182.181.190.45
184.39.235.203.74.178
228.141.140.131.49.147

In Zabbix we need to create an index discover:

In your particular example, while detecting printer error messages, you probably need very short update interval.
'Keep lost resources period' = 0 will automatically delete discovered items (messages) in Zabbix when the problem in the printer is solved, and there are no leafs available under base OID.

Create item prototype:

Pure values are extracted:

Regards,

**Theolude** · 28-05-2018, 16:44

Owww

Too much powerful

I'm not really trained with discovery tools in ZABBIX, in this case it seems very powerful. I try to build something functional and let you know.

Thanks a lot for your help.

**Theolude** · 28-05-2018, 17:14

Uhm... i've some disturbing problem

I've set my discovery rule and my item, following your instructions... but i've this error :

Invalid SNMP OID: pairs of macro and OID are expected

I've check my root OID, all is clean

Perhaps this is my trigger which creates the problem ?

**aigars.kadikis** · 29-05-2018, 11:06

Originally posted by Theolude

Uhm... i've some disturbing problem

I've set my discovery rule and my item, following your instructions... but i've this error :

I've check my root OID, all is clean

Perhaps this is my trigger which creates the problem ?

Please also share the screen with discovery rule.

**Theolude** · 29-05-2018, 12:55

See below the requested copy screen :

**aigars.kadikis** · 29-05-2018, 14:12

You need to name OID SNMP base like it was in my screenshot. It does not matter what you choose in this field. I would go with:

Code:

discovery[{#ERRMSG},1.3.6.1.2.1.43.18.1.1.8]

**Theolude** · 30-05-2018, 11:56

I'm just reading the documentation https://www.zabbix.com/documentation...y_of_snmp_oids to understand better what i do. I've well and better understand the "macro link" in the discovery rule.

And now it's work.

Thanks for your help

**Theolude** · 30-05-2018, 12:55

... uhm ...

Last problem. I get Hexa value, i would translate automatically this value in ASCII ...
I've read that about

Loading...

https://support.zabbix.com/browse/ZBXNEXT-505

with status NOT SOLVED ...

How to manage it?

Ad Widget

[SNMP][Problem with Xerox MFP][How to manage a SNMP tree]

[SNMP][Problem with Xerox MFP][How to manage a SNMP tree]

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment