domain
Command Function
Configures scenario-specific parameters in interactive mode.
- You can select and view multiple configuration templates, and save or revert selected templates.
- Full functionality of the text-based user interface (TUI) requires the terminal emulator to meet the following requirements:
- xterm style.
- Dark interface color.
- UTF-8 encoding format.
- It is recommended to use the latest version of MobaXterm. The draggable divider in the TUI requires the terminal emulator to support mouse movement event reporting. You can run the following command to check whether this feature is supported.
printf '\033[?1003h\033[?1006h'
After entering the command, move the mouse. If this feature is supported, the output will be as follows:

The restoration command is as follows:
printf '\033[?1003l\033[?1006l'
Syntax
kspect domain [-h]
Parameter Description
|
Parameter |
Description |
|---|---|
|
None |
Goes to the scenario-specific parameter configuration screen. |
|
-h/--help |
Obtains help information. |
Directory Description
The resource directory for scenario-specific parameter configurations is structured as follows:
├── resource │ ├── backups │ ├── libraries │ │ ├── bios │ │ ├── nic.sh │ │ ├── swap.sh │ │ └── sysctl.sh │ ├── resource.yaml │ └── templates │ ├── b_domain.yaml │ └── yunnan_mobile.yaml
|
Directory |
Description |
|---|---|
|
backups |
Backup directory of the scenario-specific configuration file. When parameter changes are applied, a backup of the previous configuration is automatically generated and stored in this directory. |
|
libraries |
Atomic capability library folder containing executable files.
NOTE:
The tool provides the following executable files to ensure that parameter changes take effect permanently: If the parameter changes do not take effect after the server is restarted, check the relevant system configuration files.
|
|
resource.yaml |
Mapping files for specific executable files. |
|
templates |
Scenario-specific configuration template directory. The tool provides two template files (b_domain.yaml and yunnan_mobile.yaml). |
Example
- Go to the interactive user interface.
1./kspect domain - Select a template.
By default, the b_domain.yaml file is selected. Click Apply. The page for setting parameters is displayed.

Table 3 Selection screen Area
Name
Description
①
Template selection
Use the mouse or keyboard to select a template.
②
Parameter configuration preview
Preview the full configuration of the template, including all configuration items and recommended values in the template.
③
Operation bar
Apply a template or exit.
- Configure parameters.
You can change the parameter values in the Modify Value column.
If you need to modify BMC-related parameters, enter the BMC information in the Dependency_Parameters area, and click the Apply Depend button to refresh the related content.

Table 4 Parameter configurations Area
Name
Description
①
Dependency configurations
Some parameters can only be collected with BMC information. A BMC information input window is provided. After entering the information, click Apply Depend to refresh the parameters in the parameter details area that depend on the BMC.
②
Parameter details
Displays detailed parameter information.
- Name: Parameter option name. You can click the check box or parameter name before a parameter to select or deselect the parameter.
- Current Value: Current parameter value.
- Recommended Value: Recommended parameter value.
- Modify Value: Updated parameter value. For text settings, click the current value and enter the desired content. For values marked with a right arrow (→), click the current value and select another from the drop-down list.
③
Backup details
In the file backup area, when you click Apply Change, a backup file of the previous parameter configuration is automatically created. You can load, rename, or delete the backup file.
④
Operation bar
Provides the Refresh, Apply Change, Back, and Exit options.
Table 5 Recommended values of parameters in the b_domain.yaml file Parameter
Recommended Value
Description
NIC Queue Count
NUMA Core Count
Set the NIC queue count to the number of CPU cores in the NUMA node where the NIC resides.
IRQ Core Bindg
IRQ NUMA Affinity
Bind NIC hardware interrupts to CPU cores in the same NUMA node as the NIC.
vm.min_free_kbytes
NUMAs*2097152
Set the minimum free memory in the system to 2 GB multiplied by the number of NUMA nodes in the current environment.
- Load the modified parameter values.
After completing the modification, click Apply Change and then confirm it by clicking Yes in the dialog box that is displayed. Once the changes are applied, a backup of the previous parameter configuration is automatically created.

- Exit the screen.
After completing the configuration, click Exit in the lower right corner.