Adding new disks to HSG80/Cluster

[Lloyd_9]

We have some spare slots in our array and the plan was to add another 3 disks, create a raidset from the disks and make it available to use. The configuration of the SAN consists of 1 Windows 2000 server and a 2 node Windows 2000 cluster connecting to the same fibre switch as the HSG80 controlled disk array. We would like the disk to be visible only to the 2 cluster nodes. Other disks have been setup this way on the same controller.

These are the steps we took to add the new drive including the syntax in capitals:

1 Physically add the disks to the array.

2 Add the disks into the controller configuration by using the run config command.
RUN CONFIG

3 Check the disks have been added then make the new raidset R04 using the 3 new disks.
ADD RAIDSET R04 DISK40500 DISK50500 DISK60500

4 Check and ensure that the raidset had been created then initialise the raidset R04.
INITIALIZE R04

5 Create a partition on the raidset R04.
CREATE_PARTITION R04 SIZE=LARGEST

6 Check the partition and status of the raidset then create The new unit D8 using the raidset R04.
ADD UNIT D8 R04 PARTITION=1

7. Disable all access to the unit D8 so specific access can be specified.
SET UNIT D8 DISABLE_ACCESS=ALL

8. specify the specific access required to the unit D8
SET UNIT D8 ENABLE_ACCESS_PATH= CLSTR1_PT1, CLSTR1_PT2, CLSTR2_PT1, CLSTR2_PT2

9. Reboot the 3 servers connected to the controller to access the disks in Windows.

After the reboot the servers did not pickup the new disk. We shutdown all 3 servers at once to do a total power cycle and the disks were still not visible. We ran a SHOW UNIT FULL command to compare the configuration of the working units to the new unit and the only difference was that the new unit stated NOT RESERVED compared to the working units that had RESERVED. To my knowledge this means that the unit is currently in use. After not being able to access the new disk we did a test by adding 1 new disk, initialising it and added it into a unit. This disk did not become available either

[Doug de Werd]

Don't know if this helps or not, but here is a technical paper on adding disks ("HA/F500" refers to an HSG80 based cluster)

ftp://ftp.compaq.com/pub/solutions/enterprise/ha/whitepapers/ISS091699-1.pdf

It's for NT4, but the storage procedure should be similar for Win2K

Thanks,
Doug

[Rob Buxton]

On the Server under the Disk Management, try using the Rescan Disks a couple of times.

Sometimes seems to take a while for Windows to see there's new hardware.

[Lloyd_9]

Hi Doug,

Thanks for the input. It is a usfull document but it dosent help me that much as I need to know the steps between 1 and 2 in the "adding and configuring the physical hard drive(s)" to ensure that I am doing everything correct.

Thanks,
Lloyd

[Lloyd_9]

Hi Rob,

Gave that a few trys but not luck. FYI the disks have been in there for a few days.

Thanks,
Lloyd

[Mike Naime · Accepted solution]

You did not set the ID of the unit after you created it.

SET Dxx ID=nnn

Also, why did you partition the raidset when you are using the entire raidset as the partition?

Add raid Rnn Disk.......
init Rnn
Add unit Dnn Rnn DIS=all
set Dnn ID=yyy
set Dnn ENA={connections}



D1 M1
LUN ID: 6000-1FE1-0014-47E0-0009-1340-1619-011F
IDENTIFIER = 1
Switches:
RUN NOWRITE_PROTECT READ_CACHE
READAHEAD_CACHE WRITEBACK_CACHE
MAX_READ_CACHED_TRANSFER_SIZE = 32
MAX_WRITE_CACHED_TRANSFER_SIZE = 32
Access:
CLSTR3B1, CLSTR3B2, CLSTR3T1, CLSTR3T2, CLSTR4B1, CLSTR4B2,
CLSTR4T1, CLSTR4T2
State:
ONLINE to this controller
Reserved
NOPREFERRED_PATH
Size: 35556389 blocks
Geometry (C/H/S): ( 7000 / 20 / 254 )

[Lloyd_9]

Hi Mike,

I had a look at the other existing working units and they all specify "NOIDENTIFIER" I was assuming that an ID did not have to be set. Is this right?

Lloyd

[Mike Naime]

With the AIX systems that I deal with, the D number = the ID that the AIX system see's.

Examples
(First cluster)
D1 = LUN 1
D2 = LUN 2
....
D9 = Lun 9
(Second Cluster with a connection unit offset of 20 )
D21 = LUN 1
D22 = LUN 2
...
D33 = LUN 13


With W2k and VMS, I set the ID=xxx. This determines the LUN number that is presented to the system.

This is used along with the Selective Storage presentation.

[Lloyd_9]

Hi,

Thanks for the response. I assigned an ID to the unit and rebooted the server. Unfortunately I got the same result. I am unsure if that is what the issue is as the other units do not have a identifier assigned.

once again any help is appreciated

Lloyd

[Rob Buxton]

I'm intrigued that this is D8.
Is this an issue with Large LUNs not being enabled.

I cannot recall where this is enabled / disabled. I believe it is enabled by default.

But, I do recall a check box somewhere.

[Lloyd_9]

Hi,

Our team here had discussed if this was an issue, or there was an issue of maximum LUN's. We did some research and could not find and evidence to say that this was the issue but we did not discard the thought.

Lloyd

[Lloyd_9]

I have attached the HSG80 configuration file help answer questions about this issue.

[Rob Buxton]

The setting is not on the HSG. I recall it being on a GUI during one of the installs of some of the FC Software but not too sure which.

I don't think it's Secure Path so that kind of leaves the HBA Drivers and HSZ install.

[Tien Choon Wei]

It's a large LUN issue. By default. Win2k accepts only LUN 0 to 7. You need to install the LargeLUN patch provided by HP.

The patch by HP will enable LUNs from 0 to 64 to be seen by W2k.

Search around your documentation/CDs. It should come as part of your default kit. If you don't have it, I can provide you with the software.

[Lloyd_9]

Hi,

Thanks for that it was exactly what I needed. After I installed the patch and rebooted the servers could see the new disks straight away.

Thanks,
Lloyd