Enabling SNMP trap notifications and in-context application launches for HP NNM 7.x

This topic describes how to enable HP Network Node Manager (NNM) version 7.x to receive SNMP notifications and launch TrueSight Network Automation reports and remediation requests.

To enable SNMP trap notifications and in-context application launches

1. According to your HP NNM server OS:
   • (Linux) Log in as root.
   • (Microsoft Windows) Log in as Administrator.
2. Load the MIB to enable HP NNM to translate OID numbers into names when displaying traps received from Network Automation.
   
   Locate the following MIB files in the BCAN_HOME\public\bca-networks\mib directory:
   • EmprisaNetworksV2C.mib
   • EmprisaNetworksV1.mib
3. Copy either the v1 or v2c MIB file to a temp directory on the HP NNM server.
4. From the temp directory run one of the following commands:
   
   xnmloadmib -load EmprisaNetworksV2C.mib -replace
   
   xnmloadmib -load EmprisaNetworksV1.mib -replace
5. New menu options must be added to display reports and span actions related to selected nodes in a map. You must enter in the registration file that defines the menu options the following parameters:
   
   
   • Network Automation server host name or IP address, and the port it is using for HTTPS requests.
   • Whether or not devices in the HP NNM warehouse will be imported into the Network Automation server.
6. Copy the menu registration file from the BCAN_HOME\public\hpov\registration directory to the NMM server directory.
   
   You can modify the menus in the native user interface and/or the Java-based user interface:
   
   
   • To install the menus into the native user interface, copy the enetaware.txt file to $OV_REGISTRATION.
   • To install the menus into the Java user interface, copy the enetaware.jovw file to $OV_WWW_REG.
7. Edit the copied registration file on the HP NNM server:
   1. Where you see the string %%SERVERNAME%%, replace it with your Network Automation server host name or IP address and the port number (if you are not using the default HTTPS port, 443).
   2. Where you see the string %%NAMEFIELD%%, replace it with either "IP Hostname", "Selection Name" (when importing devices into Network Automation from HP NNM) or "Selection Name", "IP Hostname" (when not importing devices into Network Automation from HP NNM). Be sure to include the quotes as shown.
8. For the Policy Action trap type you can set the category and map severities to HP NNM severities. Copy the enaTrapd.conf file from the BCAN_HOME\public\hpov directory to the HP NNM server.
   
   Edit the file to make these replacements:
   
   
   1. Where you see any of these:
      
      %%POLICY_CATEGORY%%
      %%DISCREPANCY_CATEGORY%%
      %%DISCREPANCY_CLEARED_CATEGORY%%
      %%VIOLATION_CATEGORY%%
      %%VIOLATION_CLEARED_CATEGORY%%
      
      Replace each with one of the following categories:
      
      Error Alarms
      Threshold Alarms
      Status Alarms
      Configuration Alarms
      Application Alert Alarms
      Problem Diagnosis Alarms
   2. Where you see any of these:
      
      %%POLICY_LOW_SEVERITY%%
      %%POLICY_MEDIUM_SEVERITY%%
      %%POLICY_HIGH_SEVERITY%%
      %%DISCREPANCY_SEVERITY%%
      %%DISCREPANCY_CLEARED_SEVERITY%%
      %%VIOLATION_SEVERITY%%
      %%VIOLATION_CLEARED_SEVERITY%%
      
      Replace each with one of the following severity levels:
      
      Critical
      Major
      Minor
      Warning
      Normal
9. Run this command:
   
   xnmevents -replace enaTrapd.conf