ILOM Power Budget Status Does Not Function Properly When Disabled and Then Enabled (7009654)

This issue is fixed in system software release 1.3.

In ILOM, you can enable a Power Budget cap (in watts) that works in conjunction with the Power Limit setting. When the power budget cap is reached (the server power consumption goes above the power limit), you will see a “violation” status for the Power Budget feature.

For example:

-> show /SP/powermgmt/budget

 /SP/powermgmt/budget
    Targets:

    Properties:
        activation_state = enabled
        status = ok
        powerlimit = 132 (watts)
        timelimit = 0
        violation_actions = none
        min_powerlimit = 132
        pendingpowerlimit = 132 (watts)
        pendingtimelimit = 0
        pendingviolation_actions = none
        commitpending = (Cannot show property)

-> show /SP/powermgmt/budget

 /SP/powermgmt/budget
    Targets:

    Properties:
        activation_state = enabled
        status = violation
        powerlimit = 132 (watts)
        timelimit = 0
        violation_actions = none
        min_powerlimit = 132
        pendingpowerlimit = 132 (watts)
        pendingtimelimit = 0
        pendingviolation_actions = none
        commitpending = (Cannot show property)

If you disable the power budget feature by setting activation_state=disabled, the power budget status will always show ok. However, if you re-enable the power budget feature by setting activation_state=enabled, the status might always show ok whether there is a power consumption violation, or not.

This behavior is intermittent and can occur in both the ILOM web interface and the ILOM CLI. There is no current workaround.