dm330
Contributor
Contributor

VC2.5u3 and ESX 3.0.3 many disconnects

Hello all

We have many disconnects troughout the clusters and with almost any action we get

disconnect errors...

One article comes close:

There's a new problem a few customers have reported whereby-

ESX disconnects randomly from VirtualCenter

ESX disconnects when performing VI Client tasks from VirtualCenter.

Tasks randomly timeout after a long idle time

"An error occurred communicating to the remote host" pops up.

So i think it has something to do with VC2.5U3 ???

What do you think.. ?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
20 Replies
RParker
Immortal
Immortal

We have many disconnects troughout the clusters and with almost any action we get disconnect errors...

Same here. The weird part is that I can be on a host, looking at esxtop or the logs, and it never shows up in the logs there was ever any problem, yet VC complains the host dropped. But when I do a constant ping to a host from VC machine, the host never disconnects, it's like a steady stream of activity to the host will 'keep alive' the connection, even though there really isn't a problem. This has been a problem since U2 however, maybe even U1, but it hasn't been corrected. I just ignore it since I know there isn't a problem.

0 Kudos
dm330
Contributor
Contributor

yes exactly

we have the same problems as you have,

i cannot see any problems in VC or ESX and the logfiles as far as i can see are clean...

but i am not going to ignore it it must be solved!

we pay a lot of money for support so we have droped a note there as well.. :smileyangry:

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
dconvery
Champion
Champion

Has anyone tried to remove the ESX from inventory and add it back? That would re-install the agent.

Enter maintenence mode to vmotion all live VMs off

Disconnect

Remove

Add host back to cluster.

Exit maintenence mode.

Dave

************************

The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents.

Nathaniel Borenstein

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"
0 Kudos
dm330
Contributor
Contributor

Yes

if i remove an esx server and add it back it still gives these problems.

If i completely reinstall an esx server the problems are also still there...

It is pure the communication between VC and ESX which goes wrong

many times the second try goes oke like;

power on or power off, Vmotion, migrate, clone, deploy a virtual machine

The problem is that like with a clone the machine is 1/2 created/cloned and the second try you get a second virtual machine like VM and VM_1 !

and then you have to delete the VM which in turn cannot be deleted the first time or you have to do it on the shell...

a lot of VC actions goes wrong the first time... Smiley Sad

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
dm330
Contributor
Contributor

I have found an option in our Cisco PIX firewall stateful cluster which seems to improve a lot 1 on 3 migrations goes ok and the third which takes too long for the TCP segment size gives me an error in VC but

No TCP Deny in the firewall anymore and the migration of the third does go oke even with the error "An error occurred while communicating with the remote host"

Here it goes:

Cisco PIX firewall v7.2.2 ASDM GUI

Go to

Configuration --> TCP Options --> Disable "Force maximum segment size for TCP proxy connection" so it is "0" unlimited (default is 1380 bytes)

The default TCP segment size is to small for vmware actions because I see sizes like 2000 -> 9000 which is way higher!

On the cmdline it is

#sysopt connection tcpmss 0

#wr mem

thanks for Elisha for helping me getting started Smiley Happy

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
dm330
Contributor
Contributor

well the problems are not resolved yet

1 out of 5 migrations / vmotions goes wrong and gives me the "error while communicating" but does not give me a tcp deny message in the pix firewall. (before it was 4 out of 5 went wrong)

migrating from one cluster to another cluster does give me a tcp deny error and a "error while communicating"

spontaneous disconnects from esx server: seen from pix firewall syslog

Feb 2 10:00:32 pixfirewall %PIX-6-106015: Deny TCP (no connection) from vc-server/4959 to esx-server/443 flags ACK on interface dmz-vlan41

Feb 2 10:00:32 pixfirewall %PIX-6-106015: Deny TCP (no connection) from vc-server/1610 to esx-server/443 flags PSH ACK on interface dmz-vlan41

After deploying a vm got following but no error in Virtualcenter:

Feb 2 14:54:24 pixfirewall %PIX-6-106015: Deny TCP (no connection) from vsw-vcs-001/4325 to esx-server/902 flags RST on interface dmz-vlan41

Feb 2 14:54:24 pixfirewall %PIX-6-106015: Deny TCP (no connection) from vsw-vcs-001/4325 to esx-server/902 flags RST on interface dmz-vlan41

Explanation of syslog message id "106015"

Error Message %PIX-6-106015: Deny TCP (no connection) from IP_address/port to

IP_address/port flags tcp_flags on interface interface_name.

Explanation This message is logged when the firewall discards a TCP packet that has no associated

connection in the firewall unit's connection table. The firewall looks for a SYN flag in the packet,

which indicates a request to establish a new connection. If the SYN flag is not set, and there is not

an existing connection, the firewall discards the packet.

Recommended Action None required unless the firewall receives a large volume of these invalid TCP

packets. If this is the case, trace the packets to the source and determine the reason these packets were

??? anyone ???

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
bnelson
Enthusiast
Enthusiast

I have the same problem only different. I can't add a new host to vCenter after upgrading to U3.I don't have a solution for you.

I have not tried vMotion yet; that was next after the upgrade

Hang 2 LEDs in the datacenter. The students are coming! The students are coming!
0 Kudos
alexherrera
Contributor
Contributor

Hi all I have the same problem too. Is a fresh install of ESX 3.5 with Update 3 and my host keep getting disconnected with nothing on the logs that points to any particular reason. I do know we have a PIX firewall so that might be the culprit. If any body can give more information on this it will be greatly appreciated.

Peace.

0 Kudos
bnelson
Enthusiast
Enthusiast

Well, I found the problem. VMware broke lmgrd with U3. Notice the port and IP address listings (clean install of vCenter 2.5 U3). lmgrd is only listening on 127.0.0.1. The ESX clients are never going to get a license that way.

Brian Nelson

VMWARELM.exe 3720 10.110.97.19 27010 10.110.97.19 3549 ESTABLISHED TCP C:\Program Files\VMware\VMware License Server\VMWARELM.exe

lmgrd.exe 3712 127.0.0.1 27000 127.0.0.1 3533 ESTABLISHED TCP C:\Program Files\VMware\VMware License Server\lmgrd.exe

vmware-converter.exe 3324 0.0.0.0 9086 LISTEN TCP C:\VMware\Infrastructure\Converter Enterprise\vmware-converter.exe

vmware-converter.exe 3324 127.0.0.1 9085 127.0.0.1 3704 ESTABLISHED TCP C:\VMware\Infrastructure\Converter Enterprise\vmware-converter.exe

java.exe 2756 0.0.0.0 9084 LISTEN TCP C:\VMware\Infrastructure\Update Manager\jre-1.5.0-12\bin\java.exe

vpxd.exe 1808 127.0.0.1 8089 LISTEN TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

Tomcat5.exe 3928 0.0.0.0 8086 LISTEN TCP C:\VMware\Infrastructure\VirtualCenter Server\tomcat\bin\Tomcat5.exe

vpxd.exe 1808 127.0.0.1 8085 127.0.0.1 3706 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vmware-updatemgr.exe 2788 127.0.0.1 8084 LISTEN TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

Tomcat5.exe 3928 0.0.0.0 8009 LISTEN TCP C:\VMware\Infrastructure\VirtualCenter Server\tomcat\bin\Tomcat5.exe

Tomcat5.exe 3928 127.0.0.1 8005 LISTEN TCP C:\VMware\Infrastructure\VirtualCenter Server\tomcat\bin\Tomcat5.exe

lsass.exe 420 0.0.0.0 4500 LISTEN UDP C:\WINDOWS\system32\lsass.exe

vpxd.exe 1808 127.0.0.1 3706 127.0.0.1 8085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

VpxClient.exe 3584 127.0.0.1 3705 127.0.0.1 443 ESTABLISHED TCP C:\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe

vpxd.exe 1808 127.0.0.1 3704 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3703 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3699 10.110.97.38 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3697 10.110.97.38 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3696 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3695 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3694 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3693 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3692 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3691 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3689 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3688 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3687 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3686 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3685 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3684 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3676 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3675 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3674 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3673 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3672 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3671 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3669 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3668 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3667 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3666 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 127.0.0.1 3656 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3655 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

Unknown 0 127.0.0.1 3652 127.0.0.1 8085 TIME_WAIT TCP

Unknown 0 127.0.0.1 3651 127.0.0.1 443 TIME_WAIT TCP

vpxd.exe 1808 127.0.0.1 3649 127.0.0.1 9085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3648 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

Unknown 0 127.0.0.1 3646 127.0.0.1 8085 TIME_WAIT TCP

Unknown 0 127.0.0.1 3645 127.0.0.1 443 TIME_WAIT TCP

vpxd.exe 1808 10.110.97.19 3633 10.110.97.38 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3631 10.110.97.38 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3628 10.110.97.38 443 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

Unknown 0 127.0.0.1 3625 127.0.0.1 8085 TIME_WAIT TCP

Unknown 0 127.0.0.1 3623 127.0.0.1 443 TIME_WAIT TCP

vpxd.exe 1808 127.0.0.1 3608 127.0.0.1 8085 FIN_WAIT2 TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

Unknown 0 127.0.0.1 3607 127.0.0.1 443 TIME_WAIT TCP

VpxClient.exe 3584 127.0.0.1 3606 127.0.0.1 443 ESTABLISHED TCP C:\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe

System 4 10.110.97.19 3601 10.110.92.24 445 ESTABLISHED TCP

vpxd.exe 1808 127.0.0.1 3598 127.0.0.1 8085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vmware-converter.exe 3324 10.110.97.19 3597 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\Converter Enterprise\vmware-converter.exe

vpxd.exe 1808 127.0.0.1 3596 127.0.0.1 8085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vmware-converter.exe 3324 10.110.97.19 3595 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\Converter Enterprise\vmware-converter.exe

vpxd.exe 1808 127.0.0.1 3589 127.0.0.1 8085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

java.exe 2756 127.0.0.1 3588 127.0.0.1 3587 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\jre-1.5.0-12\bin\java.exe

java.exe 2756 127.0.0.1 3587 127.0.0.1 3588 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\jre-1.5.0-12\bin\java.exe

vmware-updatemgr.exe 2788 10.110.97.19 3586 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

java.exe 2756 127.0.0.1 3585 127.0.0.1 3584 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\jre-1.5.0-12\bin\java.exe

java.exe 2756 127.0.0.1 3584 127.0.0.1 3585 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\jre-1.5.0-12\bin\java.exe

vpxd.exe 1808 127.0.0.1 3583 127.0.0.1 8085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vmware-updatemgr.exe 2788 10.110.97.19 3582 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vpxd.exe 1808 127.0.0.1 3581 127.0.0.1 8085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vmware-updatemgr.exe 2788 10.110.97.19 3580 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vpxd.exe 1808 127.0.0.1 3577 127.0.0.1 8085 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vmware-updatemgr.exe 2788 10.110.97.19 3576 10.110.97.19 443 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3575 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3574 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3573 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3572 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3571 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3570 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3569 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3568 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3567 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3566 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3565 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3564 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3563 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3562 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3561 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3560 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3559 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3558 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3557 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vmware-updatemgr.exe 2788 10.110.97.19 3556 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\Update Manager\vmware-updatemgr.exe

vpxd.exe 1808 10.110.97.19 3549 10.110.97.19 27010 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3546 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3545 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3544 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3543 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3542 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3541 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3540 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3539 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3538 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3537 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

vpxd.exe 1808 10.110.97.19 3536 10.110.104.111 1433 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

VMWARELM.exe 3720 127.0.0.1 3533 127.0.0.1 27000 ESTABLISHED TCP C:\Program Files\VMware\VMware License Server\VMWARELM.exe

VMWARELM.exe 3720 127.0.0.1 3532 127.0.0.1 3531 ESTABLISHED TCP C:\Program Files\VMware\VMware License Server\VMWARELM.exe

VMWARELM.exe 3720 127.0.0.1 3531 127.0.0.1 3532 ESTABLISHED TCP C:\Program Files\VMware\VMware License Server\VMWARELM.exe

System 4 10.110.97.19 3502 10.110.49.28 445 ESTABLISHED TCP

winlogon.exe 2000 127.0.0.1 3496 LISTEN UDP \??\C:\WINDOWS\system32\winlogon.exe

svchost.exe 1376 10.110.97.19 3389 10.110.97.99 3535 ESTABLISHED TCP C:\WINDOWS\System32\svchost.exe

winlogon.exe 360 127.0.0.1 1130 LISTEN UDP \??\C:\WINDOWS\system32\winlogon.exe

lsass.exe 420 127.0.0.1 1028 LISTEN UDP C:\WINDOWS\system32\lsass.exe

svchost.exe 796 127.0.0.1 1026 LISTEN UDP C:\WINDOWS\system32\svchost.exe

lsass.exe 420 0.0.0.0 1025 LISTEN TCP C:\WINDOWS\system32\lsass.exe

vpxd.exe 1808 0.0.0.0 902 LISTEN UDP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

rdevServer.exe 2804 0.0.0.0 735 LISTEN TCP C:\VMware\Infrastructure\Update Manager\rdevServer.exe

lsass.exe 420 0.0.0.0 500 LISTEN UDP C:\WINDOWS\system32\lsass.exe

System 4 0.0.0.0 445 LISTEN UDP

System 4 0.0.0.0 445 LISTEN TCP

vpxd.exe 1808 127.0.0.1 443 127.0.0.1 3705 ESTABLISHED TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

svchost.exe 692 0.0.0.0 135 LISTEN TCP C:\WINDOWS\system32\svchost.exe

svchost.exe 796 127.0.0.1 123 LISTEN UDP C:\WINDOWS\system32\svchost.exe

vpxd.exe 1808 0.0.0.0 80 LISTEN TCP C:\VMware\Infrastructure\VirtualCenter Server\vpxd.exe

Hang 2 LEDs in the datacenter. The students are coming! The students are coming!
0 Kudos
dm330
Contributor
Contributor

try this one on the Cisco PIX firewall via ASDM GUI

Go to

Configuration --> TCP Options --> Disable "Force maximum segment size for TCP proxy connection" so it is "0" unlimited (default is 1380 bytes)

The default TCP segment size is to small for vmware actions because I see sizes like 2000 -> 9000 which is way higher!

Via the cmdline it is:

#sysopt connection tcpmss 0

#wr mem

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
vmwareadm
Contributor
Contributor

I just discovered exactly the same probleme here, using VC 2.5 Update 4 and updating an ESX host from 3.0.2 to 3.0.3. Disconnects after 1-2 minutes. No network problem, even the heartbeat is okay (vpxa.log). Ping does not help, remove/add host does not help. Other ESX hosts with 3.5 work fine. I opened a service request. Lets wait and see...

0 Kudos
dm330
Contributor
Contributor

If you have a firewall between virtualcenter and the esx servers you could have the same timeout problems.

my case nr is:SR1157650401

I am at VC2.5U4 now and got a fix from vmware which only aplies to this specific problem and version.

you can get the fix only from vmware and when aplied you can set "vpxd.httpClientIdleTimeout value" 600s

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
vmwareadm
Contributor
Contributor

Yes, VMware Support delivers a patch that will also be included in Update 5 for the VC Server. It worked for us in one case, in another case there was a routing problem with esx servers in a different net (the problem appeared after the update since the communication has changed since VC 2.5 and esx 3.0.3, it worked perfectly before). It works now for us.

regards

Tilman

0 Kudos
erwanaliasr1
Contributor
Contributor

Does anyone knows where this parameter must be set ? (vpxd.httpClientIdleTimeout)

0 Kudos
dm330
Contributor
Contributor

That's great to hear i knew they where going to put the fix we have in vc 2.5 update 5

we are going to upgrade to update 5 soon.

tnx for the info

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
vmwareadm
Contributor
Contributor

This is part of the readme file from the patch for VC update 4 that we tested:

"The default timeout is 15 minutes (900 seconds). To change this through the VI Client click:

Administration --> VirtualCenter Management Server Configuration --> Advanced Settings --> Add Row.

Key name: vpxd.httpClientIdleTimeout

Value: number of seconds

This new value will be immediately in effect. The services do not need to be restarted. This value is stored in database and will be maintained during upgrades.

The value will not be shown here in the VI Client after entering it as this requires a new version of the VI Client which has not been released yet."

But since the issue should be fixed in update 5, maybe it is not necessary to set this value - i have not yet tested.

regards

Tilman

ssingla
Contributor
Contributor

Hello

I had been having exactly the same problem. Tried all possible solutions. But none of them fixed the issue. Finally the one that has worked is Vc 2.5 update 5. It works all ok now from the last 2-3 days since VC was updated.

Virtualization6
Contributor
Contributor

Hello SSingla,

Did you udate VC to U5 or Did this setting worked with with your current update, I have U3 version and want to know if the vpxd.httpClientIdleTimeout setting work on VC 2.5 U3 ?

Regards

0 Kudos
ssingla
Contributor
Contributor

Hi

I was running VC 2.5 u4 before when the problem started. I tried editing this vpxd.httpClientIdleTimeout setting but it did not fix the issue. But applying Update 5 fixed the issue. It has been working ok since then.

0 Kudos