Unable to reach Vmware Vcentre server (version 5.5)
hi guys
We've got problems connecting from our PC's to the Vcentre server that is on our own local LAN. The version of Vmware we are running is 5.5 which we upgraded around a year ago. Ever since, we have had a lot of performance issues on it. So the Vcentre itself sits on a physical IBM X3550 M3 server with around 8GB of ram. We can't even ping it. RDP'ing is just now impossible. However, once we restart the server manually, we can RDP and then after like 10mins, our session times out.
We were told that Vmware 5.5 and above should really be virtual and therefore sitting on the physical entity could well be causing problems. We can connect without any issues to the servers within the virtual infrastructure.
Is there a diagnosis for this? Is it a bug?
Thanks for helping
Yash
We've got problems connecting from our PC's to the Vcentre server that is on our own local LAN. The version of Vmware we are running is 5.5 which we upgraded around a year ago. Ever since, we have had a lot of performance issues on it. So the Vcentre itself sits on a physical IBM X3550 M3 server with around 8GB of ram. We can't even ping it. RDP'ing is just now impossible. However, once we restart the server manually, we can RDP and then after like 10mins, our session times out.
We were told that Vmware 5.5 and above should really be virtual and therefore sitting on the physical entity could well be causing problems. We can connect without any issues to the servers within the virtual infrastructure.
Is there a diagnosis for this? Is it a bug?
Thanks for helping
Yash
ASKER
There are x4 hosts on there. Each one is running around 6 VM's.
Memory on the Vcenter server is 16gb. I made an error previously.
One of my team members has connected a screen to the Vcenter. They logged in locally. When things are going wrong, they are unable to ping the local gateway but for example can ping the DNS server.
Details:
Physical Vcenter Server: 172.25.241.100
Subnet Mask: 255.255.248.0
Gateway: 172.25.240.1
DNS server: 172.25.241.106
The Gateway above is on a VLAN on one of our Cisco switches. Very strange behaviour.
Memory on the Vcenter server is 16gb. I made an error previously.
One of my team members has connected a screen to the Vcenter. They logged in locally. When things are going wrong, they are unable to ping the local gateway but for example can ping the DNS server.
Details:
Physical Vcenter Server: 172.25.241.100
Subnet Mask: 255.255.248.0
Gateway: 172.25.240.1
DNS server: 172.25.241.106
The Gateway above is on a VLAN on one of our Cisco switches. Very strange behaviour.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We haven't tried the last thing you wrote. We'll try that too. But like I mentioned above, it's strange that when this happens and we access it locally, it can't ping the default gateway.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've been away so helping the engineers out remotely. I'm waiting to hear back from them.
ASKER
I couldn't answer this any longer due to engineers not coming back to me. Apologies for closing without an answer.
that's foo. virtual or physical will do.
How many hosts and VMs ?
8GB might be too small.