Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

This section reviews the general rules associated with all import tasks.

  1. If more than one device in an import file has the same name, only the first one is imported. An error is logged to the Event Log for the devices with the duplicate name.

    On the other hand, duplicate addresses are allowed if the Matching Criteria is either Match By Primary Interface Address Exactly or Match By Primary Interface Address Resolved and the device agents are different.

    In addition, for the same device agents and device addresses, if the device names are different, then the existing device record is updated with new device name instead of creating a new device record.
  2. If one device is in two different import files with the same name, both entries are processed and the device modified/added in order that the entries were read from the import files.
  3. The BMC Network Automation system runs imports concurrently when their scheduled execution times overlap.
  4. The device database can be re-imported. The BMC Network Automation system merges changes as follows:
    • The Scope import option allows for selective import (for example, process all devices, process only existing devices or process only new devices). The default is to process all devices.
    • New devices are added to the database and an initial configuration snapshot is performed. You can clear the Initial Snapshot option to skip the snapshot during the import. If you have selected the Overwrite Device Type option and the device import task results in change in device type, snapshot is performed even if you have not selected the Initial Snapshot option.
    • Modifications to an existing device are merged, with the data coming from the import file taking precedence. No snapshot is performed as part of the modification. You must explicitly select the Overwrite Device Type import option to overwrite an existing device type field. This option, for example, is helpful when upgrading devices from Cisco CatOS to Cisco IOS. If a device type is overwritten, the BMC Network Automation system does maintain the old configuration files for the prior device type. If you have not selected this option and the imported device type is different, the BMC Network Automation system ignores the change. If you have selected this option and the device import task results in change in device type, snapshot is performed even if you have not selected the Initial Snapshot option.
  5. During device import, BMC Network Automation performs auto-grouping on device parameters in the same manner as it does when a user manually defines those same parameters.
  6. The status of an import task can be reviewed on the Status tab.
  7. During an import, field value errors are handled gracefully:
    • If an imported field value exceeds the maximum length, the value is trimmed to the maximum length and an appropriate event is logged.
    • Invalid fixed field values (for example, access type, device type) are set to their default value and an appropriate event is logged.
    • Invalid values for menu-based dynamic fields are processed per the Dynamic Menu Fields setting.
    • If a field is not in the system database (for example, dynamic field), then that field is ignored during the import operation and an appropriate event is logged.
  8. On platforms that are localized in languages other than English, CSV files must also be localized to the same language. (For example, you cannot import an English-language file on a Chinese operating system.)

Database import tasks can be scheduled to occur immediately, once at a specific future date or time or on a recurring daily, weekly, or monthly schedule. The Device Import Task list shows active import tasks. When Auto Purge is selected on the Import Task, non-recurring import tasks are purged the following midnight after execution.