Hello Miran
I've written this some time ago so had to check what I did. It looks like the period I use is a variable set at 0.1 of a day. I think, from 2 hours back till current time .
Let me try and break down what happened form the log:
Automation 23ECF465 100F800B KNAE08468-I NOTHING TO DO, we have a good array @ 445247
# Here it found that the balance was ok for array 445247, so it skipped this array
Automation 23ECF465 100F800B KNAE08468-I NOTHING TO DO, we have a good array @ 448655
# Here it found that the balance was ok for array 448655, so it skipped this array
Automation 23ECF465 100F800B KNAE08468-I =========================================================
Automation 23ECF465 100F800B KNAE08468-I HHHEEEEEEEEEEYYYYYYYYY
Automation 23ECF465 100F800B KNAE08468-I Looks like you need some balance there @ 445282!
Automation 23ECF465 100F800B KNAE08468-I Adjustment needed by about 6%
Automation 23ECF465 100F800B KNAE08468-I This Array is currently doing: 727 so lets move 43.62 IOPS
Automation 23ECF465 100F800B KNAE08468-I =========================================================
Automation 23ECF465 100F800B KNAE08468-I -------------------------------
Automation 23ECF465 100F800B KNAE08468-I ARRAY: 445282
Automation 23ECF465 100F800B KNAE08468-I -------------------------------
Automation 23ECF465 100F800B KNAE08468-I MP BALANCE: {1: 0, 0: 0}
Automation 23ECF465 100F800B KNAE08468-I What I need to do is:
Automation 23ECF465 100F800B KNAE08468-I Average: 0.0
Automation 23ECF465 100F800B KNAE08468-I This means
Automation 23ECF465 100F800B KNAE08468-I 1 - TOTAL: 0 so please add: 0.0
Automation 23ECF465 100F800B KNAE08468-I 0 - TOTAL: 0 so please add: 0.0
Automation 23ECF465 100F800B KNAE08468-I FINAL MP BALANCE COUNT: {1: {'total': 0, 'desired': 0.0, 'current_value': 0}, 0: {'total': 0, 'desired': 0.0, 'current_value': 0}}
Automation 23ECF465 100F800B KNAE08468-I What I've done is the following...
Automation 23ECF465 100F800B KNAE08468-I [] # This means it couldn't find
# Here it found that the balance was not ok for array 445282, so it looked at the metric you selected. I'm guessing IOPS[Maybe try a different metric]? But for that time I found that there was no IOPS difference between the luns on the CPU's to balance it. It couldn't balance 0 IOPS, so it did nothing [].
Automation 23ECF465 100F800B KNAE08468-I =========================================================
Automation 23ECF465 100F800B KNAE08468-I HHHEEEEEEEEEEYYYYYYYYY
Automation 23ECF465 100F800B KNAE08468-I Looks like you need some balance there @ 454250!
Automation 23ECF465 100F800B KNAE08468-I Adjustment needed by about 6%
Automation 23ECF465 100F800B KNAE08468-I This Array is currently doing: 25 so lets move 1.5 IOPS 0151
Automation 23ECF465 100F800B KNAE08468-I =========================================================
# Here it found that the balance was not ok for array 454250, so it looked at the metric you selected. I'm guessing IOPS? But for that time I found that there was a 6& difference between the luns on the CPU's to balance it. It calculated that the array is doing 25 ?IOPS? to bring this in balance(25IOPS*6%) it needed to move 1.50 IOPS. So it would look for a luns that's doing 1 or less IOPS and move it try and balance it. I can imaginge with such a small difference it couldn't find a ldev doing it so it might have also not done anyting.