Intranet Discovery

Notes and Constraints

• Only VMs in VMware vSphere 5.0 to 7.0 can be discovered.
• When the system scans for VMware VMs or scans for servers on specific network ranges, it uses the servers' private IP addresses and the ID of the used MgC Agent to identify discovered servers. If a server's private IP address changes after the server is discovered, the server will be identified as a new one during the next discovery, and the total number of discovered servers will increase. To avoid this, do not change private IP addresses for source servers before the migration is complete.
• Performance data of VMware VMs within a specified period can be collected during the automatical scan. For discovered VMs, a separate performance collection is not necessary.
• The performance data collected during the VMware VM scanning comes from the historical data stored in the vCenter. The default data retention policy in the vCenter is as follows:
  • One day: Data points are collected every 5 minutes.
  • One week: Data points are collected every 30 minutes.
  • One month: Data points are collected every two hours.

Prerequisites

• You have installed the MgC Agent in the source intranet environment and have connected the MgC Agent to MgC.
• You have added source server credentials to the MgC Agent.
  NOTICE:

  To perform a deep collection for your source servers to collect as much as details, provide server credentials that meet the following requirements:

  • Linux: root and its password
  • Windows: administrator and its password

Creating an IDC Discovery Task

1. Sign in to the MgC console. In the navigation pane, under Project, select an application migration project from the drop-down list.
2. In the navigation pane, choose Discover > Source Resources.
3. Click the Intranet Discovery tab and select the environment where your source servers run.
   Figure 1 Selecting the source environment
   

4. To configure an IDC discovery task, set the parameters by referring to Table 1.

   Table 1 Parameters for configuring an IDC discovery task

   Parameter	Description
   Task Name	Enter a task name.
   Task Description	Describe the task.
   MgC Agent	Select the MgC Agent installed in the source intranet environment.
   Protocol	Only TCP is available.
   Network Range	Enter an IP address range which must fall within: 10.0.0.0 – 10.255.255.255 172.16.0.0 – 172.31.255.255 192.168.0.0 - 192.168.255.255
   Linux	Enter the port for scanning for Linux servers. If you do not need to scan for Linux servers, set the port number to 0.
   Windows	Enter the port for scanning Windows servers. If you do not need to scan for Windows servers, set the port number to 0.
   Application	Select the application that you want to group the discovered servers into. If no applications are available, perform the following steps to create one: Click Create Application, enter an application name and description, select a business scenario and running environment, and select the region where the application resources will be deployed on the target cloud. Click OK.

5. Click Confirm. After the IDC discovery task is created, MgC starts discovering source resources.
6. Wait until the discovery task succeeds, return to the Source Resources page and perform a deep collection for the discovered servers.
   1. On the Source Resources page, in the server list, for each server whose details need to be collected, click Configure in the MgC Agent column.
   2. Configure the parameters listed in Table 2.

      Table 2 Parameters for configuring a deep collection

      Parameter	Configuration
      Type	Set this parameter based on the source server OS type.
      MgC Agent	Select the MgC Agent installed in the source environment.
      Access IP Address	Select the IP address for accessing the source server. It can be a public or private IP address. After the pre-migration check is passed, the IP address you select here will be used for migration.
      Port	Enter the port on the source server that allows access from the MgC Agent. By default, port 5985 on Windows source servers must be opened to the MgC Agent. The port cannot be changed. By default, port 22 on Linux source servers must be opened to the MgC Agent. You can specify a different port if needed.
      Credential	Select the server credential. If the credential is not displayed in the list, go to the MgC Agent console, add the server credential, and synchronize it to MgC.

   3. Click Confirm. Then the system automatically starts executing a deep collection. When Collected shows up in the Deep Collection column, the collection is complete. You can proceed to create a migration solution or create a migration plan.

Creating a VMware Discovery Task

1. Sign in to the MgC console. In the navigation pane, under Project, select an application migration project from the drop-down list.
2. In the navigation pane, choose Discover > Source Resources.
3. Click the Intranet Discovery tab and select the environment where your source servers run.
   Figure 2 Selecting the source environment
   

4. To configure a VMware discovery task, set the parameters by referring to Table 3.

   Table 3 Parameters for configuring a VMware discovery task

   Parameter	Description
   Task Name	Enter a task name.
   Task Description	Describe the task.
   MgC Agent	Select the MgC Agent installed in the source intranet environment.
   IP Address	Enter the IP address of the vCenter Server for discovering the managed VMs.
   Port	Enter the port for accessing the vCenter Server.
   Credential	Select the credential for accessing vCenter. If the drop-down list is empty, go to the MgC Agent console and add the credential. Set the resource type to Private cloud and enter the username and password for logging in to the vCenter Server.
   Application	Select the application that you want to group the discovered servers into. If no applications are available, perform the following steps to create one: Click Create Application, enter an application name and description, select a business scenario and running environment, and select the region where the application resources will be deployed on the target cloud. Click OK.

5. Click Confirm. After the VMware discovery task is created, MgC starts discovering source resources.
6. Wait until the discovery task succeeds, return to the Source Resources page and perform a deep collection for the discovered servers.
   1. On the Source Resources page, in the server list, for each server whose details need to be collected, click Configure in the MgC Agent column.
   2. Configure the parameters listed in Table 4.

      Table 4 Parameters for configuring a deep collection

      Parameter	Configuration
      Type	Set this parameter based on the source server OS type.
      MgC Agent	Select the MgC Agent installed in the source environment.
      Access IP Address	Select the IP address for accessing the source server. It can be a public or private IP address. After the pre-migration check is passed, the IP address you select here will be used for migration.
      Port	Enter the port on the source server that allows access from the MgC Agent. By default, port 5985 on Windows source servers must be opened to the MgC Agent. The port cannot be changed. By default, port 22 on Linux source servers must be opened to the MgC Agent. You can specify a different port if needed.
      Credential	Select the server credential. If the credential is not displayed in the list, go to the MgC Agent console, add the server credential, and synchronize it to MgC.

   3. Click Confirm. Then the system automatically starts executing a deep collection. When Collected shows up in the Deep Collection column, the collection is complete. You can proceed to create a migration solution or create a migration plan.