Sunday, 16 September 2012

How to Install vCenter 5 with SRM 5 and Compellent Integration - Part 2

The following step-by-step walkthrough goes through the steps for installing a vSphere 5 infrastructure with SRM and integrating with Compellent Enterprise Manager. The article has been split up into 4 parts:


Part 2: Install the vCenter Servers

VC01 - vCenter Install
2.1 Login with the VMService account
2.2 Download and install the SQL Server Native Client - SQLNCLI_AMD64.msi - from the Microsoft SQL Server 2008 R2 SP2 Feature Pack.
2.3 Administrative Tools > Data Sources (ODBC) > Add a new System DSN with the SQL Server Native Client 10.0 driver > and configure with name = “VMware vCenter”, to connect to the Database server Instance, with integrated Windows Authentication, and change the default database to = “VIM_VCDB”
Note: If the Database Server and Instance does not populate the “Which SQL Server do you want to connect to?” field, check Windows Firewall is not getting in the way.
2.4 Mount the VMware vCenter 5.0 U1a ISO and run the autorun.exe
2.5 Run the VMware vCenter Server Product Installer, using the DSN created in 2.3, and install to D drive, and - being the first vCenter - this will be a standalone VMware vCenter Server instance
Note: I always tick the box to increase the number of ephemeral ports available!
2.6 Restart when prompted

VC01 - Additional vCenter Components
2.7 Install vSphere Client
Note: The following 2.9 and 2.10 are required for the Compellent vSphere Plug-in
2.9 Run PowerShell as Administrator and enter the command> Set-ExecutionPolicy RemoteSigned
2.10 Install vSphere PowerCLI
2.11 Install the Compellent vSphere Plug-in
Note: 2.12 is required for vSphere Web Client
2.12 Download and install Adobe Flash Player
2.13 Install vSphere Web Client (Server) and register at http://localhost:9090/admin-app

VC01 - vCenter Update Manager
2.14 Run odbcad32.exe from C:\Windows\SysWOW64 and create a new System DSN with the SQL Server Native Client 10.0 driver > and configure with name = “vCenter Update Manager”, to connect to the Database server Instance, with integrated Windows Authentication, and change the default database to = “VIM_VCDB”
2.15 Install VMware vSphere Update Manager
Note 1: Untick the ‘Download updates from default sources immediately after installation’ as Update Manager will be configured as per requirements later
Note 2: Remember to use FQDN’s and change the install paths to D
2.16 via Services.msc change the Log On for the VMware vCenter Site Recovery Manager Server service to the VMService account, and restart the service
2.17 via the vSphere Client - Plug-ins, download and install the VMware vSphere Update Manager Extension

VC01 - Further Configuration
Note: At this point, all vCenter softwares are installed; the following steps are done via the vSphere Client connected to vCenter
2.18 Create Datacenter object(s)
2.19 Create Cluster object(s)
2.20 Add Host(s)
2.21 Create VM Storage
2.22 Create/Add Virtual Machine(s)
Note: A recommended tweak for vCenter: vSphere Client > Home > vCenter Server Settings > Set Database Retention Policy to 100 days or less to limit the growth of the Database

VC02
2.23 VC02 Is configured as per VC01 and steps 2.1 to 2.22, the only difference being that that installation of vCenter is done as Linked Mode!

No comments:

Post a Comment