Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Consolidated Management 2/Network Node Manager i Setup Guide


19.13 Configuring NNMi to enforce strict SNMPv3 inform processing

You can configure NNMi to enforce strict SNMPv3 inform processing. When you have configured this new property, NNMi is able to enforce strict SNMPv3 inform processing. NNMi does not process any SNMPv3 inform with credentials that do not match the credentials configured in Trap Forwarding Configuration. This configuration disregards the authentication or privacy configured for a node in the NNMi Communication Configuration window.

With this new property, NNMi validates SNMPv3 traps differently from how it validates SNMPv3 informs. For SNMP traps, NNMi uses the communication configuration currently being used to monitor a node in topology.

To configure the new property, do the following:

  1. Edit the following file:

    • Windows

      %NNM_DATA_DIR%\shared\nnm\conf\props\nms-communication.properties

    • UNIX

      $NNM_DATA_DIR/shared/nnm/conf/props/nms-communication.properties

  2. Add the following line:

    com.hp.ov.nms.comm.snmp.enforcestrictv3traps=true
  3. Save the file.

  4. Restart the NNMi management server:

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

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

When making file changes under HA, you must make the changes on both nodes in the cluster. For an NNMi that uses an HA configuration, if the change requires you to stop and restart the NNMi management server, you must place the nodes in maintenance mode before running the ovstop and ovstart commands.

If the property you just configured is missing or its value is set to false, NNMi does not apply validation of SNMPv3 informs to the configuration set in Trap Forwarding Configuration (the NNMi behavior before adding this feature). NNMi logs messages related to rejected SNMPv3 informs and traps to the nnm-trace*.log file.