Link to home
Start Free TrialLog in
Avatar of JaymanMasterBuilt
JaymanMasterBuilt

asked on

Slow response from host in VI Client

We have recently changed the IP's on the ESX host's service console and we have things connected and working now but I still have one nagging problem. When using the VI client, managing the VM's is fast and   other features work well but when I click on a host in the left pain to view its status it stales the VI Client for about 5-10 seconds before you can click on anything else. Has anyone every seen this before or know where I could start looking for IP change related problems.
SOLUTION
Avatar of Paul Solovyovsky
Paul Solovyovsky
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of JaymanMasterBuilt
JaymanMasterBuilt

ASKER

I have checked all of the routing, gateway and DNS addresses that I can see in the VI gui and they all look okay. From my production lan I can ping by name all of the ESX servers.
Steps take to change the ip of the service console:
Using VI I changed the the IP of the service console and then disconected and reconnected the server.

In a few fourms I found people were deleting the vswif0 and creating a new one, is this a better approch and should I be doing this?
I would delete the vswif0 as the last resort. If do this make sure you have a service console available on a different vswitch so that you can connect and re-create
So the mothod I used should not have created the problem I am seeing?  
I've seen the method you have used create issues in the past.  To re-ip a console I normally create another console login through it and then re-ip the one on vswitch0.  This avoids any issues that may occur and you dont' lose connectivity.
I'm having the same problem. Any solution?
You can always create another console on a different vswitch.  Delete the original and re-create.  This alleviates the problem of deleting the console you're connected to and prevents any lockout issues.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The problem happens when the ESX host has the wrong IP for the license server.