All Posts

or maybe it will help: VMware VCP-DCV 2023 Study Guide: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/certification/vmw-vcp-dcv-8-exam-guide.pdf https://drive.google.com/file/d/105pwcW563PMmNma4aN7TxoooIIfl8nU-/view

I found a new issure for this. 1. Do all above 2. look for the service HV-Hostservice. This Serice is listed as manuel but is started. End the service and restart. After restart the service is not started.  Now it works

Just for Information & future reference As per Aria Automation's August release notes, due to license changes related to Terraform VMware restricted the use of Terraform versions greater than 1.5.5. Refer to the below link VMware Aria Automation Release Notes

Could you give it a shot and set up a Provider VDC initially with a cluster or resource pool from the linked vCenter? the ESXi Servers in the 'Hosts' section will only show up after creating a PVDC, but I could be mistaken.

Hello, I am a user of VMware technologies as much as you are, nothing more nothing less, in my free time I express my opinions (which are worth what they're worth) and I try to help other users like me (and that doesn't mean I succeed). But If I encounter a particularly particular problem that I am not confident I can resolve independently, I will turn to VMware asking for support (a so-called "SR"), and if I have to, paying the asking price. If you start updating things based on what you find written on a forum and then something goes wrong, who do you turn to "to fix it". The risk always remains yours alone, not someone else's, I understand that you don't like what I say at all, I'm sorry, it doesn't change the state of things. Regards, Ferdinando

so I checked all the usual suspects and nothing could explain it, then I checked task manager and for some reason trend micro (not my choice) and spotify were going crazy. I force closed spotify and now my VMs behave exactly like i'm used to (good for the hardware Im given). So strange that spotify was causing some kind of interaction

Hello, I can suggest you to remove the stale entries from the NSXT backend corfu database which is usually done with help of VMware support and we dont suggest it to be done by our customers. But prior to this you would need to collect the support bundles of all the nsxt manager nodes and also take a backup of the NSXT cluster following the official documentation: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/administration/GUID-A0B3667C-FB7D-413F-816D-019BFAD81AC5.html Below are some steps you could follow, but please involve VMware support for these operations and advised not to attempt on your own. You could do the following as below:- 1. Check for presence of ReplacementInfo corresponding to the Edge nodes that fail to delete in the below corfu table:  a)/opt/vmware/bin/corfu_tool_runner.py -o showTable -n nsx -t ReplacementInfo. b) Copy the key value corresponding to deleted edges. 2. Determine edge nodes with "markedForDelete": true in the exported table EdgeTransportNode using /opt/vmware/bin/corfu_tool_runner.py -o showTable -n nsx -t EdgeTransportNode. 3. Stop all services: service proton stop; service corfu-server stop. Start only Corfu: service corfu-server start 4. Delete stale records where table contains key in format Edge path ending with UUID. Table names are mentioned in bold below:                   /opt/vmware/bin/corfu_tool_runner.py -o deleteRecord -n nsx -t ReplacementInfo --keyToDelete '{"stringId": "/infra/sites/default/enforcement-points/default/edge-transport-node/<edge-id>"}' /opt/vmware/bin/corfu_tool_runner.py -o deleteRecord -n nsx -t EdgeNodeExternalConfig --keyToDelete '{"stringId": "/infra/sites/default/enforcement-points/default/edge-transport-node/<edge-id>"}' /opt/vmware/bin/corfu_tool_runner.py -o deleteRecord -n nsx -t EdgeNodeInstallInfo --keyToDelete '{"stringId": "/infra/sites/default/enforcement-points/default/edge-transport-node/<edge-id>"}' /opt/vmware/bin/corfu_tool_runner.py -o deleteRecord -n nsx -t EdgeNodeConfigInfo --keyToDelete '{"stringId": "/infra/sites/default/enforcement-points/default/edge-transport-node/<edge-id>"}' /opt/vmware/bin/corfu_tool_runner.py -o deleteRecord -n nsx -t GenericPolicyRealizedResource --keyToDelete '{"stringId": "/infra/realized-state/enforcement-points/default/edge-transport-node/<edge-id>-edgetn"}' /opt/vmware/bin/corfu_tool_runner.py -o deleteRecord -n nsx -t EdgeTransportNode --keyToDelete '{"stringId": "/infra/sites/default/enforcement-points/default/edge-transport-node/<edge-id>"}' /opt/vmware/bin/corfu_tool_runner.py -o deleteRecord -n nsx -t DeletedVm --keyToDelete '{"stringId": "/infra/sites/default/enforcement-points/default/edge-transport-node/<edge-id>"}' This is not a full list of the steps but some of the things that could be done, but not without VMware support involved.

My tip for you: Why no training? You can try or start the journey similarly: VMware Certified Professional - VMware Cloud 2023 (VCP-VMC) is the ideal way to get started. 1. Take the free course "Designing, Configuring, and Managing the VMware Cloud 2. Register for exam 2V0-33.22 and pass it 3. Register for exam 2V0-21.23 and pass it without mandatory training VMware Certified Professional - VMware Cloud 2023 (VCP-VMC) https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/certification/vmware-vcp-vmc-certification-details.pdf + VMware Certified Professional - Data Center Virtualization 2023 (VCP-DCV) https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/certification/vmw-vcp-dcv-certification-preparation-guide.pdf

I have the same issue now in a production environment where the NFS is (well.. was) used for a temporary backup. also, I'm not sure if I got the explanation from your side completely, but for me the deployment of the file service node for all 8 hosts works without an issue, and even the file service status shows enabled. However, it throws the same root FS UUID error for us. The vCenter and the ESXi hosts have been upgrade to 8U1 upgrade before the shipment to the customer, where the file service was still working.