6.0.2
Table Of Contents
- vSphere Migration
- Contents
- About vSphere Migration
- System Requirements for Migrating vCenter Server Deployments to vCenter Server Appliance Deployments
- vCenter Server Appliance Requirements
- vCenter Server Appliance Hardware Requirements
- vCenter Server Appliance Storage Requirements
- Software Included in the vCenter Server Appliance
- vCenter Server Appliance Software Requirements
- vCenter Server Appliance Database Requirements
- vSphere Web Client Software Requirements
- Required Ports for vCenter Server and Platform Services Controller
- Pre-migration Checks
- Known Limitations
- Preparing for Migration
- Moving Update Manager to a New Host Machine When Migrating vCenter Server to vCenter Server Appliance
- Synchronizing Clocks on the vSphere Network
- Preparing vCenter Server Certificates for Migration
- Preparing vCenter Server Databases for Migration
- Prepare Managed ESXi Hosts for Migration
- Install the Client Integration Plug-In
- Required Information for Migrating vCenter Server and vCenter Single Sign-On from Windows to an Appliance
- Migration of vCenter Server with an Embedded vCenter Single Sign-On to an Appliance
- Migration of vCenter Server with an External vCenter Single Sign-On to an Appliance
- After Migrating vCenter Server
- Troubleshooting
- Index
Required Ports for vCenter Server and Platform Services Controller
The vCenter Server system both on Windows and in the appliance, must be able to send data to every
managed host and receive data from the vSphere Web Client and the Platform Services Controller services.
To enable migration and provisioning activities between managed hosts, the source and destination hosts
must be able to receive data from each other.
Ports Required for Communication Between Components
If a port is in use or is blacklisted, the vCenter Server installer displays an error message. You must use
another port number to proceed with the installation. There are internal ports that are used only for inter-
process communication.
VMware uses designated ports for communication. Additionally, the managed hosts monitor designated
ports for data from vCenter Server. If a rewall exists between any of these elements, the installer opens the
ports during the installation or upgrade process. For custom rewalls, you must manually open the required
ports. If you have a rewall between two managed hosts and you want to perform source or target activities,
such as migration or cloning, you must congure a means for the managed hosts to receive data.
N In Microsoft Windows Server 2008 and later, rewall is enabled by default.
If you congured a custom port when you installed the source vCenter Server instance, revert to default port
values before you proceed with the migration.
Table 2‑4. Ports Required for Communication Between Components
Port Protocol Description Required for
Used for Node-to-
Node
Communication
22 TCP/UDP System port for SSHD.
I This port must be open
during the migration to an appliance.
The migration process establishes an
SSH connection to transfer the data
from the existing to the new
appliance.
Appliance
deployments of
n
vCenter Server
n
Platform Services
Controller
No
80 TCP vCenter Server requires port 80 for
direct HTTP connections. Port 80
redirects requests to HTTPS port 443.
This redirection is useful if you
accidentally use hp://server instead
of hps://server.
WS-Management (also requires port
443 to be open).
If you use a Microsoft SQL database
that is stored on the same virtual
machine or physical server as the
vCenter Server, port 80 is used by the
SQL Reporting Service. When you
install or upgrade vCenter Server, the
installer prompts you to change the
HTTP port for vCenter Server.
Change the vCenter Server HTTP
port to a custom value to ensure a
successful installation or upgrade.
I You can change this port
number during the vCenter Server
and Platform Services Controller
installations on Windows.
Windows
installations and
appliance
deployments of
n
vCenter Server
n
Platform Services
Controller
No
vSphere Migration
12 VMware, Inc.