This section addresses importing device inventory directly from a database using a JDBC SQL driver. The factory-installed JDBC SQL-based import adapters include HP Data Warehouse and BMC Foundation Discovery. You can also develop your own JDBC import adapters. See Creating a user-defined database query format.
(Applicable only for HP Network Node Manager 7.x) Before executing the import task, confirm that the HP topology has been exported to the Data Warehouse. To export topology to the Data Warehouse on a regular basis, see the HP manual titled Reporting and Data Analysis with Network Node Manager, Chapter 6. "Export Utilities." The section titled "Using a Scheduler" describes how to schedule topology exports with the operating system's scheduling facility. Confirm that the Data Warehouse export occurs before the scheduled import task.
To add a JDBC database access device import task
- Navigate to Admin > Network Admin > Device Import. The Device Import Tasks page is displayed.
- Click Add to define a new device import task.
The Add Device Import Task page opens, as shown in the following figure for HP Network Node Manager 8. x Device Import.
On the Details tab, define device import task details through the displayed fields:
Enter a unique name, up to 40 characters, for the import task.
(Optional) Enter a comment or remark about the import task.
(Optional) Select this option to enable the import task. By default the task is enabled.
(Optional) Select this option to purge the import task after its scheduled execution.
(Optional) Select this option if the import task should automatically back up the configuration files of each device during the import.
When an import file contains a large number of new devices (for example, greater than 200 new devices), BMC Software recommends not performing the initial snapshot as part of the import operation. This enables the import to complete in a short duration. You can accomplish the initial snapshot for new devices by adding a job containing a snapshot action (Network > Actions > Jobs ) or by using a scheduled policy.
Specify the device import file format, one of the following:
- BMC Atrium Discovery and Dependency Mapping
- BMC Foundation Discovery
- HP Network Node Manager
In the JDBC Database Access box, define the following settings:
Select the appropriate driver for the import. The BMC Network Automation system is delivered with the Oracle, PostgreSQL, and Microsoft SQL Server JDBC drivers. For instructions on installing Solid JDBC driver see Configuring HP NNM device import.
(Optional) Specify the user name for connecting to the database.
(Optional) Specify the password for connecting to the database.
- In the Matching criteria field, specify how to match the imported device data to devices already in the system's device database. When a device match is found, the existing device record is updated with the imported values. When no match is found, a new device record is added using the imported values.
You can match on either the name or the primary address, which must then appear as a field in the import data. For example, if you import from CSV and match on address, then the CSV file must include an address column and a value in each row.
- Match by Device Name: BMC Network Automation looks for an existing device by the imported name (case-insensitive). Note that device names are unique, so only one device matches.
- Match by Primary Interface Address Exactly: BMC Network Automation searches for an existing device by the imported address, within the device agent associated with the imported device (based on the imported device agent or the default device agent).
Matching by address allows device names to be changed during import (though the resulting name must be unique). If multiple matches result (as addresses need not be unique), then the device is skipped.
- Match by Primary Interface Address Resolved: BMC Network Automation searches for an existing device by variations on the imported address, within the device agent associated with the imported device. BMC Network Automation uses DNS to resolve the supplied address into an IP address, a hostname, and a fully-qualified hostname, and then tries to match an existing device's address to any of these values. If multiple matches result, then the device is skipped.
- In the Repeat field, specify how often to repeat the import task. You can choose between a one-time occurrence (Import Once), or a recurring task (Import Daily, Import Weekly, or Import Monthly ).
In the Import Time box, set the import time. The time setting depends on your selection in the the Repeat field:
Either set the import time to Now or specify a date and time (hour and minute) in the future.
Specify the time (hour and minute) to execute the import task each day.
Specify the time (hour and minute) and day(s) of the week to execute the import task.
Specify the day of the month and import time to execute the import task.
In the Dynamic Menu Field box, select whether to accept or reject unknown menu values for dynamic fields during the import, as detailed in the following table:
|Menu value already exists for the dynamic field
||The Accept/Reject Unknown Values setting is ignored. The device record is imported.
|Menu value does not exist
||Accept Unknown Values is selected
||The new menu value is added to the list of available menu items, and the device record is imported.
|Reject Unknown Values is selected
||Field is required and has no default value
||The device record is not imported.
|Field is required and has a default value
||The device record is imported, and that field is set to the default value.
|Field is not required
||The device record is imported, and that field is set to the default value (if any).
- In the Scope box, configure the following settings:
- Process: Specify which devices to process in the import file.
- All Devices From the Import File: This option processes new and existing (that is, overwrite) devices during the import.
- Process Only New Devices From the Import File: This option only imports devices that are not found in the database.
- Process Only Existing Devices From the Import File: This option only imports devices that are found in the database.
- Overwrite Device Type: Specify for existing devices, if the Device Type (for example, Cisco CatOS Switch) should be overwritten with a new Device Type (for example, Cisco IOS Switch/Router). Configuration files for the old device type are kept in the archive. For example, this feature is helpful when converting Cisco CatOS devices to Cisco IOS devices. You must select this option to overwrite an existing device type.
On the Defaults tab, set device inventory default values (optional) for each imported device.
During the import operation, values for device fields are assigned based on the following precedence order:
- Field is assigned based on the import file
- Field is assigned based on the existing value in the device database record
- Field is assigned the default supplied on the device import task Default Tab
- Field is assigned a default value assigned by the system
- Field is left blank (only if the field is not mandatory)
Based on this precedence, the Defaults in the import task are only used when the field is not assigned in either the import file or the current device database record. Assigning Defaults is only applicable for new devices or unassigned field values on existing devices.
- Click Save to save and schedule the new import task.
After the import tasks completes, you can view the status of the import by selecting the Status tab.
Click view details on the Status tab to display a detailed import status report. This report is also available from the Import list under Execution Status.
Where to go from here
After importing devices for the first time, the following procedures are recommended:
- For those fields not imported, use the device Mass Edit feature to assign fields common to a set of devices (for example username, password, privilege password, access type) or edit each device individually.
- If you did not select Initial Snapshot on the Import tasks, perform a manual snapshot operation to retrieve the current configuration files.