[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-11。"],[],[],null,["# Discover VM instances on VMware\n\nThis document describes the steps to run an inventory discovery on your\nVMware environment using the Migration Center discovery client CLI.\n\nBefore you begin\n----------------\n\n1. Review the [requirements for downloading and running the `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 inventory discovery on VMware using vSphere API\n------------------------------------------------------\n\nUse the vSphere API to collect data about all VMs in a vCenter visible to\nthe user running the `mcdc` CLI. You can also scope a\ndiscovery to a specific folder, cluster, or data center.\n\n### Configure vCenter\n\nIf you plan to export the collected data to Migration Center,\nbefore you run an inventory discovery, you need to configure your vCenter\nenvironment.\nThe data you collect with `mcdc` CLI, in fact, depend on\nthe settings for statistics in vCenter.\n\nvCenter supports four levels of statistics:\n\n- Level 1 exposes only CPU and memory performance.\n- Level 2 exposes the network performance.\n- Level 3 exposes input/output operations per second (IOPS).\n- Level 4 exposes all the available metrics.\n\nFor a detailed list of the available metrics for all statistics levels, see\n[Data collection levels](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-25800DE4-68E5-41CC-82D9-8811E27924BC.html).\n\nBy default, the statistics level is set to level 1. Levels 1 and 2 let you\ncollect partial data about your infrastructure, while level 3 lets you\ncollect everything you need to generate a complete total cost of ownership (TCO)\nreport.\nAfter the statistics level is changed in vCenter, it might take several\nhours for performance data to become available.\n\nFor more information on how to change statistics levels in vCenter, see\n[Configure statistics collection intervals in the vSphere client](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-5D85751A-2CE8-4FD5-83C8-90A17060631E.html).\n\n### Run the discovery\n\n1. In the command line terminal, change to the directory where you downloaded the `mcdc` CLI.\n2. Run the discovery:\n\n\n ### Linux\n\n \u003cbr /\u003e\n\n ```\n ./mcdc discover vsphere -u USERNAME --url https://VSPHERE_URL\n ```\n\n \u003cbr /\u003e\n\n ### Windows\n\n \u003cbr /\u003e\n\n ```\n mcdc.exe discover vsphere -u USERNAME --url https://VSPHERE_URL\n ```\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eUSERNAME\u003c/var\u003e: your vCenter username\n - \u003cvar translate=\"no\"\u003eVSPHERE_URL\u003c/var\u003e: the URL for your vCenter Server instance or the vSphere Client\n\n To avoid a certificate check for connecting to the vCenter,\n include the `-i` (insecure) flag in the command.\n3. When prompted, enter the vCenter password.\n\nAfter the inventory discovery is complete, the collected data is stored in the\nlocal database.\n\n### Scope a discovery\n\n- Run the discovery at the root:\n\n\n ### Linux\n\n \u003cbr /\u003e\n\n ```\n ./mcdc discover vsphere --url https://VSPHERE_URL -u USERNAME --path /\n ```\n\n \u003cbr /\u003e\n\n ### Windows\n\n \u003cbr /\u003e\n\n ```\n mcdc.exe discover vsphere --url https://VSPHERE_URL -u USERNAME --path /\n ```\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n- Run the discovery at a specific folder:\n\n\n ### Linux\n\n \u003cbr /\u003e\n\n ```\n ./mcdc discover vsphere --url https://VSPHERE_URL -u USERNAME --path DATACENTER/vm/FOLDER\n ```\n\n \u003cbr /\u003e\n\n ### Windows\n\n \u003cbr /\u003e\n\n ```\n mcdc.exe discover vsphere --url https://VSPHERE_URL -u USERNAME --path DATACENTER/vm/FOLDER\n ```\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eDATACENTER\u003c/var\u003e: the name of the data center\n - \u003cvar translate=\"no\"\u003eFOLDER\u003c/var\u003e: the path to the folder\n- Run the discovery at a specific cluster:\n\n\n ### Linux\n\n \u003cbr /\u003e\n\n ```\n ./mcdc discover vsphere --url https://VSPHERE_URL -u USERNAME --path DATACENTER/host/CLUSTER\n ```\n\n \u003cbr /\u003e\n\n ### Windows\n\n \u003cbr /\u003e\n\n ```\n mcdc.exe discover vsphere --url https://VSPHERE_URL -u USERNAME --path DATACENTER/host/CLUSTER\n ```\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eCLUSTER\u003c/var\u003e: the name of the cluster\n- Run the discovery at a specific data center:\n\n\n ### Linux\n\n \u003cbr /\u003e\n\n ```\n ./mcdc discover vsphere --url https://VSPHERE_URL -u USERNAME --path DATACENTER\n ```\n\n \u003cbr /\u003e\n\n ### Windows\n\n \u003cbr /\u003e\n\n ```\n mcdc.exe discover vsphere --url https://VSPHERE_URL -u USERNAME --path DATACENTER\n ```\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\nTo avoid a certificate check for connecting to the vCenter, include the\n`-i` (insecure) flag in the command.\n\nRun an inventory discovery on VMware using RVTools\n--------------------------------------------------\n\nFor VMs running on VMware, the `mcdc` CLI lets you analyze\nthe XLSX report files generated with\n[RVTools](https://www.robware.net/rvtools/).\n\n- Collect data based on your existing RVTools export:\n\n\n ### Linux\n\n \u003cbr /\u003e\n\n ```\n ./mcdc discover rvtools REPORT_NAME.xlsx\n ```\n\n \u003cbr /\u003e\n\n ### Windows\n\n \u003cbr /\u003e\n\n ```\n mcdc.exe discover rvtools REPORT_NAME.xlsx\n ```\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n Replace \u003cvar translate=\"no\"\u003eREPORT_NAME\u003c/var\u003e with the path to the XLSX generated\n with RVTools.\n\nHowever, this method has following limitations:\n\n- The `mcdc` CLI doesn't support tables generated with the `--DBColumnNames` flag in RVTools.\n- The `mcdc` CLI doesn't support exporting the data collected using this method to Migration Center. However, you can use it to [run an offline assessment](/migration-center/docs/run-offline-assessment).\n\nWhat's next\n-----------\n\n- Learn how to [run a guest discovery](/migration-center/docs/run-guest-discovery).\n- Learn how to [export collected data to Migration Center](/migration-center/docs/export-collected-data)."]]
