21.27.1 Configuring physical sensor status

(1) Propagating physical sensor status to a physical component

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

   • Windows: %NnmDataDir%shared\nnm\conf\props

   • Linux: $NnmDataDir/shared/nnm/conf/props

2. Use a text editor to set the following text in this properties file:

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

   type is the physical sensor. For details, see 21.27 Configuring sensor status.

3. Save the properties file.

4. Restart NNMi by running the following commands:

   ovstop
   ovstart

   Important

   When making file changes under High Availability (HA), you must make the changes on both nodes in the cluster. In the case of NNMi in an HA configurations, if the changes require that you stop and restart the NNMi management server, you must put the nodes in the maintenance mode before running the ovstop and ovstart commands. For details, see 19.6.1 Placing NNMi in maintenance mode.

To Page Top

(2) Configuring physical sensor status to not propagate to the physical component

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

   • Windows: %NnmDataDir%shared\nnm\conf\props

   • Linux: $NnmDataDir/shared/nnm/conf/props

2. Use a text editor to include the following text in this properties file:

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

   type is the physical sensor. For details, see 21.27 Configuring sensor status.

3. Save the properties file.

4. Restart NNMi by running the following commands:

   ovstop
   ovstart

   Important

   When making file changes under High Availability (HA), you must make the changes on both nodes in the cluster. In the case of NNMi in an HA configuration, if the changes require that you stop and restart the NNMi management server, you must put the nodes in the maintenance mode before running the ovstop and ovstart commands. For details, see 19.6.1 Placing NNMi in maintenance mode.

To Page Top

(3) Overriding physical sensor status values

By default, the three sensor status values None, Warning, and Unavailable are mapped to the Normal status by the Causal Engine. You can override these default status mappings so that None, Warning, and Unavailable map to Critical.

To override physical sensor status values:

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

   • Windows: %NnmDataDir%shared\nnm\conf\props

   • Linux: $NnmDataDir/shared/nnm/conf/props

2. Use a text editor to include one, two, or all three of the following lines, as applicable, in this properties file:

   com.hp.ov.nms.apa.PhysSensorValueReMappedToDown_NONE=true
   com.hp.ov.nms.apa.PhysSensorValueReMappedToDown_Warning=true
   com.hp.ov.nms.apa.PhysSensorValueReMappedToDown_Unavailable=true

3. Save the properties file.

4. Restart NNMi by running the following commands:

   ovstop
   ovstart

   Important

   • You can map the Unavailable status to Unpolled status (because Unavailable means that the measurement facility is not available). Often, this situation might occur because the sensor has become nonfunctional, rather than because the component has become nonfunctional. To map Unavailable to Unpolled, use the same procedure as described above, except use the following text in step 2:

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

   • When making file changes under High Availability (HA), you must make the changes on both nodes in the cluster. In the case of NNMi in an HA configuration, if the changes require that you stop and restart the NNMi management server, you must put the nodes in the maintenance mode before running the ovstop and ovstart commands. For details, see 19.6.1 Placing NNMi in maintenance mode.

To Page Top