Skip to main content

Setting values

Use the following information to setting values.

Changing setting values in security mode​

From V2.6.0, OneCLI supports users to change the setting values in the security mode without specifying them in the command line. In the security mode, OneCLI encrypts the setting values and saves them in the file specified by users in OneCLI config file.

Note

  • Only the config set command supports this function.

  • To change the setting values in security mode through encrypted credentials, refer to Sample/config_plaintext.json.

  1. Run the encrypt command to encrypt the file with plain text setting values.

    Note
    The template file is available in Sample/setting.json. Sample command:
    OneCli encrypt --configfile setting.json --unattended

  2. Remove the file.

  3. Run the OneCLI config set command to change the setting name of the file with plain text setting values information.

    Note

    • It is unnecessary for the user to specify the setting values when running the set command.

    • Sample command:
      OneCli config set IMM.Password.1

Managing UEFI/BMC settings in ThinkSystem V4 systems​

For the ThinkSystem V4 and later systems, OneCLI supports to runs all config commands through Redfish from XCC.

Obtaining UEFI setting names

All setting groups (UEFI, BMC, and VPD) and names will be changed. Under the compatibility mode, OneCLI will convert the legacy setting names to the flat setting names in Redfish for UEFI settings. However, some legacy setting names cannot be converted due to the design change in UEFI or platform differences. To find the correct UEFI setting name, users can run the config commands displaying the configuration settings. For example,

OneCli config set Processors.TurboMode Enabled -c

Obtaining hexadecimal settings

The hex and instance settings are not supported in the ThinkSystem V4 systems. Therefore, to make the settings more readable in hexadecimal, users can use the --hex parameter in the config command. Then all instance settings will be changed to the normal settings.

Setting empty/dummy values

Depending on the UEFI or BMC design, users can set the key settings as empty or dummy. However, to avoid the data loss, it’s not recommended to run the delete command to delete any instances.

Getting the pending value

OneCLI config show command always shows the effective value of UEFI settings on the ThinkSystem V4 systems. If users change the setting value and want to check the pending value before restarting the system, it is recommended to use the comparepending command. The pending value is within the [ XXX ] field. For example,

OneCli config comparepending UEFI.SystemSettings_F1StartControl
UEFI.SystemSettings_F1StartControl=Auto=[TextSetup]

Setting CPU power capping on ThinkSystem V3​

OneCLI supports to set the status, reason, and value of CPU power capping by using the -redfish parameter on the ThinkSystem V3 servers.

Supported settings:

  • CPUPowerCapping.CPU{N}_PowerLimitedValue
  • CPUPowerCapping.CPUDomainPowerLimitCause
  • CPUPowerCapping.CPUPowerLimited
Note
Wherein, {N} stands for the socket number of CPU.

Example

OneCli config show CPUPowerCapping --redfish -b xxxx:xxxx@xxxx
CPUPowerCapping.CPU1_PowerLimitedValue=255
CPUPowerCapping.CPU2_PowerLimitedValue=255
CPUPowerCapping.CPUDomainPowerLimitCause=PSUFailSafe
CPUPowerCapping.CPUPowerLimited=true

Setting One Time Boot​

From V3.5.0, OneCLI supports to communicate with BMC through Redfish API by using the --redfish parameter. Users can also set One Time Boot under the Boot group.

Supported settings:
  • BootSourceOverrideEnabled
  • BootSourceOverrideMode
  • BootSourceOverrideTarget
  • UefiTargetBootSourceOverride

Example of setting One Time Boot to Mounted ISO

OneCli config batch --file onetimeboot.txt --redfish
File “onetimeboot.txt”:
set Boot.BootSourceOverrideEnabled Once
set Boot.BootSourceOverrideMode UEFI
set Boot.BootSourceOverrideTarget Cd

Setting security for ThinkEdge servers​

OneCLI supports to set the security by using the --redfish parameter on the ThinkEdge servers.

Example of supported values

OneCli config showvalues Security --redfish
Security.ChassisIntrusionEnabled=true=false
Security.EncryptionEnabled=true=false
Security.HostShutdown=true=false
Security.MotionDetection=true=false
Security.SED_AK=*generate=backup=restore
Security.StepCounter=0
Security.ThresholdLevel=4_Steps=10_Steps=20_Steps=50_Steps=100_Steps=500_Steps

Example of SED Authentication Key (AK) Management

  • To generate SED AK with the random method:

    OneCli.exe config generate Security.SED_AK --bmc USERID:PASSW0RD@XX.XX.XX.XX --redfish

  • To generate SED AK with the passphrase method:

    OneCli.exe config generate Security.SED_AK --passphrase xxxxxx --bmc USERID:
    PASSW0RD@XX.XX.XX.XX --redfish

  • To backup SED_AK to a file and restore with the file:

    OneCli.exe config backup Security.SED_AK --passphrase xxxxxx --file backup.txt 
    --bmc USERID:PASSW0RD@XX.XX.XX.XX --redfish
    OneCli.exe config restore Security.SED_AK --passphrase xxxxxx --file backup.txt 
    --bmc USERID:PASSW0RD@XX.XX.XX.XX --redfish

Setting XCC cache SED key from remote key management server​

OneCLI supports to set XCC cache SED key by using the -redfish parameter from remote key management server.

Example of supported values

OneCli config show BMC --redfish
BMC.EKMSCacheExpirationIntervalHours=1
BMC.EKMSLastPollingTime=
BMC.EKMSLocalCachedKeyEnabled=false
BMC.EKMSLocalCachedKeyStatus=NoCached
BMC.EKMSPollIntervalMinutes=60
BMC.EKMSPollingEnabled=false
BMC.EKMSPollingStatus=Failed

Example of result of the showvalues command

BMC.EKMSCacheExpirationIntervalHours=LowerBound=1 UpperBound=336 ScalarIncrement=1
BMC.EKMSLocalCachedKeyEnabled=true=false
BMC.EKMSPollIntervalMinutes=LowerBound=5 UpperBound=1440 ScalarIncrement=1
BMC.EKMSPollingEnabled=true=false

Setting XCC extended audit log​

OneCLI supports to set XCC extended audit log by using the -redfish parameter.

Example

OneCli config set BMC.AuditLogCapabilities Enabled --redfish

Setting XCC MPFA function​

OneCLI supports to set XCC Memory Predict Failure Analysis (MPFA) function by using the -redfish parameter.

Example

OneCli config set BMC.MPFAHealthStatusEnabled true --redfish

Setting XCC protective power capping​

OneCLI supports to set XCC protective power capping by using the -redfish parameter.

Example of supported values

OneCli config show BMC --redfish
BMC.FailsafePowerLimit_AllowableMax=750
BMC.FailsafePowerLimit_Capped=false
BMC.FailsafePowerLimit_SetPoint=0
BMC.FailsafePowerLimit_State=Disabled

Example of XCC protective power capping

OneCli config showvalues BMC.FailsafePowerLimit_SetPoint --redfish
BMC.FailsafePowerLimit_SetPoint=LowerBound=1 ScalarIncrement=1 [0 means that disable failsafe power limit]

Viewing and changing the setting value of a remote server through BMC​

To view the current value of setting IMM.SSH_Enable, see the following sample command:

OneCli.exe config show IMM.SSH_Enable --bmc userid:password@host

To change the value of setting IMM.SSH_Enable to Enabled, see the following sample command:

OneCli.exe config set IMM.SSH_Enable Enabled --bmc userid:password@host