Sunday, 29 July 2012

vCenter Server Installation Requirements


vCenter Server Installation Requirements

 

Today I am going to cover how to install VMware vCenter Server 5.0. In my case I am using Windows 2008 R2 64bit as base operating system for my VMware vCenter Server. As vCenter Server 5.0 requires a 64-bit operating system and cannot be installed on a 32-bit operating system. 

NOTE: Ensure you meet the minimum hardware requirements and that your hardware and operating system requirements are compliant. The vCenter Server 5.0 system can be a physical or a virtual machine.

vCenter Server Hardware


vCenter Server Hardware
Requirement
CPU
Two 64-bit CPUs or one 64-bit dual-core processor.
Processor
2.0GHz or faster Intel 64 or AMD 64 processor. The Itanium (IA64) processor is not supported. Processor requirements might be higher if the database runs on the same machine.
Memory
4GB RAM. Memory requirements might be higher if the database runs on the same machine.
vCenter Server includes several Java services: VMware VirtualCenter Management Webservices (Tomcat), Inventory Service, and Profile-Driven Storage Service. When you install vCenter Server, you select the size of your vCenter Server inventory to allocate memory for these services. The inventory size determines the maximum JVM heap settings for the services. You can adjust this setting after installation if the number of hosts in your environment changes.
Disk storage
4GB. Disk requirements might be higher if the vCenter Server database runs on the same machine. In vCenter Server 5.0, the default size for vCenter Server logs is 450MB larger than in vCenter Server 4.x. Make sure the disk space allotted to the log folder is sufficient for this increase.
Microsoft SQL Server 2008 R2 Express disk
(If you are selecting to install the SQL Server that comes bundled with VMware installation package)
Up to 2GB free disk space to decompress the installation archive. Approximately 1.5GB of these files are deleted after the installation is complete.
Networking
Gigabit connection recommended.



vSphere Client Hardware
Requirements and Recommendations
CPU
1 CPU
Processor
500MHz or faster Intel or AMD processor (1GHz recommended)
Memory
500MB (1GB recommended)
Disk storage
1.5GB free disk space for a complete installation, which includes the following components:

·         Microsoft .NET 2.0 SP2
·         Microsoft .NET 3.0 SP2
·         Microsoft .NET 3.5 SP1
·         Microsoft Visual J#

Remove any previously installed versions of Microsoft Visual J# on the system where you are installing the vSphere Client.

·         vSphere Client

If you do not have any of these components already installed, you must have 400MB free on the drive that has the %temp% directory.

If you have all of the components already installed, 300MB of free space is required on the drive that has the %temp% directory, and 450MB is required for vSphere Client.
Networking
Gigabit connection recommended.


NOTE: vCenter Server and vSphere Client System Recommendations for Performance Based on Deployment Size

The number of hosts and powered-on virtual machines in your environment affects performance. Use the following system requirements as minimum guidelines for reasonable performance. For increased performance, you can configure systems in your environment with values greater than those listed here.
Processing requirements are listed in terms of hardware CPU cores. Only physical cores are counted. In hyperthreaded systems, logical CPUs do not count as separate cores.

IMPORTANT: The recommended disk sizes assume default log levels. If you configure more detailed log levels, more disk space is required.

Medium Deployment of Up to 50 Hosts and 500 Powered-On Virtual Machines

Product
Cores
Memory
Disk
vCenter Server
2
4GB
5GB
vSphere Client
1
1GB
1.5GB


Large Deployment of Up to 300 Hosts and 3,000 Powered-On Virtual Machines

Product
Cores
Memory
Disk
vCenter Server
4
8GB
10GB
vSphere Client
1
1GB
1.5GB


Extra-Large Deployment of Up to 1,000 Hosts and 10,000 Powered-On Virtual Machines

Product
Cores
Memory
Disk
vCenter Server
8
16GB
10GB
vSphere Client
2
1GB
1.5GB

vSphere Web Client Hardware Requirements


The vSphere Web Client has two components: A Java server and an Adobe Flex client application running in a browser.

Hardware Requirements for the vSphere Web Client Server Component

vSphere Web Client Server Hardware
Requirement
Memory
At least 2GB: 1GB for the Java heap, and 1GB for
·         The resident code
·         The stack for Java threads
·         Global/bss segments for the Java process
CPU
2.00 GHz processor with 4 cores


vCenter Server Software Requirements


Make sure that your operating system supports vCenter Server. vCenter Server requires a 64-bit operating system, and the 64-bit system DSN is required for vCenter Server to connect to its database.

For a list of supported operating systems, see the VMware Compatibility Guide at http://www.vmware.com/resources/compatibility.

vCenter Server requires the Microsoft .NET 3.5 SP1 Framework. If it is not installed on your system, the vCenter Server installer installs it. The .NET 3.5 SP1 installation might require Internet connectivity to download more files.

NOTE:

If your vCenter Server host machine uses a non-English operating system, install both the Microsoft .NET Framework 3.5 SP1 and Microsoft .NET Framework 3.5 Language Pack through Windows Update. Windows Update automatically selects the correct localized version for your operating system. The .NET Framework installed through the vCenter Server installer includes only the English version.

If you plan to use the Microsoft SQL Server 2008 R2 Express database that is bundled with vCenter Server, Microsoft Windows Installer version 4.5 (MSI 4.5) is required on your system. You can download MSI 4.5 from the Microsoft Web site. You can also install MSI 4.5 directly from the vCenter Server autorun.exe installer.

vSphere Client and vSphere Web Client Software Requirements


Make sure that your operating system supports the vSphere Client.

For the most current, complete list of supported operating systems for the vSphere Client and the vSphere Web Client, see the VMware Compatibility Guide at: http://www.vmware.com/resources/compatibility

The vSphere Client requires the Microsoft .NET 3.5 SP1 Framework. If it is not installed on your system, the vSphere Client installer installs it. The .NET 3.5 SP1 installation might require Internet connectivity to download more files.

The following browsers are supported for the vSphere Web Client:
  • Microsoft Internet Explorer 7 and 8
  • Mozilla Firefox 3.6
 The vSphere Web Client requires the Adobe Flash Player version 10.1.0 or later to be installed with the appropriate plug-in for your browser.

Required Ports for vCenter Server


The VMware vCenter Server system must be able to send data to every managed host and receive data from every vSphere Client. To enable migration and provisioning activities between managed hosts, the source and destination hosts must be able to receive data from each other.

VMware uses designated ports for communication. Additionally, the managed hosts monitor designated ports for data from the vCenter Server system. If a firewall exists between any of these elements and Windows firewall service is in use, the installer opens the ports during the installation. For custom firewalls, you must manually open the required ports. If you have a firewall between two managed hosts and you want to perform source or target activities, such as migration or cloning, you must configure a means for the managed hosts to receive data.

NOTE: In Microsoft Windows Server 2008, a firewall is enabled by default.

Ports Required for Communication Between Components

Port
Description
80
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 http://server instead of https://server.
389
This port must be open on the local and all remote instances of vCenter Server. This is the LDAP port number for the Directory Services for the vCenter Server group. The vCenter Server system needs to bind to port 389, even if you are not joining this vCenter Server instance to a Linked Mode group.
443
The default port that the vCenter Server system uses to listen for connections from the vSphere Client. To enable the vCenter Server system to receive data from the vSphere Client, open port 443 in the firewall.
The vCenter Server system also uses port 443 to monitor data transfer from SDK clients.
636
For vCenter Server Linked Mode, this is the SSL port of the local instance.
902
The default port that the vCenter Server system uses to send data to managed hosts. Managed hosts also send a regular heartbeat over UDP port 902 to the vCenter Server system.
903
Port 903 must not be blocked between the vSphere Client and the hosts.
8080
Web Services HTTP. Used for the VMware VirtualCenter Management Web Services.
8443
Web Services HTTPS. Used for the VMware VirtualCenter Management Web Services.
60099
Web Service change service notification port
10443
vCenter Inventory Service HTTPS
10109
vCenter Inventory Service Management
10111
vCenter Inventory Service Linked Mode Communication


DNS Requirements for vSphere


You install vCenter Server, like any other network server, on a machine with a fixed IP address and well-known DNS name, so that clients can reliably access the service.

Assign a static IP address and host name to the Windows server that will host the vCenter Server system. This IP address must have a valid (internal) domain name system (DNS) registration.

Ensure that the ESXi host management interface has a valid DNS resolution from the vCenter Server and all vSphere Clients and vSphere Web Clients. Ensure that the vCenter Server has a valid DNS resolution from all ESXi hosts and all vSphere Clients and vSphere Web Clients.

Ensure that the vCenter Server is installed on a machine that has a resolvable fully qualified domain name (FQDN). To check that the FQDN is resolvable, type nslookup your_vCenter_Server_fqdn at a command line prompt. If the FQDN is resolvable, the nslookup command returns the IP and name of the domain controller machine.

Ensure that DNS reverse lookup returns a fully qualified domain name when queried with the IP address of the vCenter Server. When you install vCenter Server, the installation of the web server component that supports the vSphere Client fails if the installer cannot look up the fully qualified domain name of the vCenter Server from its IP address. Reverse lookup is implemented using PTR records. To create a PTR record, see the documentation for your vCenter Server host operating system.

NOTE: If you use DHCP instead of a static IP address for vCenter Server, make sure that the vCenter Server computer name is updated in the domain name service (DNS). Ping the computer name to test the connection. For example, if the computer name is host-1.company.com, run the following command in the Windows command prompt:

ping host-1.company.com

If you can ping the computer name, the name is updated in DNS.

What’s Next? 

Install VMware vCenter Update Manager.. (coming soon)

 


No comments :

Post a Comment