- A general-purpose ECS supports up to 12 NICs, while an H1 ECS supports up to 4 NICs. Therefore, before changing the ECS type, ensure that the number of NICs of the general-purpose ECS is less than or equal to four.
- After changing the ECS type, do not uninstall the driver. Otherwise, the H1 ECS may fail to access the network.
- After the OS of an ECS is reinstalled or switched, the SR-IOV driver becomes invalid. If SR-IOV is required, reinstall the SR-IOV driver.
- A general-purpose ECS running one of the following OSs can be changed to an H1 ECS:
- Windows Server 2016 DataCenter 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 Standard 64bit
- Windows Server 2012 DataCenter 64bit
- Windows Server 2012 R2 DataCenter 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2012 R2 Essentials 64bit
- Windows Server 2008 R2 DataCenter 64bit
- Windows Server 2008 R2 DataCenter SP1 64bit
- Windows Server 2008 R2 Enterprise 64bit
- Windows Server 2008 R2 Enterprise SP1 64bit
- Windows Server 2008 R2 WEB 64bit
- Windows Server 2008 R2 Standard 64bit
- Windows Server 2008 R2 Standard SP1 64bit
- CentOS 6.3/6.4/6.5/6.6/6.7/6.8/6.9 64bit
- CentOS 7.0/7.1/7.2/7.3/7.4 64bit
- Debian 8.0/8.4/8.5/8.6 32bit
- Debian 8.0/8.4/8.5/8.6/8.8 64bit
- Debian 9.0 64bit
- OpenSUSE 42.3 64bit
- OpenSUSE 42.2 64bit
- Ubuntu Server 16.10 32bit
- Ubuntu Server 16.10/16.04.2/16.04 64bit
- SUSE Linux Enterprise Server 11 SP2/SP3/SP4 64bit
- SUSE Linux Enterprise Server 12 64bit
- SUSE Linux Enterprise Server 12 SP1/SP2/SP3 64bit
- Red Hat Linux Enterprise 6.8/6.9/7.0/7.2/7.3/7.4 64bit
- Fedora 25 64bit
- Fedora 26 64bit
- Oracle Enterprise Linux 6.8/6.9 64bit
- Oracle Enterprise Linux 7.3/7.4 64bit
- CoreOS 1185.5.0 64bit
- CoreOS 1298.5.0 64bit
- CoreOS 1298.6.0 64bit
- CoreOS 1298.7.0 64bit
- CoreOS 1353.8.0 64bit
- EulerOS 2.2 64bit
- The available space in drive C of a Windows ECS is greater than 300 MB, and data can be written to it.
The available space in root directory of a Linux ECS is greater than 300 MB, and data can be written to it.
- DHCP is enabled in the VPC to which the ECS belongs.
- The ECS network connectivity is normal.
- The ECS security group rule in the outbound direction meets the following requirements:
- Protocol: TCP
- Port Range: 80
- Remote End: 169.254.0.0/16
If you use the default security group rule in the outbound direction, the preceding requirements are met, and the ECS can be initialized. The default security group rule in the outbound direction is as follows:
- Protocol: ANY
- Port Range: ANY
- Remote End: 0.0.0.0/16
Step 1: Configure the ECS and Enable SR-IOV for Enhanced Networking
- Log in to the ECS as user Administrator.
- Download an Intel NIC driver required by the OS running on the ECS. Table 1 lists the URLs for downloading the Intel NIC drivers required by the ECSs without an EIP bound.
- Intel driver 126.96.36.199 has been delivered with Windows Server 2012 R2. You are advised to use Pnputil.exe provided by the OS to upgrade the driver to the latest version.
- There are many restrictions on using a browser to download software for a Windows ECS. To improve the download efficiency, download the software to a Linux ECS and use a file server to share the software with the target Windows ECS.
- Find the downloaded driver file in the Download folder and decompress it.
- Press Win+R and enter cmd to switch to CLI.
- Open the folder that contains the driver and run the following command to add and install the INF file in the driver store using Pnputil:
- Log in to the ECS.
- Run the following command to switch to user root:
- Download the driver sriov.zip according to Table 1.
- Switch to the directory in which the driver is downloaded and decompress sriov.zip.
- Run the following command to configure the system so that it supports SR-IOV devices (the /tmp directory is used as an example):
Step 2: Modify the Specifications for Changing a General-Purpose ECS to an H1 ECS
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, view the status of the target ECS.
If the ECS is not in Stopped state, click More in the Operation column and select Stop.
- Click More in the Operation column and select Modify Specifications.
The Modify ECS Specifications page is displayed.
- Select the new ECS type, vCPUs, and memory as prompted.
- (Optional) Set DeH.
If the ECS is created on a DeH, the system allows you to change the DeH.
To do so, select the target DeH from the drop-down list. If no DeH is available in the drop-down list, remaining DeH resources are insufficient and cannot be used to create the ECS with specifications modified.
- Select the check box to confirm the ECS configuration.
- Click OK.
- On the Modify ECS Specifications page, confirm the modified vCPU and memory specifications and click Submit.
Step 3: Verify the Specifications Modification
After the specifications are modified, check whether all NICs can be identified to verify the modification.
- Right-click My Computer.
- Choose Properties > Device Manager.
- Check whether all NIC drivers in Network adapters are of the 82599 type.
- If yes, the enhanced SR-IOV network has taken effect, and the specifications have been modified.
Figure 1 Enhanced network
- If no, the NICs are unavailable. In such an event, right-click the NIC with a question mark (?) and choose update driver > search automatically from the shortcut menu.
The methods of verifying specifications modification for CentOS and Ubuntu OSs are the same. If NIC drivers are ixgbevf and of the 82599 type, the SR-IOV enhanced network has been enabled and the specifications have been modified. To do so, perform the following operations:
- Run the following command to check whether the NIC drivers are of the 82599 type:
lspci | grep 82599
If the information marked in the red box of Figure 2 is displayed, the NIC drivers are of the 82599 type.
Figure 2 82599 NIC drivers
- Run the following command to check whether the drivers are ixgbevf:
ethtool -i $nic
An example is provided as follows:
If the NIC name is ens5, run the following command:
ethtool -i ens5