diff --git a/docs/bms/umn/en-us_topic_0083745259.html b/docs/bms/umn/en-us_topic_0083745259.html
index f78d1b87..16d35f55 100644
--- a/docs/bms/umn/en-us_topic_0083745259.html
+++ b/docs/bms/umn/en-us_topic_0083745259.html
@@ -11,7 +11,7 @@
Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
-
Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
+
Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
diff --git a/docs/bms/umn/en-us_topic_0083745260.html b/docs/bms/umn/en-us_topic_0083745260.html
index 3a727dc3..b3c0eef5 100644
--- a/docs/bms/umn/en-us_topic_0083745260.html
+++ b/docs/bms/umn/en-us_topic_0083745260.html
@@ -9,7 +9,7 @@
EVS Disk Performance
The key indicators of EVS disk performance include read/write latency, IOPS, and throughput.
- IOPS: number of read/write operations performed by an EVS disk per second
- Throughput: amount of data successfully transmitted by an EVS disk per second, that is, the amount of data read from and written into an EVS disk
- Read/write latency: minimum interval between two consecutive read/write operations of an EVS disk
-
For more details, see Elastic Volume Service User Guide.
+
For more details, see Elastic Volume Service User Guide.
EVS Disk Device Types
BMS supports only Small Computer System Interface (SCSI) EVS disks.
On the management console, you can create EVS disks with Device Type set to SCSI. The EVS disks support transparent SCSI command transmission, allowing BMS OSs to directly access underlying storage media. The EVS disks support basic read/write SCSI commands and advanced SCSI commands.
diff --git a/docs/bms/umn/en-us_topic_0084461768.html b/docs/bms/umn/en-us_topic_0084461768.html
index b324cab6..2fa5f596 100644
--- a/docs/bms/umn/en-us_topic_0084461768.html
+++ b/docs/bms/umn/en-us_topic_0084461768.html
@@ -63,7 +63,7 @@
Percentage of time that the CPU is used by kernel space
Check the metric value changes in the /proc/stat file in a collection period.
-Run the top command to check the %Cpu(s) sy value.
+Run the top command to check the %Cpu(s) sy value.
Unit: percent
|
0-100%
@@ -382,7 +382,7 @@
| (Agent) Used Disk Space
|
Used disk space of the monitored object
-Run the df -h command to check the data in the Used column.
+Run the df -h command to check the data in the Used column.
The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~).
Unit: GB
|
@@ -706,7 +706,7 @@
Check metric value changes in the /proc/net/dev file in a collection period.
Unit: bit/s
-
≥ 0 bit/s
+ | ≥ 0 bits/s
|
BMS
|
@@ -721,7 +721,7 @@
Check metric value changes in the /proc/net/dev file in a collection period.
Unit: bit/s
-
≥ 0 bit/s
+ | ≥ 0 bits/s
|
BMS
|
diff --git a/docs/bms/umn/en-us_topic_0084807532.html b/docs/bms/umn/en-us_topic_0084807532.html
index 719912fd..2bca51f5 100644
--- a/docs/bms/umn/en-us_topic_0084807532.html
+++ b/docs/bms/umn/en-us_topic_0084807532.html
@@ -3,7 +3,7 @@
Creating a Private Image from a BMS
Scenarios
You can create a private image from a BMS and copy the system disk data of the BMS to the private image. The system disk contains an OS and pre-installed applications for running services.
-
Constraints
- This operation is supported only when the system disk is an EVS disk.
- Data disks of a BMS cannot be exported as images.
- The BMS must be stopped.
- This operation depends on the bms-network-config and Cloud-Init plug-ins in the BMS image.
- If the BMS is created using a public image, the image has the bms-network-config and Cloud-Init plug-ins by default.
- If the BMS is created using a private image, check whether bms-network-config and Cloud-Init are installed by following the instructions in Bare Metal Server Private Image Creation Guide.
+Constraints
- Currently, only a BMS that supports quick provisioning (the OS is installed on an EVS disk) can be used to create a private image.
- Data disks of a BMS cannot be exported as images.
- The BMS must be stopped.
- This operation depends on the bms-network-config and Cloud-Init plug-ins in the BMS image.
- If the BMS is created using a public image, the image has the bms-network-config and Cloud-Init plug-ins by default.
- If the BMS is created using a private image, check whether bms-network-config and Cloud-Init are installed by following the instructions in Bare Metal Server Private Image Creation Guide.
Precautions
- Delete sensitive data from the BMS before using it to creating a private image to prevent data leak.
- Delete residual files from the OS. For details, see "Deleting Files" in Bare Metal Server Private Image Creation Guide.
- During the image creation process, do not change the BMS status. Otherwise, the image will fail to be created.
diff --git a/docs/bms/umn/en-us_topic_0085714156.html b/docs/bms/umn/en-us_topic_0085714156.html
index 5d0e0bc8..b6c996eb 100644
--- a/docs/bms/umn/en-us_topic_0085714156.html
+++ b/docs/bms/umn/en-us_topic_0085714156.html
@@ -9,9 +9,7 @@
For details about how to configure a user-defined VLAN for BMSs running different OSs, see sections Configuring a User-defined VLAN (SUSE Linux Enterprise Server 12) to Configuring a User-defined VLAN (Windows Server).
-
View User-defined VLANs
User-defined VLANs are presented to you through the BMS specifications shown in Figure 1.
-
Figure 1 BMS specifications
-
A BMS created using this flavor provides one two-port 10GE NIC for connecting to the VPC as well as one two-port 10GE extension NIC for a high-speed interconnection between BMSs. You can configure VLANs on the extension NIC as needed.
+
View User-defined VLANs
User-defined VLANs are presented to you through the BMS specifications. For example, if the extended configuration of a flavor is 2 x 2*10GE, a BMS created using this flavor provides one two-port 10GE NIC for connecting to the VPC as well as one two-port 10GE extension NIC for a high-speed interconnection between BMSs. You can configure VLANs on the extension NIC as needed.
@@ -20,10 +18,3 @@
-
-
\ No newline at end of file
diff --git a/docs/bms/umn/en-us_topic_0092358576.html b/docs/bms/umn/en-us_topic_0092358576.html
index 302d8e9c..eaac4fa0 100644
--- a/docs/bms/umn/en-us_topic_0092358576.html
+++ b/docs/bms/umn/en-us_topic_0092358576.html
@@ -1,6 +1,6 @@
-
How Should I Select Storage?
+
How Do I Select Storage?
When you create a BMS, you can select one from the following storage types:
- Elastic Volume Service (EVS): provides EVS disks of different QoS configurations to meet performance requirements in various scenarios.
diff --git a/docs/bms/umn/en-us_topic_0095251849.html b/docs/bms/umn/en-us_topic_0095251849.html
deleted file mode 100644
index c3777087..00000000
--- a/docs/bms/umn/en-us_topic_0095251849.html
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
Installing Drivers and Toolkits
-
-
-
diff --git a/docs/bms/umn/en-us_topic_0095251850.html b/docs/bms/umn/en-us_topic_0095251850.html
deleted file mode 100644
index 98fdb4c6..00000000
--- a/docs/bms/umn/en-us_topic_0095251850.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
Installing the NVIDIA GPU Driver and CUDA Toolkit on a P1 BMS
-
Scenarios
After a GPU-accelerated P1 BMS (using the physical.p1.large flavor) is created, the NVIDIA GPU driver and CUDA Toolkit must be installed on it for computing acceleration.
-
-
Prerequisites
- An EIP has been bound to the BMS.
- You have obtained the required driver installation packages.
-
-
-
-
CentOS 7.4
- Log in to the target BMS and run the following command to switch to user root:
su root
- - (Optional) If the gcc, gcc-c++, make, and kernel-devel dependency packages do not exist, run the following commands to install the gcc, gcc-c++, make, and kernel-devel tools:
yum install gcc
-yum install gcc-c++
-yum install make
-yum install kernel-devel-`uname -r`
- - (Optional) Add the Nouveau driver to the blacklist.
If the Nouveau driver has been installed and loaded, perform the following operations to add the Nouveau driver to the blacklist to avoid conflicts:
-- Add blacklist nouveau to the end of the /etc/modprobe.d/blacklist.conf file.
- Run the following commands to back up and reconstruct initramfs:
mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak
-dracut -v /boot/initramfs-$(uname -r).img $(uname -r)
- - Run the reboot command to restart the BMS.
- - (Optional) If the X service is running, run the systemctl set-default multi-user.target command and restart the BMS to enter multi-user mode.
- (Optional) Install the NVIDIA GPU driver.
If you selected a specified version of NVIDIA GPU driver rather than a version contained in the CUDA Toolkit, perform this step.
-- Download NVIDIA GPU driver installation package NVIDIA-Linux-x86_64-xxx.yy.run from https://www.nvidia.com/Download/index.aspx?lang=en, and upload this package to the /tmp directory on the BMS.
Figure 1 Searching for the NVIDIA GPU driver package (CentOS 7.4)
- - Run the following command to install the NVIDIA GPU driver:
sh ./NVIDIA-Linux-x86_64-xxx.yy.run
- - Run the following command to delete the installation package:
rm -f NVIDIA-Linux-x86_64-xxx.yy.run
-
- - Install the CUDA Toolkit.
- Download CUDA Toolkit installation package cuda_a.b.cc_xxx.yy_linux.run from https://developer.nvidia.com/cuda-downloads, and upload this package to the /tmp directory on the BMS.
- Run the following command to change the permission to the installation package:
chmod +x cuda_a.b.cc_xxx.yy_linux.run
- - Run the following command to install the CUDA Toolkit:
./cuda_a.b.cc_xxx.yy_linux.run -toolkit -samples -silent -override --tmpdir=/tmp/
- - Run the following command to delete the installation package:
rm -f cuda_a.b.cc_xxx.yy_linux.run
- - Run the following commands to check whether the installation is successful:
cd /usr/local/cuda/samples/1_Utilities/deviceQueryDrv/
-make
-./deviceQueryDrv
-If the command output contains "Result = PASS", the CUDA Toolkit and the NVIDIA GPU driver have been installed successfully.
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/docs/bms/umn/en-us_topic_0096201996.html b/docs/bms/umn/en-us_topic_0096201996.html
index 6f11c39c..449c841b 100644
--- a/docs/bms/umn/en-us_topic_0096201996.html
+++ b/docs/bms/umn/en-us_topic_0096201996.html
@@ -1,7 +1,7 @@
How Do I Set SSH Configuration Items?
-
You can select the BMS login mode or account type. If you have requirements for special configuration, perform the following operations:
+
You can select the BMS login mode or account type. If you require special configuration, perform the following operations:
- To improve security of the BMS, disable remote login using the password and retain only the certificate login mode. Configure the following parameters:
- Check whether the /etc/cloud/cloud.cfg file contains parameter ssh_pwauth and its value is false. If not, add the parameter or change its value to false. This ensures that password cannot be used to log in to the BMS using Xshell.
- Check whether the value of parameter ChallengeResponseAuthentication in the /etc/ssh/sshd_config file is no. If not, change it to no. This ensures that password cannot be entered using the keyboard inactive method to log in to the BMS using Xshell.
- To enable remote login as user root and enable SSH permissions of user root, perform the following operations:
This operation may cause risks. Exercise caution before performing this operation.
Local IPv4 (EC2 Compatible API)
This interface is used to query the fixed IP address of a BMS. If there are multiple NICs, only the IP address of the primary NIC is displayed.
diff --git a/docs/bms/umn/en-us_topic_0102427987.html b/docs/bms/umn/en-us_topic_0102427987.html
index 52358dc8..ee5996cb 100644
--- a/docs/bms/umn/en-us_topic_0102427987.html
+++ b/docs/bms/umn/en-us_topic_0102427987.html
@@ -12,7 +12,7 @@
Procedure
- Log in to the management console.
- Under Computing, click Bare Metal Server.
The BMS console is displayed.
- In the upper right corner of the BMS list, enter the name, private IP address, ID, or flavor of a BMS and click
to search for the desired BMS. - Click the name of the target BMS.
The page showing details of the BMS is displayed.
- Click the Disks tab. Then, click Attach Disk.
The Attach Disk dialog box is displayed.
- - Select the disk type and target disk, and set the mount point as prompted.
If no EVS disks are available, click Create Disk in the lower part of the list.
+
- Select the disk type and target disk, and set the mount point as prompted.
If no EVS disks are available, click Create Disk in the lower part of the list.
- Click OK.
After the disk is attached, you can view the information about it on the Disks tab.
diff --git a/docs/bms/umn/en-us_topic_0102427988.html b/docs/bms/umn/en-us_topic_0102427988.html
index 0bb68eab..ee5cb713 100644
--- a/docs/bms/umn/en-us_topic_0102427988.html
+++ b/docs/bms/umn/en-us_topic_0102427988.html
@@ -2,7 +2,11 @@
Detaching a Disk
Scenarios
A disk attached to a BMS can be detached.
-
- A disk mounted to /dev/sda functions as the system disk. You can only detach the system disk from a stopped BMS.
- Disks mounted to a mount point other than /dev/sda function as data disks and can be detached from a running or stopped BMS.
+
- A disk mounted to /dev/sda functions as the system disk. You can only detach the system disk from a stopped BMS.
- Disks attached to a mount point other than /dev/sda function as data disks and can be detached from a running or stopped BMS.
+
+
After a BMS is restarted, the drive letter of an EVS disk attached to the BMS may change to the one different from that in the OS.
+
So, you are advised to use a world wide name (WWN) instead of a driver letter when you perform operations on disks. For details about the mapping between a WWN and driver letter, see How Do I Obtain the Drive Letter of an EVS Disk?
+
Constraints
- Detaching the system disk is a mission-critical operation. A BMS without the system disk cannot start. Exercise caution when performing this operation.
- Before detaching a data disk from a running Windows BMS, ensure that no program is reading data from or writing data to the disk. Otherwise, data will be lost.
- Before detaching a data disk from a running Linux BMS, you must log in to the BMS and run the umount command to cancel the association between the disk and the file system. In addition, ensure that no program is reading data from or writing data to the disk. Otherwise, detaching the disk will fail.
diff --git a/docs/bms/umn/en-us_topic_0112777566.html b/docs/bms/umn/en-us_topic_0112777566.html
new file mode 100644
index 00000000..3b8febe6
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0112777566.html
@@ -0,0 +1,84 @@
+
+
+
Configuring a NIC (SUSE Linux Enterprise Server 12)
+
This section uses SUSE Linux Enterprise Server 12 SP3 (x86_64) as an example to describe how to configure a NIC added to or deleted from a BMS.
+
If the network is disconnected after a NIC is added and the BMS is restarted, run the following command:
+
/usr/sbin/wicked ifup bond0.vlan
+
vlan indicates the VLAN used by the NIC.
+
If the network is still disconnected, add the NIC again.
+
+
Add a NIC
- Obtain information about the NIC to be added.
+
Table 1 NIC informationParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+VLAN and MAC address
+ |
+Specifies the VLAN information and MAC address of the NIC. To obtain them, perform the following operations:
+- In the BMS list, click the name of the target BMS.
- Click the NICs tab, locate the row that contains the NIC to be added, and click
 to expand details. - Obtain the values of VLAN and MAC Address.
+ |
+2835
+fa:16:3e:01:c3:2e
+ |
+
+Gateway
+ |
+Specifies the gateway address of the NIC. To obtain them, perform the following operations:
+- On the NIC details page in 2, obtain the subnet information.
- On the BMS details page, click the link following VPC to switch to the VPC list.
- Click the name of the VPC to which the BMS belongs to go to the VPC details page.
- Click the Subnets tab and obtain the gateway address of the subnet in 1.
+ |
+192.168.1.1
+ |
+
+
+
+
- Use a key or password to log in to the BMS as user root.
- Run the following command to copy network configuration file /etc/sysconfig/network/ifcfg-bond0 to generate file /etc/sysconfig/network/ifcfg-bond0.vlan (replace vlan with the VLAN obtained in step 1, such as 2835):
cp -p /etc/sysconfig/network/ifcfg-bond0 /etc/sysconfig/network/ifcfg-bond0.2835
+ - Run the following command to edit /etc/sysconfig/network/ifcfg-bond0.vlan and configure the network configuration file of the newly added NIC, such as ifcfg-bond0.2835:
vim /etc/sysconfig/network/ifcfg-bond0.2835
+Edit the file as follows:
+STARTMODE=auto
+ETHERDEVICE=bond0
+LLADDR=fa:16:3e:01:c3:2e
+NM_CONTROLLED=no
+BOOTPROTO=dhcp
+DEVICE=bond0.2835
+USERCONTRL=auto
+TYPE=Ethernet
+VLAN_ID=2835
+Where,
+- LLADDR: indicates the MAC address of the NIC to be added. For its value, see 1.
- DEVICE: Set it to bond0.vlan. vlan is the value obtained from 1, such as 2835.
- VLAN_ID: indicates the VLAN ID, such as 2835.
+After the modification, press Esc and enter :wq to save the change and exit.
+ - Run the following command to start the added NIC:
/usr/sbin/wicked ifup bond0.vlan
+For example, to start bond0.2835, run the command shown in the following figure.
+
+ - Run the following command to check the status of the NIC device:
+ - Ping the gateway from the new network device to check whether the network connectivity is normal.
Use the gateway address obtained from 1.
+
+
+
+
Deleting NICs
- Obtain the VLAN and MAC address of the NIC to be deleted.
- Use a key or password to log in to the BMS as user root.
- Locate the network device based on the VLAN information and run the /usr/sbin/wicked ifdown bond0.vlan command to delete the device.
serverc7fc560e-24d6-4ad4-9b1e-567a762532c3:~ # ip link | grep 2835
+12: bond0.2835@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP mode DEFAULT group default qlen 1000
+serverc7fc560e-24d6-4ad4-9b1e-567a762532c3:~ #
+serverc7fc560e-24d6-4ad4-9b1e-567a762532c3:~ # /usr/sbin/wicked ifdown bond0.2835
+serverc7fc560e-24d6-4ad4-9b1e-567a762532c3:~ #
+ - Run the following command to delete network configuration file /etc/sysconfig/network/ifcfg-bond0.vlan (replace vlan with the VLAN obtained from 1, such as 2835):
rm /etc/sysconfig/network/ifcfg-bond0.2835
+ - Run the following command to delete network configuration file /etc/wicked/ifconfig/bond0.vlan.xml (replace vlan with the VLAN obtained from 1, such as 2835):
rm /etc/wicked/ifconfig/bond0.2835.xml
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/bms/umn/en-us_topic_0112778363.html b/docs/bms/umn/en-us_topic_0112778363.html
new file mode 100644
index 00000000..d42d1a2e
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0112778363.html
@@ -0,0 +1,84 @@
+
+
+
Configuring a NIC (SUSE Linux Enterprise Server 11)
+
This section uses SUSE Linux Enterprise Server 11 SP4 as an example to describe how to configure a NIC added to or deleted from a BMS.
+
If the network is disconnected after a NIC is added and the BMS is restarted, run the following command:
+
/usr/sbin/wicked ifup bond0.vlan
+
vlan indicates the VLAN used by the NIC.
+
If the network is still disconnected, add the NIC again.
+
+
Add a NIC
- Obtain information about the NIC to be added.
+
Table 1 NIC informationParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+VLAN and MAC address
+ |
+Specifies the VLAN information and MAC address of the NIC. To obtain them, perform the following operations:
+- In the BMS list, click the name of the target BMS.
- Click the NICs tab, locate the row that contains the NIC to be added, and click
 to expand details. - Obtain the values of VLAN and MAC Address.
+ |
+2832
+fa:16:3e:1b:f0:3f
+ |
+
+Gateway
+ |
+Specifies the gateway address of the NIC. To obtain them, perform the following operations:
+- On the NIC details page in 2, obtain the subnet information.
- On the BMS details page, click the link following VPC to switch to the VPC list.
- Click the name of the VPC to which the BMS belongs to go to the VPC details page.
- Click the Subnets tab and obtain the gateway address of the subnet in 1.
+ |
+192.168.1.1
+ |
+
+
+
+
- Use a key or password to log in to the BMS as user root.
- Run the following command to copy network configuration file /etc/sysconfig/network/ifcfg-bond0 to generate file /etc/sysconfig/network/ifcfg-bond0.vlan (replace vlan with the VLAN obtained in step 1, such as 2832):
cp -p /etc/sysconfig/network/ifcfg-bond0 /etc/sysconfig/network/ifcfg-bond0.2832
+ - Run the following command to edit /etc/sysconfig/network/ifcfg-bond0.vlan and configure the network configuration file of the newly added NIC, such as ifcfg-bond0.2832:
vim /etc/sysconfig/network/ifcfg-bond0.2832
+Edit the file as follows:
+STARTMODE=auto
+ETHERDEVICE=bond0
+LLADDR=fa:16:3e:1b:f0:3f
+NM_CONTROLLED=no
+BOOTPROTO=dhcp
+DEVICE=bond0.2832
+USERCONTRL=auto
+TYPE=Ethernet
+VLAN_ID=2832
+Where,
+- LLADDR: indicates the MAC address of the NIC to be added. For its value, see 1.
- DEVICE: Set it to bond0.vlan. vlan is the value obtained from 1, such as 2832.
- VLAN_ID: indicates the VLAN ID, such as 2832.
+After the modification, press Esc and enter :wq to save the change and exit.
+ - Run the following command to start the added NIC:
/sbin/ifup bond0.vlan
+For example, to start bond0.2832, run the command shown in the following figure.
+
+ - Run the following command to check the status of the NIC device:
+ - Ping the gateway from the new network device to check whether the network connectivity is normal.
Use the gateway address obtained from 1.
+
+
+
+
Delete a NIC
- Obtain the VLAN and MAC address of the NIC to be deleted.
- Use a key or password to log in to the BMS as user root.
- Locate the network device based on the VLAN information and run the /sbin/ifdown bond0.vlan command to delete the device.
server7ae352a6-657c-4af5-8058-f3a9ec75ca1f:~ # ip link | grep 2832
+7: bond0.2832@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP
+server7ae352a6-657c-4af5-8058-f3a9ec75ca1f:~ #
+server7ae352a6-657c-4af5-8058-f3a9ec75ca1f:~ # /sbin/ifdown bond0.2832
+ bond0.2832
+server7ae352a6-657c-4af5-8058-f3a9ec75ca1f:~ #
+ - Run the following command to delete network configuration file /etc/sysconfig/network/ifcfg-bond0.vlan (replace vlan with the VLAN obtained from 1, such as 2832):
rm /etc/sysconfig/network/ifcfg-bond0.2832
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/bms/umn/en-us_topic_0112778364.html b/docs/bms/umn/en-us_topic_0112778364.html
new file mode 100644
index 00000000..490a338a
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0112778364.html
@@ -0,0 +1,152 @@
+
+
+
Configuring a NIC (Red Hat, CentOS, Oracle Linux, and EulerOS)
+
This section uses CentOS 6.9 (x86_64) as an example to describe how to configure a NIC added to or deleted from a BMS.
+
+
Add a NIC
Use a key or password to log in to the BMS as user root. Run the following command:
+
blkid | grep config-2
+
If the command output is empty, use Method 2. If the command output shown in the following figure is displayed, use Method 1.
+
+
+
- Obtain information about the NIC to be added.
+
Table 1 NIC informationParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+VLAN and MAC address
+ |
+Specifies the VLAN information and MAC address of the NIC. To obtain them, perform the following operations:
+- In the BMS list, click the name of the target BMS to enter the BMS details page.
- Click the NICs tab, locate the row that contains the NIC to be added, and click
 to expand details. - Obtain the values of VLAN and MAC Address.
+ |
+2838
+fa:16:3e:1a:fd:5d
+ |
+
+Gateway
+ |
+Specifies the gateway address of the NIC. To obtain them, perform the following operations:
+- On the NIC details page in 2, obtain the subnet information.
- On the BMS details page, click the link following VPC to switch to the VPC list.
- Click the name of the VPC to which the BMS belongs to go to the VPC details page.
- Click the Subnets tab and obtain the gateway address of the subnet in 1.
+ |
+192.168.1.1
+ |
+
+
+
+
- Use a key or password to log in to the BMS as user root.
- Run the following command to copy file /etc/sysconfig/network-scripts/ifcfg-bond0 to generate file /etc/sysconfig/network-scripts/ifcfg-bond0.vlan (replace vlan with the VLAN obtained in step 1, such as 2838):
cp -p /etc/sysconfig/network-scripts/ifcfg-bond0 /etc/sysconfig/network-scripts/ifcfg-bond0.2838
+ - Run the following command to edit /etc/sysconfig/network-scripts/ifcfg-bond0.vlan and configure the network configuration file of the newly added NIC, such as ifcfg-bond0.2838:
vim /etc/sysconfig/network-scripts/ifcfg-bond0.2838
+Edit the file as follows:
+MACADDR=fa:16:3e:1a:fd:5d
+USERCTL=no
+PERSISTENT_DHCLIENT=1
+PHYSDEV=bond0
+VLAN=yes
+NM_CONTROLLED=no
+BOOTPROTO=dhcp
+DEVICE=bond0.2838
+TYPE=Ethernet
+ONBOOT=yes
+Descriptions of the parameters are as follows:
+- MACADDR: indicates the MAC address of the NIC to be added. For its value, see step 1.
- DEVICE: Set it to bond0.vlan. vlan is the value obtained from 1, such as 2838.
+After the modification, press Esc and enter :wq to save the change and exit.
+ - Run the following command to start the added NIC:
ifup bond0.vlan
+For example, to start bond0.2838, run the command shown in the following figure.
+
+ - Run the following command to check the status of the NIC device:
+ - Ping the gateway from the new network device to check whether the network connectivity is normal.
Use the gateway address obtained from 1.
+
+
+
+
- Obtain information about the NIC to be added.
+
Table 2 NIC informationParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+MAC Address
+ |
+Specifies the MAC address of the NIC. To obtain them, perform the following operations:
+- In the BMS list, click the name of the target BMS.
- Click the NICs tab, locate the row that contains the NIC to be added, and click
 to expand details. - Obtain the MAC address.
+ |
+fa:16:3e:4e:f7:ae
+ |
+
+Gateway
+ |
+Specifies the gateway address of the NIC. To obtain them, perform the following operations:
+- On the NIC details page in 2, obtain the subnet information.
- On the BMS details page, click the link following VPC to switch to the VPC list.
- Click the name of the VPC to which the BMS belongs to go to the VPC details page.
- Click the Subnets tab and obtain the gateway address of the subnet.
+ |
+192.168.0.1
+ |
+
+
+
+
- Run the following command to query the name of the NIC whose MAC address is MACADDR:
ifconfig -a | grep MACADDR -B 1
+MACADDR: indicates the MAC address of the NIC to be added. For its value, see step 1.
+
+As shown in the preceding figure, the NIC name is eth7.
+ - Run the following command to edit the /etc/sysconfig/network-scripts/ifcfg-eth7 file and configure the network configuration file of the new NIC:
vim /etc/sysconfig/network-scripts/ifcfg-eth7
+Edit the file as follows:
+DEVICE=eth7
+MACADDR=fa:16:3e:1a:fd:5d
+BOOTPROTO=dhcp
+ONBOOT=yes
+Where,
+- MACADDR: indicates the MAC address of the NIC to be added. For its value, see step 1.
- Set DEVICE to the name of the new NIC. For its value, see step 2.
+After the modification, press Esc and enter :wq to save the change and exit.
+ - Run the following command to start the added NIC:
ifup eth7
+For example, to start eth7, run the following command:
+
+ - Run the following command to check the status of the NIC device:
+ - Ping the gateway from the new network device to check whether the network connectivity is normal.
Use the gateway address obtained from 1.
+
+
+
+
Delete a NIC
Use a key or password to log in to the BMS as user root. Run the following command:
+
blkid | grep config-2
+
If the command output is empty, use Method 2. If the command output shown in the following figure is displayed, use Method 1.
+
+
+
- Obtain the VLAN and MAC address of the NIC to be deleted.
- Use a key or password to log in to the BMS as user root.
- Locate the network device based on the VLAN information and run the following commands to stop and delete the device:
[root@host-192-168-0-172 ~]# ip link | grep 2838
+8: bond0.2838@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP
+[root@host-192-168-0-172 ~]# ifconfig bond0.2838 down
+[root@host-192-168-0-172 ~]#
+[root@host-192-168-0-172 ~]# ip link delete bond0.2838
+[root@host-192-168-0-172 ~]#
+ - Run the following command to delete network configuration file /etc/sysconfig/network-scripts/ifcfg-bond0.vlan (replace vlan with the VLAN obtained from 1, such as 2838):
rm /etc/sysconfig/network-scripts/ifcfg-bond0.2838
+
+
+
- Obtain the VLAN and MAC address of the NIC to be deleted.
- Use a key or password to log in to the BMS as user root.
- Locate the network device based on the VLAN information and run the following commands to stop and delete the device:
[root@bms-197-31 ~]# ip link | grep fa:16:3e:4e:f7:ae -B 1
+9: eth7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
+ link/ether fa:16:3e:4e:f7:ae brd ff:ff:ff:ff:ff:ff
+[root@bms-197-31 ~]# ifconfig eth7 down
+[52574.065410] hinic 0000:89:00.0 eth7: [NIC]Netdev is down
+ - Run the following command to delete network configuration file /etc/sysconfig/network-scripts/ifcfg-eth7:
rm /etc/sysconfig/network-scripts/ifcfg-eth7
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/bms/umn/en-us_topic_0112790033.html b/docs/bms/umn/en-us_topic_0112790033.html
new file mode 100644
index 00000000..134b159c
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0112790033.html
@@ -0,0 +1,101 @@
+
+
+
Configuring a NIC (Ubuntu)
+
This section uses Ubuntu 16.04 LTS (Xenial Xerus x86_64) as an example to describe how to configure a NIC added to or deleted from a BMS.
+
+
Add a NIC
- Obtain information about the NIC to be added.
+
Table 1 NIC informationParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+VLAN and MAC address
+ |
+Specifies the VLAN information and MAC address of the NIC. To obtain them, perform the following operations:
+- In the BMS list, click the name of the target BMS.
- Click the NICs tab, locate the row that contains the NIC to be added, and click
 to expand details. - Obtain the values of VLAN and MAC Address.
+ |
+2847
+fa:16:3e:a2:aa:65
+ |
+
+Gateway
+ |
+Specifies the gateway address of the NIC. To obtain them, perform the following operations:
+- On the NIC details page in 2, obtain the subnet information.
- On the BMS details page, click the link following VPC to switch to the VPC list.
- Click the name of the VPC to which the BMS belongs to go to the VPC details page.
- Click the Subnets tab and obtain the gateway address of the subnet in 1.
+ |
+192.168.1.1
+ |
+
+
+
+
- Use a key or password to log in to the BMS as user root.
- Check whether the /etc/network/interfaces.d/ directory contains the /etc/network/interfaces.d/70-cloud-init.cfg file.
- If yes, go to step 5.
- If no, go to step 4.
+ - Run the following commands to generate the /etc/network/interfaces.d/70-cloud-init.cfg file and set the file permissions:
touch /etc/network/interfaces.d/70-cloud-init.cfg
+chmod 644 /etc/network/interfaces.d/70-cloud-init.cfg
+ - Run the following command to edit the /etc/network/interfaces.d/70-cloud-init.cfg file and add information about the NIC to be added to the file:
vim /etc/network/interfaces.d/70-cloud-init.cfg
+Edit the file as follows:
+auto bond0.2847
+iface bond0.2847 inet dhcp
+mtu 8888
+hwaddress fa:16:3e:a2:aa:65
+vlan-raw-device bond0
+The required information has been obtained in step 1.
+- bond0.2847: indicates the name of the NIC to be added. bond0 is a fixed value and the number following it is the VLAN information of the NIC.
- hwaddress: indicates the MAC address of the NIC to be added.
- vlan-raw-device: The default value bond0 is used.
+After the modification, press Esc, enter :wq, save the configuration, and exit.
+ - Run the following command to start the added NIC:
ifup bond0.vlan
+For example, to start bond0.2847, run the ifup bond0.2847 command.
+ - Run the following command to check the status of the NIC device:
ip link
+
+ - Ping the gateway from the new network device to check whether the network connectivity is normal.
Use the gateway address obtained from 1.
+
+
+
+
Delete a NIC
- Obtain the VLAN and MAC address of the VPC NIC to be deleted.
- Use a key or password to log in to the BMS as user root.
- Locate the network device based on the VLAN information and run the following commands to stop and delete the device:
root@ubuntu:~# ip link | grep 2847
+9: bond0.2847@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP mode DEFAULT group default qlen 1000
+root@ubuntu:~# ifconfig bond0.2847 down
+root@ubuntu:~# ip link delete bond0.2847
+ - Check whether the BMS OS has been reinstalled after the NIC is added to the BMS.
- If no, go to step 5.
- If yes, go to step 9.
+ - Run the following command to copy the /etc/network/interfaces.d/70-cloud-init.cfg file to generate the /etc/network/interfaces.d/70-cloud-init.cfg.bak file to back up the network configuration:
cp -p /etc/network/interfaces.d/70-cloud-init.cfg /etc/network/interfaces.d/70-cloud-init.cfg.bak
+ - Run the following command to edit /etc/network/interfaces.d/70-cloud-init.cfg, locate the NIC to be deleted based on the VLAN and MAC address obtained from 1, and delete the NIC information from the file:
vim /etc/network/interfaces.d/70-cloud-init.cfg
+# The following information needs to be deleted:
+auto bond0.2847
+iface bond0.2847 inet dhcp
+mtu 8888
+hwaddress fa:16:3e:a2:aa:65
+vlan-raw-device bond0
+After the modification, press Esc, enter :wq, save the configuration, and exit.
+ - After the NIC is deleted, if the /etc/network/interfaces.d/70-cloud-init.cfg file contains no NIC information, run the following command to delete the /etc/network/interfaces.d/70-cloud-init.cfg file:
rm /etc/network/interfaces.d/70-cloud-init.cfg
+ - Check whether other NICs run properly. If they run properly, run the following command to delete the /etc/network/interfaces.d/70-cloud-init.cfg.bak file:
rm /etc/network/interfaces.d/70-cloud-init.cfg.bak
+ - Run the following command to copy the /etc/network/interfaces.d/50-cloud-init.cfg file to generate the /etc/network/interfaces.d/50-cloud-init.cfg.bak file to back up the network configuration:
cp -p /etc/network/interfaces.d/50-cloud-init.cfg /etc/network/interfaces.d/50-cloud-init.cfg.bak
+ - Run the following command to edit /etc/network/interfaces.d/50-cloud-init.cfg, locate the NIC to be deleted based on the VLAN and MAC address obtained from 1, and delete the NIC information from the file:
vim /etc/network/interfaces.d/50-cloud-init.cfg
+# The following information needs to be deleted:
+auto bond0.2847
+iface bond0.2847 inet dhcp
+mtu 8888
+hwaddress fa:16:3e:a2:aa:65
+vlan-raw-device bond0
+After the modification, press Esc, enter :wq, save the configuration, and exit.
+ - Check whether other NICs run properly. If they run properly, run the following command to delete the /etc/network/interfaces.d/50-cloud-init.cfg.bak file:
rm /etc/network/interfaces.d/50-cloud-init.cfg.bak
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/bms/umn/en-us_topic_0112790034.html b/docs/bms/umn/en-us_topic_0112790034.html
new file mode 100644
index 00000000..5cb04093
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0112790034.html
@@ -0,0 +1,80 @@
+
+
+
Configuring a NIC (Windows Server)
+
+
This section uses Windows Server 2012 R2 Standard as an example to describe how to configure a NIC added to or deleted from a BMS.
+
- The configuration methods of other Windows Server OSs are similar to that of Windows Server 2012 R2 Standard.
- If the network is still disconnected after the NIC is added and the BMS is restarted, add the NIC again.
+
+
Add a NIC
- Obtain information about the NIC to be added.
+
Table 1 NIC informationParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+VLAN and MAC address
+ |
+Specifies the VLAN information and MAC address of the NIC. To obtain them, perform the following operations:
+- In the BMS list, click the name of the target BMS.
- Click the NICs tab, locate the row that contains the NIC to be added, and click
 to expand details. - Obtain the values of VLAN and MAC Address.
+ |
+2812
+fa:16:3e:15:38:07
+ |
+
+Gateway
+ |
+Specifies the gateway address of the NIC. To obtain them, perform the following operations:
+- On the NIC details page in 2, obtain the subnet information.
- On the BMS details page, click the link following VPC to switch to the VPC list.
- Click the name of the VPC to which the BMS belongs to go to the VPC details page.
- Click the Subnets tab and obtain the gateway address of the subnet in 1.
+ |
+192.168.1.1
+ |
+
+
+
+
- Log in to a Windows BMS.
- On the Windows PowerShell CLI of the BMS, run the following command to check whether the NIC information contains Team1 (port group name of the VPC):
Get-NetAdapter
+- If yes, go to step 4.
- If no, contact the customer service.
+Information similar to the following is displayed.
+
+ eth0 and eth1 are the network devices that carry the VPC.
+
+ - Run the following commands to add the NIC:
Add-NetLbfoTeamNIC -Team "Team1" -VlanID vlan_id -Name "Team1-vlan-vlan_id" -Confirm:$false
+Set-NetAdapter -Name "Team1-vlan-vlan_id" -MacAddress "mac_addr" -Confirm:$false
+In the preceding command, Team1 is the port group name of the VPC, vlan_id is the VLAN information obtained in step 1 (such as 2812), and mac_addr is the MAC address obtained in step 1 (such as fa:16:3e:15:38:07).
+
+ - Run the following command to check the status of the NIC device:
Get-NetAdapter
+Information similar to the following is displayed.
+
+ - Ping the gateway from the new network device to check whether the network connectivity is normal.
The IPv4 address of the added network device Team1-vlan-2812 is that shown in the red box in the following figure.
+
+Use the gateway address obtained from step 1.
+Information similar to the following is displayed.
+
+
+
+
Delete a NIC
- Obtain the VLAN and MAC address of the NIC to be deleted.
- Log in to a Windows BMS.
- On the Windows PowerShell CLI of the BMS, run the following command to check information about the NIC to be added:
Get-NetLbfoTeamNIC -Team Team1
+
+ - Run the following command to delete the NIC:
Remove-NetLbfoTeamNIC -Team "Team1" -VlanID vlan_id
+In the command, vlan_id indicates the VLAN information obtained in step 1.
+
+ - Run the following commands to query the NIC information and verify that the NIC is deleted:
Get-NetLbfoTeamNIC -Team Team1
+Get-NetAdapter
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/bms/umn/en-us_topic_0117747866.html b/docs/bms/umn/en-us_topic_0117747866.html
index 4b877578..4ca8e30b 100644
--- a/docs/bms/umn/en-us_topic_0117747866.html
+++ b/docs/bms/umn/en-us_topic_0117747866.html
@@ -12,7 +12,7 @@
How Do I Apply for a Higher Quota?
The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.
Before dialing the hotline number or sending an email, make sure that the following information has been obtained:
-
- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
+- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
- Quota information, which includes:
- Service name
- Quota type
- Required quota
Learn how to obtain the service hotline and email address.
diff --git a/docs/bms/umn/en-us_topic_0121593247.html b/docs/bms/umn/en-us_topic_0121593247.html
new file mode 100644
index 00000000..3b876bb3
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0121593247.html
@@ -0,0 +1,130 @@
+
+
+Configuring an Enhanced High-Speed NIC (SUSE Linux Enterprise Server 12)
+This section uses SUSE Linux Enterprise Server 12 SP3 (x86_64) as an example to describe how to configure an enhanced high-speed NIC of a BMS, including the configuration for adding and deleting a NIC.
+
Add a NIC
For details about how to add a NIC in other OSs, see:
+
+
+
- Use a key or password to log in to the BMS as user root.
- On the BMS CLI, run the following command to check the NIC information:
ip link
+Information similar to the following is displayed:
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
+5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a6 brd ff:ff:ff:ff:ff:ff
+6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP mode DEFAULT group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+ eth0 and eth1 bear the VPC, and eth2 and eth3 bear the enhanced high-speed network.
+
+ - Configure the udev rules:
Run the following command to create the 80-persistent-net.rules file:
+cp /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/80-persistent-net.rules
+Write the NIC MAC address and name that are queried in 2 and that are not displayed in 80-persistent-net.rules to the file. In this way, after the BMS is restarted, the NIC name and sequence will not change.
+ Ensure that the NIC MAC address and name are lowercase letters.
+
+vim /etc/udev/rules.d/80-persistent-net.rules
+The modification result is as follows:
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:4c:7f:5d:b7:2a", NAME="eth0"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:4c:7f:5d:b7:2b", NAME="eth1"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:7d:0f:52:e3:a5", NAME="eth2"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:7d:0f:52:e3:a6", NAME="eth3"
+ - Run the following commands to create configuration files for NICs eth2 and eth3 (you can quickly create the files by copying existing NIC configuration files):
cd /etc/sysconfig/network
+cp ifcfg-eth0 ifcfg-eth2
+cp ifcfg-eth1 ifcfg-eth3
+Run the following commands to modify the configuration files of NICs eth2 and eth3:
+vi ifcfg-eth2
+Modified configuration file of NIC eth2 is as follows.
+STARTMODE=auto
+MTU=8888
+NM_CONTROLLED=no
+BOOTPROTO=STATIC
+DEVICE=eth2
+USERCONTRL=no
+LLADDR=40:7d:0f:52:e3:a5
+TYPE=Ethernet
+ In this configuration file, set MTU to 8888, BOOTPROTO to STATIC, and configure DEVICE and LLADDR as required.
+
+vi ifcfg-eth3
+Modified configuration file of NIC eth3 is as follows:
+STARTMODE=auto
+MTU=8888
+NM_CONTROLLED=no
+BOOTPROTO=STATIC
+DEVICE=eth3
+USERCONTRL=no
+LLADDR=40:7d:0f:52:e3:a6
+TYPE=Ethernet
+After the modification, save the change and exit.
+ - Run the following command to bond NICs eth2 and eth3 to a NIC, for example, bond1:
Run the following commands to create the ifcfg-bond1 file and modify the configuration file:
+cp ifcfg-bond0 ifcfg-bond1
+vi ifcfg-bond1
+Modified configuration file of NIC bond1 is as follows.
+BONDING_MASTER=yes
+TYPE=Bond
+MTU=8888
+STARTMODE=auto
+BONDING_MODULE_OPTS="mode=1 miimon=100"
+NM_CONTROLLED=no
+BOOTPROTO=STATIC
+DEVICE=bond1
+USERCONTRL=no
+LLADDR=40:7d:0f:52:e3:a5
+BONDING_SLAVE1=eth2
+BONDING_SLAVE0=eth3
+IPADDR=10.10.10.104
+NETMASK=255.255.255.0
+NETWORK=10.10.10.0
+ In this configuration file, MTU is set to 8888, BONDING_MODULE_OPTS is set to mode=1 miimon=100, BOOTPROTO is set to STATIC. DEVICE, BONDING_SLAVE1, BONDING_SLAVE0, IPADDR, NETMASK, and NETWORK are configured as required. LLADDR is set to the LLADDR value of the BONDING_SLAVE1 NIC.
+
+After the modification, save the change and exit.
+ - Run the following command to start the added bond1 NIC:
wicked ifup bond1
+ - Run the following command to query IP addresses:
ip addr show
+An example is provided as follows:
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
+5: eth3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
+6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+ inet 172.16.2.44/24 brd 172.16.2.255 scope global bond0
+ valid_lft forever preferred_lft forever
+ inet6 fe80::f816:ff:fe57:90c9/64 scope link
+ valid_lft forever preferred_lft forever
+7: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
+ inet 10.10.10.104/24 brd 10.10.10.255 scope global bond1
+ valid_lft forever preferred_lft forever
+ inet6 fe80::427d:fff:fe52:e3a5/64 scope link
+ valid_lft forever preferred_lft forever
+ - Repeat the preceding operations to configure other BMSs.
+
+
Delete a NIC
For details about how to delete a NIC in other OSs, see:
+
+
+
- Obtain the IP address of the bonded enhanced high-speed NIC to be deleted.
- Use a key or password to log in to the BMS as user root.
- Locate the bond network device and run the following command to stop and delete the device:
wicked ifdown bond1
+ - Run the following commands to delete network configuration files /etc/sysconfig/network-scripts/ifcfg-eth2, /etc/sysconfig/network-scripts/ifcfg-eth3, and /etc/sysconfig/network-scripts/ifcfg-bond1:
rm -f /etc/sysconfig/network-scripts/ifcfg-eth2
+rm -f /etc/sysconfig/network-scripts/ifcfg-eth3
+rm /etc/sysconfig/network/ifcfg-bond1
+
+
+
Configuring an Enhanced High-Speed NIC (SUSE Linux Enterprise Server 11)
+This section uses SUSE Linux Enterprise Server 11 SP4 as an example to describe how to configure an enhanced high-speed NIC of a BMS.
+
Add a NIC
- Use a key or password to log in to the BMS as user root.
- On the BMS CLI, run the following command to check the NIC information:
ip link
+Information similar to the following is displayed.
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
+5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a6 brd ff:ff:ff:ff:ff:ff
+6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP mode DEFAULT group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+ Among the devices, eth0 and eth1 bear the VPC, and eth2 and eth3 bear the user-defined VLAN.
+
+ - Configure the udev rules:
Run the following command to create the 80-persistent-net.rules file:
+cp /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/80-persistent-net.rules
+Write the NIC MAC address and name that are queried in 2 and that are not displayed in 80-persistent-net.rules to the file. In this way, after the BMS is restarted, the NIC name and sequence will not change.
+ Ensure that the NIC MAC address and name are lowercase letters.
+
+vim /etc/udev/rules.d/80-persistent-net.rules
+The modification result is as follows:
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:4c:7f:5d:b7:2a", NAME="eth0"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:4c:7f:5d:b7:2b", NAME="eth1"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:7d:0f:52:e3:a5", NAME="eth2"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:7d:0f:52:e3:a6", NAME="eth3"
+ - Create the configuration files of NICs eth2 and eth3:
You can copy an existing NIC configuration file and modify it to improve the creation efficiency.
+cd /etc/sysconfig/network
+cp ifcfg-eth0 ifcfg-eth2
+cp ifcfg-eth1 ifcfg-eth3
+Run the following commands to modify the configuration files of NICs eth2 and eth3:
+vi ifcfg-eth2
+Modified configuration file of NIC eth2 is as follows.
+STARTMODE=auto
+MTU=8888
+NM_CONTROLLED=no
+BOOTPROTO=STATIC
+DEVICE=eth2
+USERCONTRL=no
+LLADDR=40:7d:0f:52:e3:a5
+TYPE=Ethernet
+ In this configuration file, set MTU to 8888, BOOTPROTO to STATIC, and configure DEVICE and LLADDR as required.
+
+vi ifcfg-eth3
+Modified configuration file of NIC eth3 is as follows:
+STARTMODE=auto
+MTU=8888
+NM_CONTROLLED=no
+BOOTPROTO=STATIC
+DEVICE=eth3
+USERCONTRL=no
+LLADDR=40:7d:0f:52:e3:a6
+TYPE=Ethernet
+After the modification, save the change and exit.
+ - Run the following command to bond NICs eth2 and eth3 to a NIC, for example, bond1:
Run the following commands to create the ifcfg-bond1 file and modify the configuration file:
+cp ifcfg-bond0 ifcfg-bond1
+vi ifcfg-bond1
+Modified configuration file of NIC bond1 is as follows.
+BONDING_MASTER=yes
+TYPE=Bond
+MTU=8888
+STARTMODE=auto
+BONDING_MODULE_OPTS="mode=1 miimon=100"
+NM_CONTROLLED=no
+BOOTPROTO=STATIC
+DEVICE=bond1
+USERCONTRL=no
+LLADDR=40:7d:0f:52:e3:a5
+BONDING_SLAVE1=eth2
+BONDING_SLAVE0=eth3
+IPADDR=10.10.10.104
+NETMASK=255.255.255.0
+NETWORK=10.10.10.0
+ In this configuration file, MTU is set to 8888, BONDING_MODULE_OPTS is set to mode=1 miimon=100, BOOTPROTO is set to STATIC. DEVICE, BONDING_SLAVE1, BONDING_SLAVE0, IPADDR, NETMASK, and NETWORK are configured as required. LLADDR is set to the LLADDR value of the BONDING_SLAVE1 NIC.
+
+After the modification, save the change and exit.
+ - Run the following command to start the added bond1 NIC:
ifup bond1
+ - Run the following command to query IP addresses:
ip addr show
+An example is provided as follows:
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
+5: eth3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
+6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP group default qlen 1000
+ link/ether fa:16:00:57:90:c9 brd ff:ff:ff:ff:ff:ff
+ inet 172.16.2.44/24 brd 172.16.2.255 scope global bond0
+ valid_lft forever preferred_lft forever
+ inet6 fe80::f816:ff:fe57:90c9/64 scope link
+ valid_lft forever preferred_lft forever
+7: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
+ inet 10.10.10.104/24 brd 10.10.10.255 scope global bond1
+ valid_lft forever preferred_lft forever
+ inet6 fe80::427d:fff:fe52:e3a5/64 scope link
+ valid_lft forever preferred_lft forever
+ - Repeat the preceding operations to configure other BMSs.
+
+
Delete a NIC
- Obtain the IP address of the bonded enhanced high-speed NIC to be deleted.
- Use a key or password to log in to the BMS as user root.
- Locate the bond network device and run the following command to stop and delete the device:
ifdown bond1
+ - Run the following commands to delete network configuration files /etc/sysconfig/network-scripts/ifcfg-eth2, /etc/sysconfig/network-scripts/ifcfg-eth3, and /etc/sysconfig/network-scripts/ifcfg-bond1:
rm -f /etc/sysconfig/network-scripts/ifcfg-eth2
+rm -f /etc/sysconfig/network-scripts/ifcfg-eth3
+rm /etc/sysconfig/network/ifcfg-bond1
+
+
+
Configuring an Enhanced High-Speed NIC (Red Hat, CentOS, Oracle Linux, and EulerOS)
+This section uses CentOS 6.9 (x86_64) as an example to describe how to configure an enhanced high-speed NIC of a BMS.
+
The configuration methods of Red Hat, Oracle Linux, EulerOS, and CentOS are similar.
+
+
Add a NIC
Use a key or password to log in to the BMS as user root. Run the following command:
+
blkid | grep config-2
+
If the command output is empty, use Method 2. If the command output shown in the following figure is displayed, use Method 1.
+
+
+
- Use a key or password to log in to the BMS as user root.
- On the BMS CLI, run the following command to check the NIC information:
ip link
+Information similar to the following is displayed.
+
+ eth0 and eth1 bear the VPC, and eth2 and eth3 bear the enhanced high-speed network.
+
+ - Run the following command to check whether the /etc/udev/rules.d/ directory contains the 80-persistent-net.rules file:
ll /etc/udev/rules.d/ | grep 80-persistent-net.rules
+- If yes, and the file contains all NICs except bond0 and lo obtained in step 2 and their MAC addresses, go to step 6.
- If no, go to step 4.
+ - Run the following command to copy the /etc/udev/rules.d/70-persistent-net.rules file and name the copy as /etc/udev/rules.d/80-persistent-net.rules.
cp -p /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/80-persistent-net.rules
+ If the /etc/udev/rules.d/70-persistent-net.rules file does not exist, create it with the content in the following format:
+
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="4c:f9:5d:d9:e8:ac", NAME="eth0"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="4c:f9:5d:d9:e8:ad", NAME="eth1"
+
+ - Configure the udev rules:
Write the MAC addresses and names of NICs except eth0 and eth1 obtained in step 2 (those not contained in the /etc/udev/rules.d/70-persistent-net.rules file) to the /etc/udev/rules.d/80-persistent-net.rules file so that the names and sequence of NICs do not change after the BMS is restarted.
+ Ensure that NIC MAC address and name are lowercase letters.
+
+vi /etc/udev/rules.d/80-persistent-net.rules
+The modification result is as follows:
+
+After the modification, press Esc, enter :wq, save the configuration, and exit.
+ - Run the following commands to copy the network configuration file /etc/sysconfig/network-scripts/ifcfg-bond0 to generate the /etc/sysconfig/network-scripts/ifcfg-bond1 file, and copy the /etc/sysconfig/network-scripts/ifcfg-eth0 file to generate the /etc/sysconfig/network-scripts/ifcfg-eth2 and /etc/sysconfig/network/ ifcfg-eth3 files:
cp -p /etc/sysconfig/network-scripts/ifcfg-bond0 /etc/sysconfig/network-scripts/ifcfg-bond1
+cp -p /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth2
+cp -p /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth3
+ - Run the following commands to edit the /etc/sysconfig/network-scripts/ifcfg-eth2 and /etc/sysconfig/network-scripts/ifcfg-eth3 files:
- vi /etc/sysconfig/network-scripts/ifcfg-eth2
Edit the eth2 network configuration file as follows:
+USERCTL=no
+MTU=8888
+NM_CONTROLLED=no
+BOOTPROTO=static
+DEVICE=eth2
+TYPE=Ethernet
+ONBOOT=yes
+MASTER=bond1
+SLAVE=yes
+Change the value of BOOTPROTO to static, that of DEVICE to the network device name eth2, and that of MASTER to the port name of the enhanced high-speed NIC bond (bond1). Retain values of other parameters.
+ - vi /etc/sysconfig/network-scripts/ifcfg-eth3
Edit the eth3 network configuration file as follows (similar to eth2):
+USERCTL=no
+MTU=8888
+NM_CONTROLLED=no
+BOOTPROTO=static
+DEVICE=eth3
+TYPE=Ethernet
+ONBOOT=yes
+MASTER=bond1
+SLAVE=yes
+
+ - Run the following command to edit the /etc/sysconfig/network-scripts/ifcfg-bond1 file:
vi /etc/sysconfig/network-scripts/ifcfg-bond1
+Edit the file as follows:
+MACADDR=40:7d:0f:52:e3:a5
+BONDING_MASTER=yes
+USERCTL=no
+ONBOOT=yes
+NM_CONTROLLED=no
+BOOTPROTO=static
+BONDING_OPTS="mode=1 miimon=100"
+DEVICE=bond1
+TYPE=Bond
+IPADDR=10.10.10.101
+NETMASK=255.255.255.0
+MTU=8888
+Where,
+- Change the value of MACADDR to the MAC address of eth2 or eth3.
- Change the value of BOOTPROTO to static.
- Change the value of DEVICE to bond1.
- Change the value of IPADDR to the IP address to be allocated to bond1. If the IP address planned for the enhanced high-speed network does not conflict with the VPC network segment, you can plan the IP address as needed, only to ensure that BMSs communicating through the enhanced high-speed network are in the same network segment as the enhanced high-speed network. An example value is 10.10.10.101.
- Set the value of NETMASK to the subnet mask of the IP address configured for enhanced high-speed network bond1.
+Retain values of other parameters.
+After the modification, press Esc, enter :wq, save the configuration, and exit.
+ - Run the following commands to enable port group bond1 of the enhanced high-speed network:
Run the following commands to start enhanced high-speed NICs eth2 and eth3:
+ifup eth2
+ifup eth3
+ifup bond1
+
+ - Perform the preceding operations to configure other BMSs.
- After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network of other BMSs from each BMS.
+
+
+
- Use a key or password to log in to the BMS as user root.
- On the BMS CLI, run the following command to check the NIC information:
ip link
+Information similar to the following is displayed.
+
+ The NIC whose MAC address starts with fa:16 is a network device that carries the VPC network, for example, eth0 and eth1. The NIC whose MAC address is that displayed in View Enhanced High-Speed NICs is a network device that carries the enhanced high-speed network, such as eth6 and eth7.
+
+ - Run the following commands to edit the /etc/sysconfig/network-scripts/ifcfg-eth6 and /etc/sysconfig/network-scripts/ifcfg-eth7 files:
- vi /etc/sysconfig/network-scripts/ifcfg-eth6
Edit the eth6 network configuration file as follows:
+USERCTL=no
+MTU=8888
+NM_CONTROLLED=no
+BOOTPROTO=static
+DEVICE=eth6
+TYPE=Ethernet
+ONBOOT=yes
+MASTER=bond1
+SLAVE=yes
+Change the value of BOOTPROTO to static, that of DEVICE to the network device name eth6, and that of MASTER to the port name of the enhanced high-speed NIC bond (bond1). Retain values of other parameters.
+ - vi /etc/sysconfig/network-scripts/ifcfg-eth7
Edit the eth7 network configuration file as follows (similar to eth6):
+USERCTL=no
+MTU=8888
+NM_CONTROLLED=no
+BOOTPROTO=static
+DEVICE=eth7
+TYPE=Ethernet
+ONBOOT=yes
+MASTER=bond1
+SLAVE=yes
+
+ - Run the following command to edit the /etc/sysconfig/network-scripts/ifcfg-bond1 file:
vi /etc/sysconfig/network-scripts/ifcfg-bond1
+Edit the file as follows:
+MACADDR=00:2e:c7:e0:b2:37
+BONDING_MASTER=yes
+USERCTL=no
+ONBOOT=yes
+NM_CONTROLLED=no
+BOOTPROTO=static
+BONDING_OPTS="mode=1 miimon=100"
+DEVICE=bond1
+TYPE=Bond
+IPADDR=10.10.10.101
+NETMASK=255.255.255.0
+MTU=8888
+Where,
+- Change the value of MACADDR to the MAC address of eth6 or eth7.
- Change the value of BOOTPROTO to static.
- Change the value of DEVICE to bond1.
- Change the value of IPADDR to the IP address to be allocated to bond1. If the IP address planned for the enhanced high-speed network does not conflict with the VPC network segment, you can plan the IP address as needed, only to ensure that BMSs communicating through the enhanced high-speed network are in the same network segment as the enhanced high-speed network. An example value is 10.10.10.101.
- Set the value of NETMASK to the subnet mask of the IP address configured for enhanced high-speed network bond1.
+Retain values of other parameters.
+After the modification, press Esc, enter :wq, save the configuration, and exit.
+ - Run the following commands to enable port group bond1 of the enhanced high-speed network:
Run the following commands to start enhanced high-speed NICs eth6 and eth7:
+ifup eth6
+ifup eth7
+ifup bond1
+
+ - Perform the preceding operations to configure other BMSs.
- After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network of other BMSs from each BMS.
+
+
To configure a VLAN, perform the following steps:
+
- Configure the corresponding VLAN sub-interfaces based on the VLAN to be configured. Assuming that the VLAN ID is 316, run the following command to edit the /etc/sysconfig/network-scripts/ifcfg-bond1.316 file:
vi /etc/sysconfig/network-scripts/ifcfg-bond1.316
+Edit the file as follows:
+USERCTL=no
+ONBOOT=yes
+NM_CONTROLLED=no
+BOOTPROTO=static
+DEVICE=bond1.316
+TYPE=Ethernet
+IPADDR=10.10.0.101
+NETMASK=255.255.255.0
+VLAN=yes
+PHYSDEV=bond1
+Where,
+- Change the value of DEVICE to the name of the new bond sub-interface.
- Change the value of IPADDR to the IP address to be allocated to bond1.316. If the IP address planned for the VLAN sub-interface of the enhanced high-speed NIC does not conflict with the VPC network segment, you can plan the IP address as needed, only to ensure that the BMSs communicating with each other through the VLAN sub-interface of the enhanced high-speed NIC are in the same network segment as the VLAN sub-interface of the enhanced high-speed NIC. An example value is 10.10.0.101.
- Set the value of NETMASK to the subnet mask of the IP address configured for enhanced high-speed NIC bond1.316.
+Retain values of other parameters.
+After the modification, press Esc, enter :wq, save the configuration, and exit.
+ - After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network VLAN sub-interface of other BMSs from each BMS.
+
+
+
Delete a NIC
- Obtain the IP address of the bonded enhanced high-speed NIC to be deleted.
- Use a key or password to log in to the BMS as user root.
- Locate the bond network device and run the following command to stop and delete the device: If the bond has VLAN sub-interfaces, they will be automatically deleted.
[root@bms-centos ~]# ifdown eth2
+[root@bms-centos ~]# ifdown eth3
+[root@bms-centos ~]# ifdown bond1
+[root@bms-centos ~]# ip link delete bond1
+[root@bms-centos ~]# ip link
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP qlen 1000
+ link/ether fa:16:00:6d:80:29 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP qlen 1000
+ link/ether fa:16:00:6d:80:29 brd ff:ff:ff:ff:ff:ff
+4: eth2: <BROADCAST,MULTICAST> mtu 8888 qdisc mq state DOWN qlen 1000
+ link/ether 40:7d:0f:52:e3:a5 brd ff:ff:ff:ff:ff:ff
+5: eth3: <BROADCAST,MULTICAST> mtu 8888 qdisc mq state DOWN qlen 1000
+ link/ether 40:7d:0f:52:e3:a6 brd ff:ff:ff:ff:ff:ff
+6: bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP
+ link/ether fa:16:00:6d:80:29 brd ff:ff:ff:ff:ff:ff
+ - Run the following commands to delete network configuration files /etc/sysconfig/network-scripts/ifcfg-eth2, /etc/sysconfig/network-scripts/ifcfg-eth3, and /etc/sysconfig/network-scripts/ifcfg-bond1:
rm -f /etc/sysconfig/network-scripts/ifcfg-eth2
+rm -f /etc/sysconfig/network-scripts/ifcfg-eth3
+rm -f /etc/sysconfig/network-scripts/ifcfg-bond1
+If a VLAN sub-interface exists, delete network configuration file /etc/sysconfig/network-scripts/ifcfg-bond1.vlan, where vlan indicates the VLAN ID of the VLAN sub-interface, for example, 316.
+rm -f /etc/sysconfig/network-scripts/ifcfg-bond1.316
+
+
+
Configuring an Enhanced High-Speed NIC (Ubuntu)
+This section uses Ubuntu 16.04 LTS (Xenial Xerus x86_64) as an example to describe how to bond enhanced high-speed NICs of a BMS.
+
The configuration methods of other Ubuntu OSs are similar to that of Ubuntu 16.04 LTS (Xenial Xerus x86_64).
+
+
Add a NIC
- Use a key or password to log in to the BMS as user root.
- On the BMS CLI, run the following command to check the NIC information:
ip link
+Information similar to the following is displayed:
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP group default qlen 1000
+ link/ether fa:16:00:9b:91:c3 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 8888 qdisc mq master bond0 state UP group default qlen 1000
+ link/ether fa:16:00:9b:91:c3 brd ff:ff:ff:ff:ff:ff
+4: p5p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether 40:7d:0f:52:e4:1d brd ff:ff:ff:ff:ff:ff
+5: p5p2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether 40:7d:0f:52:e4:1e brd ff:ff:ff:ff:ff:ff
+6: p4p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether 40:7d:0f:52:e3:a9 brd ff:ff:ff:ff:ff:ff
+7: p4p2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether 40:7d:0f:52:e3:aa brd ff:ff:ff:ff:ff:ff
+8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP group default qlen 1000
+ link/ether fa:16:00:9b:91:c3 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.254.85/24 brd 192.168.254.255 scope global bond0
+ valid_lft forever preferred_lft forever
+ inet6 fe80::f816:ff:fe9b:91c3/64 scope link
+ valid_lft forever preferred_lft forever
+9: bond0.3157@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP group default qlen 1000
+ link/ether fa:16:00:9c:1e:79 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.100.14/24 brd 192.168.100.255 scope global bond0.3157
+ valid_lft forever preferred_lft forever
+ inet6 fe80::f816:ff:fe9c:1e79/64 scope link
+ valid_lft forever preferred_lft forever
+10: bond0.3159@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8888 qdisc noqueue state UP group default qlen 1000
+ link/ether fa:16:00:0a:2e:8e brd ff:ff:ff:ff:ff:ff
+ inet 192.168.101.153/24 brd 192.168.101.255 scope global bond0.3159
+ valid_lft forever preferred_lft forever
+ inet6 fe80::f816:ff:fe0a:2e8e/64 scope link
+ valid_lft forever preferred_lft forever
+ eth0 and eth1 bear the VPC, and p5p1, p5p2, p4p1, and p4p2 bear the enhanced high-speed network. The following operations describe how to bond enhanced high-speed NICs p4p1 and p4p2.
+
+ - Run the following command to check whether the /etc/udev/rules.d/ directory contains the 80-persistent-net.rules file:
ll /etc/udev/rules.d/ | grep 80-persistent-net.rules
+- If yes, and the file contains all NICs except bond0 and lo obtained in step 2 and their MAC addresses, go to step 6.
- If no, go to step 4.
+ - Run the following command to copy the /etc/udev/rules.d/70-persistent-net.rules file and name the copy as /etc/udev/rules.d/80-persistent-net.rules.
cp -p /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/80-persistent-net.rules
+ - Configure the udev rules:
Add the NICs and their MAC addresses obtained in step 2, except lo, eth0, eth1, and bond0, to the /etc/udev/rules.d/80-persistent-net.rules file. This ensures that the names and sequence of NICs will not change after the BMS is restarted.
+ Ensure that NIC MAC address and name are lowercase letters.
+
+vim /etc/udev/rules.d/80-persistent-net.rules
+The modification result is as follows:
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:4c:7f:5d:b6:fc", NAME="eth0"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:4c:7f:5d:b6:fd", NAME="eth1"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:7d:0f:52:e4:1d", NAME="p5p1"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:7d:0f:52:e4:1e", NAME="p5p2"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:7d:0f:52:e3:a9", NAME="p4p1"
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:7d:0f:52:e3:aa", NAME="p4p2"
+After the modification, press Esc, enter :wq, save the configuration, and exit.
+ - Run the following command to copy the /etc/network/interfaces.d/50-cloud-init.cfg file to generate the /etc/network/interfaces.d/60-cloud-init.cfg file:
cp -p /etc/network/interfaces.d/50-cloud-init.cfg /etc/network/interfaces.d/60-cloud-init.cfg
+ If the /etc/network/interfaces.d/50-cloud-init.cfg file does not exist, copy the /etc/network/interfaces file and run the following commands:
+
mkdir /etc/network/interfaces.d
+
cp -p /etc/network/interfaces /etc/network/interfaces.d/60-cloud-init.cfg
+
+ - Run the following command to edit the /etc/network/interfaces.d/60-cloud-init.cfg file of devices p4p1 and p4p2:
vim /etc/network/interfaces.d/60-cloud-init.cfg
+Edit the file as follows:
+auto p4p1
+iface p4p1 inet manual
+bond_mode 1
+bond-master bond1
+bond_miimon 100
+mtu 8888
+
+auto p4p2
+iface p4p2 inet manual
+bond_mode 1
+bond-master bond1
+bond_miimon 100
+mtu 8888
+
+auto bond1
+iface bond1 inet static
+bond_miimon 100
+bond-slaves none
+bond_mode 1
+address 10.10.10.103
+netmask 255.255.255.0
+hwaddress 40:7d:0f:52:e3:a9
+mtu 8888
+Parameters are as follows:
+- p4p1 and p4p2 are the names of the NICs that carry the enhanced high-speed network.
- hwaddress is the MAC address of p4p1.
- Change the value of address to the IP address allocated to enhanced high-speed network bond1. If the IP address planned for the enhanced high-speed network does not conflict with the VPC network segment, you can plan the IP address as needed, only to ensure that BMSs communicating through the enhanced high-speed network are in the same network segment as the enhanced high-speed network.
- Set the value of netmask to the subnet mask of the IP address configured for enhanced high-speed network bond1.
+Set values of other parameters. For example, set mtu to 8888, bond_miimon to 100, and bond_mode to 1.
+After the modification, press Esc, enter :wq, save the configuration, and exit.
+ - Run the following command to enable the bond NIC:
ifup p4p1
+ifup p4p2
+ p4p1 and p4p2 are the NICs bearing the enhanced high-speed network.
+
+ - Run the following commands to check the NIC device status and whether the bond1 configuration file takes effect:
ip link
+
+ifconfig
+
+ - Perform the preceding operations to configure other BMSs.
- After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network of other BMSs from each BMS.
For example, run the ping 10.10.10.102 command. The command output is as follows:
+[root@bms-ubuntu ~]# ping 10.10.10.102 -I bond1
+PING 10.10.10.102 (10.10.10.102) from 10.10.10.103 bond1: 56(84) bytes of data.
+64 bytes from 10.10.10.102: icmp_seq=1 ttl=64 time=0.681 ms
+64 bytes from 10.10.10.102: icmp_seq=2 ttl=64 time=0.035 ms
+64 bytes from 10.10.10.102: icmp_seq=3 ttl=64 time=0.031 ms
+64 bytes from 10.10.10.102: icmp_seq=4 ttl=64 time=0.030 ms
+^C
+--- 10.10.10.102 ping statistics ---
+4 packets transmitted, 4 received, 0% packet loss, time 3342ms
+
+
+
To configure a VLAN, perform the following steps:
+
- Configure the corresponding VLAN sub-interfaces based on the VLAN to be configured. Assuming that the VLAN ID is 316, run the following command to edit the /etc/network/interfaces.d/60-cloud-init.cfg file:
vim /etc/network/interfaces.d/60-cloud-init.cfg
+Edit the file as follows:
+auto p4p1
+iface p4p1 inet manual
+bond_mode 1
+bond-master bond1
+bond_miimon 100
+mtu 8888
+
+auto p4p2
+iface p4p2 inet manual
+bond_mode 1
+bond-master bond1
+bond_miimon 100
+mtu 8888
+
+auto bond1
+iface bond1 inet static
+bond_miimon 100
+bond-slaves none
+bond_mode 1
+address 10.10.10.103
+netmask 255.255.255.0
+hwaddress 40:7d:0f:52:e3:a9
+mtu 8888
+
+auto bond1.316
+iface bond1.316 inet static
+bond_miimon 100
+bond-slaves none
+bond_mode 1
+address 10.10.0.103
+netmask 255.255.255.0
+hwaddress 40:7d:0f:52:e3:a9
+mtu 8888
+ - Run the following command to enable the VLAN sub-interface of the bond NIC:
ifup bond1.316
+ - After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network VLAN sub-interface of other BMSs from each BMS.
+
+
Delete a NIC
- Obtain the IP address of the bonded enhanced high-speed NIC to be deleted.
- Use a key or password to log in to the BMS as user root.
- Locate the bond network device and run the following command to stop and delete the device: If the bond has VLAN sub-interfaces, they will be automatically deleted.
[root@bms-ubuntu ~]# ifdown p4p1
+[root@bms-ubuntu ~]# ifdown p4p2
+[root@bms-ubuntu ~]# ifdown bond1
+ - Run the following command to delete network configuration file /etc/network/interfaces.d/60-cloud-init.cfg:
rm -f /etc/network/interfaces.d/60-cloud-init.cfg
+
+
+
Configuring an Enhanced High-Speed NIC (Windows Server)
+This section uses Windows Server 2012 R2 Standard as an example to describe how to configure an enhanced high-speed network bond of a BMS.
+
The configuration methods of other Windows Server OSs are similar to that of Windows Server 2012 R2 Standard.
+
+
Add a NIC
- Log in to a Windows BMS.
- On the Windows PowerShell CLI of the BMS, run the following command to check the NIC information:
Get-NetAdapter
+Information similar to the following is displayed.
+
+ eth0 and eth1 bear the VPC, and eth3 and eth4 bear the enhanced high-speed network bond. The following steps use eth2 and eth3 to configure the enhanced high-speed network.
+
+ - To improve the outbound traffic on the OS, perform the operations in Method 1. If there is no special requirement on traffic, perform the operations in Method 2.
- Method 1: Use the switch standalone mode for the bond in the OS. The outbound traffic is distributed across all active NICs, and the inbound traffic is received through one of the NICs in the team.
+- Run the following command to create a bond port group for the enhanced high-speed network:
New-NetLbfoTeam -Name qinq -TeamMembers "eth2","eth3" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic -Confirm:$false
+
+ In the command, qinq is the name of the port group planned for the enhanced high-speed network, and eth2 and eth3 are the network devices that bear the enhanced high-speed network obtained in 2.
+
+ - Run the following command to query the network adapters:
get-NetLbfoTeamMember
+
+Get-NetAdapter
+
+
+- Method 2: Use the active/standby mode for the bond in the OS.
+- Run the following command to create a bond port group for the enhanced high-speed network:
New-NetLbfoTeam -Name Team2 -TeamMembers "eth2","eth3" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm IPAddresses -Confirm:$false
+
+ In the command, Team2 is the name of the port group planned for the enhanced high-speed network, and eth2 and eth3 are the network devices that bear the enhanced high-speed network obtained in 2.
+
+ - Run the following command to set a network port of port group Team2 created in 3.a to the standby port:
Set-NetLbfoTeamMember -Name "eth3" -AdministrativeMode Standby -Confirm:$false
+ The port group configured for the enhanced high-speed network supports only the active/standby mode. eth3 is one of the ports of the port group. You can determine which port is configured as the standby port based on your planning.
+
+get-NetLbfoTeamMember
+
+Get-NetAdapter
+
+
+ - Run the following command to enter the Network Connections page:
ncpa.cpl
+Then enter the following page.
+
+ - Configure the enhanced high-speed network.
- On the Network Connections page, double-click port group Team2 created in 3 to switch to the Team2 Status page.
- Click Next to switch to the Team2 Properties page.
- On the Networking tab page, double-click Internet Protocol Version 4 (TCP/IPv4) to switch to the Internet Protocol Version 4 (TCP/IPv4) Properties page.
- Select Use the following IP address, configure the IP address and subnet mask, and click OK.
+ If the IP address planned for the enhanced high-speed network does not conflict with the VPC network segment, you can plan the IP address as needed, only to ensure that BMSs communicating through the enhanced high-speed network are in the same network segment as the enhanced high-speed network.
+
+
+ - Perform the preceding operations to configure other BMSs.
- After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network of other BMSs from each BMS.
+
+
+
Delete a NIC
- Log in to a Windows BMS.
- On the Windows PowerShell CLI of the BMS, run the following command to query information about the bonded enhanced high-speed NICs to be deleted:
Get-NetLbfoTeamNIC -Team Team2
+
+ - Run the following command to delete the bonded NICs:
Remove-NetLbfoTeam -Name "Team2"
+
+ - Run the following commands to query the NIC information and verify that the NIC is deleted:
Get-NetAdapter
+
+
+
+
For more information about the IPoIB communication mode, see https://www.kernel.org/doc/Documentation/infiniband/ipoib.txt.
View IB Networks
IB networks are presented to you through the BMS specifications shown in Figure 1. You need to configure and plan the VLANs and IP addresses.
-
Figure 1 BMS extended configuration
+
Figure 1 BMS extended configuration
diff --git a/docs/bms/umn/en-us_topic_0128546229.html b/docs/bms/umn/en-us_topic_0128546229.html
index d66a6189..6dd8225d 100644
--- a/docs/bms/umn/en-us_topic_0128546229.html
+++ b/docs/bms/umn/en-us_topic_0128546229.html
@@ -8,7 +8,13 @@
-
2023-03-06
+ |
2024-09-20
+ |
+Modified the following content:
+
+ |
+
+2023-03-06
|
Modified the following content:
Added a new flavor in Instance Family.
@@ -114,13 +120,13 @@
| Added the following content:
Modified the following content:
-
+
|
2018-04-30
|
Modified the following content:
-
+
|
2018-03-30
@@ -137,7 +143,7 @@
|
2018-02-28
|
Modified the following content:
-
+
|
2018-02-12
@@ -153,15 +159,13 @@
| Added the following content:
Retrieving Metadata
Modified the following content:
-
+- Optimized the description of the shared EVS disk and deleted EVS disk types that are not supported in section EVS Disk.
- Deleted unnecessary application scenarios of licenses in section License Type.
- Optimized the description of Cloud-Init in section Cloud-Init.
- Optimized the description of the image in section Overview.
- Deleted the description of Dedicated Cloud (DeC) in section Related Services.
- Optimized the description of the security group in section Adding Security Group Rules.
|
2018-01-30
|
Added the following content:
-
-Modified the following content:
-Added the operations to install dependency packages in section Installing the NVIDIA GPU Driver and CUDA Toolkit on a P1 BMS.
+
|
2018-01-25
@@ -173,7 +177,7 @@
|
2017-12-30
|
Added the following content:
-
+
Modified the following content:
- Optimized descriptions in section EVS Disk.
- Adjusted the document structure in sections Network.
|
@@ -275,7 +279,7 @@
2017-05-05
|
Modified the following content:
-
+
|
2017-04-28
diff --git a/docs/bms/umn/en-us_topic_0140740386.html b/docs/bms/umn/en-us_topic_0140740386.html
deleted file mode 100644
index aae78720..00000000
--- a/docs/bms/umn/en-us_topic_0140740386.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-Installing the NVIDIA GPU Driver and CUDA Toolkit on a P2 BMS
-ScenariosAfter a GPU-accelerated P2 BMS (using the physical.p2.large flavor) is created, the NVIDIA GPU driver and CUDA Toolkit must be installed on it for computing acceleration.
-
- Prerequisites- An EIP has been bound to the BMS.
- You have obtained the required driver installation packages.
-
-
-
- CentOS 7.4- Log in to the target BMS and run the following command to switch to user root:
su root
- - (Optional) If the gcc, gcc-c++, make, and kernel-devel dependency packages do not exist, run the following commands to install the gcc, gcc-c++, make, and kernel-devel tools:
yum install gcc
-yum install gcc-c++
-yum install make
-yum install kernel-devel-`uname -r`
- - (Optional) Add the Nouveau driver to the blacklist.
If the Nouveau driver has been installed and loaded, perform the following operations to add the Nouveau driver to the blacklist to avoid conflicts:
-- Add blacklist nouveau to the end of the /etc/modprobe.d/blacklist.conf file.
- Run the following commands to back up and reconstruct initramfs:
mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak
-dracut -v /boot/initramfs-$(uname -r).img $(uname -r)
- - Run the reboot command to restart the BMS.
- - (Optional) If the X service is running, run the systemctl set-default multi-user.target command and restart the BMS to enter multi-user mode.
- (Optional) Install the NVIDIA GPU driver.
If you selected a specified version of NVIDIA GPU driver rather than a version contained in the CUDA Toolkit, perform this step.
-- Download NVIDIA GPU driver installation package NVIDIA-Linux-x86_64-xxx.yy.run from https://www.nvidia.com/Download/index.aspx?lang=en, and upload this package to the /tmp directory on the BMS.
Figure 1 Searching for the NVIDIA GPU driver package (CentOS 7.4)
- - Run the following command to install the NVIDIA GPU driver:
sh ./NVIDIA-Linux-x86_64-xxx.yy.run
- - Run the following command to delete the installation package:
rm -f NVIDIA-Linux-x86_64-xxx.yy.run
-
- - Install the CUDA Toolkit.
- Download CUDA Toolkit installation package cuda_a.b.cc_xxx.yy_linux.run from https://developer.nvidia.com/cuda-downloads, and upload this package to the /tmp directory on the BMS.
- Run the following command to change the permission to the installation package:
chmod +x cuda_a.b.cc_xxx.yy_linux.run
- - Run the following command to install the CUDA Toolkit:
./cuda_a.b.cc_xxx.yy_linux.run -toolkit -samples -silent -override --tmpdir=/tmp/
- - Run the following command to delete the installation package:
rm -f cuda_a.b.cc_xxx.yy_linux.run
- - Run the following commands to check whether the installation is successful:
cd /usr/local/cuda/samples/1_Utilities/deviceQueryDrv/
-make
-./deviceQueryDrv
-If the command output contains "Result = PASS", the CUDA Toolkit and the NVIDIA GPU driver have been installed successfully.
-
-
-
- Obtaining the Password of a Windows BMS
-ScenariosPassword authentication mode is required to log in to a Windows BMS. Therefore, you must use the key file used when you created the BMS to obtain the administrator password generated when the BMS was initially installed. The administrator user is Administrator or the user configured using Cloudbase-Init. This password is randomly generated, offering high security.
+ ScenariosPassword authentication mode is required to log in to a Windows BMS. Therefore, you must use the key file used when you created the BMS to obtain the administrator password generated when the BMS was initially installed. The administrator user is Administrator or the user configured using Cloudbase-Init. This password is randomly generated, offering high security.
PrerequisitesYou have obtained the private key file used during BMS creation.
diff --git a/docs/bms/umn/en-us_topic_0140749123.html b/docs/bms/umn/en-us_topic_0140749123.html
index f7753851..fb253263 100644
--- a/docs/bms/umn/en-us_topic_0140749123.html
+++ b/docs/bms/umn/en-us_topic_0140749123.html
@@ -10,6 +10,16 @@
- Setting the Source/Destination Check for a NIC
+ - Configuring a NIC (SUSE Linux Enterprise Server 12)
+
+ - Configuring a NIC (SUSE Linux Enterprise Server 11)
+
+ - Configuring a NIC (Red Hat, CentOS, Oracle Linux, and EulerOS)
+
+ - Configuring a NIC (Ubuntu)
+
+ - Configuring a NIC (Windows Server)
+
diff --git a/docs/bms/umn/en-us_topic_0160902759.html b/docs/bms/umn/en-us_topic_0160902759.html
new file mode 100644
index 00000000..1cdd82cf
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0160902759.html
@@ -0,0 +1,23 @@
+
+
+ Adding an Enhanced High-Speed NIC
+ This section describes how to add an enhanced high-speed NIC to a BMS.
+ ConstraintsThe BMS must be in Running state.
+
+ Procedure A BMS has a maximum of two enhanced high-speed NICs and depends on the total bandwidth of the extension NICs. For example, if the total bandwidth allowed for the extension NICs is 2 x 10GE and the bandwidth of the first enhanced high-speed NIC is 2 x 10GE, you cannot add another enhanced high-speed NIC.
+ You can view the total bandwidth of extension NICs in the Extended Configuration column in Flavor.
+ - If a flavor's Extended Configuration contains 2*10GE (for example, the Extended Configuration of flavor physical.h2.large is 1*100G IB + 2*10GE), BMSs of this flavor has only one NIC without extension NIC, and the total bandwidth of extension NICs is 0.
- If a flavor's Extended Configuration contains 2 x 2*10GE (for example, the Extended Configuration of flavor physical.s3.large is 2 x 2*10GE), BMSs of this flavor has two NICs, of which one is an extension NIC, and the total bandwidth of extension NICs is 2*10GE.
+
+ - Log in to the management console.
- Under Computing, click Bare Metal Server.
The BMS console is displayed.
+ - Click the name of the target BMS.
The page showing details of the BMS is displayed.
+ - Click the NICs tab. Then, click Add NIC.
- Set the NIC type to enhanced high-speed NIC and select the bandwidth.
- Click OK.
+
+
+
+
+
diff --git a/docs/bms/umn/en-us_topic_0160902760.html b/docs/bms/umn/en-us_topic_0160902760.html
new file mode 100644
index 00000000..334a50d3
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0160902760.html
@@ -0,0 +1,22 @@
+
+
+ Deleting an Enhanced High-Speed NIC
+ ScenariosYou can delete an enhanced high-speed NIC if you do not need it any longer.
+
+ ConstraintsThe BMS must be in Running or Stopped state.
+
+ Procedure- Log in to the management console.
- Under Computing, click Bare Metal Server.
The BMS console is displayed.
+ - Click the name of the target BMS.
The page showing details of the BMS is displayed.
+ - Click the NICs tab, locate the target enhanced high-speed NIC, click
 to expand its details, and make a note of the MAC address. After deleting a NIC on the console, you need to log in to the BMS OS and perform related operations to delete the device (the MAC address recorded will be used).
+
+ - Click Delete.
- Click Yes.
+
+
+
+
+
diff --git a/docs/bms/umn/en-us_topic_0170795326.html b/docs/bms/umn/en-us_topic_0170795326.html
new file mode 100644
index 00000000..83d38653
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0170795326.html
@@ -0,0 +1,29 @@
+
+
+ Enhanced High-Speed Network
+
+
+
diff --git a/docs/bms/umn/en-us_topic_0170795327.html b/docs/bms/umn/en-us_topic_0170795327.html
new file mode 100644
index 00000000..9649eb63
--- /dev/null
+++ b/docs/bms/umn/en-us_topic_0170795327.html
@@ -0,0 +1,39 @@
+
+
+ Overview
+ Enhanced High-Speed NetworkFigure 1 Enhanced high-speed network architecture
+ An enhanced high-speed network is a high-quality, high-speed, and low-latency internal network for BMSs to communicate with each other. It has the following features:
+ - Networks for high-speed internal interconnection
- Internal networks that you can customize
- A total bandwidth greater than 10 Gbit/s
+ Hardware and software in high-speed networks are upgraded to provide enhanced high-speed networks. Figure 2 shows the architecture of the high-speed network and Figure 3 shows a comparison between the architectures of the high-speed network and enhanced high-speed network.
+ Figure 2 High-speed network architecture
+ Figure 3 Comparison between the high-speed network and enhanced high-speed network
+ Compared with the high-speed network, the enhanced high-speed network has the following advantages:
+
+ View Enhanced High-Speed NICsYou can view the network interfaces of the enhanced high-speed network on the NICs tab page of the BMS details page.
+ Figure 4 Viewing enhanced high-speed NICs
+
+ Application ScenariosThe enhanced high-speed NIC applies to the following scenarios:
+ - Scenario 1: bonding
When bonding enhanced high-speed NICs, you can choose whether to configure VLANs based on network planning.
+- Do not configure VLANs.
If no VLAN is required, you can configure IP addresses and subnet masks directly when bonding enhanced high-speed NICs. After the configuration is complete, enhanced high-speed NICs on the same network can communicate with each other.
+ - Configure VLANs.
If VLANs are required, you can configure VLAN sub-interfaces after bonding enhanced high-speed NICs.
+
+ - Scenario 2: no bonding
If you use enhanced high-speed NICs directly without bonding them, you cannot configure VLANs or configure IP addresses or subnet masks. After the configuration is complete, enhanced high-speed NICs on the same network can communicate with each other.
+ A single enhanced high-speed NIC also supports bonding.
+
+
+ Configuring an Enhanced High-Speed NIC (SUSE Linux Enterprise Server 12) to Configuring an Enhanced High-Speed NIC (Windows Server) describe how to bond enhanced high-speed NICs in the OS. The configuration method varies depending on the OS.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/bms/umn/en-us_topic_0204212311.html b/docs/bms/umn/en-us_topic_0204212311.html
index e347400d..488369d2 100644
--- a/docs/bms/umn/en-us_topic_0204212311.html
+++ b/docs/bms/umn/en-us_topic_0204212311.html
@@ -1,6 +1,6 @@
- How Do Two BMSs in the Same Region But Different AZs Communicate with Each Other?
+ How Do BMSs in Different AZs of the Same Region Communicate with Each Other?
If they are in the same VPC, they communicate with each other through an internal network. If they are on the same subnet of a VPC, they communicate with each other through the layer-2 network. If they are on different subnets of a VPC, they communicate with each other through the layer-3 network. An EIP must be bound to the primary NIC of each BMS so that they can communicate with each other.
diff --git a/docs/bms/umn/en-us_topic_0204289807.html b/docs/bms/umn/en-us_topic_0204289807.html
index 50681ff7..3157dfa3 100644
--- a/docs/bms/umn/en-us_topic_0204289807.html
+++ b/docs/bms/umn/en-us_topic_0204289807.html
@@ -1,7 +1,7 @@
- Can I Configure the EIP?
- No. The EIP is automatically allocated from the DHCP address pool.
+ Can I Configure an EIP?
+ No. EIPs are automatically allocated from the DHCP address pool.
diff --git a/docs/bms/umn/en-us_topic_0263802108.html b/docs/bms/umn/en-us_topic_0263802108.html
index 89841661..cd2229ba 100644
--- a/docs/bms/umn/en-us_topic_0263802108.html
+++ b/docs/bms/umn/en-us_topic_0263802108.html
@@ -2,137 +2,50 @@
OSs Supported by Different Types of BMSs
The following tables list the 64-bit OSs supported by different BMS types.
- - Table 1 lists the OSs supported by compute-optimized physical.o2.medium BMSs.
- Table 2 lists the OSs supported by GPU-accelerated P1 and P2 BMSs.
- Table 3 lists the OSs supported by high-performance computing physical.h2.large BMSs.
- Table 4 lists the OSs supported by memory-optimized M2 BMSs.
- Table 5 lists the OSs supported by I/O optimized physical.i7n.28xlarge.4 BMSs.
+ Table 1 lists the OSs supported by high-performance computing physical.h2.large BMSs.
+ Table 2 lists the OSs supported by I/O optimized physical.i7n.28xlarge.4 BMSs.
- It is recommended that you use the official OS release versions. Do not tailor or customize the release versions, or problems may occur.
- OS vendors do not always update OS release versions regularly. Some versions are no longer maintained, and these deprecated versions no longer receive security patches. Ensure that you read the update notifications from OS vendors and update your OS so that it runs properly.
- For CentOS 7.4 or earlier, BMS extension NICs cannot be pinged due to known kernel issues. So, you are advised to use CentOS 7.5 or later. For details, see How Do I Handle the Failure to Ping a CentOS 7 Extension NIC?
- Table 1 Compute-optimized physical.o2.mediumOS
+Table 1 High-performance computing physical.h2.largeOS
|
-Version
+ | Version
|
|---|
-Windows
+ | CentOS
|
-Windows Server 2012 R2 Standard
-Windows Server 2016 Standard
+ | CentOS 6.9/7.3/7.4/7.5/7.6
|
-CentOS
+ | SUSE
|
-CentOS 6.7/6.8/6.9/7.2/7.3/7.4/7.5/7.6
+ | SUSE Linux Enterprise 11.SP4/12.SP1/12.SP2/12.SP3
|
-Red Hat
+ | Ubuntu
|
-Red Hat 6.7/6.8/6.9/7.2/7.3/7.4/7.5
+ | Ubuntu 16.04 LTS
|
-SUSE
+ | EulerOS
|
-SUSE Linux Enterprise 11.SP4/12.SP1/12.SP2/12.SP3
- |
-
-Ubuntu
- |
-Ubuntu 14.04 LTS
-Ubuntu 14.04.5 LTS
-Ubuntu 16.04 LTS
- |
-
-Oracle Linux
- |
-Oracle Linux 6.9/7.4
- |
-
-EulerOS
- |
-EulerOS 2.2/2.3
+ | EulerOS 2.3
|
Table 2 GPU-accelerated P1 and P2OS
+Table 2 I/O-optimized physical.i7n.28xlarge.4OS
|
-Version
+ | Version
|
|---|
-CentOS
+ | Ubuntu
|
-CentOS 7.4/7.5/7.6
- |
-
-Ubuntu
- |
-Ubuntu 16.04 LTS
- |
-
-EulerOS
- |
-EulerOS 2.3
- |
-
-
-
- Table 3 High-performance computing physical.h2.largeOS
- |
-Version
- |
-
|---|
-
-CentOS
- |
-CentOS 6.9/7.3/7.4/7.5/7.6
- |
-
-SUSE
- |
-SUSE Linux Enterprise 11.SP4/12.SP1/12.SP2/12.SP3
- |
-
-Ubuntu
- |
-Ubuntu 16.04 LTS
- |
-
-EulerOS
- |
-EulerOS 2.3
- |
-
-
-
- Table 4 Memory-optimized M2OS
- |
-Version
- |
-
|---|
-
-CentOS
- |
-CentOS 7.2/7.3/7.4/7.5/7.6
- |
-
-
-
- Table 5 I/O-optimized physical.i7n.28xlarge.4OS
- |
-Version
- |
-
|---|
-
-Ubuntu
- |
-Ubuntu 22.04 LTS
+ | Ubuntu 22.04 LTS
|
|
|---|
|
|---|
|
