Run File-based Import

In many IT environments, device and host configuration information is maintained in a configuration management database (CMDB). If you have this data, you might prefer to import your device information and SNMP authentication profiles through file-based import. With this method, you import an XML file that contains your device and profile data. Scanning the IT environment is not necessary.
uim901
In many IT environments, device and host configuration information is maintained in a configuration management database (CMDB). If you have this data, you might prefer to import your device information and SNMP authentication profiles through file-based import. With this method, you import an XML file that contains your device and profile data. Scanning the IT environment is not necessary.
This method offers several benefits:
  • Speed. Automated discovery can take several hours or longer in an enterprise deployment. An XML file can be imported in minutes.
  • More control over your inventory. File-based import helps to ensure that your inventory includes all the devices you want to monitor, and no others. Automated discovery could add devices that you are not interested in (such as printers or personal computers) or fail to include devices that are temporarily non-responsive.
  • Fewer security alerts.
The
cm_data_import
probe imports device and SNMP authentication data. If automated discovery finds a system automated discovery that is also included in file-based import, the information from file-based import takes precedence for most properties. However, precedence depends on device reconciliation rules and heuristics. Device reconciliation is the process of aggregating data from multiple views of the same device and resolving the data into a single device view.
Note:
The XML schema was updated for cm_data_import version 7.6 to support the import of SNMP authentication profiles. While the probe imports XML files using the old schema, we recommend that you migrate to the new schema. 
You can launch file-based import by navigating to the file in USM or by placing the file in a directory where cm_data_import can find it.
Method 1: Navigate to the XML File
  1. Prepare the XML file. See XML File Schema for details.
  2. In the USM navigation tree, expand the
    Discovery
    node.
  3. Hover over the
    External
    node and click the import icon ( USM--FileBasedImport_ICO ), or click the
    External
    node and click
    Actions > Discovery Import
    .
  4. Navigate to the XML file and click
    OK
    . Cm_data_import publishes the data to the message bus, and discovery_server imports it.
Method 2: Automatic file import
The cm_data_import probe monitors a directory for valid XML files. When it finds one, it automatically imports the information into the database. Here is how the process works:
  1. Copy the prepared XML file to
    <UIM_install_directory>
    \probes\service\cm_data_import\import on the system that hosts the cm_data_import probe (typically the primary hub).
  2. Cm_data_import scans the import directory at regular intervals (default is 60 seconds).
  3. When the probe finds the XML file you copied to the directory, it publishes the data to the discovery_server.
The result of both methods:
  • The XML file is placed in a time-stamped subfolder in
    <UIM_install_directory>
    \probes\service\cm_data_import\
    processed
    .
  • The activity of the process is logged.
  • The probe publishes the imported information to the discovery_server.
  • Processing by discovery_server can take several minutes or more to finish. Once complete, the NIS database stores any devices and authentication profiles.
  • Imported devices are listed in the
    Inventory
    node in USM.
  • Authentication profiles are viewable in the Discovery Wizard in USM.
  • When importing has completed, you can deploy and configure probes to monitor the imported devices.