I just deployed the latest vMA 5.1 after attempting vMA 5.0 Patch 2 and being unable to resolve issues with the proxy settings. IMO vMA 5.0 and vMA 5.1 are just simply awful. Anyway, I need some help with vMA 5.1.
After struggling through a myriad of issues deploying and configuring vMA 5.1, I've got it up and running. I can SSH to it, I can resolve DNS perfectly, CPU load is minimal, RAM is fine, disk is fine, etc. Things mostly work as expected.
However, whenever I SSH to vMA, it takes on average 35 seconds to get a login shell. 35 seconds! vMA 4.1 was instantaneous, as you might expect.
The next problem is this: I added the vCenter server via "vifp addserver" and it was slow to finish the request. I then targeted vCenter via "vifptarget -s" and it takes about 12 seconds to complete the request.
vMA 4.1 didn't have any of these problems at all. What gives? I have not been able to find anything yet that answers my questions. I've seen various threads relating to people being unable to SSH at all (not a problem here) or having messed up DNS lookups (again, not my problem here either). But I can't find anyone who is having slow network performance with vMA 5.x where vMA 4.x had none.
Thanks for any and all input!
--Matt