Syed's Notes

 VCF 9.0.1 How to update DNS IPs for VCF 9.0.1 environment. While deploying the VCF, I deployed it with only one Domain Controller which was serving NTP & DNS for the deployment itself. Post deployment, I had to reboot the DC and realised that there is only one DNS and NTP serving the whole stack, so I had to build a redundant DC and join it as secondary DC.  Once I finished with secondary DC, I had to update the secondary IP address on all the components, so make the new IP usable on all components, you have to update it on SDDC Manager and follow these steps. I have used VCF API Explorer in the SDDC Manager's Developer Center. Step 1: Perform a GET request to view the current configuration. Step 2: Perform a PUT request with the updated DNS servers in the request body, ensuring the isPrimary flag is set correctly for each server.  For example: {   "dnsServers": [     {       "ipAddress": "172.16.128.225",       "isPrim...

  Resolving Cross-vCenter Migration Issues with Large VMs (>30TB) Credits of this article: During cross-vCenter migrations, we encountered issues with large VMs (>30TB), resulting in prolonged migration times (days) and frequent failures (every 3rd migration). VMware support provided a workaround to extend the port reservation timeout. *Workaround Steps:* Step 1:  SSH to vCenter and take a backup `vpxd.cfg`:  cp /etc/vmware-vpx/vpxd.cfg /etc/vmware-vpx/vpxd.cfg.bak   Step 2:   Edit `vpxd.cfg` and add below ``` <vpxd> <dvs> <PortReserveTimeoutInMin>7200</PortReserveTimeoutInMin> </dvs> </vpxd> ```   This extends the port reservation timeout to 5 days (7200 minutes). 1. Restart `vpxd` service: ` service-control --restart vmware-vpxd ` 2. Retry vMotion for large VMs. 3. Post-migration, revert `vpxd.cfg` to its original state: `cp /etc/vmware-vpx/vpxd.cfg.bak /etc/vmware-vpx/vpxd.cfg` 4. Restart `vpxd` service ag...