8.6.2 Interpreting and displaying the MIB data for SNMP traps correctly

NNMi does not always know which character set to use to interpret the MIB data for SNMP traps.

The result is that NNMi displays garbled strings from MIB data (such as sysDescription and sysContact) for SNMP traps.

The solution is use the following procedure to specify the correct character set to be used by NNMi to interpret MIB data strings:

1. Open the file with a text editor:

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

   • Linux: $NNM_PROPS/nms-jboss.properties

2. Locate the following line and delete the comment symbols (#!):

   #!com.hp.nnm.sourceEncoding=

3. Edit the com.hp.nnm.sourceEncoding property.

   Add to the com.hp.nnm.sourceEncoding property the character sets supported in your environment as a comma-separated list, using the examples shown in the nms-jboss.properties file.

4. Save the changes.

5. Execute the following commands to restart NNMi:

   ovstop
   ovstart

If NNMi is to display MIB data in hexadecimal without using a character set, do the following:

1. Open the following file with a text editor:

   • Windows: %NnmDataDir%shared\nnm\conf\nnmvbnosrcenc.conf

   • Linux: $NnmDataDir/shared/nnm/conf/nnmvbnosrcenc.conf

2. Add a combination of traps OID and VarBind OID.

   Add a combination of traps OID and VarBind OID for the target MIB data using the examples shown in the nnmvbnosrcenc.conf file.

   NNMi displays specified MIB data in hexadecimal by using the custom attribute values in the incident form.

3. Save the changes.

4. Execute the following commands to restart NNMi:

   ovstop
   ovstart

To Page Top