<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Need help in interpreting the error log in ESXi 5.1u1 host in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371749#M21661</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vcli.examples.doc%2Fcli_advanced_storage.8.3.html" title="http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vcli.examples.doc%2Fcli_advanced_storage.8.3.html"&gt;VMware vSphere 5.1&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It is a two step process. First, unclaim the device by any, then reclaim the device by the PSA &lt;SPAN style="font-family: 'courier new', courier;"&gt;VMW_VAAIP_CX. The above link is useful&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Sep 2013 07:54:26 GMT</pubDate>
    <dc:creator>zXi_Gamer</dc:creator>
    <dc:date>2013-09-16T07:54:26Z</dc:date>
    <item>
      <title>Need help in interpreting the error log in ESXi 5.1u1 host</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371745#M21657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need your assistance in interpreting the following ESXi 5.1 Update 1 error log:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;2013-09-13T00:16:36.301Z cpu0:8705)WARNING: NMP: nmpCompleteRetryForPath:378:Logical device "naa.60060160e7311b006887b1bf34a7df11": awaiting fast path state update before retrying failed command again...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2013-09-13T00:16:36.632Z cpu4:8335)ScsiDeviceIO: 2331: Cmd(0x4124403c1d40) 0x12, CmdSN 0x458c3 from world 0 to dev "naa.60060160e7311b006887b1bf34a7df11" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x5 0x24 0x0.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;2013-09-13T00:16:36.632Z cpu4:8335)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.60060160e7311b006887b1bf34a7df11" is blocked. Not starting I/O from device.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;2013-09-13T00:16:36.632Z cpu5:8313)WARNING: VMW_VAAIP_CX: cx_claim_device:113:Inquiry to device naa.60060160e7311b006887b1bf34a7df11 failed&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;2013-09-13T00:16:36.634Z cpu5:8313)WARNING: NMP: nmp_SelectPathAndIssueCommand:2694:PSP selected path "vmhba1:C0:T0:L4" in a bad state (standby) on device "naa.60060160e7311b00c4fe11f33544df11".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2013-09-13T00:16:36.634Z cpu5:8313)NMP: nmp_ThrottleLogForDevice:2319: Cmd 0x12 (0x4124403c1d40, 0) to dev "naa.60060160e7311b00c4fe11f33544df11" on path "vmhba1:C0:T0:L4" Failed: H:0x1 D:0x0 P:0x0 Possible sense data: 0x5 0x24 0x0. Act:FAILOVER&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;2013-09-13T00:16:36.634Z cpu5:8313)WARNING: NMP: nmp_DeviceRetryCommand:133:Device "naa.60060160e7311b00c4fe11f33544df11": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;2013-09-13T00:16:36.634Z cpu5:8313)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device "naa.60060160e7311b00c4fe11f33544df11" is blocked. Not starting I/O from device.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2013-09-13T00:16:37.301Z cpu3:8704)WARNING: NMP: nmpDeviceAttemptFailover:562:Retry world restore device "naa.60060160e7311b006887b1bf34a7df11" - no more commands to retry&lt;/P&gt;&lt;P&gt;2013-09-13T00:16:37.428Z cpu0:8705)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.60060160e7311b00c4fe11f33544df11" - issuing command 0x4124403c1d40&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;2013-09-13T00:16:37.428Z cpu0:8705)WARNING: NMP: nmp_SelectPathAndIssueCommand:2694:PSP selected path "vmhba1:C0:T0:L4" in a bad state (standby) on device "naa.60060160e7311b00c4fe11f33544df11".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2013-09-13T00:16:37.428Z cpu0:8705)WARNING: NMP: nmpCompleteRetryForPath:348:Retry cmd 0x12 (0x4124403c1d40) to dev "naa.60060160e7311b00c4fe11f33544df11" failed on path "vmhba1:C0:T0:L4" H:0x1 D:0x0 P:0x0 Possible sense data: 0x5 0x24 0x0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2013-09-13T00:16:37.428Z cpu0:8705)WARNING: NMP: nmpCompleteRetryForPath:378:Logical device "naa.60060160e7311b00c4fe11f33544df11": awaiting fast path state update before retrying failed command again...&lt;/P&gt;&lt;P&gt;2013-09-13T00:16:38.336Z cpu3:8704)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.60060160e7311b00c4fe11f33544df11" - issuing command 0x4124403c1d40&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;2013-09-13T00:16:38.336Z cpu3:8704)WARNING: NMP: nmp_SelectPathAndIssueCommand:2694:PSP selected path "vmhba1:C0:T0:L4" in a bad state (standby) on device "naa.60060160e7311b00c4fe11f33544df11".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;2013-09-13T00:16:38.336Z cpu3:8704)WARNING: NMP: nmpCompleteRetryForPath&lt;/SPAN&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;:348:Retry cmd&lt;/SPAN&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt; 0x12 (0x4124403c1d40) to dev "naa.60060160e7311b00c4fe11f33544df11" failed on path "vmhba1:C0:T0:L4" H:0x1 D:0x0 P:0x0 Possible sense data: 0x5 0x24 0x0.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it is repeated millions of times in the newly upgraded ESXi host with missing LUN, what could be the issue with the FC SAN storage array ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is happening after I have successfully upgraded the ESX host from 4.1 into ESXi 5.1 Update 1 by using the ISO and then forced the migration with Preserve the VMFS volume.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Sep 2013 00:54:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371745#M21657</guid>
      <dc:creator>AlbertWT</dc:creator>
      <dc:date>2013-09-13T00:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: Need help in interpreting the error log in ESXi 5.1u1 host</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371746#M21658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looks like the path to the storage that the host is using is down or offline and its trying to failover to another path. &lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;2013-09-13T00:16:37.428Z cpu0:8705)WARNING: NMP: nmpCompleteRetryForPath:348:Retry cmd 0x12 (0x4124403c1d40) to dev "naa.60060160e7311b00c4fe11f33544df11" failed on path "vmhba1:C0:T0:L4" &lt;STRONG&gt;H:0x1&lt;/STRONG&gt; D:0x0 P:0x0 Possible sense data: 0x5 0x24 0x0.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;H:0x1 represents &lt;STRONG&gt;No connect.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;It is ti with failover multipathing sequence. check out this &lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1027963"&gt;KB article&lt;/A&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Sep 2013 02:57:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371746#M21658</guid>
      <dc:creator>abhilashhb</dc:creator>
      <dc:date>2013-09-13T02:57:00Z</dc:date>
    </item>
    <item>
      <title>Re: Need help in interpreting the error log in ESXi 5.1u1 host</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371747#M21659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looks like a lot of fight is going on who has taken the ownership of the device between &lt;SPAN style="font-family: 'courier new', courier;"&gt;VMW_VAAIP_CX and NMP.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;If you are using any VAAIP, unclaim the device from NMP from esxcli storage claiming&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Sep 2013 09:13:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371747#M21659</guid>
      <dc:creator>zXi_Gamer</dc:creator>
      <dc:date>2013-09-13T09:13:34Z</dc:date>
    </item>
    <item>
      <title>Re: Need help in interpreting the error log in ESXi 5.1u1 host</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371748#M21660</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the suggestion man, how can I do that ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Disclaimer: This email was sent from my iPhone, apologize for any typographical error.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Sep 2013 09:50:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371748#M21660</guid>
      <dc:creator>AlbertWT</dc:creator>
      <dc:date>2013-09-13T09:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: Need help in interpreting the error log in ESXi 5.1u1 host</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371749#M21661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vcli.examples.doc%2Fcli_advanced_storage.8.3.html" title="http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vcli.examples.doc%2Fcli_advanced_storage.8.3.html"&gt;VMware vSphere 5.1&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It is a two step process. First, unclaim the device by any, then reclaim the device by the PSA &lt;SPAN style="font-family: 'courier new', courier;"&gt;VMW_VAAIP_CX. The above link is useful&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Sep 2013 07:54:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371749#M21661</guid>
      <dc:creator>zXi_Gamer</dc:creator>
      <dc:date>2013-09-16T07:54:26Z</dc:date>
    </item>
    <item>
      <title>Re: Need help in interpreting the error log in ESXi 5.1u1 host</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371750#M21662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many thanks people for the clarification, based on this article: &lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2004684" title="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2004684"&gt;VMware KB: Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.0/5.1 &lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no explanation for the error sensing code: &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;Possible sense data: 0x5 &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;0x24&lt;/STRONG&gt;&lt;/SPAN&gt; 0x0&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Sep 2013 08:25:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371750#M21662</guid>
      <dc:creator>AlbertWT</dc:creator>
      <dc:date>2013-09-16T08:25:14Z</dc:date>
    </item>
    <item>
      <title>Re: Need help in interpreting the error log in ESXi 5.1u1 host</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371751#M21663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;&lt;CODE&gt;04/02 DTLPWROMAEBKVF LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED&lt;/CODE&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=289902" title="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=289902"&gt;VMware KB: Interpreting SCSI sense codes in VMware ESXi / ESX &lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Sep 2013 08:39:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Need-help-in-interpreting-the-error-log-in-ESXi-5-1u1-host/m-p/371751#M21663</guid>
      <dc:creator>zXi_Gamer</dc:creator>
      <dc:date>2013-09-16T08:39:24Z</dc:date>
    </item>
  </channel>
</rss>

