-> show /CMM/powermgmt actual_power
Note - The actual_power is the same as /SYS/VPS. The actual_power is the value returned by the sensor.
|
Monitor Individual Power Supply Consumption
|
1. Log in to the ILOM server SP CLI or ILOM CMM CLI.
2. Type the show command to display the individual power supply consumption.
For example:
- For CLI on rackmounted system:
-> show /SYS/platform_path_to_powersupply/INPUT_POWER|OUTPUT_POWER
-> show /CH/platform_path_to_powersupply/INPUT_POWER|OUTPUT_POWER
The following table lists and describes the properties of the CLI sensors. Both sensors, INPUT_POWER and OUTPUT_POWER, have the same properties.
Property
|
Value
|
type
|
Power Unit
|
class
|
Threshold Sensor
|
value
|
<total consumed power in watts, for example "1400">
|
upper_nonrecov_threshold
|
N/A
|
upper_critical_threshold
|
N/A
|
upper_noncritical_threshold
|
N/A
|
lower_noncritical_threshold
|
N/A
|
lower_critical_threshold
|
N/A
|
lower_nonrecov_threshold
|
N/A
|
Note - Power sensors are not supported on server modules (blades).
|
Monitor Available Power
|
1. Log in to the ILOM server SP CLI or the ILOM CMM CLI.
2. Type the show command to display the available power.
For example:
- For CLI on a rackmounted system:
-> show /SP/powermgmt available_power
-> show /CMM/powermgmt available_power
Monitor Server Hardware Maximum Power Consumption
|
1. Log in to the ILOM server SP CLI.
2. Type the show command to display the hardware configuration maximum power consumption.
For example:
-> show /SP/powermgmt hwconfig_power
Monitor Permitted Power Consumption
|
1. Log in to the ILOM Server SP CLI or the ILOM CMM CLI.
2. Type the show command to display the permitted power consumption.
For example:
- For CLI on a rackmounted system:
-> show /SP/powermgmt permitted_power
-> show /CMM/powermgmt permitted_power
Monitor Power Consumption History
|
1. Log in to ILOM the server SP CLI or the ILOM CMM CLI.
2. Use the show command to view actual power consumption.
For example:
->show /SYS/VPS
- From a server module in a chassis:
->show /CMM/BLn/VPS
- From the CMM:
->show /CH/VPS
->show /CH/VPS
/CH/VPS
Targets:
history
Properties:
type = Power Unit
ipmi_name = VPS
class = Threshold Sensor
value = 1400.000 Watts
upper_nonrecov_threshold = N/A
upper_critical_threshold = N/A
upper_noncritical_threshold = N/A
lower_noncritical_threshold = N/A
lower_critical_threshold = N/A
lower_nonrecov_threshold = N/A
alarm_status = cleared
Commands:
cd
show
|
3. Use the show command to display 15-, 30-, and 60-second rolling power usage average, and to display a choice of targets for average consumption history.
For example:
- From the server SP, type:
->show /SYS/VPS/history
->show /CH/VPS/history
->show /CH/VPS/history
/CH/VPS/history
Targets:
0 (1 Minute Average, 1 Hour History)
1 (1 Hour Average, 14 Day History)
Properties:
15sec_average = 1210.000
30sec_average = 1400.000
60sec_average = 1800.000
Commands:
cd
show
|
4. Use the show command to display average consumption history by the minute or hour respectively, type the following command with the appropriate target named.
For example
- From the server SP, type:
->show /SYS/VPS/history/0
- From the CMM:
->show /CH/VPS/history/0
For example:
->show /CH/VPS/history/0
/CH/VPS/history/
Targets:
list
Properties:
average = 1500.000
minimum = 1500.000 at Mar 4 08:51:24
maximum = 1500.000 at Mar 4 08:51:23
period = 1 Minute Average
depth = 1 Hour History
Commands:
cd
show
|
5. Use the show command to display sample set details such as time stamp and power consumed in watts.
For example:
- From the server SP, type:
->show /SYS/VPS/history/0/list
- From the CMM, type:
->show /CH/VPS/history/0/list
->show /CH/VPS/history/0/list
/CH/VPS/history/0/list
Targets:
Properties:
Mar 4 08:52:23 = 1500.000
Mar 4 08:51:24 = 1500.000
Mar 4 08:50:24 = 1500.000
Mar 4 08:49:24 = 1500.000
Mar 4 08:48:24 = 1500.000
Mar 4 08:47:23 = 1500.000
Commands:
cd
show
|
Configuring Power Policy Settings to Manage Server Power Usage
Topics
|
Description
|
Links
|
Platform Feature Support
|
Configure power policy
|
|
- x86 system server SP (prior to ILOM 3.0.4)
- SPARC system server SP
|
Before You Begin
- Review the Power Monitoring Terminology defined in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
Note - The power policy feature described in this section might not be implemented on the platform server or CMM that you are using. To determine whether the power consumption feature described in this section are supported on your server or CMM, see the ILOM Supplement or Administration guide provided for your server.
|
- To configure the Power Policy properties in ILOM for x86 servers, you must have Administrator (a) role privileges and you must be running ILOM 3.0.3 or earlier.
- To configure the Power Policy properties in ILOM for SPARC servers, you must have Administrator (a) role privileges and you must be running ILOM 3.0 or later.
Configure Server SP Power Policy
|
1. Log in to the ILOM server SP CLI.
2. Type the set command to set the power policy:
-> set /SP/powermgmt policy=Performance|Elastic
3. Type the show command to display the power policy:
-> show /SP/powermgmt policy
Configuring Power Consumption Threshold Notifications
Topics
|
Description
|
Links
|
Platform Feature Support
|
View or configure power consumption notification thresholds
|
|
- x86 system server SP
- SPARC system server SP
- CMM
|
Before You Begin
- Review the Power Monitoring Terminology defined in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
- You must have ILOM 3.0.4 or later installed on your server or CMM.
- You must have Administrator (a) privileges in ILOM to change power consumption configuration variables.
View and Configure Notification Thresholds Using the CLI
|
1. Log in to ILOM server SP CLI or the ILOM CMM CLI.
2. To view the current settings, type:
-> show /SP/powermgmt
or
-> show /CMM/powermgmt
3. To set the value for notification thresholds, type:
-> set threshold1|2=n
Where n represents watts.
Note - Setting the notification threshold value to 0 (zero) will disable the notification threshold option.
|
Monitoring Component Power Allocation Distributions
Topics
|
Description
|
Links
|
Platform Feature Support
|
View component allocation metrics for server or CMM
|
|
- x86 system server SP
- SPARC system server SP
- CMM
|
Before You Begin
- Review the Power Monitoring Terminology defined in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
- Review the conceptual information about Component Allocation Power Distribution in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
- You must have ILOM 3.0.6 or later installed on your server or CMM. Where noted, some procedures described in this section require the server or CMM to be running ILOM 3.0.10 or later.
- As of ILOM 3.0.10, some of the CLI properties for the CMM and blades have changed:
- allocated_power renamed to granted_power
- allocatable_power renamed to grantable_power
- permitted_power renamed to grant-in-aid
Where:
- Granted power represents the sum of the maximum power consumed by either a single server component (such as, memory module), a category of server components (all memory modules), or a all server power consuming components.
- Grantable Power indicates the total remaining power (watts) available from the CMM to allocate to blade slots without exceeding the grant limit.
- Grant Limit represents the maximum power the system will grant to a blade slot.
- You must have Administrator (a) privileges in ILOM to change any power consumption or allocation configuration variables.
View Server Power Allocations for All System Components
|
1. Log in to the ILOM server SP CLI.
2. To view the sum of power allocated to all components in the system, type the following command:
-> show /SP/powermgmt allocated_power
View Server Component Power Allocations
|
1. Log in to the ILOM server SP CLI.
2. To view power allocated to a component category (fans, CPUs, and so forth), type the following command:
-> show /SP/powermgmt/powerconf/component_type
Where component_type is the name of the component category.
For example, to view the power allocated to all CPUs (component category), you would type:
-> show /SP/powermgmt/powerconf/CPUs
Note - For each command, the read-only value for the maximum power consumed by the component is returned, measured in watts.
|
3. To view the power allocated to a specific component, type the following command:
-> show /SP/powermgmt/powerconf/component_type/component_name
- Where component_type is the name of the component category.
- Where component_name is the name of the component.
For example, to view the power allocated to a specific CPU, you would type:
-> show /SP/powermgmt/powerconf/CPUs/CPUn
Where n is the installed location number of the CPU.
Other rackmount server components can include:
- /SP/powermgmt/powerconf/Fans/FB0_FMn
- /SP/powermgmt/powerconf/PSUs/PSn
- /SP/powermgmt/powerconf/CPUs/MB_Pn
- /SP/powermgmt/powerconf/memory/MB_P0_Dn
- /SP/powermgmt/powerconf/IO/DBP_HDDn
Other server module components can include:
- /SP/powermgmt/powerconf/CPUs/MB_Pn
- /SP/powermgmt/powerconf/memory/MB_P0_Dn
- /SP/powermgmt/powerconf/IO/DBP_HDDn
View CMM Power Allocations for All Chassis Components
|
1. Log in to the ILOM CMM CLI.
2. To view the sum of power allocated to all chassis system components, do one of the following:
- If you are running ILOM 3.0.8 or earlier, type the following command:
-> show /CMM/powermgmt allocated_power
- If you are running ILOM 3.0.10 or later, type the following command:
-> show /CMM/powermgmt granted_power
3. To view the remaining power available to allocate to blade slots, type the following command:
-> show /CMM/powermgmt allocatable_power
View CMM Component Power Allocations
|
1. Log in to the ILOM CMM CLI.
2. To view power allocated to a component category (fans, blade slots, and so forth), type the following command:
-> show /CMM/powermgmt/powerconf/component_type
Where component_type is the name of the component category.
For example, to view the power allocated to all blade slots (component category), you would type:
-> show /CMM/powermgmt/powerconf/bladeslots
Note - For each command, the read-only value for the maximum power consumed by the component is returned, measured in watts.
|
3. To view the power allocated to a specific component, type the following command:
-> show /CMM/powermgmt/powerconf/component_type/component_name
Where component_type is the name of the component category.
Where component_name is the name of the component.
For example, to view the power allocated to a specific blade slot, you would type:
-> show /CMM/powermgmt/powerconf/bladeslots/BLn
Where n is the location number of the blade slot.
Other CMM components can include:
- /CMM/powermgmt/powerconf/NEMs/NEMn
- /CMM/powermgmt/powerconf/Fans/FMn
- /CMM/powermgmt/powerconf/PSUs/PSn
View Blade Slots Granted Power or Reserved Power as of ILOM 3.0.10
|
1. Log in to the ILOM CMM CLI.
2. To view the sum of power granted to all blade slots or the sum of power reserved for all auto-powered I/O blade slots, type the following command:
-> show /CMM/powermgmt/powerconf/bladeslots
The granted_power value and reserved_power value allocated to all blade slots appears, see example CLI output:
-> show /CMM/powermgmt/powerconf/bladeslots
/CMM/powermgmt/powerconf/bladeslots
Targets:
BL0
BL1
BL2
BL3
BL4
BL5
BL6
BL7
BL8
BL9
Properties:
granted_power = 952
reserved_power = 876
Commands:
cd
show
|
View Granted Power or Grant Limit for Blade as of ILOM 3.0.10
|
1. Log into the ILOM CMM CLI.
2. To view the sum of power granted to an individual blade or to the grant limit value set for a blade, type the following command:
-> show /CMM/powermgmt/powerconf/bladeslot/BLn
Where n represents the slot location for the blade.
Example output:
-> show /CMM/powermgmt/powerconf/bladeslots/BL1
/CMM/powermgmt/powerconf/bladeslots/BL1
Targets:
Properties:
granted_power = 0
grant_limit = 800
Commands:
cd
set
show
|
Configuring Power Limit Properties
Topics
|
Description
|
Links
|
Platform Feature Support
|
Configure server SP power limit properties
|
|
- x86 system server SP
- SPARC system server SP
- CMM
|
Before You Begin
- Review the Power Monitoring Terminology defined in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
- Review the conceptual information about Server Power Limit (or Server Power Budget) in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
- You must have ILOM 3.0.6 or later installed on your server or CMM. Where noted, some procedures described in this section require the server or CMM to be running ILOM 3.0.10 or later.
- As of ILOM 3.0.10, some of the CLI properties for the CMM and blades have changed:
- allocated_power renamed to granted_power
- allocatable_power renamed to grantable_power
- permitted_power renamed to grant_limit
Where:
- Granted power represents the sum of the maximum power consumed by either a single server component (such as a memory module), a category of server components (all memory modules), or a all server power consuming components.
- Grantable Power indicates the total remaining power (watts) available from the CMM to allocate to blade slots without exceeding the grant limit.
- Grant Limit represents the maximum power the system will grant to a blade slot.
- You must have Administrator (a) role privileges in ILOM to change any power management configuration variables.
Configure Permitted Power for Blade Slots
|
1. Log in to the ILOM CMM CLI.
2. To configure the permitted (maximum) power that the CMM will allocate to a blade slot, do one of the following:
- If you are using ILOM 3.0.8 or earlier, type the following command:
-> set /CMM/powermgmt/powerconf/bladeslots/bladeslotn permitted_power=watts
Where bladeslotn represents the blade slot that you want to configure.
For example:
-> set /CMM/powermgmt/powerconf/bladeslots/bladeslot1 permitted_power=1200
Set 'permitted_power' to '1200'
|
- If you are using ILOM 3.0.10 or later, type the following command:
-> set /CMM/powermgmt/powerconf/bladeslots/bladeslotn grant_limit=watts
Where bladeslotn represents the blade slot that you want to configure.
Note - To prevent a server module from powering-on, set the permitted power value for the blade slot to 0.
|
Configure Server Power Budget Properties
|
1. Log in to the ILOM server SP CLI.
2. To view the current power budget settings, type the following command:
-> show /SP/powermgmt/budget
Example output:
/SP/powermgmt/budget
Targets:
Properties:
activation_state = enabled
status = ok
powerlimit = 600 (watts)
timelimit = default (30 seconds)
violation_actions = none
min_powerlimit = 150
pendingpowerlimit = 600 (watts)
pendingtimelimit = default
pendingviolation_actions = none
commitpending = (Cannot show property)
Commands:
cd
show
->
|
3. To configure power budget settings, type the following command:
-> set /SP/powermgmt/budget property=value
Where property=value represents one of the following:
- activation_state=[enabled|disabled]
- pendingpowerlimit=[wattsw|percent%]
- pendingtimelimit=[default|none|seconds]
- pendingviolation_actions=[none|poweroff]
- commitpending=true
Power Budget Property
|
Description
|
Activation State
|
Enable this property to enable the power budget configuration.
|
Power Limit
|
Set a Power Limit in watts or as a percentage of the range between minimum and maximum system power.
Note - The minimum system power is viewable in the CLI under the target /SP/powermgmt/budget min_powerlimit. The maximum system power is viewable from the Allocated Power property in the web interface or from the CLI under the target /SP/powermgmt allocated_power.
|
Time Limit
|
Specify one of the following grace periods for capping the power usage to the limit:
- Default - Platform selected optimum grace period.
- None - No grace period. Power capping is permanently applied.
- Custom - User-specified grace period.
|
Violation Actions
|
The actions that the system will take if the power limit cannot be achieved within the grace period. This option can be set to None or Hard Power Off.
This setting, by default, is set to None.
|
Note - To set the powerlimit, timelimit and violation_action in the ILOM CLI, you must set the matching pending properties and then commit these three pending properties as a group. After these properties are committed by typing set /SP/powermgmt/budget commitpending=true, the new values will apply whenever the budget activation_state is set to enabled.
|
For example:
-> set /SP/powermgmt/budget activation_state=enabled
Set 'activation_state' to 'enabled'
|
Configure Grant Limit for aBlade as of ILOM 3.0.10
|
1. Log in to the ILOM CMM CLI.
Note - To change the grant power limit for any blade in ILOM requires an Admin (a) role user account.
|
2. To configure the permitted (maximum) power that the CMM will allocate to a blade, type the following command:
-> set /CMM/powermgmt/powerconf/bladeslots/BLn grant_limit=watts
Note - To prevent a server module from powering-on, set the grant limit value for the blade to 0.
|
Note - The grant_limit value cannot be less than any amount already granted (granted_power).
|
Monitoring or Configuring CMM Power Supply Redundancy Properties
Topics
|
Description
|
Links
|
Platform Feature Support
|
Monitor or configure the CMM power supply redundancy properties
|
|
|
Before You Begin
- Review the Power Monitoring Terminology defined in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
- Review the conceptual information about power supply redundancy for CMM systems in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
- You must have ILOM 3.0.6 or later installed on your server to configure CMM power supply redundancy properties.
- You must have Administrator (a) role privileges in ILOM to change any power management configuration variables.
Monitor or Configure CMM Power Supply Redundancy Properties
|
1. Log in to the ILOM CMM CLI.
2. To configure power management settings, type the following command:
-> set /CMM/powermgmt property=value
Where property=value represents the redundancy [none|n+n]
For example:
-> set /CMM/powermgmt redundancy=none
Set 'redundancy' to 'none'
|
Note - When you change the redundancy policy, this change affects the amount of power the CMM is permitted to allocate to server modules (blades). The chassis Permitted Power is set to the power that the available power supplies can provide minus the redundant power that is available. In addition, when there is no redundant power available to the system, a loss of a power supply will cause the system to reduce the Permitted Power. If the system reduces the Permitted Power below the power that had already been allocated, you should immediately take steps to turn off the server modules to reduce the allocated power.
|