This is default and expected behaviour.
Please see the workaround section for a workaround.
Workaround:
To workaround this issue, port reservation timeout needs to be extended to allow the migration to complete:
1. SSH to the vCenter.
2. Make a copy/backup of file /etc/vmware-vpx/vpxd.cfg:
cp /etc/vmware-vpx/vpxd.cfg /etc/vmware-vpx/vpxd.cfg.bak
3. Insert the following section to vpxd.cfg:
<vpxd>
<dvs>
<PortReserveTimeoutInMin>7200</PortReserveTimeoutInMin>
</dvs>
<cert>This will extend port reservation timeout to 5 days (24*60*5=7200), and it should be enough to cover any time-demanding (slow/large VM (50TB+)) share-nothing vMotion.
4. Restart vpxd service:
service-control –-restart vmware-vpxd
5. Re-try storage vMotion of your large VM(s).
6. Once the VMs have been migrated, revert the vpxd.cfg file back to its original form:
cp /etc/vmware-vpx/vpxd.cfg.bak /etc/vmware-vpx/vpxd.cfg
7. Restart vpxd service:
service-control --restart vmware-vpxd