Discovering MDisks using the CLI Scenario: typical usage for the command-line interface Creating managed disk (MDisk) groups using the CLI

This task provides step-by-step instructions for discovering MDisks using the command-line interface (CLI).

Context

When back-end controllers are added to the fibre-channel SAN and are included in the same switch zone as a SAN Volume Controller Cluster the cluster will automatically discover the back-end controller and will integrate the controller to determine what storage it is presented to the SAN Volume Controller. The SCSI LUs presented by the back-end controller will be displayed as unmanaged MDisks. If however the configuration of the back-end controller is modified after this has occurred then the SAN Volume Controller may be unaware of these configuration changes. This task allows a user to request the SAN Volume Controller to re-scan the fibre-channel SAN to update the list of unmanaged Mdisks.

Note:Note: The automatic discovery performed by SAN Volume Controller does not write anything to a unmanaged MDisk. It is only when a the user instructs the SAN Volume Controller to add a MDisk to a managed disk group or use a Mdisk to create an image mode virtual disk that the storage will actually be used.
Steps

Perform the following steps to display MDisks:

  1. Open a command prompt window.
  2. Check to see which MDisks are available by issuing the svctask detectmdisk command to manually scan the fibre-channel network for any MDisks.
  3. Issue the svcinfo lsmdiskcandidate command to show the unmanaged MDisks. These MDisks have not been assigned to an MDisk group. Alternatively, you can issue the svcinfo lsmdisk command to view all of the MDisks.
    Example

    In our hypothetical scenario we have a single back-end controller that is presenting eight SCSI LUs to the SAN Volume Controller. Issue the following command:
    svctask detectmdisk


    svcinfo lsmdiskcandidate


    This command displays the following:
    id
    0
    1
    2
    3
    4
    5
    6
    7


    Issue the following command:
    svcinfo lsmdisk -delim : -filtervalue mode=unmanaged


    This command displays the following:
    id:name:status:mode:mdisk_grp_id:mdisk_grp_name:
    capacity:ctrl_LUN_#:controller_name
    0:mdisk0:online:unmanaged:::273.3GB:0000000000000000:controller0
    1:mdisk1:online:unmanaged:::273.3GB:0000000000000001:controller0
    2:mdisk2:online:unmanaged:::273.3GB:0000000000000002:controller0
    3:mdisk3:online:unmanaged:::273.3GB:0000000000000003:controller0
    4:mdisk4:online:unmanaged:::136.7GB:0000000000000004:controller0
    5:mdisk5:online:unmanaged:::136.7GB:0000000000000005:controller0
    6:mdisk6:online:unmanaged:::136.7GB:0000000000000006:controller0
    7:mdisk7:online:unmanaged:::136.7GB:0000000000000007:controller0


Result

You have now shown that the back-end controllers and switches have been setup correctly and that the SAN Volume Controller can see the storage being presented by the back-end controller.

Related topics Scenario: typical usage for the command-line interface Creating managed disk (MDisk) groups using the CLI

(C) Copyright International Business Machines Corporation 2003, 2004