VMware VCenter Converter ports
Different VMware converter ports are required for communication, depending on the conversion of a Windows or Linux host. Also, compared to the ports required for vmware converter p2v, V2V operations require fewer ports.
VMware VCenter Converter ports
local PC (windows 10) is on my domain. remote win server 2016 fresh install is in a workgroup. both have different subnets. They can see each other so the connection is good, for example, i can remote to the server from my local machine that is on domain. dont want to install directly on the server (it works) and also dont want to turn off the firewall (this works too) but still doesnt make sense that i cant run the converter even though i have opened all the ports that i have found that needed to be opened, however, still get message "unable to contact the specified host the host might not be available on the network" etc.
Cisco Collaboration apps will explicitly indicate which Major/Minor versions they support (e.g. ESXi 4.0, 4.1, 5.0, 5.1, 5.5). There is no "or later" ... unlisted versions are not tested/supported.With a particular supported major/minor version (such as ESXi 5.1)...A Cisco Collaboration app will only specifiy a minimum maintenance release (e.g. 5.1 U1) if required by its guest OS or for hardware compatibility.A Cisco Collaboration app will only specify a MAXIMUM maintenance release if there are known incompatibilitites. To date this has never been the case, so if the hardware vendor supports it, it is allowed even if unlisted. Cisco recommendation is to use the latest Maintenance release supported by the hardware vendor.Cisco Collaboration apps do not prescribe or proscribe individual ESXi patches and updates. Cisco recommendation is to apply the latest patches and updates recommended by VMware and your hardware vendor. The following links can be used to determine if an individual Maintenance Release or patch "can" or "should" be deployed:VMware Compatibilty Guide ( ) for the the vSphere ESXi Major/Minor version supported by Cisco Collaboration.Server Vendor's hardware compatiblity information for the vSphere ESXi Major/Minor version required by Cisco Collaboration. E.g. for Cisco UCS, see the Server Compatiblity documents at _technical_reference_list.html.Always verify with server vendor if a hardware-vendor-specific ESXi image is required. E.g. you want to upgrade from 5.0 to 5.0 U3. If the server is Cisco UCS, you may need to use a UCS-specific image for U3 on vmware.com.Always verify with server vendor that the update is compatible with server model's bios/firmware/driver state. E.g. 5.0 U3 on UCS C220 M3 SFF, check the UCS interop matrix to see if any updates required before U3 will work on that hardware.Before applying a VMware upgrade or update to a host, always verify compatibility with each Cisco Collaboration app (At a Glance table at -collaboration.)Note that use of VMware vSphere ESXi 4.1 requires disabling the "LRO" setting (click here for details).For details on "legacy" virtualization support (i.e. 7.x of UC apps with VMware vSphere on limited 3rd-party servers), see the following links:Cisco Unity Virtualization Design GuideVirtualization Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted 7.5(3)Virtual Machine Version (vmv)The vmv represents the version of virtual hardware. New ESXi versions may increase the latest vmv version, but new ESXi versions support older vmv versions (see vmware.com for information on compability of old vmv versions with new ESXi versions, such as this vmware.com KB article for compatibility for ESXi version with vmv version). Cisco Collaboration apps do not require or even use most of the new features in new vmv versions (e.g. larger VMs, more virtual HW options, etc.). Cisco Collaboration apps only require vmv4 functionality, so a newer vmv is usually transparent. To date, Cisco has not discovered any issues with Collaboration apps due to a newer vmv version. Cisco-provided/required OVA files will be for the specific vmv version used when testing the ESXi major/minor version (e.g. OVAs for ESXi 5.x include vmv7 and vmv8). For customers using vSphere Client instead of vCenter, it is NOT recommended to upgrade to a newer vmv. E.g. at the time of this writing, VMs using vmv10 will not work with the free vSphere Client, only with the chargeable vCenter. Otherwise, unless indicated NOT to by a Cisco Collaboration app, customers are free to manually upgrade the vmv to a newer vmv supported by the ESXi version. Cisco does not produce OVA files for newer vmv versions, or test newer vmv versions since VMware indicates these are backwards compatible. Virtual Machine File System (VMFS)If ESXi 6.5, all applications support VMFS5 but only some support VMFS6 (check each application's virtualization page for details). Note: ESXi 6.0 only supports VMFS5.For older ESXi releases, the VMFS is transparent to Cisco Collaboration apps, but recommend using the latest version offered for the major/minor version of VMware vSphere ESXi you are deploying on. VMware ToolsVMware Tools are specialized drivers for virtual hardware that is installed in the UC applications when they are running virtualized. It is very important that the VMware tools version running in the UC application be in sync with the version of ESXi being used.If VMware tools status does not show "OK" from the viClient, the VMware Tools must be upgraded.It is important to understand that the UC application is not tied to the version of ESXi it is running on. For example, initial deployment of the OVA and UC application may have been done on ESXi 4.0 update 1. Then at a later time, you may upgrade the ESXi software to version 4.1 or migrate the vm to a host running ESXi 4.1 - once running on the different ESXi version, you will need to upgrade the VMware Tools running in your UC application to match the host it is running on. Software upgrades of the UC application will preserve the version of VMware Tools currently running.Which method to use: Early versions of the Collaboration applications required a COP file in order to upgrade the VMware Tools. Later, a CLI command was created to make the upgrades easier. Finally once the applications ran on newer embedded OS versions, it became possible to support automatic tools upgrades.For a given application/release, use ONLY the supported method(s) to upgrade the tools. The use of the wrong method almost certainly will fail and at worst may corrupt your virtual machine. ApplicationReleaseMethodUnified CM(includes standalone ELM)9.0 and later2 or 3Cisco Emergency Responder9.01, 2 or 310.0 and later3Cisco Unity Connection9.0 and later2 or 3IM and Presence Service9.x110.02 or 310.5 and later3Unified CCX9.0 and later1Unified CCE9.0 and later2Cisco Finesse9.1(1) and later1, 2 or 3Cisco MediaSense9.0(1) and later2 or 3Cisco Social Miner9.0 and later2Cisco Unified Intelligence Center9.0(1) to 11.6(1)1Cisco Virtualized Voice Browser11.5(1) and later2 or 3Method 1: CLI command Step 1 From the vSphere Client log in to vCenter, or your ESXi host, and go to the Hosts and Clusters view (Ctrl+Shift+H). Step 2 To mount the correct version of the VMware Tools software in the Guest virtual CD/DVD drive, perform the following sub-steps.a. Right-click the virtual machine that you are upgrading, and choose Guest > Install/Upgrade VMware Tools.b. In the popup window choose Interactive Tools Upgrade.Step 3 From the Unified CM CLI, enter the CLI command utils vmtools upgrade. ( For Cisco Unified Intelligence Center 11.0 and later enter CLI command utils vmtools refresh. See the Install and Upgrade guide for Cisco Unified Intelligence Center 11.0 and later for more details.)The system reboots twice. Monitor the virtual machine console from the vSphere Client to see the system status.Step 4 When the system is back up, the tools status is updated to OK from the vCenter Summary tab for the virtual machine that you upgraded.Step 5 After installation of the new version of VMware Tools is complete, remove the VMware Tools tar file from the virtual CD/DVD drive. (Usually, the VMware Tools tar file is called linux.iso). To remove the VMware Tools tar file, perform the following substeps.a. Right-click the virtual machine that you are upgrading, and choose VM > Edit Settings > CD/DVD drive.b. Choose Device Type as Client Device.Method 2: Upgrade from viClient Use the following procedure to perform this upgrade.Step 1 From the viClient, Initiate the tools upgrade by clicking on VM > Guest > Install / Upgrade VMware Tools (this can also be done by right-clicking on the VM).Step 2 Choose the automatic tools update and press OK. Step 3 The process will take a few minutes. The task should then be complete and the tools should be shown as "OK". No reboot is required. Method 3: Automatically check and upgrade VMware Tools at boot time To configure your virtual machine to automatically check the tools version during each VM power-on and automatically upgrade the tools if they are not up-to-date, use the following procedure.Step 1 Edit the VM settings by clicking on the Options tab, and select VMware tools. Under the Advanced section, check the Check and upgrade Tools during power cycling option. A check will now be performed each time the VM powers on to determine if the tools need to be updated. Updates are performed automatically.Note:If the tools do need to be updated, the VM may go through an additional boot cycle to update the tools. This will occur automatically.
Yes, have a look at the appliancesh interface which allows you to specify which inbound IPs are whitelisted. Page 27 for more info -60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-appliance-configuration-guide.pdf