• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Weird issue between vSphere Thick and Web Client

V

Vader

Supreme [H]ardness
2FA
Joined
Dec 22, 2002
Messages
5,137
I'm sure this may be known but I know some readers are members who work for VMware so I wanted to bring this up and see if it's an issue on my end or maybe a known or issue with the software.

This morning I was enabling Jumbo Frames on the vSwitch that houses the vMotion VMkernel and I found that in the web client, the vSwitch shows 1500 MTU but in the vSphere thick client it is shown correctly at 9000.

Anyone else experience this issue?
 
Last edited:
We're going to start seeing more and more issues like this as the legacy client fades into oblivion. :(

Did you try hitting the refresh button in the web client to see if it updates?
 
They better come up with an easy single host mgmt solution before they get rid of the C# client...or we'll all have to become proficient at CLI..lol..which may not be a bad thing..but in a sticky situation..forget it.

Yeah..refresh does nothing..logged out and logged back into the webclient..still shows 1500MTU..lol.
 
I just checked here at home... all the settings match between the local client and the webclient. Whenever I issue changes from the local client and reload the webclient, the change is shown correctly. I'm on 5.1 U1.
 
It could be that the thick client is wrong and needs to refresh.

Without getting myself in trouble, I’ll just say the webclient is going to get better soon. Unfortunately that also means the thick client will be sunset.

I spend 8+ hours a day in both clients but do most of my work in Pcli.
Both clients do get out of sync for a random amount of time because of refresh rates and vcenter being lame.
If you ever make a change and it appears to be "weird" throw some quick powercli at it to see what is returned from vcenter. Or, to be 100% sure, do some testing. If you enabled a 9K MTU, throw some jumbo, non fragmented packets through it.

SSH into the host and attempt a vmkping
vmkping -d -s 8500 10.10.10.10
 
The thick client is basically useless in 5.5. You can't edit any VMs you update to v10 which can cause problems if you're in a failure situation. I've also seen several times where things don't match between the clients. I only trust the web client at this point.
 
It could be that the thick client is wrong and needs to refresh.

Without getting myself in trouble, I’ll just say the webclient is going to get better soon. Unfortunately that also means the thick client will be sunset.

I spend 8+ hours a day in both clients but do most of my work in Pcli.
Both clients do get out of sync for a random amount of time because of refresh rates and vcenter being lame.
If you ever make a change and it appears to be "weird" throw some quick powercli at it to see what is returned from vcenter. Or, to be 100% sure, do some testing. If you enabled a 9K MTU, throw some jumbo, non fragmented packets through it.

SSH into the host and attempt a vmkping
vmkping -d -s 8500 10.10.10.10
Click to expand...

Yeah..I validated the functionality through vmkping before..it works..it's just not showing properly.

The thick client is basically useless in 5.5. You can't edit any VMs you update to v10 which can cause problems if you're in a failure situation. I've also seen several times where things don't match between the clients. I only trust the web client at this point.
__________________
Click to expand...

Eeeek..!
 
I've had a couple of times where the clients get unsynched, but each time it's been the web client that's wrong. The most common one is starting a VM on the web client and the console never shows anything, but the thick client can open console and use the VM. I haven't seen a case yet where the thick client was giving incorrect info, though I'm sure it will happen eventually.
 
Vader said:
They better come up with an easy single host mgmt solution before they get rid of the C# client...or we'll all have to become proficient at CLI..lol..which may not be a bad thing..but in a sticky situation..forget it.

Yeah..refresh does nothing..logged out and logged back into the webclient..still shows 1500MTU..lol.
Click to expand...

We have a solution coming, don't worry ;)
 
You must log in or register to reply here.
Back
Top