NetXMS Support Forum

Hi all,

I have an issue with a number of Brocade MIBs. When I try to import them I get errors like this one:
BROCADE-LLDP-EXT-DOT3-CAPABILITY-MIB: ERROR 001: Import symbol "brocadeAgentCapability" unresolved

Based on that particular MIB, it tries to import that particular symbol from the Brocade REG-MIB:
IMPORTS
    brocadeAgentCapability
        FROM Brocade-REG-MIB

Clearly something is not being imported or referenced right, but I'm no MIB expert and can't tell what's wrong. Contents of the Brocade-REG-MIB below:

Brocade-REG-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY,
    OBJECT-IDENTITY,
    enterprises                     FROM SNMPv2-SMI;

bcsi MODULE-IDENTITY
        LAST-UPDATED        "201202030000Z"
        ORGANIZATION        " Brocade Communications Systems, Inc."
        CONTACT-INFO
                "Brocade Communications Systems, Inc.
                 Postal: 130 Holger Way
                 San Jose, CA 95134
                 U.S.A
                 Tel: +1-408-333-8000
                 E-mail: [email protected]
                 web: www.brocade.com."
        DESCRIPTION
                "This MIB module defines Structure of Management
                Information for the Brocade enterprise and serves as
                central repository of all the OIDs under Brocade
                enterprise OID tree."

        REVISION        "201202030000Z"
        DESCRIPTION
                "Initial version of this MIB module."
        ::= { enterprises 1588 }        -- assigned by IANA

commDev OBJECT-IDENTITY
    STATUS  current
    DESCRIPTION
        "The root OID sub-tree for Communication devices of Brocade."
    ::= { bcsi 2 }

fibrechannel   OBJECT-IDENTITY
    STATUS  current
    DESCRIPTION
        "The root OID sub-tree for Fibre Channel Devices of Brocade."
    ::= { commDev 1 }

nos OBJECT-IDENTITY
    STATUS  current
        DESCRIPTION
                "The root OID sub-tree for Brocade's NOS products."
        ::= { commDev 2 }

fcSwitch OBJECT-IDENTITY
    STATUS  current
    DESCRIPTION
        "The root OID sub-tree for Fibre Channel Switches of Brocade."
    ::= { fibrechannel 1 }

bcsiReg OBJECT-IDENTITY
    STATUS  current
    DESCRIPTION
        "The root OID sub-tree for Brocade Global Registry."
    ::= { bcsi 3 }

bcsiModules OBJECT-IDENTITY
    STATUS  current
    DESCRIPTION
        "The root OID sub-tree for all the Brocade management MIBs."
    ::= { bcsiReg 1 }

brocadeAgentCapability OBJECT-IDENTITY
        STATUS  current
        DESCRIPTION
                "This provides a root object identifier from which
        AGENT-CAPABILITIES values may be assigned."
        ::= { bcsiReg 2 }
END

Any pointers?

Some MIBS have dependencies so Im guessing you will also need to add Brocade-REG-MIB into the mibs folder as well and recompile

Hi,

The Brocade-REG-MIB is already in the folder and doesn't throw any errors by itself.
Hence I posted the contents of the Brocade-REG-MIB, hoping someone might be able to help me work out why that particular MIB doesn't throw errors, but a second MIB that depends on it does - with a reference to an object that is defined in the compiled Brocade-REG-MIB.

I'm at a loss, as that really doesn't make much sense to me.

Cheers

Compiled fine for me.. Try the attached mibs..  Also one thing ive noticed is the mibs wont get picked up if they dont have the .txt extension I doubt that was your issue though

Still not working for me. Wondering if there is something else in my MIBs folder that's messing with the Brocade ones (I have a handful of Brocade ones that don't compile, I just picked the LLDP-EXT one as an example as it was the first that failed).
The MIB files all have .txt file extensions.

I've attached the contents of my mibs folder. Any chance you could try to compile that "as is" at your end? I am curious to see if that will work (in which case something else on my system must be causing the issue) or if the compile will fail (in which case there is "something" in that folder that's breaking it.

ok so i took your mibs folder created a seperate folder inside and moved each troubled mib in untill it compiled without errors so basically for what ever reason these mibs are causeing issues not sure if you need these but BRCD_REG looks like a duplicate...

BRCD_NOS_PRODUCTS.txt  BRCD_REG.txt  FOUNDRY-SN-NOTIFICATION.txt

That was it. BRCD-REG was a different version of the same MIB.
Found another one as well, SW.txt and SW-MIB.txt. Same thing, different versions.

I shall look for duplicates next time I run into one of these.

Thanks!