Viewing the health of the BMC ProactiveNet components

BMC ProactiveNet displays the health of the following components in the ProactiveNet Health node of the BMC ProactiveNet Operations Console:

• BMC ProactiveNet Cell
• BMC ProactiveNet Integration Service
• BMC PATROL Agent
• BMC ProactiveNet Central Server and Child Server (in case of a multiple server deployment)

In the navigation tree of the Operations Console, click Global > Event Collectors to view the ProactiveNet Health node. The following figure shows the ProactiveNet Health node as it appears in the Operations Console.

BMC ProactiveNet generates an event and displays it in the ProactiveNet Health node if one or all of the scenarios mentioned below occur:

• The BMC PATROL Agent crashes and is disconnected from the Integration Service.
• A KM that is configured to collect data cannot do so because of extraneous reasons such as a time mismatch or clock askew. See Reasons that a KM cannot collect data for more information.

• The connection between the Integration Service and the local or remote cell is lost.
  When the cell is disconnected from the Integration Service, an event is generated as shown in the following figure:
  
  
  When the cell is reconnected to the Integration Service, the event is closed and is displayed in Global > Event Collectors > ProactiveNet Health > By Status > Closed as shown in the following figure:
  
  
  

• The connection between the Integration Service and the BMC PATROL Agent is lost.
• The Integration Service rejects the connection from an incompatible version of the BMC PATROL Agent (for example, BMC PATROL Agent version 9.0 and earlier). For information about compatible versions of the BMC PATROL Agent, see the SPAC tool.
• The Central Server loses connection with a Child Server (in case of a multiple server deployment).
• A Child Server loses connection with the Central Server (in case of a multiple server deployment).
• The connection between the BMC ProactiveNet Server and the Integration Service is lost. This may happen if the Integration Service crashes, or the computer in which the Integration Service is installed crashes, or the network connection between the BMC ProactiveNet Server and the Integration Service is lost.

You can configure the severity for these events by performing the following steps:

1. Open the installationDirectory/pw/custom/conf/pronet.conf file. 
2. Add the following parameters for respective components and set the value to one of CRITICAL, MAJOR, or WARNING.
   
   • Integration Service disconnecting from Server: pronet.selfmonitoring.is_disconnect_severity
   • PATROL AGENT disconnecting from Server: pronet.selfmonitoring.pa_disconnect_severity
   • Cell associated to Integration Service disconnecting from Server: pronet.selfmonitoring.cell_disconnect_severity
     
     For example, pronet.selfmonitoring.is_disconnect_severity=CRITICAL   
3. Save and close the pronet.conf file.
4. Restart the BMC ProactiveNet Server.

The Details notebook displays detailed information about the system for which the event was generated. Such events as classified as self monitoring events and are displayed as such in the Summary notebook as shown in the following figure.

For information about the information that you can view and obtain from the Details notebook, see Viewing the event Details Notebook.

For a use case in the context of which viewing self monitored events is useful and what you can do with such events, see Detect problems using the automated self health monitoring capability.

Reasons that a KM cannot collect data

The following points outline some of the main reason that a KM cannot collect data hence for data gaps to emerge:

1. Data is not collected by a KM because the monitored resource is not available.

2. Data is not collected by a KM due to undefined behavior by some of the underlying APIs or external executables and data gaps are seen for a single or a set of parameters.

3. Data is collected by the KM but gaps are seen on the server when the Patrol Agent reconnects after the stats data retention period because the data points are discarded from the cache on the Patrol Agent after the stats retention period.

Related topics

Features of the BMC ProactiveNet and BMC PATROL Agent integration

Detect problems using the automated self health monitoring capability