Installing the Agent on Linux

Scenarios

You need to install the Agent on the Linux source server to be migrated. During the installation, you need to enter the AK/SK pair of the Huawei Cloud account you are migrating to. After the Agent is started, it automatically reports source server information to SMS. The information is used for migration only. For details, see What Information Does SMS Collect About Source Servers?

Prerequisites

You have obtained the AK/SK pair of your Huawei Cloud account.
- If you use an IAM user for migration, obtain an AK/SK pair by referring to How Do I Create an AK/SK Pair for an IAM User?
- If you use an account for migration, obtain an AK/SK pair by referring to How Do I Create an AK/SK Pair for an Account?

You have confirmed that the source server OS is supported by SMS. For details, see Supported Linux OSs.

Procedure

Log in to the SMS console.
In the navigation pane on the left, choose Agents.
In the Linux area, click Agent. Read carefully and agree to the service statement and click OK. Copy the command for downloading Agent installation file and run the command on the source server.
In the Click SHA256 File. Copy the command for downloading the SHA256 file and run the command on the source server. Use the hash value contained in the SHA256 file to verify the integrity of the Agent installation package. For details, see How Do I Verify the Integrity of the Agent Installation File?
Decompress the Agent software package.
```
tar -zxvf SMS-Agent.tar.gz
```
Switch to the SMS-Agent directory on the source server.
```
cd SMS-Agent
```
If you need to use an HTTP/HTTPS proxy, go to 8.
If you do not need to use an HTTP/HTTPS proxy, go to 9.
- If your source server cannot access Huawei Cloud over the Internet, a proxy server can help you. You need to configure a proxy by yourself.
- The proxy is used for registering the source server with SMS when a Direct Connect or VPN connection is used. It is not used for data migration.
Configure an HTTP/HTTPS proxy.
1. Go to the config directory.
```
cd SMS-Agent/agent/config
```
2. Open and edit the auth.cfg file. Do not edit the auth.cfg file unless you need to use an HTTP/HTTPS proxy.
```
vi auth.cfg
```
  The values shown here are for reference only.
```
[proxy-config]
enable = true
proxy_addr = https://your-proxy-addr.com 
proxy_port = 3128
proxy_user = root
use_password = true
```
  - enable: To use the proxy, set it to true.
  - proxy_addr: Enter the IP address of the proxy server. The proxy is used by the source server to access SMS. This IP address is different from the IP address of the target server. Use the protocol configured for your proxy server. HTTPS is recommended.
  - proxy_user: Enter the username for logging in to the proxy server. If no username is required, leave it blank.
  - use_password: If a password is required for logging in to the proxy server, set it to true. If none is required, set it to false.
3. Save the auth.cfg file and exit.
```
:wq
```
Start the Agent.
```
./startup.sh
```
Carefully review what information will be collected by the Agent, enter y, and press Enter.

Figure 1 Entering y
Enter the AK/SK pair of the Huawei Cloud account and the SMS domain name in the region you are migrating to. You can obtain the SMS domain name on the Agents page of the SMS console, as shown in Figure 3.

Figure 2 Entering the AK/SK pair

Figure 3 Obtaining the SMS domain name

You must enable the EPS service for the Huawei Cloud account you migrate to. When you start the Agent installed on a source server, the Agent lists all enterprise projects the account is allowed to access. You can select the enterprise you desire. Then the server will be migrated to the enterprise project. This enables you to isolate permissions, resources, and finance during the migration. For details, see Migrating Servers into an Enterprise Project.

When the following information is displayed, the Agent has been started up and will start reporting source server information to SMS. You can go to the Servers page on the SMS console to view the record of the source server.
Figure 4 Agent running