google.com, pub-4920175566720914, DIRECT, f08c47fec0942fa0 Skip to main content

Installing vCenter Appliance 6.5


vCenter appliance 6.5 is one of the latest & stable release of vCenter . vSphere 6.5 adds an X-Large deployment size, the update manager and a fully supported migration assistant to the appliance. So it’s time to migrate your Windows based vCenters to appliance with vSphere 6.5.
vSphere 6.5 is fully dependent on webclient. So no more vSphere client or C# client.

VCSA 6.5 Enhancements

  • Supports up to 2000 ESXi Hosts and 35.000 Virtual Machines
  • Guided Installer (Interactive Installer, instead of OVF Template)
  • Robust deployment (Separate Deployment and Configuration to prevent failed deployments
  • Migration Assistant (Migrate vCenter Server 5.5 or 6.0 for Windows to vCenter Server Appliance)
  • Native High Availability
  • VMware Update Manager
  • Built-In Backup+Restore
  • Improved Appliance Management
  • HTML5-based vSphere Client
  • Photon OS (Replaces SUSE Enterprise 11)

Compatibility 

To view the compatibility of Esxi, vCenter server and vsphere client version, hardware compatibilty for Esxi , device comparability, Guest operating system compatibility, VM compatibility for Esxi. please use below link.

http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php

For Hardware compatibility for Esxi follow below link

http://www.vmware.com/resources/compatibility/search.php


So, Get started with the deployment of vSphere 6.5

  1. Download the VMware VCSA 6.5 ISO from MyVMware
  2. Mount the ISO or extract it and depending upon the system (Linux, Windows or Mac) you’re using to start the deployment locate the installer folder under ‘vcsa-ui-installer’
  3. Create A record & PTR for the vCenter
  4. If you were not configuring AD, add host entry details.



1) Launch the installer

Follow the instruction and click on Install if its a fresh install or select Upgrade if you have upgrade plan.





Accept the agreement with VMware and select the deployment model as per your design






Enter the details of ESXi host or vCenter server



Accept the SSL certificate prmpt and enter the name of VCSA VM and credentials.


Specify the deployment size and based on your environment and LLD.

Select the datastore where you would like to install

At end configure networking requirements 


After this review the configuration and start the deployment.


Stay tuned for next update.... : :)

Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x
You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out.
Now the option left is from the command line of VCSA appliance.
Below steps will make it possible to change the FQDN of the VCSA from the command line.
Access the VCSA from console or from Putty session.Login with root permissionUse above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_netOpt for option 3 (Hostname)Change the hostname to new nameReboot the VCSA appliance.After reboot you will be successfully manage to change the FQDN of the VCSA .

Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client.

If you are using self-signed certificate, you can regenerate the certificate with the help of below KB 2112283 article.



Happy Sharin…

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment.
Somewhere during security auditing we require to provide several information to security team to get successful audit.
One of them is the compliance of Virtual machine auditing of creation date and time.
Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi.
To get the details we will use VMware Powercli to extract the details.
By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date.
Below is the function which needed to be copy and paste into the Powercli.
=======================================================================
function Get-VMCreationTime { $vms = get-vm $vmevts = @() $vmevt = new-object PSObject foreach ($vm in $vms) { #Progress bar: $foundString = "       Found: "+$v…

Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk

Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading. Issue occur when the customer was performing migration activity of virtual machine.
We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing.
On VCSA Shell: service-control --status vmware-vpxd shows "stopped" service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again
VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state.
Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA. After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds.
Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more than 1032 ms or more.
VCSA has generated the core dump at /var/core. …