Windows Server 2003 Cluster iSCSI drives missing from standby node

Hi All,

I'm in big trouble here.
I would appreciate any feasible response to this question ASAP.
I had been searching all the way in internet. And first time I haven't got
the reasonable link or answer to my query.

Coming back to point.
I have 2 x Windows Server 2003 servers as SQL Cluster.
I recently found some logs in cluster stating the SRV-B server is not able
to take load as the disks are not appearing in Disk Management or iSCSI
Initiator > Target Properties > Devices.
I still see the “Target� session connected, yet even after rescanning disks
the disks are not appearing.

The same setting is on Active node SRV-A and which is able to see the iSCSI
Devices (Disks).
I understand the Disk should not be actually readable on Passive node (as
they are active on other cluster node), still these disks should appear as
“Unreadable� on disk management and LUNs should be visible in iSCSI initiator.

I tried logging off from iSCSI session and reinstalled iSCSI initiator, even
rebooted the server but all in vain. Cluster service is starting properly.
But cluster is not able to fail over to SRV-B, and fails back to SRV-A.

Only difference I find in this malfunction node (SRV-B) is that - iSCSI
Initiator > Target > Identifier is ending with 000002; where as on other
servers (from other clusters - active or passive) it appears as 00001.

Same reflects in Session Connection ID which appears as 0x1; where as on
other working server it appears as 0x0.

I don’t find any option to set either of these IDs.

I’ve checked with storage team and they have advised that there are no
changes done from their end, and as long as IQN is visible on their end they
don’t find any problem. And it could be problem with server.

Could someone please advice me on this issue ASAP?

PS: Each time I log off from iSCSI Session and log in back, the above ID is
increased by 1.

Thanks in advance

What is your iSCSI target?


"Windows Server 2003 Cluster iSCSI drives" <Windows Server 2003 Cluster
iSCSI > wrote in message
news:BD65448E-ADB7-4736-A925-...
> Hi All,
>
> I'm in big trouble here.
> I would appreciate any feasible response to this question ASAP.
> I had been searching all the way in internet. And first time I haven't got
> the reasonable link or answer to my query.
>
> Coming back to point.
> I have 2 x Windows Server 2003 servers as SQL Cluster.
> I recently found some logs in cluster stating the SRV-B server is not able
> to take load as the disks are not appearing in Disk Management or iSCSI
> Initiator > Target Properties > Devices.
> I still see the "Target" session connected, yet even after rescanning
> disks
> the disks are not appearing.
>
> The same setting is on Active node SRV-A and which is able to see the
> iSCSI
> Devices (Disks).
> I understand the Disk should not be actually readable on Passive node (as
> they are active on other cluster node), still these disks should appear as
> "Unreadable" on disk management and LUNs should be visible in iSCSI
> initiator.
>
> I tried logging off from iSCSI session and reinstalled iSCSI initiator,
> even
> rebooted the server but all in vain. Cluster service is starting properly.
> But cluster is not able to fail over to SRV-B, and fails back to SRV-A.
>
> Only difference I find in this malfunction node (SRV-B) is that - iSCSI
> Initiator > Target > Identifier is ending with 000002; where as on other
> servers (from other clusters - active or passive) it appears as 00001.
>
> Same reflects in Session Connection ID which appears as 0x1; where as on
> other working server it appears as 0x0.
>
> I don't find any option to set either of these IDs.
>
> I've checked with storage team and they have advised that there are no
> changes done from their end, and as long as IQN is visible on their end
> they
> don't find any problem. And it could be problem with server.
>
> Could someone please advice me on this issue ASAP?
>
> PS: Each time I log off from iSCSI Session and log in back, the above ID
> is
> increased by 1.
>
> Thanks in advance

iSCSI target is NAS storage - NetApp filer Model 940.


"John Fullbright" wrote:

> What is your iSCSI target?
>
>
> "Windows Server 2003 Cluster iSCSI drives" <Windows Server 2003 Cluster
> iSCSI > wrote in message
> news:BD65448E-ADB7-4736-A925-...
> > Hi All,
> >
> > I'm in big trouble here.
> > I would appreciate any feasible response to this question ASAP.
> > I had been searching all the way in internet. And first time I haven't got
> > the reasonable link or answer to my query.
> >
> > Coming back to point.
> > I have 2 x Windows Server 2003 servers as SQL Cluster.
> > I recently found some logs in cluster stating the SRV-B server is not able
> > to take load as the disks are not appearing in Disk Management or iSCSI
> > Initiator > Target Properties > Devices.
> > I still see the "Target" session connected, yet even after rescanning
> > disks
> > the disks are not appearing.
> >
> > The same setting is on Active node SRV-A and which is able to see the
> > iSCSI
> > Devices (Disks).
> > I understand the Disk should not be actually readable on Passive node (as
> > they are active on other cluster node), still these disks should appear as
> > "Unreadable" on disk management and LUNs should be visible in iSCSI
> > initiator.
> >
> > I tried logging off from iSCSI session and reinstalled iSCSI initiator,
> > even
> > rebooted the server but all in vain. Cluster service is starting properly.
> > But cluster is not able to fail over to SRV-B, and fails back to SRV-A.
> >
> > Only difference I find in this malfunction node (SRV-B) is that - iSCSI
> > Initiator > Target > Identifier is ending with 000002; where as on other
> > servers (from other clusters - active or passive) it appears as 00001.
> >
> > Same reflects in Session Connection ID which appears as 0x1; where as on
> > other working server it appears as 0x0.
> >
> > I don't find any option to set either of these IDs.
> >
> > I've checked with storage team and they have advised that there are no
> > changes done from their end, and as long as IQN is visible on their end
> > they
> > don't find any problem. And it could be problem with server.
> >
> > Could someone please advice me on this issue ASAP?
> >
> > PS: Each time I log off from iSCSI Session and log in back, the above ID
> > is
> > increased by 1.
> >
> > Thanks in advance
>
>
>

You should use snapdrive to connect it as a shared disk. You may also want
to post over in the Netapp communites to get more specific help
http://www.netapp.com/us/communities/




"Windows Server 2003 Cluster iSCSI drives" <Windows Server 2003 Cluster
iSCSI > wrote in message
news:BD65448E-ADB7-4736-A925-...
> Hi All,
>
> I'm in big trouble here.
> I would appreciate any feasible response to this question ASAP.
> I had been searching all the way in internet. And first time I haven't got
> the reasonable link or answer to my que
> Coming back to point.
> I have 2 x Windows Server 2003 servers as SQL Cluster.
> I recently found some logs in cluster stating the SRV-B server is not able
> to take load as the disks are not appearing in Disk Management or iSCSI
> Initiator > Target Properties > Devices.
> I still see the "Target" session connected, yet even after rescanning
> disks
> the disks are not appearing.
>
> The same setting is on Active node SRV-A and which is able to see the
> iSCSI
> Devices (Disks).
> I understand the Disk should not be actually readable on Passive node (as
> they are active on other cluster node), still these disks should appear as
> "Unreadable" on disk management and LUNs should be visible in iSCSI
> initiator.
>
> I tried logging off from iSCSI session and reinstalled iSCSI initiator,
> even
> rebooted the server but all in vain. Cluster service is starting properly.
> But cluster is not able to fail over to SRV-B, and fails back to SRV-A.
>
> Only difference I find in this malfunction node (SRV-B) is that - iSCSI
> Initiator > Target > Identifier is ending with 000002; where as on other
> servers (from other clusters - active or passive) it appears as 00001.
>
> Same reflects in Session Connection ID which appears as 0x1; where as on
> other working server it appears as 0x0.
>
> I don't find any option to set either of these IDs.
>
> I've checked with storage team and they have advised that there are no
> changes done from their end, and as long as IQN is visible on their end
> they
> don't find any problem. And it could be problem with server.
>
> Could someone please advice me on this issue ASAP?
>
> PS: Each time I log off from iSCSI Session and log in back, the above ID
> is
> increased by 1.
>
> Thanks in advance