Brocade oid has no consistency

[sysadm01]

Hello.

I have some Brocade SAN switch.
And I monitor SFP power using zabbix

But Brocade oid has no consistency after iso.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.20 4

So I can't monitor like this .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.204 .100.45.16.0.0.0.0.0.0.0.0.{#SNMPINDEX}

can i using wild card in SNMP OID like this .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.204 .**********.{#SNMPINDEX}

how can i fix?

below is
SAN switch 1
iso.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.20 4.100.45.16.0.0.0.0.0.0.0.0.128 = STRING: "NA"
SAN switch 2
iso.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.20 4.100.38.16.0.0.0.0.0.0.0.0.128 = STRING: "NA"
SAN switch 3
iso.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.20 4.97.245.240.0.0.0.0.0.0.0.0.128 = STRING: "NA"
SAN switch 4
iso.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.20 4.100.43.112.0.0.0.0.0.0.0.0.128 = STRING: "NA"
SAN switch 5
iso.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.20 4.225.210.162.0.0.0.0.0.0.0.0.128 = STRING: "NA"
SAN switch 6
iso.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.20 4.223.177.234.0.0.0.0.0.0.0.0.128 = STRING: "NA"
Tags: None

[cyber]

I would say, it is not inconsistency, but you probably need to look up that WWN from somewhere else and then construct that OID using those values...
Some links to you

https://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_2_x/fabricware/mibs/reference/guide/alliance.pdf

https://mibs.observium.org/mib/FCMGMT-MIB/

I really hate SNMP..

[Por]

sysadm01 I'm facing the same issue, could sort out the IFALIAS problem on included Brocade templates but can't get SFP power to work... could you accomplish it?

[Por]

In case anyone needs it, I've attached the modified template with IFALIAS problem solved

[zbxusr2025]

I have the same problem with monitoring SFP optical tx/rx power in SAN Brocade switch, OID is ; 1.3.6.1.4.1.1588.2.1.1.1.28.1.1.4 from FA-EXT-MIB.

But the switch (Connectrix DS-7720B) answer in a longer and "strange" oid , for example similar to :1.3.6.1.4.1.1588.2.1.1.1.28.1.1.4.16.0.216.31.204 .100.45.16.0.0.0.0.0.0.0.0.{#SNMPINDEX}

And this OID changes from Switch to Switch , so even my discovery rule works find, I need a template for each switch.
(the first part keeps the same)

Do you have some suggestion or perhaps a template that works fine monitoring Brocade SAN switch SFP tx/rx optical power ? Thanks in advance!

[mrnobody]

Not Zabbix or SNMP cause this. It's all caused by who did this MIB, so, someone emplyed by the manufactor. Saddly it's normal, MIBs creating a lot of ".0.0", indexing, organization problems.
One stable solution is what @zbxusr2025 did, different templates to adapt different MIB/OID seaches.
Other solution, more clean, is upgrade equipament firmware and cross fingers, maybe manufactor changed this, but probably not.

And cyber why you hate SNMP? I love it without SNMP, monitoring never would be so Simple
Recomend read "Zabbix enterprise network monitoring made easy" book, it's old, done in zabbix 3 version, but explain all this things! Understand why it was created to Management (CRUD access) and now is used only to Monitoring (read access).

[cyber]

Not Zabbix or SNMP cause this. It's all caused by who did this MIB, so, someone emplyed by the manufactor. Saddly it's normal, MIBs creating a lot of ".0.0", indexing, organization problems.
One stable solution is what @zbxusr2025 did, different templates to adapt different MIB/OID seaches.
Other solution, more clean, is upgrade equipament firmware and cross fingers, maybe manufactor changed this, but probably not.

And cyber why you hate SNMP? I love it without SNMP, monitoring never would be so Simple
Recomend read "Zabbix enterprise network monitoring made easy" book, it's old, done in zabbix 3 version, but explain all this things! Understand why it was created to Management (CRUD access) and now is used only to Monitoring (read access).

Oh.. the old thread resurrections...
one of the reasons to hate it is in your own answer..

It's all caused by who did this MIB, so, someone emplyed by the manufactor. Saddly it's normal,....

Everyone making their own MIB-s, in many cases only keeping in mind their own existing tools. And then you are the one trying to adapt stuff to different tool and end up pulling hair and losing more braincells than you can count...
Recent encounters... I would really like to have a chat with the chap, who thought it is a good idea to have all varbinds with exact same OID? You have some 15 of them and they are all the same, what really prevented them to have t least some sequence there? 1-15? Try to extract something from such trap...( I do not enjoy writing such items.. "snmptrap["snmpTrapOID\.0 = (?'o'.*?).\b(?'n'82)\b\s(?&o).(?&n)\.0 = (\d+)\s(?&o).(?&n)\.0 = "\[(.*?)\] (?!Alarm cleared: )(.*)"\s"]" )
Or the "logic" of ... we have sent you a trap that something is broken... but all details are in competely different trap...

Give ... me ... that .. axe ...!!!

[mrnobody]

The old thread never dies! kkk

Give ... me ... that .. axe ...!!! Eugene?!

Be carefull; someone can knock on your door at sunday morning to talk "30 minutes about OIDs and how they changed the world";

[cyber]

mrnobody commented
04-04-2025, 14:46
The old thread never dies! kkk

Give ... me ... that .. axe ...!!! Eugene?!

Be carefull; someone can knock on your door at sunday morning to talk "30 minutes about OIDs and how they changed the world";

"Careful with That Axe, Eugene" ... yea.. that scream is something that comes to mind..
Eventhought, my quote was from somewhere else... translated etc... noone besides fellow countryman would really understand the story....

For those preachers I have a sign... "you choose the direction, dog chooses the speed"...