Solved

Connectivity lost to Virtual Center

Posted on 2008-10-24
3
852 Views
Last Modified: 2012-05-05
Out of the blue today we experienced a point when one of four production ESX Servers went a-wall and was unreachable in the Virtual Infrastructure Client. Once we logged off and back on the connection re-established but that was an intermittent issue which might be related to network issue. Not sure exactly where to start but would like some guidance.
0
Comment
Question by:bmonroe44
  • 2
3 Comments
 
LVL 42

Assisted Solution

by:paulsolov
paulsolov earned 500 total points
ID: 22801022
Check the alerts, what error does it give you if any?  Make sure you're connected to Virtual Center via FQDN.

You may also want to make sure taht you have at least two Physical network ports connected to the vswitch where the console is located.  If you have multiple vswitches you can setup an additional console just in case.  

Is your console on the same subnet/vlan as your production network or is it on the same one?  
0
 
LVL 4

Author Comment

by:bmonroe44
ID: 22813964
The errors state that it failed to connect and reconnect to the host. After about 30 minutes we were finally able to re-estabilsh a connection. We only use the FQDN when adding a host and when accessing the VC server. Each server is using 5 physical ports. 2 Console (seperate subnets) and 2 VMkernel ports.  One console is on the same VLAN as the IT department for management purposes and the other is on the production network.
0
 
LVL 4

Accepted Solution

by:
bmonroe44 earned 0 total points
ID: 22851917
Looks like I can contribute the issue to the gateway being set differently on that host.
0

Featured Post

Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

792 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question