How do I manage MIB files and MIB definitions?

To manage MIB definitions

For Entuity to poll attributes, you must load the appropriate MIBs to the Entuity server. Entuity is shipped with  a set of IETF and IANA MIB files in the MIBs directory, which are available for you to load (parse):

• RFC-1212.
• RFC-1215.
• RFC1155-SMI.
• RFC1158-MIB.
• RFC1213-MIB.
• SNMPv2-SMI MIBs.

You can augment these by importing and then loading any additional MIBs that you require.

To manage MIB definitions:

When you have access to the Entuity server, you can directly add your required MIB files to the MIB folder, which by default is entuity_home\lib\mibs. Alternatively, you can manage MIBs through the Manage MIBs window via a device's MIB Browser page, when managing traps or when adding user defined collectors.

The Manage MIBs window gives you the option to:

• import MIB definitions.
• load MIB definitions.
• unload MIB definitions.
• delete MIB definitions.
• export MIB definitions.

Importing MIBs:

• You should only import to the Entuity server those MIBs that you require.
• You should not import multiple versions of the same MIB definition, because this could cause confusion for future troubleshooting of that MIB's behavior.
  • for example, you could import the same MIB through two files that have different file extensions. When you load (parse) those MIB files, the result will be one loaded MIB, but it would not be possible to determine which MIB file it was based on.

Loading MIBs:

After you have imported MIBs to the Entuity server, you must load (parse) them to the server. When you have access to the Entuity server, you can also directly upload MIBs that are parsed on one Entuity server to the loaded MIBs folder of another server. The default folder for loaded MIBs is entuity_home\lib\mibs\parsed.

If through the Event Management System you have created events and rules from a MIB’s trap definitions, then the event project contains the rules, events and incidents to use with the traps. To set up the receiving server with the same configuration as the original server would also require importing the event project from the original server to the new server, and not just the transfer of MIB files.

Unloading MIBs:

Unloading a MIB will delete the parsed MIB from the parsed MIB folder. It does not remove any rules associated with the trap or custom events from the event project, because rules and events may potentially be shared by more than one MIB or trap definition. Instead, when required, you must separately delete custom events and trap processing rules.

Unloading a MIB does not update the event project. However, if you also delete rules and custom events associated with the MIB, this does change the event and would change the saving and deploying of the updated event project.

Deleting MIBS:

Deleting a MIB has the following effects:

• removes the trap definitions from the event project.
• deletes the loaded MIB from the parsed MIB folder.
• deletes the unparsed MIB files from the Entuity server.

It does not remove any rules associated with the trap or custom events from the event project, because rules and events may potentially be shared by more than one MIB or trap definition. Instead, when required, you must separately delete custom events and trap processing rules.

Deleting a MIB does not update the event project. However, if you also delete rules and custom events associated with the MIB, this does change the event and would change the saving and deploying of the updated event project.

Exporting MIBs:

You can export MIB files from the Entuity server e.g. to import them to another Entuity server.

• if you select one MIB, Entuity will export it as a single MIB file with the name of that MIB.
• if you select multiple MIBs, Entuity will export them as one compressed file named mibs.zip.