I seem to have no issue compiling new mibs, the issue is that the new mib tree(s) do not show in the mib explorer. I have a management console running on windows logging into a linux server.
After mucking around awhile, I removed all the mibs from the source directory (/usr/share/netxms/mibs) and left only the essential ones I was interested in and recompiled. It seems to complete satisfactorily and there is a brand new netxms.mib file, considerably smaller than the original. That seems correct. However, logging back into the management console and viewing the mib explorer I still see all the original mib trees and the new mibs I added do not show in the tree. I have restarted the linux server and the windows box but to no avail. The mib compile process seems way too easy to screw up but looks like I found a way :). What do I try now?
When you open the Management Console it downloads the netxms.mib file to your system. I noticed it doesn't always replace the version you have on your computer with a new one. However manually deleting the netxms.mib from your system, i.e. the one you run the Management Console on, does trigger a download of the new netxms.mib and you should be good to go. :)
Cheers
After locating and deleting the netxms.mib file from the management console machine, it does indeed download a new file. However, when I view the mib explorer, it appears to be the same as the original. The new compiled file is significantly smaller than the original, so I assume it is different but my new mibs are not in the tree and ones I removed are still there. I'm going back to the compile process to ensure that is working correctly.
Looking at the new netxms.mib file that the management console downloads, I find that it is NOT the same netxms.mib file that I end up with after compiling the mibs. Now to find out where the downloaded file is coming from ....
So if I copy the new compiled mib file by hand from the server to the management console, I get what I expect from the mib explorer. I just haven't found where the other file was coming from.
Sorry, haven't seen that before other. Maybe someone else has?