Netcool Process Agent Monitor Solution
This is the first of many planned technical blog posts. The solution summarised below was developed in-house by Eirteic Africa for the purposes of a demonstration at our annual Netcool Day, but this solution is also available as a customised solution to our customers. Please contact us for more information.
In the ideal production environment vital components should be monitored by the Netcool Process Agent Daemon. You do not want your employees to stop and start processes under PA that will impact your production environment negatively. Employees may skip standard procedures and not follow the process required to shut down processes under the PA. So the PA monitor is designed to force operators to go through the right steps and acquire the relevant permissions from the required people before they can go ahead and schedule maintenance and take down the process.
What the PA Monitor consists of
- PA_Monitor_AutoStart. This procedure will pass the process name as a parameter to the external script that will start the process under the PA.
- PA_Monitor_AutoStop. This procedure will pass the process name as a parameter to the external script that will stop the process under the PA.
Two external scripts
- Start_PA_Process.sh. This script will start the process under the PA passed by the procedure. The script also checks if the process is already running and will not restart the process if it is already running. The script also logs information in the log file PA_MONITOR.log found under the $OMNIHOME/log directory.
- Stop_PA_Process.sh. This script will stop the process under the PA passed by the procedure. The script also checks if the process is already down it will not attempt to stop the process again. The script also logs information in the log file PA_MONITOR.log found under the $OMNIHOME/log directory.
- PA_Monitor_AutoStop trigger. This trigger will check a maintenance table for a maintenance flag and auto maintenance flag.
- If both flags are true it will check the start time and end time. If the process falls within that period it will execute the PA_Monitor_AutoStop.
- PA_Monitor_AutoStart trigger. This trigger will check the maintenance table to see if the process is meant to be in maintenance.
- If the process is not meant to be in maintenance it will execute the auto start procedure which will automatically start the process.
- If the process is in the Maintenance table and falls with in the maintenance period it will change the severity from 5 to 4 and update the SuppressEscl field to 6 (Maintenance).
- Once the process is no longer in the maintenance period the trigger will update the SuppressEscl field to 0 (Normal) which will then cause the process to be restarted.
- Delete_Maintenance. This trigger will check the maintenance table for expired scheduled maintenance. If the maintenance period has passed it will remove the entry from the maintenance table.
- Set maintenance period. Used to define a maintenance period.
- Cancel maintenance period. Used to override an existing maintenance period that has been set.