Configuring NNMi to Authenticate SNMPv3 Traps for Nodes that are either Managed using SNMPv2 or SNMPv1 or that are not Discovered

Follow the steps in this section if NNMi is receiving SNMPv3 traps from nodes that meet either of the following criteria:

• The device is managed using SNMPv2 or SNMPv1
• The device is not discovered by NNMi

You can configure NNMi to add SNMPv3 Engine-IDs for these devices into the SNMPv3 cache. By configuring NNMi this way, NNMi can authenticate and store these SNMPv3 traps.

To configure NNMi to receive and store SNMPv3 traps for nodes that are managed using SNMPv2 or SNMPv1 or that are not discovered:

1. In the NNMiconsole, navigate to Configuration > Communication Settings. Configure entries at default, Regions or Specific Node Settings level such that each inbound trap will have a corresponding configuration to use to authenticate the trap. See "Configure Default SNMPv3 Settings" in the NNMi help for more information.

   Tip It is a good practice to use a region with included address ranges for your SNMPv3 nodes or configure a Specific Node Setting for each.

2. In the NNMi console, navigate to Configuration > Incidents > Incident Configuration.

3. Deselect Discard Unresolved SNMP Traps and Syslog Messages.

   After you deselect Discard Unresolved SNMP Traps and Syslog Messages, NNMi retains traps sent from nodes that it has not discovered.

4. Run the ovstop command on the NNMi management server.

5. Edit the following file:

   Windows:%NNM_PROPS%\nms-communication.properties

   Linux: $NNM_PROPS/nms-communication.properties

6. Add the following line to the end of the file:

   com.hp.nnm.snmp.engineid.file=<path to file>file.txt

   The <path to file>file.txt entry is the full path and file name of the file that contains the devices.

   With these configuration changes,NNMi reads the entries from this file into the SNMPv3 cache each time you restart the NNMiprocesses.

   Note On Linux NNMi management server, the file path will be in usual format such as /var/opt/OV/etc.

   On WindowsNNMi management server, disregard the drive and use forward slashes for separators. For example, specify a file such as C:/temp/file.txt as /temp/file.txt.

7. Save your changes.

8. Edit the <path to file>file.txt file:

   1. Add an IP Address for a device, the port, and the engine-ID, separating each item with a comma.

   2. Add one entry for each device each on a separate line.

      An Engine-ID is a series of hex bytes. NNMi ignores the character case, recognizes spaces.

      Use the following examples to create your entries:

      16.1.2.3,161,80 00 00 09 30 00 00 1f e9 a3 33 01

      16.1.2.4,161,80 00 00 11 03 00 00 2d 51 99 30 00

      1050:0000:0000:0000:0005:0600:300c:326b, 161, 800000090300001f9ea33000

      ff06::c3,161,80 00 00 09 03 00 00 1f 9A A3 30 00

1. Run the ovstart command on the NNMi management server to start NNMiand read in the <path to file>file.txt file.

2. Review the Boot.log file to verify that NNMi read the file.

   The file should contain log messages to indicate that the file was read, and should look similar to the following text:

   2012-10-17 14:44:44.876 INFO  [NnmTrapService] Start: Populate engineIDs from file

   2012-10-17 14:45:08.017 INFO  [SnmpV3EngineIdCachePopulator] Successfully loaded 3 V3

    Engine IDs from file /temp/patch2/v3hosts.txt

   If there was a failure mapping the node to a valid configuration, you should see a message similar to the following:

   2012-10-17 14:45:03.485 WARNING [SnmpV3EngineIdCachePopulator] V3 

   Engine IDs: Could not resolve SNMPv3 configuration for 16.1.2.6

   If you see a message similar to the previous one, adjust the Configuration > Communication Configuration settings for this node.