Using Generic agent with IMF
Intelligent monitoring is supported for the Generic agent only under specific configurations. The complete list of such configurations is provided in the following table:
Table:
|
MonitorProgram
|
MonitorProcesses |
PidFiles |
IMF Monitoring Mode |
|
Not Configured
|
Not Configured |
Not Configured |
Not Applicable |
|
Not Configured
|
Not Configured |
Configured |
Online, Offline |
|
Not Configured
|
Configured |
Not Configured |
Online, Offline |
|
Not Configured
|
Configured |
Configured |
Online, Offline |
|
Configured
|
Not Configured |
Not Configured |
Offline Only |
|
Configured
|
Not Configured |
Configured |
Online, Offline |
|
Configured
|
Configured |
Not Configured |
Online, Offline |
|
Configured
|
Configured |
Configured |
Online, Offline |
Note: |
When you do not configure MonitorProcesses, IMF monitors only the StartProgram on the offline node. Hence, the MonitorFreq of IMF attribute must be set to 1 so that IMF monitors the resource on the offline node every monitor cycle. |
When multiple processes are configured under the MonitorProcesses attribute and only some of them are running, offline registration with IMF fails repeatedly until RegisterRetryLimit is reached. In such a scenario, IMF cannot determine when the resource goes ONLINE and the agent monitors the resource in the traditional way.
