08-27-2013 08:50 PM - edited 08-28-2013 12:24 AM
I need to divide CPU Utilization policy into 3 stages:
Everyday: - from 8h00 to 15h00: specify a threshold
- from 15h00 to 17h00: specify a threshold
- from 17h00 to 8h00: specify a threshold
I need to control threshold for myself in each stage.
Solved! Go to Solution.
08-27-2013 09:28 PM
Hi, if you are using the SISPI, then you would know that it is possible to set thresholds outside of the policy, using xpl config.
So, you need to set / change the thresholds at different times of day.
to change the thresholds you would call ovconfchg command.
to do changes per a schedule, you could use a schedule policy and read from a config file containing the change time and new set of thresholds. sample config file below assuming you wish to change only the cpu usage threshold. you can be creative and add some more threshold values for 'load average' too.
# time_of_day thresholds_for_cpu_usage
the schedule policy would check current system time and at 0800 run the following commands -
ovconfchg -ns eaagt -set CpuUsageCriticalThreshold t1
ovconfchg -ns eaagt -set CpuUsageMajorThreshold t2
ovconfchg -ns eaagt -set CpuUsageMinorThreshold t3
ovconfchg -ns eaagt -set CpuUsageWarningThreshold t4
and so on.. optimization can be done to avoid re-implementing the same thresholds every interval - change only when needed.
If you are doing this with your own OM measurement threshold policy, then you can handle the threshold change using scripting - but the thresholds will remain externally inaccessible.
If you are using a simple monitor policy (like OMU 8x style) then you would need 3 sets of policies with differing thresholds set internally, and then you can disable/enable the ones required/not required using a different scheduler policy.
Let me know if you need more info/details.