6
For an upgrade from an earlier version to NPU C72B050 or later, skip system reboot in Upgrading Ascend 910 NPU Firmware and system reboot in Upgrading the Ascend 910 NPU Driver. After the driver upgrade is complete, use iBMC to perform a restart.
+For an upgrade from an earlier version to NPU C72B050 or later, skip system reboot in Upgrading Ascend 910 NPU Firmware and system reboot in Upgrading the Ascend 910 NPU Driver. After the driver upgrade is complete, perform a restart.
You can run the following command to check the NPU version:
/usr/local/Ascend/driver/tools/upgrade-tool --device_index -1 --component -1 --version
(Optional) Configuring the DNS Server
-Scenario
For XenServer 7.1, you need to configure a DNS server. For other OSs, skip this section.
-Procedure
- Run the vi /etc/resolv.conf command and change the IP address following nameserver to 8.8.8.8. The value is an example only. Change it as needed.
- Run the systemctl status ntpd.service command to check the ntpd status. If automatic startup is not enabled for ntpd, run the systemctl enable ntpd.service command to enable it.
- Registering an ISO File (Windows)
- - Creating a Windows ECS Using the ISO Image File
+ - Creating a Windows ECS from an ISO Image
- Installing a Windows OS and the VMTools Driver
diff --git a/docs/bms/image-creation-guide/en-us_topic_0000001289583000.html b/docs/bms/image-creation-guide/en-us_topic_0000001289583000.html
index 8cfa38947..ac9761d00 100644
--- a/docs/bms/image-creation-guide/en-us_topic_0000001289583000.html
+++ b/docs/bms/image-creation-guide/en-us_topic_0000001289583000.html
@@ -1,50 +1,47 @@
-
-
-
- Install the Windows OS.
- Specify the parameters on the Install Windows page.Figure 1 Install Windows-
- Click Next.
The installation confirmation window is displayed.
-Figure 2 Installation confirmation window-
- Click Install now.
The Select the operating system you want to install window is displayed.
-Figure 3 Selecting the OS version-
- Select the version of the OS to be installed and click Next.
The Please read the license terms window is displayed.
-Figure 4 License terms window-
- Select I accept the license terms, and click Next.
The Which type of installation do you want? window is displayed.
-Figure 5 Installation type-
- Select Custom (advanced).
The Where do you want to install Windows? window is displayed.
-- If the system displays a message indicating that no driver is found, go to 1.g.Figure 6 Installation path-
- If a disk is displayed, go to 1.j.Figure 7 Installation path+
- Install the Windows OS.
- Specify the parameters on the Install Windows page.Figure 1 Install Windows+
- Click Next.
The installation confirmation window is displayed.
+Figure 2 Installation confirmation window+ - Click Install now.
The Select the operating system you want to install window is displayed.
+Figure 3 Selecting the OS version+ - Select the version of the OS to be installed and click Next.
The Please read the license terms window is displayed.
+Figure 4 License terms window+ - Select I accept the license terms, and click Next.
The Which type of installation do you want? window is displayed.
+Figure 5 Installation type+ - Select Custom (advanced).
The Where do you want to install Windows? window is displayed.
+ - - Click Load Driver and then Browse.Figure 8 Loading drivers-
- Choose the following path and click OK.
vmtools-windows/upgrade/$OS_Version/drivers/viostor
- - Select the driver matching the OS and click Next.
The system may provide multiple drivers. Select VISOTOR.INF shown in the following figure.
-Figure 9 Selecting the driver to install-
- Select the disk and click Next.Figure 10 Installation path-
If the disk type is Offline, you can stop and then start the ECS, and restart the OS installation process.Figure 11 Offline disk+
- Click Load Driver and then Browse.
Figure 8 Loading drivers+- Choose the following path and click OK.
vmtools-windows/upgrade/$OS_Version/drivers/viostor
+- Select the driver matching the OS and click Next.
The system may provide multiple drivers. Select VISOTOR.INF shown in the following figure.
+Figure 9 Selecting the driver to install+- Select the disk and click Next.
Figure 10 Installation path+- If the disk type is Offline, you can stop and then start the ECS, and restart the OS installation process.Figure 11 Offline disk- The Installing Windows window is displayed, and the OS installation starts.
The installation takes about 50 minutes. The ECS restarts during the installation. After the ECS successfully restarts, log in to it again and configure the OS as prompted.
- diff --git a/docs/bms/image-creation-guide/en-us_topic_0000001289739500.html b/docs/bms/image-creation-guide/en-us_topic_0000001289739500.html index 63b90c8bd..972806bb3 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0000001289739500.html +++ b/docs/bms/image-creation-guide/en-us_topic_0000001289739500.html @@ -3,16 +3,16 @@ -You are required to set a password for the OS user.
-Supported special characters include !@$%^-_=+[{}]:,./?
+- The Installing Windows window is displayed, and the OS installation starts.
-The installation takes about 50 minutes. The ECS restarts during the installation. After the ECS successfully restarts, log in to it again and configure the OS as prompted.
+- You are required to set a password for the OS user.
+Supported special characters include !@$%^-_=+[{}]:,./?
Figure 12 Installation progress+
Figure 12 Installation progress- Install related drivers.
- Open Computer and double-click the CD driver.Figure 13 Starting the CD driver-
- Double-click the vmtools-windows folder.Figure 14 Opening the vmtools-windows folder-
- Double-click the Setup file.Figure 15 Executing the Setup file-
- Install drivers as prompted.Figure 16 Installing UVP VMTools for Windows-
- After the driver is installed, start Device Manager and verify that the drivers shown in the red box in the following figure are successfully installed.Figure 17 Device Manager+
- Install related drivers.
- Open Computer and double-click the CD driver.Figure 13 Starting the CD driver+
- Double-click the vmtools-windows folder.Figure 14 Opening the vmtools-windows folder+
- Double-click the Setup file.Figure 15 Executing the Setup file+
- Install drivers as prompted.Figure 16 Installing UVP VMTools for Windows+
- After the driver is installed, start Device Manager and verify that the drivers shown in the red box in the following figure are successfully installed.Figure 17 Device Manager
- Open Computer and double-click the CD driver.
Creating a Windows ECS Using the ISO Image File
-Scenarios
This section describes how to create an ECS using the registered ISO image.
+Creating a Windows ECS from an ISO Image
+-Scenarios
This section describes how to create an ECS from a registered ISO image.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Compute, click Image Management Service.
The IMS console is displayed.
++Procedure
- Access the IMS console.
- Log in to the management console.
- Under Compute, click Image Management Service.
The IMS console is displayed.
- Use an ISO image to create a Windows ECS.
- Click the Private Images tab. Locate the row that contains the ISO image and click Create ECS in the Operation column.-
If you are a DeC user, the Create ECS button in the Operation column will be unavailable for you because a DeC user cannot use an ISO image to create an ECS.
- - Configure the ECS as prompted and click OK.
- Click the Private Images tab. Locate the row that contains the ISO image and click Create ECS in the Operation column.
- Use an ISO image to create a Windows ECS.
- Click the Private Images tab. Locate the row that contains the ISO image and click Create ECS in the Operation column.
- Configure the ECS as prompted and click OK.
Follow-up Procedure
After the ECS is created, you can log in remotely to continue with OS and drivers installation.
+ - Access the IMS console.
diff --git a/docs/bms/image-creation-guide/en-us_topic_0000001341593125.html b/docs/bms/image-creation-guide/en-us_topic_0000001341593125.html index c021cee17..a9d8adfd1 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0000001341593125.html +++ b/docs/bms/image-creation-guide/en-us_topic_0000001341593125.html @@ -10,7 +10,7 @@- Registering an ISO File (Linux)
- - Creating a Linux ECS Using the ISO File
+ - Creating a Linux ECS from an ISO Image
Creating a Linux ECS Using the ISO File
-Scenarios
This section describes how to create an ECS using the registered ISO image.
+Creating a Linux ECS from an ISO Image
+-Scenarios
This section describes how to create an ECS from a registered ISO image.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Compute, click Image Management Service.
The IMS console is displayed.
++Procedure
- Access the IMS console.
- Log in to the management console.
- Under Compute, click Image Management Service.
The IMS console is displayed.
- Use an ISO image to create a Windows ECS.
- Click the Private Images tab. Locate the row that contains the ISO image and click Create ECS in the Operation column.-
If you are a DeC user, the Create ECS button in the Operation column will be unavailable for you because a DeC user cannot use an ISO image to create an ECS.
- - Configure the ECS as prompted and click OK.
- Click the Private Images tab. Locate the row that contains the ISO image and click Create ECS in the Operation column.
- Use an ISO image to create a Linux ECS.
- Click the Private Images tab. Locate the row that contains the ISO image and click Create ECS in the Operation column.
- Configure the ECS as prompted and click OK.
Follow-up Procedure
After the ECS is created, you can log in remotely to continue with OS and drivers installation.
+ - Access the IMS console.
diff --git a/docs/bms/image-creation-guide/en-us_topic_0000001341779861.html b/docs/bms/image-creation-guide/en-us_topic_0000001341779861.html index 0281ffa07..fac16257e 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0000001341779861.html +++ b/docs/bms/image-creation-guide/en-us_topic_0000001341779861.html @@ -12,7 +12,9 @@Procedure
- Access the IMS console.
- Log in to the management console.
- Under Compute, click Image Management Service.
The IMS console is displayed.
- Register an ISO file as an ISO image.
- Click Create Image in the upper right corner.
- In the Image Type and Source area, select ISO image for Type.
- In the image file list, select the bucket and then the image file.
- In the Image Information area, set the following parameters.
- Boot Mode: Select BIOS or UEFI. Ensure that the selected boot mode is the same as that in the image file, or the ECSs created from this image will not be able to boot up.
- OS: Select the OS specified in the ISO file. To ensure that the image can be created and used properly, select an OS consistent with that in the image file.
- System Disk: Set the system disk capacity (value range: 40 GB to 1024 GB), which must be no less than the size of the system disk in the image file.
- Name: Enter a name for the image to be created.
- Description: (Optional) Enter image description as needed.
- Register an ISO file as an ISO image.
- Click Create Image in the upper right corner.
- In the Image Type and Source area, select ISO image for Type.
- In the image file list, select the bucket and then the image file.
- In the Image Information area, set the following parameters.
+
- Boot Mode: Select BIOS or UEFI. Ensure that the selected boot mode is the same as that in the image file, or the ECSs created from this image will not be able to boot up.
- OS: Select the OS specified in the ISO file. To ensure that the image can be created and used properly, select an OS consistent with that in the image file.
- System Disk: Set the system disk capacity (value range: 40 GB to 1024 GB), which must be no less than the size of the system disk in the image file.
- Name: Enter a name for the image to be created.
- Enterprise Project: Select the enterprise project to which your images belong.
- Tag: (Optional) Add a tag to the image to be created.
- Description: (Optional) Enter image description as needed.
- Click Create Now.
- Confirm the settings and click Submit.
- Switch back to the Image Management Service page to monitor the image status.
When the image status changes to Normal, the image is registered successfully.
This section describes how to install the VMTools driver for an ISO file using Dism++.
Prerequisites
You have obtained an ISO file.
- The ISO image file name can contain only letters, digits, hyphens (-), and underscores (_). If the name does not meet the requirements, change it.
+ The ISO file name can contain only letters, digits, hyphens (-), and underscores (_). If the name does not meet the requirements, change it.
Procedure
- Download VMTools matching the OS and decompress it on the local PC.
- Decompress the vmtools-windows.zip file downloaded in 1 to obtain vmtools-windows.iso, and then decompress vmtools-windows.iso to obtain the vmtools-windows folder.Figure 1 vmtools-windows folderdiff --git a/docs/bms/image-creation-guide/en-us_topic_0081116558.html b/docs/bms/image-creation-guide/en-us_topic_0081116558.html index 8e6dc7209..c64652cf6 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116558.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116558.html @@ -8,7 +8,13 @@
- Click Load Driver and then Browse.
- Specify the parameters on the Install Windows page.
- Install the Windows OS.
- If the system displays a message indicating that no driver is found, go to 1.g.
- Specify the parameters on the Install Windows page.
Installing a Windows OS and the VMTools Driver
-Scenarios
This section uses Windows Server 2008 R2 64-bit as an example to describe how to install Windows on an ECS.
-The installation procedure varies depending on the image file you use. Perform operations as prompted.
- Set the time zone, KMS address, patch server, input method, and language based on service requirements.
+Scenarios
This section uses Windows Server 2008 R2 64-bit as an example to describe how to install Windows on an ECS.
+The installation procedure varies depending on the image file you use. Perform operations as prompted.
+ Set the time zone, KMS address, patch server, input method, and language based on service requirements.
Prerequisites
You have remotely logged in to the ECS and entered the installation page.
+Prerequisites
You have remotely logged in to the ECS and entered the installation page.
Procedure
Do not stop or restart the ECS during the OS installation. Otherwise, the OS installation will fail.
+Procedure
Do not stop or restart the ECS during the OS installation. Otherwise, the OS installation will fail.
2022-10-30
+2023-02-28
+This issue is the seventeenth official release.
+Deleted XenServer from Installing a Linux OS on the VM.
+2022-10-30
This issue is the sixteenth official release.
Modified the following content:
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116559.html b/docs/bms/image-creation-guide/en-us_topic_0081116559.html index 52ab4ebe4..039be1e5d 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116559.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116559.html @@ -52,9 +52,7 @@ -Procedure
-- Enter the directory where the bms-network-config software package is stored and run the rpm -ivhbms-network-config-1.0-7.centosRedhat7.x86_64.rpm command.
[root@localhost r74]# rpm -ivhbms-network-config-1.0-7.centosRedhat7.x86_64.rpm +
-Procedure
- Enter the directory where the bms-network-config software package is stored and run the rpm -ivhbms-network-config-1.0-7.centosRedhat7.x86_64.rpm command.
[root@localhost r74]# rpm -ivhbms-network-config-1.0-7.centosRedhat7.x86_64.rpm Preparing... ############################### [100%] Updating / installing... 1:bms-network-config-1.0.7.centosRe############################### [100%]@@ -102,8 +100,6 @@ WantedBy=multi-user.targetIf the startup sequence is incorrect, use the vim /usr/lib/systemd/system/bms-network-config.service command to correct it.
Procedure (XenServer)
- Extract xenserver-bms-config.zip from bms-network-config.
- Create the /opt/huawei directory and put GetVpcNicMac.sh, unique-uuid-config.sh, and xenserver-bms-network-config.sh in this directory. Run the chmod +x Script name command to make these scripts executable.
- Put the xenserverInit.service file in the /usr/lib/systemd/system/ directory and run the systemctl daemon-reload command to update system services.
- Enter the directory where the bms-network-config software package is stored and run the rpm -ivhbms-network-config-1.0-7.centosRedhat7.x86_64.rpm command.
-
-
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116597.html b/docs/bms/image-creation-guide/en-us_topic_0081116597.html index 4bda5cb92..63823ba6c 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116597.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116597.html @@ -14,8 +14,6 @@
-
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116632.html b/docs/bms/image-creation-guide/en-us_topic_0081116632.html index 1b9928102..9abd944f1 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116632.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116632.html @@ -1,6 +1,6 @@ -
SUSE 12 SP2/SUSE 12 SP3/SUSE 15/Oracle Linux 7/Red Hat 7/CentOS 7/CentOS 8/XenServer 7
+SUSE 12 SP2/SUSE 12 SP3/SUSE 15/Oracle Linux 7/Red Hat 7/CentOS 7/CentOS 8
- Check whether the Cloud-init services will automatically start when the system starts.
systemctl status cloud-init-local
systemctl status cloud-init
systemctl status cloud-config
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116681.html b/docs/bms/image-creation-guide/en-us_topic_0081116681.html index 2df408564..42c87e0d3 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116681.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116681.html @@ -8,7 +8,7 @@ - SUSE 12 SP1
- - SUSE 12 SP2/SUSE 12 SP3/SUSE 15/Oracle Linux 7/Red Hat 7/CentOS 7/CentOS 8/XenServer 7
+ - SUSE 12 SP2/SUSE 12 SP3/SUSE 15/Oracle Linux 7/Red Hat 7/CentOS 7/CentOS 8
- EulerOS/OpenEuler
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116685.html b/docs/bms/image-creation-guide/en-us_topic_0081116685.html
index fcc6a4a6c..7d9796b87 100644
--- a/docs/bms/image-creation-guide/en-us_topic_0081116685.html
+++ b/docs/bms/image-creation-guide/en-us_topic_0081116685.html
@@ -5,7 +5,7 @@
Prerequisites
You have logged in to the VM.
Procedure
- Add or modify the configuration file.
- For Red Hat/Oracle Linux/EulerOS/OpenEuler/SUSE 12/SUSE 15/CentOS/XenServer, use the vi editor to open the /etc/dracut.conf file and change or add the value of add_drivers. In the following example, the value of add_drivers is a list of RAID drivers.
logfile=/var/log/dracut.log +
-Procedure
- Add or modify the configuration file.
- For Red Hat/Oracle Linux/EulerOS/OpenEuler/SUSE 12/SUSE 15/CentOS, use the vi editor to open the /etc/dracut.conf file and change or add the value of add_drivers. In the following example, the value of add_drivers is a list of RAID drivers.
logfile=/var/log/dracut.log # fileloglvl=7 ... ... @@ -44,8 +44,8 @@ INITRD_MODULES="
You can enter multiple RAID drivers and separate them with spaces. The RAID driver names can be obtained from the purchased hardware devices. Multiple types of drivers can be added at the same time, such as mpt3sas, mpt2sas, and megaraid_sas. If any hardware driver cannot be installed here, you can install it after the BMS is created.
- For Red Hat/Oracle Linux/EulerOS/OpenEuler/SUSE 12/SUSE 15/CentOS, use the vi editor to open the /etc/dracut.conf file and change or add the value of add_drivers. In the following example, the value of add_drivers is a list of RAID drivers.
- Add or modify the configuration file.
- Update the kernel. For Ubuntu 16.04 ARM and Ubuntu 18.04 ARM, skip this step.
For Rad Hat/Oracle Linux/EulerOS/SUSE 12/SUSE 15/Ubuntu 16.04/Ubuntu 18.04/CentOS/XenServer run the dracut -f command.
-- For Rad Hat/Oracle Linux/EulerOS/OpenEuler/CentOS/XenServer, run the dracut -f command. Wait for several seconds. If no command output is returned, the drivers have been loaded.
- For SUSE 12 SP1, run the dracut -f command. Check the command output in the last few lines. If message "Some kernel modules could not be included. This is not necessarily an error:" is displayed and drivers not loaded are displayed (excluding the RAID drivers), the RAID drivers are loaded successfully.
... +
- Update the kernel. For Ubuntu 16.04 ARM and Ubuntu 18.04 ARM, skip this step.
For Rad Hat/Oracle Linux/EulerOS/SUSE 12/SUSE 15/Ubuntu 16.04/Ubuntu 18.04/CentOS run the dracut -f command.
+- For Rad Hat/Oracle Linux/EulerOS/OpenEuler/CentOS, run the dracut -f command. Wait for several seconds. If no command output is returned, the drivers have been loaded.
- For SUSE 12 SP1, run the dracut -f command. Check the command output in the last few lines. If message "Some kernel modules could not be included. This is not necessarily an error:" is displayed and drivers not loaded are displayed (excluding the RAID drivers), the RAID drivers are loaded successfully.
... Some kernel modules could not be included This is not necessarily an error: pcmcia @@ -68,12 +68,12 @@ Some kernel modules could not be included
If some disk partitions do not have UUIDs, check whether the VM OS is properly installed. If it is not, install it again.
- Use the vi editor to open the /boot/grub/menu.lst file, modify the OS boot parameters, and save the configuration.
Original menu.lst file
-
Modified menu.lst file
+Modified menu.lst file
-
- Use the vi editor to open the /boot/grub/device.map file.
Original device.map file
+ - Use the vi editor to open the /boot/grub/device.map file.
Original device.map file
(hd0) /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001 ~
-Modified device.map file
+Modified device.map file
(hd0) /dev/sda
- Use the vi editor to open the /etc/fstab file.
Original fstab file
@@ -91,7 +91,7 @@ Some kernel modules could not be included
If SUSE 11 SP4 uses LVM, replace the virtual disks in the VM file with the actual physical disks.
- In the /boot/grub directory of the VM, run the blkid command to check whether disk partitions are normal.
If some disk partitions do not have UUIDs, check whether the VM OS is properly installed. If it is not, install it again.
- - Use the vi editor to open the /boot/grub/menu.lst file, modify the OS boot parameters, and save the configuration.
Original menu.lst file
+ - Use the vi editor to open the /boot/grub/menu.lst file, modify the OS boot parameters, and save the configuration.
Original menu.lst file
Modified menu.lst file
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116736.html b/docs/bms/image-creation-guide/en-us_topic_0081116736.html index 52546d469..48ac3c7b8 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116736.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116736.html @@ -1,7 +1,7 @@
Installing the SDI Driver
-Scenario
Currently, there are three types of SDI cards: SDI storage cards, SDI 2.2 (network cards), and SDI 3.0 (integrated storage and network cards). If the BMS uses SDI storage cards (neither SDI 2.2 nor SDI 3.0), the SDI driver needs to be installed on the VM so that EVS disks can be attached to the BMS. In other cases, skip this section. Currently, ARM 64, XenServer, and ESXi VMs do not support SDI cards. You do not need to install the SDI driver on such VMs.
+Scenario
Currently, there are three types of SDI cards: SDI storage cards, SDI 2.2 (network cards), and SDI 3.0 (integrated storage and network cards). If the BMS uses SDI storage cards (neither SDI 2.2 nor SDI 3.0), the SDI driver needs to be installed on the VM so that EVS disks can be attached to the BMS. In other cases, skip this section. Currently, ARM 64 VMs do not support SDI cards. You do not need to install the SDI driver on such VMs.
Prerequisites
- You have logged in to the VM.
- You have downloaded the SDI driver (scsi_ep_front) as instructed in Software and have uploaded it to the VM.diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116754.html b/docs/bms/image-creation-guide/en-us_topic_0081116754.html index 8dfa884ff..07dd8cde2 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116754.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116754.html @@ -212,13 +212,6 @@
The scsi_ep_front version must be 1.0.13 or later.
3.13.0-24-generic
- In the /boot/grub directory of the VM, run the blkid command to check whether disk partitions are normal.
- For Red Hat/Oracle Linux/EulerOS/OpenEuler/SUSE 12/SUSE 15/CentOS/XenServer, use the vi editor to open the /etc/dracut.conf file and change or add the value of add_drivers. In the following example, the value of add_drivers is a list of RAID drivers.
XenServer
-XenServer 7.1 64bit
-4.4.x86_64
-Debian
Debian 8.6 64bit
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116771.html b/docs/bms/image-creation-guide/en-us_topic_0081116771.html index 7d107b1aa..890e37cef 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116771.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116771.html @@ -33,13 +33,13 @@SDI driver
With the SDI driver, EVS disks can be attached to BMSs. The EVS disks can be used as system disks from which the BMSs are booted. This facilitates quick BMS provisioning.
-This software package is only required by images with SDI 2.2 and SDI 3.0 cards installed.
+This software package is only required by images with SDI cards installed (exclude SDI 2.2 and SDI 3.0).
Linux:
-Visit https://support.huawei.com/enterprise/en/intelligent-accelerator-components/sd100-pid-22040214/software/253495955?idAbsPath=fixnode01%7C23710424%7C251364409%7C21782478%7C22040214, download SD100-2.0.2.SPC15-DRIVER.zip, and decompress it. Obtain the driver package based on the OS type. For example, the driver package for CentOS 7.6 is kmod-scsi_ep_front-centos_7.6_1.0.18-3.10.0_957.el7.centos.x86_64.rpm.
+Visit https://support.huawei.com/enterprise/en/intelligent-accelerator-components/sd100-pid-22040214/software/253495955?idAbsPath=fixnode01%7C23710424%7C251364409%7C21782478%7C22040214, download SD100-2.0.2.SPC15-DRIVER.zip, and decompress it. Obtain the driver package based on the OS type. For example, the driver package for CentOS 7.6 is kmod-scsi_ep_front-centos_7.6_1.0.18-3.10.0_957.el7.centos.x86_64.rpm.
Windows (Windows 2016 as an example):
-Visit https://support.huawei.com/enterprise/en/intelligent-accelerator-components/sd100-pid-22040214/software/250607152?idAbsPath=fixnode01%7C23710424%7C251364409%7C21782478%7C22040214, download SD100-2.0.2.SPC11-DRIVER-V010.zip, and decompress it. For example, the driver package for Windows Server 2016 is sdidriver_win-2016-installpack.zip.
+Visit https://support.huawei.com/enterprise/en/intelligent-accelerator-components/sd100-pid-22040214/software/250607152?idAbsPath=fixnode01%7C23710424%7C251364409%7C21782478%7C22040214, download SD100-2.0.2.SPC11-DRIVER-V010.zip, and decompress it. For example, the driver package for Windows Server 2016 is sdidriver_win-2016-installpack.zip.
Huawei
This driver needs to be installed for centralized BMSs with Hi1822 NICs.
Visit https://support.huawei.com/enterprise/en/management-software/fusionserver-idriver-pid-21588909/software/. Click the recommended or latest version. Download FusionServer iDriver-xxx-Driver-xxx.zip based on the image OS type to obtain the Hi1822 driver packages.
+Visit https://support.huawei.com/enterprise/en/management-software/fusionserver-idriver-pid-21588909/software/. Click the recommended or latest version. Download FusionServer iDriver-xxx-Driver-xxx.zip based on the image OS type to obtain the Hi1822 driver packages.
Example:
Click FusionServer iDriver 3.0.34, select CentOS, and download FusionServer iDriver-CentOS7.6-Driver-V116.zip. Decompress the package to obtain onboard_driver_CentOS7.6.iso and then decompress the .iso package to obtain the NIC-Hi1822-CentOS7.6-hinic-3.9.0.8-1-x86_64.rpm and NIC-Hi1822-CentOS7.6-hinicadm-3.9.0.8-1-x86_64.rpm driver packages.
This driver needs to be installed for distributed BMSs with SDI 2.2 offload cards.
Visit https://support.huawei.com/carrier/navi?coltype=software#allProduct=true&col=software&path=PBI1-21430725/PBI1-23710112/PBI1-23710137/PBI1-22346033. Click the latest version. Download Hi1822_BM_X86_xxx.tar.gz to obtain the driver package based on the image OS type.
-Example:
-Click Bare Metal Server 20.6.101. Download Hi1822_BM_X86_1.19.3.B036.tar.gz. Decompress it to obtain the kmod-hinic-1.8.3.16_3.10.0_693-1.el7.centos.x86_64.rpm driver package.
+- Visit https://support.huawei.com, search for Hi1822_BM_X86_xxx.tar.gz (xxx indicates the package version), download the package of the latest version, and decompress it.
- In the decompressed folder, obtain the driver package based on the image OS type.
Huawei
This driver needs to be installed for distributed BMSs with SDI 3.0 offload cards.
Visit https://support.huawei.com/carrier/navi?coltype=software#allProduct=true&col=software&path=PBI1-21430725/PBI1-23710112/PBI1-23710137/PBI1-22720245. Click the latest version. Download uNIC_GuestOS_Driver_BM_xxx.tar.gz to obtain the driver package based on the image OS type.
-For example, to obtain the driver package for CentOS7.6:
-Click IaaS OpenStack 21.8.8. Download uNIC_GuestOS_Driver_BM_2.21.8.B070.tar.gz. Decompress it to obtain the kmod-hinic-5.0.0.7_3.10.0_957-1.el7.x86_64.rpm driver package.
+- Visit https://support.huawei.com, search for uNIC_GuestOS_Driver_BM_xxx.tar.gz (xxx indicates the package version), download the package of the latest version, and decompress it.
- In the decompressed folder, obtain the driver package based on the image OS type.
Huawei
Command output:
tigervnc-server-1.1.0-5.e16.x86_64
- If no command output is displayed or the command output shows that VNC Server is not installed, go to 2.
- If the command output shows that VNC Server has been installed, go to 3.
- Run the lsblk command (the OS ISO file must have been mounted to the BMC virtual CD-ROM drive. If not, mount the ISO file in the same way as you mount it during OS installation).
- Locate the block device whose name is sr0 and type is rom, and check whether any directories are mounted to the mount point. If no, run the following command:
mount /dev/sr0 /mnt
+ - (Optional) Install tigervnc-server.
- Run the lsblk command (the OS ISO file must have been mounted to the BMC virtual CD-ROM drive. If not, mount the ISO file in the same way as you mount it during OS installation).+
If you cannot log in to or perform operations on BMC, contact O&M administrators.
+ - Locate the block device whose name is sr0 and type is rom, and check whether any directories are mounted to the mount point. If no, run the following command:
mount /dev/sr0 /mnt
- Enter the /etc/yum.repos.d directory where the configuration is stored and back up all .repo files. Use vim to create a .repo file, for example tiger.repo. The file content is as follows:
[rhel-local] baseurl=file:///mnt enabled=1 diff --git a/docs/bms/image-creation-guide/en-us_topic_0081250916.html b/docs/bms/image-creation-guide/en-us_topic_0081250916.html index 293019755..068a8500e 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081250916.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081250916.html @@ -3,7 +3,7 @@
What Can I Do If Data Cannot Be Injected into BMSs Due to cloud-init-local Failures?
-Symptom
For Red Hat 7 or CentOS 7, cloud-init-local may fail to start up. As a result, BMS failed to inject data correctly. When you run the systemctl status cloud-init-local.service command, the message "OSError: [Errno 2] No such file or directory" is displayed.
Solution
For Red Hat 7 and CentOS 7, if the libselinux version is earlier than 2.5.7, cloud-init-local may fail to start up. This is a known issue and has been fixed in libselinux 2.5.7. For details, see https://bugzilla.redhat.com/show_bug.cgi?id=1406520. If you are creating a Red Hat 7 or CentOS 7 image, upgrade libselinux to 2.5.7 or later after you configure the yum source in XenServer.
+Solution
For Red Hat 7 and CentOS 7, if the libselinux version is earlier than 2.5.7, cloud-init-local may fail to start up. This is a known issue and has been fixed in libselinux 2.5.7. For details, see https://bugzilla.redhat.com/show_bug.cgi?id=1406520. If you are creating a Red Hat 7 or CentOS 7 image, upgrade libselinux to 2.5.7 or later after you configure the yum source in section "Installing Cloud-Init > SUSE/Red Hat/CentOS/Oracle Linux/Ubuntu/Debian > CentOS".
diff --git a/docs/bms/image-creation-guide/en-us_topic_0100489884.html b/docs/bms/image-creation-guide/en-us_topic_0100489884.html index 936575530..5e338013f 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0100489884.html +++ b/docs/bms/image-creation-guide/en-us_topic_0100489884.html @@ -6,8 +6,6 @@- Overview
- - XenServer
- - SUSE/Red Hat/CentOS/Oracle Linux/Ubuntu/Debian
- EulerOS/OpenEuler
diff --git a/docs/bms/image-creation-guide/en-us_topic_0100489885.html b/docs/bms/image-creation-guide/en-us_topic_0100489885.html deleted file mode 100644 index 5e1d8bf18..000000000 --- a/docs/bms/image-creation-guide/en-us_topic_0100489885.html +++ /dev/null @@ -1,24 +0,0 @@ - - -XenServer
--- Before configuring the yum source on the VM, back up files in the /etc/yum.repos.d directory. Perform the following operations to back up the default source:
- Open the directory and run the cd /etc/yum.repos.d command.
- Run the ll -h command to check the repo files in the directory.
If no repo file exists, no further action is required.
- - Run the mv /etc/yum.repos.d/xxx.repo /etc/yum.repos.d/xxx.repo.backup command to back up all repo files.
xxx is a file name.
-
- Run the following command to copy the yum source to the /etc/yum.repos.d directory:
wget -O /etc/yum.repos.d/CentOS7.repo Image source address
-Alternatively, run the following command:
-curl -o /etc/yum.repos.d/CentOS7.repo Image source address
- - Run yum repolist command to update the yum repository.
The access may fail (for example, "404 Not Found" is displayed).
-If this problem occurs, use the vi or vim editor to change the value of $releasever following baseurl to 7 in the /etc/yum.repos.d/CentOS7.repo file .
- -Run the yum repolist command again to update the yum repository.
- - Run the following command to install Cloud-Init: -
- Run the following command to check the Cloud-Init version:
-
If the Cloud-Init version is displayed, the installation is successful.
-
-- diff --git a/docs/bms/image-creation-guide/en-us_topic_0100489888.html b/docs/bms/image-creation-guide/en-us_topic_0100489888.html index 86d29abc5..d394546c0 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0100489888.html +++ b/docs/bms/image-creation-guide/en-us_topic_0100489888.html @@ -1,7 +1,7 @@--Parent topic: Installing Cloud-Init-EulerOS/OpenEuler
-- Use EulerOS2.2 as an example. Configure the yum source of EulerOS2.2 by editing the /etc/yum.repos.d/EulerOS-base.repo file. For example, the configuration is:
[EulerOS-base] +
- Use EulerOS2.2 as an example. Configure the yum source of EulerOS2.2 by editing the /etc/yum.repos.d/EulerOS-base.repo file. For example, the configuration is:
[EulerOS-base] name=EulerOS-base baseurl=https://repo.huaweicloud.com/euler/2.2/os/x86_64/ enabled=1 diff --git a/docs/bms/image-creation-guide/en-us_topic_0100601386.html b/docs/bms/image-creation-guide/en-us_topic_0100601386.html index 161d32df5..6e4bae95f 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0100601386.html +++ b/docs/bms/image-creation-guide/en-us_topic_0100601386.html @@ -1,7 +1,9 @@
What Do I Do If Cloudbase-Init Is Stopped on a Provisioned Windows BMS?
-Symptom
If Cloudbase-Init is stopped after a Windows BMS is provisioned, and information "Failed to find trace ID description from Cloudbase-Init because the component triggering the trace is not installed or has been damaged. You can install or recover the component." is displayed, you need to reinstall Cloudbase-Init.
++ If you cannot log in to or perform operations on BMC, contact O&M administrators.
+Symptom
If Cloudbase-Init is stopped after a Windows BMS is provisioned, and information "Failed to find trace ID description from Cloudbase-Init because the component triggering the trace is not installed or has been damaged. You can install or recover the component." is displayed, you need to reinstall Cloudbase-Init.
diff --git a/docs/bms/image-creation-guide/en-us_topic_0131700230.html b/docs/bms/image-creation-guide/en-us_topic_0131700230.html index fdd0c92a8..8292436de 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0131700230.html +++ b/docs/bms/image-creation-guide/en-us_topic_0131700230.html @@ -5,10 +5,9 @@Solution
- Log in to the BMS using BMC and back up the .conf files in the C:\Program Files\Cloudbase Solutions\Cloudbase-Init\ directory and all the files in the LocalScripts directory.
- Download Cloudbase-Init from the official website.
- Click Remote Control on the BMC host management page.
The remote control window is displayed.
diff --git a/docs/bms/image-creation-guide/en-us_topic_0108488467.html b/docs/bms/image-creation-guide/en-us_topic_0108488467.html index a4b2e1472..f27f578ac 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0108488467.html +++ b/docs/bms/image-creation-guide/en-us_topic_0108488467.html @@ -22,7 +22,7 @@ groups=Administrators - Add parameter plugins and configure the modules to be loaded. Separate different modules with commas (,). The information in bold is the keyword of each module.The following is an example of the Cloudbase-Init file content:
plugins=cloudbaseinit.plugins.common.localscripts.LocalScriptsPlugin,cloudbaseinit.plugins.common.mtu.MTUPlugin,cloudbaseinit.plugins.windows.createuser.CreateUserPlugin,cloudbaseinit.plugins.common.setuserpassword.SetUserPasswordPlugin,cloudbaseinit.plugins.common.sshpublickeys.SetUserSSHPublicKeysPlugin,cloudbaseinit.plugins.common.sethostname.SetHostNamePlugin,cloudbaseinit.plugins.windows.extendvolumes.ExtendVolumesPlugin,cloudbaseinit.plugins.common.userdata.UserDataPlugin,cloudbaseinit.plugins.windows.winrmlistener.ConfigWinRMListenerPlugin,cloudbaseinit.plugins.windows.winrmcertificateauth.ConfigWinRMCertificateAuthPlugin,cloudbaseinit.plugins.windows.licensing.WindowsLicensingPlugin
Functions of the modules are as follows:
-- LocalScriptsPlugin: sets the scripts.
- MTUPlugin: sets the MTU network ports.
- CreateUserPlugin: creates a user.
- SetUserPasswordPlugin: sets the password.
- SetUserSSHPublicKeysPlugin: sets the private key.
- SetHostNamePlugin: sets the hostname.
- ExtendVolumesPlugin: partitions the disks.
- UserDataPlugin: injects user data.
- ConfigWinRMListenerPlugin: sets listening to remote login.
- ConfigWinRMCertificateAuthPlugin: sets remote login without the password authentication.
- WindowsLicensingPlugin: activates Windows instances.
- LocalScriptsPlugin: sets the scripts.
- MTUPlugin: sets the MTU network ports.
- CreateUserPlugin: creates a user.
- SetUserPasswordPlugin: sets the password.
- SetUserSSHPublicKeysPlugin: sets the private key.
- SetHostNamePlugin: sets the hostname.
- ExtendVolumesPlugin: partitions the disks.
- UserDataPlugin: injects user data.
- ConfigWinRMListenerPlugin: sets listening to remote login.
- ConfigWinRMCertificateAuthPlugin: sets remote login without the password authentication.
- WindowsLicensingPlugin: activates Windows instances.
Making Preparations
- Determine the .zip driver packages to be used.
-
- CentOS 7.6: FusionServer iDriver-CentOS7.6-Driver-V116.zip
- RHEL 7.3: FusionServer iDriver-RHEL7.3-Driver-V116.zip
- Ubuntu 16.04: FusionServer iDriver-Ubuntu16.04-Driver-V116.zip
- XenServer 7.1: FusionServer iDriver-Citrix7.1-Driver-V109.zip
- EulerOS 2.8 ARM: TaiShanServer iDriver-EulerOS2.8-Driver-V103.zip
- CentOS 7.6 ARM: TaiShanServer iDriver-CentOS7.6-Driver-V112.zip
- Obtain the installation packages. (Examples for installing V5 server drivers: CentOS 7.6 and XenServer 7.1; examples for installing TaiShan server drivers: EulerOS 2.8 ARM and CentOS 7.6 ARM)
- CentOS 7.6
Download and decompress the FusionServer iDriver-CentOS7.6-Driver-V116.zip driver package to obtain the onboard_driver_CentOS7.6.iso file. Decompress onboard_driver_CentOS7.6.iso to obtain the NIC-X710_X722_XL710_XXV710-CentOS7.6-i40e-2.15.9-1-x86_64.rpm, RAID-3008IR_3008IT_3408IT_3416IT-CentOS7.6-mpt3sas-27.00.00.00-1-x86_64.rpm, and RAID-3004iMR_3108_3408iMR_3416iMR_3508_3516-CentOS7.6-megaraid_sas-07.716.01.00-1-x86_64.rpm files.
+- CentOS 7.6: FusionServer iDriver-CentOS7.6-Driver-V116.zip
- RHEL 7.3: FusionServer iDriver-RHEL7.3-Driver-V116.zip
- Ubuntu 16.04: FusionServer iDriver-Ubuntu16.04-Driver-V116.zip
- EulerOS 2.8 ARM: TaiShanServer iDriver-EulerOS2.8-Driver-V103.zip
- CentOS 7.6 ARM: TaiShanServer iDriver-CentOS7.6-Driver-V112.zip
- Obtain the installation packages. (Example for installing V5 server drivers: CentOS 7.6; examples for installing TaiShan server drivers: EulerOS 2.8 ARM and CentOS 7.6 ARM)
- CentOS 7.6
Download and decompress the FusionServer iDriver-CentOS7.6-Driver-V116.zip driver package to obtain the onboard_driver_CentOS7.6.iso file. Decompress onboard_driver_CentOS7.6.iso to obtain the NIC-X710_X722_XL710_XXV710-CentOS7.6-i40e-2.15.9-1-x86_64.rpm, RAID-3008IR_3008IT_3408IT_3416IT-CentOS7.6-mpt3sas-27.00.00.00-1-x86_64.rpm, and RAID-3004iMR_3108_3408iMR_3416iMR_3508_3516-CentOS7.6-megaraid_sas-07.716.01.00-1-x86_64.rpm files.
The NIC-X710_X722_XL710_XXV710-CentOS7.6-i40e-2.15.9-1-x86_64.rpm, RAID-3008IR_3008IT_3408IT_3416IT-CentOS7.6-mpt3sas-27.00.00.00-1-x86_64.rpm, and RAID-3004iMR_3108_3408iMR_3416iMR_3508_3516-CentOS7.6-megaraid_sas-07.716.01.00-1-x86_64.rpm files are used to install LOM drivers, mpt3 drivers, and megaraid_sas drivers of V5 servers, respectively.
- - XenServer 7.1
Download and decompress the FusionServer iDriver-Citrix7.1-Driver-V109.zip driver package to obtain onboard_driver_Citrix7.1.iso and NIC-X710_X722_XL710-Citrix7.1-i40e-2.0.23-1-x86_64.iso. Decompress onboard_driver_Citrix7.1.iso to obtain the RAID-3004iMR_3108_3408iMR_3416iMR_3508_3516-Citrix7.1-megaraid_sas-07.716.01.00-1-x86_64.rpm file. Decompress the NIC-X710_X722_XL710-Citrix7.1-i40e-2.0.23-1-x86_64.iso package and obtain the intel-i40e-2.0.23-1.x86_64.rpm package from the Packages directory. The intel-i40e-2.0.23-1.x86_64.rpm package is used to install megaraid_sas and LOM drivers.
- EulerOS 2.8 ARM
Download and decompress the TaiShanServer iDriver-EulerOS2.8-Driver-V103.zip driver package to obtain onboard_driver_EulerOS2.8.iso. Decompress onboard_driver_EulerOS2.8.iso to obtain NIC-IN200-EulerOS2.8-hinic-2.4.1.0-aarch64.rpm, which is used to install the Hi1822 standard card driver. However, the Hi1822 driver has been installed in Installing the Hi1822 Driver. Therefore, you can skip this step.
- CentOS 7.6 ARM
Download and decompress the TaiShanServer iDriver-CentOS7.6-Driver-V112.zip driver package to obtain onboard_driver_CentOS7.6.iso. Decompress the onboard_driver_CentOS7.6.iso file to obtain the RAID-3108_3408iMR_3416iMR_3508_3516-CentOS7.6-megaraid_sas-07.716.01.00-aarch64.rpm and NIC-Hi1822-CentOS7.6-hinic-3.9.0.8-aarch64.rpm files for installing the megaraid_sas and Hi1822 drivers. The Hi1822 (hinic) driver has been installed in Installing the Hi1822 Driver. Therefore, you do not need to install it again.
Overview
-You can install growpart to automatically extend the root partition. For SUSE, growpart is installed by default. However, for SUSE 11 SP4, you need to install growpart with an earlier version to replace the default one. For other SUSE distributions, you do not need to install growpart. For Ubuntu, growpart is installed by default and the version meets requirements. Therefore, you do not need to install growpart. For XenServer, partitions can be selected during the OS installation. Therefore, automatic root partition extension is not supported.
+diff --git a/docs/bms/image-creation-guide/en-us_topic_0151001259.html b/docs/bms/image-creation-guide/en-us_topic_0151001259.html deleted file mode 100644 index 71aa74ee6..000000000 --- a/docs/bms/image-creation-guide/en-us_topic_0151001259.html +++ /dev/null @@ -1,22 +0,0 @@ - - - - - -You can install growpart to automatically extend the root partition. For SUSE, growpart is installed by default. However, for SUSE 11 SP4, you need to install growpart with an earlier version to replace the default one. For other SUSE distributions, you do not need to install growpart. For Ubuntu, growpart is installed by default and the version meets requirements. Therefore, you do not need to install growpart.
If the boot mode is UEFI (for example, it is UEFI for Arm), run the yum install gdisk command to install gdisk.
XenServer 7.1
--When you configure the storage during XenServer installation, select the item shown in the red box in the following figure. In addition, this OS does not support automatic disk capacity. You are advised to set the system disk capacity to around 100 GB to ensure sufficient root partition capacity after the VM is provisioned. Configure other parameters as needed.
-
-
-- - - \ No newline at end of file diff --git a/docs/bms/image-creation-guide/en-us_topic_0151001260.html b/docs/bms/image-creation-guide/en-us_topic_0151001260.html deleted file mode 100644 index e712c1b6b..000000000 --- a/docs/bms/image-creation-guide/en-us_topic_0151001260.html +++ /dev/null @@ -1,22 +0,0 @@ - - - - - ---Parent topic: Installing a Linux OS on the VM-x86: XenServer 7.1
--- Use the vi editor to open the /boot/grub/grub.cfg file and add console=ttyS0 after the XenServer startup parameter console=tty0.
-
- To enable user root to log in to the BMS through a serial port, add ttyS0 to the end of the security configuration file /etc/securetty.
-- - - \ No newline at end of file diff --git a/docs/bms/image-creation-guide/public_sys-resources/icon-arrowdn.gif b/docs/bms/image-creation-guide/public_sys-resources/icon-arrowdn.gif index 84eec9be2..379428032 100644 Binary files a/docs/bms/image-creation-guide/public_sys-resources/icon-arrowdn.gif and b/docs/bms/image-creation-guide/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/bms/image-creation-guide/public_sys-resources/icon-arrowrt.gif b/docs/bms/image-creation-guide/public_sys-resources/icon-arrowrt.gif index 39583d168..6aaaa11c2 100644 Binary files a/docs/bms/image-creation-guide/public_sys-resources/icon-arrowrt.gif and b/docs/bms/image-creation-guide/public_sys-resources/icon-arrowrt.gif differ--Parent topic: Configuring Remote Login to a BMS- - CentOS 7.6
- CentOS 7.6
- Use EulerOS2.2 as an example. Configure the yum source of EulerOS2.2 by editing the /etc/yum.repos.d/EulerOS-base.repo file. For example, the configuration is:
- Before configuring the yum source on the VM, back up files in the /etc/yum.repos.d directory. Perform the following operations to back up the default source:
- Overview
- Run the lsblk command (the OS ISO file must have been mounted to the BMC virtual CD-ROM drive. If not, mount the ISO file in the same way as you mount it during OS installation).