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 again.
*Note:*
- This workaround requires vCenter downtime due to the `vpxd` service restart.
- This solution is specifically for large VM migrations (>30TB) and should be reverted post-migration.
Comments
Post a Comment