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

Post a Comment

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 permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot 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...
2 comments
Read more

Issue : Configure Management Network option is Grayed out into ESXi

Last week I got into an issue of one of my client into Vsphere environment where one of its ESXi went done out of the network. Issue was IP address was showing 0.0.0.0 on main Esxi screen and when I tried to change the network configuration, its " Configure Management network option was greyed out.  I tried to gid into it and try to analyis its vmKernal and vmwarning logs. What I found is its VMkernal switch got removed due to unexpected reason. So to resolve the issue I tried to reconfigure its vswitch0 (vmk0) by going into Tech Mode of that Exi. Below are the steps which I followed to resolve the issue. 1) Login to ESXi 2) Press F2, Check if you " Configure Management network " is greyed out or not" if yes,    follow below 3) Press ALT+F1 to move the ESXi screen to tech mode   ( This is command line like dos) 4) login with root account 5) Run the following command into it esxcli network ip interface add --interface-name= vmk0 ...
2 comments
Read more

Collecting Logs from NSX-T Edge nodes using CLI

  This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)
Post a Comment
Read more