HSG80 / Windows 2000 Cluster missing LUNs

[David Evans_5]

Hello

I've had a look at the forum message 'Adding new disks to HSG80/Cluster' - it's similar to the issue we've been experiencing, but just stops short of providing the answer for us.

We have a pair of HP DL380G3 servers running Windows 2000 SP3, MS Cluster Service & SecurePath 3.1a SP3. The Large LUNs utility has also been installed. Each server has a pair of HBAs, with each HBA cross-connected to a pair of switches. The switches are then cross-connected to a pair of HSG80 controllers, running V86F-13 software & configured in dual-redundant mode with multi-bus failover.

On the HSG80s, we have 10 units defined, using LUN IDs 0-8 & 14. Ive checked the "show connections" output, the physical cabling & the zone /name server outputs and found that everything connects as expected.

When the first cluster node is started, all disks from the StorageWorks system are accessible. It doesn't matter which of the two physical servers we try this on, the results are the same. With the exception on LUN7 (which hasn't been brought into use yet), all other disks are members of the cluster.

The problem we have is that when the second node is started, it can only see 8 LUNS - 0 to 7. This has been checked both in Secure Path & also in the Windows 2000 Disk Management applet. If we attempt to move disk resources from one cluster node to the other, the move fails as the second node can't see two disks, LUNs 8 & 14. We've tried re-scanning the SCSI bus but the disks don't appear. Only if we shutdown the first node & re-scan the SCSI bus do we get access to the missing LUNs. We can then bring the cluster resources on-line on the second node. If we subsequently re-start the first cluster node, we have the same result, only 8 LUNS visible, with 8 & 14 missing again.

Any help or useful suggestions would be greatly appreciated.

[Michael Schulte zur Sur]

Hi,

can you post show conn full?

thanks,

Michael

[Mike Naime]

I believe that this may be a limitation of the old securepath software. When we first added a W2K cluster back in 2001, I seem to remember an 8 LUN/HBA pair presentation limit on the W2K systems. AIX had a 16 LUN limit at that time. No limit on VMS.

I'm a VMS admin, so I can't comment on what the latest Securepath version for W2K is.

I would check to see what the latest securepath version is, and upgrade to that.

Mike

[David Evans_5]

Hi

To Michael: Thanks for the the reply. Here's the show conn (plus other) output.

To Mike : I know there are various updates for SecurePath, but as it's a costly upgrade & I'd prefer to be sure that it's SP at fault first.

Regards

Dave

[Mike Naime]

David:

Any reason that you are setup for SCSI-2 mode instead of SCSI-3? I know that the default setting when the HSG's ship is SCSI-2. But since your OS supports it, why not SCSI-3?

From the controller standpoint, there is nothing to keep your systems from seeing all of the drives. It is something at the server/OS level that is preventing you from seeing the drives.

Looking at the release notes.http://h200007.www2.hp.com/bc/docs/support/UCR/SupportManual/TPM_aa-rtd4a-te/TPM_aa-rtd4a-te.pdf
Look at page 8 of 9 and you will see that it supports 64 LUNS in one HSG (Target)

[David Evans_5]

Mike

We recently upgraded the servers from NT4 to Windows 2000. The installation Engineer obviously missed that change - thanks for the prompt.

I believe that we'd have to move the existing LUN 0 to another ID as SCSI-3 requires LUN 0 for communications ?

I agree that SecurePath 3.1A SP3 should see all LUNS upto ID 63, but sadly it doesn't seem to be the case with this installation. I can't see any reason why the OS wouldn't be able to see a drive, other than SecurePath isn't making it available.

Dave