No MIB variable name available after compiling an registering Dell 10892 mib

[T. Hatlø]

I've downloaded, registered and compiled a couple of Dell MIBS.When I try to register a new system type and select the actual mib under the "Mib Definition File Name" the drop down list "MIB variable name" is emty. I've tried the same with tje last three versions of the Dell provided mibs.

[ramesh_naik_]

Hi Terje,

These must help you a lot!!!

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=994918

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=993940


Hope it works!!!!

Regards,
rmn

[T. Hatlø]

I've read the info in the other threads without any result. The person who got around the problem had "hacked" the datbase. The must be some other way to resolve this problem.

I've downloaded several versions of the Dell mibs, compiled (mcompile), registered (mxmib -a) and unregistered them (mxmib -d). Each time I have used different names like FromDell10892, org10892 etc..

The dcstorag.mib is fine but the 10892.mib doesn't work (no information in the "Mib variable name" drop-down list).

[T. Hatlø]

I have now recompiled the original dell10892.mib that was a part of the SIM 5.0 installation. Now this one don't work either..... There must be some remaining rubbish in the SIM database that creates this trouble. Can someone tell me how to clean up the database in a way that gives me the opportunity to manage Dell servers from SIM? I hope I don't have to use the Dell tool to manage HP servers...... We have decided to use SIM as our primary tool!

[Don Bitters]

I had the same problem. It happens when an error occurs when removing or updating mibs. For example, if two of the same dell mib is registered but with different names or versions, then the database gets confused and craps out. frakly I don't think the database is a very solid one, or one with any type of automatic recovery.

I had to uninstall SIM and scrap the database and start over to fix that problem because I coucldn't seem to "hack" the database.
But next time, only register one mib at a time, and make sure it doesn't already exist with the same or different name in the database. And always remove the old mib before compiling and registering a new one. Don't just delete the mib out of the folder, use the mxmib -d command.

Maybe HP will finally fix this problem in the near future since its quite common and causes a big problem.

[JTC]

Hi

I had this exact same issue, i looked into the SQL tables and after deleting the old 10892 mib and importing the new one the "mibfiles" table renames this new_dell_10892.mib.

Delete the old mib with mxmib-a , rename the 10892.mib to new_dell_10892.mib import using mcompile new_dell_10892.cfg , then mxmib-a new_dell_10892.cfg

Tested all ok

[T. Hatlø]

Thank you for your reply. Some months ago I reinstalled SIM to solve this problem. Since then I have heard that SIM does not handle all Dell traps properly. I hope SIM 5.1 will be better in this way.

[Wilbert Chin]

Here's a bit of extra help on this subject.

Essentially this problem is caused by an old MIB conflicting with the new MIB.

a) To see this conflict in the database, go to SQL Server.(We use SQL Server as the database so I'll use that in this example.) Run the following query and look for duplicates in the "module" field.

select * from mibFiles, mibFilesEx where mibFiles.Mib_File_Id = mibFilesEx.Mib_File_Id order by Module

b) On the SIM server, run mxmib -d xxx.mib to remove all of the conflicting MIBs including the MIBs you're trying to install.

c) On the SIM server, run mxmib -a xxx.cfg to reinstall the MIB you want.

d) In SIM, look at "Options/Events/SNMP Trap Settings" for your new MIBs. Hopefully, they now show up correctly.

[Bruce.H]

I met exactly the same problem and finally found the way to workaround.

a) Unregister all dell related mibs. These mibs may include dell10892.mib, dellarymgr.mib, dcstorag.mib, etc

b) Register the 10892.mib, you need rename it to new10892.mib or anyone you want for HP SIM do not accept only numerical characters in mib name.

c) Register other mibs which you unregistered in step a).

This will also fix the problem that only part of traps are recognized by HP SIM.

[Derek_56]

Additional:
HP SIM has (or had when I added my Dell MIBs) an issue with a MIB that does not start with a letter. So the 10892.mib file will not import properly. I worked around this by renaming the MIB before I compiled it and then it imports just fine. Just prepend it with DELL so you have DELL10892.mib.

[OlivierV]

Thank you Bruce.H, it worked also for me.