Hi John,
We had the same issue with a new vMA that was upgraded from 5.1.0.0 to 5.1.0.1 (right out of the gates)
However, we were able to get it to work with this noted solution. (once we corrected a typo we had made)
alias vifptarget="source /opt/vmware/vma/bin/vifptarget"
source /opt/vmware/vma/bin/completion_vifp
source /opt/vmware/vma/bin/completion_vifptarget
source /opt/vmware/vma/bin/completion_vifs
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}/opt/vmware/vma/lib64:/opt/vmware/vma/lib
You might wish to double check for typos as we believe this solution is still valid. -j