Skip to main content

Disable vCenter vCLS advanced settings

   1. SSH into your vCenter Server

   2. Open the vpxd config file:


vi /etc/vmware-vpxd/vpxd.cfg

   3. Search for  <vcls> inside the file

   4. You will see something similar to this (if you have any other clusters that you have disabled vCLS on, you will also see them):

  <vcls>

    <clusters>

      <domain-c1003:1f309344-8dbb-4c9f-b0cb-b3b61fa8513f>

        <enabled>False</enabled>

      </domain-c1003:1f309344-8dbb-4c9f-b0cb-b3b61fa8513f>

      <domain-c13>

        <enabled>False</enabled>

      </domain-c13>

    </clusters>

  </vcls>

   5. You will have to modify this file and remove the record you do not want . In your case, you will have to delete this tag (incl. its content):

      <domain-c1003:1f309344-8dbb-4c9f-b0cb-b3b61fa8513f>

        <enabled>False</enabled>

      </domain-c1003:1f309344-8dbb-4c9f-b0cb-b3b61fa8513f>

!!! If you do not have any other clusters, where vCLS is disabled on, you will have the following configuration:

  <vcls>

    <clusters>

      <domain-c1003:1f309344-8dbb-4c9f-b0cb-b3b61fa8513f>

        <enabled>False</enabled>

      </domain-c1003:1f309344-8dbb-4c9f-b0cb-b3b61fa8513f>

    </clusters>

  </vcls>

In this case, please remove the whole <vcls> ... </vcls> entry. !!!

   6. Save the changes to the file.

   7. Restart vpxd:

service-control --restart vmware-vpxd

   8.Upon successful restart you should receive the following message:

Successfully restarted service vpxd

   9. If you go the Advanced Settings tab in the vSphere Client now, the changes should have taken place.

Comments

Post a Comment

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported