Exporting MIB data

How to export SNMP MIB data from MIB Manager to a variety of formats.

Procedure

To export MIB data:

  1. Click MIB export icon Export or, from the menu, click File > Export.
  2. In the Directory field, specify the destination directory for the exported files.
  3. In the File Type field, specify a file type for the exported files.

    You must use the Netcool Knowledge Library (NCKL) whenever possible, because the NCKL rules files are based on the functionality of the device. When using NCKL, you must specify the Netcool Knowledge Library version 3.x file type. This enables the generated files to be added to the existing Netcool Include Library installations.

    The following options are available from the File Type drop-down list:

    File type Description
    CSV Select this option to specify that all the object data is loaded into CSV files, so that it can be viewed using a spreadsheet application.
    CSV Trap Objects Select this option to specify that all trap data and associated variable bindings object data is loaded into a single CSV file, so that it can be viewed using a spreadsheet application.
    HTML with frames Select this option to create a web page that is suitable for publishing.

    The selected MIB tree view is displayed on the left side of the generated web page. You can navigate through the MIB tree view by expanding and collapsing nodes within the MIB tree. When an element is selected from the MIB tree, its associated information is displayed on the right side of the web page.

    This format can often create a large number of export files, each containing a HTML file for each object listed in the MIB tree. The target directory can be zipped up and located under any web server, or the pages can be viewed directly from a disk by opening the index.html file created in the export directory.

    If you want to use individual HTML files with a web browser, export to HTML with frames and then use the files in the data sub-directory located under the export directory.

    HTML without frames Select this option to create a single file named oids.html. This file will contain a list of all objects selected for output, each separated by horizontal rules (using the <HR> tag). Each OID is enclosed by an anchor tag so that when it is loaded, the browser automatically scrolls down to any OID that includes a hash symbol (#) in the URL, for example: file:c:/oids.html#1.3.6.1.4.1.9.

    This file can become very large if you are exporting a large number of objects. Therefore, this format should only used for exporting a small number of traps.

    Netcool Lookup Table Select this option to output all specified values in a tabbed list, with the OIDs displayed in the left column and the object names displayed in the right column. This is suitable for inclusion into any rules file.
    Netcool Include Library Select this option to create separate include files for each enterprise, and to generate a single file for the generic traps (that is, for any traps that are not located below the enterprise sub-tree). It is assumed that the include files are inserted into existing snmp.rules files, either those previously created by MIB Manager or those created by the Netcool Include Library (NCIL).
    Netcool Knowledge Library version 1.1 Select this option to output files from MIB Manager. The files will be included in an existing Netcool Knowledge Library implementation.
    Netcool Knowledge Library version 3.x Select this option to output files from MIB Manager. The files will be included in an existing Netcool Knowledge Library implementation.
    Standalone Rules Select this option to create a single rules file that contains all the selected traps. You can specify this file in the properties file of any Tivoli Netcool/OMNIbus SNMP trap probe.
    Individual Text Files The Individual Text Files format is used for the Netcool Event List right-click menu.

    When you export to individual text files, each OID is output to a separate text file, for example 1.3.6.1.4.1.9.1.1.txt. An external tool can then be added to the right-click menu that uses nco_message to display all object information for an event that has the OID specified in a field, for example: cat 1.3.6.1.4.1.9.1.txt |nco_message stdin title "trap info".

    Tivoli Universal Agent The Tivoli Universal Agent format exports .mdl and trapcnfg files based on the selected content.
    Multiple sub-trees can be selected when this format is selected for exporting files. If multiple sub-trees are selected, .mdl and trapcnfg files are created for all the objects located below a selected item in the MIB tree.
    Note: The first three letters of the application name, following the //APPL tag in the .mdl file, must be unique within an enterprise. MIB Manager tries to adhere to this requirement but it cannot be aware of any other agents that may be running. You may need to modify the .mdl file to ensure that the application name is unique in the enterprise.
  4. In the Scope field, use the drop-down list to specify whether MIB Manager outputs traps only, objects only, or all OIDs.

    The options available depend on the file type that you are exporting.

  5. To limit the number of objects included in the generated file, select the Selected Subtree(s) only checkbox.
  6. Click Export to export the files to the destination directory.