ESXi 6.0 host locked up

All the logs will be in /var/log

the problem is, depending upon how you have installed ESXi, is whether those logs have been reset, when you restarted the host, and it's recommended

1. to specify a remote location to store the logs.
2. specify and configure a syslog server to send all the logs to.

the host is not oversubscribed, this is to mean all the host memory has not been allocated to VMs...

were none of the VMs responsive or running ?

Is the host patched to 6.0.0B?

Is this a new host?

Have you tested the hardware ?

I've redirected the logs to a LUN, but didn't know if there was a specific one or quick way to view.

Host has been up and running for about a year.  ESXi 6.0.0, 2809209

Not even half memory is used.

Now getting this "vmrc console has disconnected attempting to reconnect" on vCenter VM, which was one VM I couldn't access.

How many hosts do you have?
Did you try to move this VM to other host, see if its works?

ESXi 6.0, was only released in March 2015!

You are on 6.0.0b, released in July 2015.

you need to check and inspect all the logs, but the main log is \var\vmkernel.log

do you have shared storage ?

Luis: my vCenter VM is the one I can't get into.  :-(

Andrew: there is a dedicated LUN for the logs.

I can't even power off the VM, DANG!!   vim-cmd vmsvc/power.off 11

check the /var/logs and vmkernel.log

and check there are no loss of paths, if iSCSI, which could cause the hang!

wow, this is not good. I can't even force reboot the host.

Which log?

Can't view anything in configuration. hangs

check the /var/logs and vmkernel.log

configure a syslog server.

how do I view them?

vi or download them and use notepad++

Never viewed this, can you make any of this out?
vmkernel.log

That's my vCenter LUN. I see it but don't see errors on SAN or ESX side.

something is not happy with that LUN.

do you have multi paths...

"do you have multi paths?"  meaning to the SAN?  Yes, and they are all up.

That scared me! Finally got back into vCenter VM. Not sure what's going on but have to investigate the SAN for potential problems.

But as far as the Host failing, is there something I need to look for along with this other problem and how do I locate particulars in the logs?

What is fip? The SAN is fiber channel.
fip: host14: FIP VLAN ID unavail. Retry VLAN discovery.
2015-09-10T18:27:17.275Z cpu15:33252)<6>host14: fip: fcoe_ctlr_vlan_request() is done

Fibre Channel over Ether discovery.

This acronym would have made more since..fcoe. Anyway, sorry for the delay, it was the FC controller that failed.

Thanks again

Regards