Ad Widget

Collapse

Brocade SAN IFALIAS

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • RustyP
    Junior Member
    • Mar 2019
    • 7

    #1

    Brocade SAN IFALIAS

    Hi guys!

    We would like to label our brocade switch interfaces so they have meaningful names in alerts/dashboard, but brocade dosent support the IFALIAS OID. Has anyone found any suitable alternative? I would like to avoid manually adding the interface name to items/emails if possible

    Thanks
  • dimir
    Zabbix developer
    • Apr 2011
    • 1080

    #2
    Which would be the source to read the interface names from then?

    Comment

    • RustyP
      Junior Member
      • Mar 2019
      • 7

      #3
      Im not sure what you mean, but with all other network devices we use IF-MIB::ifAlias. In the case of brocade we cant because its not supported, just trying to find a way we can name the brocade interfaces.

      Comment

      • Hamardaban
        Senior Member
        Zabbix Certified SpecialistZabbix Certified Professional
        • May 2019
        • 2713

        #4
        You may store an array of interface names in the macro (eth0:Foo,eth1:Boo) and change the json coming from LLD using JS preprocessing substituting the corresponding values in it....

        Comment

        • RustyP
          Junior Member
          • Mar 2019
          • 7

          #5
          Thats genius!

          Sorry, im pretty new to zabbix so can you explain how to do a macro array? Is it in LLD Macro in the discovery rule? is this also where I do the pre-processing rule?

          Comment

        • zkoro
          Junior Member
          • Oct 2020
          • 5

          #6
          Brocade has command "portname" and you can label your ports in the switch itself.
          Then you can view your port names in FCMGMT-MIB::connUnitPortName tree.

          Comment

          • RustyP
            Junior Member
            • Mar 2019
            • 7

            #7
            zkoro

            The problem with this tree is that it doesnt seem to have the same OIDs as the interface tree, like bits in/out etc.

            Comment

            • zkoro
              Junior Member
              • Oct 2020
              • 5

              #8
              I don't know which version of FOS you are using, but for better understanding read carefully this document - https://docs.broadcom.com/doc/12398210 . It may clear things out.

              Comment

              • dribeirosilva@gmail.com
                Junior Member
                • Oct 2021
                • 2

                #9
                Hello Team, i've a similar situation, is not Brocade equipment, but is very similar. We don't use IfAlias and we want build one.

                Build Discovery
                Execute a Preprocessing using regex for example. (already successfully) and with that Data result build a #Macro that we can use in other Items creation.

                Example Template:
                1. Discovery using SNMP Agent
                2. Return table with WWN: 20 00 01 02 03 04 05 06 / 20 01 01 02 03 04 05 06 / 20 02 01 02 03 04 05 06 / 20 03 01 02 03 04 05 06, .... etc
                3. Execute preprocessing (regex): For example WWN translate for something else "Port 0", "Port 1", ... etc
                4. And with that Data Result build a Macro that can be possible create Items, Graphs,...etc

                I'm Ok with steps 1, 2 and 3 but i'm with Discover Error "Invalid discovery rule value: cannot parse as a valid JSON object: invalid object format, expected opening character '{' or '[' at: 'Port 0'"
                Any ideas or i'm doing something wrong?

                Thanks

                Comment

                Working...