Unable to change Provider VDC virtual hardware support beyond version 10

-


My environment:

vCloud Director 9.1.0.3 and ESXi 6.5.0.

 This could happen regardless of what vCloud director and ESXi version you are on.




Provider VDC config: 



ESXi Version : 



So ideally I should be able to see the hardware version 13 in the vCloud director but I see only till version 10


Why does this happen : 

It’s most likely a user error depending on how vCenter is set up and what vCenter has reported to VCD as far as available HW versions

How to fix ? 

 From vCenter FLEX UI, go to Datacenter, right click and select 'Edit Default VM Compatibility' and there select 'ESX 6.5 and later' (This config depends on your environment)
Then go to the cluster and right click and select 'Edit Default VM Compatibility' and there the value selected would be 'Use datacenter setting and host version'. This setting would take it from datacenter setting done above.

From the vCloud director , perform and refresh of the vCenter and try to create the Provider VDC and check the HW version.

If  the refresh does not do the trick then you will need to do a clean up of the inventory tables and have the updated entries added into the vCloud director database.

NOTE : Take a Backup of the vCD Database before performing this operation

- Stop the vCloud director service on all the cells.
https://docs.vmware.com/en/vCloud-Director/9.1/com.vmware.vcloud.install.doc/GUID-65C8B7B6-EC5E-4BDA-8564-56DD6671F5FE.html

- Run the below query on the vCD Database (Below query has been tested till vCD 9.5) . I understand the queries look scary but these are just inventory which gets repopulated automatically when the vCenter is connected to the vCloud director.

Delete from     vm_dstore_metrics_inv;
Delete from     managed_server_inv;
Delete from     vm_inv;
Delete from     datastore_inv;
Delete from     ccr_drs_rule_inv;
Delete from     resource_pool_inv;
Delete from     drs_rule_vm_inv;
Delete from     dv_switch_inv;
Delete from     network_inv;
Delete from     dv_portgroup_inv;
Delete from     custom_field_manager_inv;
Delete from     ccr_drs_host_group_inv;
Delete from     datacenter_inv;
Delete from     ccr_drs_host_group_host_inv;
Delete from     folder_inv;
Delete from     ccr_drs_vm_group_inv;
Delete from     compute_resource_inv;
Delete from     ccr_drs_vm_group_vm_inv;
Delete from     cluster_compute_resource_inv;
Delete from     ccr_drs_vm_host_rule_inv;
Delete from     storage_profile_inv;
Delete from     datastore_profile_inv;
Delete from     managed_server_network_inv;
Delete from     managed_server_datastore_inv;
Delete from     datacenter_network_inv;
Delete from     storage_pod_inv;
Delete from     task_inv;
Delete from     property_map;

- Start the vCloud director service on one of the cells
- Wait for the sync to complete
- Start the other cell(s) ( If any)


Hope it helps :)

Comments

Post a Comment

Popular posts from this blog

vCloud director 9.7 appliance deployment step by step guide

-
Image
With the new vCloud director releasing and making it full appliance with embedded vpostgres, I though I will put up a post with the complete installation guide. There have been some challenges in the getting the deployment successful. Prerequisite : Reverse DNS proxy must be configured for the eth0 ipaddress. This is to get the correct hostname for the appliance.  The NFS share is setup for the VCD transfer directory. It is recommended to have the eth0 and eth1 in different subnets. eth0 is for the vcd cell and eth1 is for the vPostgres .The reason for the having 2 subnets is to avoid duplicate entries in the route table.  Installing vCloud director step by step guide :  I should ideally be using different submets as per the VMware documentation but since I do not have a different portgroup setup, I am going with the same subnet.  As mentioned in the prereq section, the reason for the having 2 subnets is to avoid duplicate entries in the route tab
Read more

How to Install and Uninstall Guest agent for vRA Windows machines

-
Image
Connect to the vRA appliance using the IP or hostname  Choose the appropriate setup for your Windows server  Extract the files to C:\VRMGuestAgent\ . In my case, I have already extracted it.  Before you install the guest agent download and install the IAAS manager server certificate into the windows machine  Save the file as Cert.cer  Install the Cert into the Local machine and Trusted root store Rename the cert.cer to cert.pem and move it to folder C:\VRMGuestAgent\ Now, copy the certificate file into the vRMGuestAgent Extracted folder  Open the command prompt as admin and navigate to C:\VRMGuestAgent. In this case 192.168.2.15 is my Manager server . The default port is 443.  You will see the Guest agent service in the services list. Manually start the service.  Your windows guest agent is installed :)  How to Uninstall Guest agent on windows machine  To uninsta
Read more

VM console fails to connect - vCloud director 9.7

-
Image
I deployed a new vCloud director 9.7 and the VM console fails to connect even though the certificates and URLs are updated correctly in Public Addresses. The chrome browser console (ctrl+shift+j) fails like below :  failed: Error during WebSocket handshake: Unexpected response code: 404 After reading the VMware documentation which says " For an installation with a single IP address, you can customize the console proxy address from the  vCloud Director  Web Console. For example, for the  vCloud Director  appliance, you must customize the console proxy address to  vcloud.example.com :8443 " From vCloud director 9.7, the second network (eth1) is dedicated to vpostgres database and console proxy uses (eth0) with a custom port 8443 Fix :  Update the console proxy address with custom port 8443 under vCD portal --> Administrator --> Public addresses Tadaa!  Thanks for reading. Hope it helps :) 
Read more