chcontroller

The chcontroller command modifies the attributes of a controller.

Syntax


>>- svctask -- -- chcontroller -- --+---------------------+----->
                                    '- -name -- new_name -'   

>-- --+-------------------------+--+- controller_id ---+-------><
      '- -allowquorum --+-yes-+-'  '- controller_name -'   
                        '-no--'

Parameters

-name new_name: (Optional) Specifies the new name to be assigned to the controller.
-allowquorum yes | no: (Optional) Specifies that the controller is allowed or is not allowed to support quorum disks. A value of yes enables a suitable controller to support quorum disks. A value of no disables a controller from supporting quorum disks, provided that the specified controller is not currently hosting a quorum disk.
controller_id | controller_name: (Required) Specifies the controller to modify; use either the controller name or the controller ID.

Description

This command changes the name of the controller that is specified by the controller_id | controller_name variable to the value that you specify with the -name parameter.

Use the optional -allowquorum parameter to turn quorum on or off for the specified controller.

Note: If any controller that is associated with an MDisk shows the allow_quorum attribute set to no with the svcinfo lscontroller command, the set quorum action fails for that MDisk. Before using the svctask chcontroller command to set the -allowquorum parameter to yes on any disk controller, check the following Web site to see whether the controller supports quorum.

www.ibm.com/storage/support/2145

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 that the controller is set up correctly for use with the cluster.

You can create one or more arrays on the controller using RAID-5, RAID-1, or RAID-0+1 (called RAID-10) for maximum redundancy and reliability. If your controller provides array partitioning, you can create a single partition from the entire capacity that is available in the array. Record the LUN number that you assign to each partition. If your disk controller system requires LUN mapping, follow the mapping guidelines to map the partitions or the arrays to the cluster ports.

To add a new disk controller system to a running configuration, ensure that the cluster has detected the new storage MDisks by issuing the svctask detectmdisk command. The controller has automatically been assigned a default name. If you are unsure of which controller is presenting the MDisks, issue the svcinfo lscontroller command to list the controllers. The new controller is listed with the highest numbered default name. Record the controller name and follow the instructions in the section about determining a disk controller system name.

Give this controller a unique name by issuing the following command:

svctask chcontroller -name newname oldname

List the unmanaged MDisks by issuing the following command:

svcinfo lsmdisk -filtervalue mode=unmanaged:controller_name=newname

These MDisks correspond to the RAID arrays or partitions that you have created. Record the field controller LUN number. The field controller LUN number corresponds with the LUN number that you assigned to each of the arrays or partitions.

Create a new managed disk group and add only the RAID arrays that belong to the new controller to this MDisk group. Avoid mixing RAID types; for each set of RAID array types (for example, RAID-5 or RAID-1), create a new MDisk group. Assign this MDisk group an appropriate name; if your controller is called FAST650-abc and the MDisk group contains RAID-5 arrays, assign the MDisk a name similar to F600-abc-R5. Issue the following command:

svctask mkmdiskgrp -ext 16 -name mdisk_grp_name -mdisk colon-separated list of RAID-x mdisks returned

Note: This creates a new MDisk group with an extent size of 16 MB.

An invocation example

svctask chcontroller -name newtwo 2

The resulting output

No feedback