Technical bulletin

Managing PATROL Agent disconnect event severities

You can manage the severities of self-monitoring events received from the PATROL Agent disconnect events starting from the TrueSight Infrastructure Management Server 10.5 version. Use the following sections to understand the procedures for managing these events.

Configuring PATROL Agent disconnect events with Critical severity

By default, the PATROL Agent disconnect events severity property is set to OK. To configure the severity to Critical status, perform the following steps:

1. From the TrueSight Infrastructure Management server deployment folder, navigate to pw/custom/conf/ and open the pronet.conf file.
2. Edit the pronet.selfmonitoring.pa_disconnect_severity property and reset value from OK to CRITICAL.
3. Restart the TrueSight Infrastructure Management server.
   Wait for the server to restarted.
4. Verify the newly generated events are coming in with Critical severity.

Adding a rule to generate PATROL Agent disconnect Critical severity events

The PATROL Agent disconnect events come in with OK status by default, and do not change to Critical status even after 5 minutes. To resolve this, update the ppm_sm_ev_rules.mrl rule file, which adds a new timer rule for changing the status of these events to CRITICAL, if the Event is still open after 5 minutes. All PATROL Agent disconnect events are closed through normal behavior once the PATROL Agent reconnects.

1. Back up the existing ppm_sm_ev_rules.mrl rules file from the pw\server\etc\<cellname>\kb\rules\ folder.
2. Download the new ppm_sm_ev_rules.mrl file to any local folder.
3. Copy the new ppm_sm_ev_rules.mrl under the pw\server\etc\<cellname>\kb\rules\ folder.
4. Re-compile the cell by running the mccomp –n <cellname> command.
5. After successful compilation, start the cell by running the pw p r mcell command.