Cisco UCS C-Series Integrated Management Controller CLI Configuration Guide for C3X60 Servers

Creating Virtual Drives from Unused Physical Drives

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # create virtual-drive	At this point, you are prompted to enter information corresponding to the RAID level, the physical drives to be used, the size and the write policy for the new virtual drive. Enter the appropriate information at each prompt. When you have finished specifying the virtual drive information, you are prompted to confirm that the information is correct. Enter y (yes) to confirm, or n (no) to cancel the operation.
Step 5	Server /chassis/storageadapter # show virtual-drive	Displays the existing virtual drives.

This example shows how to create a new virtual drive that spans two unused physical drives.

Server # scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # create-virtual-drive
Please enter RAID level
0, 1, 5, 10, 50 --> 1

Please choose from the following 10 unused physical drives:
    ID  Size(MB)       Model        Interface  Type
     1  571776         SEAGATE      SAS        HDD
     2  571776         SEAGATE      SAS        HDD
     4  571776         SEAGATE      SAS        HDD
     5  428672         SEAGATE      SAS        HDD
     6  571776         SEAGATE      SAS        HDD
     7  571776         SEAGATE      SAS        HDD
     8  571776         SEAGATE      SAS        HDD
     9  428672         SEAGATE      SAS        HDD
    10  571776         SEAGATE      SAS        HDD
    11  953344         SEAGATE      SAS        HDD

Specify physical disks for span 0:
  Enter comma-separated PDs from above list--> 1,2
  Please enter Virtual Drive name (15 characters maximum)--> test_v_drive
  Please enter Virtual Drive size in MB, GB, or TB
   Example format: '400 GB' --> 10 GB

Optional attribute:

  stripsize: defaults to 64K Bytes

     0: 8K Bytes
    1: 16K Bytes
    2: 32K Bytes
    3: 64K Bytes
    4: 128K Bytes
    5: 256K Bytes
    6: 512K Bytes
    7: 1024K Bytes
  Choose number from above options or hit return to pick default--> 2
stripsize will be set to 32K Bytes (6 and 'strip-size\:32k')

  Disk Cache Policy: defaults to Unchanged

     0: Unchanged
    1: Enabled
    2: Disabled
  Choose number from above options or hit return to pick default--> 0
Disk Cache Policy will be set to Unchanged (0 and 'disk-cache-policy\:unchanged'                                                                                                             )

  Read Policy: defaults to No Read Ahead

     0: No Read Ahead
    1: Always
  Choose number from above options or hit return to pick default--> 0
Read Policy will be set to No Read Ahead (0 and 'read-policy\:no-read-ahead')

  Write Policy: defaults to Write Through

     0: Write Through
    1: Write Back Good BBU
    2: Always Write Back
  Choose number from above options or hit return to pick default--> 0
Write Policy will be set to Write Through (0 and 'write-policy\:write-through')

  IO Policy: defaults to Direct I/O

     0: Direct I/O
    1: Cached I/O
  Choose number from above options or hit return to pick default--> 0
IO Policy will be set to Direct I/O (0 and 'io-policy\:direct-io')

  Access Policy: defaults to Read Write

     0: Read Write
    1: Read Only
    2: Blocked
  Choose number from above options or hit return to pick default--> 0
Access Policy will be set to Read Write (0 and 'access-policy\:read-write')

New virtual drive will have the following characteristics:
  - Spans: '[1.2]'
  - RAID level: '1'
  - Name: 'test_v_drive'
  - Size: 10 GB
  - stripsize: 32K Bytes
  - Disk Cache Policy: Unchanged
  - Read Policy: No Read Ahead
  - Write Policy: Write Through
  - IO Policy: Direct I/O
  - Access Policy: Read Write

OK? (y or n)--> y

Server /chassis/server/storageadapter # show virtual-drive
Virtual Drive Health         Status               Name             Size       RAID Level Boot Drive
------------- -------------- -------------------- ---------------- ---------- ---------- ----------
0             Good           Optimal                               150528 MB  RAID 0     false
1             Good           Optimal                               20480 MB   RAID 0     true
2             Good           Optimal                               114140 MB  RAID 0     false
3             Good           Optimal              test_v_drive     10000 MB   RAID 1     false
4             Good           Optimal              new_from_test    500 MB     RAID 1     false

Server /chassis/storageadapter #

Creating Virtual Drive from an Existing Drive Group

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/storageadapter # carve-virtual-drive	At this point, you are prompted to enter information corresponding to the virtual drives to be used, and the size and the write policy for the new virtual drive. Enter the appropriate information at each prompt. When you have finished specifying the virtual drive information, you are prompted to confirm that the information is correct. Enter y (yes) to confirm, or n (no) to cancel the operation.
Step 5	Server /chassis/server/storageadapter # show virtual-drive	Displays the existing virtual drives.

This example shows how to carve a new virtual drive out of unused space in an existing RAID 1 drive group:

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # carve-virtual-drive
  < Fetching virtual drives...>

ID  Name              RL  VDSize        MaxPossibleSize PD(s)
----------------------------------------------------------------
0  RAID0_12          0   100 MB        Unknown         1,2

Please choose from the above list the virtual drive number
whose space the new virtual drive will share--> 0
New virtual drive will share space with VD 0

Please enter Virtual Drive name (15 characters maximum)--> test_v_drive
Please enter Virtual Drive size in MB, GB, or TB (maximum: Unknown)
  Example format: '400 GB' --> 10 GB

Optional attributes:

  stripsize: defaults to 64K Bytes
     0: 8K Bytes
    1: 16K Bytes
    2: 32K Bytes
    3: 64K Bytes
    4: 128K Bytes
    5: 256K Bytes
    6: 512K Bytes
    7: 1024K Bytes
  Choose number from above options or hit return to pick default--> 0
stripsize will be set to 8K Bytes (4 and 'strip-size\:8k')

  Disk Cache Policy: defaults to Unchanged
     0: Unchanged
    1: Enabled
    2: Disabled
  Choose number from above options or hit return to pick default--> 0
Disk Cache Policy will be set to Unchanged (0 and 'disk-cache-policy\:unchanged')

  Read Policy: defaults to No Read Ahead
     0: No Read Ahead
    1: Always
  Choose number from above options or hit return to pick default--> 0
Read Policy will be set to No Read Ahead (0 and 'read-policy\:no-read-ahead')

  Write Policy: defaults to Write Through
     0: Write Through
    1: Write Back Good BBU
    2: Always Write Back
  Choose number from above options or hit return to pick default--> 0
Write Policy will be set to Write Through (0 and 'write-policy\:write-through')

  IO Policy: defaults to Direct I/O
     0: Direct I/O
    1: Cached I/O
  Choose number from above options or hit return to pick default--> 0
IO Policy will be set to Direct I/O (0 and 'io-policy\:direct-io')

  Access Policy: defaults to Read Write
     0: Read Write
    1: Read Only
    2: Blocked
  Choose number from above options or hit return to pick default--> 0
Access Policy will be set to Read Write (0 and 'access-policy\:read-write')

New virtual drive will have the following characteristics:
  - It will share space with virtual drive 0
  - Name: 'amit'
  - Size: 10 GB
  - stripsize: 8K Bytes
  - Disk Cache Policy: Unchanged
  - Read Policy: No Read Ahead
  - Write Policy: Write Through
  - IO Policy: Direct I/O
  - Access Policy: Read Write

OK? (y or n)--> y
Server /chassis/storageadapter # show virtual-drive
Virtual Drive Health         Status               Name             Size       RAID Level Boot Drive
------------- -------------- -------------------- ---------------- ---------- ---------- ----------
0             Good           Optimal                               150528 MB  RAID 0     false
1             Good           Optimal                               20480 MB   RAID 0     true
2             Good           Optimal                               114140 MB  RAID 0     false
3             Good           Optimal              test_v_drive     10000 MB   RAID 1     false
4             Good           Optimal              new_from_test    500 MB     RAID 1     false

Server /chassis/server/storageadapter #

Setting a Virtual Drive as Transport Ready

Before You Begin

You must log in with admin privileges to perform this task.
The virtual drive must be in optimal state to enable transport ready.

Procedure

Command or Action

Purpose

Step 1

Server # scope chassis

Enters the chassis command mode.

Step 2

Server /chassis # scope server {1 | 2}

Enters server command mode of server 1 or 2.

Step 3

Server /chassis/server # scope storageadapter slot ID

Enters the command mode for an installed storage card.

Step 4

Server /chassis/server/storageadapter # scope virtual-drive drive-number

Enters the command mode for the specified virtual drive.

Step 5

Server /chassis/server/storageadapter/virtual-drive # set-transport-ready {include-all | exclude-all | include-dhsp}

Enter the initialization type using which you can set the selected virtual drive as transport ready. This can be one of the following:

exlude-all— Excludes all the dedicated hot spare drives.
include-all— Includes any exclusively available or shared dedicated hot spare drives.
include-dhsp— Includes exclusive dedicated hot spare drives.

Sets the virtual drive to transport ready and assigns the chosen properties.

When you are prompted to confirm the action. Enter y to confirm.

Note

When you set a virtual drive to transport ready all the physical drives associated with it are displayed as Ready to remove.

Step 6

Server /chassis/server/storageadapter/virtual-drive # show detail

(Optional)

Display the virtual drive properties with the change.

This example shows how to set virtual drive 5 to transport ready:

Server # scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-HBA
Server /chassis/server/storageadapter # scope virtual-drive 5
Server /chassis/storageadapter/virtual-drive # set-transport-ready exclude-all
Since they belong to same drive group, all these virtual drives will be set to Transport Ready - 0
Are you sure you want to proceed?[y|N]y
Server /chassis/storageadapter/virtual-drive # show detail
Virtual Drive 0:
    Health: Good
    Status: Optimal
    Visibility : Visible
    Name: RAID0_124_RHEL
    Size: 2858160 MB
    Physical Drives: 1, 2, 4
    RAID Level: RAID 0
    Boot Drive: false
    FDE Capable: 0
    FDE Enabled: 0
    Target ID: 0
    Strip Size: 64 KB
    Drives Per Span: 3
    Span Depth: 1
    Access Policy: Transport Ready
    Cache Policy: Direct
    Read Ahead Policy: None
    Requested Write Cache Policy: Write Through
    Current Write Cache Policy: Write Through
    Disk Cache Policy: Unchanged
    Auto Snapshot: false
    Auto Delete Oldest: true
    Allow Background Init: true
Server /chassis/server/storageadapter/virtual-drive #

Clearing a Virtual Drive as Transport Ready

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters the chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter slot ID	Enters the command mode for an installed storage card.
Step 4	Server /chassis/server/storageadapter # scope virtual-drive drive-number	Enters the command mode for the specified virtual drive.
Step 5	Server /chassis/server/storageadapter/virtual-drive # clear-transport-ready	This reverts the selected transport ready virtual drive to its original state. When you are prompted to confirm the action. Enter `y` to confirm.
Step 6	Server /chassis/server/storageadapter/virtual-drive # show detail	(Optional) Display the virtual drive properties with the change.

This example shows how to revert the selected transport ready virtual drive to its original state:

Server # scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-HBA
Server /chassis/server/storageadapter # scope virtual-drive 5
Server /chassis/storageadapter/virtual-drive # clear-transport-ready
Since they belong to same drive group, all these virtual drives will be moved out of Transport Ready - 0
Are you sure you want to proceed?[y|N]y
Server /chassis/storageadapter/virtual-drive # show detail
Virtual Drive 0:
    Health: Good
    Status: Optimal
    Visibility : Visible
    Name: RAID0_124_RHEL
    Size: 2858160 MB
    Physical Drives: 1, 2, 4
    RAID Level: RAID 0
    Boot Drive: false
    FDE Capable: 0
    FDE Enabled: 0
    Target ID: 0
    Strip Size: 64 KB
    Drives Per Span: 3
    Span Depth: 1
    Access Policy: Read-Write
    Cache Policy: Direct
    Read Ahead Policy: None
    Requested Write Cache Policy: Write Through
    Current Write Cache Policy: Write Through
    Disk Cache Policy: Unchanged
    Auto Snapshot: false
    Auto Delete Oldest: true
    Allow Background Init: true
Server /chassis/server/storageadapter/virtual-drive #

Importing Foreign Configuration

When one or more physical drives that have previously been configured with a different controller are inserted into a server, they are identified as foreign configurations. You can import these foreign configurations to a controller.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

Command or Action

Purpose

Step 1

Server # scope chassis

Enters chassis command mode.

Step 2

Server /chassis # scope server {1 | 2}

Enters server command mode of server 1 or 2.

Step 3

Server /chassis/server # scope storageadapter Slot-ID

Enters storage adapter command mode.

Step 4

Server /chassis/server/storageadapter # import-foreign-config

You are prompted to confirm the action. Enter yes to confirm.

Note

If you do not enter yes, the action is aborted.

This example shows how to import all foreign configurations on the MegaRAID controller in slot 3:

Server# scope chassis
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # import-foreign-config
Are you sure you want to import all foreign configurations on this controller?
Enter 'yes' to confirm -> yes
Server /chassis/server/storageadapter #

Clearing Foreign Configuration

Important:

This task clears all foreign configuration on the controller. Also, all configuration information from all physical drives hosting foreign configuration is deleted. This action cannot be reverted.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

Command or Action

Purpose

Step 1

Server # scope chassis

Enters chassis command mode.

Step 2

Server /chassis # scope server {1 | 2}

Enters server command mode of server 1 or 2.

Step 3

Server /chassis/server # scope storageadapter Slot-ID

Enters storage adapter command mode.

Step 4

Server /chassis/server/storageadapter # clear-foreign-config

You are prompted to confirm the action. Enter yes to confirm.

Note

If you do not enter yes, the action is aborted.

This example shows how to clear all foreign configurations on the MegaRAID controller in slot 3:

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # clear-foreign-config
Are you sure you want to clear all foreign configurations on this controller?
All data on the drive(s) will be lost.
Enter 'yes' to confirm -> yes
Server /chassis/server/storageadapter #

Enabling and Disabling JBOD

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # enable-jbod-mode	Enables the JBOD Mode for the selected controller
Step 5	Server /chassis/server/storageadapter # disable-jbod-mode	Disables the JBOD Mode for the selected controller

This example enables and disables the JBOD mode for the selected controller:

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Enabling JBOD
Server /chassis/server/storageadapter # enable-jbod-mode 
Are you sure you want to enable JBOD mode?
Enter 'yes' to confirm -> yes
Server/chassis/server/storageadapter # show settings
PCI Slot SLOT-3:
    Info Valid: Yes
    Enable JBOD Mode: true
Disabling JBOD
Server /chassis/server/storageadapter # disable-jbod-mode 
Are you sure you want to disable JBOD mode?
Enter 'yes' to confirm -> yes
Server/chassis/server/storageadapter # show settings
PCI Slot SLOT-3:
    Info Valid: Yes
    Enable JBOD Mode: false

What to Do Next

Clearing a Boot Drive

Important:

This task clears the boot drive configuration on the controller. This action cannot be reverted.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

Command or Action

Purpose

Step 1

Server # scope chassis

Enters chassis command mode.

Step 2

Server /chassis # scope server {1 | 2}

Enters server command mode of server 1 or 2.

Step 3

Server /chassis/server # scope storageadapter Slot-ID

Enters storage adapter command mode.

Step 4

Server /chassis/server/storageadapter # clear-boot-drive

You are prompted to confirm the action. Enter yes to confirm.

Note

If you do not enter yes, the action is aborted.

This example shows how to clear the boot drive configuration on the MegaRAID controller in slot 3:

Server# scope chassis
Server/chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # clear-boot-drive
Are you sure you want to clear the controller's boot drive? 
Enter 'yes' to confirm -> yes
Server /chassis/server/storageadapter #

Retrieving Storage Firmware Logs for a Controller

This task retrieves the firmware logs for the controller and places it in the /var/log location. This ensures that this log data is available when Technical Support Data is requested.

Before You Begin

You must log in with admin privileges to perform this task

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters the chassis command mode.
Step 2	Server /chassis # scope storageadapter slot	Enters the command mode for an installed storage card.
Step 3	Server /chassis/storageadapter # get-storage-fw-log	Retrieves the storage firmware log file to the specified controller.
Step 4	At the prompt, enter `yes`.	Begins download of the storage firmware log files.

This example shows how to view the download status of the retrieved storage firmware log files:

Server # scope chassis
Server /chassis # scope storageadapter SLOT-HBA
Server /chassis/storageadapter # get-storage-fw-log

You are initiating the retrieval of the storage firmware log to Cisco IMC.
This task will take a few minutes to complete. You may monitor the status
  of the retrieval by running the 'get-storage-fw-log-download-progress' command.
When the download is finished, the 'Storage Firmware Log Status' value will be
  'Complete', along with the size of the logfile.
You may then download the log file using the Technical Support facility,
  accessible from /cimc/tech-support scope, or the WebUI's Utilities page.

Do you want to proceed?
Enter 'yes' to confirm -> yes
Server /chassis/storageadapter # get-storage-fw-log-download-progress
Storage Firmware Log Status: Complete (total size 61906 bytes)

Deleting a Virtual Drive

Important:

This task deletes a virtual drive, including the drives that run the booted operating system. So back up any data that you want to retain before you delete a virtual drive.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

Command or Action

Purpose

Step 1

Server # scope chassis

Enters chassis command mode.

Step 2

Server /chassis # scope server {1 | 2}

Enters server command mode of server 1 or 2.

Step 3

Server /chassis/server # scope storageadapter Slot-ID

Enters storage adapter command mode.

Step 4

Server /chassis/server/storageadapter # scope virtual-drive drive-number

Enters command mode for the specified virtual drive.

Step 5

Server /chassis/server/storageadapter/virtual-drive # delete-virtual-drive

You are prompted to confirm the action. Enter yes to confirm.

Note

If you do not enter yes, the action is aborted.

This example shows how to delete virtual drive 3.

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # scope virtual-drive 3
Server /chassis/server/storageadapter/virtual-drive # delete-virtual-drive
Are you sure you want to delete virtual drive 3?
All data on the drive will be lost.  Enter 'yes' to confirm -> yes
Server /chassis/server/storageadapter/virtual-drive #

Initializing a Virtual Drive

All data on a virtual drive is lost when you initialize the drive. Before you run an initialization, back up any data on the virtual drive that you want to save.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope virtual-drive drive-number	Enters command mode for the specified virtual drive.
Step 5	Server /chassis/server/storageadapter/virtual-drive # start-initialization	Initializes the specified virtual drive.
Step 6	Server /chassis/server/storageadapter/virtual-drive # cancel-initialization	(Optional) Cancels the initialization of the specified virtual drive.
Step 7	Server /chassis/server/storageadapter/physical-drive # get-operation-status	Displays the status of the task that is in progress on the drive.

This example shows how to initialize virtual drive 3 using fast initialization:

Server# scope chassis
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/storageadapter # scope virtual-drive 3
Server /chassis/server/storageadapter/virtual-drive # start-initialization
Are you sure you want to initialize virtual drive 3?
All data on the drive will be lost.  Enter 'yes' to confirm -> yes
Fast (0) or full (1) initialization?  -> 0
Server /chassis/server/storageadapter/virtual-drive # get-operation-status

progress-percent: 20%
elapsed -seconds: 30
operation-in-progress: initializing virtual drive

Server /chassis/server/storageadapter/virtual-drive #

Set as Boot Drive

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope virtual-drive drive-number	Enters command mode for the specified virtual drive.
Step 5	Server /chassis/server/storageadapter # set-boot-drive	Specifies the controller to boot from this virtual drive.

This example shows how to specify the controller to boot from virtual drive 3:

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # scope virtual-drive 3
Server /chassis/server/storageadapter/virtual-drive # set-boot-drive
Are you sure you want to set virtual drive 3 as the boot drive?
Enter 'yes' to confirm -> yes
Server /chassis/server/storageadapter/virtual-drive #

Editing a Virtual Drive

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server chassis/server/storageadapter # scope virtual-drive drive number	Enters command mode for the specified virtual drive.
Step 5	Server chassis/server/storageadapter /virtual-drive # modify-attributes	Prompts you to select a different current policy.
Step 6	Server chassis/server/storageadapter/virtual-drive# set raid-level value	Specifies the RAID level for the specified virtual drive.
Step 7	Server chassis/server/storageadapter/virtual-drive# set physical-drive value	Specifies the physical drive for the specified virtual drive.

This example shows to edit a virtual drive:

Server# scope chassis
Server /chassis # scope chassis
Server /chassis/server # scope storageadapter slot-3
Server /chassis/server/storageadapter # scope virtual-drive 3
Server /chassis/server/storageadapter/virtual-drive #set raid-level 1
Server /chassis/server/storageadapter/virtual-drive *# physical-drive 1
Server /chassis/server/storageadapter/virtual-drive* #commit
Server /chassis/server/storageadapter /virtual-drive # modify-attribute
Current write policy: Write Back Good BBU

    0: Write Through
    1: Write Back Good BBU
    2: Always Write Back
  Choose number from above options--> 0
The following attribute will be modified:
  - Write Policy: Write Through

OK? (y or n)--> y
Server /chassis/server/storageadapter/virtual-drive #

Modifying Attributes of a Virtual Drive

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope virtual-drive 3	Enters the command mode for the virtual drive.
Step 5	Server /chassis/server/storageadapter/virtual-drive # modify-attributes	Prompts you to select a different current policy.

This example shows how to carve a new virtual drive out of unused space in an existing RAID 1 drive group:

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # scope virtual-drive
Server /chassis/server/storageadapter/virtual-drive # modify-attributes

Current write policy: Write Back

  0: Write Through
  1: Write Back
  2: Write Back even if Bad BBU

Choose number from above options --> 0

The following attribute will be modified:

 - Write policy: Write Through

OK? (y or n) --> y

operation in progress.

Server /chassis/server/storageadapter/virtual-drive #

Making a Dedicated Hot Spare

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope physical-drive drive-number	Enters command mode for the specified physical drive.
Step 5	Server /chassis/server/storageadapter/physical-drive # make-dedicated-hot-spare	You are prompted to choose a virtual drive for which the dedicated hot spare is being created.

This example shows how to make physical drive 3 a dedicated hot spare for virtual drive 6:

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # scope physical-drive 3
Server /chassis/server/storageadapter/physical-drive # make-dedicated-hot-spare
  5: VD_OS_1, RAID 0, 102400 MB, physical disks: 1
  6: VD_OS_2, RAID 0, 12288 MB, physical disks: 1
  7: VD_OS_3, RAID 0, 12288 MB, physical disks: 1
  8: VD_DATA_1, RAID 0, 12512 MB, physical disks: 1
  9: RAID1_2358, RAID 1, 40000 MB, physical disks: 2,3,5,8
  11: JFB_RAID1_67, RAID 1, 20000 MB, physical disks: 6,7
  12: JFB_Crv_R1_40, RAID 1, 40000 MB, physical disks: 6,7
  13: JFB_R1_10GB, RAID 1, 10000 MB, physical disks: 6,7

  Please choose from the above 8 virtual drives-->6

Server /chassis/server/storageadapter/physical-drive #

Making a Global Hot Spare

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope physical-drive drive-number	Enters command mode for the specified physical drive.
Step 5	Server /chassis/server/storageadapter/physical-drive # make-global-hot-spare
Step 6	Server /chassis/server/storageadapter/physical-drive # get-operation-status	Displays the status of the task that is in progress on the drive.

This example shows how to make physical drive 3 a global hot spare:

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # scope physical-drive 3
Server /chassis/server/storageadapter/physical-drive # make-global-hot-spare
Server /chassis/server/storageadapter/physical-drive #

Preparing a Drive for Removal

You can confirm this task only on physical drives that display the Unconfigured Good status.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope physical-drive drive-number	Enters command mode for the specified physical drive.
Step 5	Server /chassis/server/storageadapter/physical-drive # prepare-for-removal

This example shows how to prepare physical drive 3 for removal.

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # scope physical-drive 3
Server /chassis/server/storageadapter/physical-drive # prepare-for-removal
Server /chassis/server/storageadapter/physical-drive #

Toggling Physical Drive Status

Before You Begin

You must log in with admin privileges to perform this task.
The controller must support the JBOD mode and the JBOD mode must be enabled.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope physical-drive 4	Enters command mode for the physical drive.
Step 5	Server /chassis/server/storageadapter/physical-drive # make-unconfigured-good	Modifies the status of the drive to Unconfigured good.
Step 6	Server /chassis/server/storageadapter/physical-drive # make-jbod	Enables the JBOD mode on the physical drive.

This example shows how to toggle between the status of the physical drive:

Server# scope chassis
Server /chassis # scope chassis
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # scope physical-drive 4
Server /chassis/server/storageadapter/physical-drive # show detail
Physical Drive Number 4:
    Controller: SLOT-4
    Health: Good
    Status: JBOD
    Boot Drive: true
    Manufacturer: ATA
    Model: ST500NM0011
    Predictive Failure Count: 0
    Drive Firmware: CC02
    Coerced Size: 476416 MB
    Type: HDD
Server /chassis/server/storageadapter/physical-drive # make-unconfigured-good
Server /chassis/server/storageadapter/physical-drive # show detail
Physical Drive Number 4:
    Controller: SLOT-4
    Health: Good
    Status: Unconfigured Good
    Boot Drive: true
    Manufacturer: ATA
    Model: ST500NM0011
    Predictive Failure Count: 0
    Drive Firmware: CC02
    Coerced Size: 476416 MB
    Type: HDD
Server /chassis/server/storageadapter/physical-drive # make-jbod
Server /chassis/server/storageadapter/physical-drive # show detail
Physical Drive Number 4:
    Controller: SLOT-4
    Health: Good
    Status: JBOD
    Boot Drive: true
    Manufacturer: ATA
    Model: ST500NM0011
    Predictive Failure Count: 0
    Drive Firmware: CC02
    Coerced Size: 476416 MB
    Type: HDD

Setting a Physical Drive as a Controller Boot Drive

Before You Begin

You must log in with admin privileges to perform this task.
The controller must support the JBOD mode and the JBOD mode must be enabled.

Procedure

Command or Action

Purpose

Step 1

Server # scope chassis

Enters chassis command mode.

Step 2

Server /chassis # scope server {1 | 2}

Enters server command mode of server 1 or 2.

Step 3

Server /chassis/server # scope storageadapter Slot-ID

Enters storage adapter command mode.

Step 4

Server /chassis/server/storageadapter # scope physical-drive 4

Enters command mode for the physical drive.

Step 5

Server /chassis/server/storageadapter/physical-drive # set-boot-drive

You are prompted to confirm the action. Enter yes to confirm.

Note

If you do not enter yes, the action is aborted.

This example shows how to set a physical drive as a boot drive for a controller:

Server# scope chassis
Server/chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # show detail
PCI Slot SLOT-4:
    Health: Good
    Controller Status: Optimal
    ROC Temperature: Not Supported
    Product Name: MegaRAID 9240-8i (RAID 0,1,10,5)
    Serial Number: SP23807413
    Firmware Package Build: 20.11.1-0159
    Product ID: LSI Logic
    Battery Status: no battery
    Cache Memory Size: 0 MB
    Boot Drive: none
    Boot Drive is PD: false
    TTY Log Status: Not Downloaded
Server /chassis/server/storageadapter # scope physical-drive 4
Server /chassis/server/storageadapter/physical-drive # set-boot-drive 
Are you sure you want to set physical drive 4 as the boot drive?
Enter 'yes' to confirm -> yes
Server /chassis/server/storageadapter/physical-drive # exit
Server /chassis/server/storageadapter # show detail
PCI Slot SLOT-4:
    Health: Good
    Controller Status: Optimal
    ROC Temperature: Not Supported
    Product Name: MegaRAID 9240-8i (RAID 0,1,10,5)
    Serial Number: SP23807413
    Firmware Package Build: 20.11.1-0159
    Product ID: LSI Logic
    Battery Status: no battery
    Cache Memory Size: 0 MB
    Boot Drive: 4
    Boot Drive is PD: true
    TTY Log Status: Not Downloaded

Removing a Drive from Hot Spare Pools

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope physical-drive drive-number	Enters command mode for the specified physical drive.
Step 5	Server /chassis/server/storageadapter/physical-drive # remove-hot-spare	Removes a drive from the host spare pool.

This example shows how to remove physical drive 3 from the hot spare pools:

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # scope physical-drive 3
Server /chassis/server/storageadapter/physical-drive # remove-hot-spare
Server /chassis/server/storageadapter/physical-drive #

Undo Preparing a Drive for Removal

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope physical-drive drive-number	Enters command mode for the specified physical drive.
Step 5	Server /chassis/server/storageadapter/physical-drive # undo-prepare-for-removal

This example shows how to respin physical drive 3 after preparing the drive for removal.

Server# scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # scope physical-drive 3
Server /chassis/server/storageadapter/physical-drive # undo-prepare-for-removal
Server /chassis/server/storageadapter/physical-drive #

Enabling Auto Learn Cycles for the Battery Backup Unit

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope bbu	Enter the battery backup unit command mode.
Step 5	Server /chassis/server/storageadapter # enable-auto-learn	Enables the battery auto-learn cycles

This example shows how to enable the battery auto-learn cycles:

Server # scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-2
Server /chassis/server/storageadapter # scope bbu
Server /chassis/server/storageadapter/bbu # enable-auto-learn
Automatic BBU learn cycles will occur without notice if enabled.
Are you sure? [y/n] --> y
enable-auto-learn initiated
Server /chassis/server/storageadapter/bbu #

Disabling Auto Learn Cycles for the Battery Backup Unit

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope bbu	Enter the battery backup unit command mode.
Step 5	Server /chassis/server/storageadapter # disable-auto-learn	Disables the battery auto-learn cycles

This example shows how to disables the battery auto-learn cycles:

Server # scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-2
Server /chassis/server/storageadapter # scope bbu
Server /chassis/server/storageadapter/bbu # disable-auto-learn
Automatic BBU learn cycles will no longer occur if disabled.
Are you sure? [y/n] --> y
disable-auto-learn initiated

Server /chassis/server/storageadapter/bbu #

Starting a Learn Cycle for a Battery Backup Unit

Before You Begin

You must be logged in as an admin to use this command.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope bbu	Enter the battery backup unit command mode.
Step 5	Server /chassis/server/storageadapter # start-learn-cycle	Starts the learn cycle for the battery.

This example shows how to initiate the learn cycles for a battery:

Server # scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-2
Server /chassis/server/storageadapter # scope bbu
Server /chassis/server/storageadapter/bbu # start-learn-cycle
Server /chassis/server/storageadapter/bbu #

Toggling the Locator LED for a Physical Drive

Before You Begin

You must be logged in as an admin to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # scope physical-drive 3	Enters the physical drive command mode.
Step 5	Server /chassis/server/storageadapter/physical-drive # locator-led {on \| off}	Enables or disables the physical drive locator LED.

This example shows how to enable the locator LED for physical drive 3:

Server # scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-2
Server /chassis/server/storageadapter # scope physical-drive 3
Server /chassis/server/storageadapter/physical-drive # locator-led on
Server /chassis/server/storageadapter/physical-drive* # commit
Server /chassis/server/storageadapter/physical-drive #

Viewing Storage Controller Logs

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server # scope chassis	Enters chassis command mode.
Step 2	Server /chassis # scope server {1 \| 2}	Enters server command mode of server 1 or 2.
Step 3	Server /chassis/server # scope storageadapter Slot-ID	Enters storage adapter command mode.
Step 4	Server /chassis/server/storageadapter # show log	Displays the storage controller logs.

This example shows how to display storage controller logs:

Server # scope chassis
Server /chassis # scope server 1
Server /chassis/server # scope storageadapter SLOT-3
Server /chassis/server/storageadapter # show log

Time                        Severity         Description
----                        --------        -------------
Fri March 1 09:52:19 2015   Warning      Predictive Failure
Fri March 1 07:50:19 2015   Info         Battery charge complete 
Fri March 1 07:50:19 2015   Info         Battery charge started
Fri March 1 07:48:19 2015   Info         Battery relearn complete
Fri March 1 07:47:19 2015   Info         Battery is discharging
Fri March 1 07:45:19 2015   Info         Battery relearn started

Server /chassis/server/storageadapter #

Bias-Free Language

Book Title

Cisco UCS C-Series Integrated Management Controller CLI Configuration Guide for C3X60 Servers

Chapter Title

Managing Storage Adapters

Results

Chapter: Managing Storage Adapters

Managing Storage Adapters

Creating Virtual Drives from Unused Physical Drives

Creating Virtual Drive from an Existing Drive Group

Setting a Virtual Drive as Transport Ready

Clearing a Virtual Drive as Transport Ready

Importing Foreign Configuration

Clearing Foreign Configuration

Enabling and Disabling JBOD

Clearing a Boot Drive

Retrieving Storage Firmware Logs for a Controller

Deleting a Virtual Drive

Initializing a Virtual Drive

Set as Boot Drive

Editing a Virtual Drive

Modifying Attributes of a Virtual Drive

Making a Dedicated Hot Spare

Making a Global Hot Spare

Preparing a Drive for Removal

Toggling Physical Drive Status

Setting a Physical Drive as a Controller Boot Drive

Removing a Drive from Hot Spare Pools

Undo Preparing a Drive for Removal

Enabling Auto Learn Cycles for the Battery Backup Unit

Disabling Auto Learn Cycles for the Battery Backup Unit

Starting a Learn Cycle for a Battery Backup Unit

Toggling the Locator LED for a Physical Drive

Viewing Storage Controller Logs

Was this Document Helpful?

Contact Cisco