2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
→ESXi: Reworded slightly
(→Storage: Added "ESX Installation Sizing") |
(→ESXi: Reworded slightly) |
||
| Line 633: | Line 633: | ||
=== ESXi === | === ESXi === | ||
To view logfiles from an ESX'''i''' server, they need to be downloaded to your client machine 1st, and then viewed from there... | To view logfiles from an ESX'''i''' server, assuming you don't have SSH access, they need to be downloaded to your client machine 1st, and then viewed from there... | ||
# Using VI Client, go to '''File | Export | Export System Logs...''' | # Using VI Client, go to '''File | Export | Export System Logs...''' | ||
#* Tick the appropriate object | #* Tick the appropriate object | ||
| Line 653: | Line 653: | ||
'''Logfiles get lost at restart !''' If you have to restart your ESX (say, because it locked up) there will be no logs prior to the most recent boot. In theory they'll get written to a dump file if a crash is detected, but I've never found them, so assume they're only generated during a semi-graceful software crash. | '''Logfiles get lost at restart !''' If you have to restart your ESX (say, because it locked up) there will be no logs prior to the most recent boot. In theory they'll get written to a dump file if a crash is detected, but I've never found them, so assume they're only generated during a semi-graceful software crash. | ||
However, there is a way around this. Message's can be sent to a syslog file (say on centrally available SAN LUN), a syslog server (in both cases see http://kb.vmware.com/ | However, there is a way around this. Message's can be sent to a syslog file (say on centrally available SAN LUN), a syslog server (in both cases see [http://kb.vmware.com/kb/1016621 VM KB 1016621]), or to a vMA server (see http://www.vmware.com/support/developer/vima/vima40/doc/vma_40_guide.pdf). | ||
=== ESXi Tech Support Mode === | === ESXi Tech Support Mode === | ||