I’ve been rebuilding our lab CLARiiONs recently, and wanted to configure the Reserved LUN Pool (RLP) for use with SnapView and MirrorView/Asynchronous. Since I spent approximately 8 days per week in Unisphere recently performing storage provisioning, I’ve since made it a goal of mine to never, ever have to log in to Unisphere to do anything again. While this may be unattainable, you can get an awful lot done with a combination of Microsoft Excel, Notepad and naviseccli.
So I needed to configure a Reserved LUN Pool for use with MV/A, SnapView Incremental SAN Copy, and so forth. I won’t go into the reasons for what I’ve created, but let’s just say I needed to create about 50 LUNs and give them each a label. Here’s what I did:
Firstly, I created a RAID Group with an ID of 1 using disks 5 – 9 in the first enclosure.
C:\>naviseccli -h 256.256.256.256 createrg 1 0_0_5 0_0_6 0_0_7 0_0_8 0_0_9
It was then necessary to bind a series of 20GB LUNs to use, 25 for each SP. If you’re smart with Excel you can set the following command to do this for you with little fuss.
C:\>naviseccli -h 256.256.256.256 bind r5 50 -rg 1 -aa 0 -cap 20 -sp a -sq gb
Here I’ve specified the raid-type (r5), the lun id (50), the RAID Group (1), -aa 0 (disabling auto-assign), -cap (the capacity), -sp (a or b), and the -sq (size qualifier, which can be mb|gb|tb|sc|bc). Note that if you don’t specify the LUN ID, it will automatically use the next available ID.
So now I’ve bound the LUNs, I can use another command to give them a label that corresponds with our naming standard (using our old friend chglun):
C:\>naviseccli -h 256.256.256.256 chglun -l 50 -name TESTLAB1_RLP01_0050
Once you’ve created the LUNs you require, you can then add them to the Reserved LUN Pool with the reserved command.
C:\>naviseccli -h 256.256.256.256 reserved -lunpool -addlun 99
To check that everything’s in order, use the -list switch to get an output of the current RLP configuration.
C:\>naviseccli -h 256.256.256.256 reserved -lunpool -list
Name of the SP: GLOBAL
Total Number of LUNs in Pool: 50
Number of Unallocated LUNs in Pool: 50
Unallocated LUNs: 53, 63, 98, 78, 71, 56, 88, 69, 92, 54, 99, 79, 72, 58, 81, 5
7, 85, 93, 61, 96, 67, 76, 86, 64, 50, 66, 52, 62, 68, 77, 89, 70, 55, 65, 91, 8
0, 73, 59, 82, 90, 94, 84, 97, 74, 60, 83, 95, 75, 87, 51
Total size in GB: 999.975586
Unallocated size in GB: 999.975586
Used LUN Pool in GB: 0
% Used of LUN Pool: 0
Chunk size in disk blocks: 128
No LUN in LUN Pool associated with target LUN.
If, for some reason, you want to remove a LUN from the RLP, and it isn’t currently in use by one of the layered applications, you can use the -rmlun switch.
C:\>naviseccli -h 256.256.256.256 reserved -lunpool -rmlun 99 -o
If you omit the override [-o] option, the CLI prompts for confirmation before removing the LUN from reserved LUN pool. It’s possible to argue that, with the ability to create multiple LUNs from Unisphere, it might be simpler to not worry about naviseccli, but I think that it’s a very efficient way to get things done quickly, particularly if you’re working in a Unisphere domain with a large number of CLARiiONs, or on a workstation that has some internet browser “issues”.