Updated on 2024-05-21 GMT+08:00

Discovering Resources over an Intranet

This section describes how to discover on-premises infrastructure with limited Internet access. You need to install Edge in the on-premises environment to discover resources by network range or VMware host.

Precautions

  • Only VMs in VMware vSphere 5.0 to 7.0 can be discovered.
  • When the system scans VMware VMs or scans servers on specified network ranges, private IP addresses and the ID of the involved Edge device are used to identify discovered servers. If the private IP address of a discovered server, the server will be identified as a new one during the next collection, and the total number of discovered servers will increase. To avoid this, you are advised not to change private IP addresses of source servers before the migration is complete.

Prerequisites

  • You have installed Edge in the source intranet environment and have connected the Edge device with MgC.
  • You have added source server credentials to the Edge device.

    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 account and password
    • Windows: Administrator account and password

Creating a Discovery Task

  1. Log in to the MgC console.
  2. In the navigation pane on the left, choose Research > Application Discovery. Select a migration project in the upper left corner of the page.
  3. If you are first-time user of MgC, click Discover Over Intranet in the Edge Discovery area.

    If you are not a first-time user of MgC, choose Discover > Over Intranet in the Discovery Task card.

  4. Configure a discovery task based on Table 1.

    Table 1 Parameters for creating an intranet-based discovery task

    Parameter

    Description

    Task Name

    Specify a name for the task.

    Task Description

    Describe the task.

    Device

    Select the device where Edge was installed in the source intranet environment.

  5. Enable Scan Network Range or Scan VMware VMs to discover servers as needed.

    • If Scan Network Range is enabled, configure parameters listed in Table 2.
      Table 2 Parameters for scanning a network range

      Parameter

      Description

      Protocol

      Select the communication protocol TCP or ICMP.

      Network Range

      There are three supported IP address ranges:

      • 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 Linux servers. This parameter is available only if you choose the TCP protocol. If you need to skip Linux servers during the scan, set this parameter to 0.

      Windows

      Enter the port for scanning Windows servers. This parameter is available only if you choose the TCP protocol. If you need to skip Windows servers during the scan, set this parameter to 0.

    • If Scan VMware VMs is enabled, enter the IP address of a vCenter Server in the IP Address text box, and select the credential for accessing the vCenter Server. All VMs managed by the vCenter Server will be discovered. If the vCenter Server's credential has not been added, click Create to add it to MgC by referring to Adding Resource Credentials. When adding the credential, enter the username and password for logging in to the vCenter Server.

  6. Click Confirm. An intranet-based discovery task is created, and MgC starts collecting details about source servers.

    On the Application Discovery page, click View next to Total tasks to go to the task list and view the task status.

  7. Wait until the task status changes to Succeeded, and perform a deeper discovery. Servers discovered on an intranet have an Edge device associated. You just need to associated credentials with these servers before you can perform a deeper discovery.

    1. On the Application Discovery page, click the Resources tab and click the number in the Server row.
    2. Locate a server and click Associate in the Credential column.
    3. Select the server credential. If the credential has not been added to MgC, go to the Edge console and add the server credential to the Edge device and synchronize it to MgC.
    4. Click OK. MgC checks the credential association status. When the collection status is Ready, click Discover in the Status column to perform a deeper discovery. You can click Rediscover in the Status column to perform a second deeper discovery if needed.