chcontroller

Use the chcontroller command to modify the attributes of a controller.

Syntax

chcontroller [ -name new_name ] [ -allowquorum { yes | no } ] { [ -site { site_name | site_id } ] | [ -nosite ] } { controller_id | controller_name }

Parameters

-namenew_name: (Optional) Specifies the new name to be assigned to the controller.
-allowquorumyes | 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.
-sitesite_name | site_id: (Optional) Specifies the numeric site value or site name for the controller. The value is 1, 2, or 3.
Note: The controller site cannot be changed if the system topology is hyperswap (and there are managed MDisks).
-nosite: (Optional) Resets the site value for the controller.
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.

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

https://datacentersupport.lenovo.com/us/en/products/storage/lenovo-storage/v3700v2/6535

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 clustered system (system).

To add a new disk controller system to a running configuration, ensure that the system has detected the new storage MDisks by issuing the detectmdisk command. The controller has automatically been assigned a default name. If you are unsure of which controller is presenting the MDisks, issue the 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 descriptive name by issuing the following command:

chcontroller -name newnameoldname

List the unmanaged MDisks by issuing the following command:

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 storage pool and add only the RAID arrays that belong to the new controller to this storage pool. Avoid mixing RAID types; for each set of RAID array types (for example, RAID-5 or RAID-6), create a new storage pool. Assign this storage pool an appropriate name; if your controller is called FAST650-abc and the storage pool contains RAID-5 arrays, assign the MDisk a name similar to F600-abc-R5. Issue the following command:

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

Note: This creates a new storage pool with an extent size of 16 MB.

An invocation example

chcontroller -name newtwo 2

The resulting output:

No feedback

An invocation example

chcontroller -site site1 controller18

The resulting output:

No feedback