the vma is running slow, specially when I have connected to a remote esx server using a vifptarget cmd.
It just sits there. I have used console connection, putty, duplicate sessions in putty and all of them are showing me the same behaviour. Wonder, where is the problem.
BTW - I have also upgraded the memory to 1GB and this is vMA 4.1 - connected to ESX (4.1 build - 260247) target
Do you have any stale targets that's still in vMA? I've seen this to sometimes slow things a bit, but in general it's pretty responsive. Things going over the API won't be as snappy as running them directly on an ESX(i) host, but it shouldn't be sitting there. This maybe due to stale targets that vMA is still trying to access.
Try running the following command and verify that all of these hosts are still valid:
Also are you using vMA as a syslog system and are you logging multiple/all hosts? How many targets is your vMA managing?
Lastly, I would recommend taking a look at the vMA logs to ensure no errors are being thrown:
So all targets that's currently managed by vMA are accessible? Meaning you can manually connect to them? Have you taken a look at the logs as I mentioned to see if there's any warning/errors? How many targets are you managing? Is the filesystem full on vMA?
This is no annoying...something is definately a problem here
1) vifp listservers -l - gave me only one server as listed
2) vifptarget -d - show no fastpass target set
3) vifptarget -s <servername> - the putty session just sits there witout any prompt and eventually logs me out
4) from the vi client console - The same behaviour - no cursor, just blank.....
Checked the logs nothing interesting....
No idea, what to do now....