NNMi Configuration Issues

This section includes common issues with NNMi configuration and the steps to resolve these Issues.

Incorrect Display of the SNMP Data and MIB Strings

NNMi displays garbled strings from some SNMP traps and other octet string data, such as sysDescription and sysContact, if an incorrect character set if configured in the nms-jboss.properties file.

To resolve this problem, do the following:

1. Edit the following file:

   • Windows:%NNM_PROPS%\nms-jboss.properties
   • Linux:$NNM_PROPS/nms-jboss.properties

2. Remove the comment (#! characters) from the line that begins as follows:

   #!com.hp.nnm.sourceEncoding=

3. Set the com.hp.nnm.sourceEncoding JVM property to a comma-separated list of source encodings that your environment currently supports using the examples shown in the nms-jboss.properties file. These examples show combinations of the Shift_JIS, EUC_JP, UTF-8, and ISO-8859-1 character sets.
4. Save your changes.

5. Restart the NNMi management server:

   Run the ovstop command on the NNMi management server

   Run the ovstart command on the NNMi management server

6. To test your changes, resend the suspect trap to NNMi and make sure the garbled display problem no longer occurs.

   If the garbled text involves binary data or data that cannot be interpreted for any reason, do the following to configure NNMi to display the strings in hexadecimal format:

   1. Open the following file:

      Windows: %NNMDATADIR%\shared\nnm\conf\nnmvbnosrcenc.conf

      Linux: $NNMDATADIR/shared/nnm/conf/nnmvbnosrcenc.conf

   2. Add the trap OID - varbind OID value combinations that NNMi displays in a garbled format. Also add the combinations from any varbind values you do not want NNMi to decode, such as binary data. Use the examples shown in the nnmvbnosrcenc.conf file as templates to configure your combinations. This tells NNMi to display the Custom Incident Attribute values in the Incident form using a hexadecimal value.
   3. Save your changes.

   4. Restart the NNMi management server:

      Run the ovstop command on the NNMi management server.

      Run the ovstart command on the NNMi management server.

   5. Test your changes to make sure these changes result in a hexadecimal display of the formerly garbled strings.

ESXi Servers Appear as Devices with no SNMP on NNMi Maps

To address this, make sure that the SNMPM agent is installed and enabled on the ESXi server..

Problem with the Node Group Map

A node group map may show an error message when your NNMi environment includes the following:

• An Oracle database.
• A top-level NNMi node group with multiple child node groups
• A child node groups contain 1000 or more members

To address this, do one of the following:

• Limit the child node groups to less than 1000 members
• Do not select Nodes to Node Groups or Node Groups to Node Groups in the Node Group Map Settings->Connectivity->Node Group Connectivity section for these node groups.

Accidental Removal of the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files Library

If you accidentally removed the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files library, and need to enable NNMi to use the AES-192, AES-256, and TripleDES privacy protocols for SNMPv3 communication, follow these steps:

1. Download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files library from the Oracle Technology Network web site for Java developers.

2. Uncompress the download package, and then copy both JAR files (local_policy.jar and US_export_policy.jar) to the following location:

   • Windows: %NnmInstallDir%\nonOV\jdk\nnm\jre\lib\security
   • Linux: $NnmInstallDir/nonOV/jdk/nnm/jre/lib/security

3. Restart the NNMi management server:

   1. Run the ovstop command on the NNMi management server.
   2. Run the ovstart command on the NNMi management server.