Manage parameters

Hosts running the Tencent OS do not support RDMA configuration.

Features

• Configure system parameters

• Configure the email server

• Configure SMS parameters

• Configure the syslog server

• Configure the middleware

• Configure RDMA

• Configure ISLP and security hardening

• Configure network settings

• QR code login

• Configure the access protocol

Configure system parameters

Perform this task to configure the global parameters of the management platform.

System parameters include the following:

• Basic System Parameters—Configure basic parameters of the management platform.

• Appearance Customization Parameters—Configure the management platform interface customization parameters.

• Customized Menu Parameters—Configure the customized menu parameters used to access other systems.

• VNC Console Parameters—Configure VNC proxy server parameters. Virtual Network Computing (VNC) enables you to remotely control another computer. It transmits the remote computer screen to the local over the network. VNC consists of VNC clients and VNC servers. The VM consoles in the management platform are VNC clients and VMs on the hosts are VNC servers. Operators might access the VMs within the data center from an external network. As a best practice to ensure data security, specify a VNC proxy server for the VMs. The VNC proxy server is the only node that the data center exposes to external networks. The external network can communicate with VMs within the data center only through the VNC proxy server.

• HA System Parameters—Configure the host heartbeat interval and the storage heartbeat interval. The host heartbeat and storage heartbeat enables the management platform to manage hosts, monitor HA resources, detect failed hosts and VMs in the cluster, and migrate VMs to available hosts.

• Image Clean Up—Set the resource usage thresholds for cached images saved in /vms/nova, for example, cached images for interoperation with NCloud and native OpenStack. The system will clean up cached images that exceed the usage thresholds automatically.

• Storage Space Cleanup Parameters—Set the frequency and time for cleaning the shared storage space. Shared storage space cleanup automatically organizes and reclaims shared storage. It recovers released but not yet reclaimed space, ensuring system health and usable capacity.

• CPU and Memory Parameters—Set the maximum VM CPU and memory allocation ratios for each host. The system no longer creates VMs on a host if one of the ratios is reached.

• Upgrade Parameters—Set the graceful host recovery period during the host upgrade process as needed to ensure a successful upgrade.

• Performance Monitoring Parameters—Set the refresh interval for real-time performance data, performance data polling interval, directory for performance data storage.

• Host Debugging Mode—Set whether to enable debugging mode for hosts. After you enable this mode, you can configure output settings on the advanced settings page of a host for issue location, analysis, and resolution.

Restrictions and guidelines

With RBAC enabled, only security administrators can configure system parameters.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the System Parameters tab.

4. Configure basic system parameters, customization parameters, customized menu parameters, VNC console parameters, HA parameters, and image cleanup parameters, as described in "Parameters."

5. Click Save.

Parameters Basic System Parameters

• Idle Timeout: Specify the idle timeout for the operators. An operator automatically logs out of the system when the idle timeout expires.

• Lockout Period: Specify the time period during which the IP address that an operator uses to access the system is forbidden from logging in to the system. The timer starts for an operator's IP address after the operator fails to log in to the system consecutively for the specified times.

• Max Login Attempts: Specify the maximum number of allowable consecutive login failures. If an operator fails to log in to the system for the specified times, the operator's IP address cannot log in to the system within the specified time period.

• Max Online Operators: Specify the maximum number of online operators. 0 indicates that the number of online operators is not limited.

• Log Level: Select a log level. Options include Error, Warning, and Info.

• Max Client Connection: Specify the maximum number of connections that an IP address can establish to the management platform.

• Alarm Lifetime: Specify the lifetime period of alarms. If the alarm lifetime is longer than 7 days, make sure the root partition on the single management host or the mysql-share partition on the stateful failover system has enough space. If you fail to do so, system faults might occur.

• Recycled VM Lifetime: Specify the lifetime period of VMs in the recycle bin. The system automatically deletes a VM in the recycle bin after the lifetime period of the VM expires. The value of 0 indicates that VMs in the recycle bin will not be automatically deleted. The specified recycled VM lifetime applies when you move a VM to the recycle bin if you do not specify a new recycled VM lifetime for the VM.

• Temporary File Directory: Enter a temporary directory for uploaded and downloaded files.

• Migration Pause Period: Set the VM pause period for migrating the remaining dirty pages before online migration is completed. As a best practice, do not set this parameter.

• Delete Logs Older Than: Use this parameter to restrict the operation log cleanup time range. The system only deletes logs older than the configured duration. For example, when you set this parameter to 6 months, the system only deletes operation logs older than 6 months. Logs from the last 6 months cannot be deleted.

• Encoding Mode: Select the encoding mode that the hosts use to report alarms to the alarm server. Options include BASE64, GBK, and UTF-8.

• Intel RDT Noisy Neighbor Quieting: Select whether to enable Intel RDT noisy neighbor quieting. After you enable this feature on the system parameter configuration page, you can enable this feature for a VM on the VM editing page. To enable Intel RDT noisy neighbor quieting for a VM, make sure the physical CPUs on the host where the VM resides support this feature.

• Max Snapshots: Specify the maximum number of external snapshots that can be created for a VM. When you create snapshots through a snapshot policy, the allowed number of snapshots depends on the smaller value between the Max Snapshots in the snapshot policy and Max Snapshots system parameter. When management platform automatically executes a snapshot policy, if the number of snapshots reaches the limit, it automatically deletes the earliest snapshots. When you manually create external snapshots, the Max Snapshots system parameter takes effect. If the number of snapshots has reached the value for the Max Snapshots system parameter, the system reports an error and prohibits snapshot creation. To manually create a snapshot, delete unnecessary snapshots and try again.

• Storage Pool Level-2 Directory: Enable the system to create level-2 directories for VMs in storage pools.

○ With this feature enabled, the system automatically creates a level-2 directory named VM name_dir in the root directory of a storage pool to store a VM image file when you perform an operation that creates the VM image file, such as deploying a VM.

○ With this feature disabled, the system does not create level-2 directories in storage pools, and existing level-2 directories are still available for use.

• Shared Storage Fault Action: Select the action to take when the shared storage of a host fails. Options include Restart Host and Do Not Restart Host.

• VM IPv6 Address Management: Select whether to enable IPv6 configuration for VMs. If you select Yes, you can configure IPv6 addresses for VMs when you add, Edit, or clone VMs, or deploy VMs through templates. When you view information about a VM, its IPv6 address is displayed.

• Intelligent DRX and DRS: Select whether to enable intelligent DRX and DRS. Hosts running the Tencent OS do not support this feature. Intelligent DRX: Obtains the DRX services that are effective and enabled with intelligent DRX at an interval of 10 minutes.

○ If a metric value of a service VM exceeds the corresponding threshold specified in a DRX service (for example, setting the service duration to 20 seconds and configuring the condition as CPU usage > 60%), DRX is triggered.

○ If no metric values of service VMs exceed the specified thresholds in a DRX service, DRX is triggered when the following conditions are met:

▪ The system predicts whether the CPU usage and memory usage will exceed the thresholds 5 minutes and 10 minutes later based on the history data in the last 3 days for each service VM. Either of the predicted value of a service VM exceeds the threshold.

▪ The current metric value of the service VM is in the range of 0.875 × A to A. A indicates the threshold specified in the monitoring policy for resource import.

Intelligent DRS: Obtains the DRS services that are effective and enabled with intelligent DRS at an interval of 10 minutes.

○ If a metric value of a host exceeds the specified threshold in a DRS service, DRS is triggered.

○ If no metric values of hosts exceed the specified thresholds in a DRS service, DRS is triggered when the following conditions are met:

▪ The system predicts whether the CPU usage and memory usage will exceed the thresholds 5 minutes and 10 minutes later based on the history data in the last 3 days for each host. Either of the predicted value of a host exceeds the threshold.

▪ The current metric value of the host is in the range of 0.875 × A to A. A indicates the threshold specified in the monitoring policy for dynamic compute resource scheduling.

• DRS VM Startup: Set the state of DRS VM startup. With this function enabled, the system checks whether a host meets the VM startup requirements before starting up a VM on the host. If the requirements are not met, the system migrates the VM to the optimal host to start up. This function takes effect only when automatic migration is enabled for VMs.

• Shared File System Overcommitment Limit: Select whether to enable shared file system overcommitment limit. With this feature disabled, shared file system overcommitment is not limited. As a best practice, enable this feature for critical services. With this feature enabled, you can set the shared file system overcommitment ratio. If you do not enable this feature, monitor the shared file system usage. When the shared file system usage is high, expand the file system or delete unnecessary files to avoid read/write service interruption.

• Overcommitment Ratio for Shared File Systems: Set the overcommitment ratio for shared file systems. To disable overcommitment, set the value to 0. A larger overcommitment ratio indicates a higher overcommitment multiplier. After you set the overcommitment ratio for shared file systems, the system automatically enables shared file system overcommitment alarm if this feature is not enabled. This parameter is available only after you enable shared file system overcommitment limit.

• Custom Volume Provisioning: Set the default provisioning mode for VM disks. Options include lazy zeroed, eager zeroed, and thin.

○ Lazy Zeroed—Allocates the specified maximum storage size to the storage volume when the storage volume is created. Data on the physical device is not erased during creation, but is erased on first write from the VM.

○ Eager Zeroed—Allocates the specified maximum storage size to the storage volume when the storage volume is created. Data remaining on the physical device is erased during creation. It might take a longer time to create storage volumes in this format than to create storage volumes of other formats.

○ Thin—Allocates only as much storage space as the storage volume needs for its initial operations when the storage volume is created. If the storage volume needs more storage space later, you can allocate as much storage space as the volume requires based on the specified maximum storage size.

• Force NTP Sync: Select whether to enable the force NTP sync feature. With this feature enabled, the system forcibly restarts the NTP service upon detecting a time difference with the NTP server. After restart, the NTP service immediately synchronizes with the NTP server. With this feature disabled, the system adjusts the time gradually and smoothly without restarting the NTP service.

• Reset: To restore basic system parameters (except for Custom Volume Provisioning) to the default, click Reset.

Appearance Customization Parameters

• System Name: Enter a name for the management platform.

• Copyright Info: Enter the copyright information on the login page.

• Homepage Tiny Logo: Enter the path where the small size homepage logo is saved. The logo is displayed on the top left of the homepage when the navigation tree is collapsed.

• Favicon: Enter the path where the favicon is saved.

• Copyright Logo: Enter the path where the copyright logo is saved.

• Login Page Background: Enter the path where the login page background is saved.

Customized Menu Parameters

• Menu Name: Enter the name of the system to be accessed from the management platform.

• Menu URL: Enter the URL for accessing the system.

VNC Console Parameters

• Server IP: Enter the IP address of the VNC proxy server.

• Username: Enter the username used to access the VNC proxy server.

• VNC Proxy Login Password: Enter the password for the user to access the VNC proxy server.

• VNC Password: Select whether to use VNC random password for the VMs. After you enable this feature, the configured VNC passwords become invalid.

• Default Password of VNC Console: Specify the password used to connect to the VNC consoles of VMs. This password takes effect only on VMs that are created after the password configuration. To change the VNC console password of a specific VM, access the VM editing page.

DNS Server Parameters

DNS Server: Enter a maximum of three semicolon-separated DNS server IP addresses for the management platform. This setting takes effect on all hosts on the management platform.

HA system Parameters

• Use the default settings for the HA system as long as possible. The stability of platform might degrade if a too large or too small value is set.

• Do not change the default HA settings for initial deployment.

○ To change the HA settings for temporary use, evaluate your configuration first and make sure you understand the impact of the change on services.

○ To change HA settings for long time use, contact technical support to evaluate the impact on services.

• Host Heartbeat Interval (Seconds): Specify the interval at which hosts send heartbeat packets to the management platform. If a host fails, the heartbeat is interrupted, and VMs on the host are migrated to other hosts in the same cluster after three host heartbeat intervals and three storage heartbeat intervals.

• Storage Heartbeat Interval (Seconds): Specify the interval at which a host writes timestamps to the storage pool. If a storage network fails, the heartbeat is interrupted, and affected VMs are migrated to other hosts in the same cluster after three storage heartbeat intervals.

• VM Migration Mode: Select a VM migration mode in the HA system. Options include Balance First and Efficiency First.

○ Balance First—Assigns VMs to less-loaded hosts for balanced resource usage. This prioritizes load balancing across nodes in a cluster but might reduce migration speed. In this mode, a maximum of three VMs can be migrated at a time.

○ Efficiency First—Assigns VMs to more-loaded hosts with shorter migration paths. This prioritizes migration speed and efficiency but might result in uneven load distribution. In this mode, a maximum of 32 VMs can be migrated at a time.

Image Cleanup Parameters

• Max Usage (%): Specify the threshold for triggering image cleanup. When the space usage of /vms/nova exceeds the maximum usage threshold, the system cleans up the cached images in this path until the space is larger than the reserved space or smaller than the specified space usage after cleanup.

• Reserved Space: Specify the space that must be reserved after image cleanup.

• Usage After Cleanup: Specify the maximum space usage after image cleanup. The value range for this field is 40% to the value for the Max Usage (%) field minus 1%. The default is 60%.

Storage Space Cleanup Parameters

• Frequency: Configure the interval for the system to execute storage space cleanup tasks, specifying how often the task runs. Options include Daily, Weekly, and Monthly.

• Date: Configure this option when the frequency is set to monthly. This parameter specifies the exact date (for example, the 1st day of each month) to execute storage space cleanup.

• Days: Configure this option when the frequency is set to weekly. This parameter specifies the exact day (for example, Monday) to execute storage space cleanup.

• Time: Configure the specific execution time during the day (for example, 02:00) to trigger the storage space cleanup task.

CPU and Memory Parameters

• Reserve Host Memory: Configure whether to reserve host memory. If you select Yes, the system reserves 20% of the host memory or 10 GB host memory (whichever is smaller). The reserved memory of a host cannot be used for VMs started on or migrated to the VM.

• Memory Allocation Ratio for All VMs: Configure the maximum ratio of the memory allocated to all VMs to the total memory size of a host. The system identifies whether this ratio is reached when one of the following events occurs:

○ A VM is created, deployed, or cloned.

○ A VM is migrated manually or automatically by the HA or DRS feature.

○ A VM is restored from the recycle bin.

○ A VM is added by DRX.

○ A VM is migrated to a host through cloud rainbow.

○ CPU or memory allocation is edited for a VM.

○ An OVF template is imported.

○ A VM is restored from a snapshot or backup.

To ensure service continuity when the maximum memory allocation ratio is exceeded, DRX and VM migration by the HA or DRS feature will still run normally.

• Memory Allocation Ratio for Running VMs: Configure the maximum ratio of the memory allocated to running VMs to the total memory size of a host. The system identifies whether this ratio is reached when one of the following events occurs:

○ A VM starts.

○ CPU or memory allocation is edited for a running VM.

○ A VM is restored from a memory snapshot.

○ A running VM is migrated manually.

○ A VM is migrated automatically by DRS.

○ A VM is added by DRX.

○ A VM is migrated to a host through cloud rainbow.

To ensure service continuity when the maximum memory allocation ratio is exceeded, DRX and VM migration by the HA or DRS feature will still run normally.

• CPU Overcommit: Select whether to enable CPU overcommitment. Options include Yes and No. If you select Yes, the number of vCPUs bound to the physical CPUs of a NUMA node can exceed the number of the physical CPUs. If you select No, the number of vCPUs bound to the physical CPUs of a NUMA node cannot exceed the number of the physical CPUs.

• CPU Allocation Ratio for All VMs: Configure the maximum ratio of the CPUs allocated to all VMs to the total number of CPUs on a host. The system identifies whether this ratio is reached when one of the following events occurs:

○ A VM is created, deployed, or cloned.

○ A VM is migrated manually or automatically by the HA or DRS feature.

○ A VM is restored from the recycle bin.

○ A VM is added by DRX.

○ A VM is migrated to a host through cloud rainbow.

○ CPU or memory allocation is edited for a VM.

○ An OVF template is imported.

○ A VM is restored from a snapshot or backup.

To ensure service continuity when the maximum CPU allocation ratio is exceeded, DRX and VM migration by the HA or DRS feature will still run normally.

• CPU Allocation Ratio for Running VMs: Configure the maximum ratio of the CPUs allocated to running VMs to the total number of CPUs on a host. The system identifies whether this ratio is reached when one of the following events occurs:

○ A VM starts.

○ CPU or memory allocation is edited for a running VM.

○ A VM is restored from a memory snapshot.

○ A running VM is migrated manually.

○ A VM is migrated automatically by DRS.

○ A VM is added by DRX.

○ A VM is migrated to a host through cloud rainbow.

To ensure service continuity when the maximum CPU allocation ratio is exceeded, DRX and VM migration by the HA or DRS feature will still run normally.

Upgrade Parameters

Graceful Host Recovery Period (Seconds): Configure this parameter for the system to wait for a specific period of time to all a host to restart successfully and restore to normal state. This practice ensures that the host has completed the upgrade and is running stably before continuing to run VMs. This parameter takes effect only when a restart is required in host upgrade.

Performance Monitor Parameters

• Monitor Refresh Interval: Set the refresh interval for real-time performance data. The minimum interval is 30 seconds and the maximum interval is 10 minutes.

• Monitor Data Polling Interval: Set the interval at which the system records performance data. The minimum interval is 10 seconds and the maximum interval is 120 seconds.

• Data Directory for Primary Node: Specify the directory for the saving the performance data in the database of the primary node. Edit this directory directly as needed. Do not set the data directory to a shared storage path of the hardware assisted locking type. To estimate the required storage space, click Estimate Used Storage Space.

○ Hosts: Enter the estimated number of hosts to be added to the management platform.

○ VMs: Enter the estimated number of VMs used on the management platform.

○ vNICs: Enter the estimated number of NICs used by each VM on the management platform.

○ VM Disks: Enter the estimated number of disks used by each VM on the management platform.

○ Host NICs: Enter the estimated number of NICs used by each host on the management platform.

○ Host Disks: Enter the estimated number of disks used by each host on the management platform.

Configure the mail server

Perform this task to configure the SMTP server.

SMTP provides mail services based on FTP and is mainly used to transfer system mails and notifications.

Restrictions and guidelines

With RBAC enabled, only system administrators and security administrators can configure SMTP server settings.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the Email Server tab.

4. Configure the parameters as described in "Parameters."

5. Click Email Test.

6. Click Save.

Parameters

• Server Address: Enter the domain name or IP address of the SMTP server.

• Port Number: Specify the TCP port number of the SMTP server.

• Require Auth: Enable or disable identity authentication. By default, identity authentication is disabled.

• Encoding Type: Select an encoding type. Options include UTF-8 and GB2312.

• Username: Enter the username for accessing the SMTP server. This parameter is required if you enable identity authentication.

• Password: Enter the password for the user to access the SMTP server. This parameter is required if you enable identity authentication.

• Sender Address: Enter the email address of the sender.

• Sender Name: Enter the name of the sender.

Configure SMS parameters

Perform this task to configure the SMS parameters. After you enable SMS notifications, the system

can send SMS notifications to the administrators through SMS agents such as Jixintong message platform or Huawei message machine.

Restrictions and guidelines

With RBAC enabled, only system administrators and security administrators can configure SMS settings. To send SMS notifications, perform the following tasks:

• Enable SMS notifications and configure SMS parameters.

• Configure SMS notification parameters in "Configure SMS notification parameters."

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the SMS tab.

4. Configure the parameters as described in "Parameters."

5. Click SMS Test.

6. Click Save.

Parameters

• SMS: Select whether to enable SMS notifications or not. If you enable SMS notification, configure the corresponding parameters as required.

• SMS Gateway: Select an SMS platform type. Options include Jixintong Message Platform, Huawei Message Machine, Mobile Agent Server, Ruicheng Message Platform, Common SMS Platform, NetsUnion Platform, and REpresentational State Transfer.

○ Jixintong Message Platform—Third-party message sending platform that requires registration and deployment. For more information, see the official website of Jixintong.

○ Huawei Message Machine—Message sending device.

○ Mobile Agent Server—Third-party message agent server.

○ Ruicheng Message Platform—Third-party message sending platform that requires registration and deployment. For more information, see the official website of Ruicheng.

○ Common SMS Platform—Common SMS platform that sends messages through HTTP requests or commands.

○ NetsUnion Platform.

○ REpresentational State Transfer.

• If Jixintong Message Platform is selected, configure the following parameters:

○ Login Name: Enter the login name used to access the Jixintong message platform.

○ Login Password: Enter the password used to access the Jixintong message platform.

○ HTTP Proxy: Select whether to enable HTTP proxy to access the Jixintong message platform. If HTTP proxy is enabled, configure the proxy address, proxy port, proxy name, and proxy password.

• If Huawei Message Machine is selected, configure the following parameters:

○ IP Address: Enter the IP address of the Huawei message machine.

○ Database Username: Enter the database username of the Huawei message machine.

○ Password: Enter the database password of the Huawei message machine.

○ Login Name: Enter the login name of the Huawei message machine.

○ Login Password: Enter the password of the Huawei message machine.

○ Service Code: Enter the service code of the Huawei message machine.

○ Port Number: Enter the database port number of the Huawei message machine.

• If Mobile Agent Server is selected, configure the following parameters:

○ IP Address: Enter the IP address of the mobile agent server.

○ Interface Code: Enter the interface code of the mobile agent server.

○ Database Username: Enter the database username of the mobile agent server.

○ Password: Enter the database password of the mobile agent server.

○ Port Number: Enter the port number of the mobile agent server.

• If Ruicheng Message Platform is selected, configure the following parameters:

○ IP Address: Enter the IP address of the Ruicheng message platform.

○ Login Name: Enter the login name of the Ruicheng message platform.

○ Login Password: Enter the password of the Ruicheng message platform.

○ HTTP Proxy: Select whether to enable HTTP proxy to access the Ruicheng message platform. If HTTP proxy is enabled, configure the proxy address, proxy port, proxy name, and proxy password.

• If Common SMS Platform is selected, configure the following parameters:

○ SMS Code: Select an encoding type. Options include UTF-8 and GBK.

○ Method: Select a message sending mode. Options include HTTP Request (POST) and Command.

○ Request URL: Enter the request URL for the common SMS platform to send messages. This parameter is required when the send type is HTTP Request (POST). To obtain the exact address and address format, contact the SMS provider. Example: http://192.168.0.1:80/sendSms?userName=a&pwd=b&mobile={Mobile}&content={Co ntent}, where {Mobile} represents the telephone numbers to receive alarm messages and {Content} represents alarm message contents.

○ Command: Enter the command for the common SMS platform to send messages. This parameter is required when the send type is Command. To obtain the scripts, script installation path, and command-line syntax, contact the SMS provider. Example: /vms/sendMsg.sh --mobile {Mobile} --content {Content}, where {Mobile} represents the telephone numbers to receive alarm messages and {Content} represents alarm message contents.

• If REpresentational State Transfer is selected, configure the following parameters:

○ Auth Method: Specify the authentication method.

○ IP Address: Enter the IP address of the REST service.

Configure the syslog server

Perform this task to configure the syslog server. After configuration, the system sends syslog

information for specific operations to the syslog server.

Restrictions and guidelines

• With RBAC enabled, only security auditors can edit syslog server settings. System administrators and security administrators can view syslog server settings.

• You must specify the IP address of the management node on the syslog server. If stateful failover is configured, you must specify the IP addresses of both the primary and backup nodes to ensure that the syslog server can obtain logs correctly after a primary/backup switchover.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the Syslog Server tab.

4. Configure the parameters as described in "Parameters."

5. Click Save.

Parameters

• Server IP: Enter the IP address of the syslog server. If you enter multiple IP addresses, use semicolons to separate the addresses, 192.168.0.27;192.168.0.28 or FC00::1;FC00::2 for example.

• Protocol: Select a protocol to send syslog messages. Options include UDP and TCP.

• Server Port: Specify the port number of the syslog server.

• Range: Specify the types of information to be sent to the syslog server. Options include Alarms, Operation Log, and System Log.

○ Alarms: Alarm information.

○ Operation Log: User operation logs recorded on the management platform task console.

○ System Log: Log information automatically generated during system operation, such as system startup, running status, and fault alarms, excluding command log information after login to the backend through SSH.

• Code：Specify the character set used when system messages are sent to the Syslog server. This parameter should be consistent with the configuration of the target Syslog server. This setting only applies to alarms and operation logs, and does not affect syslog.

• Channel：Configure the complete path for system messages to be transmitted from the management platform to the syslog server.

Configure the middleware

Perform this task to configure the message middleware to communicate with third-party services. After

you edit the middleware settings in the management platform, you must synchronize the settings to the third-party service.

Restrictions and guidelines

With RBAC enabled, only system administrators and security administrators can configure middleware settings. Security auditors can view middleware settings.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the Middleware Settings tab.

4. Configure the parameters as described in "Parameters."

5. Click Save.

6. To restore the initial settings, click Reset.

Parameters

• RabbitMQ Server Address: Enter the address of the RabbitMQ server.

• Port Number: Enter the port number of the RabbitMQ server.

• Username: Enter the username for accessing the RabbitMQ server.

Configure RDMA

With a SeerAnalyzer (SA) platform server specified, the system collects the IP address, server name,

and Rx and Tx packet statistics on an intelligent physical NIC and sends the information to the SA platform. The SA platform displays the CPU usage and Rx and Tx statistics for the intelligent NIC within the specified time range.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the RDMA Monitoring Configuration tab.

4. Configure the parameters as described in "Parameters."

5. Click Save.

Parameters

• Enable RDMA Monitoring: Enable or disable RDMA.

• Server IP: Specify the IP address of the SA platform.

• Port Number: Specify the port number of the SA platform.

Configure ISLP and security hardening

Information security level protection (ISLP) and security hardening secure the system and its

confidential data.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the ISLP and Security Hardening tab.

4. Click Edit and then edit the parameters as needed.

5. Click Save.

Parameters

• Secure Mode: Select whether to enable the secure mode or not. You can enable secure mode only after you enable Mandatory HTTPS. You can create encrypted VMs only after the system is enabled with the secure mode. After you enable the secure mode, the following restrictions take effect:

○ A storage volume can be used by only one VM.

○ The login names of operators cannot be modified.

○ An operator username can be used by only one user at a time.

○ Users can access NSphere only through HTTPS.

Configure network settings

Perform this task to configure a default MTU for a vSwitch. When you add a vSwitch, this MTU is used

as the default MTU for that vSwitch. You can set an MTU for all networks or set an MTU as per network.

Restrictions and guidelines

If you select multiple networks, the default MTU is the smallest one among the MTUs for the selected networks.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the Network Settings tab.

4. Click Edit and then edit the parameters as needed.

5. Click Save.

Parameters

All Networks

• Default MTU: Specify a default MTU for vSwitches of different network types.

Per Network

• Management: Specify a default MTU for the newly added management network vSwitch.

• Service: Specify a default MTU for the newly added service network vSwitch.

• Storage: Specify a default MTU for the newly added storage network vSwitch.

• Backup: Specify a default MTU for the newly added backup network vSwitch.

• Migration: Specify a default MTU for the newly added migration network vSwitch.

Configure QR code login

On the System > Parameters > QR Code Login page of the management platform, you can select

whether to enable the QR code login service. In the current software version, only DingTalk-based QR code login is supported. After you enable this service, you can click QR Code Login on the login page, and then log in to the system by scanning the QR code. This login method does not require entering any username or password.

Restrictions and guidelines

Users of the LDAP authentication method do not support QR code login.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the QR Code Login tab.

4. Click Edit, enable the QR code login service, and then configure the parameters as needed.

5. Click Save.

6. To restore the initial settings, click Reset.

Parameters

• Type: QR code login type. Only DingTalk is supported in the current software version.

• Domain Name: IP address of the authentication server called after the management platform obtains user information from DingTalk. The format is http://ip:port or http://ip. Do not enter a slash (/) at the end of the URL. The ip argument represents the real IP address of the management platform and the port argument represents the real port number of the management platform.

• Auth Method: To use a third-party authentication platform for identity authentication and log in to the management platform through QR code scanning, you can configure this parameter. For example, you can enter script /vms/auth_method.py -t '%s' -c '%s' to have the third-party authentication platform authenticate user access to the management platform.

○ The first parameter -t represents the key that the third-party authentication platform uses for access to authorization resources.

○ The second parameter -c is a code value that the third-party authentication platform assigns to the management platform. The management platform uses this code value to perform user authentication on the third-party authentication platform.

• Appkey: Application public key. You can create multiple applications for an enterprise and each application has a unique public key. Public key information is obtained from the DingTalk open platform.

• AppSecret: Application private key. You can create multiple applications for an enterprise and each application has a unique private key. Private key information is obtained from the DingTalk open platform.

Configure the access protocol

This feature provides protocol selection and secure access control for the management platform. The

access protocol can be HTTP or HTTPS. Use HTTP in the internal network debugging scenario to simplify deployment. Use mandatory HTTPS and a certificate in production environments and high-security industries such as finance and healthcare to ensure communication security and compliance.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the Access Protocol tab.

4. Click Edit to edit the parameters. Click Save to complete the operation.

5. Click Reset to restore configuration parameters to the system default settings.

Parameters

• Mandatory HTTPS: You can enable or disable mandatory HTTPS when Secure Mode is disabled on the ISLP and Security Hardening tab. After you enable mandatory HTTPS, the management platform can be accessed only through HTTPS. Do not modify this parameter if a task is running on the management platform..

• Certificate: When the access protocol is HTTPS, you can upload a security certificate used by the browser. If no certificate is uploaded, the default one is used.