Feature Scope

Preparation

1. Log in to aBMC with an account that has configuration permission on the target device.
2. Confirm that the target sub-board is connected to aBMC and is displayed on the Devices > General page.
3. Before configuring, confirm the target device name, its business role, and the expected power recovery behavior.
4. Before restoring power in bulk or centrally, confirm that the policy and delay will not break the dependency order of the array devices.

UI Terminology

When the Policy Takes Effect

aBMC reads and applies sub-board boot policies when PowerManager starts. On models that support sub-board linkage, applying power through the server power button or the sub-board hot-plug flow also re-applies the corresponding policy. Saving a configuration does not immediately restart, power off, or change the state of sub-boards that are already powered on; when a Power-on Delay greater than 0 is set, subsequent power-on actions wait the corresponding number of seconds before executing the hardware power-on callback.

Open the Device List

1. Select Devices in the left main navigation bar.
2. Select General in the secondary navigation bar.
3. Locate the target sub-board in the device list.
4. Check the boot policy in the Boot column; when a delay greater than 0 is configured, Delay: <seconds>s is also displayed below the policy.

List Field Descriptions

Open the Boot Policy Window

1. On the Devices > General page, locate the target sub-board.
2. Click the settings icon in the Actions column of the target device.
3. Select Boot Policy Setting to open the boot policy window.

View the Current Configuration

The boot policy window shows the target sub-board's current Boot Policy and Power-on Delay. Before submitting, verify the device name at the top of the window to avoid writing the configuration to the wrong sub-board.

Select the Boot Policy

Select the target policy from the Boot Policy drop-down list:

Set the Power-on Delay

1. Enter the number of seconds to wait in Power-on Delay.
2. The value must be an integer no less than 0; setting 0 adds no delay.
3. Set a reasonable delay based on the array topology, device dependencies, and power supply capacity. The delay only affects subsequent power-on flows and never automatically restarts a device that is currently running.

Save and Confirm the Result

1. Confirm that the device name, Boot Policy, and Power-on Delay are all correct.
2. Click Confirm to save; click Cancel to discard the changes.
3. Return to the General list and confirm the Boot column shows the new policy.
4. If a delay greater than 0 was set, confirm that Delay: <seconds>s is displayed below the policy.

Query the Target Device's Configuration Capabilities

Before configuring, query the target sub-board's ActionInfo to confirm whether the field accepts input and the allowable values of PowerRestorePolicy.

{
  "Parameters": [
    {
      "DisallowedInput": false,
      "DataType": "Number",
      "Name": "PowerOnDelaySeconds",
      "Required": false
    },
    {
      "DisallowedInput": false,
      "AllowableValues": ["AlwaysOn", "AlwaysOff", "LastState"],
      "DataType": "String",
      "Name": "PowerRestorePolicy",
      "Required": true
    }
  ]
}

Submit the Boot Policy

The request body contains the following fields:

{
  "PowerRestorePolicy": "AlwaysOn",
  "PowerOnDelaySeconds": 0
}

curl --user '<username>:<password>' \\
  --request POST \\
  --header 'Content-Type: application/json' \\
  --data '{
    "PowerRestorePolicy": "AlwaysOn",
    "PowerOnDelaySeconds": 0
  }' \\
  '<protocol>://<device-ip>:<port>/redfish/v1/Systems/<system-id>/Actions/SetPowerConfig'

Select the Target Devices

1. On the Devices > General page, select at least two sub-boards that need the same configuration.
2. Click the settings icon in the Actions column of any selected device.
3. Select Boot Policy Setting to open the bulk configuration window.

Submit the Bulk Configuration

1. In Boot Policy, select the policy to apply to all target devices.
2. In Power-on Delay, set a unified delay in seconds.
3. Verify the selected device scope, then click Confirm.
4. The page sends a separate SetPowerConfig request to each selected device; after all requests complete, the page updates the policies and delays in the list.