19.9 Configuring NNMi to authenticate SNMPv3 traps for nodes not being monitored

NNMi often receives SNMPv3 traps from devices it is not managing. You can configure NNMi so that it adds SNMPv3 engineIDs for these devices into the SNMPv3 cache.

By configuring NNMi in this way, NNMi can authenticate and store these SNMPv3 traps.

Do the following to configure NNMi to receive and store these SNMPv3 traps:

1. Navigate to Configuration > Communication Configuration in the NNMi console.

   Configure communication settings so that each inbound trap will have a corresponding configuration to use. For details, see Configure Default SNMPv3 Settings in NNMi Help.

   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. Navigate to Configuration > Incidents > Incident Configuration in the NNMi console.

   Clear Discard Unresolved SNMP Traps and Syslog Messages.

   After you clear Discard Unresolved SNMP Traps and Syslog Messages, NNMi retains traps sent from nodes that it is not managing.

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

4. Edit the following file:

   • Windows: %NNM_PROPS%\nms-communication.properties

   • UNIX: $NNM_PROPS/nms-communication.properties

5. Add the following line at the end of the file:

   com.hp.nnm.snmp.engineid.file=path-to-filefile.txt

   The path-to-filefile.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 NNMi processes.

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

   On Windows NNMi management servers, use forward slashes for separators. For example, specify a file such as C:/temp/file.txt

6. Save your changes.

7. Edit the path-to-filefile.txt file.

8. For each device, add its IP address, port, and engine ID, using the comma as the separator between the items. Add the entry for each device on a separate line.

   An engine ID is a series of hexadecimal bytes. NNMi ignores the character case but does recognize 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

9. Run the ovstart command on the NNMi management server to start NNMi and read in the path-to-filefile.txt file.

10. Check the Boot.log file to verify that NNMi has read the file.

    The file prepared in step 8 will contain log messages similar to the following if the file was read correctly:

    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 in mapping the node to a valid configuration, you will 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 such as this, you will have to adjust the Configuration > Communication Configuration settings for that node.

    If you need to remove an entry from the cache as well as from the path-to-filefile.txt file, it is best to make the change to the path to filefile.txt to remove the entry, then restart NNMi:

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

    b. Run the ovstart command on the NNMi management server.

To Page Top