MAN page from Fedora 30 ipmctl-01.00.00.3474-1.fc30.x86_64.rpm
Section: ipmctl (1)
ipmctl-change-preferences - Modifies one or more user preferences
ipmctl set [OPTIONS] -preferences [PROPERTIES]
Modifies one or more user preferences in the DCPMM software.
- Displays help for the command.
-o (text|nvmxml), -output (text|nvmxml)
- Changes the output format. One of: "text" (default) or "nvmxml".
- The default display of DCPMM identifiers. One of:
- *"UID": Use the DimmUID attribute as defined in the sectionShow Device.
- *"HANDLE": Use the DimmHandle attribute as defined in sectionShow Device. This is the default
- The default display of capacities in the CLI. One of:
- *"AUTO": Automatically choose the best format for each capacity in binarymultiples of bytes (i.e., B, MiB, GiB or TiB). This is the default.
- *"AUTO_10": Automatically choose the best format for each capacity in decimalmultiples of bytes (i.e., B, MB, GB or TB).
- *"B": Displays all capacities in bytes.
- *"MB": Displays all capacities in megabytes.
- *"MiB": Displays all capacities in mebibytes.
- *"GB": Displays all capacities in gigabytes.
- *"GiB": Displays all capacities in gibibytes.
- *"TB": Displays all capacities in terabytes.
- *"TiB": Displays all capacities in tebibytes.
- The interleave settings to use when creating App Direct capacity in theformat: (IMCSize_ChannelSize). Must be one of the BIOS supportedApp Direct settings returned by the command Show System Capabilities.
ByOne is not a valid setting for this preference. The default is"RECOMMENDED" which uses the BIOS recommended App Direct settings.
The same interleave settings are used for all the App Direct capacity inthe system. Therefore, if any App Direct capacity already exists, thispreference cannot be changed.
- The minimum App Direct granularity per DCPMM supported by the commandCreate Memory Allocation Goal. One of:
- *"RECOMMENDED": Use the recommended App Direct granularity of 32 GiB.
- *"1": Allows 1 GiB App Direct granularity which may result in App Direct regionsizes that are not recommended.
- Whether or not the monitor is periodically storing performance metrics for theDCPMMs in the host server. One of:
- *"0": Disable performance monitoring.
- *"1": Enable performance monitoring. This is the default.
- The interval in minutes that the monitor is storing performance metrics (ifenabled). The default value is 180 minutes and must be >= 1.
- Whether or not the monitor is periodically checking for DCPMM events.
- *"0": Disable event monitoring.
- *"1": Enable event monitoring. This is the default.
- The interval in minutes that the monitor is checking for DCPMM events (ifenabled). The default value is 1 minutes and must be >= 1.
- The maximum number of events to keep in the management software. The defaultvalue is 0 (no limit). The valid range is 0 - 2,147,483,647.
- The maximum number of debug log entries to keep in the management software.The default value is 0 (no limit). The valid range is0 - 2,147,483,647.
- Whether debug logging is enabled in the DCPMM host software. These logspertain to the operation of the command-line tool only and do not reflect anylogging functionality of the DCPMM. One of:
- *"0": Logging is disabled. This is the default.
- *"1": Log Errors.
- *"2": Log Warnings, Errors.
- *"3": Log Informational, Warnings, Errors.
- *"4": Log Verbose, Informational, Warnings, Errors.
Use DimmUID as the default DCPMM identifier, and display all capacities in bytes.
ipmctl set -preferences CLI_DEFAULT_DIMM_ID=UID CLI_DEFAULT_SIZE=B
Returns the status of the operation.
Set (Property)=(Value): Success|Error (Code)-(Description)
- RETURN DATA
- SAMPLE OUTPUT
This document was created byman2html,using the manual pages.