Difference between revisions of "Troubleshooting (ESX)"

Jump to navigation Jump to search
564 bytes removed ,  22:50, 21 February 2012
Update table style
(→‎Storage: Added "Recover lost SAN VMFS partition (ESX4)")
(Update table style)
Line 4: Line 4:
'''Timestamps in logfiles are in UTC !!!'''
'''Timestamps in logfiles are in UTC !!!'''
=== ESX ===
=== ESX ===
{|cellpadding="2" cellspacing="0" border="1"
{|class="vwikitable"
|- style="background-color:#bbddff;"
|-
! Item                  !!  Path                                      !!  Comments
! Item                  !!  Path                                      !!  Comments
|-
|-
Line 35: Line 35:
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]]
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"
{|class="vwikitable"
|- style="background-color:#bbddff;"
|-  
! Name          !!  PowerCLI Key            !!  Diagnostic Dump Path                        !!  Comments
! Name          !!  PowerCLI Key            !!  Diagnostic Dump Path                        !!  Comments
|-
|-
Line 77: Line 77:
== ESXTOP ==
== ESXTOP ==


{|cellpadding="2" cellspacing="0" border="1"
{|class="vwikitable"
|- style="background-color:#bbddff;"
|-  
! Key              !!  Change View  !!  Key              !!  Sort by                                 
! Key              !!  Change View  !!  Key              !!  Sort by                                 
|-
|-
Line 149: Line 149:
CPU Ready can creep up if the the system is pushed, or if the VM has multiple CPUs (as it needs multiple physical CPUs to become available at the same time, aka CPU Co-Scheduling).  Multiple CPU's are especially a problem in environments where there are large number of SMP VM's.
CPU Ready can creep up if the the system is pushed, or if the VM has multiple CPUs (as it needs multiple physical CPUs to become available at the same time, aka CPU Co-Scheduling).  Multiple CPU's are especially a problem in environments where there are large number of SMP VM's.


{|cellpadding="2" cellspacing="0" border="1"
{|class="vwikitable"
|- style="background-color:#bbddff;"
|-  
! % CPU Ready !! MSec CPU Ready !! Performance
! % CPU Ready !! MSec CPU Ready !! Performance
|-
|-
Line 174: Line 174:


Latency occurs when the hypervisor or physical storage cannot keep pace with the demand for IO, as a rough guide to indicate if theres a problem or not...
Latency occurs when the hypervisor or physical storage cannot keep pace with the demand for IO, as a rough guide to indicate if theres a problem or not...
{|cellpadding="2" cellspacing="0" border="1"
{|class="vwikitable"
|- style="background-color:#bbddff;"
|-
! Latency up to !! Status
! Latency up to !! Status
|-
|-
Line 195: Line 195:


The status message consists of the follow four decimal and hex blocks...
The status message consists of the follow four decimal and hex blocks...
{| cellpadding="4" cellspacing="0" border="1"
{| class="vwikitable"
|-  
|-  
|''Device Status'' / ''Host Status'' || ''Sense Key'' || ''Additional Sense Code'' || ''Additional Sense Code Qualifier''
|''Device Status'' / ''Host Status'' || ''Sense Key'' || ''Additional Sense Code'' || ''Additional Sense Code Qualifier''
Line 205: Line 205:
  Mar  2 10:04:44 vmkernel: 81:00:00:15.893 cpu8:4633964)StorageMonitor: 196: vmhba0:0:4:0 status = D:0x28/H:0x0 0x0 0x0 0x0
  Mar  2 10:04:44 vmkernel: 81:00:00:15.893 cpu8:4633964)StorageMonitor: 196: vmhba0:0:4:0 status = D:0x28/H:0x0 0x0 0x0 0x0


{| cellpadding="4" cellspacing="0" border="1"
{| class="vwikitable"
|-  
|-  
|<code>D:</code>''Device Status'' / <code>H:</code>''Host Status'' || ''Sense Key'' || ''Additional Sense Code'' || ''Additional Sense Code Qualifier''
|<code>D:</code>''Device Status'' / <code>H:</code>''Host Status'' || ''Sense Key'' || ''Additional Sense Code'' || ''Additional Sense Code Qualifier''
Line 211: Line 211:


Where the ESX Device and SAN host status' mean...
Where the ESX Device and SAN host status' mean...
{| cellpadding="4" cellspacing="0" border="1"
{| class="vwikitable"
|- style="background-color:#bbddff;"
|-  
! Decimal !! Device Status        !! Host Status      !! Comments
! Decimal !! Device Status        !! Host Status      !! Comments
|-
|-
Line 245: Line 245:


Where the Sense Key mean...
Where the Sense Key mean...
{| cellpadding="4" cellspacing="0" border="1"
{| class="vwikitable"
|- style="background-color:#bbddff;"
|-  
! Hex !! Sense Key
! Hex !! Sense Key
|-
|-
Line 279: Line 279:


The Additional Sense Code and Additional Sense Code Qualifier mean
The Additional Sense Code and Additional Sense Code Qualifier mean
{| cellpadding="4" cellspacing="0" border="1"
{| class="vwikitable"
|- style="background-color:#bbddff;"
|-
! Hex !! Sense Code
! Hex !! Sense Code
|-
|-
Line 474: Line 474:
The interface is a bit dodgy, you can enter the same command twice, and it'll be rejected one time and accepted another, patience is required.
The interface is a bit dodgy, you can enter the same command twice, and it'll be rejected one time and accepted another, patience is required.


{|cellpadding="4" cellspacing="0" border="1"
{|class="vwikitable"
|- style="background-color:#bbddff;"
|-  
! Command                                !! Comments
! Command                                !! Comments
|-
|-

Navigation menu