<?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: fcp show initiator still display a dead server's wwpn in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/fcp-show-initiator-still-display-a-dead-server-s-wwpn/m-p/17146#M1521</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;black,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yes, happens at our machines as well, seems it might stay there for a while if they dont properly do a fabric logout or so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But you can be sure if your service is shut down, then your LUN is save, regardless if the initiator is visible there or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check Bug &lt;STRONG&gt;75407&lt;/STRONG&gt; by NetApp:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"When a host initiator has been disconnected from the Fibre Channel fabric, the&lt;BR /&gt;filer's "fcp show initiator" command continues to show the initiator as logged&lt;BR /&gt;in, even though the switch shows the right status for the host.&amp;nbsp; This is due to&lt;BR /&gt;the nature of the fcp protocol.&amp;nbsp; When a host initiator first tries to &lt;BR /&gt;communicate with the filer, it must log in with the filer first.&amp;nbsp; This login&lt;BR /&gt;status is shown in "fcp show initiator".&amp;nbsp; In order for it to be removed from&lt;BR /&gt;the "fcp show initiator" list, it needs to be logged out.&amp;nbsp; Disconnecting a&lt;BR /&gt;host from the fabric does not trigger this logout event with the filer.&amp;nbsp; The&lt;BR /&gt;filer does not know the host has been removed and thus, still believes the host&lt;BR /&gt;to be logged in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Having "fcp show initiator" display information about the disconnected host&lt;BR /&gt;initiator does not affect any filer functionality.&amp;nbsp; The login state is simply&lt;BR /&gt;left open until the target adapter is reset or the host initiator logs back&lt;BR /&gt;in again."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Thomas &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Aug 2010 07:57:36 GMT</pubDate>
    <dc:creator>thomas_glodde</dc:creator>
    <dc:date>2010-08-04T07:57:36Z</dc:date>
    <item>
      <title>fcp show initiator still display a dead server's wwpn</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/fcp-show-initiator-still-display-a-dead-server-s-wwpn/m-p/17140#M1520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have 2 windows sql 2005 cluser servers using lun in 2040A, When one of the host is down (for quite a while) ,&amp;nbsp; I type fcp show initiator , the wwpn is still there.&amp;nbsp; It does not make sense to me. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FAS2040A&amp;gt; fcp show initiator&lt;BR /&gt;Initiators connected on adapter 0b:&lt;BR /&gt;Portname&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Group&lt;BR /&gt;--------&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; -----&lt;BR /&gt;21:00:00:1b:32:1a:d3:0e&amp;nbsp;&amp;nbsp; FCP_cluster&amp;nbsp; &lt;SPAN style="color: #ff0000;"&gt;&amp;lt;-- this is weird&lt;/SPAN&gt;&lt;SPAN style="color: #ff0000;"&gt;, this host is down actually.&lt;/SPAN&gt;&lt;BR /&gt;21:00:00:1b:32:13:02:38&amp;nbsp;&amp;nbsp; FCP_cluster; FCP_dedicate&lt;BR /&gt;FAS2040A&amp;gt; fcp stop&lt;BR /&gt;Wed Aug&amp;nbsp; 4 14:06:20 CST [FAS2040A: fcp.service.shutdown:info]: FCP service shutdown&lt;BR /&gt;FCP service stopped.&lt;BR /&gt;FAS2040A&amp;gt; fcp start&lt;BR /&gt;Wed Aug&amp;nbsp; 4 14:06:25 CST [FAS2040A: fcp.service.startup:info]: FCP service startup&lt;BR /&gt;Wed Aug&amp;nbsp; 4 14:06:25 CST [FAS2040A: scsitarget.ispfct.onlining:notice]: Onlining Fibre Channel target adapter 0b.&lt;BR /&gt;FAS2040A&amp;gt; Wed Aug&amp;nbsp; 4 14:06:26 CST [FAS2040A: scsitarget.ispfct.linkUp:notice]: Link up on Fibre Channel target adapter 0b.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FAS2040A&amp;gt; fcp show initiator&lt;BR /&gt;Initiators connected on adapter 0b:&lt;BR /&gt;Portname&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Group&lt;BR /&gt;--------&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; -----&lt;BR /&gt;21:00:00:1b:32:13:02:38&amp;nbsp;&amp;nbsp; FCP_cluster; FCP_dedicate&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:11:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/fcp-show-initiator-still-display-a-dead-server-s-wwpn/m-p/17140#M1520</guid>
      <dc:creator>blackjack168</dc:creator>
      <dc:date>2025-06-05T07:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: fcp show initiator still display a dead server's wwpn</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/fcp-show-initiator-still-display-a-dead-server-s-wwpn/m-p/17146#M1521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;black,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yes, happens at our machines as well, seems it might stay there for a while if they dont properly do a fabric logout or so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But you can be sure if your service is shut down, then your LUN is save, regardless if the initiator is visible there or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check Bug &lt;STRONG&gt;75407&lt;/STRONG&gt; by NetApp:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"When a host initiator has been disconnected from the Fibre Channel fabric, the&lt;BR /&gt;filer's "fcp show initiator" command continues to show the initiator as logged&lt;BR /&gt;in, even though the switch shows the right status for the host.&amp;nbsp; This is due to&lt;BR /&gt;the nature of the fcp protocol.&amp;nbsp; When a host initiator first tries to &lt;BR /&gt;communicate with the filer, it must log in with the filer first.&amp;nbsp; This login&lt;BR /&gt;status is shown in "fcp show initiator".&amp;nbsp; In order for it to be removed from&lt;BR /&gt;the "fcp show initiator" list, it needs to be logged out.&amp;nbsp; Disconnecting a&lt;BR /&gt;host from the fabric does not trigger this logout event with the filer.&amp;nbsp; The&lt;BR /&gt;filer does not know the host has been removed and thus, still believes the host&lt;BR /&gt;to be logged in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Having "fcp show initiator" display information about the disconnected host&lt;BR /&gt;initiator does not affect any filer functionality.&amp;nbsp; The login state is simply&lt;BR /&gt;left open until the target adapter is reset or the host initiator logs back&lt;BR /&gt;in again."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Thomas &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Aug 2010 07:57:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/fcp-show-initiator-still-display-a-dead-server-s-wwpn/m-p/17146#M1521</guid>
      <dc:creator>thomas_glodde</dc:creator>
      <dc:date>2010-08-04T07:57:36Z</dc:date>
    </item>
  </channel>
</rss>

