Deployment Example: Sun Java System Communications Services for Access Anywhere (EdgeMail)

2.2.2.3 Creating Logical Drives and Logical Partitions

Each 3510 will have 2 logical drives and 1 global spare. One Logical drive consist of 6 drives (Raid5) and another consist of 5 disk Raid5. So you will end up with one logical disk with 682GB and another with 545 GB. Disk 11 will always be Global Spare. All minnows are configured identically.

Figure 2–3 Logical Drives on each 3510

Description in text above.

Each logical drive is further divided in to 4 volumes. Logical drives ld0, ld2 and ld4 of size 682 GB are divided into the following volume sizes:

ld0:00 = 20GB 

ld0:01 = 227GB 

ld0:02 = 227GB 

ld0:03 = 227GB 

ld0:04 = 5MB (leftover) 

Logical Drive ld1, ld3 and ld5 of size 545 GB are divided into the following volume sizes:

ld1:00 = 20GB 

ld1:01 = 180GB 

ld1:02 = 180GB 

ld1:03= 180GB 

ld1:04 = 5MB (leftover) 

Figure 2–4 Logical Volumes on each 3510

Description in text above.

ProcedureTo Set up Logical Drives and Volumes

Steps
  1. Delete the existing logical drive configured by default:


    sccli> show logical
    sccli> unmap ld0
    sccli> unmap ld1
    sccli> delete logical-drive ld1
    sccli> delete logical-drive ld0
    
  2. Remove unneeded global-spare. By default each 3510 brick will have 2 global spares and you need to remove one of them:


    sccli> show disk 2.5
    Ch  Id      Size   Speed  LD     Status   IDs                   Rev
    -------------------------------------------------------------------
     2   5  136.73GB   200MB  GLOBAL STAND-BY SEAGATE ST314FSUN146G 0307
                                                  S/N 3HY87KSM00007445
    sccli> unconfigure global-spare 2.5
    
  3. Create logical drives. This process is same for all minnows and they are all carved up logically same way. This will take couple of hours.


    sccli> create logical-drive raid5 2.0 2.1 2.2 2.3 2.4 2.5
        sccli: created logical drive 08C6C8D4
    sccli> create logical-drive raid5 2.6 2.7 2.8 2.9 2.10
        sccli: created logical drive 55689384
    sccli> create logical-drive raid5 2.16 2.17 2.18 2.19 2.20 2.21
        sccli: created logical drive 68B4C07E
    sccli> create logical-drive raid5 2.22 2.23 2.24 2.25 2.26
        sccli: created logical drive 2B7F3FDA
    sccli> create logical-drive raid5 2.32 2.33 2.34 2.35 2.36 2.37
        sccli: created logical drive 014D9F13
    sccli> create logical-drive raid5 2.38 2.39 2.40 2.41 2.42
        sccli: created logical drive 189DAEFF
  4. Configure the global spares as follows:


    sccli> configure global-spare 2.43
    sccli> configure global-spare 2.27
    sccli> configure global-spare 2.11
    
  5. After all logical drives are built, they need to be assigned to either primary or secondary controller. By default all disks will be assigned to primary controller. For better distribution of i/o loads, logical drives ld0, ld2, and ld4 are assigned to primary and ld1, ld3, and ld5 need to be reassigned to secondary. This process needs to be done through telnet.


    telnet amer-minnow-01
    CTL-L    (select vt100 if need to select term type)
    ---
    "View and Edit Logical Drives"
    select LD1
    "Logical Drive Assignments"
    "Redundant Controller Logical Drive Assign to Secondary Controller"
    "Yes"
    Query:  "Do you want to Reset the Controller now?"   
    "No"
    

    Repeat the above sequence for LD3 and LD5, except you must reset the controller after reassigning LD5.

  6. Verify the logical disks assignments by using the sccli interface:


    # sccli amer-minnow-01
    sccli: selected se3000://172.31.0.141:58632 [SUN StorEdge 3510 SN#084DCD]
    sccli> show logical
    LD    LD-ID     Size      Assigned    Type  Disks Spare Failed Status
    ---------------------------------------------------------------------
    ld0   08C6C8D4  682.39GB  Primary     RAID5   6     3     0    Good
    ld1   55689384  545.91GB  Secondary   RAID5   5     3     0    Good
    ld2   68B4C07E  682.39GB  Primary     RAID5   6     3     0    Good
    ld3   2B7F3FDA  545.91GB  Secondary   RAID5   5     3     0    Good
    ld4   014D9F13  682.39GB  Primary     RAID5   6     3     0    Good
    ld5   189DAEFF  545.91GB  Secondary   RAID5   5     3     0    Good
  7. Create the logical volumes, called partitions, with the following commands:


    sccli> configure partition ld0-00  20g
    sccli> configure partition ld0-01  226090m
    sccli> configure partition ld0-02  226090m
    sccli> configure partition ld0-03  226090m
    sccli> configure partition ld2-00  20g
    sccli> configure partition ld2-01  226090m
    sccli> configure partition ld2-02  226090m
    sccli> configure partition ld2-03  226090m
    sccli> configure partition ld4-00  20g
    sccli> configure partition ld4-01  226090m
    sccli> configure partition ld4-02  226090m
    sccli> configure partition ld4-03  226090m
    
    sccli> configure partition ld1-00  20g
    sccli> configure partition ld1-01  179510m
    sccli> configure partition ld1-02  179510m
    sccli> configure partition ld1-03  179510m
    sccli> configure partition ld3-00  20g
    sccli> configure partition ld3-01  179510m
    sccli> configure partition ld3-02  179510m
    sccli> configure partition ld3-03  179510m
    sccli> configure partition ld5-00  20g
    sccli> configure partition ld5-01  179510m
    sccli> configure partition ld5-02  179510m
    sccli> configure partition ld5-03  179510m
    
  8. Verify the logical partitions created. You will notice left over disk space will be under ld0-04 partition:


    sccli> show part
    LD/LV    ID-Partition      Size
    -------------------------------
    ld0-00   08C6C8D4-00    20.00GB
    ld0-01   08C6C8D4-01   220.79GB
    ld0-02   08C6C8D4-02   220.79GB
    ld0-03   08C6C8D4-03   220.79GB
    ld0-04   08C6C8D4-04       17MB
    [...]
  9. Reset the controller when configuration is complete and recheck partitions.


    scli> reset controller
    WARNING: This is a potentially dangerous operation.
    The controller will go offline for several minutes.
    Data loss may occur if the controller is currently in use.
    Are you sure? y
    sccli: shutting down controller...
    sccli: controller is shut down
    sccli: resetting controller...
    sccli> show part
    [...]