I have one host that refuses to allow me to add it to my data center. It acts like it is going to work when I add it then just fails with no details at all in the logs.
The only difference I really see from other hosts is the VirtualCenter Agent is stopped and won't start. NTP is stopped and won't start as well.
Not really sure of the order of dependency but it seems this may be the reason it fails?
Any help greatly appreciated
I think maybe it is a DNS issue. I can't ping my License / Virtual server by name from this host either. Other hosts also seem fine in this regard as well.
Just to post up some resolution on this one....
Part DNS - The DNS server was not properly handing out recently added host enties. (temp resolution was to change to a different DNS server)
Part Port 902 - This port has to be routed on both sides of the connection, we only had it properly routing in one direction invlolving the Ip addresses of the host and the VC server..
Well maybe not out of the woods yet.
This one host keeps disconnecting / unresponsive now on the foundation / vcenter console.
I can always disconnect and recconect. So not the worse thing. Once again other hosts are stable, same config.
What is the make and model of Server ?
Color of USB Attached ?
The Vcenter server is a Server I built. Not virtualized.
The host is a Dell 2950III, not sure what color the USB drive is that contains the esxi on the host in question. Not sure I can easily find out either.
My VMware specialist states he made a change to one of the config files on each host that enabled the other hosts to work properly.
He also said there is a fair amount of work to get putty working on new hosts so the change can be made?
I have that working to all my other hosts as I suppose he set it up upon initial installation months ago.
Is there a good doccument that describes the steps needed to get putty up and running so I can get to my esxi command line stuff on new hosts I add in the future?
Login to server using ILO access to console
1.) While you are at the console hit *ALT +
F1*
2.) Type in ” unsupported ” and
hit Enter
3.) Go ahead and type the root password
4.) Go and edit the /etc/inetd.conf
file
5.) Uncoment the line where you can see “#ssh” (line 32).
Remove the “#” mark at the begining.
6.) Type “ps -a |grep inetd”
7.) Kill the process
8.) start inetd
Enjoy ...
Still going crazy with the one host here.....
It disconnects 1-2 min after connection to Foundation / Vcenter...
We thought it still a port issue, but I made each side the DMZ zone and it still disconnects.
This has got to be something simple I am missing here.
Were you able to find a solution to your problem. My problem appears to be somewhat similar to what you're experiencing. http://communities.vmware.com/message/1316115#1316115
Dan