This topic contains information about the integration between TrueSight Network Automation and HP Network Node Manager (HP NNM).
Key points of integration
This section provides information for configuring the key integration points between Network Automation and HP NNM.
Device import/discovery
Network Automation can connect to the HP NNM database on a routine basis (for example, daily) and import newly discovered devices. The import can also trigger a configuration snapshot for new devices.
Send policy-based notifications
Network Automation sends policy-based SNMP notifications to the HP NNM Alarms Browser or SNMP Traps viewer to report change drift and compliance violations. This enables network operations personnel to identify potential service impacting changes and begin immediate remediation.
Launching in-context reports and remediation requests
From HP NNM 7.x, authenticated users can launch in-context change reports (for example, Change Summary Report, Compliance Summary Report) to investigate policy notifications.
Authorized HP NNM users can also remediate change drift and compliance violations by launching remediation requests.
Environment variables
The following table specifies the default environment variables used for installation directories.
Environment variables | Installation directories |
|---|---|
$OV_SNMP_MIBS | HP NNM-install-dir\snmp_mibs |
$OV_CONTRIB | HP NNM-install-dir\contrib |
$OV_SYMBOLS | HP NNM-install-dir\symbols |
$OV_BITMAPS | HP NNM-install-dir\bitmaps |
$OV_WWW | HP NNM-install-dir\www |
$OV_CONF | HP NNM-install-dir\conf |
$OV_REGISTRATION | HP NNM-install-dir\registration |
$OV_WWW_REG | HP NNM-install-dir\www\registration |
Note
Although most of the examples in this section will use Microsoft Windows directory notation that uses a backslash ( \ ), be sure to use a forward slash ( / ) when installing on Linux systems.
