2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
→ESXi: Added "ESXi Tech Support Mode"
(→Procedures: Added KB1026380 link) |
(→ESXi: Added "ESXi Tech Support Mode") |
||
| Line 591: | Line 591: | ||
#* Untick ''Include information from vCenter Server and vSphere Client'', unless you additionally want this info | #* Untick ''Include information from vCenter Server and vSphere Client'', unless you additionally want this info | ||
# Once exported, uncompress the ESX's tgz file | # Once exported, uncompress the ESX's tgz file | ||
However, this is most easily achieved if you've got the PowerCLI installed, in which case see [[VI_Toolkit_(PowerShell)#ESXi_Logs]] | However, this is most easily achieved if you've got the PowerCLI installed, in which case see [[VI_Toolkit_(PowerShell)#ESXi_Logs|ESXi Logs via PowerCLI]] | ||
{|cellpadding="2" cellspacing="0" border="1" | {|cellpadding="2" cellspacing="0" border="1" | ||
| Line 607: | Line 607: | ||
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/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1016621), or to a vMA server (see http://www.vmware.com/support/developer/vima/vima40/doc/vma_40_guide.pdf). | 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/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1016621), or to a vMA server (see http://www.vmware.com/support/developer/vima/vima40/doc/vma_40_guide.pdf). | ||
=== ESXi Tech Support Mode === | |||
There's no Service Console on ESXi, so you have to do without. Well almost, there is the ''unsupported'' Tech Support Mode, which is a lightweight Service Console, to enable... | |||
'''ESXi 3.5 and 4.0''' | |||
# Go to the local ESXi console and press Alt+F1 | |||
# Type '''unsupported''' | |||
# Blindly type the root password (yes, there's no prompt) | |||
# Edit <code> /etc/inetd.conf </code> and uncomment (remove the #) from the line that starts with <code> #ssh </code>, and save | |||
# Restart the management service <code> /sbin/services.sh restart </code> | |||
'''ESXi 4.1''' | |||
# Go to the local ESXi console and press F2 | |||
# Enter root user and pass | |||
# Go to the '''Troubleshooting Options''' | |||
# Enable '''Local Tech Support''' or '''Remote Tech Support (SSH)''' as required | |||
Alternatively... | |||
# From the vSphere Client, select the host and click the '''Configuration''' tab | |||
# Go to '''Security profile > Properties''' | |||
# Select '''Local Tech Support''' or '''Remote Tech Support (SSH)''' and click '''Options''' | |||
# Choose the startup policy, click '''Start''', and then '''OK'''. | |||
== CPU == | == CPU == | ||