Deploying the MgC Agent (Formerly Edge)

Preparations

• Prepare a Linux server for installing the MgC Agent in the source intranet environment. The Linux server must:
  • Be able to access the Internet and the domain names of MgC, IoTDA, and other cloud services. For details about the domain names to be accessed, see Domain Names.
  • Allow the ports required by the MgC Agent (formerly Edge). For details about the required ports, see Communication Matrix.
  • Allow outbound traffic on 8883 if the server is in a security group.
  • Run CentOS 8.X.
  • Have at least 4 CPUs and 8 GB of memory. If you want to use big data verification, the server must have at least 8 CPUs and 16 GB of memory.
  CAUTION:

  Do not install the MgC Agent on a source server to be migrated.

  • High resource consumption: The MgC Agent consumes CPU and memory resources during collection and migration. If a large number of migration tasks are performed by the MgC Agent, services on the source server may be affected.
  • Port occupation: The MgC Agent occupies some ports on the server, which may affect services running on it.
• Run the following command to check whether rng-tools is installed on the Linux server where the MgC Agent is installed:

  rpm -qa | grep rng-tools
  If no rng-tools-related information is displayed, rng-tools is not installed on the server. Run the following command to install rng-tools:

  yum -y install rng-tools
• Disable any antivirus and protection software on the Linux server where the MgC Agent is installed. This type of software may stop the MgC Agent from executing migration commands, resulting in migration failures.
• Add an inbound rule to the security group of the Linux server to allow TCP traffic on port 27080. Set the source address to the IP address of the Windows server you use to log in to the MgC Agent console.

  

• Sign up for a HUAWEI ID and enable Huawei Cloud services, and obtain an AK/SK pair for the account.
• Create a migration project on the MgC console.

Downloading and Installing the MgC Agent

1. Sign in to the MgC console from the Linux server you prepared.
2. In the navigation pane on the left, choose MgC Agents.
3. In the Linux area, click Download Installation Package or Copy Download Command to download the MgC Agent installation program to the Linux server.
4. Decompress the MgC Agent installation package.

   tar zxvf Edge.tar.gz

5. Go to the scripts directory in the decompressed MgC Agent directory.

   cd Edge/scripts/

6. Run the MgC Agent installation script.

   ./install.sh

7. Enter the EIP bound to the NIC of the Linux server. The IP address will be used for accessing the MgC Agent console. If the entered IP address is not used by the Linux server, the system will prompt you whether to use any public IP address of the Linux server as the MgC Agent access address.

   

8. Check if the message shown in the following figure is displayed. If it is, the MgC Agent for Linux has been installed. The port in the following figure is for reference only. Note the actual port returned. Generally, the port is 27080.

   

   Update environment variables.

   source /etc/profile

9. On the Windows server for which an inbound rule is added to the security group of the server where the MgC Agent is installed, open a browser and enter https://<IP-address-entered-in-step-7>:<port-obtained-in-step-8> in the address box to access the user registration page of the MgC Agent. For example, if the IP address entered in step 7 is 192.168.x.x and the port returned in step 8 is 27080, the MgC Agent access address is https://192.168.x.x:27080.
   NOTICE:

   If there are access problems, check the IP address entered in the address box and the inbound rule settings of the security group of the Linux server with the MgC Agent installed.

Registering an Account

When you log in to the MgC Agent console for the first time, you must set a username and password. Keep the username and password secure.

1. On the Register page, specify a username and password, confirm the password, and click Privacy Statement.

   

2. Read the privacy statement carefully before selecting I have read and agree to the Privacy Statement, and click Register.
   CAUTION:

   You are advised to change your password for accessing the MgC Agent every three to six months.

Connecting the MgC Agent to MgC

1. Use the registered account to log in to the MgC Agent console.
2. On the Overview page, click Connect in the upper right corner. The Connect to MgC page is displayed on the right.
   Figure 1 Connecting the MgC Agent to MgC
   

3. In Step 1: Enter Cloud Credential, select the region where your MgC migration project is located, enter the AK/SK of your Huawei Cloud account, and click Query Project. After the MgC Agent is authenticated using the entered AK/SK pair, you can go to the next step. If the system displays a message indicating that the AK/SK pair is incorrect, try to rectify the fault by following the instructions in What Can I Do If the AK/SK Verification Fails?
   NOTICE:

   If your source servers need to be migrated, the entered AK/SK pair must have permissions to use SMS. For details, see SMS Custom Policies.

   Determine whether to save the entered AK/SK pair as the target credential which will be used for migrating your workloads to Huawei Cloud.

   • If you select No, the entered AK/SK pair will be deleted after the MgC Agent is connected to MgC.
   • If you select Yes, the entered AK/SK pair will be encrypted and saved locally after the connection to MgC is established. When you migrate workloads to Huawei Cloud, the AK/SK pair will be delivered to SMS-Agent on the source servers for executing the migration.

4. In Step 2: Select MgC Migration Project, select a migration project from the project drop-down list. The MgC Agent will report the collected information about your source resources to this project.
5. In Step 3: Preset MgC Agent Name, specify a name for the MgC Agent, which will be displayed on the MgC console, and click Next. Confirm the connection to MgC, and click OK.
   CAUTION:

   After the MgC Agent is connected to MgC, the name you specified here cannot be modified.

6. If Connected shows up on the overview page, the connection to MgC is successful.

Adding Resource Credentials

You can add credentials of the following types of resources to the MgC Agent: private clouds, servers, big data clusters, and containers. For details about the authentication methods supported for each resource type, see Table 1.

1. Use the registered username and password to log in to the MgC Agent console.
2. In the navigation pane, choose Agent-based Discovery > Credentials.
3. Click Create Certificate above the list.
   Figure 2 Adding a credential
   

4. Select a resource type and authentication method as prompted. Specify a credential name, enter your credentials, and click Confirm.
   • If the MgC Agent is not connected to MgC, the added resource credentials can be used for deep collection.
   • If the MgC Agent is connected to MgC, the added resource credentials will be automatically synchronized to MgC.