VMware VS4-ENT-PL-A - vSphere Enterprise Plus, Руководство по установке

Страница: 116 / 276

Linked Mode Troubleshooting
If you are having trouble with your Linked Mode group, consider the following points.
When you have multiple vCenter Server instances, each instance must have a working relationship with the
domain controller and not conflict with another machine that is in the domain. Conflicts can occur, for
example, when you clone a vCenter Server instance that is running in a virtual machine and you do not use
sysprep or a similar utility to ensure that the cloned vCenter Server instance has a globally unique identifier
(GUID).
If the domain controller is unreachable, vCenter Server might be unable to start. You might be unable to
change the Linked Mode configuration of the affected vCenter Server system. If this occurs, resolve the
problem with the domain controller and restart vCenter Server. If resolving the problem with the domain
controller is impossible, you can restart vCenter Server by removing the vCenter Server system from the
domain and isolating the system from its current Linked Mode group.
The DNS name of the machine must match with the actual machine name. Symptoms of machine names not
matching the DNS name are data replication problems, ticket errors when trying to search, and missing
search results from remote instances.
N
OTE
Make sure your Windows and network-based firewalls are configured to allow Linked Mode.
Configure Firewall Access by Opening Selected Ports
vCenter Server uses Microsoft ADAM/AD LDS to enable Linked Mode, which uses the Windows RPC port
mapper to open RPC ports for replication. When you install vCenter Server in Linked Mode, the firewall
configuration on any network-based firewalls must be modified.
Incorrect configuration of firewalls can cause licenses and roles to become inconsistent between instances.
Procedure
u
Configure Windows RPC ports to generically allow selective ports for machine-to-machine RPC
communication.
Choose one of the following methods.
n
Change the registry settings. See http://support.microsoft.com/kb/154596/en-us .
n
Use Microsoft's
RPCCfg.exe
tool. See http://support.microsoft.com/kb/908472/en-us .
Configuring VMware vCenter Server - tc Server Settings in vCenter
Server
Starting with vCenter Server 5.1, VMware Tomcat Server settings can no longer be configured through the
Windows user interface. vCenter Server versions 5.1 and later use VMware vCenter Server - tc Server, an
enterprise version of Apache Tomcat 7. Tomcat version 7 does not provide a control panel in the Windows
user interface. Instead, you configure Tomcat by editing configuration files manually.
You can adjust the JVM maximum heap size for vCenter Server,vCenter Inventory Service, and Profile-
Driven Storage Service. For JVM heap size recommendations, see “Hardware Requirements for vCenter
Server, the vSphere Web Client, vCenter Inventory Service, and vCenter Single Sign-On,” on page 17.
Settings for Java options are stored in the following files.
n
vCenter Server.
installation_directory\VMware\Infrastructure\tomcat\conf\wrapper.conf
n
vCenter Inventory Service.
installation_directory\VMware\Infrastructure\Inventory
Service\conf\wrapper.conf
vSphere Installation and Setup
116 VMware, Inc.