Import MIBs

The Discovery Import MIBs Screen is used to import new or updated MIB files into OmniVista. All MIB files are imported to the OmniVista Server. Before you import MIBs, it is important to understand that the purpose of this function is to import MIB files that reside somewhere on your local file system into OmniVista. A mibs.txt ASCII file lists the order in which the MIBs will be compiled. Also:

• All MIB files that you import must have a file extension of .mib.
• If you create a new MIB directory for a new device, note that you must import a complete set of MIBs into that directory. This means that if any proprietary MIBs you are using have imports of standard MIBs, the standard MIBs must be included and imported into that directory as well.
• For the MIBs to compile correctly, you are strongly advised to order them so that all the referenced MIB files are compiled before the files that reference them. MIB compilers follow import references from one MIB to another on the fly, and do not strictly require that the MIBs be compiled in any particular order. For this to work successfully, however, the MIB filenames must match the import statements exactly, and unfortunately this is almost never the case. To avoid these problems, as stated above, order the MIB files so that all the referenced MIB files are compiled before the files that reference them. You can specify the order in which the MIB files will be compiled by selecting files and using the Up and Down arrows in the Import Files to Mibset Screen, as described in the procedure below. MIB files will be compiled in the order that the files are listed in the Import Files to Mibset Screen.
• It is not advisable to add new MIB files to a MIB directory supplied by default with OmniVista. It is preferable to create a separate new directory for each new third-party device you want to support. This will ensure proper operation of the OmniVista MIB Browser. If you add a new MIB file to an existing MIB directory, you will need to re-import the existing MIB files in order for them all to display in the OmniVista MIB Browser.
• Once you have completed the MIB importation process, OmniVista does not immediately parse the MIBs. When you discover a device with an OID that is specified for the MIB directory into which you imported the new MIBs, OmniVista will poll the device for standard MIB-II objects. If the standard MIB-II MIBs are not included in the directory, error messages will be written to file server.txt (which can be viewed from the Audit application). Any proprietary MIBs that you imported into the directory will not be parsed until you load the MIB Browser for a device with an OID that is specified for that directory. However, if you close the OmniVista client and completely stop the OmniVista server after completing the MIB importation process, then start the server, the MIBs will be parsed when the server starts.

Importing MIBs

Follow the steps below to import MIB files into OmniVista.

1. Select the Mibset to be updated from the drop-down box at the top of the screen (e.g., Cisco). If you entered a new directory name in the Third-Party Device Support Screen, the name will be displayed in the drop-down menu.

2. Click on the Import button, then click on the Upload Files button.

3. Browse to the folder containing the MIBs you want to import, select all of the files and click Open. The files will appear in the imported into the Import Files to Mibset Screen.

Note: If you are using Chrome, you will have the option of selecting an Upload Folder button in Step 2. Select the folder containing the MIB Files to import all of the files in the folder. This option is not supported in Firefox or Internet Explorer.

4. The MIB files will be loaded into OmniVista in the correct order. However, you can adjust this order by selecting individual files and clicking the Up and Down arrows in the upper-right corner of the screen.

5. Click the Apply button. The MIB files are imported to the OmniVista Server.