IP 범위 스캔을 사용하면 네트워크에서 애셋을 감지하고 사용자 인증 정보를 확인하며 감지된 애셋에서 데이터를 수집할 수 있습니다. 수집된 데이터에는 가상 머신(VM) 인스턴스 및 물리적 서버를 포함하여 머신에서 실행 중인 애플리케이션에 대한 데이터와 머신 구성, 하드웨어, 네트워크, 열린 파일, 서비스, 프로세스 등에 대한 세부정보가 포함됩니다.
IP 범위 스캔은 다음 시나리오에서 유용합니다.
마이그레이션 센터 탐색 클라이언트 CLI가 Azure에서 실행 중인 VM 또는 온프레미스 인프라에서 실행 중인 머신과 같이 인벤토리 검색을 지원하지 않는 환경에서 애셋을 스캔하려는 경우
IP 범위에 머신이 여러 개 있거나 스캔하려는 인프라를 잘 모르는 경우
vCenter API에 대한 액세스 권한이 없더라도 VMware에서 실행되는 VM의 전체 스캔을 수행하려면 게스트 검색 대신 IP 범위 스캔을 사용하면 됩니다.
AWS API에 대한 액세스 권한이 없더라도 AWS에서 실행되는 VM의 전체 스캔을 수행하려면 게스트 검색 대신 IP 범위 스캔을 사용하면 됩니다.
IP 범위 스캔은 2단계 프로세스입니다.
먼저 mcdc CLI에서 IP 주소를 스캔하여 인프라에서 애셋을 감지합니다.
그런 다음 감지된 애셋에서 평가를 수행하는 데 필요한 데이터를 스캔합니다.
mcdc CLI은 Linux 및 Windows 대상 머신 모두에 대해 IP 범위 스캔을 통한 데이터 수집을 지원합니다.
IP 범위 스캔 중에 mcdc CLI는 SSH를 사용하여 Linux 머신에 연결하고 WMI를 사용하여 Windows 머신에 연결합니다.
IP 범위 스캔은 SSH 또는 WMI를 사용하여 원격으로 게스트 검색을 실행하는 데이터와 동일한 데이터를 수집합니다.
IP_RANGE를 스캔하려는 단일 IP 주소나 IP 주소 범위로 바꿉니다. IP 범위는 하이픈으로 연결하거나 CIDR 표기법으로 표시할 수 있습니다.
예를 들면 0.0.0.0-0.0.0.3 또는 0.0.0.0/30입니다. --ranges 플래그를 여러 개 사용하여 한 번에 범위를 두 개 이상 지정할 수 있습니다.
스캔이 완료되면 수집된 데이터는 호스트 머신에 mcdc CLI를 설치한 로컬 디렉터리와 동일한 로컬 디렉터리에 저장됩니다. 또한 같은 디렉터리에 CSV 파일이 생성되어 성공 및 실패한 스캔에 대한 세부정보를 제공합니다.
이 CSV 파일에 다른 위치를 지정하려면 discover ips 명령어와 함께 --output-file을 사용하면 됩니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-01-23(UTC)"],[],[],null,["# Run an IP range scan\n\nThis document describes the steps to run an IP range scan using the\n`mcdc` CLI.\n\nOverview\n--------\n\nIP range scan lets you detect assets on the network, verify credentials, and\ncollect data from the detected assets. The collected data includes data about\nthe running applications on your machines, which includes both virtual machine\n(VM) instances and physical servers, and details about the machine\nconfiguration, hardware, network, as well as open files, services, and\nprocesses.\n\nIP range scan is useful in the following scenarios:\n\n- If you want to scan assets on environments for which the Migration Center discovery client CLI doesn't support [inventory discovery](/migration-center/docs/run-inventory-discovery), such as VMs running on Azure or machines running in your on-premises infrastructure.\n- If you have have several machines in an IP range, or you don't have much knowledge about the infrastructure you want to scan.\n- If you want to do a complete scan of VMs running on VMware even if you lack access to the vCenter API, you can use IP range scan as an alternative to [guest discovery](/migration-center/docs/run-guest-discovery).\n- If you want to do a complete scan of VMs running on AWS even if you lack access to the AWS API, you can use IP range scan as an alternative to guest discovery.\n\nIP range scan is a two-step process:\n\n- First, the `mcdc` CLI scans IP addresses to detect assets in your infrastructure.\n- Then, it scans the detected assets for data required to perform an assessment.\n\nThe `mcdc` CLI supports data collection through\nIP range scan for both Linux and Windows target machines.\nDuring the IP range scan, the `mcdc` CLI connects to\nLinux machines using SSH, and to Windows machines using\nWindows Management Instrumentation (WMI).\nIP range scan collects the same data as running a guest discovery remotely\nwith SSH or WMI.\n\nTo scan an environment with both Windows and Linux machines, run\n`mcdc` CLI from a Windows workstation. Windows\nmachines require WMI for connection during scanning, and WMI is only\nsupported on Windows workstations.\n\nBefore you begin\n----------------\n\n1. Review the [requirements for downloading and running the\n `mcdc` CLI](/migration-center/docs/review-collector-cli-requirements).\n2. Complete the steps to [download `mcdc` CLI](/migration-center/docs/download-collector-cli).\n\nRun an IP scan to discover assets\n---------------------------------\n\n- To detect assets in your infrastructure, run the following command:\n\n\n ### Linux\n\n \u003cbr /\u003e\n\n ```\n ./mcdc discover ipscan --ranges IP_RANGE\n ```\n\n \u003cbr /\u003e\n\n ### Windows\n\n \u003cbr /\u003e\n\n ```\n mcdc.exe discover ipscan --ranges IP_RANGE\n ```\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n Replace \u003cvar translate=\"no\"\u003eIP_RANGE\u003c/var\u003e with a single IP address or a range\n of IP addresses that you want to scan. The IP ranges can be hyphenated or in\n [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).\n For example, `0.0.0.0-0.0.0.3` or `0.0.0.0/30`. You can specify more than one\n range at a time using multiple `--ranges` flags.\n- Alternatively, you can specify a file that contains a list of IP ranges to scan:\n\n\n ### Linux\n\n \u003cbr /\u003e\n\n ```\n ./mcdc discover ipscan --file IP_RANGE_FILE.csv\n ```\n\n \u003cbr /\u003e\n\n ### Windows\n\n \u003cbr /\u003e\n\n ```\n mcdc.exe discover ipscan --file IP_RANGE_FILE.csv\n ```\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n Replace \u003cvar translate=\"no\"\u003eIP_RANGE_FILE\u003c/var\u003e with the name of the CSV file which contains\n the range of IP addresses you want to scan. The file must contain\n comma-separated ranges or ranges in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).\n Following in an example of an IP range file: \n\n rangeStart,rangeEnd,CIDR\n 192.168.9.0,192.168.9.255,\"\"\n \"\",\"\",192.168.10.0/24\n\n| **Note:** You can specify ranges using either the `--ranges` flag or `--file` flag. You can't use both of these flags in a single command.\n\nThis command then outputs a CSV file containing the list IP addresses of the\ndetected assets. The file looks similar to the following example: \n\n ipAddress\n 192.168.9.1\n 192.168.9.2\n\nThis file is used as an input for the next step, which is to\nscan and collect data on the detected assets. By default, this file is saved in\nthe same directory where you installed the `mcdc` CLI.\n\nScan the discovered assets\n--------------------------\n\n1. After you've scanned your infrastructure and have the file containing a list\n of discovered IPs, run a scan on the discovered assets:\n\n\n ### Linux\n\n \u003cbr /\u003e\n\n ```\n ./mcdc discover ips --file SCANNED_IPS.csv\n ```\n\n \u003cbr /\u003e\n\n ### Windows\n\n \u003cbr /\u003e\n\n ```\n mcdc.exe discover ips --file SCANNED_IPS.csv\n ```\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eSCANNED_IPS\u003c/var\u003e: the path to the file generated by the `discover ipscan` command which contains a list of the IP addresses of your discovered assets.\n2. When prompted, accept the terms and conditions.\n\n Optionally, to skip this step and accept the terms and conditions in\n the previous step, you can include the `--accept-terms` flag with the\n `discover ips` command command.\n3. When prompted, enter the credentials using JSON format:\n\n - Enter username and password:\n\n [{\"username\":\"\u003cvar translate=\"no\"\u003eUSERNAME\u003c/var\u003e\",\"password\":\"\u003cvar translate=\"no\"\u003ePASSWORD\u003c/var\u003e\"}]\n\n - Enter username and specify the path to the identity file:\n\n [{\"username\":\"\u003cvar translate=\"no\"\u003eUSERNAME\u003c/var\u003e\",\"identityFile\":\"\u003cvar translate=\"no\"\u003eIDENTITY_FILE\u003c/var\u003e\"}]\n\n - Enter the username, specify the path to the encrypted identity file, and\n enter the passphrase:\n\n [{\"username\":\"\u003cvar translate=\"no\"\u003eUSERNAME\u003c/var\u003e\",\"identityFile\":\"\u003cvar translate=\"no\"\u003eIDENTITY_FILE\u003c/var\u003e\",\"passphrase\":\"\u003cvar translate=\"no\"\u003ePASSPHRASE\u003c/var\u003e\"}]\n\n If required, you can specify multiple credentials at a time: \n\n [{\"username\":\"\u003cvar translate=\"no\"\u003eFIRST_USERNAME\u003c/var\u003e\",\"password\":\"\u003cvar translate=\"no\"\u003eFIRST_PASSWORD\u003c/var\u003e\"},{\"username\":\"\u003cvar translate=\"no\"\u003eSECOND_USERNAME\u003c/var\u003e\",\"password\":\"\u003cvar translate=\"no\"\u003eSECOND_PASSWORD\u003c/var\u003e\"}]\n\nAfter the scan is complete, the collected data is saved in the same local\ndirectory where you installed the `mcdc` CLI on the host\nmachine. Additionally, a CSV file is also generated in the same directory,\nwhich provides you with the details about the successful and unsuccessful scans.\nIf you want to specify a different location for this CSV file, you can use the\n`--output-file` with the `discover ips` command.\n\nWhat's next\n-----------\n\n- Learn how to [export collected data to Migration Center](/migration-center/docs/export-collected-data)."]]
