Configuring HP NNM device import

TrueSight Network Automation can import devices from the HP Network Node Manager (NNM) database. Mapping for the HP Network Node Manager formats  describes which fields are imported from HP NNM.

• • Configuring HP NNM version 7.x
  • Automating import and export
  • Configuring HP NNM version 8.x and 9.x
    

Configuring HP NNM version 7.x

The steps for configuring device import for HP NNM version 7.x are described in this section.

Network Automation supports the import from Oracle, Microsoft SQL Server 2000, and the HP embedded (Solid) database management systems (DBMSs).

Before you begin

If you are using the HP Embedded (Solid) DBMS, a JDBC driver must be copied into place:

1. Copy the JDBC driver, SolidDriver2.0.jar, from the $OV_WWW\htdocs\classes\solid directory to the BCAN_DATA\endorsed\lib directory.
2. Restart the BCA-Networks Web Service as follows:
   
   • (Microsoft Windows) Restart using Windows Services
   • (Linux) /etc/init.d/enatomcat stop | start

To import devices from HP NNM version 7.x

1. Export the HP NNM topology by selecting Tools > Database > Export Topology from the main HP NNM window.
   
   If you want to schedule a recurring export from HP NNM and import to Network Automation, see Automating import and export.
2. Import from the database into Network Automation by doing the following:
   1. Log into Network Automation as sysadmin.
   2. Select Admin > Device Import > Add.
   3. Enter a value the Name field, such as HP NNM Import.
   4. (Optional) Enter a value for the Annotation field.
   5. Select the Enabled option.
   6. Do not select the Auto Purge and Initial Snapshot options.
   7. For the Format field, select HP NNM Network Node Manager database.
   8. Select the appropriate value for the Database Type field.
   9. If Network Automation and HP NNM are co-located on the same server, leave the Location field set to its default value. Otherwise, modify localhost to reflect the host name of the computer running HP NNM.
   10. Enter the User Name and Password to an account that has access to the database. If you need to create an account for Network Automation to use, execute the following on the command line of the computer hosting HP NNM:
       
       C:\> ovdwquery
       create user user name identified by password;
       quit;
       C:\>
   11. Ensure that the Repeat Type field is set to Import Once.
   12. Ensure that the Import Time field is set to Now.
   13. Click Save.
   14. Check the Execution Status in the Device Import Task list. You can refresh this screen to see updates. If you click the Successful link, a list of imported devices is displayed.

Automating import and export

You can keep Network Automation and HP NNM synchronized by automating the export/import from HP NNM to Network Automation:

1. Set up a scheduled job (that is, cron on Linux) on the HP NNM server that executes the ovdwtopo --export command on a regular basis.
2. Schedule an import job in Network Automation (Admin > Device Import) to run on a regular basis just after the scheduled export from HP NNM.

Configuring HP NNM version 8.x and 9.x

The steps for configuring device import for HP NNM version 8.x and 9.x  are described in this section.

Before you begin

• Determine whether the HP NNM server database is embedded or not. If it is embedded, the server runs various PostgreSQL processes. If it is not embedded, the database is running on an Oracle server.
• To import devices from a non-embedded database, you need to know the server host name or IP address, and the database user name and password. The name of the database is nnm. No additional configuration is necessary.
• To import devices from an embedded PostgreSQL database, you must configure the HP NNM server system to allow a remote client system (that is, Network Automation) to connect to the embedded database.

To import devices from HP NNM version 8.x or 9.x

1. As root or administrator, edit the postgresql.conf file in the OV/shared/nnm/databases directory. Add a new line to the end:
   
   listen_addresses='*'
2. Edit the pg_hba.conf file in the same directory. Add a new line to the end:
   
   host nnm postgres 1.2.3.0/24 trust
3. Replace 1.2.3.0/24 with the IP address/netmask of the Network Automation application server.
4. Stop and start HP NNM.