I have 2 windows sql 2005 cluser servers using lun in 2040A, When one of the host is down (for quite a while) , I type fcp show initiator , the wwpn is still there. It does not make sense to me.
FAS2040A> fcp show initiator Initiators connected on adapter 0b: Portname Group -------- ----- 21:00:00:1b:32:1a:d3:0e FCP_cluster <-- this is weird, this host is down actually. 21:00:00:1b:32:13:02:38 FCP_cluster; FCP_dedicate FAS2040A> fcp stop Wed Aug 4 14:06:20 CST [FAS2040A: fcp.service.shutdown:info]: FCP service shutdown FCP service stopped. FAS2040A> fcp start Wed Aug 4 14:06:25 CST [FAS2040A: fcp.service.startup:info]: FCP service startup Wed Aug 4 14:06:25 CST [FAS2040A: scsitarget.ispfct.onlining:notice]: Onlining Fibre Channel target adapter 0b. FAS2040A> Wed Aug 4 14:06:26 CST [FAS2040A: scsitarget.ispfct.linkUp:notice]: Link up on Fibre Channel target adapter 0b.
FAS2040A> fcp show initiator Initiators connected on adapter 0b: Portname Group -------- ----- 21:00:00:1b:32:13:02:38 FCP_cluster; FCP_dedicate
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.
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.
Check Bug 75407 by NetApp:
"When a host initiator has been disconnected from the Fibre Channel fabric, the filer's "fcp show initiator" command continues to show the initiator as logged in, even though the switch shows the right status for the host. This is due to the nature of the fcp protocol. When a host initiator first tries to communicate with the filer, it must log in with the filer first. This login status is shown in "fcp show initiator". In order for it to be removed from the "fcp show initiator" list, it needs to be logged out. Disconnecting a host from the fabric does not trigger this logout event with the filer. The filer does not know the host has been removed and thus, still believes the host to be logged in.
Having "fcp show initiator" display information about the disconnected host initiator does not affect any filer functionality. The login state is simply left open until the target adapter is reset or the host initiator logs back in again."