ESXi 5.5 How To export the log bundle to a shared vmfs datastore?

[sicnarf_latosa]

Hi Guys,

any idea how can I export log bundle to a shared vmfs datastore? I'm using SSH "/usr/bin/vm-support" because one of our ESXi 5.5 after the upgrade it is not reachable on our network.

Note: The -f option is not available in ESXi 5.x, ESXi/ESX 4.1 Update 3, and later.

Command: vm-support -f -w /vmfs/volumes/DATASTORE_NAME

[scott28tt]

Moderator note: Technical questions about a product should be asked in the relevant product forum area - moving from the VCP area to the ESXi 5 area.

[UmeshAhuja]

To which version you have upgraded....  5.5 or 6.0

[UmeshAhuja]

Hi,

Also try to login into the ESXi Datastores inventory browser and save the target if possible..

[grasshopper]

Hi sicnarf_latosa,

Since you have no upstream networking, I am unsure how you expect to reach the shared VMFS datastores from that host.  However, if you feel this is what you want, you can use the streaming feature of vm-support with the -s switch.

vm-support streaming example:

vm-support -s > /vmfs/volumes/big-vol-01/vm-support-host3.tgz

Honestly though, since this is the only host that did not come back after the upgrade, I would consider some local troubleshooting on the host as well.  Some things you may consider are restarting the management agents or reverting to the previous install by using SHIFT + R at boot time.

If all else fails and you absolutely must have logs, you can always use the Alt +F12 vmkernel log viewer at the direct console (easy) or serial line logging (difficult).  As a final option you can always connect directly to the host via crossover (or on the same L2 VLAN if the problem is only L3 upstream) and then use the vSphere Client or gather vm-support via HTTP.

Just some ideas. Please keep us posted on your success.  Supporting links below.

Reverting to a previous version of ESXi (1033604)

http://kb.vmware.com/kb/1033604

Collecting diagnostic information using the vm-support command in VMware ESX/ESXi (1010705)

http://kb.vmware.com/kb/1010705

Using PuTTY to capture serial-line logs from ESX/ESXi hosts (1033843)

http://kb.vmware.com/kb/1033843

Restarting the Management agents on an ESXi or ESX host (1003490)

http://kb.vmware.com/kb/1003490

[sicnarf_latosa]

Hi grasshopper and Umesh,

My ESXi host version is 5.5 U2 and I upgraded it to U3.

- If we rollback to previous version all works fine

- I already rebooted the host all services already restarted but faced the same issue, one thing I never check the logs. later I will enable the tech support console and check everything I cannot do anything to export the logs as my ESXi host destination unreachable to the network.

Later I will update you guys regarding the status  

[UmeshAhuja]

Hi,

What is your vCenter version.... Have you updated vCenter Server first to 5.5 Update 3B ? If Not then You need to update to latest vCenter Server 5.5 Update 3b version and then update to ESXi 5.5 Update 3b. If we don’t update to vCenter Server 5.5 Update 3b, then we need to enable SSLv3 on ESXi for all services. Enabling SSLv3 on ESXi will cause POODLE vulnerability which is not recommended from security point-of-view.

HOLD ON with patch ESXi 5.5 Update 3B as it requires vCenter Server 5.5 Update 3b first.......

[sicnarf_latosa]

Hi Umesh,

VC upgraded first it is same U3a  actually out of 27 host upgraded to U3a using VUM two having the same issue after the upgrade ping test to host ip destination unreachable if we rollback to the old version issue not happening anymore. My boss requested U3a only

[sicnarf_latosa]

Tnx Buddy grasshopper below command you recommend working like a charm

vm-support streaming example:

vm-support -s > /vmfs/volumes/big-vol-01/vm-support-host3.tgz

[grasshopper]

Excellent!