Showing results for 
Search instead for 
Did you mean: 

Import MIB Files

Go to solution
Occasional Contributor

Import MIB Files

Hi Community,


i have got an IMC 5.2 Installation and a brand new HP-2920-24G POE Switch. With the default MIBs it is recognized as "HP Unknown Product" with sysOID "".


However i downloaded the new MIBs from HP (mibs-Feb2013). Inside the hpicfOid.mib i found the right OID for my Switch. The Description says: " The authoritative identifier for the HP
stack of 2920 series switches. The stack can
include devices like
hpSwitchJ9726, hpSwitchJ9727, hpSwitchJ9728,


How can i import this new MIB File into IMC?

Honored Contributor

Re: Import MIB Files

Importing the MIB is not really required if you just want to change it from "Unknown Device"


Go to System -> Resource Management -> Device Model. Click "Add". Fill in the model name. Easiest way to find the sysOID is to query the existing device. Set the Vendor, Series and Category as required. Fill in the description field if you like.


The device will then be updated to show the new model name. That's all you really need to do. You don't HAVE to import any MIBS for regular management. However, if you want to import the MIB to use it for things like the mib browser, or for traps, there's two places to do that:


For trap definitions, copy the MIB to the IMC server, under <imc>/client/TrapMIB. Then go to Alarm -> Trap Management -> Trap Definition. Click "Import trap definition from MIB file" and follow the instructions.

Note that the HP MIBs are already imported, and I would be surprised if there's much in the way of new traps for this specific device.


For use in the MIB Browser, go to System -> Resource Management -> MIB Management. Go Tools -> Load MIB Files. Click the icon that looks like a screwdriver and a crescent. Follow the instructions to load & Compile the MIB.



Occasional Contributor

Re: Import MIB Files

thank you for the answer, with your help i managed to change the device model to HP 2920.


The MIB Managment works fine now, but it would be a lot easier to just import the MIBs with the correct Model names.