1 / 81

VMware vCenter Server 4.0

VMware vCenter Server 4.0. Product Support Engineering. VMware Confidential. Module 1-3 Lessons. Lesson 1 – vSphere Upgrade Lesson 2 – ESX 4.0 Install Lesson 3 – vCenter Server 4.0 Lesson 4 – vSphere 4.0 Licensing Lesson 5 – Remote CLI. Module 1-3 Lessons.

jason
Download Presentation

VMware vCenter Server 4.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VMware vCenter Server 4.0 Product Support Engineering VMware Confidential

  2. Module 1-3 Lessons • Lesson 1 – vSphere Upgrade • Lesson 2 – ESX 4.0 Install • Lesson 3 – vCenter Server 4.0 • Lesson 4 – vSphere 4.0 Licensing • Lesson 5 – Remote CLI VI4 - Mod 1-3 - Slide

  3. Module 1-3 Lessons • Lesson 1 – Overview of vCenter Server 4.0 • Lesson 2 – vCenter Server 4.0 Hardware requirements • Lesson 3 – Supported Databases • Lesson 4 – Preparing VC Databases • Lesson 5 – Maintaining VC Database • Lesson 6 – Installing VC 4.0 • Lesson 7 – Installing vSphere Client • Lesson 8 – Linked-Mode Groups • Lesson 9 – ADAM ( Active Directory Application Mode ) • Lesson 10 – vCenter 4.0 Log collection VI4 - Mod 1-3 - Slide

  4. vSphere Components • ESX • vCenter Server • vCenter Server Plugin • vSphere Client • Web Access • Databases VI4 - Mod 1-3 - Slide

  5. vSphere Components The major components of vSphere are: • VMware ESX Server • ESX provides a virtualization layer that abstracts the processor, memory, storage, and networking resources of the physical host into multiple virtual machines. • vCenter Server • This server installs on a Windows machine, either physical or virtual, to centrally manage your VMware ESX hosts. • The vCenter Server allows the use of advanced vSphere features such as VMware DRS, VMware HA, and VMotion™.A VMware SDK Web service is installed with the vCenter Server. • vCenter Server Plugins • Optional applications that provide additional capabilities and features. • Generally, plugins are released separately, installed on top of vCenter Server, and can be upgraded independently. • You can install server components of plugins on the same computer where the vCenter Server resides, or on a separate one. • After the server component of a plugin is installed, you can activate the plugin’s client component, which enhances the vSphere Client with appropriate UI options. VI4 - Mod 1-3 - Slide

  6. vSphere Components • The vSphere Client installs on a Windows machine and is the primary method of interaction with vSphere. The vSphere Client acts as: • A console to operate virtual machines. • An administration interface into the vCenter Servers and ESX hosts. The vSphere Client is downloadable from the vCenter Server and ESX hosts. • Web Access • A browser lets you download the vSphere Client from the vCenter Server or ESX hosts. • Lets you perform limited management of your vCenter Server and ESX hosts. • Databases • vCenter Server uses a database to organize all the configuration data for the vSphere environment. The bundled Microsoft SQL Server 2005 Express database lets you set up a limited numbers of hosts and virtual machines (5 hosts and 50 VM’s ). • vCenter Server supports several other database products for larger deployments. vCenter Update Manager also requires a database. VMware recommends that you use separate databases for vCenter Server and vCenter Update Manager. VI4 - Mod 1-3 - Slide

  7. vCenter Server Hardware Requirements • The vCenter Server is a physical machine or virtual machine configured with access to a supported database. • The vCenter Server hardware must meet the following requirements: • Processor – 2.0GHz or higher Intel or AMD x86 processor.Processor requirements can be larger if your database is run on the same hardware. Consult Database documentation. • Memory – 2GB RAM minimum. RAM requirements can be larger if your database is run on the same hardware. • Disk storage – 1GB minimum, 2GB recommended. • Microsoft SQL Server 2005 Express disk requirements – The bundled database requires up to 2GB free disk space to decompress the installation archive. • However, approximately 1.5GB of these files are deleted after the installation is complete. • Networking – 1 GB recommended. VI4 - Mod 1-3 - Slide

  8. vSphere Client Hardware Requirements • The vSphere Client hardware must meet the following requirements: • Processor – 266MHz or higher Intel or AMD x86 processor (500MHz recommended). • Memory – 256MB RAM minimum, 512MB recommended. • Disk Storage – 150MB free disk space required for basic installation. You must have 55MB free on the destination drive for installation of the program, and you must have 100MB free on the drive containing your %temp% directory. • Networking – 1 Gb recommended. VI4 - Mod 1-3 - Slide

  9. vSphere Client and vCenter Server Software Requirements • For any operating system except Windows Server 2003 SP1, install Microsoft Windows Installer 3.1, otherwise your vCenter Server installation can fail. • See http://support.microsoft.com/?id=893803 for information on downloading Windows Installer 3.1. • The vSphere Client requires the Microsoft .NET 3.0 SP1 Framework and Microsoft Visual J# 2.0 Second Edition. If your system does not have these installed, the vSphere Client installer installs them. VI4 - Mod 1-3 - Slide

  10. Supported Operating Systems VI4 - Mod 1-3 - Slide

  11. Supported Operating Systems VI4 - Mod 1-3 - Slide

  12. vSphere Web Access Requirements • VMware vSphere Web Access is a browser-based application designed to manage virtual machines on ESX/ ESXi and vCenter Server deployments. VI4 - Mod 1-3 - Slide

  13. vCenter Server Database Requirements • IBM DB2 Support • IBM DB2 Express-C v9.5 • IBM DB2 Express Edition v9.5 • IBM DB2 Workgroup Server Edition v9.5 • IBM DB2 Enterprise Server Edition v9.5 • Microsoft SQL server Database Support • Microsoft SQL Server 2005 Express • Microsoft SQL Server 2005 Standard edition (SP2) • Microsoft SQL Server 2005 Enterprise edition (SP2) • Microsoft SQL Server 2005 Enterprise edition (SP2) x64 • Microsoft SQL Server 2008 Standard Edition • Microsoft SQL Server 2008 Enterprise Edition • Microsoft SQL Server 2008 Enterprise Edition (x64) VI4 - Mod 1-3 - Slide

  14. vCenter Server Database Requirements • Oracle Database Support • Oracle 10g Standard edition (Release 1 [10.1.0.3.0]) • Oracle 10g Enterprise edition (Release 1 [10.1.0.3.0]) • Oracle 10g Standard edition (Release 2 [10.2.0.1.0]) • Oracle 10g Enterprise edition (Release 2 [10.2.0.1.0]) • Oracle 10g Enterprise edition (Release 2 [10.2.0.1.0]) x64 • Oracle 11g Standard edition • Oracle 11g Enterprise edition VI4 - Mod 1-3 - Slide

  15. Supported Guest Operating Systems • The VMware Guest Operating System Installation Guide includes information on supported guest operating systems. • ESX offers support for a number of 64-bit guest operating systems. • Specific hardware requirements for 64-bit guest operating system • AMD Opteron-based systems, the processors must be Opteron Rev E and later • Intel Xeon-based systems, the processors must include support for Intel Virtualization Technology (VT). • CPUs with VT support might ship with VT disabled by default • To determine whether your server has the necessary support, you can use a CPU Compatibility Tool at http://www.vmware.com/download/vi/drivers_tools.html VI4 - Mod 1-3 - Slide

  16. Virtual Machine Requirements • Each Virtual Machine has the following requirements. • Virtual processor • Intel Pentium II or later (dependent on system processor) • One, two, four or eight processors per virtual machineNOTE If you create a two-processor virtual machine, your ESX machine must have at least two physical processors. For a four-processor virtual machine, your ESX machine must have at least four physical processors. • Virtual chip set — Intel 440BX-based motherboard with NS338 SIO chip • Virtual BIOS — PhoenixBIOS 4.0 Release 6 VI4 - Mod 1-3 - Slide

  17. ESX and vCenter Server and Client Compatibility • Use this section to look up the ESX/ESXi versions that are compatible with vCenter Server 4.0 VI4 - Mod 1-3 - Slide

  18. ESX and vCenter Server and Client Compatibility • ESX/ESXi versions compatible with the vSphere Client 4.0 VI4 - Mod 1-3 - Slide

  19. vCenter Required Ports VI4 - Mod 1-3 - Slide

  20. Configure vCenter Server to Use Evaluation Mode • When you run vCenter Server in evaluation mode, vCenter Server behaves for 60 days as if it has a vCenter Server edition license. • The vCenter Server and evaluation editions of vCenter Server allow you to manage an unlimited number of hosts and use Linked-Mode vCenter Server. • To configure vCenter Server to use evaluation mode • If you install vCenter Server and do not enter a license key during the installation, vCenter Server is installed in evaluation mode. When the install wizard prompts you for a license key, leave the license-key field blank and click Next. • If vCenter Server is licensed and you want to convert vCenter Server to evaluation mode, you can do so. VI4 - Mod 1-3 - Slide

  21. Licensing vCenter Server After the Evaluation Expires • After the 60-day evaluation period expires, unless you obtain licenses for your software, you are no longer able to perform most operations in vCenter Server and ESX. VI4 - Mod 1-3 - Slide

  22. Switching vCenter Server to Licensed Mode • When you switch your vCenter Server and ESX from evaluation mode to the licensed mode, consider the following: • If vCenter Server is managing vSphere 3 hosts (for example, ESX 3.0.x or ESXi 3.5), vCenter Server must have access to the VMware License Server. You can download the VMware License Server from the VMware Web site. • When you assign a license to a machine on which a vSphere component is installed, the license must be compatible with all of the resources and features that you configure during the evaluation period. VI4 - Mod 1-3 - Slide

  23. Preparing vSphere Databases • VMware recommends using a separate database for vCenter Server and vCenter Update Manager • vCenter Server and vCenter Update Manager require databases to store and organize server data. • vSphere supports Oracle, Microsoft SQL Server and IBM DB2 databases. • IBM DB2 database only supported for vCenter, no support for Update Manager or any plug-in that requires a database. • You must have administration credentials (ID and password) to log in to an Oracle, SQL Server or IBM DB2 database. • Microsoft SQL Server 2005 Express is intended to be used for small deployments of up to 5 hosts and 50 virtual machines. VI4 - Mod 1-3 - Slide

  24. Supported Database Types VI4 - Mod 1-3 - Slide

  25. Supported Database Types VI4 - Mod 1-3 - Slide

  26. Configure DB2 Databases • If you use a DB2 database for your vCenter Server repository, you need to configure your database to work with vCenter Server. 1. “Configure an IBM DB2 Database User and Group,” on page 54If you plan to use an IBM DB2 database when you install vCenter Server, you must configure the database user and group. 2. “Use a Script to Create a DB2 Database,” on page 55When you use a DB2 database with vCenter Server, the database must have certain buffer pools, table spaces, and privileges. 3. “Use a Script to Create the DB2 Database Schema,” on page 56This script, in conjunction with the script that creates the DB2 database, enables you to have tighter control over the parameters of your database. 4. “Configure a Connection to a Local Database on Windows,” on page 57You can configure a DB2 database for vCenter Server either locally on the same Windows machine as vCenter Server or remotely on a network-connected host. 5. “Configure a Connection to a Remote Database on Linux, Unix or Windows,” on page 58You can configure a DB2 database for vCenter Server either locally on the same Windows machine as vCenter Server or remotely on a network-connected Windows, Linux, or Unix host. VI4 - Mod 1-3 - Slide

  27. Configure Microsoft SQL Server Databases • If you use a Microsoft SQL database for your vCenter Server repository, you need to configure your database to work with vCenter Server. 1. “Use a Script to Create a Local or Remote Microsoft SQL Server Database,” on page 59When you use a SQL Server database with vCenter Server, the database must have certain buffer pools, table spaces, and privileges. To simplify the process of creating the database, you can run a script. 2. “Use a Script to Create the Microsoft SQL Server Database Schema,” on page 60This script, in conjunction with the script that creates the SQL Server database, enables you to have tighter control over the parameters of your database. 3. “Configure a SQL Server ODBC Connection,” on page 61When you install the vCenter Server system, you can establish a connection with a SQL Server database. 4. “Configure Microsoft SQL Server TCP/IP for JDBC,” on page 62If the Microsoft SQL Server database has TCP/IP disabled and the dynamic ports are not set, the JDBC connection remains closed. This causes the vCenter Server statistics to malfunction. VI4 - Mod 1-3 - Slide

  28. Configure Oracle Databases • If you use an Oracle database for your vCenter Server repository, you need to configure your database to work with vCenter Server. 1. “Use a Script to Create a Local or Remote Oracle Database,” on page 63When you use an Oracle database with vCenter Server, the database must have certain buffer pools, tablespaces, and privileges. 2. “Configure an Oracle Database User,” on page 64If you plan to use an Oracle database when you install vCenter Server, you must configure the database user. 3. “Use a Script to Create the Oracle Database Schema,” on page 64This script, in conjunction with the script that creates the Oracle database, enables you to have tighter control over the parameters of your database. 4. “Configure an Oracle Connection for Local Access,” on page 65VMware recommends that the vCenter Server database be located on the same system as vCenter Server. 5. “Configure an Oracle Connection for Remote Access,” on page 66To have a vCenter Server system access the database remotely, use the following procedure. 6. “Connect to an Oracle Database Locally,” on page 66To have a vCenter Server system access the database locally, use the following procedure. VI4 - Mod 1-3 - Slide

  29. vCenter Server Prerequisites • Before you begin the installation procedure, ensure that you have done the following: • Make sure that your hardware meets vCenter Server Hardware Requirements. • Make sure that the system you use for your vCenter Server installation belongs to a domain rather than a workgroup. • To determine whether the system belongs to a workgroup or a domain, right-click My Computer and click Properties and the Computer Name tab. The Computer Name tab displays either a Workgroup label or a Domain label. • Create a vCenter Server database, unless you want to use SQL Server 2005 Express. • Static IP address and host name to the Windows server. This IP address must have a valid (internal) DNS registration that resolves properly from all managed ESX hosts. • You can deploy vCenter Server behind a firewall. However, make sure there is no Network Address Translation (NAT) firewall between vCenter Server and the hosts it will manage. VI4 - Mod 1-3 - Slide

  30. vCenter Server Account Considerations • The vCenter Server install wizard gives you the option to use the Windows system account or a user-specified account for the purpose of running vCenter Server. • The primary reason to use a user-specified account is to enable the use of Windows authentication for SQL Server. • If you choose this option, • The user-specified account must be an Administrator on the local machine • You must specify the account name as DomainName\Username in the vCenter Server install wizard • You must configure the SQL Server database to allow the domain account access to SQL Server. VI4 - Mod 1-3 - Slide

  31. vCenter Server Account Considerations • Another reason to use a user-specified account is security. • The built-in system account has more permissions and rights on the server than vCenter Server needs, which can contribute to security problems. • Even if you do not plan to use Windows authentication for SQL Server or you are using an Oracle database, you might want to set up a local user-specified account for vCenter Server. • The only requirement is that the user-specified account is an Administrator on the local machine. VI4 - Mod 1-3 - Slide

  32. vCenter Server Install Notes • To ensure a smooth installation of vCenter Server, review the following lists that you will be prompted for during the installation. VI4 - Mod 1-3 - Slide

  33. vCenter Server Install Notes VI4 - Mod 1-3 - Slide

  34. Install vCenter Server 1 In the software installer directory, double-click the autorun.exe file. 2 Click vCenter Server. 3 Choose a language for the installer and click OK. 4 When the Welcome screen appears, click Next. 5 Select I agree to the terms in the license agreement and click Next. 6 Type your user name, organization, and vCenter Server license key, and click Next.If you omit the license key, the installer installs vCenter Server in evaluation mode. 7 Choose the type of database that you want to use. • If you want to use the bundled database, click Install SQL Server 2005 Express instance. • If you want to use an existing database, click Use an existing database server and select your database from the list of available DSNs. Enter the user name and password for the DSN and click Next. VI4 - Mod 1-3 - Slide

  35. Install vCenter Server 8 Choose the account type and click Next. 9 Either accept the default destination folders or click Change to select another location, and click Next. 10 Select Standalone vCenter Server Instance or Join Group and click Next. Join a Linked Mode group to enable the vSphere Client to view, search, and manage data across multiple vCenter Server systems. 11 If you join a group, enter the fully qualified domain name and LDAP port number of any remote vCenter Server system and click Next. In some cases, you can enter the IP address instead of the fully qualified domain name. 12 Enter the port numbers that you want to use or accept the default port numbers and click Next. 13 Click Install. 14 Click Finish. VI4 - Mod 1-3 - Slide

  36. Install the vSphere Client 1 In the software installer directory, double-click the autorun.exe file. 2 Click VMware vSphere Client. 3 Choose a language for the installer and click OK. 4 When the Welcome screen appears, click Next. 5 SelectI agree to the terms in the license agreement and click Next. 6 Type your user name and company name and click Next. 7 Select Install VMware vSphere Host Update Utility if you want to manage host patches, updates, and upgrades from this machine and click Next. 8 Accept the default installation location and click Next, or click Change to select a different location and click Next. 9 Click Install to begin the installation. 10 Click Finish to complete the installation. VI4 - Mod 1-3 - Slide

  37. Install the vSphere Host Update Utility • The vSphere Host Update Utility is for patching ESXi hosts and upgrading ESX 3.x/ESXi 3.5 hosts & ESXi 4.0 • vSphere Host Update Utility is bundled with the vSphere Client. You can install vSphere Host Update Utility when you install the vSphere Client. 1 Open a command window: • a Select Start > Run. • b Enter cmd. 2 Navigate to the folder that contains VMware-viclient.exe.E.g. C:\Program Files\VMware\Infrastructure\vSphere Client\Launcher\ 3 Run the VpxClient.exe executable with the following command: VpxClient.exe /S /V"/qr INSTALL_VIUPDATE=1 /L*v %temp%\vim-viu-launch.log" The vSphere Host Update Utility is installed. VI4 - Mod 1-3 - Slide

  38. Lab – Install vCenter 4.0 Lab 4 Part 1 – vCenter 4.0 Installation Lab 4 Part 2 – vCenter 4.0 Client Installation VI4 - Mod 1-3 - Slide

  39. Linked-Mode Product Overview • Core Features • Standard vSphere Client can access inventory across multiple vCenter Servers • Query combined inventory of a group of vCenter Servers • vCenter Servers in linked mode share replicated data • Replicated Group Data • Role and privilege definitions • Licenses Inventory Search Inventory Search Inventory Search vSphere Client Security Manager Security Manager Security Manager Inventory Cache Inventory Cache Inventory Cache DB DB DB LDAP LDAP LDAP VC 3 VC 2 VC 1 VI4 - Mod 1-3 - Slide

  40. Linked-Mode Product Overview • 2 Installation Methods • Standalone vCenter instance • First instance of vCenter to be installed • Join to a vCenter Linked-Mode group • Add vCenter Server to an existing vCenter Linked-Mode group • Isolate from a vCenter Linked-Mode group • Roles and privilege information are retained • Join an existing linked-mode group ( Post Install ) • Join an existing group of VCs, after installing as standalone • Roles and privilege information are retained VI4 - Mod 1-3 - Slide

  41. Linked-Mode Components • ADAM Instance • Tomcat Web Services • VWS application • Other webapps • Stats Reporter, SMS Tomcat Web Services / VWS Tomcat Web Services / VWS VC Server VC Server ADAM Instance (VMware VCMSDS) ADAM Instance (VMware VCMSDS) VI4 - Mod 1-3 - Slide

  42. ADAM Fundamentals • Implementation of Lightweight Directory Access Protocol (LDAP) • Loose consistency across instances • Consistency achieved through replication • Forms of replication: • Configuration/Schema replication • Attempts to paint a uniform global picture for all servers (instances) • Data replication • Attempts to keep data across all instances synchronized VI4 - Mod 1-3 - Slide

  43. Active Directory Application Mode (ADAM) • Shared distributed store for: • Global data • Connection information to available services • All vCenters (VIMAPI) • All query services (VIMWEBSVC) • Installer installs ADAM with every install of vCenter Server • Runs the ‘jointool’ java application • Stores Roles and Privileges across VCs • Stores Licensing information VI4 - Mod 1-3 - Slide

  44. Linked-Mode Jointool • Installer calls into the Jointool application • Runs a bunch of pre-operative validations • For all linked mode operations: • Finds at least one reachable remote instance to connect to • Validates write privileges for current user on remote instance • Validates clock synchronization (clocks cannot be more than 5 mins out of sync) • Validates DNS name and name lookup • Runs ADAM installer • Does post-operative validations • Forces replication of unreplicated data from remote instances • Verifies if basic information VC Server needs to startup is present VI4 - Mod 1-3 - Slide

  45. Linked-Mode Jointool (contd.) Recovery and rollback • On all errors • Attempts to reset local and remote ADAM state VI4 - Mod 1-3 - Slide

  46. Data in ADAM Using ADSI Edit VI4 - Mod 1-3 - Slide

  47. Data in ADAM Data partition : dc=virtualcenter,dc=vmware,dc=int • Roles data under OU=Roles, Privileges data under OU=Privileges • Licensing information under OU=Licenses • Connection information under OU=Instances VI4 - Mod 1-3 - Slide

  48. ADAM prerequisites for Linked mode • Domain membership • If on different domains • trust relationship between machines on different domains • Machines should be able to ‘ping’ each other with fully qualified domain name, • i.e. ping xyz.abc.com • Pinging by IP address is not a strong enough guarantee! • Install should be done using domain accounts • Domain accounts should have privileges on local machine (on all Linked mode vCenters) to install into ‘join mode’ VI4 - Mod 1-3 - Slide

  49. Backing up ADAM data to DB • vCenter has an internal thread that backs up ADAM data • periodically (every 12 hours) • Note: Replication is done every 15 minutes AD • In case VC has trouble starting up due to a detected ADAM error • Attempts to load most recent backup • Verify integrity of backup • Restore ADAM DB files from backupBack up directory: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS\ • Restart ADAM service • On any failure, re-attempts backup with next older backup On vCenter Server Startup (vpxd logs ) [2008-11-06 15:39:35.326 05252 info 'App'] [LdapBackup] Backing up directory: C:\Program Files\ADAM\VMwareVCMSDS\ [2008-11-06 15:39:38.311 05252 verbose 'App'] [LdapBackup] Device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy74 [2008-11-06 15:39:42.686 05252 info 'App'] [LdapBackup] Deleted snapshot VI4 - Mod 1-3 - Slide

  50. Install issues with ADAM Jointool reports errors it encounters C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\status.txt See jointool-0.log as well C:\Documents and Settings\<User>\Local Settings\Temp List of operations performed by jointool Usual errors: Pre-operative validation errors: Name resolution errors Clock out-of-sync errors VI4 - Mod 1-3 - Slide

More Related