ESXi 4.1 not connecting using VC o VI

[kopper27]

hi guys

I don't know why one of my ESXi 4.1 update 1 just appeared disconnected I tried to reconnect it  back (didn't work) so I removed it and now there is no way to add it back to the cluster.

I cannot even connect directly to the ESXi using VI Client (a connection failure occurred message)

I've restarted the Management agents from DCUI - same thing

Server was restarted - same thing

I started thinking about firewall issues but ESXi looks like does not have Firewall.

but there are two nodes cluster Management network is 10.1.26.x the second node is working fine (just to test I've removed it and added it back to the cluster) but I found that a telnet to Node01 is not working to some ports like the ones below:

node01 = 10.1.26.21 - ssh = OK - 443 = not OK - 80= not OK

node02 = 10.1.26.22 - ssh = OK - 443 = OK - 80= OK

any reason why these ports are down?

how can I fix this?

adding screens when trying to add node01 to and messages log

Logs

Apr 27 19:23:41 vmkernel: 0:01:20:07.274 cpu4:4100)LinNet: map_skb_to_pkt: This message has repeated 325632 times: invalid vlan tag: 4095 dropped
Apr 27 19:23:51 Vpxa: [2011-04-27 19:23:51.471 113C9B90 verbose 'App'] [VpxaHalCnxHostagent] Creating temporary connect spec: localhost:443
Apr 27 19:23:51 Vpxa: [2011-04-27 19:23:51.471 113C9B90 error 'App'] [HttpUtil::ExecuteRequest] Error in sending request - Connection refused
Apr 27 19:23:51 Vpxa: [2011-04-27 19:23:51.471 113C9B90 error 'App'] [VpxaHalCnxHostagent] Failed to discover version: vim.fault.HttpFault
Apr 27 19:23:51 Vpxa: [2011-04-27 19:23:51.471 113C9B90 warning 'App'] [VpxaHalCnxHostagent] Could not resolve version for authenticating to host agent
Apr 27 19:23:58 vmkernel: 0:01:20:23.427 cpu4:4100)LinNet: map_skb_to_pkt: This message has repeated 326656 times: invalid vlan tag: 4095 dropped
Apr 27 19:24:11 Vpxa: [2011-04-27 19:24:11.472 11694B90 verbose 'App'] [VpxaHalCnxHostagent] Creating temporary connect spec: localhost:443
Apr 27 19:24:11 Vpxa: [2011-04-27 19:24:11.473 11694B90 error 'App'] [HttpUtil::ExecuteRequest] Error in sending request - Connection refused
Apr 27 19:24:11 Vpxa: [2011-04-27 19:24:11.473 11694B90 error 'App'] [VpxaHalCnxHostagent] Failed to discover version: vim.fault.HttpFault
Apr 27 19:24:11 Vpxa: [2011-04-27 19:24:11.473 11694B90 warning 'App'] [VpxaHalCnxHostagent] Could not resolve version for authenticating to host agent
Apr 27 19:24:14 vmkernel: 0:01:20:40.054 cpu4:4100)LinNet: map_skb_to_pkt: This message has repeated 327680 times: invalid vlan tag: 4095 dropped
Apr 27 19:24:19 Vpxa: [2011-04-27 19:24:19.021 11694B90 verbose 'App'] [VpxaAAM::PollForVMAPCommands] Running ftExecute

[MauroBonder]

check if help http://www.yellow-bricks.com/2010/07/13/vsphere-4-1-datacenter-queryconnectioninfo-failed/

check ports that vcenter use http://kb.vmware.com/kb/1012382

[kopper27]

yes like I said.....

these are two ESXi servers one is connected I already removed it and added it back so no name resolution problems just to be sure I tried IP to add the server to the virtual center and also there is no way to connect to the ESXi server using the VI client.....

my question would how one server is workig fine and the other is not if it were firewall in my network the other server would have the same issues but second node is fine

any firewall or something to check on this specific ESXi that is not working

I mentioned 443 and 80 are closed I cannot telnet them on node01 and node02 is fine

thanks

[kopper27]

the only way to fixed it was to select on DCUI the option "Reset System Configuration" and apply my host profile up and running again.

[kopper27]

I read that in what you posted but like I said IP was the same thing. VI client could not be used.

when using IP in browser like IE not display about ESXi

it was like port 80 and 443 were not responding

[MauroBonder]

you tried disable firewall of vcenter to test ?

check FQND in DNS. And check if have any firewall in your network that can blocked any traffic between VI client and vcenter.

and check if service of vcenter is UP