Adding a new storage controller to a running configuration using the CLI Advanced functions with the CLI Expanding a VDisk using the CLI

This task provides step-by-step instructions for adding a new disk controller system to a running configuration.

Prerequisites

You can add a new disk controller system to your SAN at any time. Follow the switch zoning guidelines in the section about switch zoning. Also, ensure the controller is setup correctly for use with the SAN Volume Controller .

You should create one or more arrays on the new controller. It is recommend that you use, RAID-5, RAID-1 or RAID-0+1 (sometimes called RAID-10) for maximum redundancy and reliability. Generally 5+P arrays are recommend. If your controller provides array partitioning we recommend that you create a single partition from the entire capacity available in the array, remember the LUN number that you assign to each partition as you will need this later. You should also follow the mapping guidelines (if your disk controller system requires LUN mapping) to map the partitions or arrays to the SAN Volume Controller ports.

Steps

Perform the following steps to add a new disk controller system to a running configuration:

  1. To ensure that the cluster has detected the new storage (MDisks) issue the following command:
    svctask detectmdisk
  2. The controller itself will have automatically been assigned a default name. If you are unsure which controller is presenting the MDisks, list the controllers by issuing the following command:
    svcinfo lscontroller
    You should see a new controller listed (the one with the highest numbered default name). Remember the controller name and follow the instructions in the section about determining a disk controller system name.
  3. You should give this controller a name that you can easily use to identify it. Issue the following command:
    svctask chcontroller -name <newname> <oldname>
  4. List the unmanaged MDisks by issuing the following command:
    svcinfo lsmdisk -filtervalue mode=unmanaged:controller_name=<new_name>
    These MDisks should correspond with the RAID arrays or partitions you have created. Remember the field controller LUN number. This corresponds with the LUN number you assigned to each of the arrays or partitions.
  5. It is recommended that you create a new managed disk group and add only the RAID arrays that belong to the new controller to this MDisk group. You should also avoid mixing RAID types, so for each set of RAID array types (for example, RAID-5, RAID-1) you should create a new MDisk group. Give this MDisk group an appropriate name, so if your controller is called FAST650-fred, and the MDisk group contains RAID-5 arrays, call it something like F600-fred-R5). Issue the following command:
    svctask mkmdiskgrp -ext 16 -name <mdisk_grp_name>
    -mdisk <colon separated list of RAID-x mdisks returned
    in step 4.

    Note:Note: This will create a new MDisk group with an extent size of 16MB.
Related topics Advanced functions with the CLI Expanding a VDisk using the CLI

(C) Copyright International Business Machines Corporation 2003, 2004