INSTALLING vCENTER SERVER

vCenter Server Deployment options:

vCenter Server Hardware and Software Requirements: Hardware Requirements(Physical or Virtual Machine) Number of CPUs-Two 64-bit CPUs or 64-bit Duel-core processor Processor 2.0GHz or higher Intel or AMD processor* Memory 4GB RAM minimum* Disk storage 4GB minimum* Networking Gigabit connection recommended Higher if database runs on the same machine Software requirements: 64-bit operating system is required. See vSphere Compatibility Matrixes. vCenter Server Database Requirements: Each vCenter Server instance must have a connection to a database to organize all the configuration data. Supported databases: Microsoft SQL Server 2005 SP3 (required) SP4 recommended

 Microsoft SQL Server 2008 R2 Express Microsoft SQL Server 2008 Oracle 10g R2 and 11g IBM DB2 9.5 and 9.7 Default database Microsoft SQL Server 2008 Express: Bundled with vCenter Server Used for product evaluations and demos Also used for small deployments (up to five hosts and 50 virtual machines)

Considerations for calculating the database size:

Before Installing vCenter Server: Before beginning the vCenter Server installation, make sure that the following prerequisites are met: Ensure that vCenter Server hardware and software requirements are met. Ensure that the vCenter Server system belongs to a domain rather than a workgroup. Create a vCenter Server database, unless you are using the default database. Obtain and assign static IP address and host name to the vCenter Server system.

vCenter Server installation Wizard: The vCenter Server Installation wizard asks for the following data.

Installing vCenter Server and Its components:

click on Install.

Standalone Instance or Linked mode Group:

Welcome to the installation wizard for VMware vCenter Server appears, Click on Next

Accept the Patent Agreement carefully, and click on Next

Select Accept the VMware End User License Agreement, click on Next

Fill the Customer Information, ie the User Name, Organization and License Key and Click on Next

At this Please select your choice of Database, go for Microsoft SQL Server 2008 Express Instance if it's for a small deployment. Otherwise select Use existing supported database.

vCenter Server Services: Instead of using the vCenter Serer appliance, you can install vCenter Server on a Windows system. After vCenter Server is installed, a number of services start upon reboot and can be managed from the Windows Control Panel (Administrative Tools > Services).

Manage vCenter Server Inventory Datacenter Object:

Organizing Inventory Objects into Folders:

Navigating the vSphere Client:

vCenter Server Views: Hosts and Clusters, VMs, and Templates:

Adding a Host to the vCenter Server Inventory

vCenter License Overview

Licenses are managed and monitored from vCenter Server. Licensing consists of: Product License to use a vSphere software component or feature License key 25-character string that corresponds to a product Asset Machine on which a product is installed vCenter Server Events

vCenter Server System Logs

VMware vSphere User Interfaces

Downloading the vSphere Client vSphere Client is an interface used to connect remotely to VMware vCenter Server from a widows system. You can download the vSphere Client in two ways: Use the VMware Infrastructure Management Installer Download the client form the vCenter Server system or an ESXi host.

Using the vSphere Client: The vSphere Client is an interface used to remotely connect to an ESXi host or a vCenter Server from a Windows PC.On the vSphere Client login screen, Enter: Host name or IP address of ESXi host or vCenter Server User Name Password for the user (Optional) Use your Windows session credentials.

vSphere Client Configuration Tab:

Viewing Processor and Memory Information:

Viewing ESXi System Logs: Use the vSphere Client to view logs. Export System logs to an archive file. Send to VMware support.

Viewing Licensed Features:

Before purchasing licenses, you can install ESXi in evaluation mode: Intended for demonstration and evaluation purposes Allows software to be completely operational immediately after installation Does not require any licensing configuration Provide full functionality for 60 days Managing ESXi from the Command Prompt: To perform management tasks from a remote command prompt, Use: VMware vSphere Command-Line Interface(vCLI): Set of commands run from a remote Linux or Windows system and executed on an ESXi host. Packaged as an applicaion VMware vSphere Management Assistant(vMA): Platform for running a variety of toolkints. vCLI vSphere SDK for Perl vSphere API Packaged as virtual appliance based on Linux VMware vSphere PowerCLI: Automation tool for administering a vSphere environment Distributed as a snap-in to windows PowerShell The New vSphere Web Client:

Note: It takes some time since you started the Web Client Service in the vCenter Server Appliance and when the page is accessible le. If you get a network error, please allow a couple of minutes for the service to start.

Open a browser and point it to https://10.10.10.51/vsphere-client/ This is the IP address of the vCSA, with the path to the vSphere Web Client. If you get this screen about the website's security certificate, click on Continue to this website (not recommended). At the bottom of the browser you will notice a message prompting you that the webpage wants to run the VMware Remote Console and Client Integration Plug-in. Click Allow.

Type in the login credentials and then click on Login

Accept the vCenter server's certificate and then click on Ignore

What can I see in the Main screen of the vSphere Web Client: The Left Panel: In the left panel you can see all the objects you can manage from the web client. Click on each of the four icons of the left panel to see how the related objects change. When finished, click back on the Hosts and Clusters button.

The main panel When you select one of the objects from the left panel, its properties are shown in the main panel. Feel free to select various objects from the left panel and see how the main panel changes to show the different properties for each one. You can expand the list by clicking the down arrow icon.

When you are done, click on the esx-01a.corp.local host on the left panel to see its properties

Changing the look of the main panel

How do I find my stuff in the new vSphere Web Client?

Clicking on the down-arrow near to vCenter Management shows the vCenter tasks.

Advanced Search in vSphere web Client

In the new window, click on Advanced Search. New searching criteria drop-lists appear, to help us find what we are looking for.

Right-button is also present in the Web Client

 As in the classic vSphere client, you can use the right button of the mouse to access the tasks you can apply to an object. Select the vCSA01 virtual machine, the vCenter we configured in the previous chapter in the left panel. Now, do right-click on the selection. You will see a new menu with all the tasks you can start over the virtual machine. Take a look at the menus.

vMotion the vCSA Virtual Machine using vSphere Web Client

Select the vCSA01 virtual machine, right-click the selection and choose Inventory and then Migrate.

vMotion steps
A new window appears to guide us in the options of the vMotion task. Select Change host. Click Next.

Choose destination for the VM

Select A Cluster under the CORP data center. Click Next.

Choose destination host for the VM

In the next step, leave the default options, click Next. In the last screen, review the options and click Finish. The vMotion of vCSA01will start.

The notification window.

When a task is launched, completed or failed, a notification window appears in the right-bottom of the screen with the summary of the task.

In the right side of the screen you will find My Recent Tasks, where you can see the status of the running, previous or all tasks launched from the vSphere Web Client. Clicking in one of the tasks will open a new window with the details for that task. You can have a more detailed view clicking on Go to Task Console.

The Task Console shows all the tasks performed in the virtual environment. Clicking over each tasks shows the details of that task at the bottom of the screen. You can also see the Events and Alarms. Click on the down-button near to Task Console and select Monitoring followed by Event

In this view you can see the Alarms and Events registered. Clicking an event will show you the details of that event at the bottom of the screen
Additional Information vCenter Server Appliance 5.x Service Description and Service Name correlation list Service Description VMware VirtualCenter Server Service Embedded vPostgres Database service VMware Tools Service VMware vSphere Profile-Driven Storage Service VMware vCenter Inventory Service VMware vSphere Network Dump Collector service VMware vSphere Log Browser VMware vSphere Auto Deploy service Service Name vmware-vpxd vmware-vpostgres vmware-tools-services vmware-sps vmware-inventoryservice vmware-netdumper vmware-logbrowser vmware-rbd-watchdog

[For vSphere 5.1 Only] vCenter Single Sign-On 5.1

vmware-sso

[For vSphere 5.5 Only] vCenter Single Sign-On 5.5 VMware Directory Service [For vSphere 5.5 Only] vCenter Single Sign-On 5.5 -

vmdird vmcad

VMware Certificate Service [For vSphere 5.5 Only] vCenter Single Sign-On 5.5 VMware Secure Token Service [For vSphere 5.5 Only] vCenter Single Sign-On 5.5 VMware Kdc Service [For vSphere 5.5 Only] vCenter Single Sign-On 5.5 VMware Identity Management Service

vmware-stsd vmkdcd vmware-sts-idmd

vCenter Server and ESXi 5.x network ports that SRM requires

SRM and vSphere Replication require certain ports to be open on vCenter Server: Default Protocol or Source Target Port Description 80 HTTP SRM Description

Remote All management traffic to SRM Server vCenter goes to port 80 on the vCenter Server proxy Server system. vCenter Default SSL Web port Server Remote Traffic from the SRM Server on the ESXi recovery site to ESX hosts when recovering host or testing virtual machines with IP customization, with configured callout commands on recovered virtual machines, or that use raw disk mapping (RDM). All NFC traffic for updating or patching the VMX files of virtual machines that are replicated using vSphere Replication use this port.

443

HTTPS

SRM

902

TCP

SRM

SRM Server 5.x network ports The SRM Server instances on the protected and recovery sites require certain ports to be open. Note: SRM Server at the recovery site must have NFC traffic access to the target ESXi servers.

Default Protocol or Source Target Port Description 80 TCP SRM

Endpoints or Consumers

Remote All management traffic to SRM Server vCenter goes to port 80 on the vCenter Server Server proxy system. Local Management traffic to the local vSphere vCenter Replication management server (VRMS) Server goes to port 80 on the local vCenter Server proxy system. vCenter Default SSL Web Port for incoming TCP Server traffic Remote ESXi host Traffic from the SRM Server on the recovery site to ESXi hosts when recovering or testing VMs with IP customization, with configured callout commands on recovered VMs, or that use raw disk mapping (RDM). All NFC traffic for updating or patching the VMX files of VMs that are replicated using vSphere Replication use this port.

80

TCP

SRM

443

TCP

SRM

902

TCP and UDP

SRM

1433

TCP

SRM

Microsoft SRM connectivity to Microsoft SQL SQL Server (for SRM database) Server Oracle SRM database connectivity to Oracle Database Server Oracle SRM database connectivity to Oracle Database Server

1521

TCP

SRM

1526

TCP

SRM

5000

TCP

SRM

IBM SRM database connectivity to IBM DB2 DB2 Database Server From the vCenter Server proxy to the SRM Server (intrasite only).

8095

SOAP

vCenter SRM Server and vSphere Client SRM SRM External API Client vCenter SRM Server

9007

TCP

Used by external API clients for task automation.

9085

HTTP

HTTP interface for downloading the UI plug-in and icons. This port must be accessible from the vCenter Server proxy system. SRM client plug-in download between the vCenter Server proxy and SRM.

9086

HTTPS

vCenter SRM Server

vSphere Replication Appliance 5.x network ports The vSphere Replication appliance requires certain ports to be open. In SRM 5.1 and later and vSphere Replication 5.x, vSphere Replication is shipped as a combined appliance that contains both the vSphere Replication management server (VRMS) and a vSphere Replication server. SRM 5.x allows you to deploy additional vSphere Replication servers. Note: vSphere Replication management servers must have NFC traffic access to target ESXi hosts.

Default Protocol or Port Description 80 TCP

Source vSphere Replication appliance

Target Remote vCenter Server

Endpoints or Consumers All management traffic to the vSphere Replication appliance goes to port 80 on the vCenter Server proxy system. Used to establish the connection before initial replication starts Used by vSphere Replication servers to send replication traffic to the destination ESXi hosts.

80

HTTP

vSphere Replication appliance vSphere Replication server in the vSphere Replication appliance

Remote ESXi host

902

TCP and UDP

Remote ESXi host

5480

vSphere Browser Replication appliance virtual appliance management interface (VAMI) Web UI (vSphere Replication 5.x) SOAP

vSphere Administrator's Web Replication browser. 5.x appliance

8043

vCenter Server vSphere From the vCenter Server Proxy Replication proxy to the vSphere appliance Replication appliance (intrasite only).

8123

SOAP

vSphere Replication appliance

vSphere Management traffic from Replication the vSphere Replication server appliance to additional vSphere Replication servers (intrasite only). vSphere Replication server in the vSphere Replication appliance vSphere Replication server in the vSphere Replication appliance From the ESXi host at the protected site to the vSphere Replication appliance or vSphere Replication server at the recovery site. From the ESXi host at the protected site to the vSphere Replication appliance or vSphere Replication server at the recovery site.

31031

Initial replication ESXi host on traffic primary site

44046

Ongoing ESXi host on replication traffic primary site

vSphere Replication Management Server 1.0.x network ports The vSphere Replication appliance requires certain ports to be open. SRM 5.0.x includes vSphere Replication 1.0.x. In vSphere Replication 1.0.x, vSphere Replication consists of a vSphere Replication management server (VRMS) appliance and one or more vSphere Replication servers. Note: vSphere Replication management servers must have NFC traffic access to target ESXi hosts.

Default Protocol or Source Port Description 80 TCP

Target

Endpoints or Consumers All management traffic to the vSphere Replication management server goes to port 80 on the vCenter Server proxy system. Used to establish the connection before initial replication starts

vSphere Remote Replication vCenter management Server server

80

HTTP

vSphere Remote Replication ESXi host management server vSphere Remote Replication ESXi host management server and vSphere Replication server vCenter Server Proxy

902

TCP and UDP

Used by vSphere Replication servers to send replication traffic to the destination ESXi hosts.

8043

SOAP

vSphere From the vCenter Server proxy Replication to the vSphere Replication management management server (intrasite server only). VRMS 1.0.x Administrator's Web browser.

8080

VRMS Browser virtual appliance management interface (VAMI) Web UI

8123

SOAP

vSphere vSphere Replication Replication management server server

Management traffic from the vSphere Replication management server to the vSphere Replication servers (intrasite only).

vSphere Replication Server 1.0.x and 5.x network ports The vSphere Replication 5.x appliance contains a vSphere Replication server. You can deploy additional vSphere Replication servers if you use vSphere Replication 5.1 with SRM 5.1 or if you use vSphere Replication 5.5. You cannot deploy additional vSphere Replication servers if you use vSphere Replication 5.1 without SRM. SRM 5.0.x includes vSphere Replication 1.0.x. In vSphere Replication 1.0.x, vSphere Replication consists of a vSphere Replication management server (VRMS) appliance and one or more vSphere Replication server appliances that you deploy separately from the VRMS. If you deploy additional vSphere Replication servers, ensure that the subset of the ports that vSphere Replication servers require are open on those servers. Default Protocol or Port Description 902 TCP and UDP Source vSphere Replication server Target Remote ESXi host Endpoints or Consumers Traffic (specifically the NFC service to the destination ESXi servers) between the vSphere Replication server and the ESXi hosts on the same site. Administrator's Web

5480

VAMI Web UI Browser

vSphere

for any additional vSphere Replication servers 8123 SOAP vSphere Replication management server

Replication browser. server

vSphere Management traffic from Replication the vSphere Replication server appliance or VRMS to the vSphere Replication servers (intrasite only). vSphere From the ESXi host at the Replication protected site to the server vSphere Replication appliance or vSphere Replication server at the recovery site. vSphere From the ESXi host at the Replication protected site to the server vSphere Replication appliance or vSphere Replication server at the recovery site.

31031

Initial replication traffic

ESXi host on primary site

44046

Ongoing replication traffic

ESXi host on primary site

Network ports that must be open between the SRM and vSphere Replication protected and recovery sites SRM and vSphere Replication require that the protected and recovery sites can communicate.

Port 80

Protocol or Source Description SOAP SRM and vSphere Replication appliance or VRMS

Target

Endpoints or Consumers

Remote vCenter Management traffic Server between SRM Server instances and vSphere Replication appliances or VRMS. To allow the SRM UI to verify vSphere Replication appliance or VRMS certificates. To allow the SRM UI to verify SRM Server certificates. From the ESXi host at the protected site to the vSphere Replication appliance or vSphere Replication server at the recovery site. From the ESXi host at the protected site to the vSphere Replication appliance or vSphere Replication server at the recovery site.

8043 SOAP

vSphere Client vSphere Replication appliance 5.x or VRMS 1.0.x vSphere Client SRM

8095 SOAP

31031 Initial replication traffic

ESXi host

vSphere Replication appliance 5.x or vSphere Replication server vSphere Replication appliance 5.x or vSphere Replication server

44046 Ongoing replication traffic

ESXi host

Site Recovery Manager1.0 - 4.x network ports VMware Virtual Center/vCenter Server:

80

- HTTP

443 - SSL interface 902 - VMware 8096 - Tomcat Note: The vSphere Client must be able to communicate with vCenter Server through ports 8095 and 9007 for the SRM plug-in to function. VMware Site Recovery Manager:

80 HTTP 8095 SOAP interface between the vCenter Server proxy and SRM 8096 HTTP Listen 9007 SOAP interface for external API clients 9008 HTTP Listen

Note: The vSphere Client must be able to communicate with both SRM servers through port 8095 for the SRM plug-in to function.