The status of Physical Sensors & Node Components are not getting updated within NNMi when their status values adjust to a 'Warning' or 'Unavailable'

  • Document ID:KM02502091
  • Creation Date:31-Jul-2016
  • Modified Date:31-Aug-2017
    • Micro Focus Products:
      network node manager 9.20
      network node manager i premium
      network node manager i ultimate

Summary

As and when the status of a Physical Sensor or Node Component adjusts to 'Warning' or 'Unavailable', the same is not reflected on the NNMi side. Here, the status of the sensor/component continues to show as 'Normal' even after a Configuration poll / Status poll is performed on the hosting node.

Question

Illustrative scenario : When the ciscoEnvMonSupplyState (OID : .1.3.6.1.4.1.9.9.13.1.5.1.3) for Node Power Supply assumes the value of warning(2) or notPresent(5), on the NNMi (Network Node Manager) side this sensor/component status continues to show as 'Normal'.

By default, the three physical sensor state values (None, Warning, and Unavailable) are mapped up to a Normal status. In a similar fashion, the three node component state values (None, Warning, and Unavailable) are also mapped up to a Normal status by the NNMi Causal Engine (aka APA).

  Physical Sensors : Fan, Power Supply Temperature, Voltage, Backpane
  Node Sensors      : CPU, Memory, Buffers, Disk Space

How can the user override these default state mappings such that None, Warning, and Unavailable are re-mapped to show as 'Critical' ?

Answer

The following steps can be performed to override Physical Sensor & Node Component Status Values -

1. If not already present, create a new properties file with the name nnm-apa.properties in the following directory:

    on Windows: %NnmDataDir%\shared\nnm\conf\props
    on Linux: $NnmDataDir/shared/nnm/conf/props

    Note: When making file changes under High Availability (HA), you need to make the changes on both nodes in the cluster.

2. To override the Physical Sensor Status Values, within the properties file, use a text editor to include one, two, or all three of the following lines, as applicable:

     com.hp.ov.nms.apa.PhysicalSensorValueReMappedToDown_NONE=true
     com.hp.ov.nms.apa.PhysicalSensorValueReMappedToDown_WARNING=true
     com.hp.ov.nms.apa.PhysicalSensorValueReMappedToDown_UNAVAILABLE=true

     Note: Users can opt to map an Unavailable state to an Unpolled status (since Unavailable means that the measurement facility is not available). This situation can often occur because the
             sensor is non-functional as opposed to the component being non-functional. To map Unavailable to Unpolled, use the following text:

     com.hp.ov.nms.apa.PhysicalSensorValueReMappedToUnpolled_UNAVAILABLE=true

3. To override the Node Component Status Values, within the properties file, use a text editor to include one, two, or all three of the following lines, as applicable:

     com.hp.ov.nms.apa.NodeComponentValueReMappedToDown_NONE=true
     com.hp.ov.nms.apa.NodeComponentValueReMappedToDown_WARNING=true
     com.hp.ov.nms.apa.NodeComponentValueReMappedToDown_UNAVAILABLE=true

   Note: Users can opt to map an Unavailable state to an Unpolled status (since Unavailable means that the measurement facility is not available). This situation can often occur because the
            sensor is non-functional as opposed to the component being non-functional. To map Unavailable to Unpolled, use the following text:

     com.hp.ov.nms.apa.NodeComponentValueReMappedToUnpolled_UNAVAILABLE=true

4. Save the properties file.

5. Restart the NNMi management server:

   - Run the ovstop command on the NNMi management server
   - Run the ovstart command on the NNMi management server