|
Intelligent resource monitoring has not reduced system utilization
|
If the system is busy even after intelligent resource monitoring is enabled, troubleshoot as follows:
-
Check the agent log file to see whether the imf_init agent function has failed.
If the imf_init agent function has failed, then do the following:
-
Make sure that the IMF attribute values are set correctly for the following attribute keys:
The value of the Mode key of the IMF attribute must be set to 1, 2, or 3. -
The value of the MonitorFreq key of the IMF attribute must be be set to either 0 or a value greater than 0.
For example, the value of the MonitorFreq key can be set to 0 for the Process agent. Refer to the appropriate agent documentation for configuration recommendations corresponding to the IMF-aware agent.
Note that the IMF attribute can be overridden. So, if the attribute is set for individual resource, then check the value for individual resource.
See Resource type attributes.
Verify that the resources are registered with the AMF driver. Check the amfstat command output. -
Check the LevelTwoMonitorFreq attribute settings for the agent. For example, Process agent must have this attribute value set to 0.
Refer to the appropriate agent documentation for configuration recommendations corresponding to the IMF-aware agent.
|
|
Enabling the agent's intelligent monitoring does not provide immediate performance results
|
The actual intelligent monitoring for a resource starts only after a steady state is achieved. So, it takes some time before you can see positive performance effect after you enable IMF. This behavior is expected.
For more information on when a steady state is reached, see the following topic:
See How intelligent resource monitoring works.
|
|
Agent does not perform intelligent monitoring despite setting the IMF mode to 3
|
For the agents that use AMF driver for IMF notification, if intelligent resource monitoring has not taken effect, do the following:
-
Make sure that IMF attribute's Mode key value is set to three (3).
See Resource type attributes.
-
Review the the agent log to confirm that imf_init() agent registration with AMF has succeeded. AMF driver must be loaded before the agent starts because the agent registers with AMF at the agent startup time. If this was not the case, start the AMF module and restart the agent.
See Administering the AMF kernel driver.
|
|
AMF module fails to unload despite changing the IMF mode to 0
|
Even after you change the value of the Mode key to zero, the agent still continues to have a hold on the AMF driver until you kill the agent. To unload the AMF module, all holds on it must get released.
If the AMF module fails to unload after changing the IMF mode value to zero, do the following:
|
|
When you try to enable IMF for an agent, the haimfconfig -enable -agent <agent_name> command returns a message that IMF is enabled for the agent. However, when VCS and the respective agent is running, the haimfconfig -display command shows the status for agent_name as DISABLED.
|
A few possible reasons for this behavior are as follows:
The agent might require some manual steps to make it IMF-aware. Refer to the agent documentation for these manual steps. The agent is a custom agent and is not IMF-aware. For information on how to make a custom agent IMF-aware, see the Cluster Server Agent Developer's Guide. If the preceding steps do not resolve the issue, contact Symantec technical support.
|
