H3C CAS Cloud Computing Management

Platform
Compatibility Test Tool configuration guidelines
Version: 5W101-20220816

Copyright © 2025 新华三技术有限公司 版权所有，保留一切权利。

No unit or individual may, without the written permission of the Company, copy or reproduce the contents of this
document in part or in whole, and may not be distributed in any form.
In addition to the trademarks of New China Three Technology Co., Ltd., the trademarks, product logos and trade names
of other companies appearing in this manual are owned by their respective owners.
The information in this document is subject to change without notice.
 Table of Contents
1 简介·································································································································1
2 注意事项·····························································································································1
3 配置要求·····························································································································1
4 配置环境·····························································································································1
4.1 服务器·····························································································································1
4.2 软件······························································································································1

5 配置指导·····························································································································2
5.1 服务器安装虚拟化软件················································································································2
5.2 配置模板存储·······················································································································2
5.3 部署配置测试工具的虚拟机············································································································3
5.3.1 模板部署虚拟机·············································································································3
5.3.2 Linux 系统挂载 CAStools·····························································································4
5.3.3 虚拟机配置 IP 地址·········································································································6
5.4 执行测试···························································································································8
5.5 测试结果···························································································································8

i
1 Introduction
The purpose of this document is to describe how to use the Compatibility Test Tool to detect
whether a server is compatible with CAS Cloud Computing Management Platform.

2 Configuration prerequisites
The configurations in this document are configured and validated in a lab environment, and all
parameters of the server and software are factory-default configurations prior to configuration. If
you have already configured the object under test, to ensure that the configuration works, verify
that the existing configuration does not conflict with the one in the following example.

3 Caution
 If there is a failed condition after the execution results, it is recommended to perform the
corresponding function manually on the platform.
 The tool supports X86 architecture and ARM architecture servers.
 The operation of this document does not apply to Windows system virtual machines.
 It is normal for the test to fail with the error "Failed to enter maintenance mode" if only one
server is used. Cause: The virtual machine executing the script on this server is running
and the server does not enter maintenance mode.
 Once the test is complete, log in to the server BCM to obtain the server RAID card
hardware information, and the screenshot is fed back to R&D along with the test log to
update the compatibility list.

4 配置要求
 Prepare at least one server, preferably two, with at least two network ports active on the
server being tested, one of which is the management network. The other network port is
the port to be tested.
 For example, two servers are used to build a virtualization management platform, and the
tested servers will be installed as CVM. The server is not restricted in naming at
installation, but it needs to be modified in the configuration file to the actual name of the
host, for example, the host of the server under test is named cvk111 at build time, and the

1
 value of the variable ${hostname} needs to be changed to cvk111 when modifying the
configuration file. Non-tested server names are unlimited and do not affect testing.
 At least one HBA card is active and if there is no HBA card, the corresponding test item will
fail.
 The test tool involves LLDP testing, please configure LLDP on the switch side beforehand;
In the case of blade servers, the corresponding test item can be ignored as it is not
recommended to turn on LLDP.
 Please turn on the IOMMU feature at Host - Advanced Settings - Startup Item Configuration
(restart the host after power on). It is important to note that ARM architecture and some x86
architecture hosts need to be manually started in the BIOS.

5 Configure the environment

5.1 Server
This document does not strictly correspond to the specific hardware server model. If the use of
the product differs from the actual product, please refer to the relevant product manual or the
actual equipment.

5.2 Software

Software Version

Server virtualization management

Based on actual site requirements
software

6 Configuration instructions
6.1 Server installation virtualization software
Server installs virtualization management software where the test server acts as a CVM, and
after installation configures the host pool, cluster, Join all hosts to the cluster.

6.2 Configure template storage

(1) Log in to CAS Cloud Management Platform, select the Cloud Resources tab at the top,
click the left navigation tree [Virtual Machine Templates] menu item to enter the Virtual
Machine Templates list page.

2
(2) Click the <Template Storage> button to go to the Template Storage List page.
(3) Click the <Add Template Store> button to bring up the Add Template Store dialog box.
(4) Set the relevant parameters.
(5) Click the <OK> button to complete the operation.

(6) Click the <Back> button. Go to the Virtual Machine Templates List page.
(7) Click the <Import Virtual Machine Template> button to bring up the Import Virtual Machine
Template page.
(8) Select the template storage location and click the <Next> button.

3
 (9) Click in the Virtual Box area, select the virtual machine template archive that you want to
import in the pop-up dialog box, or drag a "*.tar.gz" type template file directly into the dotted
box, click the <Start Upload> button to upload the virtual machine template.

Virtual machine templates need to differentiate between ARM and X86 architecture hosts,
ARM hosts use arm_vm_template.tar.gz and X86 hosts use x86_vm_template.tar.gz.

(10) When the upload is complete, click the icon for the Network Policy Template input box to
select a network policy template for the virtual machine template.
(11) Select the template owner.
(12) Click the <OK> button.

6.3 Deploy a virtual machine for the configuration test tool

6.3.1 模板部署虚拟机

(1) Go to the Virtual Machine Templates List page by selecting the Cloud Resources tab at the
top, and selecting the [Virtual Machine Templates] menu item in the left navigation tree.

4
 (2) Select the appropriate virtual machine template to deploy the virtual machine and click the
<Deploy> button in the Actions column to begin deploying the virtual machine.
(3) In the Deploy Virtual Machine Configuration dialog box that pops up, configure basic
information about the virtual machine, host clusters deployed, storage information, Network
information and system information.

If you have two servers, deploy the virtual machines on a non-tested host.

(4) After the task desk shows that the virtual machine has been successfully deployed, the
deployed virtual machine is visible on the node host where the virtual machine is deployed.
(5) Power on the virtual machine, open the console, and see that the virtual machine's system
already exists, consistent with the virtual machine template operating system.

6.3.2 Linux 系统挂载 CAStools

Mount CAStools Mode:

 Mode 1: CAStools can be mounted by modifying the virtual machine.
 Option two: CD-ROM mount can be selected in the hardware information bar from the
Virtual Machine Summary page.

If the virtual machine template has CAStools installed by default, this step can be skipped,
and repeated if it is confirmed that the deployed virtual machine does not have CAStools
installed.

本文档以方式二为例。
(1) Go to the virtual machine summary page by selecting the top Cloud Resources tab, clicking
the left navigation tree (Compute/Host Pool/Host/<Virtual Machine>) or the Compute/Host
Pool/Cluster/Host/<Virtual Machine> menu item.
(2) Select the optical drive in the hardware information bar and click the <Mount Optical Drive>
button.

5
(3) Select the Console tab to go to the console page for this virtual machine. Log in to the
system using the root account, where the root account corresponds to the virtual machine
password deployed by the template, and install CAStools.

 The x86 Architecture Virtual Machine template username/password is: Root/123456.

 The ARM Architecture Virtual Machine template username/password is:
Root/cloud@1234.

(4) Mount 挂载光驱。Execute the mount command in the Linux system virtual machine, mount the
optical drive device, and go to the Linux directory of the agent tool.
(5) Then execute the installation command "./CAS_tools_install.sh ".

6
 (6) After the installation is complete, it is recommended that you restart the virtual machine,
showing that the agent tool is functioning properly on the virtual machine's Summary page.

6.3.3 Virtual machine configuration IP address

After the virtual machine is installed, the IP address does not exist by default and the IP address
information is blank on the virtual machine's Summary page. Virtual machines can be assigned
IP addresses through the virtual machine proxy tool.
(1) Log in to CAS Cloud Management Platform, select the top Cloud Resources tab, click the
left navigation tree [Compute/ Host Pool/ Host/ <Virtual Machine>] or the menu item
Compute/ Host Pool/ Cluster/ Host/ <Virtual Machine> to enter the Virtual Machine
Summary page
(2) Select Modify Virtual Machine to go to the Modify Virtual Machine dialog box of the virtual
machine and check IP/MAC Binding or Manual Configuration in the Network column.
(3) Take the proxy tool configuration as an example. Tick Manual Configuration and enter the
IP address information for the virtual machine in the IP address-related field. Then click the
<Apply> button to restart the virtual machine.

7
 When configuring an IP address, it is recommended that you use the ping function to check
if the IP address is in use.

(4) After the virtual machine IP address configuration is successful, the IP address information
you just configured is displayed on the Network Information page. Or, in the virtual
machine's operating system, verify that the corresponding IP address information is
configured for the virtual machine with the ipconfig command.

(5) Log in to the virtual machine with the ssh tool, upload packages.tar to the root directory,
and then extract the archive.

(6) 进入/root/packages/test/resource/robot，编辑 resource.robot 文件，根据实际情况修改参数，然后保存，各参数解释说

明以本文档为准。
[Root@localhost ~]#cd/root/packages/test/resource/robot

8
*** Variable ***

${hostpool} pool # Host pool name, modify to actual host pool name.

${clustername} cluster # cluster name, please modify to actual cluster name.

${hostname} cvnode # hostname, modify to the actual name of the host being tested.

# cas 登录信息

${host_ip} 172.16.202.98 #请修改为 CAS 系统登录的 IP 地址。

${host_ip_xieyi} http://${host_ip}# is not used and does not need to be

modified.

${host_port} 8080 # Please modify the port number after the IP address when logging
in to the CAS.

${cas_host} http://${host_ip}:${host_port}# Please enter a port number based

on whether or not the CAS system version login is required, and if so, enter a port
number. Delete the "${host_port}" field if you do not need a port.

${cas_username} admin

${cas_password} Cloud@1234 #cas0708 version default password, modify corresponding

login password depending on CAS version.

${cas_back_ip} 172.16.202.98 # Please modify to the IP address of the host being

tested.

${cas_back_username} root # Please modify to the background login username of the

host being tested.

${cas_back_password} root123 # Please change to the tested host background login

password.

${cas_new_password} cloud@12345 # Modify the host password without changing it.

# Performs the centos virtual machine information for the compatibility test case,
modified as appropriate.

${vm_ip} 172.16.134.13 # virtual machine IP, modified as appropriate.

${vm_username} root # 虚拟机登录用户名，根据实际情况修改。

${vm_passwd} 123456 # Virtual machine background login password, modified as

appropriate.

# Provisioning physical network card

${eth0} eth0 #物理网卡 1 根据实际配置，选择接口 up 的网口。

${eth} eth3 # Physical NIC 2 for testing physical NIC mtu tests, pausing recovery
of physical NIC, etc. 根据实际配置，选择接口 up 的网口。

${eth1} eth4 # Physical NIC 3 to test modify the physical NIC driver test.
Depending on the actual configuration, select the network interface of interface

9
 up. All three of the above-mentioned network interfaces need to use a network
interface other than the management network interface. You can choose the same
network interface.

# Virtual machine templates to validate test cases related to virtual machines

${vm_template} vm_template # 虚拟机模板名，请根据 ARM 或 X86 主机进行修改。

${storage_pool} defaultpool # 本地存储池，默认

# 主机 cpu 信息

${cpuSocket} 4 # number of host CPUs, modify to be less than the actual number of
hosts.

${cpuCore} 2 # Host CPU Cores, please modify to a number less than the actual
number of cores on the host.

6.4 Perform the test

进入/root/packages/test，执行 test_execution.sh 脚本，参数 N 代表不重启主机，Y 代表重启主机。
[root@localhost ~]#cd /root/packages/test

6.5 Test results

运行结束后，会在/root 目录下生成一个 result 文件夹，该文件夹中即为测试结果。

10
7 Frequently Asked Questions
(1) Virtual machine deletion failed: The script is not up-to-date.
(2) Network card information is inconsistent: Confirm that the host queried by the front
interface and the host logged in in in the background is not the same host, usually it is
filled in incorrectly. Cvm as the tested server. If cvk is the tested server, you need to
change ${hostname} to the corresponding cvk hostname
(3) Prompt to enter maintenance mode failed on a single server: Yes, there is a virtual
machine running the script on the host.
(4) Error reported Host IOMMU status not on: Needs to be manually turned on.
(4) Prompt that the host NIC cannot be repaired or is not effective after modification:
Make sure that the NIC is used by the virtual switch, and that the interface state needs to
be up, otherwise lldp will fail.
（5）报错“Variable ${host} not found.”：脚本不是最新的。
(6) Physical NIC is in use and setup is not allowed. Probable cause: 1. Test physical
interface used by switch; (2) Multiple interface IOMMU Group groups are the same, or -1
(need to enable iommu in bios).
(7) Online virtual machines do not allow modification of memory reservations or limit
sizes. Limit of Euler version, OK.

11