Skip to main content

Deploying VCSA6.5 on VMware Distributed Switches (DVSwitches)

In one of my labs all the hosts and VMs are on the VMware distributed switch to mimic one of the production environment. When I planned for the upgrade from vSphere 5.5 to 6.5 in that lab and started deploying the VCSA 6.5 using the .iso image - I came across this. 



So, VMware doesn't support distributed switches with non-ephemeral port group when deploying the VCSA and PSC on 6.5. I read few articles and most of them suggested to migrate your vCenter 5.5 to Standard switch as well as build the new VCSA 6.5 on standard switch for smooth migration. 

But what if environment is 100% on distributed switch and going back and creating standard switch is not an option. Well, there is a work around to get past this screen. You will need to create a port group on distributed switch with "ephemeral binding". 




Once you create that port group on the distributed switch, all the VLANs/port groups from that distributed switch would show up and you can deploy the VCSA on the distributed switches. As you see in below screenshot - I have created one port  group with suffix ephemeral and now I can see all my VLANs/Port groups in the view for the selection of the network.



It may not be recommended way from the VMware to build the VCSA6.5 appliance but that is the way to snick in if you have everything on distributed switch. 

Another way - if you want to create just VCSA 6.5 with embedded PSC is using OVA file that is in the VCSA installer folder. So, instead of using the installer.exe (Located under - vcsa-ui-installer\win32) file for install use the .ova (Located under vcsa folder) to deploy the appliance. Once the appliance is deployed - you can use https://VCSAIP Address:5480 to get the option to configure, upgrade or migrate the vCenter.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to Check Up Time of ESXi Host or Virtual Machine from vCenter Server

To check up time of ESXi host from vCenter server - Logon to vCenter Server -  If using C# (fat) client - click on cluster - on right side pane click on Hosts - select the up time option by right clicking on the header. The column will be added at the end. You can drag and drop column to place it in your view. If using HTML client - click on cluster - on right side pane click on Hosts - select the up time attribute from show/hide column by clicking on the header  If using web (Flash)  client - click on cluster - on right side pane click on related objects - hosts - right click on the header to show/hide column - click on up time attribute Similarly,  you can check the up time for a virtual machine by clicking on the virtual machine tab instead of host tab, but only caveat  is vCenter gives you up time of a virtual machine according to reboots performed from the vCenter. So, rather than rebooting server fr...
Post a Comment
Read more

VMware vCenter 5.5 getting Disconnected Sporadically

I recently experienced an issue with vCenter 5.5 was getting disconnected sporadically. vCneter was running on windows 2012 server. I was able to see following errors in windows logs. vCenter Logs were showing following errors -          2018-08-18T01:30:03.630-04:00 [11432 error 'Default' opID=92132b4] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) ODBC error: (08S01) - [Microsoft][SQL Server Native Client 11.0]TCP Provider: The specified network name is no longer available.         2018-08-18T01:30:03.630-04:00 [11432 error 'Default' opID=92132b4] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) ODBC error: (08S01) - [Microsoft][SQL Server Native Client 11.0]TCP Provider: The specified network name is no longer available.         2018-08-19T19:28:31.801-04:00 [06368 warning...
Post a Comment
Read more

Initial Configuration of VMware NSX Manager

Here are the steps for the initial configuration of VMware NSX Manager-  Deploy NSX Manager for the vCenter. NSX manager and vCenter have 1:1 binding, so if there are multiple vCenters - multiple NSX manager needs to be deployed each in one vCenter Once NSX manager is deployed, logon to the NSX manager using the IP address or the FQDN of the NSX manager Configure the NTP settings by clicking on "View Summary" on home page and then clicking Configure NTP Servers from Manage - General - Time Setting  Once the NTP time settings are configured, configure look up service and vCenter Server to connect to the NSX manager. Click on manage vCenter registration and click on configure look up service to configure the lookup service. Accept the SSL certificate. Once Lookup service is connected successfully, register the vCenter to the NSX Manager. Note - SSO admin account (administrator@domain.local) needs to be used for the configuration of look up service and registration o...
Post a Comment
Read more